Re: IANA Considerations

To: Joe Touch <touch at ISI.EDU>
Subject: Re: IANA Considerations
From: "Steven M. Bellovin" <smb at cs.columbia.edu>
Date: Wed, 06 Jul 2005 11:55:57 -0400
Cc: Ned Freed <ned.freed at mrochek.com>, Dave Crocker <dcrocker at bbiw.net>, Bob Hinden <bob.hinden at nokia.com>, Sam Hartman <hartmans-ietf at mit.edu>, ietf at ietf.org
In-reply-to: Your message of "Wed, 06 Jul 2005 08:29:07 PDT." <42CBF8C3.8080102@isi.edu>
List-help: <mailto:ietf-request@ietf.org?subject=help>
List-id: IETF-Discussion <ietf.ietf.org>
List-post: <mailto:ietf@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
Sender: ietf-bounces at ietf.org

In message <42CBF8C3.8080102 at isi.edu>, Joe Touch writes:
>This is an OpenPGP/MIME signed message (RFC 2440 and 3156)

>
>It seems like such considerations are, by definition, relevant only for
>standards-track RFCs. It is not useful to require it for other documents.
>
>
Not at all -- code points can be assigned by non-standards track RFCs.

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb



_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

References:
- Re: IANA Considerations
  - From: Joe Touch

Prev by Date: Re: IANA Considerations
Next by Date: Re: Should the IESG rule or not? and all that...
Previous by thread: Re: IANA Considerations
Next by thread: Re: IANA Considerations
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: IANA Considerations

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.