On Dec 22, 2009, at 8:39 PM, Dave CROCKER wrote:
Brian,
This seems worth being a bit pedantic about, to make sure we all share the
same understanding: I take your interpretation to mean that the RFC Editor
can, on their own initiative, fix the problem(s) that Julan has raised and
that
discussion list;
Bob Hinden; rfc-inter...@rfc-editor.org; dcroc...@bbiw.net
Subject: Re: [rfc-i] Important: do not publish draft-iab-streams-
headers-boilerplates-08 as is!
On Dec 22, 2009, at 12:08 PM, Russ Housley wrote:
Dave:
I agree with Birain's assessment. The RFC Editor can handle
Julian Reschke wrote:
...
In the meantime, draft-iab-streams-headers-boilerplates is in AUTH48,
and I have updated my document with the current changes; see
http://tools.ietf.org/html/draft-reschke-hab-01, in particular
http://tools.ietf.org/html/draft-reschke-hab-01#appendix-A.1 (change
Julian,
You wrote:
This problem was reported over three weeks ago. Are we really incapable
to fix something simple like that within three weeks?
We are at a point where making trivial changes to headers and boilerplates
leads to discussion about more substantive matters and causes even
FWIW, the document allows the RFC editor some headway in maintaining the
language in the style guide.
Maybe we^H^Hthe IAB should have aimed at full delegation of the boilerplate,
exactly as for the Trust-maintained boilerplate.
For now, there are indeed weasel words such as:
However, this
Dave:
I agree with Birain's assessment. The RFC Editor can handle this
issue without delaying publication of the document.
Russ
At 02:39 PM 12/22/2009, Dave CROCKER wrote:
Brian,
This seems worth being a bit pedantic about, to make sure we all
share the same
understanding: I take your
On Dec 22, 2009, at 12:08 PM, Russ Housley wrote:
Dave:
I agree with Birain's assessment. The RFC Editor can handle this issue
without delaying publication of the document.
+1
Bob
___
Ietf mailing list
Ietf@ietf.org
All,
I agree with Birain's assessment. The RFC Editor can handle this issue without
delaying publication of the document.
+1
Me too. Publish the RFC. Please.
Jari
___
Ietf mailing list
Ietf@ietf.org
Julian Reschke wrote:
Bob Braden wrote:
Jim,
Understood, but the RFC Editor does care how it flows. We would like to
get it as nearly right as possible, going out of the gate.
Bob Braden
...
For tracking purposes, I just published draft-reschke-hab-00
Can we please recommend *not* to put a file extension into the URL?
The text can be updated - there is no file extension. The URL is of
the form:
http://www.rfc-editor.org/static-path/rfcrfc-no
For example:
http://www.rfc-editor.org/info/rfc2026
RFC Editor/ah
On Nov 24, 2009, at 7:01
Subject: [rfc-i] Important: do not publish draft-iab-streams-headers-
boilerplates-08 as is!
Hi,
I just created five test cases representing the appendices A.1 to A.5.
Turns out that the text in the examples is not in sync with the
definitions in Section 3 (see, for instance,
http
Bob Braden wrote:
Jim,
Understood, but the RFC Editor does care how it flows. We would like to
get it as nearly right as possible, going out of the gate.
Bob Braden
...
For tracking purposes, I just published draft-reschke-hab-00
Jim Schaad wrote:
Let's just get this published and go with what we have even if it does not
necessarily read real pretty. The text of the strings can be updated at a
later point by a modification of the RFC Style Guide if there are enough
complaints about how the text looks. Given that it is
Bob Braden wrote:
Jim Schaad wrote:
Let's just get this published and go with what we have even if it does not
necessarily read real pretty.
Ready Fire Aim has characterized the pattern of IPR work on this topic in
recent years, and the results have been exactly as messy as one would
Jim Schaad wrote:
Let's just get this published and go with what we have even if it does not
necessarily read real pretty. The text of the strings can be updated at a
later point by a modification of the RFC Style Guide if there are enough
complaints about how the text looks. Given that it is
Hi Julian,
I went through version -08 of the headers-boilerplates document and
attempted to put together all of the possible combinations of text for
the Status of This Memo. I believe the attached file is a complete
list of these possibilities, based on the text in Section 3.
Please note
16 matches
Mail list logo
