Jeffrey Hutzelman wrote:
while I don't think the document necessarily needs to be changed to
REQUIRE this, I think it would be good if last call announcements
continued to call out normative downrefs, for two reasons:
(1) To make it easier to catch potentially problematic downrefs
(2) To
- Original Message -
From: Sam Hartman [EMAIL PROTECTED]
To: Tom.Petch [EMAIL PROTECTED]
Cc: ietf ietf@ietf.org
Sent: Saturday, February 24, 2007 10:09 PM
Subject: Re: Last Call: draft-klensin-norm-ref (Handling Normative References
for Standards Track Documents) to BCP
My strong
This document has a reasonable goal, but the implementation is objectionable.
The reasonable goal (from the introduction):
This document replaces the hold on normative reference rule with a
note downward normative reference and move on approach for
normative references to
On Wednesday, February 28, 2007 03:56:44 PM -0500 Eric Rosen
[EMAIL PROTECTED] wrote:
In many cases (probably the vast majority) where a document is
advancing despite a downward normative reference, the referenced
document (and the technology described therein) is no less stable
On 2007-02-26 07:51, Eliot Lear wrote:
Sam Hartman wrote:
My strong preference as an individual is to approve this document as
is. I think there's a good split between RFC 3967 and this document.
RFC 3967 will cover informational documents; this document will cover
standards track.
I'm not in
Bill == Bill Fenner [EMAIL PROTECTED] writes:
Bill On 2/24/07, Sam Hartman [EMAIL PROTECTED] wrote:
I think there's a good split between RFC 3967 and this
document. RFC 3967 will cover informational documents; this
document will cover standards track.
Bill I have to
inline
Tom Petch
- Original Message -
From: John C Klensin [EMAIL PROTECTED]
To: Sam Hartman [EMAIL PROTECTED]; Tom.Petch [EMAIL PROTECTED]
Cc: ietf ietf@ietf.org
Sent: Sunday, February 25, 2007 12:00 AM
Subject: Re: Last Call: draft-klensin-norm-ref (Handling Normative References
I'd be happy with this title change. Does anyone object?
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
--On Monday, 26 February, 2007 13:45 -0500 Sam Hartman
[EMAIL PROTECTED] wrote:
I'd be happy with this title change. Does anyone object?
No.
And, while I sympathize with the problem Tom discusses, the
solution lies, IMO, in at least a 2026 replacement and probably
some rethinking of the
I believe that if we follow the authors' suggestion
to proceed rapidly, Tom's concern could be met by
a simple informational note summarizing how to deal
with downrefs in practice. Such a note could be input to
an eventual combined document after some experience,
as John suggests.
Brian
On
On 2/24/07, Sam Hartman [EMAIL PROTECTED] wrote:
I think there's a good split between RFC 3967 and this document.
RFC 3967 will cover informational documents; this document will cover
standards track.
I have to admit that when I was reading this document I was confused
by section 4; I thought
Sam Hartman wrote:
My strong preference as an individual is to approve this document as
is. I think there's a good split between RFC 3967 and this document.
RFC 3967 will cover informational documents; this document will cover
standards track.
I'm not in principle opposed to having one
Tom == Tom Petch [EMAIL PROTECTED] writes:
Tom I have no problem with the underlying idea, in so far as I
Tom understand it, but I do not agree that this I-D is the best
Tom way to achieve it.
Tom I think that my problem is well illustrated by a sentence in
Tom the Abstract
--On Saturday, February 24, 2007 4:09 PM -0500 Sam Hartman
[EMAIL PROTECTED] wrote:
Tom == Tom Petch [EMAIL PROTECTED] writes:
Tom I have no problem with the underlying idea, in so far
as I Tom understand it, but I do not agree that this I-D
is the best Tom way to achieve it.
BCP97 and what revised
BCP97.
Tom Petch
- Original Message -
From: The IESG [EMAIL PROTECTED]
To: IETF-Announce ietf-announce@ietf.org
Sent: Friday, February 16, 2007 5:02 PM
Subject: Last Call: draft-klensin-norm-ref (Handling Normative References for
Standards Track Documents) to BCP
-Original Message-
From: The IESG [mailto:[EMAIL PROTECTED]
Sent: Friday, February 16, 2007 11:02 AM
To: IETF-Announce
Subject: Last Call: draft-klensin-norm-ref (Handling
Normative References for Standards Track Documents) to BCP
The IESG has received a request from
16 matches
Mail list logo
