Subject: Commit in docs/usefor (usepro.xml)

From: [email-masked]
Date: Sun, 14 Jan 2007 16:43:02 -0800 (PST)

Date: Sunday, January 14, 2007 @ 16:43:01
  Author: eagle
Revision: 2242

Improve wording of Xref modifications allowed by relaying and serving
agents and reference USEFOR for the requirement that there be at most
one Xref header field.

Modified:
  docs/usefor/usepro.xml

Modified: docs/usefor/usepro.xml
===================================================================
--- docs/usefor/usepro.xml	2007-01-15 00:39:13 UTC (rev 2241)
+++ docs/usefor/usepro.xml	2007-01-15 00:43:01 UTC (rev 2242)
@@ -832,11 +832,10 @@
             <t>It MUST update the Path header field as described in <xref
             target="path-construct" />.</t>
 
-            <t>It MAY delete any Xref header field present and MAY add a
-            new Xref header field with any valid content.  The Xref header
-            field is not used by relaying agents, but relaying agents that
-            are also serving agents may generate Xref header fields for
-            their own internal purposes.</t>
+            <t>It MAY delete any Xref header field already present.  It
+            MAY add a new Xref header field for its own use (but recall
+            that <xref target="USEFOR" /> permits at most one such
+            header field).</t>
 
             <t>Finally, it passes the article on to other relaying and
             serving agents to which it is configured to send articles.</t>
@@ -911,7 +910,8 @@
             <t>It MUST (except when specially configured to preserve the
             &lt;article-locator>s set by the sending site) remove any Xref
             header field from each article.  It then MAY (and usually
-            will) generate a fresh Xref header field.</t>
+            will) add a new Xref header field (but recall that <xref
+            target="USEFOR" /> permits at most one such field).</t>
 
             <t>Finally, it stores the article and makes it available for
             reading agents.</t>