Packet Pseudowire Encapsulation over an MPLS PSN
draft-ietf-pwe3-packet-pw-03

The information below is for an old version of the document
Document Type Active Internet-Draft (pwe3 WG)
Last updated 2012-04-10 (latest revision 2012-01-28)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Matthew Bocci
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Responsible AD Adrian Farrel
IESG note Matthew Bocci (matthew.bocci@alcatel-lucent.com) is the document shepherd.
Send notices to pwe3-chairs@tools.ietf.org, draft-ietf-pwe3-packet-pw@tools.ietf.org
Network Working Group                                     S. Bryant, Ed.
Internet-Draft                                                L. Martini
Intended status: Standards Track                              G. Swallow
Expires: July 31, 2012                                     Cisco Systems
                                                                A. Malis
                                                  Verizon Communications
                                                        January 28, 2012

            Packet Pseudowire Encapsulation over an MPLS PSN
                    draft-ietf-pwe3-packet-pw-03.txt

Abstract

   This document describes a pseudowire mechanism that is used to
   transport a packet service over an MPLS PSN is the case where the
   client Label Switching Router (LSR) and the server Provider Edge
   equipments are co-resident in the same equipment.  This pseudowire
   mechanism may be used to carry all of the required layer 2 and layer
   3 protocols between the pair of client LSRs.

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 RFC2119 [RFC2119].

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 July 31, 2012.

Copyright Notice

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

Bryant, et al.            Expires July 31, 2012                 [Page 1]
Internet-Draft                  Packet PW                   January 2012

   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.  Network Reference Model  . . . . . . . . . . . . . . . . . . .  4
   3.  Client Network Layer Model . . . . . . . . . . . . . . . . . .  4
   4.  Forwarding Model . . . . . . . . . . . . . . . . . . . . . . .  5
   5.  Packet PW Encapsulation  . . . . . . . . . . . . . . . . . . .  6
   6.  Ethernet Functional Restrictions . . . . . . . . . . . . . . .  8
   7.  Congestion Considerations  . . . . . . . . . . . . . . . . . .  8
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  8
   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  9
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     11.1.  Normative References  . . . . . . . . . . . . . . . . . .  9
     11.2.  Informative References  . . . . . . . . . . . . . . . . .  9
   Appendix A.  Encapsulation Approaches Considered . . . . . . . . . 10
     A.1.   A Protocol Identifier in the Control Word . . . . . . . . 11
     A.2.   PID Label . . . . . . . . . . . . . . . . . . . . . . . . 11
     A.3.   Parallel PWs  . . . . . . . . . . . . . . . . . . . . . . 12
     A.4.   Virtual Ethernet  . . . . . . . . . . . . . . . . . . . . 13
     A.5.   Recommended Encapsulation . . . . . . . . . . . . . . . . 13
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14

Bryant, et al.            Expires July 31, 2012                 [Page 2]
Internet-Draft                  Packet PW                   January 2012

1.  Introduction

   There is a need to provide a method of carrying a packet service over
   an MPLS PSN in a way that provides isolation between the two
   networks.  The server MPLS network may be an MPLS network or a
   network conforming to the MPLS Transport Profile (MPLS-TP) [RFC5317].
   The client may also be either an MPLS network or a network conforming
   to the MPLS-TP.  Considerations regarding the use of an MPLS network
   as a server for an MPLS-TP network are outside the scope of this
   document.
Show full document text