Re: Last Call: Textual Conventions for IPv6 Flow Label to ProposedStandard

[Pekka Savola <pekkas@netcore.fi>]

On Fri, 4 Apr 2003, The IESG wrote:
> The IESG has received a request from the Operations & Management 
> Open Area Working Group to consider Textual Conventions for IPv6 
> Flow Label <draft-ietf-ops-ipv6-flowlabel-00.txt> as a Proposed 
> Standard.  

Looks pretty good.

As being uneducated wrt. deeper implications, I would like to see more
explicit justification for FlowLabelOrAny.  I cannot imagine all that many
uses that the extra '-1' for any value might bring, except for the
implementation laziness (just report -1 with everything for read access).  
This might be different if you were aiming towards R/W access.. which in
turn might be a bad idea.

Another minor issue is that one might want to informationally refer to 
draft-ietf-ipv6-flow-label-06.txt.

An editorial nit:

   unneeded compelxity.

==> s/compel/comple/

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings