IPP Mail Archive: IPP> Posted - draft-ietf-ipp-url-scheme-03

IPP> Posted - draft-ietf-ipp-url-scheme-03.txt (2 April 2001)

From: McDonald, Ira (IMcDonald@crt.xerox.com)
Date: Fri Mar 30 2001 - 21:16:45 EST

  • Next message: RonBergman@aol.com: "IPP> Fwd: Media Names, case sensitivity"

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

    Hi folks, Friday (30 March 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-03.pdf (PDF w/ line numbers of '.txt')

        draft-ietf-ipp-url-scheme-03.txt (2 April 2001)

    The substance of this document is in five pages, starting at page 6 (see
    the change log below). Carl-Uno Manros (IETF IPP WG chair) plans to
    send this version to our IETF Applications Area Directors for IETF 'last
    call' and publication as a Proposed Standard RFC.

    Comments?

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

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

    Appendix X - Change History

       [To be deleted before RFC publication]
       
       2 April 2001 - draft-ietf-ipp-url-scheme-03.txt
       - final edits after IETF IPP WG 'last call' comments;
       - revised 'Abstract' and section 1 'Introduction' to remove
         references to ISSUE's and request for comments to the 'ipp@pwg.org'
         mailing list, in preparation for publication as an RFC;
       - revised section 4.5 'IPP URL Scheme Syntax in ABNF' to delete all
         references to HTTP proxy behavior (which IPP does NOT specify), per
         request of Don Wright;
       - revised section 4.5.1 'IPP URL Examples' to remove note
         discouraging the use of literal IP addresses in URLs, to remove
         dependency on Informational [RFC-1900];
       - revised section 4.5.2 'IPP URL Comparisons' to specify the use of
         rules defined in section 3.2.3 'URI Comparison' in [RFC-2616], with
         the sole exception that an empty port MUST be treated as equivalent
         to the IPP well-known port 631, per request of Don Wright;
       - revised section 9 'References' to delete all unused references;
       - revised section 11 'Authors' Addresses' to add the address of the
         IPP WG mailing list for usage questions and comments;

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

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

    I-D Editor, Friday (30 March 2001)

    IETF IPP WG:

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

        <draft-ietf-ipp-url-scheme-03.txt> (2 April 2001)

    It replaces the previous:

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

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

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

    Abstract

       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].

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



    This archive was generated by hypermail 2b29 : Fri Mar 30 2001 - 21:18:24 EST