--On 17 August 2004 09:20 -0700 Bob Braden [EMAIL PROTECTED] wrote:
* From: Iljitsch van Beijnum [EMAIL PROTECTED]
*
* Why is the list of internet standards so hard to find?
*
* It seems to me this list deserves top ranking on the first page at
* www.ietf.org, but that's certainly not
Bob,
I think the intent of Iljitsch's note was that the list of IETF
Standards should appear in an obvious place (labeled IETF
Standards) on http://www.ietf.org/ - if the label points to
http://www.rfc-editor.org/rfc.html, that's fine.
... leaving the question of what standards are actually
On 18-aug-04, at 13:15, Spencer Dawkins wrote:
I think the intent of Iljitsch's note was that the list of IETF
Standards should appear in an obvious place (labeled IETF
Standards) on http://www.ietf.org/ - if the label points to
http://www.rfc-editor.org/rfc.html, that's fine.
Right.
There seems
Eric A. Hall wrote:
On 8/17/2004 2:09 PM, John C Klensin wrote:
To be clear about this, I think there are three choices which we
might prefer in descending order:
(1) There is a single canonical wire format in which
these things are transmitted.
Such a specification would
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] writes:
--On 17 August 2004 09:20 -0700 Bob Braden [EMAIL PROTECTED] wrote:
* From: Iljitsch van Beijnum [EMAIL PROTECTED] *
* Why is the list of internet standards so hard to find? *
* It seems to me this list deserves top ranking on the
Actually if you knew what it meant but weren't that familiar with the place
of an RFC(someone who's read 2 specs or something) you would assume IMHO
that an Internet Standard is NOT a request for comments.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
--On Wednesday, 18 August, 2004 10:03 -0700 Thomas Gal
[EMAIL PROTECTED] wrote:
Actually if you knew what it meant but weren't that familiar
with the place of an RFC(someone who's read 2 specs or
something) you would assume IMHO that an Internet Standard
is NOT a request for comments.
Another fake bounce from Mr. Austein.
It was also pointed out that Mr. Austein also fails to disclose his
conflict of interest with Av8 Internet according to the ISOC Code of
Conduct: http://www.isoc.org/members/codeconduct.shtml
8. In the case of financial or material conflict between
The IESG has approved the following document:
- 'RTP payload format for a 64 kbit/s transparent call '
draft-ietf-avt-rtp-clearmode-05.txt as a Proposed Standard
This document is the product of the Audio/Video Transport Working Group.
The IESG contact persons are Allison Mankin and Jon
The IESG has approved the following document:
- 'Framework for Layer 2 Virtual Private Networks (L2VPNs) '
draft-ietf-l2vpn-l2-framework-05.txt as an Informational RFC
This document is the product of the Layer 2 Virtual Private Networks Working
Group.
The IESG contact persons are Thomas
10 matches
Mail list logo
