On Mon, Jun 18, 2012 at 5:04 PM, <[email protected]> wrote: > Catching up ... > > In draft-bl-nvo3-dataplane-requirements-00.txt, the last paragraph > in Section 3.3.1.2. Service QoS identifier says: > > Support for NVE Service CoS SHOULD be provided through a QoS field, > inside the NVO3 overlay header. Examples of service CoS provided > part of the service tag are 802.1p and DE bits in the VLAN and PBB > ISID tags and MPLS EXP bits in the VPN labels. > > Why "inside the NVO3 overlay header"? Earlier in the section, IP DSCP > and Ethernet 802.1p are mentioned as examples of CoS (Class of Service) > indicators and QoS fields - when used between NVEs, these (obviously) > belong in the outer IP and outer Ethernet headers respectively. > > What's the rationale for an additional QoS field in the overlay header?
I don't see a need for it either. Anoop _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
