Hi, Peter, all,
Many thanks for the comments; replies inline...
On May 17, 2012, at 5:25 AM, Peter Saint-Andre wrote:
On 5/16/12 3:53 PM, The IESG wrote:
The IESG has received a request from the Managed Incident Lightweight
Exchange WG (mile) to consider the following document:
-
On Fri, May 18, 2012 at 1:06 AM, Hector Santos hsan...@isdg.net wrote:
Lee Howard wrote:
-Original Message-
From: ietf-boun...@ietf.org [mailto:ietf-boun...@ietf.org] On Behalf Of
Dave Cridland
Consider:
An octet may contain 0-255.
An octet contains 0-255.
An octet might
I find this morning a message on the URN WG list
by Alfred Hines on RFC 6329, which has a new (AFAIK) convention on
normative language
3. Conventions Used in This Document
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT,
SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in
On May 16, 2012, at 10:22 PM 5/16/12, Ned Freed wrote:
On May 16, 2012, at 5:22 PM 5/16/12, ned+i...@mauve.mrochek.com wrote:
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT,
SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this
document are to be interpreted as
On Fri, May 18, 2012 at 12:41 PM, Ralph Droms rdroms.i...@gmail.com wrote:
On May 16, 2012, at 10:22 PM 5/16/12, Ned Freed wrote:
On May 16, 2012, at 5:22 PM 5/16/12, ned+i...@mauve.mrochek.com wrote:
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT,
SHOULD, SHOULD NOT,
Hi, Jean-Marc and co-authors
On Thu, 2012-05-17 at 12:49 -0400, Jean-Marc Valin wrote:
Hi Elwyn,
We're submitted a -14 draft to address your comments. Again, see the
response to each of these issues in the attached document.
I think we are done. Thanks once again for the rapid response.
So, I recommend an errata to RFC 2119: These words MUST NOT appear in a
document in lower case.
I'm glad you said I recommend instead of I have recommended, as the
latter would violate the recommended (oh dear) rule.
This RECOMMENDED rule would also imply that documents can no longer be
I recommend an errata to RFC 2119: These words MUST NOT appear in a
document in lower case.
first, that is not an erratum, it is a non-trivial semantic change.
second, do we not already have enough problems being clear and concise
without removing common words from our language?
randy
I recommend an errata to RFC 2119: These words MUST NOT appear in a
document in lower case.
first, that is not an erratum, it is a non-trivial semantic change.
And therefore explicitly disallowed by the erratum process.
second, do we not already have enough problems being clear and
On May 18, 2012, at 2:27 PM 5/18/12, Randy Bush wrote:
I recommend an errata to RFC 2119: These words MUST NOT appear in a
document in lower case.
first, that is not an erratum, it is a non-trivial semantic change.
You are correct and point taken.
second, do we not already have
Dave Crocker's suggestion would minimize the number of words taken out
of our vocabulary:
for a language other than english.
In addition to clear and concise we need precision and avoidance of
ambiguity.
wonderful rofl. thanks. mind if i put that in my public quotes file?
randy
On May 18, 2012, at 2:40 PM 5/18/12, Randy Bush wrote:
Dave Crocker's suggestion would minimize the number of words taken out
of our vocabulary:
for a language other than english.
In addition to clear and concise we need precision and avoidance of
ambiguity.
wonderful rofl. thanks.
The changes in draft-ietf-emu-chbind-15.txt satisfactorily address
almost all of the comments in my April 13, 2012 secdir review. I do
have one remaining substantive comment on this latest draft and two
non-substantive ones.
Substantive Comment
---
The last paragraph of section
my wife says the purpose of tourists (we in japan) is to amuse the
natives
randy
A new Request for Comments is now available in online RFC libraries.
RFC 6621
Title: Simplified Multicast Forwarding
Author: J. Macker, Ed.
Status: Experimental
Stream: IETF
Date: May 2012
Mailbox:
A new Request for Comments is now available in online RFC libraries.
RFC 6624
Title: Layer 2 Virtual Private Networks
Using BGP for Auto-Discovery and Signaling
Author: K. Kompella, B. Kothari,
R. Cherukuri
A new Request for Comments is now available in online RFC libraries.
RFC 6625
Title: Wildcards in Multicast VPN Auto-Discovery
Routes
Author: E. Rosen, Ed.,
Y. Rekhter, Ed.,
W. Hendrickx,
A new Request for Comments is now available in online RFC libraries.
RFC 6636
Title: Tuning the Behavior of the
Internet Group Management Protocol (IGMP) and
Multicast Listener Discovery (MLD) for Routers
18 matches
Mail list logo
