I disagree with Valdis' description. I actually worked for a standards
organization that used a codebase as part of the definition of the
standards it produced. The concept of "Running code" is good, but where
are the IETF reference implementations? If "running code" is the actual
standard, then
*> Then requests for an RFC should _never_ redirect to a STD (which was
*> where I was going, BTW), but it's OK for the STD to redirect to the
*> current RFC (or set thereof, if multiples).
*>
*> In that case, redirection isn't as simple as an HTTP redirect, since
*> there are sever
*>
*>
*> Bob Braden wrote:
*>
*> > *>
*> > *> And what happens when a STD is updated/revised?
*> > *>
*> > *> Joe
*> >
*> > Joe,
*> >
*> > Unnnh, let me guess. Update the web pointer to the new RFC(s)?
*> >
*> > Bob Braden
*>
*> I was thinking of the
On Thu, 03 Jun 2004 11:04:06 PDT, Joe Touch said:
> STD-5 is a nice choice - it actually refers to 6 different RFCs.
>
> So which one redirects to STD005.txt, and what is in it?
>
> (To see this noted in the RFCs themselves, see STD-62, which refers to a
> set of 8 different RFCs.)
>
> And wha
*>
*> And what happens when a STD is updated/revised?
*>
*> Joe
Joe,
Unnnh, let me guess. Update the web pointer to the new RFC(s)?
Bob Braden
___
Ietf mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf
Michael Richardson wrote:
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
STD-5 is a nice choice - it actually refers to 6 different RFCs.
So which one redirects to STD005.txt,
-BEGIN PGP SIGNED MESSAGE-
> "Bob" == Bob Braden <[EMAIL PROTECTED]> 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 a
If the message will not displayed automatically,
follow the link to read the delivered message.
Received message is available at:
www.ietf.org/inbox/ietf/read.php?sessionid-24762
[Filename: message.scr, Content-Type: audio/x-wav]
The attachment file in the message has been removed by eManager.
A reminder to the people actively posting on the "spoofing email addresses"
thread:
RFC 3005 says the following (emphasis mine):
This list is meant for INITIAL discussion only. Discussions that
fall within the area of any working group or well established list
should be moved to such more
Bravo! At last. Spam is a clutter of our way to use TCP/IP and SMTP in
which criminal and cyberwarfare actions develop. I was interested talking
about vulnerability to internet with the Chair of a Banking Association
Committee on Security to hear him calling spam "saturation bombing".
Solution
10 matches
Mail list logo
