datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Dynamic Placement of Multi-Segment Pseudowires
draft-ietf-pwe3-dynamic-ms-pw-22

Document type: Active Internet-Draft (pwe3 WG)
Document stream: IETF
Last updated: 2014-03-25 (latest revision 2014-03-10)
Intended RFC status: Proposed Standard
Other versions: plain text, pdf, html

IETF State: Submitted to IESG for Publication Aug 2012
Consensus: Yes
Document shepherd: Loa Andersson
Shepherd Write-Up: Last changed 2013-10-09

IESG State: RFC Ed Queue
IANA Action State: RFC-Ed-Ack
RFC Editor State: EDIT
Responsible AD: Adrian Farrel
Send notices to: pwe3-chairs@tools.ietf.org, draft-ietf-pwe3-dynamic-ms-pw@tools.ietf.org, loa@pi.nu

Network Working Group                                 Luca Martini (Ed.)
Internet Draft                                        Cisco Systems Inc.
Expires: September 2014
Intended status: Standards Track                     Matthew Bocci (Ed.)
Updates: 6073                                         Florin Balus (Ed.)
                                                          Alcatel-Lucent

                                                          March 10, 2014

             Dynamic Placement of Multi-Segment Pseudowires

                  draft-ietf-pwe3-dynamic-ms-pw-22.txt

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
   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/ietf/1id-abstracts.txt.

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

   This Internet-Draft will expire on September 10, 2014

Abstract

   RFC5254 describes the service provider requirements for extending the
   reach of pseudowires (PW) across multiple Packet Switched Network
   domains. A Multi-Segment PW is defined as a set of two or more
   contiguous PW segments that behave and function as a single point-
   to-point PW. This document describes extensions to the PW control
   protocol to dynamically place the segments of the multi-segment
   pseudowire among a set of Provider Edge (PE) routers. This document
   also updates RFC6073 as follows: it updates the

Martini, et al.                                                 [Page 1]
Internet Draft    draft-ietf-pwe3-dynamic-ms-pw-22.txt    March 10, 2014

    value of the length field of the PW Switching Point PE Sub-TLV Type
   0x06 to 14.

Table of Contents

    1        Introduction  .........................................   3
    1.1      Scope  ................................................   3
    1.2      Specification of Requirements  ........................   3
    1.3      Terminology  ..........................................   3
    1.4      Architecture Overview  ................................   4
    2        Applicability  ........................................   5
    2.1      Changes to Existing PW Signaling  .....................   5
    3        PW Layer 2 Addressing  ................................   6
    3.1      Attachment Circuit Addressing  ........................   6
    3.2      S-PE Addressing  ......................................   7
    4        Dynamic Placement of MS-PWs  ..........................   7
    4.1      Pseudowire Routing Procedures  ........................   8
    4.1.1    AII PW Routing Table Lookup Aggregation Rules  ........   8
    4.1.2    PW Static Route  ......................................   9
    4.1.3    Dynamic Advertisement with BGP  .......................   9
    4.2      LDP Signaling  ........................................  11
    4.2.1    Multiple Alternative Paths in PW Routing  .............  13
    4.2.2    Active/Passive T-PE Election Procedure  ...............  13
    4.2.3    Detailed Signaling Procedures  ........................  14
    5        Failure Handling Procedures  ..........................  15
    5.1      PSN Failures  .........................................  15
    5.2      S-PE Specific Failures  ...............................  16
    5.3      PW Reachability Changes  ..............................  16
    6        Operations and Maintenance (OAM)  .....................  17
    7        Security Considerations  ..............................  17
    8        IANA Considerations  ..................................  18
    8.1      Corrections  ..........................................  18
    8.2      LDP TLV TYPE NAME SPACE  ..............................  18
    8.3      LDP Status Codes  .....................................  19
    8.4      BGP SAFI  .............................................  19
    9        References  ...........................................  19
    9.1      Normative References  .................................  19
    9.2      Informative References  ...............................  20
   10        Contributors  .........................................  20
   11        Acknowledgements  .....................................  21
   12        Author's Addresses  ...................................  21

[include full document text]