Re: RFC 2434 term "IESG approval" (Re: IANA Action: Assignment of an IPV6 Hop-by-hop Option)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > 	  We can reasonably delegate a determination of
> > 	definitional adequacy to an individual, but decisions
> > 	about "good" or "bad", or recommendations to use or not
> > 	use something, require community consensus.
> 
> nice, simple language.  seems to capture the distinction -- and the 
> requirement -- nicely.

I disagree.  We normally require a higher standard than community consensus
for technical specifications - we require both consensus and technical soundness.
Technical soundness is determined by both community feedback and IESG review.
I don't see why we should impose a lesser standard for IP options.

Keith

_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]