Eric, > Thomas, > > We really cannot say -
> " VLANs are a well understood construct in the networking > industry, providing an L2 service via a physical network in > which tenant forwarding information is part of the [physical] > network infrastructure." > - because this is not anything that VLANs are "well understood" to > do. The term "tenant" is alien in the context of VLANs, and the > (tenant associated) information is not part of the physical network, > but is (instead) included as part of the frame-header for Ethernet > frames forwarded in the context of each VLAN. Yep, I messed up on the rewording a bit here. > Perhaps if I knew why you were proposing this change > to the earlier text, I could provide a better formulation? To address Adrian's comment and observation that "in-band" was barely used and arguably didn't need to be in the terminology section... > I think we are trying to do is characterize the way that the L2 > service is provided by VLANs is "in-band" â by which we apparently > mean that the mechanism used for VLANs is to carry identifiers for > virtual networks in the data-frames themselves, as part of the > Ethernet frame-header. Right. And a key difference between "in-band" and overlays is that in the in-band case, the network infrastructure uses those identifiers while making forwarding decisions. With overlays, the identifiers are only used at the edge and not in the forwarding plane (at least not directly -- deep packet inspection muddies this, but is really just an optimization). > This might be part of the changes you indicated you would do to > address Adrian's comment. If that is the case, I would suggest that > the text should be changed to: > "VLANs are a well understood construct in the networking industry, > providing an L2 service to VLAN member end-stations where VLAN > forwarding information is included in the PDU header of each data > PDU." This is better, but would prefer something like: VLANs are a well understood construct in the networking industry, providing an L2 service via a physical network in which tenant forwarding information (i.e., the VLAN ID) is included in the L2 frame header and used by the physical network while making forwarding decisions. (this avoids using "PDU", which the PS document hasn't used...) Thomas
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
