IPP Mail Archive: RE: IPP> IPP Bake-Off 3 Issue 5

IPP Mail Archive: RE: IPP> IPP Bake-Off 3 Issue 5

RE: IPP> IPP Bake-Off 3 Issue 5

From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Thu Oct 26 2000 - 19:34:23 EDT

  • Next message: sune.pedersen@i-data.com: "Re: IPP> IPP Bake-Off 3 Implementation specific issues (5) - BO3-IMP-2: Persistent connections in HTTP1.1"

    Hi Pete,

    Yes, you have it right - the authority is RFC 2368 'mailto:' URL
    (see excerpt below).

    Cheers,
    - Ira McDonald, consulting architect at Xerox and Sharp
      High North Inc

    ----Original Message-----
    From: Zehler, Peter [mailto:Peter.Zehler@usa.xerox.com]
    Sent: Thursday, October 26, 2000 11:48 AM
    To: IPP Discussion List (E-mail)
    Subject: IPP> IPP Bake-Off 3 Issue 5

    All,
    BO3-5: In the subscription object is the does the mailto URL contain '//'.
    Is it <mailto://mumble> or <mailto:mumble> ?
                    Proposed resolution: The mailto URL does not include '//'.

                                    Peter Zehler
                                    XEROX
                                    
    --------------------------------------------------------
    [from RFC 2368]

    2. Syntax of a mailto URL

       Following the syntax conventions of RFC 1738 [RFC1738], a "mailto"
       URL has the form:

         mailtoURL = "mailto:" [ to ] [ headers ]
         to = #mailbox
         headers = "?" header *( "&" header )
         header = hname "=" hvalue
         hname = *urlc
         hvalue = *urlc

       "#mailbox" is as specified in RFC 822 [RFC822]. This means that it
       consists of zero or more comma-separated mail addresses, possibly
       including "phrase" and "comment" components. Note that all URL
       reserved characters in "to" must be encoded: in particular,
       parentheses, commas, and the percent sign ("%"), which commonly occur
       in the "mailbox" syntax.

       "hname" and "hvalue" are encodings of an RFC 822 header name and
       value, respectively. As with "to", all URL reserved characters must
       be encoded.

       The special hname "body" indicates that the associated hvalue is the
       body of the message. The "body" hname should contain the content for
       the first text/plain body part of the message. The mailto URL is
       primarily intended for generation of short text messages that are
       actually the content of automatic processing (such as "subscribe"
       messages for mailing lists), not general MIME bodies.

       Within mailto URLs, the characters "?", "=", "&" are reserved.

       Because the "&" (ampersand) character is reserved in HTML, any mailto
       URL which contains an ampersand must be spelled differently in HTML
       than in other contexts. A mailto URL which appears in an HTML
       document must use "&amp;" instead of "&".

       Also note that it is legal to specify both "to" and an "hname" whose
       value is "to". That is,

         mailto:addr1%2C%20addr2

         is equivalent to

         mailto:?to=addr1%2C%20addr2

         is equivalent to

         mailto:addr1?to=addr2

       8-bit characters in mailto URLs are forbidden. MIME encoded words (as
       defined in [RFC2047]) are permitted in header values, but not for any
       part of a "body" hname.



    This archive was generated by hypermail 2b29 : Thu Oct 26 2000 - 19:57:56 EDT