IPP Mail Archive by subject
IPP Mail Archive by subject
Starting: Fri 08 Nov 1996 - 00:00:-47207 EST
Ending: Thu 12 Feb 1998 - 03:11:27 EST
Messages: 3353
- "Held" is not Active [Ok if I don't include
- "NEED NOT" is a better negative than "MAY NOT" - from
- "NEED NOT" is a better negative than "MAY NOT" - from POSIX [and capatalizing con
- (no subject)
- -No Subject-
- 0.92 review comments
- 0.92 review comments [by Roger and Scott]
- 0.92 review comments [by Roger and Scott] -Reply
- [Fwd: IPP> create job IPP operation]
- [Fwd: SEC - Protocol names for security protocols]]
- ABNF
- adding <jobs-in-queue> to ipp [relates to JMP]
- Additional IPP comments
- Additional IPP comments -Reply
- ADM - Advice to the Editors
- ADM - Draft minutes [client security issues]
- ADM - ftp server directory names and PDF
- ADM - IPP Charter and Slot in Memphis
- ADM - IPP Charter and Slot in Memphis -Reply
- ADM - IPP Documents for the IETF
- Agenda for the WG-Chairs/Directorate meeting
- Albuquerque Meeting
- Are "embellishments" really desirable right now?
- Area Directors' comments on
- Area Directors' comments on IPP
- Area Directors' comments on IPP)
- Ascii maps
- BOF for IPP
- Can I distribute the X/Open PSIS/XDPA Appendix on LPD
- Comm Protocols for IPP
- Comments on Requirements document
- Comments on shortest-job-first attribute
- Compiled list of directory schema issues
- Compiled list of directory schema issues; Comments
- complaint from Keith Moore on press release
- Conference Call
- Content-disposition: A better place for command verbs?
- deBry Section 5.1 updates on FTP server
- deBry security proposal
- Directory Entry Schema
- Draft for IETF IPP WG
- draft-isaacson-ipp-info-00.txt
- draft-isaacson-ipp-info-00.txt -Reply
- draft-mutz-http-attributes-02.txt
- Editorial comments to IPP93.doc
- emerging directory schema standards?
- Empty values (and unspecified attributes) in IPP
- First draft of Schema Registry charter
- For IPP Wed 13-Nov telecon: proposal for objects, operations,
- FTP Server problem (Was: Suggested text for the state syntax in IPP V0.92)
- FW: IPP> FW: MyPost vs. Post
- FW: reminder of Internet-Draft cutoff date
- Fwd: RE: IPP> MOD - UPDATE FOR STATUS CODE KEYWORDS IN THE M
- General Issues
- How should the server behave
- I'm getting: "Message not deliverable" when I send to ipp DL
- I've created a http-related-rfcs directory under ipp/
- I-D ACTION:draft-holtman-http-negotiation-04.txt
- IETF Agenda
- IETF BOF PING
- IETF draft for publication
- IETF vs PWG
- IFax security)
- Inconsistency with REQUESTED attributes [I don't think its
- IPP
- IPP 0.92 is in drafts
- IPP > FAQ - How should the server behave?
- IPP > TES> IBM Client Prototype
- IPP Action Items
- IPP Additional info about the BOF
- IPP Agenda for Teleconference - Wednesday November 13
- IPP and OMG PF coordination)
- IPP and OMG PF coordination.
- IPP charter
- IPP Charter - Overlap with IETF Fax?
- IPP Charter modifications
- IPP Conference Call - December 4th
- IPP conflict with TLS in DC
- IPP Cost for attending just the IETF BOF on Internet Printing
- IPP developers mailing list established
- IPP document for ipp phone call on Wednesday 11/13
- IPP formatting problem: 8-bit characters present and how to
- IPP FYI: Novell announcing free LDAP server
- IPP Headlines: Fax and Printing get "mixed up"
- IPP ietf-fax charter
- IPP Last Call
- IPP Mail Archive: RE: IPP> Notifications
- IPP Mark your Calendars for December 12
- IPP Name
- IPP over TCP
- IPP over TCP -Reply
- IPP PING for IETF BOF Meeting on December 12
- IPP PING for IETF BOF Meeting on December 12 -Reply
- IPP Prototyping
- IPP Revised Charter Text
- IPP SEC - suggestions for Model document
- IPP Security
- IPP test
- IPP test message
- IPP The IETF Application Area rules for starting a WG
- IPP Version 0.92
- IPP Version 0.92 -Reply
- IPP Version 0.93
- IPP WG Last Call for Requirements and LPD Mapping drafts
- IPP. Who gets to hijack ? **READ - IMPORTANT** -
- ipp92.doc - Concept Virus
- IPP>
- IPP> "Asynchronous Notification"
- IPP> "form-data" as a separate draft
- IPP> "IPP" == "DPA"
- IPP> "IPP" == "DPA" -Reply
- IPP> ....IMPORTANT - A4-US letter tug of war treaty !
- IPP> 1/15/97 Conference Call
- IPP> 11/26 Conference Call
- IPP> 2/19/97 IPP Conference Call Minutes
- IPP> 38th IETF: IPP
- IPP> > QUIZ < MAC addresses - where does one register as a manufacturer ??
- IPP> >REQ - Requirements Internet Draft available
- IPP> [Fwd: I-D ACTION:draft-ietf-urn-naptr-03.txt]
- IPP> [Fwd: keeping the LDAP survey current]
- IPP> A few typos in 980116 Model document
- IPP> A free IPP test suite to be available!
- IPP> A friendly reminder to "ping" for the PWG meeting in Austin
- IPP> ABNF near finished?
- IPP> ABNF near finished? [problem with - for range?]
- IPP> ABNF syntax document
- IPP> ABQ PINGers
- IPP> Acrobat PDF files now available for recently posted REQ/PRO files
- IPP> Additional comments on PRO + MOD docs...
- IPP> Additional proposal details
- IPP> Additional proposal details [why
- IPP> ADM
- IPP> ADM Test post - IGNORE
- IPP> ADM - 2/19 Teleconference Agenda
- IPP> ADM - 2/26 telecon notes (partial)
- IPP> ADM - 9/3/97 Telecon minutes
- IPP> ADM - Advice to the Editors
- IPP> ADM - Agenda for 970212 Telephone Conference
- IPP> ADM - Agenda for Conference Call on 970326
- IPP> ADM - Agenda for IETF IPP WG Meeting
- IPP> ADM - Agenda for IPP Conference call - April 30, 1997
- IPP> ADM - Agenda for IPP Conference Call 970305
- IPP> ADM - Agenda for IPP meeting in Austin, TX on April 3, 1997
- IPP> ADM - Agenda for IPP Meeting in San Jose February 6
- IPP> ADM - Agenda for IPP Phone Conference 970226
- IPP> ADM - Agenda for IPP Phone Conference 970312
- IPP> ADM - Agenda for IPP Phone Conference April 15, 1997
- IPP> ADM - Agenda for IPP Phone Conference on 970219
- IPP> ADM - Agenda for January 29 Phone Conference
- IPP> ADM - Agenda for Munich
- IPP> ADM - Agenda for PWG IPP Conference Call - May 7, 1997
- IPP> ADM - Agenda for PWG IPP Conference Call 970924
- IPP> ADM - Agenda for PWG IPP Meeting in Atlanta September 17-18,
- IPP> ADM - Agenda for PWG IPP Meeting in Nassua NH
- IPP> ADM - Agenda for PWG IPP Meeting in Redmond August 6-7
- IPP> ADM - Agenda for PWG IPP Phone Conference - 980114
- IPP> ADM - Agenda for PWG IPP Phone Conference - 980121
- IPP> ADM - Agenda for PWG IPP Phone Conference - May 28
- IPP> ADM - Agenda for PWG IPP Phone Conference 970723
- IPP> ADM - Agenda for PWG IPP Phone Conference May 21
- IPP> ADM - Agenda for PWG IPP Phone Conference on 971001
- IPP> ADM - Agenda for PWG IPP Phone Conference on 971022
- IPP> ADM - Agenda for PWG IPP Phone Conference on June 11, 1 - 3:30
- IPP> ADM - Agenda for PWG IPP Phone Conference on June 4
- IPP> ADM - Agenda for Telephone Conference Jan 22
- IPP> ADM - Agenda for the IPP Phone Conference April 23, 1997
- IPP> ADM - Agenda Topics for the PWG IPP Phone Conference on
- IPP> ADM - Agenda WITH Phone Numbers
- IPP> ADM - April 3rd IPP Meeting Minutes
- IPP> ADM - Article about IPP in Infoworld
- IPP> ADM - Article about IPP in Web Vantage
- IPP> ADM - barriers to IPP WG participation
- IPP> ADM - Checklist for IPP I-D Document Quality Checking
- IPP> ADM - Co-chair for IPP WG in IETF
- IPP> ADM - Comments on the PWG Press Release Text
- IPP> ADM - Conference calls
- IPP> ADM - Consensus on sending our drafts to the IESG?
- IPP> ADM - Corrections to the latest PWG IPP Teleconference Minutes
- IPP> ADM - Document numerique article on IPP
- IPP> ADM - Draft for IPP press release
- IPP> ADM - Draft minutes from the IETF IPP WG Meeting
- IPP> ADM - Editors submitting I-D
- IPP> ADM - FAQ Text
- IPP> ADM - FAQ Text -Reply
- IPP> ADM - Final Agenda for the PWG IPP meeting in San Diego on May
- IPP> ADM - ftp server directory names and PDF
- IPP> ADM - FYI
- IPP> ADM - General Issues
- IPP> ADM - Goals of the IPP Working Group
- IPP> ADM - Harald's report from the IETF meeting
- IPP> ADM - Harold's travel notes from Munich IETF available
- IPP> ADM - HELP
- IPP> ADM - How is IPP a "compatible subset" of DPA?
- IPP> ADM - How is IPP a "compatible subset" of DPA? -Reply
- IPP> ADM - How to follow the fate of the IPP drafts
- IPP> ADM - How to follow up on IESG comments on IPP
- IPP> ADM - How to learn about XML
- IPP> ADM - I posted the minutes of 10/22 Phone Conference
- IPP> ADM - IETF Instructions to chairs and presenters
- IPP> ADM - IETF38
- IPP> ADM - IPP Charter and Slot in Memphis
- IPP> ADM - IPP Documents for the IETF
- IPP> ADM - IPP in the News
- IPP> ADM - IPP in the press
- IPP> ADM - IPP Phone Comnference - Minutes from 970319
- IPP> ADM - IPP Phone Conference July 9 & 16, 1997
- IPP> ADM - IPP Phone conference on Wednesday
- IPP> ADM - Issues List for Seattle Meeting
- IPP> ADM - Last Call for Model and Protocol documents now closed
- IPP> ADM - Last minute information for PWG LA meeting
- IPP> ADM - Maui PWG IPP Meeting on 28 and 29 and Januari 7 Phone
- IPP> ADM - Meeting Minutes and Presentations from Munich
- IPP> ADM - Minutes for TLS WG meeting, 12/10/97
- IPP> ADM - Minutes from 7/23/97 Phone Conference
- IPP> ADM - Minutes from IPP 9/10/97 telecon
- IPP> ADM - Minutes from IPP Conference Call 970305
- IPP> ADM - Minutes from IPP Telephone Conference on April 30, 1997
- IPP> ADM - Minutes from Munich
- IPP> ADM - Minutes from PWG IPP Phone Confeence - 980121
- IPP> ADM - Minutes from PWG IPP Phone Conference - 980107
- IPP> ADM - Minutes from PWG IPP Phone Conference - 98011
- IPP> ADM - Minutes from PWG IPP Phone Conference - 980114
- IPP> ADM - Minutes from PWG IPP Phone Conference 970709
- IPP> ADM - Minutes from PWG IPP Phone Conference 971008
- IPP> ADM - Minutes from PWG IPP Phone Conference 971015
- IPP> ADM - Minutes from PWG IPP Phone Conference 971105
- IPP> ADM - Minutes from PWG IPP Phone Conference on 970924
- IPP> ADM - Minutes from PWG IPP Phone Conference on 971001
- IPP> ADM - Minutes from PWG IPP Phone Conference on June 11, 1997
- IPP> ADM - minutes of 10/22 Phone Conference
- IPP> ADM - Minutes of 10/29 - 10/30 IPP Meeting, Boulder
- IPP> ADM - Minutes of 7/16 IPP Phone Call
- IPP> ADM - Minutes of the IPP telecon, Wed, 11/19/97
- IPP> ADM - Muich Meeting Deadlines
- IPP> ADM - Munich Agenda
- IPP> ADM - Munich IETF Meeting
- IPP> ADM - Name of the Requirements Document etc.
- IPP> ADM - New draft from Harald on Character Sets & Languages
- IPP> ADM - New drafts of Model and Protocol documents
- IPP> ADM - New version of the IPP FAQ document
- IPP> ADM - No more "contributions-for-discussion" folder!!!!
- IPP> ADM - No PWG IPP Phone Conference on July 2
- IPP> ADM - Novell Press Release
- IPP> ADM - old PC week article
- IPP> ADM - PC Week Report on IPP
- IPP> ADM - Phone Conference into PWG IPP Meeting - 980128
- IPP> ADM - Phone Conference into PWG IPP Meeting on December 3
- IPP> ADM - Phone Conference into the PWG IPP Meeting - REMINDER
- IPP> ADM - PING for IETF in Munich
- IPP> ADM - PING time for Memphis
- IPP> ADM - Presentations from Memphis now on FTP server
- IPP> ADM - Proposal for revised IETF Charter
- IPP> ADM - Proprietary Internet Printing under way
- IPP> ADM - Protocol Specification and LPD Mapping to IETF
- IPP> ADM - PWG IPP Confeence Call on 980211
- IPP> ADM - PWG IPP in Maui - Participants
- IPP> ADM - PWG IPP Phone Conference - 971126
- IPP> ADM - PWG IPP Phone Conference - July 16, 1997
- IPP> ADM - PWG IPP Phone Conference - July 9, 1997
- IPP> ADM - PWG IPP Phone Conference - September 10
- IPP> ADM - PWG IPP Phone Conference 971105
- IPP> ADM - PWG IPP Phone Conference 971112
- IPP> ADM - PWG IPP Phone Conference 971112, 1:00 - 3:00 pm PST
- IPP> ADM - PWG IPP Phone Conference on 971008
- IPP> ADM - PWG IPP Phone Conference on 971015
- IPP> ADM - PWG Meeting in LA, December 1 - 5
- IPP> ADM - PWG Press Release
- IPP> ADM - Request for a slot for Internet Printing Protocol (IPP)
- IPP> ADM - Requirements for TXT format documentation
- IPP> ADM - Revised text for press release
- IPP> ADM - Revised version of the FAQ
- IPP> ADM - RFC 2223 - Instructions to RFC Authors
- IPP> ADM - Robin Cover's XML Home Page
- IPP> ADM - Rules for IPP message subject line
- IPP> ADM - Spring cleaning in the SEC folder
- IPP> ADM - Subjects for discussion in Boulder
- IPP> ADM - Subjects for IPP Meeting on April 3 in Austin, TX
- IPP> ADM - Subjects to be added to our Austin Agenda
- IPP> ADM - Suggested rewrite of the press release
- IPP> ADM - Technical Overview of IPP
- IPP> ADM - THANKS
- IPP> ADM - This is not and I-D wording
- IPP> ADM - Two Munich slots for IPP
- IPP> ADM - Unigram about IPP
- IPP> ADM - Upcoming Deadlines
- IPP> ADM - Updated FAQ document
- IPP> ADM - Wake Up Call
- IPP> ADM - We are in
- IPP> ADM - We got our drafts in
- IPP> ADM - We have strong consensus for progressing to IESG
- IPP> ADM - We meet in NASHUA
- IPP> ADM - We now have a slot in Munich
- IPP> ADM - Web pages
- IPP> ADM - What happened to our IPP Charter?
- IPP> ADM - yet another press article
- IPP> ADM -- web pages
- IPP> ADM >Press Release - Alternative Quote
- IPP> ADM, REQ - Spring cleaning in the REQ folder
- IPP> ADM: Conference Calls 1/7, 1/14, 1/21
- IPP> ADM: Conference Calls 2/11, 2/18
- IPP> ADM> Conference Call Schedule
- IPP> ADM> IETF Meeting
- IPP> ADM> IPP Conference Call
- IPP> ADM> Press Release Draft
- IPP> ADM>Text Drawings
- IPP> Adobe Job Ticket URL
- IPP> Agenda for December 4 Phone Conference
- IPP> Agenda for February Meeting ?
- IPP> Agenda for PWG IPP Phone Conference on June 18, 1 - 3:30 PST
- IPP> Albuerque
- IPP> Albuquerque Meeting
- IPP> Albuquerque Meeting - PING
- IPP> Albuquerque RSCPs
- IPP> Alignment of IPP and the Job Monitoring MIB
- IPP> Alta-Vista Forum: improved e-meeting
- IPP> Alta-Vista Forum: improved e-meeting approach
- IPP> Alta-Vista Forum: improved e-meeting approach for
- IPP> Alta-Vista Forum: improved e-meeting approach for PWG, PMP,
- IPP> Any TLS prototypes or implementations yet?
- IPP> Appendix-B of Protocol document
- IPP> application/ipp vs. application/print-job
- IPP> April 3rd Meeting Minutes
- IPP> Area Directors' comments on IPP
- IPP> Article on IPP written by Adina Levin of CAPV
- IPP> ASIAN languages in IPP.
- IPP> Atlanta Ping
- IPP> Atlanta Ping List
- IPP> Attribute Summary
- IPP> Attribute syntax
- IPP> Attributes
- IPP> August Meeting Agenda
- IPP> August Meeting Minutes
- IPP> August Printer Working Group Meetings
- IPP> August PWG meetings
- IPP> Background for the upcoming Austin meeting (3 March 98)
- IPP> BOF Minutes
- IPP> BOF Presentation Comments
- IPP> BOF Presentation on Requirements
- IPP> BOF Presentations
- IPP> Boston Meeting
- IPP> Boston PWG and IEEE Meetings
- IPP> Boulder PWG Schedule / LA Meeting Details
- IPP> Boulder Weather
- IPP> briefing model and protocol presentation
- IPP> briefing presentation review telecon
- IPP> Cancel Job operation
- IPP> charset type vs charset printer attribute
- IPP> Client usage of TCP port number selection
- IPP> Comment on LPD Mapping document
- IPP> Comments on BOF Presentation
- IPP> Comments on BOF Presentation -Reply
- IPP> Comments on BOF Presentation -Reply -Reply
- IPP> Comments on Current Requirements Presentation for BOF
- IPP> Comments on IPP BOF Presentation IPP-INFO3
- IPP> Comments on ipp93.doc - posted as \new\ipp93tnh.doc .pdf
- IPP> Comments on Operation attributes and operation validation
- IPP> Comments on Requirements document
- IPP> Comments on the IPP slides, V3 - from Carl-Uno and Tom
- IPP> Comments on the Model Document
- IPP> Comments on the Model Document -Reply
- IPP> Comments on your IPP/LPD mapping document
- IPP> Common alerts from the IETF printer MIB for inclusion in the IPP
- IPP> Common concerns regarding the SWP proposal
- IPP> Comparison of JMP and IPP and some issues for each
- IPP> compression of IPP messages
- IPP> Conference Call
- IPP> Conference Call 2/26/96
- IPP> Conference Call Meeting Minutes
- IPP> Conference Call Minutes
- IPP> Conference Call Minutes for 1/22/97
- IPP> Conference Calls
- IPP> Conference Calls (cancel 7/30 and add 8/20, 8/27)
- IPP> Conference Calls 2/12 & 2/19
- IPP> Connection Maintenance in IPP
- IPP> Consensus on sending our drafts to the IESG
- IPP> Content-disposition: A better place for command verbs?
- IPP> contention document
- IPP> Copy Center example: http://www.sirspeedy.com
- IPP> Correction on the location of the new Internet Draft documents
- IPP> create job IPP operation
- IPP> Current IPP Scenarios Subgroup Participants List
- IPP> December Meeting in LA
- IPP> December Meeting Minutes
- IPP> Delay of IPP ratification
- IPP> Delay of IPP ratification [How big is an XML
- IPP> Denver weather - yuck!!
- IPP> Desperately seeking info on HTTP servers and CGI
- IPP> Desperately seeking info on HTTP servers and CGI scripts
- IPP> Dinner
- IPP> DIR
- IPP> DIR - Comments from an X.500/LDAP specialist
- IPP> DIR - Compiled list of directory schema issues
- IPP> DIR - Directory Issues
- IPP> DIR - Directory Issues -Reply
- IPP> DIR - draft-apple-schema-listing-rqmts-00.txt
- IPP> DIR - ID submitted to IETF and ver 2.0 dir schema doc posted
- IPP> DIR - Mapping of directory attributes to model attributes
- IPP> DIR - new 970612 directory document and Internet-Draft
- IPP> DIR - New Directory issues list
- IPP> DIR - New issues and directory doc posted
- IPP> DIR - Update
- IPP> DIR - X.500 Attributes for Device
- IPP> Directions to DAZEL for Upcoming Meetings
- IPP> Directory Schema attribute question
- IPP> Directory Schema attribute question - resolved
- IPP> DNS resource records for IPP Services
- IPP> Do it all at once? Or do it in incremental steps?
- IPP> Document attributes
- IPP> Document available...(finally)
- IPP> Document IDs for IPP drafts
- IPP> Document production attributes vs. PDL-specified attributes
- IPP> Does the world need a robust host-to-device network
- IPP> Does the world need a robust host-to-device network printing protocol?
- IPP> draft-ietf-ipp-rat-01.txt
- IPP> draft-isaacson-ipp-info-00.txt -Reply
- IPP> DSEC - Presentation from San Diego
- IPP> Dumb question
- IPP> Dumb question -Reply
- IPP> Editorial corrections for the model doc.
- IPP> Encoding
- IPP> extensibility
- IPP> FAQ - How should the server behave?
- IPP> Fax - E-Mail - Ifax Identification
- IPP> Final chance for October reservations
- IPP> Final IPP/JMP job-state and job-state-reasons
- IPP> Firewalls and IPP
- IPP> First draft Mapping of LPR/LPD to IPP in I-D format
- IPP> Focus on IPP
- IPP> Fonts, Job Redirection, and Protocol
- IPP> For the record...
- IPP> Forthcoming PWG Server Outage (12/15 12/16)
- IPP> From Carl-Uno Manros: Proposed Charter Text - Again
- IPP> ftp://ietf.org/internet...t-goldsmith-utf7-01.txt
- IPP> FUN - County Line
- IPP> FUN - Dinner at County Line
- IPP> FW: I-D ACTION:draft-iesg-iana-considerations-01.txt
- IPP> FW: MyPost vs. Post
- IPP> FW: POST vs. New Methods
- IPP> FW: Protocol Action: The TLS Protocol Version 1.0 to Proposed St
- IPP> FW: User Petition on Standards to Netscape and Microsof
- IPP> FW: User Petition on Standards to Netscape and Microsoft
- IPP> FWD: draft-isaacson-ipp-info-00.txt comments.
- IPP> FWD: emerging directory schema standards?
- IPP> FWD: Protocol Action: IETF Policy on Character Sets and
- IPP> FYI...on SSL
- IPP> Get Attributes
- IPP> Getting the $101 rate at the Hyatt hotel for the PWG meeting
- IPP> Give Your Child "One of the Best Children's Videos""
- IPP> Group dinner
- IPP> Handling the request for an Interpreter enum for TIFF-F
- IPP> Happy Holidays
- IPP> Here are my notes from the IETF meeting in San Jose, December
- IPP> Hi
- IPP> Home business opportunity
- IPP> How should a PDF document be indicated in the Printer MIB, Job
- IPP> How to monitor IESG last call comments on IPP?
- IPP> HTTP POST design
- IPP> HTTP proposal (most recent proposal)
- IPP> HTTP transport for IPP
- IPP> HTTP vs. HTTP-lite
- IPP> HTTP vs. HTTP-lite -Reply
- IPP> I-D ACTION: draft-ietf-ipp-security-01.txt
- IPP> I-D ACTION:draft-ietf-drums-abnf-04.txt
- IPP> I-D ACTION:draft-ietf-drums-abnf-05.txt
- IPP> I-D ACTION:draft-ietf-ipp-dir-schema-00.txt
- IPP> I-D ACTION:draft-ietf-ipp-dir-schema-01.txt
- IPP> I-D ACTION:draft-ietf-ipp-lpd-ipp-map-00.txt
- IPP> I-D ACTION:draft-ietf-ipp-lpd-ipp-map-02.txt
- IPP> I-D ACTION:draft-ietf-ipp-lpd-ipp-map-03.txt
- IPP> I-D ACTION:draft-ietf-ipp-model-00.txt
- IPP> I-D ACTION:draft-ietf-ipp-model-01.txt
- IPP> I-D ACTION:draft-ietf-ipp-model-02.txt
- IPP> I-D ACTION:draft-ietf-ipp-model-03.txt
- IPP> I-D ACTION:draft-ietf-ipp-model-04.txt
- IPP> I-D ACTION:draft-ietf-ipp-model-05.txt
- IPP> I-D ACTION:draft-ietf-ipp-model-06.txt
- IPP> I-D ACTION:draft-ietf-ipp-model-07.txt
- IPP> I-D ACTION:draft-ietf-ipp-model-08.txt
- IPP> I-D ACTION:draft-ietf-ipp-model-09.txt
- IPP> I-D ACTION:draft-ietf-ipp-protocol-00.txt
- IPP> I-D ACTION:draft-ietf-ipp-protocol-01.txt
- IPP> I-D ACTION:draft-ietf-ipp-protocol-02.txt
- IPP> I-D ACTION:draft-ietf-ipp-protocol-04.txt
- IPP> I-D ACTION:draft-ietf-ipp-protocol-05.txt
- IPP> I-D ACTION:draft-ietf-ipp-rat-00.txt
- IPP> I-D ACTION:draft-ietf-ipp-rat-01.txt
- IPP> I-D ACTION:draft-ietf-ipp-rat-02.txt
- IPP> I-D ACTION:draft-ietf-ipp-req-00.txt
- IPP> I-D ACTION:draft-ietf-ipp-req-01.txt
- IPP> I-D ACTION:draft-ietf-ipp-security-00.txt (resend)
- IPP> I-D ACTION:draft-ietf-tls-https-00.txt
- IPP> I-D ACTION:draft-lutz-print-types-00.txt
- IPP> IBM Client
- IPP> IBM IPP client
- IPP> IBM Network Printer Manager
- IPP> IBM's IPP Client Prototype Problems
- IPP> Identifying jobs in requests
- IPP> IETF Internet Printing Protocol working group: Request for
- IPP> IETF IPP WG - LAST CALL for Model & Semantics and Protocol
- IPP> IETF vs PWG
- IPP> IETF/IPP Working Group Minutes 8/11/97
- IPP> Ignore attachment
- IPP> Inconsistency with REQUESTED attributes
- IPP> Initial discussion of the Universal Print Driver in San Diego
- IPP> Internet Printing Protocol WG Agenda
- IPP> Internet Printing Web Site
- IPP> Internet-Drafts@ietf.org: I-D
- IPP> ipp & tiff
- IPP> IPP - Communications Week
- IPP> IPP - current documents and implementation
- IPP> IPP > Chunking
- IPP> IPP > FAQ - How should the server behave?
- IPP> IPP > IBM Client Prototype
- IPP> IPP >MOD new model document
- IPP> IPP >MOD: new model document
- IPP> IPP >PRO Protocol Meeting Friday March 7
- IPP> IPP and OMG PF coordination.
- IPP> IPP Attributes
- IPP> IPP Client Prototype
- IPP> IPP Comments on BOF Presentation - Followup to Reply
- IPP> IPP Conference Call - December 18th
- IPP> IPP Conference Call - December 4th
- IPP> IPP Conference Call - January 15, 1997
- IPP> IPP Conference Call Minutes for 2/12/97
- IPP> IPP Conference Calls
- IPP> IPP Conference Calls 3/12, 3/19, 3/26
- IPP> IPP Conference Calls for 2/26 adn 3/5
- IPP> IPP developers mailing list established
- IPP> IPP Error codes
- IPP> IPP implementation question
- IPP> IPP Internet-Draft
- IPP> IPP Internet-Draft -Reply
- IPP> IPP Phone Calls and MIME-type
- IPP> IPP Press Release, Draft 1.06
- IPP> IPP printing standards should be wholely separate from mgmt standards
- IPP> IPP protocol document...
- IPP> IPP Protocol I-D (White paper)
- IPP> IPP Protocol Meeting Minutes
- IPP> IPP Requirements Scenarios
- IPP> IPP SEC - suggestions for Model document
- IPP> IPP Security
- IPP> IPP Server Contention Analysis
- IPP> IPP Table of Contents should have had 4 levels
- IPP> IPP Telecon on 1/15
- IPP> IPP Test Suite
- IPP> IPP WG Last Call for Requirements and LPD Mapping drafts
- IPP> IPP-Security comments and clarifications from the 39th IETF.
- IPP> IPP. Resuming relavant discussions. RFC 1730 as a basis !
- IPP> IPP. Who gets to hijack ? **READ - IMPORTANT**
- IPP> IPP/1.0 BOF Presentation
- IPP> IPP/1.0 BOF Presentation -Reply
- IPP> IPP/HTTP analysis document
- IPP> ipp> Dictionary attribute syntax
- IPP> ipp> Minutes
- IPP> IPP_SEC - New ietf draft
- IPP> ipppreso.ppt
- IPP> ipppreso.ppt (EMBEDDED TEXT VERSION)
- IPP> Is that it?/ A tome from home
- IPP> ISSUE - Dependencies on browsers, shit fights & other code words.
- IPP> ISSUE Resolution: Suggested Print operation results -
- IPP> Issues and agenda for job-state and job-state-reasons for
- IPP> Issues from the TES sub-group
- IPP> Issues List
- IPP> January Meeting Minutes
- IPP> January Meeting Notice
- IPP> JetSend
- IPP> JMP> Job state implementation questions for Unix-based print
- IPP> job attributes et by Printer
- IPP> Job identification mandatory
- IPP> Job state implementation questions for Unix-based
- IPP> Job state implementation questions for Unix-based print queues
- IPP> Job Templates (Retry)
- IPP> Job Templates (Retry) -Reply
- IPP> Job Templates (Retry) [I like getting rid of Job
- IPP> Job Templates (Retry) [I like getting rid of Job Te
- IPP> job-message-from-administrator attribute (section 6.2.3.4)
- IPP> Job-name atribute
- IPP> Job-URI discussion
- IPP> Job-URI vs. Job-Id: How would you handle moving jobs?
- IPP> jobid (one more time)
- IPP> JobID in Win32
- IPP> June 4th Conference Call Minutes
- IPP> June Meeting in Boston
- IPP> LA Schedule
- IPP> Lasers/Optics/Optical Tables - Save!
- IPP> Last Call for the IPP Rationale document
- IPP> Last Call: Augmented BNF for Syntax Specifications: ABNF to
- IPP> Last Call: Internet Printing Protocol/1.0: Protocol
- IPP> Last Reminder: September Meeting in Atlanta
- IPP> Let Us Do It For You!
- IPP> Lost print Jobs
- IPP> LPD (RFC1179) <-> IPP gateway
- IPP> LPD Extensions posted (from X/Open(TM) PSIS Appendix D)
- IPP> Majordomo Filtering of PWG Mailing lists
- IPP> Making [which-]document-format MANDATORY for
- IPP> May 21st Conference Call
- IPP> May 28th Conference Call
- IPP> May 7, 1997 IPP Conference Call
- IPP> May Meeting in San Diego
- IPP> Meeting Charges for San Diego
- IPP> Meeting Location
- IPP> Meeting Minutes and Presentations from the IPP WG meeting in DC
- IPP> Meeting Times
- IPP> Microsoft Presentation
- IPP> Microsoft Presentation -Reply
- IPP> Microsoft proposal
- IPP> Microsoft's XML pages
- IPP> Microsoft/HP press release on SWP
- IPP> MIME multipart/* vs HTTP
- IPP> MIME-types and alignment
- IPP> Minutes
- IPP> Minutes for 01/15/97 Conference Call
- IPP> Minutes from April 16 Phone Call
- IPP> Minutes from IPP teleconference 2/19/97
- IPP> Minutes from the IPP Working Group Meeting held at IETF38
- IPP> Minutes of IPP Weekly Conference call - Nove. 12, 1997
- IPP> misleading press release issued by IPP WG
- IPP> MOD - new model document 971107
- IPP> MOD -- xxx-supported attributes
- IPP> MOD optional attributes for more info and driver
- IPP> MOD optional attributes for more info and driver installer
- IPP> MOD optional attributes for more info and driver,
- IPP> MOD optional attributes for more info and driver,,
- IPP> MOD & JMP - Adding why to join ipp and jmp DLs
- IPP> MOD & PRO - Security terminology
- IPP> MOD - "compression" should not be a Job Description attribute
- IPP> MOD - "job-state-reason" clarifications, additions and
- IPP> MOD - "orientation" enum should have values 3, 4, 5, not 1, 2,
- IPP> MOD - 'canceled' and 'aborted' job state semantics
- IPP> MOD - 1/21 Minutes
- IPP> MOD - 1/21 telecon
- IPP> MOD - 1/24 telecon
- IPP> MOD - 14/18 discussion minutes
- IPP> MOD - 2/14 minutes
- IPP> MOD - 2/14 Telecon
- IPP> MOD - 2/19 Model Issues list
- IPP> MOD - 2/21 Minutes
- IPP> MOD - 2/21 Teleconference
- IPP> MOD - 2/24 Telecon
- IPP> MOD - 3/14 Telecon info
- IPP> MOD - 3/21 call
- IPP> MOD - 3/21 call [and request attributes by file-typ
- IPP> MOD - 3/21 call [and request attributes by file-type]
- IPP> MOD - 3/3 meeting minutes
- IPP> MOD - 3/3 minutes TEXT
- IPP> MOD - 3/3 Telecon
- IPP> MOD - 3/6 Telecon
- IPP> MOD - 4/18 conf call
- IPP> MOD - 5/14 agenda
- IPP> MOD - 5/14 mintues
- IPP> MOD - 5/2 call mintues
- IPP> MOD - 5/9 call phone number
- IPP> MOD - 6/6 Telecon
- IPP> MOD - 6/6 telecon minutes
- IPP> MOD - A reference to number-up '0' needs to be removed
- IPP> MOD - ABNF is RFC 2234
- IPP> MOD - ACTION ITEM: Change color-supported from Boolean to
- IPP> MOD - Action Items Steve, Peter, Harry, Tom
- IPP> MOD - Agreed changes for internationalization
- IPP> MOD - Agreed changes to IPP/JMP "job-state" and
- IPP> MOD - Algorithm in section 15.3 Attribute Processing
- IPP> MOD - Allow more JT attributes to be document attributes
- IPP> MOD - Appendix comparing IPP to JMP
- IPP> MOD - Attribute documents
- IPP> MOD - Automated IPP Printer Installation
- IPP> MOD - Base printer implementation requirements
- IPP> MOD - blind rev of the model documet
- IPP> MOD - CHANGE!! 5/2 telecon
- IPP> MOD - client scenarios with security
- IPP> MOD - Closure on status codes
- IPP> MOD - Comment on handling version numbers
- IPP> MOD - Comment on RFC 2044: need to specify the ISO 10646
- IPP> MOD - Comments from Patrick Powell
- IPP> MOD - Comments on Internationalization
- IPP> MOD - Comments on Internationalization (RESEND)
- IPP> MOD - Comments on IPP Model V1.1, printer-state attribute
- IPP> MOD - Comments on Model V1.1, dated 2/3/97
- IPP> MOD - COMMENTS ON PRINTER-STATE AND PRINTER-STATE-REASONS
- IPP> MOD - Comments on printer-state, printer-state-reasons viz a
- IPP> MOD - Comments on printer-state, printer-state-reasons viz aviz Printer
- IPP> MOD - Comments on the New Attributes Table
- IPP> MOD - Comments on version 1.3 of Model and Semantics spec
- IPP> MOD - Complete Issues List for Wed meeting - from Carl-Uno and
- IPP> MOD - Concerns about "fan-in"
- IPP> MOD - Concerns about "fan-in" -Reply
- IPP> MOD - Concise table of valid attributes and associated values available?
- IPP> MOD - Contradictions on client MUST/SHOULD support TLS
- IPP> MOD - Definition for 'reverse-portrait' enum value
- IPP> MOD - DESCRIPTION OF ADDITIONAL TEXT FORMATTING ATTRIBUTES
- IPP> MOD - Directions for IPP Model Meeting on Wed afternoon 2/5 at Sun
- IPP> MOD - document format question
- IPP> MOD - document-format-supported using MIME types and
- IPP> MOD - document-format-supported using MIME types and 'a
- IPP> MOD - draft of text on document processing
- IPP> MOD - draft of text on document processing (again)
- IPP> MOD - Edit to be made to 1.5: Print return job-status
- IPP> MOD - Editorial comments on Model
- IPP> MOD - Exactly what is a reasonable subset?
- IPP> MOD - Fix Section 2.4 Object Identify with multiple
- IPP> MOD - Fix Section 2.4 Object Identify with multiple Printer
- IPP> MOD - Formatting problem with note on unknown/unsupported
- IPP> MOD - Further Simplification of Internationalization - from
- IPP> MOD - Future change: early binding of defaults: more
- IPP> MOD - FYI: RESEND: PWG Standard Job Monitoring MIB, V1, posted
- IPP> MOD - I've posted some issues: isstnh03.doc .pdf
- IPP> MOD - I've posted some issues: isstnh03.doc .pdf-Re
- IPP> MOD - I've posted some issues: isstnh03.doc .pdf-Reply
- IPP> MOD - I-D ACTION:draft-ietf-drums-msg-fmt-01.txt
- IPP> MOD - I-D ACTION:draft-ietf-ipp-protocol-01.txt
- IPP> MOD - ID submitted to IETF and ver 2.0 model doc posted
- IPP> MOD - Incompatible attribute specs: To Print or Not
- IPP> MOD - Incompatible attribute specs: To Print or Not To Print?
- IPP> MOD - IPP clients SHOULD implement TLS
- IPP> MOD - IPP Model telecon minutes from 4/25/97
- IPP> MOD - IPP Versioning
- IPP> MOD - Is "best-effort" a new printing system feature?
- IPP> MOD - ISSUE - IPP Architecture
- IPP> MOD - ISSUE - Revised discussion paper on Architecture
- IPP> MOD - ISSUE: "document-format" data type: keyword vs name?
- IPP> MOD - ISSUE: # of octets of 'text'/'name' SHALL a
- IPP> MOD - ISSUE: # of octets of 'text'/'name' SHALL a Printer
- IPP> MOD - ISSUE: # of octets of 'text'/'name' SHALL a Printer support?
- IPP> MOD - ISSUE: 'canceled' and 'aborted' job state semantics
- IPP> MOD - ISSUE: Add back simple job-print-after with just
- IPP> MOD - ISSUE: ambiguity "printer-description" group v.attribute
- IPP> MOD - ISSUE: How to determine the document-uri schemes
- IPP> MOD - ISSUE: Make "page-range" multi-valued
- IPP> MOD - ISSUE: Send-Document MUST be supported if Create-Job is,
- IPP> MOD - ISSUE: SHOULD vs SHALL on document-format supplied by
- IPP> MOD - Issues
- IPP> MOD - ISSUES in 09/03 Model document
- IPP> MOD - Issues with the Model V1.2 (and V1.3)
- IPP> MOD - ISSUES: Contents of "document-format" attribute
- IPP> MOD - ISSUES: Contents of "document-format" attribute = MIME
- IPP> MOD - Job Monitoring MIB V0.86 posted and sent as an I-D
- IPP> MOD - Job Status- more fuel on the fire...
- IPP> MOD - Lets use integer pairs in the "printer-resolution"
- IPP> MOD - Mandatory attributes
- IPP> MOD - meeting location at Sun
- IPP> MOD - Meeting notes and action items from 1/9/97
- IPP> MOD - MIME Parameter Charset/Language is RFC 2231
- IPP> MOD - Minutes from Meeting at Sun on February 5
- IPP> MOD - Minutes from Meeting at Sun on February 5 -
- IPP> MOD - MOD Meeting in San Diego May 14)
- IPP> MOD - MOD Meeting in San Diego May 14
- IPP> MOD - MOD Meeting in San Diego May 14)
- IPP> MOD - Model 1.4 pdf and pdr files posted
- IPP> MOD - Model 2/24/97 telecon minutes posted
- IPP> MOD - Model group telecon
- IPP> MOD - Model group telecon -Reply
- IPP> MOD - Model Issues .pdf file posted
- IPP> MOD - model issues list posted
- IPP> MOD - Model Minutes from 2/21/97 is 0 bytes long!
- IPP> MOD - multiple document each with a different PDL
- IPP> MOD - My Last Call Model Comments
- IPP> MOD - Names of printer states
- IPP> MOD - New 1.7 version
- IPP> MOD - New 1.8 version
- IPP> MOD - new 2.1 model doc
- IPP> MOD - new 970116 model document
- IPP> MOD - new 970623 model document and Internet-Draft
- IPP> MOD - new 971219 model document posted
- IPP> MOD - new 980109 model document
- IPP> MOD - new attribute table
- IPP> MOD - New Attributes Table
- IPP> MOD - New enum data type and attributes text
- IPP> MOD - New model doc: draft-ietf-ipp-model-01.txt
- IPP> MOD - new model document
- IPP> MOD - new model document (QUESTION on Job
- IPP> MOD - new model document (QUESTION on Job Template
- IPP> MOD - New model document 1.6
- IPP> MOD - new model document posted
- IPP> MOD - new model document version 1.3.1
- IPP> MOD - New Model Issues list
- IPP> MOD - new posting fixes
- IPP> MOD - New Reference
- IPP> MOD - new text version of model document
- IPP> MOD - new version 1.2
- IPP> MOD - New version will soon come
- IPP> MOD - new_MOD clean up
- IPP> MOD - Next conference call
- IPP> MOD - oops on new section 5.3.2
- IPP> MOD - Outside the box resolution for the two URIs
- IPP> MOD - Outside the box resolution for the two URIs issue
- IPP> MOD - Paper size
- IPP> MOD - Patrick Powell's model comments
- IPP> MOD - Please review Appendix E: Processing IPP Attributes
- IPP> MOD - Printer resolutions
- IPP> MOD - Printer URI names
- IPP> MOD - Problem with job ID and containing printer URI
- IPP> MOD - Processing algorithm - from Bob, Scott, Roger, and Tom
- IPP> MOD - Properties of IPP attributes [mainly Operational
- IPP> MOD - Proposal for natural language and charset
- IPP> MOD - Proposal for status code keywords in the Model document
- IPP> MOD - Proposal to remove ValidateJob in IPP 1.0
- IPP> MOD - Proposed application/ipp registration text
- IPP> MOD - proposed text for 3.1.5 Versions
- IPP> MOD - Proposed text for IPP Security Application Profile for
- IPP> MOD - Push back on simplifying Print operation
- IPP> MOD - Push back on simplifying Print operation response
- IPP> MOD - Push back on simplifying Print operation resp
- IPP> MOD - Push back on simplifying Print operation response
- IPP> MOD - Pushback on removing job-hold-until/job-print-after and
- IPP> MOD - Questions on IPP Model and Protocol Document
- IPP> MOD - Randy's proposal in ASCII
- IPP> MOD - Rationale for why we dropped "document-charset" attribute
- IPP> MOD - Re. HTML and IPP streams
- IPP> MOD - Re. Paper size
- IPP> MOD - Re. Standard API required???
- IPP> MOD - RE: Base printer implementation requirements
- IPP> MOD - RE: Status codes
- IPP> MOD - RE: The Universal Print Driver
- IPP> MOD - Reference errors in section 15.5
- IPP> MOD - Reminder about I18N
- IPP> MOD - Remove last 4 attr from Job Template table
- IPP> MOD - RESEND: Suggested simplified IANA Considerations
- IPP> MOD - RESEND: proposed "document-formats-detected" attribute
- IPP> MOD - Review of MOD attributes
- IPP> MOD - Revised 'application/ipp' MIME type
- IPP> MOD - RSVP for IPP Model Meeting on Wed afternoon 2/5 at Sun
- IPP> MOD - RTF version of the 970903 model doc
- IPP> MOD - Send-URI "document-uri" and "last-document"
- IPP> MOD - Separate 'document-format' and 'document-language'
- IPP> MOD - simplified legal state transition diagram
- IPP> MOD - Some comments on content
- IPP> MOD - Status codes
- IPP> MOD - Status Codes for IPP
- IPP> MOD - Suggested replacement text on notifications
- IPP> MOD - Suggested Requirements for XML to encode IPP
- IPP> MOD - Suggested simplification of IANA Considerations
- IPP> MOD - Suggestion: add RequiredResources call to
- IPP> MOD - Suggestion: add RequiredResources call to Windows GDI
- IPP> MOD - Suggestion: add RequiredResources call to Windows GDI to help drivers emit I
- IPP> MOD - Suggestion: add RequiredResources call to Windows GDI to
- IPP> MOD - Suggestion: add RequiredResources call...
- IPP> MOD - Supported URIs for print-by-reference
- IPP> MOD - Syntax of 'document-format' proposal
- IPP> MOD - term "enum" is problematic
- IPP> MOD - Terminology: "Internet media type" vs. "MIME-type"
- IPP> MOD - text for "number-of-documents" Job Description attribute
- IPP> MOD - text version of new mod document posted
- IPP> MOD - The Get-Jobs operation and
- IPP> MOD - The Get-Jobs operation and completed/canceled/aborted
- IPP> MOD - The Universal Print Driver
- IPP> MOD - towards conformance/simplification
- IPP> MOD - Two documents downloaded
- IPP> MOD - Two documents downloaded -- additional information
- IPP> MOD - Two Get Attributes Operations
- IPP> MOD - UPDATE FOR STATUS CODE KEYWORDS IN THE
- IPP> MOD - UPDATE FOR STATUS CODE KEYWORDS IN THE MODEL
- IPP> MOD - UPDATE FOR STATUS CODE KEYWORDS IN THE MODEL DOCUMENT
- IPP> MOD - Updated 'application/ipp' MIME type - 7 Dec 1997
- IPP> MOD - Updated list of IPP attributes and tags
- IPP> MOD - Updated Model sections for internationalization
- IPP> MOD - Updated Section 15.3 from Bob, Scott, Roger,
- IPP> MOD - Updated Section 15.3 from Bob, Scott, Roger, Tom
- IPP> MOD - Updated simplified internationalization proposal
- IPP> MOD - URGENT: Ok to call 2nd printer uri:
- IPP> MOD - URGENT: Ok to call 2nd printer uri: "printer-map
- IPP> MOD - URGENT: Ok to call 2nd printer uri: "printer-map-uri"?
- IPP> MOD - Use of "enums"
- IPP> MOD - V1.0 - 1.6 say attributes can be added
- IPP> MOD - V1.0 - 1.6 say attributes can be added -Reply
- IPP> MOD - verbiage for info and driver attributes
- IPP> MOD -- xxx-supported attributes
- IPP> MOD 4/18 telecon
- IPP> MOD JobState suggestion
- IPP> MOD more editorial comments
- IPP> MOD New Text for Get-Printer-Attributes
- IPP> MOD pdl-override inconsistency
- IPP> MOD/PRO - ISSUE Do we need to represent "unknown" value or not?
- IPP> MOD/PRO - ISSUE: Model and Protocol disagree on
- IPP> MOD/PRO - Proposal to add 'dictionary' attribute
- IPP> MOD/PRO - Proposal to add 'dictionary' attribute syntax
- IPP> MOD/PRO - What are MIME types for IPP document-format
- IPP> MOD/PRO Should mediaType be mimeType in the Protocol
- IPP> MOD/PRO Should mediaType be mimeType in the Protocol spec?
- IPP> MOD: new table posted
- IPP> MOD: Proposal to improve job submission in IPP 1.0
- IPP> MOD> A New View of Notification Requirements
- IPP> Model 1.5 posted
- IPP> More about your objections to the PWG Press Release
- IPP> more on IPP and OMG PF coordination.
- IPP> More requirements
- IPP> More Time for IPP in January
- IPP> More Time for IPP in January [agenda: IPP
- IPP> Move "orientation-requested" from J.T. to Operation
- IPP> Move "orientation-requested" from J.T. to Operation attribute
- IPP> Munich PING
- IPP> My comments on IPP Model draft of 3 Sept
- IPP> Nahsua Meeting Minutes
- IPP> Need a new "whip" for the Scenarios subgroup
- IPP> Netscape participation
- IPP> New BOF presentation
- IPP> New Document Alliance
- IPP> New Document Alliance -Reply
- IPP> New document available (PS)
- IPP> New draft
- IPP> New draft available
- IPP> New HTTP Methods vs POST
- IPP> New HTTP Methods vs POST -Reply
- IPP> New Internet draft
- IPP> New IPP docs uploaded
- IPP> new model and protocol slides for briefing
- IPP> New protocol doc available
- IPP> New protocol document & Security issues
- IPP> New protocol document (PDF) available
- IPP> New protocol document available
- IPP> New protocol document?
- IPP> New PWG Mailing Lists & Outage
- IPP> New Requirements document
- IPP> New Security draft
- IPP> New srvloc printer schema draft
- IPP> Next IPP conference call
- IPP> non uu DTD
- IPP> non uu XML scheme
- IPP> Not on mailing list
- IPP> Notification Requirements
- IPP> Notifications
- IPP> NT 5.0 beta Print Server
- IPP> October Meeting
- IPP> October Meeting in Denver
- IPP> October PING
- IPP> October PING list
- IPP> October PWG Meeting Details
- IPP> OK to send e-mail?
- IPP> on the use of SSL3 framing and SASL
- IPP> Option Negotiations
- IPP> Output Bin Select
- IPP> Paul Moore from Microsoft will join us
- IPP> PC WEEK: IETF charters group for Web-based printing standard
- IPP> PEP now an ID
- IPP> Phone # for protocol teleconference
- IPP> Ping for Albuquerque
- IPP> PING for IPP BOF in San Jose
- IPP> PING for Los Angeles Meeting December 1-5
- IPP> Please RSVP to the June Meetings if you have not already done so
- IPP> Please send your email address for Scenarios subgroup participation
- IPP> PMP> MIME-types and alignment
- IPP> Pointer to new IETF MIME document
- IPP> Pointer to penultimate draft of IPP Security document
- IPP> Poll for interest for a new "Universal Print Driver" (UPD) discussion list
- IPP> Possible scenarios that reflect discussion of 2/7/97
- IPP> Preliminary Apps area report for Munich
- IPP> Presentation
- IPP> Press Release - Final
- IPP> Press Release - Quote
- IPP> Printer Instance Creation/Installation
- IPP> Printer Instance Creation/Installation - hassle
- IPP> printer-resolution standard values retrograded
- IPP> Printers and Spooling Systems
- IPP> PRO & MOD - Need to synchronize thought on operations
- IPP> PRO - A value-type field for the Protocol Spec
- IPP> PRO - A value-type field for the Protocol Spec proposa
- IPP> PRO - A value-type field for the Protocol Spec proposal
- IPP> PRO - About using HTTP 1.1
- IPP> PRO - Binary vs. ASCII
- IPP> PRO - Change to the JmPrinterResolutionTC
- IPP> PRO - Comment on latest encoding proposal
- IPP> PRO - Comments on IPP Level 1 (formerly SWP) document
- IPP> PRO - How much IPP request validation can an XML parser do?
- IPP> PRO - I-D ACTION:draft-ietf-drums-abnf-03.txt
- IPP> PRO - My last call comments on the Protocol document
- IPP> PRO - Need some value-tags reserved for private extensions
- IPP> PRO - Notifications
- IPP> PRO - PWG Phone Conference TOMORROW
- IPP> PRO - Re Protocol Meeting Friday March 7
- IPP> PRO - Re. RFC 1730 as a basis !
- IPP> PRO - Re. Protocol Specification Language
- IPP> PRO - Registering MIME types for the Printer MIB PDL types
- IPP> PRO - Resolving the issue of adding data type tags
- IPP> PRO - Resolving the issue of adding data type tags in the encoding
- IPP> PRO - Security Considerations
- IPP> PRO - Suggested text for form-data
- IPP> PRO - Suggested text for form-data (more questions)
- IPP> PRO - Support for UTF16
- IPP> PRO - Thoughts around use of XML
- IPP> PRO - Transaction protocol anyone?
- IPP> PRO - txt and pdf versions of the 970702 document
- IPP> PRO - Updated "Mapping between LPD and IPP Protocols"
- IPP> PRO - Updated requirements for XML encoding of IPP
- IPP> PRO - Use of special port for IPP
- IPP> PRO - Using a new scheme for IPP protocol handling
- IPP> PRO --> Protocol Extension Protocol
- IPP> PRO and MOD - UPDATE ON STATUS CODE KEYWORDS IN THE MODEL
- IPP> PRO interoperability clarification request from TES
- IPP> PRO latest protocol document - .pdf files stored
- IPP> PRO proposed tweak to protocol
- IPP> PRO Section 9.4 - Error in Print-URI Example
- IPP> PRO,MOD> User model for clients
- IPP> PRO: Paul Moore's Presentation
- IPP> PRO> Editorial Correction
- IPP> PRO> Question from Mr. Danknick of Canon
- IPP> Problem with issues.PDF is that the file extension is .PDF, while URL is .pdf
- IPP> Processing Algorithm
- IPP> Proposal for IPP to meet IESG Language/CharSet requirements
- IPP> Proposed Agenda for next week's IPP meeting
- IPP> Proposed Agenda for the IPP meeting in San
- IPP> Proposed Agenda for the IPP meeting in San Diego on May 15
- IPP> Proposed jobmon MIB note for impressions (that count blank
- IPP> Proposed Summary of IPP Feature Set
- IPP> Proposed Summary of IPP Feature Set -Reply
- IPP> Prosed Agenda for IPP Telephone Conference on December
- IPP> Prosed Agenda for IPP Telephone Conference on December 18
- IPP> Protocol Definition
- IPP> Protocol encoding addition...
- IPP> Protocol minutes - 6/9/97
- IPP> Protocol Specification Language
- IPP> Protocol Specification Language -Reply
- IPP> Public relations...
- IPP> PWG conference
- IPP> PWG May Meeting Minutes
- IPP> PWG Meeting Agenda - Final
- IPP> PWG meeting in Austin on 3/2-6
- IPP> PWG Server Available
- IPP> PWG Server back on-line
- IPP> PWG server back online
- IPP> PWG> 1998 Meeting Plan
- IPP> PWG> Meeting Charges
- IPP> PWG> Meeting Notice: January Joint PWG/PWG-C Meeting
- IPP> PWG> Seattle PING
- IPP> PWG>IPP - Customer involvement
- IPP> PWG>IPP - Directory
- IPP> Question about April IPP meeting
- IPP> Question about rangeOfInteger
- IPP> Question on directory schema attributes
- IPP> Question on directory schema attributes -Reply
- IPP> Questions on IPP Model and Protocol
- IPP> Random thougts on naming and Job-templates
- IPP> Rational for IPP Arch or "Why We Shot ourselves in
- IPP> Rational for IPP Arch or "Why We Shot ourselves in the foot"
- IPP> RE: "Asynchronous Notification"
- IPP> RE: ADM - FAQ Text
- IPP> RE: Bob Herriot's IPP/JMP 2 new states proposal
- IPP> RE: Does the world need a robust host-to-device network prin
- IPP> RE: draft-isaacson-ipp-info-00.txt
- IPP> RE: JMP> Final IPP/JMP job-state and job-state-reasons
- IPP> RE: JMP> HELD vs NEEDS-ATTENTION
- IPP> RE: JMP> MOD - simplified legal state transition diagram
- IPP> RE: MIME multipart/* vs HTTP
- IPP> RE: MOD - Printer resolutions
- IPP> RE: MOD - Push back on simplifying Print operation response
- IPP> RE: Move "orientation-requested" from J.T. to Operation attribute group?
- IPP> RE: Multiple documents per job
- IPP> RE: Print by Reference
- IPP> RE: Printer Instance Creation/Installation
- IPP> RE: Printer Instance Creation/Installation -Reply
- IPP> RE: Protocol Definition
- IPP> RE: PWG> Getting the $101 rate at the Hyatt hotel for the PWG meeting
- IPP> RE: PWG> PWG meeting in Austin on 3/2-6
- IPP> RE: Random thougts on naming and Job-templates
- IPP> RE: Should 'pending' be a mandatory state or not?
- IPP> RE: SSL3
- IPP> RE: TES:binary files
- IPP> RE: TES> Outbound binary request bug in NetScape Proxy V2
- IPP> RE^2: Some Comments on ipp92.doc - the issues we didn't get to address [replies to Bob Herriot
- IPP> RE^4: IPP over TCP
- IPP> redirection
- IPP> Relationship to MIME and HTTP
- IPP> REMINDER: Copyright notice requirement for standards track RFCs
- IPP> REMINDER: Forthcoming PWG Server Outage (12/15 12/16)
- IPP> REMINDER: IPP Conference Call - TODAY, December 18th
- IPP> Report from BOF Session on IPP, December 12
- IPP> REQ document comments
- IPP> REQ Issues and directory cleanup
- IPP> REQ - A call for issues
- IPP> REQ - another way of doing things
- IPP> REQ - Comments
- IPP> REQ - Comments/issues on Feb 17 (01a) Requirements
- IPP> REQ - Comments/issues on Feb 17 (01a) Requirements docu
- IPP> REQ - Comments/issues on Feb 17 (01a) Requirements document
- IPP> REQ - Final Editorial round for the Requirements document
- IPP> REQ - Firewalls
- IPP> REQ - ISSUE - Add a requirement that printing files
- IPP> REQ - ISSUE - Add a requirement that printing files have
- IPP> REQ - ISSUE - Add a requirement that printing files have same
- IPP> REQ - Issues with the 2/17 Requirements Scenarios
- IPP> REQ - Last minute scenario comments
- IPP> REQ - My comments on Scenarios posted
- IPP> REQ - New deadline for comments
- IPP> REQ - Requirements Document Issues
- IPP> REQ - Requirements Match?
- IPP> REQ - Requirements Scenarios
- IPP> REQ - response to Bob Herriot's Comments
- IPP> REQ - scenario issues
- IPP> REQ - Scenario when printer jams and job flushes
- IPP> REQ - Scenarios group telecon
- IPP> REQ - Scenarios group telecon info
- IPP> REQ - unable to read issues.pdf and closed.pdf with 2.1
- IPP> REQ - yet another way of doing things
- IPP> REQ Driver download in/out of IPP
- IPP> REQ Driver download in/out of IPP -Reply
- IPP> REQ Issues list for teleconference
- IPP> REQ updated issues and closed items
- IPP> REQ, PRO, MOD - SNMP relation to IPP
- IPP> REQ: New Requirements Document
- IPP> REQ: Updated issues list and closed issues
- IPP> REQ:IPP -> Scenarios
- IPP> REQ:IPP-> telecon
- IPP> REQ> Conference Call to Review REQ Document
- IPP> REQ> Document Available
- IPP> Requirement Document
- IPP> Requirement paper now up on the IETF Web
- IPP> Requirements Draft
- IPP> Requirements presentation
- IPP> Requirements Scenarios
- IPP> RESEND: Austin - Ping (from Don Wright <don@lexmark.com>)i
- IPP> RESEND: How should a PDF document be indicated in the Printer
- IPP> RESEND: MOD - Resolving IPP/JMP job-state and
- IPP> Resolutions
- IPP> Resolving IPP/JMP job-state and job-state-reasons
- IPP> Resolving IPP/JMP job-state and job-state-reasons differences:
- IPP> Restaurant details for Tuesday, Dec 10 at 6pm
- IPP> RETRY: list mandatory vs optional operations 19970626
- IPP> Review of Model Document - unsupported job template
- IPP> Review of Model Document - unsupported job template attribut
- IPP> Revised Agenda for IPP WG
- IPP> Revised Charter Text for IPP
- IPP> Revised FAQ now available
- IPP> Revision of section 4.2.6 multiple-document-handling
- IPP> RFC 2119, March 1997 has conformance language spec
- IPP> RFC 2184 language tags for parameter values
- IPP> rooms in San Jose
- IPP> Roster from San Jose
- IPP> Roster from yesterday's IETF meeting
- IPP> Scope of Scenarios
- IPP> Scott's Presentation for the BOF
- IPP> Scott's Presentation for the BOF -Reply
- IPP> Seattle PING
- IPP> SEC
- IPP> SEC & MOD - Get-Attributes operation
- IPP> SEC - a few new slides
- IPP> SEC - Access Control: What's On The Wire
- IPP> SEC - ComputerWorld Article
- IPP> SEC - Draft document prereading for IPP Security phone conference
- IPP> SEC - Example of security specification
- IPP> SEC - GSS-API - RFC 2078
- IPP> SEC - IPP and firewalls
- IPP> SEC - IPP Security Requirements
- IPP> SEC - Minutes and Presentation from 970207 now in PWG server
- IPP> SEC - Minutes from phone conference 970220
- IPP> SEC - Minutes from SEC meeting in El Segundo, February 7
- IPP> SEC - Minutes from telephone conference 970213
- IPP> SEC - New RFC on HTTP Security
- IPP> SEC - No phone conference this week
- IPP> SEC - Phone conference 970220
- IPP> SEC - Phone Conference 970313
- IPP> SEC - Phone conference on 970214
- IPP> SEC - Phone conference on 970306
- IPP> SEC - Phone Conference on Thursday April 24, 1 - 3 PST
- IPP> SEC - Possible Security Solotions for IPP
- IPP> SEC - Protocol names for security protocols
- IPP> SEC - PWG phone conference - May 22, 1 - 2:30 pm
- IPP> SEC - PWG Phone Conference - May 22, 1997
- IPP> SEC - PWG Phone Conference on IPP Security - June 12, 1 - 3 PST
- IPP> SEC - PWG Phone Conference on IPP Security - June 5
- IPP> SEC - PWG Phone Conference on IPP Security - May 29, 1 - 3 pm
- IPP> SEC - PWG Phone Conference on IPP Security - May 8
- IPP> SEC - PWG Phone Conference September 11
- IPP> SEC - PWG Phone Conference September 11 NEW TIME
- IPP> SEC - Revised document on security services
- IPP> SEC - SASL is about to happen
- IPP> SEC - SASL will soon go to IETF Wide (4 week) Last Call (fwd)
- IPP> SEC - Security subgroup meeting on February 7
- IPP> SEC - Security texts on FTP server
- IPP> SEC - SET/SSL Information
- IPP> SEC - Some input for today's phone conference
- IPP> SEC - Some more editing comments on Security draft
- IPP> SEC - Telephone conference 970213
- IPP> SEC - Updated document
- IPP> SEC - Weekly phone conference 970227
- IPP> SEC - yet another security protocol
- IPP> SEC, REQ, MOD - Internet-Draft on IPP Security
- IPP> SEC: DIR: Re. Security attribute(s) required in Directory
- IPP> SEC: DIR: Security attribute(s) required in Directory S
- IPP> SEC: DIR: Security attribute(s) required in Directory Schema
- IPP> Security - Issues with the existing proposals
- IPP> Security proposal
- IPP> Security text for IPP protocol doc (PROPOSED)
- IPP> seeking volunteer
- IPP> Sending html in e-mail
- IPP> Separate IPPDEV list will cease to exist as of tomorrow
- IPP> Separating the IPP protocol from the transport mechanism
- IPP> Separation of PWG and IETF activities
- IPP> Seperating the IPP protocol from the transport
- IPP> Seperating the IPP protocol from the transport mechanism.
- IPP> September Meeting in Atlanta
- IPP> September Meeting Minutes
- IPP> September Minutes)
- IPP> Short report from IPP sessions in IETF-39
- IPP> Some clarifications about RFC1179 (LPR/LPD) being a "spec"
- IPP> Some notes from an IETF Area Director
- IPP> Some notification reqmts?
- IPP> Some observations from the IPP BOF in the IETF
- IPP> Special Conference Call
- IPP> Standards Quandary: Speed Vs. Science
- IPP> Status of TLS spec.
- IPP> steering by the rear-view mirror
- IPP> Submission vs. Monitoring and Management
- IPP> submitted "draft-lutz-print-types-01.txt" as internet draft
- IPP> Suggestion for timed delay error code.
- IPP> Summary for the IETF IPP WG Meeting
- IPP> Summary of IPP WG Meeting at Washington DC IETF
- IPP> Supported URIs for print-by-reference
- IPP> Teleconference Times and Dates
- IPP> Templates
- IPP> Templates -Reply
- IPP> Templates Issues
- IPP> TES
- IPP> TES Trace files uploaded
- IPP> TES - Info about IPP prototype from IBM
- IPP> TES - January meeting
- IPP> TES - sharing binary IPP trace files
- IPP> TES How are we going to do this?
- IPP> TES Meeting Agenda(Proposed)
- IPP> TES Meeting Minutes
- IPP> TES meeting PING
- IPP> TES Phone conference agenda
- IPP> TES Phone conference info
- IPP> TES Some first steps
- IPP> TES: binary files
- IPP> TES: Who is planning on prototyping IPP?
- IPP> TES: IBM Client Prototye
- IPP> TES: IPP Prototyping and Demonstrations
- IPP> TES: prototype ping results
- IPP> TES: Who is planning on a prototype?
- IPP> TES> Outbound binary request bug in NetScape Proxy V2
- IPP> TES> Prototype Status
- IPP> TES>Anyone want to try an internet test with my IPP server and cl
- IPP> text version of the model document
- IPP> Thanks Carl.
- IPP> Three types of notification.
- IPP> Thursday evening: Discussion/tutorial on char sets
- IPP> Thursday evening: Discussion/tutorial on char sets and
- IPP> tiff-f format & ipp1
- IPP> Tips for making plain text files for IETF from WORD .doc files
- IPP> TLS security section of protocol document
- IPP> transaction-based HTTP
- IPP> Tweak to protocol - your note
- IPP> Updated IPP job-state/job-state-reasons & JMP
- IPP> Updated IPP state transition diagram
- IPP> Updated version of Requirements Scenarios
- IPP> URGENT - New Time and Number for Today's Phone Conference
- IPP> URGENT - PLEASE CALL IN THURSDAY
- IPP> URGENT: JMP/IPP job-state/job-state-reasons: 1:00-1:15 PDT
- IPP> URGENT: Should impressions include blank last page back sides
- IPP> URI scheme and port numbers for TLS
- IPP> Use of "-" for range in ABNF: confusion with "-" in rule names?
- IPP> Use of HTML forms
- IPP> Use of SSL3 Framing
- IPP> Use of SSL3 Framing????
- IPP> Using MIME types instead of enumerations for document formats
- IPP> vacation
- IPP> Validate-Job for print by reference
- IPP> Vote
- IPP> Vote on IESG last call submission
- IPP> voting on submission
- IPP> We need to improve our publication announcements
- IPP> Wed 1/15 Telecon
- IPP> Wednesday's Conference Call
- IPP> Wednesday/Thursday agenda
- IPP> What ever happened to IEEE 1284.1 (aka TIPSI, aka NPAP)?
- IPP> What is it we really need?
- IPP> Who gets to hijack ?
- IPP> Who or What will use IPP notification?
- IPP> Why HTTP and thoughts on forms etc
- IPP> Why HTTP and thoughts on forms etc -Reply
- IPP> Would you please delete my name from the mailing list?
- IPP> Xerox Comments on IPP Security White Paper
- IPP> XML 1.0: W3C Recommendation; XML Activity Update
- IPP> XML DTD and schema example
- IPP> XML et al
- IPP> xml etc.
- IPP> Your IPP article
- IPP>ADM
- IPP>ADM Agenda for March 19 meeting
- IPP>ADM Agenda for March 19 meeting (Resend)
- IPP>ADM changes to ABNF notation -- editors: please note
- IPP>ADM Munich IETF meeting
- IPP>Apparent conflicts clarification
- IPP>Comments on Operations Attributes
- IPP>DIR - comments on directory document
- IPP>DIR - comments on security document
- IPP>DIR - Compiled list of directory schema issues; Comments
- IPP>DIR - New Internet drafts
- IPP>DIR OID and string attribute
- IPP>IPP Last Call - need advance list of issues
- IPP>MOD
- IPP>MOD Ambiguity in what groups should be in an
- IPP>MOD Ambiguity in what groups should be in an operation
- IPP>MOD (with missing text) Issue with Conditionally Mandatory
- IPP>MOD - 5/2 call
- IPP>MOD - adornments to specify display strings
- IPP>MOD - Attribute conformance
- IPP>MOD - attribute description in Model document
- IPP>MOD - best effort
- IPP>MOD - coding mechanism for parameters
- IPP>MOD - color job attribute
- IPP>MOD - comments on latest model document
- IPP>MOD - comments on latest model document -Reply
- IPP>MOD - COMMENTS ON UPDATED DIAGRAM
- IPP>MOD - Comments on version 1.6, attributes
- IPP>MOD - Conformance
- IPP>MOD - Conformance -Reply
- IPP>MOD - conformance [for Friday's 4/18 telecon]
- IPP>MOD - editorial comment
- IPP>MOD - fax
- IPP>MOD - Globally unique IDs
- IPP>MOD - HTML and IPP streams
- IPP>MOD - HTML and IPP streams -Reply
- IPP>MOD - IPP comments!
- IPP>MOD - Jay's comment on complexity
- IPP>MOD - job attributes for public printers
- IPP>MOD - Job Identifier
- IPP>MOD - Job status on Send Document
- IPP>MOD - job-sheet-content attribute
- IPP>MOD - Job-URI vs. JOb-ID
- IPP>MOD - Latest model document - internationalization
- IPP>MOD - Mandatory job description attributes
- IPP>MOD - minor corrections
- IPP>MOD - minor corrections <RESEND>
- IPP>MOD - missing job template attributes
- IPP>MOD - Model diagram
- IPP>MOD - more comments on v1.6
- IPP>MOD - Multiple documents per job
- IPP>MOD - Must charset and natural-language always be
- IPP>MOD - Must charset and natural-language always be sent?
- IPP>MOD - Must charset and natural-language always besent?
- IPP>MOD - Names of printer states
- IPP>MOD - Names of printer states -Reply
- IPP>MOD - new attributes
- IPP>MOD - Phone Number?
- IPP>MOD - Print by reference
- IPP>MOD - printe-uri-user and printer-more-info-site
- IPP>MOD - Scott's Mandatory attribute note
- IPP>MOD - SendDocument proposal
- IPP>MOD - Standard API required???
- IPP>MOD - Standard API required??? -Reply
- IPP>MOD - Suggestions for new introduction
- IPP>MOD - Too Many IPP Operations?
- IPP>MOD - Type 4 Keywords
- IPP>MOD - updated conformance paper
- IPP>MOD - updated conformance paper - defaults
- IPP>MOD - updated conformance paper -Reply
- IPP>MOD - Updated Diagram
- IPP>MOD - your comments on conformance
- IPP>MOD 26Sep97, questions and typos
- IPP>MOD Action Item from LA: fix requesting-user-name
- IPP>MOD Action Item from LA: fix requesting-user-name explana
- IPP>MOD Action Item from LA: fix requesting-user-name explanation
- IPP>MOD action item: revised text for requesting-user-name
- IPP>MOD add another issue [encoding nameWithLanguage and
- IPP>MOD add another issue [encoding of CompoundValue]
- IPP>MOD Concern about Event Notification Content
- IPP>MOD copies-supported with regard to collated.
- IPP>MOD default tag
- IPP>MOD document object problem for SendURI
- IPP>MOD Editorial Comments on Model Doc
- IPP>MOD encoding of language in string
- IPP>MOD Interesting observation
- IPP>MOD Issue with best-effort
- IPP>MOD Issue with Conditionally Mandatory
- IPP>MOD Issue with conformance
- IPP>MOD Issue with localization
- IPP>MOD job-k-octets-supported issue
- IPP>MOD just sent draft-ietf-ipp-model-4.txt to ietf
- IPP>MOD maximum lengths of some strings not explicitly stated
- IPP>MOD maximum lengths of some strings not explicitly stated in model
- IPP>MOD May 14 MOD meeting
- IPP>MOD missing attribute to map job-uri to printer-uri
- IPP>MOD more new operations?
- IPP>MOD new attributes, such as orientation
- IPP>MOD printer-uri/printer-tls-uri issues
- IPP>MOD PRO Comments on Microsofts IPP document
- IPP>MOD PRO Dictionary type
- IPP>MOD problem with MANDATORY support of operation
- IPP>MOD problem with MANDATORY support of operation attributes
- IPP>MOD reconsideration of model decision
- IPP>MOD Requirements for in channel vs out of channel
- IPP>MOD Specifiying locale for a response
- IPP>MOD Specifiying locale for a response -Reply
- IPP>MOD thoughts on proposal from Roger and Keith
- IPP>MOD What if we had both Job-Id and Job-URI for Jobs?
- IPP>MOD Why use Job-Id instead of Job-URI for Jobs?
- IPP>Output bin Select
- IPP>PRO
- IPP>PRO feedback on type byte
- IPP>PRO !!LOCATION CHANGE!! directions and agenda for June 17th meeting at Sun
- IPP>PRO - comments on latest draft
- IPP>PRO - comments on transport mapping document
- IPP>PRO - comments on your Bob's protocol proposal
- IPP>PRO - http comments
- IPP>PRO - posted white paper and foils
- IPP>PRO - Print by reference
- IPP>PRO - Protocol meeting on 3/7 at Sun
- IPP>PRO - segments and synchronous responses
- IPP>PRO - segments and synchronous responses -Reply
- IPP>PRO - things that worry me
- IPP>PRO A simple XML example for today's teleconference
- IPP>PRO Analysis of XML as IPP Protocol
- IPP>PRO Analysis of XML as IPP Protocol [.pdf file posted]
- IPP>PRO another reason for needing byterange and documen
- IPP>PRO another reason for needing byterange and document
- IPP>PRO another reason for needing byterange and document number
- IPP>PRO best-effort and the LPD gateway
- IPP>PRO change of date for face-to-face meeting
- IPP>PRO comments on CPAP
- IPP>PRO corrected protocol document
- IPP>PRO corrected protocol document [.pdf files posted]
- IPP>PRO Enclosed: Update to Randy's document
- IPP>PRO examples for proposed tweak to protocol
- IPP>PRO face-to-face meeting on June 17
- IPP>PRO future face-to-face meeting
- IPP>PRO ideas for protocol meeting agenda (please comment)
- IPP>PRO IPP>MOD new tables for types of values in the model
- IPP>PRO June 17 meeting
- IPP>PRO latest LPD document at PWG site and sent to IETF
- IPP>PRO latest protocol and lpd drafts
- IPP>PRO latest protocol and lpd drafts [plus the .pdf files]
- IPP>PRO latest protocol doc
- IPP>PRO latest protocol doc [.pdf files uploaded]
- IPP>PRO latest protocol document
- IPP>PRO latest protocol document available
- IPP>PRO latest protocol document downloaded
- IPP>PRO latest version of XML analysis
- IPP>PRO lengths versus delimiting characters
- IPP>PRO Magic Numbers in ipp-messages
- IPP>PRO minutes of 4/21/97 teleconference
- IPP>PRO minutes of 4/28 IPP protocol teleconference
- IPP>PRO Minutes of June 17th meeting
- IPP>PRO Monday 5/19 meeting (canceled)
- IPP>PRO Monday teleconference
- IPP>PRO new ietf drafts for protocol and lpd
- IPP>PRO new ietf drafts for protocol and lpd [.pdf
- IPP>PRO new protocol document
- IPP>PRO new protocol document - .pdf files downloaded too
- IPP>PRO new protocol document [.pdf files uploaded]
- IPP>PRO new protocol document available
- IPP>PRO new version of protocol doc for Wed meeting
- IPP>PRO phone number for weekly teleconference 10am-noon PDT
- IPP>PRO proposed tweak to protocol
- IPP>PRO protocol document downloaded, text and new .doc file
- IPP>PRO revised agenda
- IPP>PRO revised agenda [some additional ideas]
- IPP>PRO Teleconference
- IPP>PRO Teleconference Agenda and ideas for discussion
- IPP>PRO teleconference on Monday June 2
- IPP>PRO teleconference on Mondays during June, starting June 2
- IPP>PRO teleconference, Monday May 5 10am-12noon PDT
- IPP>PRO Update to Randy's document
- IPP>PRO: protocol problem, WAS: sorry, but binary is better
- IPP>PRO: sorry, binary is better (?)
- IPP>PRO: sorry, but binary is better
- IPP>REQ - A call for issues
- IPP>REQ - A call for issues -Reply
- IPP>REQ - A call for issues -Reply -Reply
- IPP>REQ - A call for issues -Reply)
- IPP>REQ - Comments due tomorrow midnight!
- IPP>REQ - comments for next draft of requirements document
- IPP>REQ - customer value statement for press release
- IPP>REQ - end to end scenarios
- IPP>REQ - end to end scenarios -Reply
- IPP>REQ - Re end to end scenarios
- IPP>REQ - Scenarios telecon
- IPP>REQ Comments on latest draft
- IPP>REQ comments on latest requirements
- IPP>REQ Scenarios posted
- IPP>REQ,PRO
- IPP>SEC
- IPP>SEC (Roger's draft Postscript document has been renamed)
- IPP>SEC - getting rid of the security document
- IPP>SEC - ID submitted
- IPP>SEC - minutes of 2/27/97 conference call
- IPP>SEC - Minutes of 4/24 call
- IPP>SEC - new Internet Drafts
- IPP>SEC - Security services
- IPP>SEC - Sun's SunConnect architecture
- IPP>SEC >MOD security and the LPD gateway
- IPP>SEC Internet Draft
- IPP>SEC, IPP>MOD, IPP>DIR - Security attributes
- IPP>Subgroups
- IPP>TES - January agenda
- JMP> Cancel
- JMP> documentFormatIndex
- JMP> jmJobState and jmJobStateReasonsTC [ISSUE:
- JMP> jmJobState and jmJobStateReasonsTC [ISSUE: Are
- JMP> jmJobState and jmJobStateReasonsTC [ISSUE: Are the
- JMP> jmJobState and jmJobStateReasonsTC [ISSUE: Are ther
- JMP> jmJobState and jmJobStateReasonsTC [ISSUE: Are there
- JMP> Job state implementation questions for Unix-based
- JMP> JobStateValue
- JMP> LPD Job submission mapping
- JMP> Minutes for Printer MIB Working Group at IETF Meeting
- JMP> MOD - 'canceled' and 'aborted' job state sema
- JMP> MOD - 'canceled' and 'aborted' job state semantics
- JMP> Proposed jobmon MIB note for impressions (that count blank pages)
- JMP> Updated IPP/JMP joint job-state/job-state-reasons
- JMP> URGENT: JMP/IPP job-state/job-state-reasons: 1:00-1:15 PDT
- JMP> URGENT: Should impressions include blank
- JMP> URGENT: Should impressions include blank last
- JMP> URGENT: Should impressions include blank last p
- JMP> URGENT: Should impressions include blank last p age back sides or not?
- JMP> URGENT: Should impressions include blank last page back sides
- job attributes for public printers
- JobStateReasons -1 [semantics of canceledByOp
- JobStateReasons -1 [semantics of canceledByOperator]
- June Meeting in Boston
- LDAP section of IPP spec
- Locating Printers
- Locating printers in LDAP
- Meeting Info about IETF in San Jose
- Meeting room for proposed UPD meeting on 3/3
- Microsoft Internet Printing Efforts
- MIME multipart/* vs HTTP
- MIME types
- Minutes
- Minutes from SEC meeting in El Segundo, February 7
- misleading press release issued by IPP WG
- MOD - Comment on RFC 2044: need to specify the
- MOD - Comment on RFC 2044: need to specify the ISO 10646
- MOD - Comment on RFC 2044: need to specify the ISO 10646 conformance level
- MOD - Comments from Patrick Powell
- MOD - ISSUE: How to determine the document-uri schemes
- MOD - New Reference
- MOD - Proposed application/ipp registration text
- MOD - Re. Paper size
- MOD - RE: Base printer implementation
- MOD - RE: Base printer implementation requir
- MOD - RE: Base printer implementation requireme
- MOD - RE: Base printer implementation requirements
- MOD - RESEND: Proposal for IPP to meet IESG
- MOD - RESEND: Proposal for IPP to meet IESG Language and
- MOD - RESEND: Proposal for IPP to meet IESG Language and CharSet requirements
- MOD&PRO - Wake Up Call [fix request id lower
- Munich schedule
- New HTTP Methods vs POST -Reply
- New I-Ds from the IPP WG - RESENT DUE TO NON-REPLY
- New Internet Draft Request
- New Internet-Draft Internet Printing Protocol 1.0:
- New Internet-Draft Internet Printing Protocol 1.0: Rationale
- New Internet-Draft Request
- New Internet-Draft Request (another idea on the protocol
- New Internet-Draft Request (another idea on the protocol)
- New Internet-Draft Request [ job-state-reasons being empty]
- New protocol document & Security issues
- P1394> October Meeting in Denver
- Ping - December IETF Meeting
- PING Confirmations for IETF BOF
- PMP> IETF concerns regarding the Printer MIB dr
- PMP> IETF concerns regarding the Printer MIB draft?
- PMP> IETF concerns regarding the Printer MIB draft???
- PMP> ISSUE: OCTET STRING MUST be US-ASCII in 0-127; allow
- PMP> MIME-types and alignment
- PMP> prtAlertTime issue
- PP> PRO - A value-type field for the Protocol Spec
- Print by reference
- printer-resolution standard values retrograded
- PRO (MOD?) - Wake Up Call [request-id needs more syntax]
- producing flat RFC-ready text files from WORD
- producing flat RFC-ready text files from WORD -Reply
- Proposed Charter for Internet Printing Protocol WG
- Proposed IETF Charter, Version 2
- Proposed IETF Charter, Version 2 -Reply
- Proposed well known port for printing via HTTP
- Proposed well known port for printing via HTTP -Reply
- Protocol Definition
- PWG and IPP mailing list subject lines
- PWG IPP charter
- PWG/IPP meeting tomorrow
- PWG> Austin Agenda [will there by a UPD meeting Tues
- PWG> Austin Agenda [will there by a UPD meeting Tues evening?]
- PWG> Maui PWG Overview Minutes
- PWG> October Meeting in Denver
- PWG> PWG OID Structure Proposals [the case for a flat
- RE: Directory Entry Schema
- RE: IPP 0.92 is in drafts
- RE: IPP Mail Archive: RE: IPP> Notifications
- RE: IPP> Additional proposal details
- RE: IPP> ADM - Minutes from PWG IPP Phone Conference - 980114
- RE: IPP> ADM - Minutes from PWG IPP Phone Conference 971015
- RE: IPP> Client usage of TCP port number selection
- RE: IPP> Consensus on sending our drafts to the IESG
- RE: IPP> Delay of IPP ratification
- RE: IPP> Desperately seeking info on HTTP servers and CGI
- RE: IPP> Desperately seeking info on HTTP servers and CGI sc
- RE: IPP> Desperately seeking info on HTTP servers and CGI scripts
- RE: IPP> Desperately seeking info on HTTP servers and CGIscripts
- RE: IPP> Document attributes
- RE: IPP> Does the world need a robust host-to-device network prin
- RE: IPP> FW: MyPost vs. Post
- RE: IPP> Get Attributes
- RE: IPP> HTTP vs. HTTP-lite
- RE: IPP> Identifying jobs in requests
- RE: IPP> IPP Server Contention Analysis
- RE: IPP> ipppreso.ppt (EMBEDDED TEXT VERSION)
- RE: IPP> Job identification mandatory
- RE: IPP> jobid (one more time)
- RE: IPP> Microsoft Presentation
- RE: IPP> Minutes of IPP Weekly Conference call - Nove. 12, 1997
- RE: IPP> MOD optional attributes for more info and driver,
- RE: IPP> MOD & PRO - Security terminology
- RE: IPP> MOD - COMMENTS ON VERSION 1.3 OF MODEL AND SEMANTICS SPE
- RE: IPP> MOD - new 971219 model document posted
- RE: IPP> MOD - Outside the box resolution for the two URIs issue
- RE: IPP> MOD - Push back on simplifying Print operation response
- RE: IPP> MOD - Suggestion: add RequiredResources call to
- RE: IPP> MOD - Suggestion: add RequiredResources call to Windows
- RE: IPP> MOD - Updated Section 15.3 from Bob, Scott, Roger,
- RE: IPP> MOD - URGENT: Ok to call 2nd printer uri: "printer-map-u
- RE: IPP> MOD> A New View of Notification Requirements
- RE: IPP> New HTTP Methods vs POST
- RE: IPP> New HTTP Methods vs POST -Reply
- RE: IPP> Notifications
- RE: IPP> PRO,MOD> User model for clients
- RE: IPP> Processing Algorithm
- RE: IPP> RE: MOD - Push back on simplifying Print operation response
- RE: IPP> RE: Move "orientation-requested" from J.T. to Operation attribute group?
- RE: IPP> RE: Printer Instance Creation/Installation
- RE: IPP> RE: Printer Instance Creation/Installation -Reply
- RE: IPP> RE: SSL3
- RE: IPP> Security - Issues with the existing proposals
- RE: IPP> Security proposal
- RE: IPP> Separating the IPP protocol from the transport mechanism
- RE: IPP> Some notes from an IETF Area Director
- RE: IPP> Some observations from the IPP BOF in the IETF
- RE: IPP> Submission vs. Monitoring and Management
- RE: IPP> Supported URIs for print-by-reference
- RE: IPP> TLS security section of protocol document
- RE: IPP> URGENT: Should impressions include blank last page back
- RE: IPP> Use of SSL3 Framing????
- RE: IPP> What is it we really need?
- RE: IPP> What is it we really need? -Reply
- RE: IPP>MOD
- RE: IPP>MOD - best effort
- RE: IPP>MOD - Print by reference
- RE: IPP>MOD Action Item from LA: fix requesting-user-name explana
- RE: IPP>MOD printer-uri/printer-tls-uri issues
- RE: IPP>MOD PRO Comments on Microsofts IPP document
- RE: IPP>MOD reconsideration of model decision
- RE: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?
- RE: IPP>PRO
- RE: IPP>PRO - Print by reference
- RE: IPP>PRO: sorry, binary is better (?)
- RE: IPP>REQ - end to end scenarios
- RE: IPP>TES - January agenda
- RE: JMP> IPP>MOD HELD vs NEEDS-ATTENTION
- RE: RE: IPP> MOD> A New View of Notification Requirements
- RE: Re[2]: IPP> Notifications
- RE: Some Comments on ipp92.doc - the issues we didn't get to,
- Re[2]: IPP Agenda for Teleconference - Wednesday November 13
- Re[2]: IPP> Common concerns regarding the SWP proposal
- Re[2]: IPP> Firewalls and IPP
- Re[2]: IPP> MIME-types and alignment
- Re[2]: IPP> MOD - RE: The Universal Print Driver
- Re[2]: IPP> Notifications
- Re[2]: IPP> PRO - A value-type field for the Protocol Spec
- Re[2]: IPP> PRO,MOD> User model for clients
- Re[2]: IPP> Proposed Summary of IPP Feature Set -Reply
- Re[2]: IPP> RE: Printer Instance Creation/Installation
- Re[2]: IPP> Security proposal
- Re[2]: IPP> Suggestion for timed delay error code.
- Re[2]: IPP> What is it we really need?
- Re[2]: IPP>MOD - conformance
- Re[2]: IPP>MOD - HTML and IPP streams