On 05/16/2012 06:59, Barry Leiba wrote:
In fact, RFC 2119 says that the normative keywords are often
capitalized, but doesn't require that they be.
Standards should be written in such a way as to remove as much ambiguity
as possible, not show how clever we are. That allowance in 2119 was a
At 14:53 16-05-2012, The IESG wrote:
The IESG has received a request from the Managed Incident Lightweight
Exchange WG (mile) to consider the following document:
- 'Guidelines for Defining Extensions to IODEF'
draft-ietf-mile-template-04.txt as Informational RFC
The IESG plans to make a
- Original Message -
From: Doug Barton do...@dougbarton.us
To: ietf@ietf.org
Cc: Barry Leiba barryle...@computer.org
Sent: Thursday, May 17, 2012 7:18 AM
On 05/16/2012 06:59, Barry Leiba wrote:
In fact, RFC 2119 says that the normative keywords are often
capitalized, but doesn't
Andrew Sullivan a...@anvilwalrusden.com wrote:
On Wed, May 16, 2012 at 07:17:04AM -0700, Dave Crocker wrote:
Case does not define meaning in normal language, why should it here?
That is false. Consider these two passages:
The King asked the Queen,
and the Queen asked the
Randy Bush ra...@psg.com wrote:
can != may
one is ability, the other permission
Right, and if you are giving some entity permission to do something in a
protocol spec, surely that ought to be written in normative terms.
Tony.
--
f.anthony.n.finch d...@dotat.at http://dotat.at/
FitzRoy:
On 2012-05-16 22:29, Dave Cridland wrote:
On Wed May 16 21:10:02 2012, Randy Bush wrote:
Authors must be fastidious about this.
s/this/documents/
RFC 2119 ยง6 says:
Imperatives of the type defined in this memo must be used with care
and sparingly. In particular, they MUST only be used where
I think the authors just about have a -14 draft ready but I wanted to comment
on one topic inline
On May 16, 2012, at 3:26 PM, Elwyn Davies wrote:
Hi, Jean-Marc.
... and thanks for the super-quick response! You have been quite busy.
I have had a look through the new draft and I
-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 contain 0-255 - or it might not?
The Foo octet MUST lie between 0 and 127 inclusive; that is,
Hi, Jean-Marc.
... and thanks for the super-quick response! You have been quite busy.
I have had a look through the new draft and I think the additions help
considerably with comprehension for the naive (and to give new
implementers a way in.)
I'll leave you to negotiate with the RFC Editor
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.
Thanks again,
Jean-Marc
On 12-05-16 05:26 PM, Elwyn Davies wrote:
Hi, Jean-Marc.
... and thanks for the super-quick response! You have been
Total of 57 messages in the last 7 days.
script run at: Fri May 18 00:53:03 EDT 2012
Messages | Bytes| Who
+--++--+
10.53% |6 | 7.75% |35365 | d...@dcrocker.net
5.26% |3 | 11.69% |53304 |
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 contain 0-255 - or it might not?
The Foo octet MUST lie between 0 and 127
The IESG has approved the following document:
- 'EAP Extensions for EAP Re-authentication Protocol (ERP)'
(draft-ietf-hokey-rfc5296bis-07.txt) as Proposed Standard
This document is the product of the Handover Keying Working Group.
The IESG contact persons are Stephen Farrell and Sean Turner.
The IESG has approved the following document:
- 'S/MIME Capabilities for Public Key Definitions'
(draft-ietf-pkix-pubkey-caps-07.txt) as Informational RFC
This document is the product of the Public-Key Infrastructure (X.509)
Working Group.
The IESG contact persons are Sean Turner and Stephen
We plan to run a virtual interim meeting for CORE WG on Monday, June 4
at 09:00 EDT. This will be a webex phone call that is scheduled for two
hours. The agenda and conference bridge details will be announced on
the CORE WG email list.
The IESG has received a request from the DNS-based Authentication of
Named Entities WG (dane) to consider the following document:
- 'The DNS-Based Authentication of Named Entities (DANE) Transport Layer
Security (TLS) Protocol: TLSA'
draft-ietf-dane-protocol-21.txt as Proposed Standard
This
16 matches
Mail list logo
