Dear Authors, WG Chairs, et. al,
firstly, many thanks to the Design Team for very good start. Please find my
notes, comments to the document below. Greatly appreciate your kind
consideration.
- Section 2 states "The chosen design should also operate well with ICMP
and in ECMP environments." While I understand ECMP environment and possible
ways to generate entropy value for path selection, I'm bit puzzled by role
of ICMP can play. Is it to suggest use of particular OAM mechanism?
- Section on Telemetry, in my opinion, overlooks value of mechanism that
generates entropy value at the edge instead of generating it at transit
nodes. This mechanism is known in IP/MPLS as Entropy label and being
proposed in BIER encapsulation header as Entropy field. I think that NVO3
header can benefit from allocating the Entropy field. Then, ensuring that
active OAM messages share the same path as data packets would be as simple
as using the same Entropy value. More so, by applying different values
active OAM be able to monitor all available multipaths even if there's no
data traffic.
- I believe that "in band parameters" is misleading and confusing
terminology. Active OAM can be and, in my opinion, must be in-band, i.e.
receive the same forwarding and scheduling treatment as data flow being
monitored.
- Now I'm making assumption that the draft-ietf-nvo3-geneve should be
used to discuss format of NVO3 header proposed by the design team.
- If that is correct, I'm interested to discuss benefit of using O
bit to specify that OAM message follows the NVO3 header vs. define OAM as
one of values of Protocol Type field.
- If the OAM message identified by value of Protocol Type field, then
the O bit can be reused for passive performance measurement
(allocating two
bit-long field would be ideal).
Regards,
Greg
On Thu, Feb 9, 2017 at 9:03 AM, Sam Aldrin <[email protected]> wrote:
> Hello NVo3 WG,
>
> NVo3 Design Team for encap has put in quite a bit of effort to meet,
> discuss and hashout various requirements and issues and coming up with a
> draft on proposed encap. Thanks to all who have participated and made it
> possible.
>
> This document could be found at
> URL: https://www.ietf.org/internet-drafts/draft-dt-nvo3-
> encap-00.txt
> Status: https://datatracker.ietf.org/doc/draft-dt-nvo3-encap/
> Htmlized: https://tools.ietf.org/html/draft-dt-nvo3-encap-00
>
> Kindly go through the document and review thoroughly and provide your
> comments.
> This will enable DT to close any issues or pending gaps.
>
> cheers
> Sam & Matthew
>
> _______________________________________________
> nvo3 mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/nvo3
>
>
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
