Re: [aqm] I-D Action: draft-ietf-aqm-ecn-benefits-04.txt

[Mirja Kühlewind <[e-mail]>]

Hi Wes,

the concern I have is that, even if no normative language is used (which is correct), people might still take this as a IETF recommendation and therefore I think we should review it carefully. However, as no normative language is used, people might not review this document sufficiently… Definitely good to mention this to the IESG explicitly!

Mirja


> Am 12.06.2015 um 17:29 schrieb Wesley Eddy <[e-mail]>:
> 
> On 6/12/2015 8:46 AM, [e-mail] wrote:
>> Since we are already in WGLC, the WG Chairs probably will need to decide
>> the scope - if this is changed, I expect will anyway require a new WGLC. 
>> Hopefully the new ID will help.
> 
> 
> Here are my thoughts, with chair hat on.
> 
> It's an Informational document (i.e. not Standards Track or BCP).  It
> does have some advice about how not to break ECN, but it's not
> altering or changing any previous standards or BCPs about how devices,
> hosts, or applications behave.
> 
> I think it correctly avoids using the 2119 capitalized words (SHOULD,
> MUST, etc.).  There are some non-capitalized "must" and "should" words
> in section 5 when going through the high-level list of prerequisites
> for successful use of ECN, and in my opinion, this is one of the more
> useful parts of the document to summarize and bring the advice together.
> 
> There's definitely a valid criticism that it isn't particularly
> specific about some details in this guidance, but I think that's
> probably desirable, as some are still being worked out, and would
> ultimately go into Standards Track and BCP documents from TSVWG or
> some other working group.
> 
> I think as the AQM working group, the level of detail and strength
> of recommendations made in -04 are pretty much on the mark for what
> we should say.
> 
> Certainly people should let us know during this Last Call if they
> feel otherwise.  It can be something we explicitly ask the AD to
> confirm during their review too.
> 
> -- 
> Wes Eddy
> MTI Systems