On Mar 14, 2005, at 1:32 AM, Frank Ellermann wrote:
Gaurav Vaish wrote:
I'm not sure what you mean by "Informational RFC".
I'm also not sure, but you got me... :-) RfC 2229 is "only"
an informational RfC, and I don't know who could update or
replace it without the consent of the original authors.
I have some bed-time reading for you:
ftp://ftp.isi.edu/in-notes/rfc2026.txt
2026 The Internet Standards Process -- Revision 3. S. Bradner. October
1996. (Format: TXT=86731 bytes) (Obsoletes RFC1602) (Updated by
RFC3667, RFC3668, RFC3932, RFC3979, RFC3978) (Also BCP0009)
(Status:
BEST CURRENT PRACTICE)
ftp://ftp.isi.edu/in-notes/rfc3667.txt
3667 IETF Rights in Contributions. S. Bradner. February 2004. (Format:
TXT=43297 bytes) (Obsoleted by RFC3978) (Updates RFC2026) (Status:
BEST CURRENT PRACTICE)
ftp://ftp.isi.edu/in-notes/rfc3668.txt
3668 Intellectual Property Rights in IETF Technology. S. Bradner.
February 2004. (Format: TXT=41365 bytes) (Obsoleted by RFC3979)
(Updates RFC2026, RFC2028) (Status: BEST CURRENT PRACTICE)
ftp://ftp.isi.edu/in-notes/rfc3932.txt
3932 The IESG and RFC Editor Documents: Procedures. H. Alvestrand.
October 2004. (Format: TXT=17093 bytes) (Updates RFC3710, RFC2026)
(Also BCP0092) (Status: BEST CURRENT PRACTICE)
ftp://ftp.isi.edu/in-notes/rfc3979.txt
3979 Intellectual Property Rights in IETF Technology. S. Bradner, Ed..
March 2005. (Format: TXT=41366 bytes) (Obsoletes RFC3668) (Updates
RFC2028, RFC2026) (Also BCP0079) (Status: BEST CURRENT PRACTICE)
ftp://ftp.isi.edu/in-notes/rfc3978.txt
3978 IETF Rights in Contributions. S. Bradner, Ed.. March 2005.
(Format: TXT=43574 bytes) (Obsoletes RFC3667) (Updates RFC2026)
(Also
BCP0078) (Status: BEST CURRENT PRACTICE)
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf