Note: This ballot was opened for revision 02 and is now closed.
Summary: Has enough positions to pass.
Comment (2011-07-13) 
There is no mention of the fact that individual nodes in a network are free to
implement different algorithms without impacting the interoperability or
function of the network.
Comment (2011-07-14)
Maybe add (e.g., by using IPsec between the two tunnel end-points) to the end
of the 2nd sentence in the security considerations. Just to provide an example
of how it might be done.
Comment (2011-07-13)
A reference to draft-ietf-mpls-entropy-label-00 would seem appropriate since
they seek to achieve the same though at different layers.
Comment (2011-07-11)
I agree with the DISCUSS from Pete Resnick that this seems like a Standards
Track document, not a BCP.
Comment (2011-07-11)
I found this document clear and hope it has the impact the group intends.
I support Pete's discuss though - why did the group choose BCP as the intended
status for this document?
datatracker.ietf.org