-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Bob" == Bob Braden <braden@xxxxxxx> writes:
Bob> Good objective. It is the purpose of the "Official Internet
Bob> Protocol Standards" document, which is periodically published
Bob> by the RFC Editor and exists as a living document online at:
Bob> http://www.rfc-editor.org/rfcxx00.html
Bob> Note that STD numbers are only applied to specifications in the
Bob> Standard category. When people say "standards", they often
Bob> mean specifications in the Proposed Standard or Draft Standard
Bob> category. Few specs make it to Standard, for a variety of
Bob> real-world reasons.
Yes, that's fine.
The key thing is for the right thing to show up in an RFP.
I have seen RFC1180 specified, when RFC791/792/793 was intended.
Upon challenging this, a completely different RFC was
specified... (can't find that in my notes)
Bob> Perhaps STD numbers should be applied all levels of the
Bob> standards track (but before we did that, we would need to think
Bob> carefully about the consequences).
It might be worth doing this. Yes, some thought is necessary.
One thing to consider, is having a web server which, when asked for:
http://www.ietf.org/ref/rfc0791.txt
redirects to:
http://www.ietf.org/std/std005.txt
The point being to change people's habits a little bit.
- --
] "Elmo went to the wrong fundraiser" - The Simpson | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr@xxxxxxxxxxxxx http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBQL57/4qHRg3pndX9AQERmAP8CbkKmS1PKn1uK/jlt7IaKRLrsSv8npMI
QpnduXiEvn+i+ZB7x+oLD0ipjxdzHAL035werW8Yklra1+Amf2OxbPw50KxiZ4Ru
lniUrUQ304lEQm1iMUIoBTZuCUOZ+M4aOLrH5WOrrEYh7e6dz51Z9gMocerAkig+
2xe2QDfxMO0=
=f5eM
-----END PGP SIGNATURE-----
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf