http://www.ietf.org/internet-drafts/draft-duerst-archived-at-02 .txt

Martin,

Two nits concerning the header field registration (copied below).

1. Specify that the entry is for the permanent header field registry, 
assuming the relevant conditions are satisfied; e.g.
[[
   IANA is herewith requested to register the Archived-At header field
   in the Permanent Message Header Fields Registry, per RFC 3864, as follows:
]]


2. You need to decide if this is or is not to be usable with netnews.  If 
it is to be usable in netnews, then (for clarity) there should be two 
registration templates, one for mail and one for netnews, otherwise the same.
If you are really not sure about netnews, then I suggest you leave it out 
and separately request an entry for netnews in the provisional header field 
registry:  it can be moved later if netnews community think that's reasonable.
#g
--


[[
7.  IANA considerations


   IANA is herewith requested to register the Archived-At header field
   in the Message Header Fields Registry as follows:


      Header field name:
         Archived-At


      Applicable protocol:
         mail (RFC 2822), optionally also netnews (RFC 1036)


      Status:
         provisional
         (Note to RFC Editor: Replace this with "standard")


      Author/Change controller:
         Martin Duerst, duerst(_at_)w3(_dot_)org, W3C/Keio University
         (Note to RFC Editor: Replace this with "IETF")


      Specification document(s):
         Internet-Draft draft-duerst-archived-at-02.txt
         (Note to RFC Editor: Replace this with
          RFC YYYY (RFC number of this spec))


      Related information:
         none
]]



------------
Graham Klyne
For email:
http://www.ninebynine.org/#Contact