-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Joe" == Joe Touch <touch@xxxxxxx> writes:
>> 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
Joe> STD-5 is a nice choice - it actually refers to 6 different
Joe> RFCs.
You mean that there are 5 documents in the set.
Hmm. I didn't realize that this occured.
Joe> So which one redirects to STD005.txt, and what is in it?
Joe> (To see this noted in the RFCs themselves, see STD-62, which
Joe> refers to a set of 8 different RFCs.)
Hmm. okay, so what I want to do doesn't entirely work.
Joe> And what happens when a STD is updated/revised?
I had hoped that all the RFCs that have become STDs would direct to
the STD. The specific version would be available via another URL (such
as the /rfc/rfcXXXX.txt that we have now).
The idea was that it would always refer to the most recent one.
But, if we have multiple documents as part of STD-5, then that won't
work at all.
- --
] "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
iQCVAwUBQL/CDoqHRg3pndX9AQEA+QQA7+GUypFwFKG2F1DD+5vfXpqEgbtot1U0
poFo73KfhDoaP22nR1ElkiApUifqSnpTRfNy+HgujD2nfdjBX00fy0ietPVVHlpy
BetE+8/7+9JPrW7wwI7Yljs9TfB6jtCcgHaDxkl+vsWWlX+vI9i7EFBvjyUOT354
q9btQvGEbzg=
=uTXm
-----END PGP SIGNATURE-----
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf