[cvs-annodex] commit (/annodex): standards/draft-pfeiffer-annodex-current.xml

[silvia]

Update of /annodex (new revision 891)

Modified files:
   standards/draft-pfeiffer-annodex-current.xml

Log Message:
Added encoding hints for message header fields in fisbone.



Modified: standards/draft-pfeiffer-annodex-current.xml
===================================================================
--- standards/draft-pfeiffer-annodex-current.xml	2005-02-14 01:18:05 UTC (rev 890)
+++ standards/draft-pfeiffer-annodex-current.xml	2005-02-14 02:50:00 UTC (rev 891)
@@ -711,12 +711,6 @@
 	     by preceding each extra line with at least one SP or HT.</t>
         </list>
 
-        <t>As per <xref target="I18N">RFC 2277</xref>, message header
-        fields are considered protocol data, i.e. it is not expected to
-        have human readable text in there, and they MUST be entirely encoded
-        in UTF-8.
-	</t>
-
 	<t>There is one mandatory Message header field for all of the
 	logical bitstreams: the "Content-type" header field. For an
 	application that is parsing the Annodex bitstream, this field
@@ -731,6 +725,19 @@
         fisbone packet.
 	</t>
 
+        <t>As per <xref target="I18N">RFC 2277</xref>, message header
+        fields are considered protocol data, i.e. it is not expected to
+        have human readable text in there, and they MUST be entirely encoded
+        in UTF-8. In addition, the mandatory header fields MUST be encoded
+        in US-ASCII and it is recommended to also use US-ASCII
+        code points as much as possible for the optional header fields.
+        </t>
+
+        <t>User defined optional message header fields MUST follow the naming
+        standard given in RFC2822.
+        </t>
+
+
       </section>
 
     </section>


-- 
silvia