Authors
I am the document shepherd for this draft. I have reviewed the draft and have
the following comments. In general, the draft is clear and well written – thank
you!. Please treat these comments as you would any other working group last
call comment.
Best regards
Matthew
Section 2.3 EVPN Network OAM
[…]
- the MP2P tunnels used for the transport of unicast traffic between
PEs. EVPN allows for three different models of unicast label
assignment: label per EVI, label per <ESI, Ethernet Tag> and label
per MAC address. In all three models, the label is bound to an EVPN
Unicast FEC.
EVPN Network OAM MUST provide mechanisms to check the operation of
the data plane and verify that operation against the control plane
view.
MB> The formatting here breaks the list up and makes it a bit hard to parse.
Maybe you intend this paragraph to be attached to the list bullet above? If so
then it would be clearer to merge the paragraphs or indent it to be aligned
with the list bullet text.
EVPN network OAM mechanisms MUST provide in-band management
capabilities. As such, OAM messages MUST be encoded so that they
exhibit identical entropy characteristics to data traffic.
MB> I think it would be clearer to refer to in-band monitoring rather than
management to prevent confusion with the DCN of RFC5718. It is the monitoring
that is in-band. I would also suggest adding a clarification with the second
sentence in this paragraph along the lines of “… in order that they share the
same fate.”
_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess
