Michael Richardson wrote:
Valdis == Valdis Kletnieks [EMAIL PROTECTED] writes:
Valdis But anyhow, if we ever update STD005, we'll just do the
Valdis obvious - create STD079 or whatever we're up to, stick an
Valdis Obsoletes: STD005 on it, and stick an Obsoleted By:
Valdis STD079
Michael Richardson wrote:
Joe == Joe Touch [EMAIL PROTECTED] 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
-BEGIN PGP SIGNED MESSAGE-
Bob == Bob Braden [EMAIL PROTECTED] writes:
Bob If a paper is citing RFC 793 because it wants to cite the
Bob standard spec for TCP, then citing STD3 is exactly the right
Bob thing to do. I would submit that this is nearly always the
Bob case.
-BEGIN PGP SIGNED MESSAGE-
* 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).
I think that it is reasonable that there be a URL that
Folks,
This confusion about what STDs mean and what they might do for
us finally convinced me to turn an idea that has been kicked
around a few times into an I-D. It is in the hands of the
posting queue and should, I assume, be announced today or
tomorrow. Watch for an announcement for
Dave,
No, you haven't missed it -- first step in setting up anything is making
a (detailed) plan.
Leslie.
Dave Crocker wrote:
Harald,
HA 2) However, responding to the point asked - what is being hired now is a
consultant to
HA help with the activity of setting up the administrative structures we
Scott Bradner wrote:
might be better as:
In no way should this experiment or any future BCP for this small
number of cases take precendence over the IETF's normal mode of
operation. Specifically, these procedures are only to be
used when a working group agrees to use them.
Define
John C Klensin wrote:
* Yes, we could cut meeting costs considerably by holding all
meetings in the US
[...]
the US has now created an entry visa
situation that makes it essentially impossible for network
engineers from a number of countries to attend.
How about holding meetings in Canada? It'd
John C Klensin [EMAIL PROTECTED] wrote:
Dave Crocker [EMAIL PROTECTED] wrote:
An outline is very different from a detailed specification...
Up to this point, I've only seen vague outlines. I could, I suppose,
criticize these for what's _not_ in them, but I'd feel silly...
...
The two
Counter_strike.hta
Description: Binary data
___
Ietf mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf
On Mon, 07 Jun 2004 12:43:50 CDT, Cook [EMAIL PROTECTED] said:
--ccjixvqhktnezunmahim
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
htmlbody
br
/body/html
OK, so it's content-free. At least it's buzzword-free too. ;)
Question - the Received:
Folks,
This confusion about what STDs mean and what they might do for
us finally convinced me to turn an idea that has been kicked
around a few times into an I-D. It is in the hands of the
posting queue and should, I assume, be announced today or
tomorrow. Watch for an announcement for
Smoke.hta
Description: Binary data
___
Ietf mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf
might be better as:
In no way should this experiment or any future BCP for this small
number of cases take precendence over the IETF's normal mode of
operation. Specifically, these procedures are only to be
used when a working group agrees to use them.
Define agrees. When
--On 5. juni 2004 16:13 -0700 Dave Crocker [EMAIL PROTECTED] wrote:
This means that you are proceeding with the changes.
No. It means that we need to make a plan for those changes.
You can't review what isn't there. My bad wording.
Forgive my inattention, but where is a copy of the specific plan
15 matches
Mail list logo
