IETF Logo Mail Archive

Re: [PWE3] Working group last call and IPR call for dynamic Multi-Segment PW drafts

Wen Lin <wlin@juniper.net> Thu, 04 October 2012 03:08 UTC

Return-Path: <wlin@juniper.net>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E49C11E80CC for <pwe3@ietfa.amsl.com>; Wed, 3 Oct 2012 20:08:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.033
X-Spam-Level:
X-Spam-Status: No, score=-5.033 tagged_above=-999 required=5 tests=[AWL=-1.566, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1H9nXcdeFcnz for <pwe3@ietfa.amsl.com>; Wed, 3 Oct 2012 20:08:43 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id 0C27811E80C5 for <pwe3@ietf.org>; Wed, 3 Oct 2012 20:08:40 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUGz9uP01kffAmH/+MidQUlC//HW3bX9+@postini.com; Wed, 03 Oct 2012 20:08:41 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 3 Oct 2012 20:07:56 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Wed, 3 Oct 2012 20:07:55 -0700
Received: from TX2EHSOBE010.bigfish.com (65.55.88.14) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 3 Oct 2012 20:13:24 -0700
Received: from mail97-tx2-R.bigfish.com (10.9.14.253) by TX2EHSOBE010.bigfish.com (10.9.40.30) with Microsoft SMTP Server id 14.1.225.23; Thu, 4 Oct 2012 03:07:54 +0000
Received: from mail97-tx2 (localhost [127.0.0.1]) by mail97-tx2-R.bigfish.com (Postfix) with ESMTP id C10B2320177 for <pwe3@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Thu, 4 Oct 2012 03:07:54 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); (null); H:BL2PRD0510HT003.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -22
X-BigFish: PS-22(zzbb2dI98dI9371I542M1432I4015Iac02pzz1202h1d1ah1d2ahzz8275ch1033IL8275dhz2dh2a8h668h839h944hd25hf0ah107ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1155h)
Received: from mail97-tx2 (localhost.localdomain [127.0.0.1]) by mail97-tx2 (MessageSwitch) id 1349320072957218_24257; Thu, 4 Oct 2012 03:07:52 +0000 (UTC)
Received: from TX2EHSMHS037.bigfish.com (unknown [10.9.14.252]) by mail97-tx2.bigfish.com (Postfix) with ESMTP id DE04240046; Thu, 4 Oct 2012 03:07:52 +0000 (UTC)
Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS037.bigfish.com (10.9.99.137) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 4 Oct 2012 03:07:51 +0000
Received: from BL2PRD0510MB363.namprd05.prod.outlook.com ([169.254.3.251]) by BL2PRD0510HT003.namprd05.prod.outlook.com ([10.255.100.38]) with mapi id 14.16.0207.009; Thu, 4 Oct 2012 03:07:51 +0000
From: Wen Lin <wlin@juniper.net>
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: [PWE3] Working group last call and IPR call for dynamic Multi-Segment PW drafts
Thread-Index: AQHNoH/YSg98fJgGfka9pFPwiC9egJeoZMxA
Date: Thu, 04 Oct 2012 03:07:46 +0000
Message-ID: <BE246B4FBFE3B744B52CD1281D1E552B05EDE0@BL2PRD0510MB363.namprd05.prod.outlook.com>
References: <DF7F294AF4153D498141CBEFADB17704C7EBF0A08E@EMBX01-WF.jnpr.net> <CC906F1A.359DF%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <CC906F1A.359DF%matthew.bocci@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%ALCATEL-LUCENT.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Subject: Re: [PWE3] Working group last call and IPR call for dynamic Multi-Segment PW drafts
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2012 03:08:44 -0000

Hi Matthew,

Thank you for the reply.  

On the T-PE, the MP-BGP advertises this MS-PW NLRI for the VPWS instance and the layer 2 VPN. A MS-PW may go across different ASes.  The route target serves as a VPN identifier and helps to control the route distribution.   

Also we shall not exclude using the same MS-PW NRLI for the auto-discovery of S-PE or T-PE by using the type 2 AII. 
We shall also not exclude using the same NLRI for the VPLS. The route target will help us identify the VPLS domain that the VSI belongs to and helps us build different topologies for the PW. 


Thanks,
Wen


-----Original Message-----
From: Bocci, Matthew (Matthew) [mailto:matthew.bocci@alcatel-lucent.com] 
Sent: Tuesday, October 02, 2012 5:25 AM
To: Wen Lin; pwe3@ietf.org
Subject: Re: [PWE3] Working group last call and IPR call for dynamic Multi-Segment PW drafts

Wen,

Thanks for your comment. I am not sure why sending or processing a route target would be mandatory in the case of MS-PW routing. This is somewhat different from the auto-discovery case described in RFC6074. In MS-PW routing, you know a-priori the PEs that can participate in MS-PW routing and can terminate MS-PWs, the set of PSN tunnel between T-Pes/S-Pes, and the T-LDP next-hop.

Regards

Matthew   

On 05/09/2012 20:40, "Wen Lin" <wlin@juniper.net> wrote:

>When BGP is used for advertising PW address information, I think we 
>shall specify in the section 6.1.3 that it MUST have one or more route 
>targets associated with it since the NRLI is for L2VPN with a an AFI 
>equals to L2VPN(25).
>
>Thanks,
>Wen
>
>
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www.ietf.org/mailman/listinfo/pwe3

v2.29.0 | Report a Bug | By Email | System Status