[mpls] Clarification request on PW types (Manual, 128 FEC, 129 FEC) usage for MPLS-TP

venkatesan mahalingam <venkatflex@gmail.com> Thu, 26 August 2010 09:20 UTC

Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 0EDEF3A6AA6; Thu, 26 Aug 2010 02:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 6p66FqX6xxu3; Thu, 26 Aug 2010 02:20:29 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com []) by core3.amsl.com (Postfix) with ESMTP id 717903A6AA5; Thu, 26 Aug 2010 02:20:29 -0700 (PDT)
Received: by pzk6 with SMTP id 6so665865pzk.31 for <multiple recipients>; Thu, 26 Aug 2010 02:21:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=bGbB2cvR5LDw4PgQKU4f15WXWZAl2Ph7a1Honpsj/aI=; b=c2MeI39CYtPgqdcuzI1znZ3Mf7BQ4feUqbqOSSzJ8x3qLstBWkc2gpliqJLoZYw8gM KPdIfzHs0yLsVgymz5ax9Lvoop5oFnXMJQi9owL24T7Jf0sNLbD25MukpeCA40JwVYgC QVnj3RA8dcwcU3y7XeGpsgOMrbA+Jrqkj4n2k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=a6iIQJK726HlqtmZ6dUCg41A7emLmBZo+gPyVb6zKXBgHKYtlfnk0ZBx5f2cLOkCcV dYxQ6SLlKIBrtspA7Av9KhBn3zEi0AfKQ10Dde6vxAC1NvvhoWd8ndDU8++V+ViwMuPO sstGg0DHb94qbFmuGdRpRAvHG4BqHZponhdQY=
MIME-Version: 1.0
Received: by with SMTP id r2mr8072516wfd.262.1282814462083; Thu, 26 Aug 2010 02:21:02 -0700 (PDT)
Received: by with HTTP; Thu, 26 Aug 2010 02:21:02 -0700 (PDT)
Date: Thu, 26 Aug 2010 14:51:02 +0530
Message-ID: <AANLkTinyCssR3POW-mx=jbs4ALtxzcchAs0gb0AuLdNR@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: pwe3@ietf.org, mpls <mpls@ietf.org>, mpls-tp@ietf.org
Content-Type: multipart/alternative; boundary="000e0cd3291c534492048eb684d6"
Subject: [mpls] Clarification request on PW types (Manual, 128 FEC, 129 FEC) usage for MPLS-TP
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Aug 2010 09:20:31 -0000

As per MPLS-TP identifiers-2 draft, Section 6.  Pseudowire Path Identifiers,
draft mentions that the 129 FEC AII Type-2 fits the requirement of MPLS-TP.

Can we say that other types of PWs (128 FEC, 129 FEC AII Type-1, manual) are
not applicable for MPLS-TP networks?
It looks to me that 129 FEC is always used in signalling for label
distribution using LDP/BGP.
Can we use 129 FEC AII type-2 for static/signalling?
draft-ietf-mpls-tp-on-demand-cv-00 draft, section 2.4.2.  Static Pseudowire
mentions that the 129 FEC AII type-2 can be static PW, Can somebody explain
the configurations expected in RFC-5601 MIB to achieve this static 129 FEC
AII Type-2, Can you please let me know the reason for not having the AGI in
the Static PW Sub-TLV.

What sort of changes update the RFC-5601?

What is the pwOwner expected for PW created for MPLS-TP networks?

For manual PW (by configuring the labels manually) - pwOwner should have the
value *manual*.
For 128 FEC PW (signalling) - pwOwner should have the *pwIdFecSignaling*.
For 129 FEC PW (signalling) - pwOwner should have the value *genFecSignaling

            manual                (1),
            pwIdFecSignaling      (2), -- PW signaling with PW ID FEC
            genFecSignaling       (3), -- Generalized attachment FEC
            l2tpControlProtocol   (4),
            other                 (5)
     MAX-ACCESS    read-create
     STATUS        current
          "This object is set by the operator to indicate the protocol
           responsible for establishing this PW.
           'manual' is used in all cases where no maintenance
           protocol (PW signaling) is used to set up the PW, i.e.,
           configuration of entries in the PW tables including
           PW labels, etc., is done by setting the MIB fields manually.
           'pwIdFecSignaling' is used in case of signaling with the
           Pwid FEC element with LDP signaling.
           'genFecSignaling' is used in case of LDP signaling with
           the generalized FEC.
           'l2tpControlProtocol' indicates the use of the L2TP
           control protocol.
           'other' is used for other types of signaling."
     ::= { pwEntry 3 }

Best Regards,
Venkatesan Mahalingam.