Re: Colloquial language [Re: Last Call: (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]

2012-05-30 Thread Dave Crocker
On 5/31/2012 8:36 AM, Brian E Carpenter wrote: Have we any evidence that this is a problem for the community? The informal style is one of the virtues of the Tao. I'd be sorry to lose it. Let's separate use of colloquial language from overall writing style. It is possible to write in an info

Colloquial language [Re: Last Call: (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]

2012-05-30 Thread Brian E Carpenter
On 2012-05-31 02:49, Peter Saint-Andre wrote: > Overall I continue to think that this is a helpful document, as were its > predecessors. > > That said, I would assume that many potential readers of this document > are not native English speakers. Thus I suggest that the more colloquial > words and

Mission statement [Re: Last Call: (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]

2012-05-30 Thread Brian E Carpenter
On 2012-05-31 07:22, Eliot Lear wrote: ... > * I've been told by some that the Mission of the IETF is in some way > out of date. I don't know whether this is true, That sound like somebody's personal opinion, but it is still a BCP and therefore still represents IETF consensus. > but

Re: Last Call: (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC

2012-05-30 Thread Eliot Lear
Hi, I agree with much of what Peter Saint-Andre wrote. In addition I suggest the following changes: * I've been told by some that the Mission of the IETF is in some way out of date. I don't know whether this is true, but if it is, the reference should be removed. * It's probably wor

Re: Last Call: (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC

2012-05-30 Thread Peter Saint-Andre
Overall I continue to think that this is a helpful document, as were its predecessors. That said, I would assume that many potential readers of this document are not native English speakers. Thus I suggest that the more colloquial words and phrases might best be changed to more standard English. N

last call comments on draft-ietf-krb-wg-kdc-model

2012-05-30 Thread Sam Hartman
--- Begin Message --- Topics: [Ietf-krb-wg] Add. comments on Kdc model, WAS[Re: I-D Action: draft-ietf-krb-wg-kdc-model-12.txt] Re: [Ietf-krb-wg] I-D Action: draft-ietf-krb-wg-kdc-model-12.txt --- End Message --- --- Begin Message --- I have additional comments. These following 3 attribu

Re: [Ietf-krb-wg] Add. comments on Kdc model, WAS[Re: I-D Action: draft-ietf-krb-wg-kdc-model-12.txt]

2012-05-30 Thread Sam Hartman
[I'm going to forward Simo's original comments to the IETF list because this doc is in IETF last call. Here are my responses as chair. ] > "Simo" == Simo Sorce writes: Simo> 4.1.1.5. principalNumberOfFailedAuthenticationAttempts Simo>This single-valued integer attribute contains

RE: New Maillist for the discussion on the Management of Constrained Networks and Devices

2012-05-30 Thread Ersue, Mehmet (NSN - DE/Munich)
Hi All, as noted in the maillist announcement of IETF secretary "coma" maillist is for the discussion on the management of constrained networks and devices. The mailing list will discuss and identify the issues and requirements and objectives for the management of devices in such an environment wi

new mailing list for discussing ABNF issues

2012-05-30 Thread Dave Crocker
Folks, Periodically someone wants to ask a question about ABNF, suggest an enhancement or otherwise exchange views about ABNF. There has not been an obvious forum for this. This sometimes means that Paul Overell and I get queried, as authors of the relevant RFC. For quick items, that's fin

RE: Last Call: (Guidelines for DefiningExtensions to IODEF) to Informational RFC

2012-05-30 Thread Romascanu, Dan (Dan)
Hi, The inclusion of the template as an Appendix in the document is confusing - right now A.1 through A.7 define sections in the future I-Ds, while A.8 and A.9 describe appendices in the future I-D. This document has two sections each titled Appendix A and Appendix B. Moreover, this inclusion has