RBridges: Campus VLAN and Priority Regions
draft-ietf-trill-rbridge-vlan-mapping-06

The information below is for an old version of the document
Document Type Active Internet-Draft (trill WG)
Last updated 2011-10-28 (latest revision 2011-04-26)
Replaces draft-perlman-trill-rbridge-vlan-mapping
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TRILL Working Group                                        Radia Perlman
INTERNET-DRAFT                                                Intel Labs
Intended status: Proposed Standard                           Dinesh Dutt
                                                           Ayan Banerjee
                                                           Cisco Systems
                                                       Anil Rijhsinghani
                                                           HP Networking
                                                         Donald Eastlake
                                                                  Huawei
Expires: April 27, 2012                                 October 28, 2011

               RBridges: Campus VLAN and Priority Regions
             <draft-ietf-trill-rbridge-vlan-mapping-06.txt>

Abstract

   Within an RBridge campus, the VLAN and priority of TRILL encapsulated
   frames is preserved. However, in some cases it may be desired that
   data VLAN and/or priority be mapped at the boundary between regions
   of such a campus. This document describes an optional RBridge feature
   to provide this function.

Status of This Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Distribution of this document is unlimited. Comments should be sent
   to the TRILL working group mailing list.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

R. Perlman, et al.                                              [Page 1]
INTERNET-DRAFT                       RBridges: VLAN and Priority Regions

Table of Contents

      1. Introduction............................................3
      1.1 RBridge Campus Regions.................................4
      1.2 Terminology............................................5

      2. Internal and Cut Set RBridge Configuration and Mappings.6
      2.1 Multiple Crossings.....................................7
      2.2 Native Frame Considerations............................8
      2.3 More than Two Regions..................................8
      2.4 Mapping Implementation.................................9

      3. End Node Address Learning Between Regions..............11
      4. Cut Set RBridge Attraction of VLANs and Multicast......12
      5. Advertisement of VLAN and Priority Mappings............13

      6. IANA Considerations....................................13
      7. Security Considerations................................13
      8. Normative References...................................14
      9. Informative References.................................14

      Appendix Z: Change Summary and RFC Editor Notes...........15

R. Perlman, et al.                                              [Page 2]
INTERNET-DRAFT                       RBridges: VLAN and Priority Regions

1. Introduction

   The IETF TRILL protocol provides transparent forwarding, with a
   number of additional features, by use of link state routing and
   encapsulation with a hop count as specified in [RFC6325].

   Devices implementing the TRILL protocol are called RBridges. An
   RBridge campus is an area of RBridges and possibly bridges bounded by
   and interconnecting end stations and Layer 3 routers, analogous to a
   customer bridge LAN (which is an area of bridges interconnecting end
   stations, routers, and RBridges). In an RBridge campus, native frames
   (as defined in [RFC6325]), when they arrive at their first or ingress
   RBridge, are encapsulated, routed in encapsulated form via zero or
   more transit RBridges, and finally decapsulated and delivered by
   their egress RBridge or RBridges.

   The ports of RBridges are the same as the ports of IEEE [802.1Q-2005]
   bridges, except as described in [RFC6325], with TRILL being
   implemented above those ports. Such ports provide for the association
   of incoming frames with a particular frame priority and customer
   VLAN. (See Appendix D of [RFC6325].)

   Bridge ports can map frame priorities, a process called "priority
   regeneration" in IEEE 802.1. In addition, some bridge products
   provide a feature to map the customer VLAN of incoming VLAN tagged
   frames, a process of the type called "VLAN ID translation" in IEEE
   802.1.

   Using such port features, it is possible to configure RBridge ports
Show full document text