[tcpm] Re: draft-ietf-tcpm-tcp-antispoof-01.txt

[Joe Touch <[e-mail]>]

Pekka Savola wrote:
> On Sat, 8 Oct 2005, Joe Touch wrote:
>>> 8.1. Normative References
>>>
>>>    As this is not a standards document, this section has no meaning.
>>>
>>> ==> Normative means more than just what's what's MUST or MUST not for a
>>> standard document.  It also means 1) "documents which should be read and
>>> understood by the reader of this document in order to understand this
>>> document" and 2) "documents which should be published as stable
>>> references
>>> before this document gets published as RFC".
>>>
>>> I think there are a number of references in category 1).  There are
>>> also a
>>> couple of others in category 2),e.g., tcpmd5app-01, ikev2/AH, dccp.
>>
>> Although I personally agree with you (esp. w.r.t. #1) I've had this
>> debate before, and my understanding is that "normative" in the IETF
>> means "refers to a standard to enable a a specificiation". Since this
>> isn't a spec (standards track), there can be no normative refs.
>>
>> If that's not the case, however, somebody in authority holler. ;-)
>>
>> My original wording was a bit sarcastic in response to that
>> understanding, so it has been downgraded to 'None.'
> 
> FWIW,
> 
> There's extensive precedent for having Normative references for
> Informational documents and the IESG not barking on that.

The IESG isn't the one that barks (they're asleep - consider the TCP
roadmap and discussion on the normative ref to an ID); it's the
RFC-Editor pass that catches these.

Joe

_______________________________________________
tcpm mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/tcpm