IPP> draft-ietf-ipp-url-scheme-01.txt (5 Feb 2001)

IPP> draft-ietf-ipp-url-scheme-01.txt (5 Feb 2001)

McDonald, Ira imcdonald at sharplabs.com
Mon Feb 5 21:09:23 EST 2001


Copies: Carl-Uno Manros <cmanros at cp10.es.xerox.com>
        IPP WG <ipp at pwg.org>

Hi folks,                                       Monday (5 February 2001)

I've just sent a new version of 'IPP: IPP URL Scheme' to the
Internet-Drafts editor and posted a copy on the PWG server in the
directory 'ftp://ftp.pwg.org/pub/pwg/ipp/new_URL/' in the files:

    draft-ietf-ipp-url-scheme-01.txt (February 2001)

    draft-ietf-ipp-url-scheme-01.pdf (PDF w/ line numbers of '.txt')

The substance of this document is in five pages, starting at page 5 (see
the change log below).  Carl-Uno Manros (IETF IPP WG chair) wants to
discuss this document at the IETF 50 Plenary in Minneapolis in March.

Comments?

Cheers,
- Ira McDonald, consulting architect at Xerox and Sharp
  High North Inc
  imcdonald at sharplabs.com
  imcdonald at crt.xerox.com

------------------------------------------------------------------------

Appendix X - Change History

   [To be deleted before RFC publication] 
   
   5 February 2001 - draft-ietf-ipp-url-scheme-01.txt 
   - revised section 4.1 'IPP URL Applicability and Intended Usage' to
     clarify that a given IPP URL MAY identify an IPP Printer object or 
     an IPP Job object, per request of Tom Hastings; 
   - revised section 4.5 'IPP URL Scheme Syntax in ABNF' to define IPP
     URLs consistently with section 3.2.2 'http URL' of HTTP/1.1
     [RFC-2616], per request of Tom Hastings; 
   - revised section 4.5 'IPP URL Scheme Syntax in ABNF' to clarify that
     IPP URLs may reference IPP Printer objects, IPP Job objects, or
     (possibly other future) IPP objects, per request of Bob Herriot; 
   - added section 4.5.1 'IPP URL Examples' to supply meaningful
     examples of IPP URLs with host names, IPv4 addresses, and IPv6
     addresses, per request of Tom Hastings; 
   - added section 4.5.2 'IPP URL Comparisons' to define IPP URL
     comparisons consistently with section 3.3 'URI Comparison' of
     HTTP/1.1 [RFC-2616], per request of Tom Hastings; 
   - revised section 5.1 'Conformance Requirements for IPP Clients' to
     clarify that an IPP Client MUST convert IPP URLs to their
     corresponding HTTP URL forms according to section 5 'IPP URL
     Scheme' in [RFC-2910], per request of Tom Hastings and Bob Herriot;
   - revised section 5.1 'Conformance Requirements for IPP Clients' and
     section 5.2 'Conformance Requirements for IPP Printers' to clarify
     that IPP Clients and IPP Printers SHOULD interoperate with IPP/1.0
     systems according to section 9 'Interoperability with IPP/1.0
     Implementations' in [RFC-2910], per request of Carl Kugler; 
   - revised section 5.2 'Conformance Requirements for IPP Printers' to 
     clarify that an IPP Printer MUST listen on (IANA assigned
     well-known) port 631, unless explicitly configured, per request of
     Michael Sweet; 
   - revised section 5.2 'Conformance Requirements for IPP Printers' to 
     clarify that an IPP Printer SHOULD NOT listen on ports other than
     (IANA assigned well-known) port 631, unless explicitly configured, 
     per request of Don Wright; 
   - revised section 6 'IANA Considerations' to clarify that the sole
     purpose of the entire document is IANA registration of the "ipp"
     URL scheme; 
   - deleted Appendix A 'Registration of IPP Port' as unnecessary (port
     is already registered); 
   - deleted Appendix B 'Registration of MIME "application/ipp" as
     unnecessary (MIME registry has recently caught up to RFC 2910); 

------------------------------------------------------------------------

Copies: "Internet Drafts Editor" <internet-drafts at ietf.org>
        "Carl-Uno Manros" <cmanros at cp10.es.xerox.com>
        "Bob Herriot" <robert.herriot at pahv.xerox.com>
        "Ira McDonald" <imcdonald at sharplabs.com>
        "Ira McDonald" <imcdonald at crt.xerox.com>

I-D Editor,                                     Monday (5 February 2001)

IETF IPP WG:

Please place this document in the Internet-Drafts repository named:

    <draft-ietf-ipp-url-scheme-01.txt> (February 2001)

It replaces the previous:

    <draft-ietf-ipp-url-scheme-00.txt> (January 2001)

Thanks very much,
- Ira McDonald (IPP WG member, co-editor of IPP URL scheme)
  High North Inc
  imcdonald at sharplabs.com
  imcdonald at crt.xerox.com

--------------------

Abstract 

   This document is a product of the Internet Printing Protocol Working 
   Group of the Internet Engineering Task Force (IETF).  Comments should
   be submitted to the ipp at pwg.org mailing list.  
   
   This document is intended for use in registering the "ipp" URL scheme
   with IANA and fully conforms to the requirements in [RFC-2717].  This
   document defines the "ipp" URL (Uniform Resource Locator) scheme for
   specifying the location of an IPP Printer, IPP Job, or other IPP
   object (defined in some future version of IPP) which implements the
   IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP 
   [RFC-2910] or any later version of IPP.  The intended usage of the
   "ipp" URL scheme is COMMON.  
   
   The IPP URL scheme defined in this document is based on the ABNF for
   the HTTP URL scheme defined in HTTP/1.1 [RFC-2616], which is derived
   from the URI Generic Syntax [RFC-2396] and further updated by
   [RFC-2732] and [RFC-2373] (for IPv6 addresses in URLs).  An IPP URL
   is transformed into an HTTP URL according to the rules specified in
   section 5 of the IPP/1.1 Protocol [RFC-2910].  

------------------------------------------------------------------------



More information about the Ipp mailing list