/
Response to IEEE 802.11 comments on PAR for IEEE P802.1Qcd Response to IEEE 802.11 comments on PAR for IEEE P802.1Qcd

Response to IEEE 802.11 comments on PAR for IEEE P802.1Qcd - PowerPoint Presentation

pasty-toler
pasty-toler . @pasty-toler
Follow
401 views
Uploaded On 2016-07-13

Response to IEEE 802.11 comments on PAR for IEEE P802.1Qcd - PPT Presentation

July 2013 July 2013 Pat Thaler IEEE 8021 DCB task group chair Slide 1 8021Qcd PAR Does IETF provide any similar VLAN tag No VLAN tags are defined in IEEE 8021Q and was fundamental to the initial IEEE 8021Q VLAN tags carry ID: 402663

ieee 802 vlan management 802 ieee management vlan network station july 2013 slide traffic simplifies stations bridges application chair

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "Response to IEEE 802.11 comments on PAR ..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

Response to IEEE 802.11 comments on PAR for IEEE P802.1Qcd

July 2013

July 2013

Pat Thaler, IEEE 802.1 DCB task group chair.

Slide

1Slide2

802.1Qcd

PAR

Does IETF provide any similar VLAN tag?

No, VLAN tags are defined in IEEE 802.1Q and was fundamental to the initial IEEE 802.1Q. VLAN tags carry QoS

information (i.e. priority) and VLAN IDs.

How does VLAN tag simplify management

? The VLAN ID is used to mark traffic as belonging to a Virtual LAN. This amendment simplifies management of end stations (i.e. devices that create and are the destination of traffic, rather than bridging the traffic) by providing a means for the adjacent bridge to tell the end station what VLAN ID to use for a particular application. We already have a similar TLV that indicates the priority to use for a particular application. See IEEE 802.1Q Annex D.2.12.3 (currently published in IEEE 802.1Qaz).In 5.2.b, the last scope sentence is actually a need statement and should be moved to 5.5. Accept, we will move that sentence to the start of 5.5

Slide 2

Pat Thaler, IEEE 802.1 DCB task group chair.

July 2013Slide3

802.1Qcd continued

5C

Slide 6 Please define the scope of “end stations” or provide some examples.

This term is defined in IEEE 802 and used in IEEE 802.1Q.The 5C alternately claims that Qcd

will

simplify network management and end station management – which is it

? It doesn’t say that it simplifies network management – it says management of such networks. The network includes the end station network interfaces and the bridges, even though the term “network management” often is used in industry meaning just management of bridges. Typically, different administrators and management applications are involved in managing end stations and bridges. This presents a challenge for coordinating end stations with the network to which they are attached. DCBX (part of IEEE 802.1Qaz) was created to address this by providing a way for the adjacent bridge to tell an end station things it needed to know about the network configuration.

The Application VLAN ID TLV fills a gap in the information currently covered by DCBX. This simplifies end station management as well as management of the network as a whole.

Slide

3

Pat Thaler, IEEE 802.1 DCB task group chair

July 2013