I do not support adoption of this document.

At its net, this document seems to define an extra header to be used by (all? 
some?) overlay (def? what’s in scope?) protocols, but said header adds no value 
other than extra overhead. This seems problematic on a number of levels, adding 
just an indirection, and a bit flag with a flag define for a timestamp, which 
creates an OAM in itself conflicting potentially with the proposed OAM carried 
(and its timestamp). There is no definition for protocols to carry this extra 
shim, so it is basically floating, and no specifics of what OAMs are carried 
(and what the benefit is on this indirection instead of carrying natively the 
OAM). The draft points to BIER MPLS but not to MPLS, which makes me question 
the scope once again. Perhaps an “Implementation Status” section [RFC 7942] 
will help.

Thanks,

— Carlos.

On Mar 31, 2017, at 11:34 AM, Bocci, Matthew (Nokia - GB) 
<[email protected]<mailto:[email protected]>> wrote:

This email begins a two week poll for adoption of 
draft-ooamdt-rtgwg-ooam-header-03 in the NVO3 working group.

Please review the draft and send any comments to the NVO3 list.
Please also indicate whether you support adoption of the draft as an NVO3 
working group document.

Simultaneously, we are also poling for any IPR that may apply to the draft.

Authors and contributors, are you aware of any IPR that applies to this draft?
If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 
3979, 4879, 3669 and 5378 for more details)?
If you are listed as a document author or contributor, please respond to
this email stating of whether or not you are aware of any relevant
IPR. The response needs to be sent to the NVO3 WG mailing list. The
document will not advance to the next stage until a response
has been received from each author and each contributor.

This poll closes on Friday 14th April 2017.

Regards

Matthew and Sam
_______________________________________________
nvo3 mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/nvo3

_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3

Reply via email to