Re: [apps-discuss] WGLC on draft-ietf-appsawg-rfc5451bis-00

[Barry Leiba <[e-mail]>]

Just on one item:

>> 8.1. *Normative References*
>>
>> [AR-ORIG] will be obsolete by the time this I-D is published.  How can
>> it be a normative reference?
>
> That's a good procedural question.  I think it has to be because it involves
> IANA actions that are being amended, but I think this is something that can
> be sorted out during IESG Evaluation.

Coupla things:

1. It's usually not necessary for the obsolescent document to be a
normative reference, as the obsoleting document has all the necessary
information.  That's certainly true in this case, and I suggest making
the reference informative.

2. Have I told you how unhappy I am with the citation style you use?
It's generally not something I'm willing to argue about, preferring to
defer to the authors' style of citations, but in this case it seems
particularly bad.  May I suggest this?:

OLD
   [AR-ORIG] defined a new header field for electronic mail messages
   that presents the results of a message authentication effort in a
   machine-readable format.

NEW
   The first edition of this document [RFC5451] defined a new header
   field for electronic mail messages that presents the results of a
   message authentication effort in a machine-readable format.

...and replace all other instances of "[AR-ORIG]" with "[RFC5451]" (or
even just "RFC 5451"; how many citations to the same document do you
need?).

Barry