Centralized Replication for Active-Active BUM Traffic
draft-ietf-trill-centralized-replication-13

Document Type Active Internet-Draft (trill WG)
Last updated 2018-02-02 (latest revision 2018-01-25)
Replaces draft-hao-trill-centralized-replication
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Dec 2014 - Submit Active-Active... )
Document shepherd Donald Eastlake
Shepherd write-up Show (last changed 2017-11-11)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
TRILL Working Group                                              W. Hao
INTERNET-DRAFT                                                    Y. Li
Intended Status: Standards Track                    Huawei Technologies
Updates: 6325                                                M. Durrani
                                                                Equinix
                                                               S. Gupta
                                                            IP Infusion
                                                                  A. Qu
                                                               MediaTec
Expires: July 2018                                     January 25, 2018

           Centralized Replication for Active-Active BUM Traffic
              draft-ietf-trill-centralized-replication-13.txt

Abstract

   In TRILL active-active access, an RPF (Reverse Path Forwarding) check
   failure issue may occur when using the pseudo-nickname mechanism
   specified in RFC 7781. This draft describes a solution to resolve
   this RPF check failure issue through centralized replication. All
   ingress RBridges send BUM (Broadcast, Unknown unicast and Multicast)
   traffic to a centralized node with unicast TRILL encapsulation.
   When the centralized node receives the BUM traffic, it decapsulates
   the packets and forwards them to their destination RBridges using
   a distribution tree established as per TRILL base protocol RFC 6325.
   To avoid RPF check failure on a RBridge sitting between the ingress
   RBridge and the centralized replication node, some change in the
   RPF calculation algorithm is required. RPF checks on each RBridge
   MUST be calculated as if the centralized node was the ingress
   RBridge, instead of being calculated using the actual ingress
   RBridge. This document updates RFC 6325.

Status of this Memo

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

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

Hao & Li, et al        Expires July 25, 2018                  [Page 1]
Internet-Draft Centralized replication for BUM traffic    January 2018

   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.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with
   respect to this document. Code Components extracted from this
   document must include Simplified BSD License text as described in
   Section 4.e of the Trust Legal Provisions and are provided without
   warranty as described in the Simplified BSD License.

Table of Contents

   1. Introduction ................................................3
   2. Conventions used in this document............................4
   3. Centralized replication solution overview....................5
   4. Frame duplication from remote RBridge........................6
   5. Local forwarding behavior on ingress RBridge.................7
   6. Loop prevention among RBridges in an edge group..............8
   7. Centralized replication forwarding process...................9
   8. BUM traffic load balancing among multiple centralized nodes..11
   9. Co-existing with the CMT solution........................... 12

Hao & Li, et al         Expires July 25, 2018                 [Page 2]
Internet-Draft Centralized replication for BUM traffic    January 2018

   10. Network upgrade analysis................................... 13
   11. TRILL protocol extensions.................................. 13
      11.1. "R" and "C" Flag in the Nickname Flags APPsub-TLV......13
   12. Security Considerations.................................... 14
   13. IANA Considerations........................................ 15
   14. References ................................................ 15
      14.1. Normative References.................................. 15
      14.2. Informative References................................ 16
Show full document text