1 / 6

Interaction of RBridges and 802 Protocols

This draft provides an analysis of how RBridges relate to various specific work being done in the IEEE 802.1 and 802.3 protocols. It covers topics such as bridges, VLANs, MAC security, discovery, and more.

nbooth
Télécharger la présentation

Interaction of RBridges and 802 Protocols

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interaction of RBridges and 802 Protocols Donald E. Eastlake 3rd 111 Locke Drive, Marlborough, MA 01752 USA Donald.Eastlake@motorola.com IETF 68 Prague

  2. Questions → Draft • Questions have repeatedly been raised as to how RBridges relate to various specific work being done in IEEE 802.1 (and sometimes 802.3) or to “all” the work being done there. • draft-eastlake-trill-802-protocols-00.txt is a first stab at answering some of these questions. It reflects only my opinions. IETF 68 Prague

  3. Comments & Input Requested • Tentatively analysis: An integral part of Rbridges • 802.1D-2004 - Bridges • 802.1Q-2005 - VLANs • Tentatively analysis: Port facilities equally applicable to bridges, routers, hosts, … • 802.1AB-2005 - Discovery • 802.1AE-2005 - MAC Security • 802.1af (Amends 802.1X) MAC Keying IETF 68 Prague

  4. Comments & Input Requested • Tentatively analysis: “Provider” facilities outside of current Rbridge proposal • 802.1ad-2005 (amends 802.1Q) Provider Bridges • 802.1ah (amends 802.1Q) Provider Backbone Bridges • Tentatively analysis: Facility in early stages which should be tracked and supported • 802.1au (amends 802.1Q) Congestion Management (D0.01) IETF 68 Prague

  5. Comments & Input Requested • TBD: Not yet looked at (by me) • 802.1ag (amends 802.1Q) Connectivity Fault Management (D7.1) • There are other things I haven’t looked at yet • Tentative analysis: one of the reasons no on seems to be worrying much about frame size • 802.3as-2006 (amends 802.3) Frame format extensions • Tentative analysis: deprecate in favor of Congestion Notification? • 802.3-2005 PAUSE, etc. IETF 68 Prague

  6. 802.1/802.3 Multicast Block • Multicast Addresses from0180C2000000 → 0180C200000Fare reserved for 802.1 and “media specific protocols” (802.3). Examples: • 0180C2000000 – All Bridges (BPDUs) • 0180C200000E – 802.1AB link layer discovery • RBridges must recognize and process frames to multicast addresses in this block for features they implement and discard those for features they do not implement. IETF 68 Prague

More Related