Commit in docs/usefor (usepro.xml)

    Date: Thursday, December 11, 2008 @ 20:03:08
  Author: eagle
Revision: 5531

Add a specification for the Original-Sender header field as requested
during Last Call comments and have incoming gateways use it to preserve
the original Sender header field.  Include its registration in the
IANA Considerations section.

This specification may move to USEFOR as part of the final publication
process of both documents.

Modified:
  docs/usefor/usepro.xml

Modified: docs/usefor/usepro.xml
===================================================================
--- docs/usefor/usepro.xml	2008-12-12 04:00:20 UTC (rev 5530)
+++ docs/usefor/usepro.xml	2008-12-12 04:03:08 UTC (rev 5531)
@@ -1384,9 +1384,45 @@
           this <mailbox> SHOULD indicate that the entity responsible
           for injection of the message is a gateway.  If the original
           message already had a Sender header field, it SHOULD be renamed
-          so that its contents can be preserved.</t>
+          to Original-Sender so that its contents can be preserved.  See
+          <xref target="orig-sender" /> for the specification of that
+          header field.</t>
         </section>
 
+        <section anchor="orig-sender" title="Original-Sender header
+          field">
+          <t>The Original-Sender header field holds the content of a
+          Sender header field in an original message received by an
+          incoming gateway, preserving it while the incoming gateway adds
+          its own Sender header field.  The content syntax makes use of
+          syntax defined in <xref target="USEFOR" /> and <xref
+          target="RFC2822" />.</t>
+
+          <figure>
+            <artwork type="abnf">
+      header              =/ Original-Sender-header
+      Original-Sender-header
+                          = "Original-Sender" ":" SP
+                               Original-Sender-content 
+      Original-Sender-content
+                          = mailbox
+            </artwork>
+          </figure>
+
+          <figure>
+            <preamble>The Permanent Message Header Field Repository entry
+            for this header field is:</preamble>
+
+            <artwork>
+   Header field name:          Original-Sender
+   Applicable protocol:        Netnews
+   Status:                     standard
+   Author/Change controller:   IETF
+   Specification document(s):  RFC&rfc.number;
+            </artwork>
+          </figure>
+        </section>
+
         <section title="Gateway Example">
           <t>To illustrate the type of precautions that should be taken
           against loops, here is an example of the measures taken by one
@@ -2219,6 +2255,10 @@
       <t>application/news-transmission is a change to a previous
       registration.</t>
 
+      <t>IANA is requested to register the new header field
+      Original-Sender in the Permanent Message Header Field Repository
+      using the template in <xref target="orig-sender" />.</t>
+
       <t>IANA is also requested to change the status of the message/news
       media type to "OBSOLETE".  message/rfc822 should be used instead.
       An updated template is included in <xref target="media" />.</t>