RE: [EFM] RE: [EFM-OAM] Performance monitoring, installation, trouble shoot ing.
Speaking only for myself...
802.3 defines an Ethernet link, not a network, and Ethernet links have
no intrinsic QoS mechanisms. What 802.1D or IP or anyone else does as
far as prioirty queueing in order to gain access to this link is a
problem thats important to address - but not here.
> -----Original Message-----
> From: Chou, Joey [mailto:joey.chou@xxxxxxxxx]
> Sent: Wednesday, January 23, 2002 6:01 PM
> To: carlosal@xxxxxxxxxxxxxxxxxx; Geoff Thompson
> Cc: bob.barrett@xxxxxxxxxxxxxxx; mattsquire@xxxxxxx;
> stds-802-3-efm-oam@ieee.org; stds-802-3-efm@ieee.org
> Subject: [EFM] RE: [EFM-OAM] Performance monitoring, installation,
> trouble shoot ing.
>
>
>
> Geoff and Carlos,
>
> End-to-end QoS is required, if the IP networks were to
> support the mix of
> real-time (e.g. voice, video) and non-real-time(e.g. data)
> applications. It
> is true that several mechanisms, such as Diffserv, RSVP,
> MPLS, have been
> designed in the upper layers to support QoS. However, the
> true end-to-end
> QoS will not happen until QoS is supported in every network
> segment along
> the path. 802.1D user_priority uses 3 bits in the 802.1Q VLAN
> tag to define
> 8 types of traffic riding in the Ethernet frame.
>
> I thought there should be a need for an OAM requirement to
> support 802.1D
> user_priority bits to prevent voice packets from blocking by
> huge Ethernet
> data packets.
>
> Regards,
>
> Joey Chou
> Intel
>