Pseudowire Preferential Forwarding Status Bit
draft-ietf-pwe3-redundancy-bit-08

The information below is for an old version of the document
Document Type Active Internet-Draft (pwe3 WG)
Last updated 2012-09-14
Replaces draft-muley-dutta-pwe3-redundancy-bit
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Andrew Malis
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Needs a YES. Needs 5 more YES or NO OBJECTION positions to pass.
Responsible AD Stewart Bryant
IESG note Andy Malis (amalis@gmail.com) is the document shepherd.
Send notices to pwe3-chairs@tools.ietf.org, draft-ietf-pwe3-redundancy-bit@tools.ietf.org
Network Working Group                                Praveen Muley, Ed. 
Internet Draft                                   Mustapha Aissaoui, Ed. 
Intended Status: Standards Track                         Alcatel-Lucent 
Expires: March 14, 2013                              September 14, 2012 
                                      
                                      

               Pseudowire Preferential Forwarding Status Bit  
                   draft-ietf-pwe3-redundancy-bit-08.txt 

Abstract 

   This document describes a mechanism for signaling the active and 
   standby status of redundant pseudowires (PWs) between their 
   termination points. A set of redundant PWs is configured between 
   provider edge (PE) nodes in single-segment pseudowire (SS-PW) 
   applications, or between terminating provider edge (T-PE) nodes in 
   multi-segment pseudowire (MS-PW) applications.  

   In order for the PE/T-PE nodes to indicate the preferred PW to use 
   for forwarding PW packets to one another, a new status bit is 
   defined. This bit indicates a preferential forwarding status with a 
   value of Active or Standby for each PW in a redundant set.  

   In addition, a second status bit is defined to allow peer PE nodes 
   to coordinate a switchover operation of the PW. 

 

Status of this Memo 

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

   Internet-Drafts are working documents of the Internet Engineering 
   Task Force (IETF).  Note that other groups may also distribute 
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/. 

   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." 

   This Internet-Draft will expire on March 14, 2013. 

 

 
 
 
Muley et al.            Expires March 14,2013                  [Page 1] 


Internet-Draft PW Preferential Forwarding Status Bit September 14, 2012 
    

Copyright Notice 

   Copyright (c) 2012 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. 

 

Requirements Language 

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
   document are to be interpreted as described in RFC-2119 [1]. 

 

Table of Contents 

    
   1. Introduction...................................................3 
   2. Motivation and Scope...........................................3 
   3. Terminology....................................................6 
   4. PE Architecture................................................8 
   5. Modes of Operation.............................................8 
      5.1. Independent Mode:.........................................9 
      5.2. Master/Slave Mode:.......................................11 
   6. PW State Transition Signaling Procedures......................13 
      6.1. PW Standby Notification Procedures in Independent mode...13 
      6.2. PW Standby notification procedures in Master/Slave mode..14 
         6.2.1. PW State Machine....................................15 
      6.3. Coordination of PW Switchover............................16 
         6.3.1. Procedures at the requesting endpoint...............18 
         6.3.2. Procedures at the receiving endpoint................19 
   7. Status Mapping................................................20 
      7.1. AC Defect State Entry/Exit...............................20 
      7.2. PW Defect State Entry/Exit...............................20 
   8. Applicability and Backward Compatibility......................21 
   9. Security Considerations.......................................21 
 
 
Muley et al.            Expires March 14, 2013                 [Page 2] 


Internet-Draft PW Preferential Forwarding Status Bit September 14, 2012 
    

   10. MIB Considerations...........................................21 
   11. IANA Considerations..........................................22 
Show full document text