
From zhangmingui@huawei.com  Thu Aug  1 00:56:49 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31D2021F9A57; Thu,  1 Aug 2013 00:56:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IFsJd2hz14eY; Thu,  1 Aug 2013 00:56:45 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5EEE421F8E8E; Thu,  1 Aug 2013 00:56:44 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AVQ01738; Thu, 01 Aug 2013 07:56:42 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 1 Aug 2013 08:56:25 +0100
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 1 Aug 2013 08:56:37 +0100
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.110]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.01.0323.007; Thu, 1 Aug 2013 15:56:26 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: RE: [PWE3] Updated agenda for Thursday
Thread-Topic: [PWE3] Updated agenda for Thursday
Thread-Index: AQHOjTGYD7ZCFG76WUOVjX9mla0rKpl/9cmQ
Date: Thu, 1 Aug 2013 07:56:25 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7335CA8DB@nkgeml508-mbx.china.huawei.com>
References: <CAK+d4xtm9zTVGPubdhspDWLZJ+to3P6fKs9S5orcKTom9ymr2Q@mail.gmail.com>
In-Reply-To: <CAK+d4xtm9zTVGPubdhspDWLZJ+to3P6fKs9S5orcKTom9ymr2Q@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "l3vpn@ietf.org" <l3vpn@ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 07:56:49 -0000

Dear All,

Apologize that I am unable to be in Berlin to make the presentations due to=
 visa issues. But our slides are still available online.=20
Please read them and review the drafts. Comments are welcome.

ICCP Application TLVs for VPN Route Label Sharing
http://tools.ietf.org/agenda/87/slides/slides-87-pwe3-1.pdf
http://www.ietf.org/id/draft-zhang-pwe3-iccp-label-sharing-00.txt
Also,
Label Sharing for Fast PE Protection
http://tools.ietf.org/agenda/87/slides/slides-87-l3vpn-0.pdf
http://www.ietf.org/id/draft-zhang-l3vpn-label-sharing-00.txt

Many thanks!
Mingui

>-----Original Message-----
>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
>Andrew G. Malis
>Sent: Tuesday, July 30, 2013 10:29 PM
>To: pwe3@ietf.org
>Subject: [PWE3] Updated agenda for Thursday
>
>There seems to be a bug in the IETF tools that is preventing us from uploa=
ding a
>revised agenda for Thursday. Meanwhile, I've included it below. All slides=
 have
>been received, thanks to the presenters!!!!
>
>Cheers,
>Andy
>
>---------
>
>*****************************************************************
>*****
>IETF 87 PWE3 - Thursday, July 12, 2013 - 17:00 - 18:30  Potsdam 3 (55/90 m=
in
>allocated)
>*****************************************************************
>*****
>Chairs: Matthew Bocci and Andy Malis
>Secretary: David Sinicrope
>(x =3D slide sets NOT received as of July 30 16:30 Central Europe Time)
>
>1. 15 min - Agenda bash, WG Agenda and Status - Andy MALIS and Matthew
>BOCCI
>
>2. 10 min - PW Endpoint Fast Failure Protection - Yimin SHEN
>http://www.ietf.org/id/draft-shen-pwe3-endpoint-fast-protection-04.txt
>Objectives: To present the updates in the new rev, and pursue acceptance a=
s a
>WG draft.
>
>3. 10 min - Dynamic Placement of Multi Segment Pseudowires - Loa ANDERSSON
>http://www.ietf.org/id/draft-ietf-pwe3-dynamic-ms-pw-17.txt
>Objectives: To present an update on the draft and explain how a non-wg
>document shepherd guides a standards track wg document into and through
>IESG review and RFC Editor editing.
>
>4. 10 min - ICCP Application TLVs for VPN Route Label Sharing - Mingui ZHA=
NG
>http://www.ietf.org/id/draft-zhang-pwe3-iccp-label-sharing-00.txt
>Objectives:  Need direction from the WG on the draft.
>Note: This draft depends on another draft: Label Sharing for Fast PE Prote=
ction
>http://www.ietf.org/id/draft-zhang-l3vpn-label-sharing-00.txt
>
>5. 5 min - Keyed IPv6 Tunnel - Giles HERON
>http://www.ietf.org/id/draft-mkonstan-keyed-ip-tunnel-00
>Objective: Notify the WG of the draft's existence and intent to address it=
 in
>L2TPEXT (i.e., heads up)
>
>6. 5 min - Liaison statement on clarifying Point to Multi Point (P2MP)
>combinations (to IETF PWE3 and MPLS WGs) - David SINICROPE
>https://datatracker.ietf.org/documents/LIAISON/liaison-2013-07-23-itu-t-sg=
-15-
>mpls-liaison-statement-on-clarifying-point-to-multi-point-p2mp-combination=
s-to-
>ietf-pwe3-and-mpls-wgs-attachment-1.pdf
>Objective: Explain request from the ITU-T SG15 and note intention to reply
>
>
>
>*****************************************************************
>*****
>Overflow (Will be presented if time permits.)
>*****************************************************************
>*****
>
>xx. - None currently
>
>*****************************************************************
>*****
>REMOTE INFORMATION FOR THE PWE3 SESSION(S)
>*****************************************************************
>*****
>Remote Participation Info:
>http://www.ietf.org/meeting/87/remote-participation.html
>- No WebEx
>- Audio will be on: http://ietf87streaming.dnsalias.net/ietf/ietf876.m3u
>- Jabber room is "pwe3"
>


From xuxiaohu@huawei.com  Thu Aug  1 01:48:25 2013
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1875721F91F4; Thu,  1 Aug 2013 01:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.35
X-Spam-Level: 
X-Spam-Status: No, score=-2.35 tagged_above=-999 required=5 tests=[AWL=-0.554,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Kozpqnw2qWD; Thu,  1 Aug 2013 01:48:20 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9200D21F9C91; Thu,  1 Aug 2013 01:48:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATZ54247; Thu, 01 Aug 2013 08:48:10 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 1 Aug 2013 09:47:53 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 1 Aug 2013 09:48:05 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.175]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Thu, 1 Aug 2013 16:47:59 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "nvo3@ietf.org" <nvo3@ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>
Subject: re: About gap analysis on L3VPN [RFC4365]
Thread-Topic: About gap analysis on L3VPN [RFC4365]
Thread-Index: AQHOjfqR4+7pITNBRkuTXoDlEf8XapmAB9SM
Date: Thu, 1 Aug 2013 08:47:59 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DAE27@NKGEML512-MBS.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DABBC@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DABBC@NKGEML512-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.147.13]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 08:48:25 -0000

SGkgYWxsLA0KDQpJJ20gZ2xhZCB0byBzZWUgdGhhdCB0aGlzIGlzc3VlIGlzIG1lbnRpb25lZCBp
biB0aGUgTlZvMyBjaGFpcnMnIHNsaWRlcyBhcyB3ZWxsIChpLmUuLCBzb21lIHJlZmVyZW5jZXMg
dG8gTDNWUE4gdGVjaG5vbG9neS1iYXNlZCBEQyBWUE4gYXBwcm9hY2hlcyBhcmUgdXNlZnVsKS4g
IFVuZm9ydHVuYXRlbHksIHRoaXMgaXNzdWUgaXMgbm90IGRpc2N1c3NlZCBmdXJ0aGVyIGFmdGVy
IHRoZSBzdXJ2ZXkgb2YgYWRvcHRpb24gb2YgTlZHUkUgYW5kIFZYTEFOIGRyYWZ0cy4gTXkgZG91
YnQgaXMgaW4gd2hpY2ggV0cgdGhlIEwzVlBOIHRlY2hub2xvZ3ktYmFzZWQgREMgVlBOIGRyYWZ0
cyBzaG91bGQgYmUgcHVyc3VlZCAoTDNWUE4gV0cgb3IgTlZvMyBXRz8pLg0KDQpCZXN0IHJlZ2Fy
ZHMsDQpYaWFvaHUNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
t6K8/sjLOiBsM3Zwbi1ib3VuY2VzQGlldGYub3JnIFtsM3Zwbi1ib3VuY2VzQGlldGYub3JnXSC0
+rHtIFh1eGlhb2h1IFt4dXhpYW9odUBodWF3ZWkuY29tXQ0Kt6LLzcqxvOQ6IDIwMTPE6jfUwjMx
yNUgMjI6NDMNCrW9OiBudm8zQGlldGYub3JnOyBsM3ZwbkBpZXRmLm9yZw0K1vfM4jogQWJvdXQg
Z2FwIGFuYWx5c2lzIG9uIEwzVlBOIFtSRkM0MzY1XQ0KDQpIaSBhbGwsDQoNCkkgbm90aWNlZCB0
aGF0IEwzVlBOIFtSRkM0MzY1XSBpcyBsaXN0ZWQgYXMgb25lIG9mIHRoZSBjYW5kaWRhdGEgdGVj
aG5vbG9naWVzIGluIHRoZSBOVm8zIGdhcCBhbmFseXNpcyBkb2MuIEhvd2V2ZXIsIElNSE8sIHRo
ZSBjdXJyZW50IG1lY2hhbmlzbSBkZWZpbmVkIGluIFJGQzQzNjUgYWxvbmUgY291bGRuJ3Qgc3Vw
cG9ydCBWTSBtb2JpbGl0eSB3aGljaCBpcyBvbmUgb2YgdGhlIGJhc2ljIHJlcXVpcmVtZW50cyBv
ZiBEQyBWUE4uIEhlbmNlLCBJIGJlbGlldmUgaXQncyBtdWNoIHdvcnRod2hpbGUgdG8gaGF2ZSBh
biBpbmZvcm1hdGlvbmFsIGRyYWZ0IGRlc2NyaWJpbmcgaG93IHRvIHJldXNlIHRoZSBMM1ZQTiBt
ZWNoYW5pc20gZm9yIERDIFZQTiBiZWZvcmUgcGVyZm9ybWluZyBnYXAgYW5hbHlzaXMgb24gdGhl
IEwzVlBOIHRlY2hub2xvZ3kuDQoNCkJlc3QgcmVnYXJkcywNClhpYW9odQ==

From ietf@meetecho.com  Thu Aug  1 02:07:16 2013
Return-Path: <ietf@meetecho.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0ED421F9F5E for <l3vpn@ietfa.amsl.com>; Thu,  1 Aug 2013 02:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.753
X-Spam-Level: 
X-Spam-Status: No, score=0.753 tagged_above=-999 required=5 tests=[AWL=-0.617,  BAYES_05=-1.11, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sU-K8c1QlJVo for <l3vpn@ietfa.amsl.com>; Thu,  1 Aug 2013 02:07:09 -0700 (PDT)
Received: from smtpdg5.aruba.it (smtpdg223.aruba.it [62.149.158.223]) by ietfa.amsl.com (Postfix) with ESMTP id 576F321F9ADD for <l3vpn@ietf.org>; Thu,  1 Aug 2013 02:06:37 -0700 (PDT)
Received: from dell-tcastaldi ([130.129.65.11]) by smtpcmd02.ad.aruba.it with bizsmtp id 7M6c1m0180EaGCq01M6d2Z; Thu, 01 Aug 2013 11:06:37 +0200
Date: Thu, 1 Aug 2013 11:06:34 +0200 (CEST)
From: Meetecho Team <ietf@meetecho.com>
To: l3vpn@ietf.org
Message-ID: <958829171.19.1375347994930.JavaMail.tcastaldi@dell-tcastaldi>
Subject: L3VPN session recording available
MIME-Version: 1.0
Content-Type: multipart/mixed;  boundary="----=_Part_18_1414250481.1375347994928"
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 09:07:16 -0000

------=_Part_18_1414250481.1375347994928
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear all,

the full recording (synchronized video, audio, slides and jabber room) of the 
L3VPN WG session at IETF 87 is available at the following URL:
http://ietf87.conf.meetecho.com/index.php/Recorded_Sessions#L3VPN

For the chair(s): please feel free to put the link to the recording in the minutes,
if you think this might be useful.

Cheers,
the Meetecho Team


This email has been automatically generated by The Meetecho Conferencing System


------=_Part_18_1414250481.1375347994928--

From kireeti.kompella@gmail.com  Fri Aug  2 10:22:57 2013
Return-Path: <kireeti.kompella@gmail.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEFF411E80E7; Fri,  2 Aug 2013 10:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.853
X-Spam-Level: 
X-Spam-Status: No, score=-0.853 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZCZUbMK-l4qz; Fri,  2 Aug 2013 10:22:57 -0700 (PDT)
Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 465AD11E80EE; Fri,  2 Aug 2013 10:22:57 -0700 (PDT)
Received: by mail-yh0-f45.google.com with SMTP id i72so432126yha.32 for <multiple recipients>; Fri, 02 Aug 2013 10:22:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=LhAJQ3TUiJhymKj8FVrfIAE49UteZbXEoDCbnEvQu0w=; b=tvw1UIRTcdSNywG/H+Rz/sjDNnQTpqfym/AwtC2krrrR7xNAUYqnWhgm8I9vIJJvAQ YgUGaoKdcwFETKOJ69NAflCLtabqllRvIH2DMBgMtdclSjlKkTZaYQbALLptZVxlCkx7 +ecq5F5qiAp9bIax8i6YxwSaCAr0FJxqLr5ZBwcocT9wOZODvgTvCyyoWVBYsGGOzo4+ woL2HxtV5uK3baxEnd7iD8DZxXydrtakkrQIU20ANiOlqyq3wfq/ex4RqpHJYJ+jeNoV +cpqwNYYe9EHlXwxJuwnVHARcSK+znlOTl2QJBgZpe8ImeaYlx20SDOymMAd+cKOHvq2 /mSQ==
X-Received: by 10.236.17.165 with SMTP id j25mr4760011yhj.89.1375464171497; Fri, 02 Aug 2013 10:22:51 -0700 (PDT)
Received: from [10.118.72.206] (mobile-166-147-108-141.mycingular.net. [166.147.108.141]) by mx.google.com with ESMTPSA id j63sm13377475yhh.17.2013.08.02.10.22.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 10:22:50 -0700 (PDT)
References: <EB9B93801780FD4CA165E0FBCB3C3E672AE93EF8@SJEXCHMB09.corp.ad.broadcom.com> <2691CE0099834E4A9C5044EEC662BB9D4527F3FB@dfweml509-mbx.china.huawei.com> <CAOA2mbyafkhFe-_Tgn_Q+sW+CHDVsQzVe-G3ZwB8UUuWjCrHRg@mail.gmail.com>
In-Reply-To: <CAOA2mbyafkhFe-_Tgn_Q+sW+CHDVsQzVe-G3ZwB8UUuWjCrHRg@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <B719C606-D41E-4FEB-988E-1F8B40F59A2F@gmail.com>
X-Mailer: iPhone Mail (10B329)
From: Kireeti Kompella <kireeti.kompella@gmail.com>
Subject: Re: [nvo3] The possibility of using global MPLS labels as VNIs ... for l3vpn
Date: Fri, 2 Aug 2013 19:22:41 +0200
To: Aldrin Isaac <aldrin.isaac@gmail.com>
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, L3VPN <l3vpn@ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 17:22:57 -0000

Hi Aldrin,

On Aug 2, 2013, at 15:24, Aldrin Isaac <aldrin.isaac@gmail.com> wrote:

> Local ID is useful to key into any action or context versus only into cont=
ext that represents a flat tenant network. =20

Great point!  Hadn't thought of it this way ...

> This can be leveraged by an SDN controller or via distributed provisioning=
.  If standards produce a one trick pony than proprietary complexity will cr=
eep in.

I hope folks get this!!!

Cheers,
Kireeti


From swallow@cisco.com  Fri Aug  2 13:05:57 2013
Return-Path: <swallow@cisco.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1780311E8113; Fri,  2 Aug 2013 13:05:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.998
X-Spam-Level: 
X-Spam-Status: No, score=-109.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wrTmxeug36PJ; Fri,  2 Aug 2013 13:05:50 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 6467711E80E7; Fri,  2 Aug 2013 13:05:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=24503; q=dns/txt; s=iport; t=1375473950; x=1376683550; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=qGd3nN2+zVlvai4ZS8KJb3qeI13OCodUflaU2mP4y64=; b=S47jgeQWMK9LoVg5HvsTB22X206tLzU0ADBIPSASOQD/6M52FdwREeME Ve+qsrYwiK72/+cbIgvUKWq3G6aV+cHXkBsMqNFqk84tevJm7fmjQIc4K grVE++e0tY2uIcrJEMp2PhwwR3guEWOnlEWQ1L8JeR8CA77yuVffhQETA U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AogFAEQQ/FGtJXHA/2dsb2JhbABagkJENVC/DIEeFnSCJAEBAQECAQEBASpBCwUNAQgRAQIBAQELFgcoBgsUAwYIAgQBDQUIh3YDCQYMsB0NiFoBAwaNIYEpgRcgDQQGAYMZdAOVdo4QhSeDF4FxOQ
X-IronPort-AV: E=Sophos;i="4.89,803,1367971200";  d="scan'208,217";a="242929160"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-6.cisco.com with ESMTP; 02 Aug 2013 20:05:47 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r72K5kdN002921 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 Aug 2013 20:05:46 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.159]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Fri, 2 Aug 2013 15:05:45 -0500
From: "George Swallow (swallow)" <swallow@cisco.com>
To: Lucy yong <lucy.yong@huawei.com>, "Luyuan Fang (lufang)" <lufang@cisco.com>, Aldrin Isaac <aldrin.isaac@gmail.com>, Kireeti Kompella <kireeti.kompella@gmail.com>
Subject: Re: [nvo3] The possibility of using global MPLS labels as VNIs ... for l3vpn
Thread-Topic: [nvo3] The possibility of using global MPLS labels as VNIs ... for l3vpn
Thread-Index: AQHOj7uslJcwB7cuXUyZbndRbqLXWQ==
Date: Fri, 2 Aug 2013 20:05:45 +0000
Message-ID: <2FE467D3673DCE409A84D67EC2F607BB13FAB14D@xmb-rcd-x10.cisco.com>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D4527E309@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.0.121105
x-originating-ip: [10.61.98.27]
Content-Type: multipart/alternative; boundary="_000_2FE467D3673DCE409A84D67EC2F607BB13FAB14Dxmbrcdx10ciscoc_"
MIME-Version: 1.0
Cc: L3VPN <l3vpn@ietf.org>, Yakov Rekhter <yakov@juniper.net>, "nvo3@ietf.org" <nvo3@ietf.org>, "thomas.morin@orange.com" <thomas.morin@orange.com>, "UTTARO, JAMES" <ju1738@att.com>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 20:05:57 -0000

--_000_2FE467D3673DCE409A84D67EC2F607BB13FAB14Dxmbrcdx10ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Lucy -

Some form of Global ID might be useful to help organize the SDN Controller,=
 but there is no point in putting it in the data plane.

George

From: Lucy yong <lucy.yong@huawei.com<mailto:lucy.yong@huawei.com>>
Date: Tuesday, July 23, 2013 12:28 PM
To: "Luyuan Fang (lufang)" <lufang@cisco.com<mailto:lufang@cisco.com>>, Ald=
rin Isaac <aldrin.isaac@gmail.com<mailto:aldrin.isaac@gmail.com>>, Kireeti =
Kompella <kireeti.kompella@gmail.com<mailto:kireeti.kompella@gmail.com>>
Cc: L3VPN <l3vpn@ietf.org<mailto:l3vpn@ietf.org>>, Yakov Rekhter <yakov@jun=
iper.net<mailto:yakov@juniper.net>>, "nvo3@ietf.org<mailto:nvo3@ietf.org>" =
<nvo3@ietf.org<mailto:nvo3@ietf.org>>, "thomas.morin@orange.com<mailto:thom=
as.morin@orange.com>" <thomas.morin@orange.com<mailto:thomas.morin@orange.c=
om>>, "UTTARO, JAMES" <ju1738@att.com<mailto:ju1738@att.com>>
Subject: RE: [nvo3] The possibility of using global MPLS labels as VNIs ...=
 for l3vpn

In distributed control plane approach, we have strong consensus that local =
ID is the way to go.

Like to hear more the people opinions about: in SDN approach, will global I=
D and local ID are equally good (just mater choice) or one is better than o=
ther?

Lucy

From: Luyuan Fang (lufang) [mailto:lufang@cisco.com]
Sent: Tuesday, July 23, 2013 11:06 AM
To: Lucy yong; Aldrin Isaac; Kireeti Kompella
Cc: L3VPN; Yakov Rekhter; nvo3@ietf.org<mailto:nvo3@ietf.org>; Xuxiaohu; th=
omas.morin@orange.com<mailto:thomas.morin@orange.com>; UTTARO, JAMES
Subject: Re: [nvo3] The possibility of using global MPLS labels as VNIs ...=
 for l3vpn

You choose the ID type: global or local.
You choose the control paradigm, SDN, dynamic control plane, or hybrid.

The two decisions are independent.

My personal preferences: SDN with local ID.

Luyuan

From: Lucy yong <lucy.yong@huawei.com<mailto:lucy.yong@huawei.com>>
Date: Tuesday, July 23, 2013 11:58 AM
To: Luyuan Fang <lufang@cisco.com<mailto:lufang@cisco.com>>, Aldrin Isaac <=
aldrin.isaac@gmail.com<mailto:aldrin.isaac@gmail.com>>, Kireeti Kompella <k=
ireeti.kompella@gmail.com<mailto:kireeti.kompella@gmail.com>>
Cc: L3VPN <l3vpn@ietf.org<mailto:l3vpn@ietf.org>>, Yakov Rekhter <yakov@jun=
iper.net<mailto:yakov@juniper.net>>, "nvo3@ietf.org<mailto:nvo3@ietf.org>" =
<nvo3@ietf.org<mailto:nvo3@ietf.org>>, Xuxiaohu <xuxiaohu@huawei.com<mailto=
:xuxiaohu@huawei.com>>, "thomas.morin@orange.com<mailto:thomas.morin@orange=
.com>" <thomas.morin@orange.com<mailto:thomas.morin@orange.com>>, "UTTARO, =
JAMES" <ju1738@att.com<mailto:ju1738@att.com>>
Subject: RE: [nvo3] The possibility of using global MPLS labels as VNIs ...=
 for l3vpn



As I see, using SDN approach or distributed control plane, and using global=
 or local ID are two orthogonal questions.
[Lucy] then, the question to be asked is which usage makes sense in the SDN=
 approach,  global ID or local ID? IMHO: they are related.

Lucy

> is distributed architecture better than centralized architecture for VPN =
or virtual network overlay?
No necessarily.

Luyuan
From: Lucy yong <lucy.yong@huawei.com<mailto:lucy.yong@huawei.com>>
Date: Tuesday, July 23, 2013 11:14 AM
To: Aldrin Isaac <aldrin.isaac@gmail.com<mailto:aldrin.isaac@gmail.com>>, K=
ireeti Kompella <kireeti.kompella@gmail.com<mailto:kireeti.kompella@gmail.c=
om>>
Cc: Luyuan Fang <lufang@cisco.com<mailto:lufang@cisco.com>>, L3VPN <l3vpn@i=
etf.org<mailto:l3vpn@ietf.org>>, Yakov Rekhter <yakov@juniper.net<mailto:ya=
kov@juniper.net>>, "nvo3@ietf.org<mailto:nvo3@ietf.org>" <nvo3@ietf.org<mai=
lto:nvo3@ietf.org>>, Xuxiaohu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.c=
om>>, "thomas.morin@orange.com<mailto:thomas.morin@orange.com>" <thomas.mor=
in@orange.com<mailto:thomas.morin@orange.com>>, "UTTARO, JAMES" <ju1738@att=
.com<mailto:ju1738@att.com>>
Subject: RE: [nvo3] The possibility of using global MPLS labels as VNIs ...=
 for l3vpn

For distributed based architecture, the local context ID has a lot of benef=
its. For centralized (or SDN) architecture, will the global context ID have=
 advance?  Another way to ask this is: is distributed architecture better t=
han centralized architecture for VPN or virtual network overlay?

Lucy

From:nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org> [mailto:nvo3-bounc=
es@ietf.org] On Behalf Of Aldrin Isaac
Sent: Tuesday, July 23, 2013 8:00 AM
To: Kireeti Kompella
Cc: Luyuan Fang (lufang); L3VPN; Yakov Rekhter; nvo3@ietf.org<mailto:nvo3@i=
etf.org>; Xuxiaohu; thomas.morin@orange.com<mailto:thomas.morin@orange.com>=
; UTTARO, JAMES
Subject: Re: [nvo3] The possibility of using global MPLS labels as VNIs ...=
 for l3vpn

+1.

Network operators lose flexibility with Global VNIDs. Virtual topology will=
 be fine tuned on top of VNIDs by squeezing a square peg (ACLs) into a roun=
d hole (where it's otherwise not needed).  I think local context IDs will m=
ake a come back once we regain our sanity.  :).

On Tuesday, July 23, 2013, Kireeti Kompella wrote:
Hi Xuxiaohu,

Sorry for the previous empty email.

On Jul 23, 2013, at 4:51, Xuxiaohu <xuxiaohu@huawei.com<javascript:;>> wrot=
e:

> The reason that I started this discussion is to make sure whether the Vir=
tual Network Context Identification contained in the data packet is REALLY =
required to be globally unique in some cases.

No. There's nothing useful that I know that one can do with global IDs in t=
he data plane that one cannot do with local IDs, and local IDs are easier t=
o allocate and manage. So, I'd be going the other way and advocate locally =
significant VNIDs for VXLAN and NVGRE, not global IDs for VPNs. (And I do)

Kireeti
_______________________________________________
nvo3 mailing list
nvo3@ietf.org<javascript:;>
https://www.ietf.org/mailman/listinfo/nvo3

--_000_2FE467D3673DCE409A84D67EC2F607BB13FAB14Dxmbrcdx10ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-ID: <48D7024C39C8894AACFB03B71BEC015E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Lucy -</div>
<div><br>
</div>
<div>Some form of Global ID might be useful to help organize the SDN Contro=
ller, but there is no point in putting it in the data plane.</div>
<div><br>
</div>
<div>George</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Lucy yong &lt;<a href=3D"mail=
to:lucy.yong@huawei.com">lucy.yong@huawei.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, July 23, 2013 12:28 =
PM<br>
<span style=3D"font-weight:bold">To: </span>&quot;Luyuan Fang (lufang)&quot=
; &lt;<a href=3D"mailto:lufang@cisco.com">lufang@cisco.com</a>&gt;, Aldrin =
Isaac &lt;<a href=3D"mailto:aldrin.isaac@gmail.com">aldrin.isaac@gmail.com<=
/a>&gt;, Kireeti Kompella &lt;<a href=3D"mailto:kireeti.kompella@gmail.com"=
>kireeti.kompella@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>L3VPN &lt;<a href=3D"mailto:l3v=
pn@ietf.org">l3vpn@ietf.org</a>&gt;, Yakov Rekhter &lt;<a href=3D"mailto:ya=
kov@juniper.net">yakov@juniper.net</a>&gt;, &quot;<a href=3D"mailto:nvo3@ie=
tf.org">nvo3@ietf.org</a>&quot; &lt;<a href=3D"mailto:nvo3@ietf.org">nvo3@i=
etf.org</a>&gt;,
 &quot;<a href=3D"mailto:thomas.morin@orange.com">thomas.morin@orange.com</=
a>&quot; &lt;<a href=3D"mailto:thomas.morin@orange.com">thomas.morin@orange=
.com</a>&gt;, &quot;UTTARO, JAMES&quot; &lt;<a href=3D"mailto:ju1738@att.co=
m">ju1738@att.com</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: [nvo3] The possibility=
 of using global MPLS labels as VNIs ... for l3vpn<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: brea=
k-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">In distributed control plane appro=
ach, we have strong consensus that local ID is the way to go.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">Like to hear more the people opini=
ons about: in SDN approach, will global ID and local ID are equally good (j=
ust mater choice) or one is better than
 other?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">Lucy<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif; ">From:</span></b><span style=3D"font-size: 10pt; font-fami=
ly: Tahoma, sans-serif; "> Luyuan Fang (lufang) [<a href=3D"mailto:lufang@c=
isco.com">mailto:lufang@cisco.com</a>]
<br>
<b>Sent:</b> Tuesday, July 23, 2013 11:06 AM<br>
<b>To:</b> Lucy yong; Aldrin Isaac; Kireeti Kompella<br>
<b>Cc:</b> L3VPN; Yakov Rekhter; <a href=3D"mailto:nvo3@ietf.org">nvo3@ietf=
.org</a>; Xuxiaohu;
<a href=3D"mailto:thomas.morin@orange.com">thomas.morin@orange.com</a>; UTT=
ARO, JAMES<br>
<b>Subject:</b> Re: [nvo3] The possibility of using global MPLS labels as V=
NIs ... for l3vpn<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">You choose the ID type: global or local.<o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">You choose the control paradigm, SDN, dynam=
ic control plane, or hybrid.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">The two decisions are independent.<o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">My personal preferences: SDN with local ID.=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Luyuan<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 11pt; font-family: Cali=
bri, sans-serif; color: black; ">From:
</span></b><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif=
; color: black; ">Lucy yong &lt;<a href=3D"mailto:lucy.yong@huawei.com">luc=
y.yong@huawei.com</a>&gt;<br>
<b>Date: </b>Tuesday, July 23, 2013 11:58 AM<br>
<b>To: </b>Luyuan Fang &lt;<a href=3D"mailto:lufang@cisco.com">lufang@cisco=
.com</a>&gt;, Aldrin Isaac &lt;<a href=3D"mailto:aldrin.isaac@gmail.com">al=
drin.isaac@gmail.com</a>&gt;, Kireeti Kompella &lt;<a href=3D"mailto:kireet=
i.kompella@gmail.com">kireeti.kompella@gmail.com</a>&gt;<br>
<b>Cc: </b>L3VPN &lt;<a href=3D"mailto:l3vpn@ietf.org">l3vpn@ietf.org</a>&g=
t;, Yakov Rekhter &lt;<a href=3D"mailto:yakov@juniper.net">yakov@juniper.ne=
t</a>&gt;, &quot;<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a>&quot; &=
lt;<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a>&gt;, Xuxiaohu
 &lt;<a href=3D"mailto:xuxiaohu@huawei.com">xuxiaohu@huawei.com</a>&gt;, &q=
uot;<a href=3D"mailto:thomas.morin@orange.com">thomas.morin@orange.com</a>&=
quot; &lt;<a href=3D"mailto:thomas.morin@orange.com">thomas.morin@orange.co=
m</a>&gt;, &quot;UTTARO, JAMES&quot; &lt;<a href=3D"mailto:ju1738@att.com">=
ju1738@att.com</a>&gt;<br>
<b>Subject: </b>RE: [nvo3] The possibility of using global MPLS labels as V=
NIs ... for l3vpn<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; "><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span><span style=3D"color:=
black"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">&nbsp;</span><span style=3D"color:black"><o=
:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">As I see, using SDN approach or distributed=
 control plane, and using global or local ID are two orthogonal questions.<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size: 11pt; font-family: C=
alibri, sans-serif; color: rgb(31, 73, 125); ">[Lucy] then, the question to=
 be asked is which usage makes sense in the SDN approach, &nbsp;global ID o=
r local ID? IMHO: they are related.</span></i></b><span style=3D"color:blac=
k"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size: 11pt; font-family: C=
alibri, sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span></i></b><span s=
tyle=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size: 11pt; font-family: C=
alibri, sans-serif; color: rgb(31, 73, 125); ">Lucy
</span></i></b><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">&nbsp;</span><span style=3D"color:black"><o=
:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">&gt;&nbsp;</span><span style=3D"font-size: =
11.5pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">is dis=
tributed architecture better than centralized
 architecture for VPN or virtual network overlay?</span><span style=3D"colo=
r:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">No necessarily.</span><span style=3D"color:=
black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">&nbsp;</span><span style=3D"color:black"><o=
:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">Luyuan</span><span style=3D"color:black"><o=
:p></o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 11pt; font-family: Cali=
bri, sans-serif; color: black; ">From:
</span></b><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif=
; color: black; ">Lucy yong &lt;<a href=3D"mailto:lucy.yong@huawei.com">luc=
y.yong@huawei.com</a>&gt;<br>
<b>Date: </b>Tuesday, July 23, 2013 11:14 AM<br>
<b>To: </b>Aldrin Isaac &lt;<a href=3D"mailto:aldrin.isaac@gmail.com">aldri=
n.isaac@gmail.com</a>&gt;, Kireeti Kompella &lt;<a href=3D"mailto:kireeti.k=
ompella@gmail.com">kireeti.kompella@gmail.com</a>&gt;<br>
<b>Cc: </b>Luyuan Fang &lt;<a href=3D"mailto:lufang@cisco.com">lufang@cisco=
.com</a>&gt;, L3VPN &lt;<a href=3D"mailto:l3vpn@ietf.org">l3vpn@ietf.org</a=
>&gt;, Yakov Rekhter &lt;<a href=3D"mailto:yakov@juniper.net">yakov@juniper=
.net</a>&gt;, &quot;<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a>&quot=
;
 &lt;<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a>&gt;, Xuxiaohu &lt;<=
a href=3D"mailto:xuxiaohu@huawei.com">xuxiaohu@huawei.com</a>&gt;, &quot;<a=
 href=3D"mailto:thomas.morin@orange.com">thomas.morin@orange.com</a>&quot; =
&lt;<a href=3D"mailto:thomas.morin@orange.com">thomas.morin@orange.com</a>&=
gt;,
 &quot;UTTARO, JAMES&quot; &lt;<a href=3D"mailto:ju1738@att.com">ju1738@att=
.com</a>&gt;<br>
<b>Subject: </b>RE: [nvo3] The possibility of using global MPLS labels as V=
NIs ... for l3vpn</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black; ">&nbsp;</span><span style=3D"color:black"><o=
:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">For distributed based architecture=
, the local context ID has a lot of benefits. For centralized (or SDN) arch=
itecture, will the global context ID
 have advance? &nbsp;Another way to ask this is: is distributed architectur=
e better than centralized architecture for VPN or virtual network overlay?<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span><span style=3D"color:=
black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">Lucy</span><span style=3D"color:bl=
ack"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span><span style=3D"color:=
black"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif; color: black; ">From:</span></b><span style=3D"font-size: 1=
0pt; font-family: Tahoma, sans-serif; color: black; "><a href=3D"mailto:nvo=
3-bounces@ietf.org">nvo3-bounces@ietf.org</a>
 [<a href=3D"mailto:nvo3-bounces@ietf.org">mailto:nvo3-bounces@ietf.org</a>=
] <b>On Behalf Of
</b>Aldrin Isaac<br>
<b>Sent:</b> Tuesday, July 23, 2013 8:00 AM<br>
<b>To:</b> Kireeti Kompella<br>
<b>Cc:</b> Luyuan Fang (lufang); L3VPN; Yakov Rekhter; <a href=3D"mailto:nv=
o3@ietf.org">
nvo3@ietf.org</a>; Xuxiaohu; <a href=3D"mailto:thomas.morin@orange.com">tho=
mas.morin@orange.com</a>; UTTARO, JAMES<br>
<b>Subject:</b> Re: [nvo3] The possibility of using global MPLS labels as V=
NIs ... for l3vpn</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&#43;1.<o:p></o:p></span=
></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Network operators lose f=
lexibility&nbsp;with Global VNIDs.&nbsp;Virtual&nbsp;topology will be fine =
tuned&nbsp;on top of VNIDs by&nbsp;squeezing a square peg (ACLs) into a rou=
nd hole (where it's otherwise not needed). &nbsp;I think&nbsp;local context
 IDs will make a come back once we regain our&nbsp;sanity. &nbsp;:).<o:p></=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">On Tuesday, July 23, 201=
3, Kireeti Kompella wrote:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi Xuxiaohu,<br>
<br>
Sorry for the previous empty email.<br>
<br>
On Jul 23, 2013, at 4:51, Xuxiaohu &lt;<a href=3D"javascript:;">xuxiaohu@hu=
awei.com</a>&gt; wrote:<br>
<br>
&gt; The reason that I started this discussion is to make sure whether the =
Virtual Network Context Identification contained in the data packet is REAL=
LY required to be globally unique in some cases.<br>
<br>
No. There's nothing useful that I know that one can do with global IDs in t=
he data plane that one cannot do with local IDs, and local IDs are easier t=
o allocate and manage. So, I'd be going the other way and advocate locally =
significant VNIDs for VXLAN and
 NVGRE, not global IDs for VPNs. (And I do)<br>
<br>
Kireeti<br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"javascript:;">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/nvo3</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_2FE467D3673DCE409A84D67EC2F607BB13FAB14Dxmbrcdx10ciscoc_--

From aldrin.isaac@gmail.com  Fri Aug  2 06:25:29 2013
Return-Path: <aldrin.isaac@gmail.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0414511E80D3; Fri,  2 Aug 2013 06:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1kOkCIzECYR; Fri,  2 Aug 2013 06:25:28 -0700 (PDT)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id 2713E21E8323; Fri,  2 Aug 2013 06:24:38 -0700 (PDT)
Received: by mail-lb0-f179.google.com with SMTP id v1so449091lbd.10 for <multiple recipients>; Fri, 02 Aug 2013 06:24:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=il4B7sWn8NUGqvpU/Ku12qiNune20DPlyruUdo4SnVc=; b=WdVraI+1hEIKUCnAUYMca48Q1qS3MU3XqACZKpuBv5lp8OmITO0Tnrs52A/Wsan9hq yAneiim5nhDPgF4eRlFt2soTeBGodKgQQzD8AZW1TRy3tyU261LmoiE1wwqy7JMy00HT XN7H2GB7+tPpXQulviBFDnqrpsvoIA3+g86nU6J2a9MBF2x43lxvgTba+oBy3qDX4OOv GtCQ/qQSSmsOsw1woQKf//feKmTaf5fOlWf7HT9wwzGVyoVjkM8q3o3yYdgqvTBOFaXW Aeifmmch/fr1EN8GnydSjAZjGe/BxTL/Ex2nshP81hsdPYh/0SFbBTHLCTec7NjWu3Xo Hkcw==
MIME-Version: 1.0
X-Received: by 10.112.160.74 with SMTP id xi10mr3477634lbb.63.1375449877558; Fri, 02 Aug 2013 06:24:37 -0700 (PDT)
Received: by 10.152.6.234 with HTTP; Fri, 2 Aug 2013 06:24:37 -0700 (PDT)
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D4527F3FB@dfweml509-mbx.china.huawei.com>
References: <EB9B93801780FD4CA165E0FBCB3C3E672AE93EF8@SJEXCHMB09.corp.ad.broadcom.com> <2691CE0099834E4A9C5044EEC662BB9D4527F3FB@dfweml509-mbx.china.huawei.com>
Date: Fri, 2 Aug 2013 09:24:37 -0400
Message-ID: <CAOA2mbyafkhFe-_Tgn_Q+sW+CHDVsQzVe-G3ZwB8UUuWjCrHRg@mail.gmail.com>
Subject: Re: [nvo3] The possibility of using global MPLS labels as VNIs ... for l3vpn
From: Aldrin Isaac <aldrin.isaac@gmail.com>
To: Lucy yong <lucy.yong@huawei.com>
Content-Type: multipart/alternative; boundary=001a11c3421e5bba9704e2f6e1b8
X-Mailman-Approved-At: Fri, 02 Aug 2013 15:07:50 -0700
Cc: "thomas.morin@orange.com" <thomas.morin@orange.com>, L3VPN <l3vpn@ietf.org>, Pat Thaler <pthaler@broadcom.com>, Yakov Rekhter <yakov@juniper.net>, "nvo3@ietf.org" <nvo3@ietf.org>, "UTTARO, JAMES" <ju1738@att.com>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 13:25:29 -0000

--001a11c3421e5bba9704e2f6e1b8
Content-Type: text/plain; charset=ISO-8859-1

Local ID is useful to key into any action or context versus
only into context that represents a flat tenant network.   This can be
leveraged by an SDN controller or via distributed provisioning.  If
standards produce a one trick pony than proprietary complexity will creep
in.

On Friday, July 26, 2013, Lucy yong wrote:

> (change back to the original subject title)
>
> For this context, the global VN ID means that the label is used as the VN
> identifier in the data plane and is allocated per VN basis (maybe by NVA);
> the local (VN) ID means that the label is allocated by individual NVEs and
> only has the significance for the NVE that creates it. Thus, each NVE has
> to distribute the local (VN) ID to all the other NVEs that are the members
> of the same VN, which requires some distributed control plane capability.
> The NVE may create one local ID for a VN or several local IDs associated to
> a VN.
>
> Local ID mechanism provides some flexibility to NVE in egress forwarding
> process. However, if the major application of NVO3 is for the case that NVE
> resides on server, i.e. NVE and end-points resides on a same device, is
> this flexibility necessary? Sometimes "flexibility" also means
> "complexity". When using separated NVE forwarder and NVE controller, and
> having SDN based NVE controller, will local ID distribution make this
> solution more complex than using global VN ID?
>
> NVO3 requires supporting both NVE local and NVE remote. Can one solution
> fit both applications well? or we need more than one solution and let
> providers to choose?
>
> Lucy
>
> > -----Original Message-----
> > From: nvo3-bounces@ietf.org <javascript:;> [mailto:nvo3-bounces@ietf.org<javascript:;>]
> On Behalf Of
> > Pat Thaler
> > Sent: Thursday, July 25, 2013 7:59 AM
> > To: Richard Li; Kireeti Kompella; Lucy yong
> > Cc: L3VPN; Yakov Rekhter; nvo3@ietf.org <javascript:;>; Aldrin Isaac;
> > thomas.morin@orange.com <javascript:;>; UTTARO, JAMES
> > Subject: [nvo3] The meaning of "global"
> >
> > "Global" seems to be used in this discussion and the data plane
> > requirements to mean "unique in the administrative domain" as
> > contrasted to a "local" identifier that is mapped to another value at
> > some points in the domain.
> >
> > On the other hand, when discussing VN Name in the hyperviser - NVE
> > control plane, global is used in the sense that I understand global -
> > i.e. unique in the world - e.g. a UUID. 24-bit identifiers aren't large
> > enough to be global in that sense.
> >
> > It would be better to use another term when we mean unique in the
> > administrative domain.
> >
> > Pat
> >
> > -----Original Message-----
> > From: nvo3-bounces@ietf.org <javascript:;> [mailto:nvo3-bounces@ietf.org<javascript:;>]
> On Behalf Of
> > Richard Li
> > Sent: Tuesday, July 23, 2013 5:12 PM
> > To: Kireeti Kompella; Lucy yong
> > Cc: L3VPN; Yakov Rekhter; nvo3@ietf.org <javascript:;>; Aldrin Isaac;
> > thomas.morin@orange.com <javascript:;>; UTTARO, JAMES
> > Subject: Re: [nvo3] The possibility of using global MPLS labels as
> > VNIs ... for l3vpn
> >
> > We may be able to get some wisdom from VLAN where both local and global
> > ids are used.
> >
> > The global vlan id is used to build a whole "subnet" across different
> > and multi-hop Ethernet segments.
> >
> >
> >
> > -----Original Message-----
> > From: l3vpn-bounces@ietf.org <javascript:;> [mailto:
> l3vpn-bounces@ietf.org <javascript:;>] On Behalf
> > Of Kireeti Kompella
> > Sent: Wednesday, July 24, 2013 12:46 AM
> > To: Lucy yong
> > Cc: thomas.morin@orange.com <javascript:;>; L3VPN; Yakov Rekhter;
> nvo3@ietf.org <javascript:;>;
> > Aldrin Isaac; UTTARO, JAMES
> > Subject: Re: [nvo3] The possibility of using global MPLS labels as
> > VNIs ... for l3vpn
> >
> > On Jul 23, 2013, at 19:28, Lucy yong <lucy.yong@huawei.com<javascript:;>>
> wrote:
> >
> > > Like to hear more the people opinions about: in SDN approach, will
> > global ID and local ID are equally good (just mater choice) or one is
> > better than other?
> >
> > The SDN (centralized) approach makes allocation of global IDs easier.
> > However, Xiaohu asked a data plane question. Local IDs are much easier
> > for the data plane.
> >
> > BTW, I am not in favor of centralizing everything.
> >
> > Kireeti
> > _______________________________________________
> > nvo3 mailing list
> > nvo3@ietf.org <javascript:;>
> > https://www.ietf.org/mailman/listinfo/nvo3
> >
> >
> > _______________________________________________
> > nvo3 mailing list
> > nvo3@ietf.org <javascript:;>
> > https://www.ietf.org/mailman/listinfo/nvo3
>

--001a11c3421e5bba9704e2f6e1b8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Local ID is=A0useful to key into any=A0action or context versus only=A0into=
=A0context=A0that represents a=A0flat=A0tenant network. =A0 This can be lev=
eraged by<span></span>=A0an SDN controller or via=A0distributed provisionin=
g. =A0If standards produce a one trick pony than=A0proprietary complexity w=
ill creep in.<br>
<br>On Friday, July 26, 2013, Lucy yong  wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">(change back to the original subject title)<br>
<br>
For this context, the global VN ID means that the label is used as the VN i=
dentifier in the data plane and is allocated per VN basis (maybe by NVA); t=
he local (VN) ID means that the label is allocated by individual NVEs and o=
nly has the significance for the NVE that creates it. Thus, each NVE has to=
 distribute the local (VN) ID to all the other NVEs that are the members of=
 the same VN, which requires some distributed control plane capability. The=
 NVE may create one local ID for a VN or several local IDs associated to a =
VN.<br>

<br>
Local ID mechanism provides some flexibility to NVE in egress forwarding pr=
ocess. However, if the major application of NVO3 is for the case that NVE r=
esides on server, i.e. NVE and end-points resides on a same device, is this=
 flexibility necessary? Sometimes &quot;flexibility&quot; also means &quot;=
complexity&quot;. When using separated NVE forwarder and NVE controller, an=
d having SDN based NVE controller, will local ID distribution make this sol=
ution more complex than using global VN ID?<br>

<br>
NVO3 requires supporting both NVE local and NVE remote. Can one solution fi=
t both applications well? or we need more than one solution and let provide=
rs to choose?<br>
<br>
Lucy<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#=
39;nvo3-bounces@ietf.org&#39;)">nvo3-bounces@ietf.org</a> [mailto:<a href=
=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;nvo3-bounces@ie=
tf.org&#39;)">nvo3-bounces@ietf.org</a>] On Behalf Of<br>

&gt; Pat Thaler<br>
&gt; Sent: Thursday, July 25, 2013 7:59 AM<br>
&gt; To: Richard Li; Kireeti Kompella; Lucy yong<br>
&gt; Cc: L3VPN; Yakov Rekhter; <a href=3D"javascript:;" onclick=3D"_e(event=
, &#39;cvml&#39;, &#39;nvo3@ietf.org&#39;)">nvo3@ietf.org</a>; Aldrin Isaac=
;<br>
&gt; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;tho=
mas.morin@orange.com&#39;)">thomas.morin@orange.com</a>; UTTARO, JAMES<br>
&gt; Subject: [nvo3] The meaning of &quot;global&quot;<br>
&gt;<br>
&gt; &quot;Global&quot; seems to be used in this discussion and the data pl=
ane<br>
&gt; requirements to mean &quot;unique in the administrative domain&quot; a=
s<br>
&gt; contrasted to a &quot;local&quot; identifier that is mapped to another=
 value at<br>
&gt; some points in the domain.<br>
&gt;<br>
&gt; On the other hand, when discussing VN Name in the hyperviser - NVE<br>
&gt; control plane, global is used in the sense that I understand global -<=
br>
&gt; i.e. unique in the world - e.g. a UUID. 24-bit identifiers aren&#39;t =
large<br>
&gt; enough to be global in that sense.<br>
&gt;<br>
&gt; It would be better to use another term when we mean unique in the<br>
&gt; administrative domain.<br>
&gt;<br>
&gt; Pat<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#=
39;nvo3-bounces@ietf.org&#39;)">nvo3-bounces@ietf.org</a> [mailto:<a href=
=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;nvo3-bounces@ie=
tf.org&#39;)">nvo3-bounces@ietf.org</a>] On Behalf Of<br>

&gt; Richard Li<br>
&gt; Sent: Tuesday, July 23, 2013 5:12 PM<br>
&gt; To: Kireeti Kompella; Lucy yong<br>
&gt; Cc: L3VPN; Yakov Rekhter; <a href=3D"javascript:;" onclick=3D"_e(event=
, &#39;cvml&#39;, &#39;nvo3@ietf.org&#39;)">nvo3@ietf.org</a>; Aldrin Isaac=
;<br>
&gt; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;tho=
mas.morin@orange.com&#39;)">thomas.morin@orange.com</a>; UTTARO, JAMES<br>
&gt; Subject: Re: [nvo3] The possibility of using global MPLS labels as<br>
&gt; VNIs ... for l3vpn<br>
&gt;<br>
&gt; We may be able to get some wisdom from VLAN where both local and globa=
l<br>
&gt; ids are used.<br>
&gt;<br>
&gt; The global vlan id is used to build a whole &quot;subnet&quot; across =
different<br>
&gt; and multi-hop Ethernet segments.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#=
39;l3vpn-bounces@ietf.org&#39;)">l3vpn-bounces@ietf.org</a> [mailto:<a href=
=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;l3vpn-bounces@i=
etf.org&#39;)">l3vpn-bounces@ietf.org</a>] On Behalf<br>

&gt; Of Kireeti Kompella<br>
&gt; Sent: Wednesday, July 24, 2013 12:46 AM<br>
&gt; To: Lucy yong<br>
&gt; Cc: <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39=
;thomas.morin@orange.com&#39;)">thomas.morin@orange.com</a>; L3VPN; Yakov R=
ekhter; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;=
nvo3@ietf.org&#39;)">nvo3@ietf.org</a>;<br>

&gt; Aldrin Isaac; UTTARO, JAMES<br>
&gt; Subject: Re: [nvo3] The possibility of using global MPLS labels as<br>
&gt; VNIs ... for l3vpn<br>
&gt;<br>
&gt; On Jul 23, 2013, at 19:28, Lucy yong &lt;<a href=3D"javascript:;" oncl=
ick=3D"_e(event, &#39;cvml&#39;, &#39;lucy.yong@huawei.com&#39;)">lucy.yong=
@huawei.com</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; Like to hear more the people opinions about: in SDN approach, wil=
l<br>
&gt; global ID and local ID are equally good (just mater choice) or one is<=
br>
&gt; better than other?<br>
&gt;<br>
&gt; The SDN (centralized) approach makes allocation of global IDs easier.<=
br>
&gt; However, Xiaohu asked a data plane question. Local IDs are much easier=
<br>
&gt; for the data plane.<br>
&gt;<br>
&gt; BTW, I am not in favor of centralizing everything.<br>
&gt;<br>
&gt; Kireeti<br>
&gt; _______________________________________________<br>
&gt; nvo3 mailing list<br>
&gt; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;nvo=
3@ietf.org&#39;)">nvo3@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/nvo3</a><br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; nvo3 mailing list<br>
&gt; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;nvo=
3@ietf.org&#39;)">nvo3@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/nvo3</a><br>
</blockquote>

--001a11c3421e5bba9704e2f6e1b8--

From internet-drafts@ietf.org  Tue Aug  6 10:25:05 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3559D21F9654; Tue,  6 Aug 2013 10:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ebDAJYkivqj; Tue,  6 Aug 2013 10:25:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 83A4D21F918C; Tue,  6 Aug 2013 10:25:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-l3vpn-mvpn-extranet-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.61
Message-ID: <20130806172504.21056.76579.idtracker@ietfa.amsl.com>
Date: Tue, 06 Aug 2013 10:25:04 -0700
Cc: l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 17:25:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Layer 3 Virtual Private Networks Working =
Group of the IETF.

	Title           : Extranet Multicast in BGP/IP MPLS VPNs
	Author(s)       : Yakov Rekhter
                          Eric C. Rosen
                          Rahul Aggarwal
                          Yiqun Cai
                          Wim Henderickx
                          Thomas Morin
                          Praveen Muley
                          Ray Qiu
                          IJsbrand Wijnands
	Filename        : draft-ietf-l3vpn-mvpn-extranet-02.txt
	Pages           : 55
	Date            : 2013-08-06

Abstract:
   Previous RFCs specify the procedures necessary to allow IP multicast
   traffic to travel from one site to another within a BGP/MPLS IP VPN
   (Virtual Private Network).  However, it is sometimes desirable to
   allow multicast traffic whose source is in one VPN to be received by
   systems that are in another VPN.  This is known as a "Multicast VPN
   (MVPN) extranet".  This document updates RFCs 6513, 6514, and 6625 by
   specifying the procedures that are necessary in order to provide MVPN
   extranet service.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-l3vpn-mvpn-extranet

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-l3vpn-mvpn-extranet-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3vpn-mvpn-extranet-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From thomas.morin@orange.com  Wed Aug 21 07:03:37 2013
Return-Path: <thomas.morin@orange.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A053411E81FF for <l3vpn@ietfa.amsl.com>; Wed, 21 Aug 2013 07:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EEvhxPpFYGwP for <l3vpn@ietfa.amsl.com>; Wed, 21 Aug 2013 07:03:32 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 9A92F21F99B7 for <l3vpn@ietf.org>; Wed, 21 Aug 2013 07:03:28 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 39EBE18C79B; Wed, 21 Aug 2013 16:03:27 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 21E1327C046; Wed, 21 Aug 2013 16:03:27 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Wed, 21 Aug 2013 16:03:26 +0200
From: <thomas.morin@orange.com>
To: L3VPN <l3vpn@ietf.org>
Subject: Draft minutes of our IETF 87 session
Thread-Topic: Draft minutes of our IETF 87 session
Thread-Index: AQHOnnc0CmnClIO6O0W9rNBivZgSZA==
Date: Wed, 21 Aug 2013 14:03:26 +0000
Message-ID: <17866_1377093807_5214C8AF_17866_5499_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D075703F5@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
x-originating-ip: [10.197.38.1]
Content-Type: text/plain; charset="utf-8"
Content-ID: <9139B9C966701D4CB3D8AF5CA7B48BC0@adroot.infra.ftgroup>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.8.21.131830
Cc: L3VPN Chairs <l3vpn-chairs@tools.ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 14:03:37 -0000

SGVsbG8gYWxsLA0KDQpUaGUgKmRyYWZ0cyogbWludXRlcyBvZiBvdXIgSUVURjg3IHNlc3Npb24g
YXJlIG5vdyBhdmFpbGFibGUgYXQNCmh0dHA6Ly90b29scy5pZXRmLm9yZy93Zy9sM3Zwbi9taW51
dGVzIC4NCg0KVGhhbmtzIHRvIERhbiBLaW5nIGZvciB0YWtpbmcgdGhlbS4NCg0KUGxlYXNlIHJl
dmlldyB0aGVtIGFuZCBzZW5kIHVzIGFueSBhZGRpdGlvbiBvciBjb3JyZWN0aW9uIHRoYXQgeW91
IG1heSANCmZpbmQgdXNlZnVsLg0KDQpUaGFuayB5b3UsDQoNCi1UaG9tYXMsIGFzIGwzVlBOIGNv
LWNoYWlyCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18KCkNlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQg
Y29udGVuaXIgZGVzIGluZm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVz
IGV0IG5lIGRvaXZlbnQgZG9uYwpwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGll
cyBzYW5zIGF1dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJy
ZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxlcgphIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBh
aW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBl
dGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLApPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNw
b25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZp
ZS4gTWVyY2kuCgpUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBj
b25maWRlbnRpYWwgb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0
ZWQgYnkgbGF3Owp0aGV5IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVk
IHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBp
biBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdl
IGFuZCBpdHMgYXR0YWNobWVudHMuCkFzIGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlz
IG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2Vk
IG9yIGZhbHNpZmllZC4KVGhhbmsgeW91LgoK

From thomas.morin@orange.com  Wed Aug 21 07:47:39 2013
Return-Path: <thomas.morin@orange.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5ED021F9C56 for <l3vpn@ietfa.amsl.com>; Wed, 21 Aug 2013 07:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8PljqkPUpJtK for <l3vpn@ietfa.amsl.com>; Wed, 21 Aug 2013 07:47:35 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 0A2A521F9C5A for <l3vpn@ietf.org>; Wed, 21 Aug 2013 07:47:35 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id C500B18C482; Wed, 21 Aug 2013 16:47:33 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id A84A1238067; Wed, 21 Aug 2013 16:47:33 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Wed, 21 Aug 2013 16:47:33 +0200
From: <thomas.morin@orange.com>
To: L3VPN <l3vpn@ietf.org>
Subject: WG Last Call for draft-ietf-l3vpn-mldp-vrf-in-band-signaling
Thread-Topic: WG Last Call for draft-ietf-l3vpn-mldp-vrf-in-band-signaling
Thread-Index: AQHOnn1dDHhIXeAOQU6e4ATKggMlhg==
Date: Wed, 21 Aug 2013 14:47:32 +0000
Message-ID: <14292_1377096453_5214D305_14292_2376_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07570795@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
x-originating-ip: [10.197.38.5]
Content-Type: text/plain; charset="utf-8"
Content-ID: <28CD82E81F4FB346B703673DE6DB3189@adroot.infra.ftgroup>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.8.21.133617
Cc: "draft-ietf-l3vpn-mldp-vrf-in-band-signaling@tools.ietf.org" <draft-ietf-l3vpn-mldp-vrf-in-band-signaling@tools.ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 14:47:40 -0000

SGVsbG8gd29ya2luZyBncm91cCwNCg0KVGhpcyBlbWFpbCBzdGFydHMgYSB0d28td2VlayBXb3Jr
aW5nIEdyb3VwIExhc3QgQ2FsbCBvbiANCmRyYWZ0LWlldGYtbDN2cG4tbWxkcC12cmYtaW4tYmFu
ZC1zaWduYWxpbmcsIHdoaWNoIGlzIGNvbnNpZGVyZWQgbWF0dXJlIA0KYW5kIHJlYWR5IGZvciBh
IHdvcmtpbmcgZ3JvdXAgcmV2aWV3Lg0KDQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1pZXRmLWwzdnBuLW1sZHAtdnJmLWluLWJhbmQtc2lnbmFsaW5nDQoNClBsZWFzZSByZWFkIHRo
ZSBkb2N1bWVudCBpZiB5b3UgaGF2ZW4ndCByZWFkIHRoZSBtb3N0IHJlY2VudCB2ZXJzaW9uLCAN
CmFuZCBzZW5kIHlvdXIgY29tbWVudHMgdG8gdGhlIGxpc3QsIG5vIGxhdGVyIHRoYW4gV2VkbmVz
ZGF5IFNlcHRlbWJlciA0dGguDQoNClRoYW5rIHlvdSwNCg0KLVRob21hcyAmIE1hcnRpbg0KCl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18KCkNlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQgY29udGVuaXIg
ZGVzIGluZm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRv
aXZlbnQgZG9uYwpwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5zIGF1
dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJyZXVyLCB2ZXVp
bGxleiBsZSBzaWduYWxlcgphIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUg
bGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBldGFudCBzdXNj
ZXB0aWJsZXMgZCdhbHRlcmF0aW9uLApPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNwb25zYWJpbGl0
ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVyY2ku
CgpUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRp
YWwgb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkgbGF3
Owp0aGV5IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVkIHdpdGhvdXQg
YXV0aG9yaXNhdGlvbi4KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciwg
cGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdlIGFuZCBpdHMg
YXR0YWNobWVudHMuCkFzIGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlzIG5vdCBsaWFi
bGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2VkIG9yIGZhbHNp
ZmllZC4KVGhhbmsgeW91LgoK

From julien.meuric@orange.com  Tue Aug 27 04:28:23 2013
Return-Path: <julien.meuric@orange.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADC8A11E82AA for <l3vpn@ietfa.amsl.com>; Tue, 27 Aug 2013 04:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.751
X-Spam-Level: ***
X-Spam-Status: No, score=3.751 tagged_above=-999 required=5 tests=[AWL=-10.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, URIBL_SBL=20]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a8nXF7k4DrWD for <l3vpn@ietfa.amsl.com>; Tue, 27 Aug 2013 04:28:19 -0700 (PDT)
Received: from r-mail2.rd.orange.com (r-mail2.rd.orange.com [217.108.152.42]) by ietfa.amsl.com (Postfix) with ESMTP id C7E8111E8179 for <l3vpn@ietf.org>; Tue, 27 Aug 2013 04:28:19 -0700 (PDT)
Received: from r-mail2.rd.orange.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 910985D8C92 for <l3vpn@ietf.org>; Tue, 27 Aug 2013 13:28:10 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.orange.com (Postfix) with ESMTP id 87A3B5D8C84 for <l3vpn@ietf.org>; Tue, 27 Aug 2013 13:28:10 +0200 (CEST)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 27 Aug 2013 13:28:10 +0200
Received: from [10.193.71.94] ([10.193.71.94]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 27 Aug 2013 13:28:10 +0200
Message-ID: <521C8D49.8070204@orange.com>
Date: Tue, 27 Aug 2013 13:28:09 +0200
From: Julien Meuric <julien.meuric@orange.com>
Organization: Orange
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: l3vpn@ietf.org
Subject: MPLS/SDN 2013 Program Information
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Aug 2013 11:28:10.0092 (UTC) FILETIME=[824C8AC0:01CEA318]
X-Mailman-Approved-At: Tue, 27 Aug 2013 05:21:02 -0700
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 11:28:23 -0000

The MPLS/SDN 2013 Conference (the 16th annual event) program is now
posted and is available at www.mpls2013.com, or specifically

Tutorials (Sun): http://www.isocore.com/mpls2013/program/tutorials.htm

Technical sessions (Mon-Wed): 
http://www.isocore.com/mpls2013/program/technical_sessions.htm

The conference will take place November 17-20 in Washington DC and will
include an extensive four day program consisting of tutorials, technical
sessions, panels, and exhibits. The key topics to be discussed at this
year's conference include: Virtualization, SDN, Cloud and Data Centers,
Mobility and SDN, PCE, Traffic Engineering and Emerging Technologies,
Transport SDN, Orchestration, and emerging multi-play applications
across common infrastructure.

The conference hotel is the Marriott Wardman Park in Washington DC. Please
note that there are only a limited number of rooms available this year at a
reduced rate.

Please make reservations at:
https://resweb.passkey.com/Resweb.do?mode=welcome_ei_new&eventID=10583503&utm_source=1786&utm_medium=email&utm_campaign=23303762 



From eric.gray@ericsson.com  Tue Aug 27 12:23:27 2013
Return-Path: <eric.gray@ericsson.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 511D211E81A7; Tue, 27 Aug 2013 12:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.077
X-Spam-Level: 
X-Spam-Status: No, score=-0.077 tagged_above=-999 required=5 tests=[AWL=-2.281, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I9Y-RebS5cqg; Tue, 27 Aug 2013 12:23:21 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id BE79511E81E9; Tue, 27 Aug 2013 12:23:21 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-f0-521cfca894eb
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 50.BD.09414.8ACFC125; Tue, 27 Aug 2013 21:23:21 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0328.009; Tue, 27 Aug 2013 15:23:20 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>
Subject: RE: About gap analysis on L3VPN [RFC4365]
Thread-Topic: About gap analysis on L3VPN [RFC4365]
Thread-Index: AQHOjfqR4+7pITNBRkuTXoDlEf8XapmAB9SMgCmN9iA=
Date: Tue, 27 Aug 2013 19:23:20 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF643104B@eusaamb107.ericsson.se>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DABBC@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DAE27@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DAE27@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCLMWRmVeSWpSXmKPExsUyuXRPuO7KPzJBBp/W8Vicne9v8XS+pMXW 86sYHZg9Wo68ZfVYsuQnUwBTFJdNSmpOZllqkb5dAldG7+p37AVXFCvW3fvI2MD4RKGLkZND QsBE4uiZKSwQtpjEhXvr2boYuTiEBI4ySvzafYYJJCEksJxRYu3CdBCbTUBD4tidtYwgtohA hsStc/uYQWxhASOJBVOvANkcQHFjiS09lhAlVhLNv/+DlbMIqEqsX3meHcTmFfCW6J3zmRli 10JGiRmnPrOCJDgFwiR2LX8EdhAj0EHfT60Bu4FZQFzi1pP5TBCHCkgs2XOeGcIWlXj5+B8r hK0s8X0ORC+zgJbEvIbfUL2KElO6H0ItFpQ4OfMJywRG0VlIxs5C0jILScssJC0LGFlWMXKU FqeW5aYbGWxiBMbEMQk23R2Me15aHmKU5mBREuddpXcmUEggPbEkNTs1tSC1KL6oNCe1+BAj EwenVAMj54NeO5PGzQ+ChBSi2j7s2rfwkN9yJb/Wy03ZKppfvmgH7V5fa7+LkVmkSTxvz7Kc e2FP83IK52faX83yiVi8/LLmH07/ZhaDWxt0NKW6J66SfqO7dKfUxev9ZjrL7hRt0jhY4Ltz l2ftJMu1Xlk3VzhOOfvU0m7bIoMjG6U0ZJoTMztV/i5XYinOSDTUYi4qTgQAN9ZaFlcCAAA=
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 19:23:27 -0000

WGlhb2h1LA0KDQoJWW91J3JlIGdldHRpbmcgYWhlYWQgb2YgdGhpbmdzLCBhIGJpdC4NCg0KCUl0
IGlzIG5vdCB0aGUgcHVycG9zZSBvZiB0aGUgR2FwIEFuYWx5c2lzIHRvIGRldGVybWluZSBob3cg
dG8gZml4IHRoZSBnYXBzLg0KVGhlIHB1cnBvc2Ugb2YgdGhlIEdhcCBBbmFseXNpcyBpcyB0byBj
b21wYXJlIGV4aXN0aW5nIGNhbmRpZGF0ZSBhcHByb2FjaGVzIHRvIHRoZQ0KcmVxdWlyZW1lbnRz
IGJlaW5nIGRlZmluZWQgaW4gdGhlIE5WTzMgd29ya2luZyBncm91cCAtIHRvIGRldGVybWluZSB3
aGVyZSB0aGUNCmV4aXN0aW5nIGNhbmRpZGF0ZSB0ZWNobm9sb2dpZXMvYXBwcm9hY2hlcyBtYXkg
ZmFsbCBzaG9ydC4NCg0KCUl0IGlzIGFmdGVyIHRoaXMgYW5hbHlzaXMgaXMgZG9uZSB0aGF0IHdl
IC0gYXMgYSB3b3JraW5nIGdyb3VwIC0gd291bGQgdGhlbiBiZQ0KaW4gYSBwb3NpdGlvbiB0byBt
YWtlIHNvbWUgZGVjaXNpb25zIGFzIHRvIHdoYXQgd29yayBtYXkgbmVlZCB0byBiZSBkb25lIGZv
ciBlYWNoDQpjYW5kaWRhdGUgaW4gb3JkZXIgdG8gbWVldCB0aGUgcmVxdWlyZW1lbnRzIHdlJ3Zl
IGRldGVybWluZWQuDQoNCglPbmNlIHdlJ3ZlIGRvbmUgdGhhdCwgdGhlbiB3ZSBjYW4gbG9vayBh
dCBmYXJtaW5nIHRoZSBzcGVjaWZpYyB3b3JrIG91dCB0bw0Kb3RoZXIgd29ya2luZyBncm91cHMs
IG9yIHJlLWNoYXJ0ZXJpbmcgTlZPMyB0byBpbmNsdWRlIGZpeGluZyB3aGF0J3MgbWlzc2luZy4N
Cg0KCUlmIHlvdSBhcmUgYXdhcmUgb2Ygc3BlY2lmaWMgZ2FwcyBpbiBMM1ZQTiB0ZWNobm9sb2dp
ZXMgLSBhZ2FpbnN0IHNwZWNpZmljDQpyZXF1aXJlbWVudHMgdGhhdCBoYXZlIGJlZW4gYWdyZWVk
IG9uIGJ5IHRoZSB3b3JraW5nIGdyb3VwIC0gdGhlbiBwbGVhc2UgbGV0IHVzDQprbm93IHdoYXQg
dGhvc2UgZ2FwcyBhcmUgYW5kIHdlIHdpbGwgZXZhbHVhdGUgaW5jbHVkaW5nIHRoZW0gaW4gdGhl
IGdhcCBhbmFseXNpcyANCmRyYWZ0Lg0KDQoJQW4gaW5mb3JtYXRpb24gZHJhZnQgb2YgdGhlIHR5
cGUgeW91IGRlc2NyaWJlIGlzIG5vdCBjdXJyZW50bHkgaW4gc2NvcGUgZm9yDQpOVk8zLCBhcyBp
dCB3b3VsZCBiZSBlc3NlbnRpYWxseSBhICJzb2x1dGlvbiIgZHJhZnQgZm9yIHVzaW5nIEwzVlBO
LiAgV2UgY2FuJ3Qgc3RvcA0KeW91IChvciBhbnlvbmUgZWxzZSkgZnJvbSB3cml0aW5nIHN1Y2gg
YSBkcmFmdCwgb2YgY291cnNlLg0KDQoJSSB0aGluayB5b3UgKG9yIHdob2V2ZXIpIHNob3VsZCBi
ZSBjYXJlZnVsLCBob3dldmVyLCB0byBlbnN1cmUgdGhhdCB0aGlzIA0KZHJhZnQgaXMgYWxpZ25l
ZCB3aXRoIHJlcXVpcmVtZW50cyBiZWluZyBkZXZlbG9wZWQgYW5kIGFncmVlZCB0byBpbiBOVk8z
LCBvciBpdCANCmlzIHZlcnkgbGlrZWx5IHRoYXQgYW55IHN1Y2ggZHJhZnQgd2lsbCBzaW1wbHkg
YWRkIHRvIHRoZSBub2lzZSBhdCB0aGUgbW9tZW50Lg0KDQoJQWxzbywgYW55IHN1Y2ggZHJhZnQg
Y291bGQgbm90IGJlIGFkb3B0ZWQgYnkgdGhlIE5WTzMgd29ya2luZyBncm91cCB1bnRpbA0KYWZ0
ZXIgaXQgaXMgcmUtY2hhcnRlcmVkIHRvIHdvcmsgb24gc29sdXRpb25zLCByZWNvbW1lbmRlZCBw
cmFjdGljZSBvciBhcHBsaWNhYmlsaXR5IA0Kd29yay4NCg0KLS0NCkVyaWMNCg0KLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IG52bzMtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOm52
bzMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFh1eGlhb2h1DQpTZW50OiBUaHVyc2Rh
eSwgQXVndXN0IDAxLCAyMDEzIDQ6NDggQU0NClRvOiBudm8zQGlldGYub3JnOyBsM3ZwbkBpZXRm
Lm9yZw0KU3ViamVjdDogUmU6IFtudm8zXSBBYm91dCBnYXAgYW5hbHlzaXMgb24gTDNWUE4gW1JG
QzQzNjVdDQoNCkhpIGFsbCwNCg0KSSdtIGdsYWQgdG8gc2VlIHRoYXQgdGhpcyBpc3N1ZSBpcyBt
ZW50aW9uZWQgaW4gdGhlIE5WbzMgY2hhaXJzJyBzbGlkZXMgYXMgd2VsbCAoaS5lLiwgc29tZSBy
ZWZlcmVuY2VzIHRvIEwzVlBOIHRlY2hub2xvZ3ktYmFzZWQgREMgVlBOIGFwcHJvYWNoZXMgYXJl
IHVzZWZ1bCkuICBVbmZvcnR1bmF0ZWx5LCB0aGlzIGlzc3VlIGlzIG5vdCBkaXNjdXNzZWQgZnVy
dGhlciBhZnRlciB0aGUgc3VydmV5IG9mIGFkb3B0aW9uIG9mIE5WR1JFIGFuZCBWWExBTiBkcmFm
dHMuIE15IGRvdWJ0IGlzIGluIHdoaWNoIFdHIHRoZSBMM1ZQTiB0ZWNobm9sb2d5LWJhc2VkIERD
IFZQTiBkcmFmdHMgc2hvdWxkIGJlIHB1cnN1ZWQgKEwzVlBOIFdHIG9yIE5WbzMgV0c/KS4NCg0K
QmVzdCByZWdhcmRzLA0KWGlhb2h1DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCreivP7IyzogbDN2cG4tYm91bmNlc0BpZXRmLm9yZyBbbDN2cG4tYm91bmNlc0Bp
ZXRmLm9yZ10gtPqx7SBYdXhpYW9odSBbeHV4aWFvaHVAaHVhd2VpLmNvbV0NCreiy83KsbzkOiAy
MDEzxOo31MIzMcjVIDIyOjQzDQq1vTogbnZvM0BpZXRmLm9yZzsgbDN2cG5AaWV0Zi5vcmcNCtb3
zOI6IEFib3V0IGdhcCBhbmFseXNpcyBvbiBMM1ZQTiBbUkZDNDM2NV0NCg0KSGkgYWxsLA0KDQpJ
IG5vdGljZWQgdGhhdCBMM1ZQTiBbUkZDNDM2NV0gaXMgbGlzdGVkIGFzIG9uZSBvZiB0aGUgY2Fu
ZGlkYXRhIHRlY2hub2xvZ2llcyBpbiB0aGUgTlZvMyBnYXAgYW5hbHlzaXMgZG9jLiBIb3dldmVy
LCBJTUhPLCB0aGUgY3VycmVudCBtZWNoYW5pc20gZGVmaW5lZCBpbiBSRkM0MzY1IGFsb25lIGNv
dWxkbid0IHN1cHBvcnQgVk0gbW9iaWxpdHkgd2hpY2ggaXMgb25lIG9mIHRoZSBiYXNpYyByZXF1
aXJlbWVudHMgb2YgREMgVlBOLiBIZW5jZSwgSSBiZWxpZXZlIGl0J3MgbXVjaCB3b3J0aHdoaWxl
IHRvIGhhdmUgYW4gaW5mb3JtYXRpb25hbCBkcmFmdCBkZXNjcmliaW5nIGhvdyB0byByZXVzZSB0
aGUgTDNWUE4gbWVjaGFuaXNtIGZvciBEQyBWUE4gYmVmb3JlIHBlcmZvcm1pbmcgZ2FwIGFuYWx5
c2lzIG9uIHRoZSBMM1ZQTiB0ZWNobm9sb2d5Lg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpudm8zIG1haWxp
bmcgbGlzdA0KbnZvM0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9udm8zDQo=

From xuxiaohu@huawei.com  Tue Aug 27 20:30:36 2013
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E62E21F9A2E; Tue, 27 Aug 2013 20:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.457
X-Spam-Level: 
X-Spam-Status: No, score=-1.457 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zsrptv8Tfkp2; Tue, 27 Aug 2013 20:30:32 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id BFCC221F9CAD; Tue, 27 Aug 2013 20:30:31 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AWQ71944; Wed, 28 Aug 2013 03:30:28 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 28 Aug 2013 04:29:53 +0100
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 28 Aug 2013 04:30:04 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.199]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.01.0323.007; Wed, 28 Aug 2013 11:29:59 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Eric Gray <eric.gray@ericsson.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>
Subject: re: About gap analysis on L3VPN [RFC4364]
Thread-Topic: About gap analysis on L3VPN [RFC4364]
Thread-Index: AQHOo57fOk8Aig3c0Uqm9wyNHur0Ew==
Date: Wed, 28 Aug 2013 03:29:59 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082006F1@NKGEML512-MBS.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DABBC@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DAE27@NKGEML512-MBS.china.huawei.com> <48E1A67CB9CA044EADFEAB87D814BFF643104B@eusaamb107.ericsson.se>
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF643104B@eusaamb107.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.130]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 03:30:36 -0000

SGkgRXJpYywNCg0KVGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzLCBhbmQgcGxlYXNlIHNlZSBteSBy
ZXNwb25zZSBpbmxpbmUuDQoNCj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+ILeivP7IyzogRXJpYyBH
cmF5IFttYWlsdG86ZXJpYy5ncmF5QGVyaWNzc29uLmNvbV0NCj4gt6LLzcqxvOQ6IDIwMTPE6jjU
wjI4yNUgMzoyMw0KPiDK1bz+yMs6IFh1eGlhb2h1OyBudm8zQGlldGYub3JnOyBsM3ZwbkBpZXRm
Lm9yZw0KPiDW98ziOiBSRTogQWJvdXQgZ2FwIGFuYWx5c2lzIG9uIEwzVlBOIFtSRkM0MzY1XQ0K
PiANCj4gWGlhb2h1LA0KPiANCj4gCVlvdSdyZSBnZXR0aW5nIGFoZWFkIG9mIHRoaW5ncywgYSBi
aXQuDQo+IA0KPiAJSXQgaXMgbm90IHRoZSBwdXJwb3NlIG9mIHRoZSBHYXAgQW5hbHlzaXMgdG8g
ZGV0ZXJtaW5lIGhvdyB0byBmaXggdGhlIGdhcHMuDQo+IFRoZSBwdXJwb3NlIG9mIHRoZSBHYXAg
QW5hbHlzaXMgaXMgdG8gY29tcGFyZSBleGlzdGluZyBjYW5kaWRhdGUgYXBwcm9hY2hlcyB0bw0K
PiB0aGUNCj4gcmVxdWlyZW1lbnRzIGJlaW5nIGRlZmluZWQgaW4gdGhlIE5WTzMgd29ya2luZyBn
cm91cCAtIHRvIGRldGVybWluZSB3aGVyZQ0KPiB0aGUNCj4gZXhpc3RpbmcgY2FuZGlkYXRlIHRl
Y2hub2xvZ2llcy9hcHByb2FjaGVzIG1heSBmYWxsIHNob3J0Lg0KDQpBZ3JlZS4gSG93ZXZlciwg
dGhlIEwzVlBOIHRlY2hub2xvZ3kgQUxPTkUgYXMgZGVzY3JpYmVkIGluIFtSRkM0MzY0XSBpcyB1
bnN1aXRhYmxlIHRvIGJlIGxpc3RlZCBhcyBhIGNhbmRpZGF0ZSBhcHByb2FjaCBzaW5jZSBpdCBh
bG9uZSBjb3VsZG4ndCBhbGxvdyBWTSBtaWdyYXRpb24gd2l0aG91dCBJUCByZW51bWJlcmluZywg
d2hpY2ggaGFzIGJlZW4gcmVjb2duaXplZCBhcyBvbmUgb2YgdGhlIGZ1bmRhbWVudGFsIHJlcXVp
cmVtZW50cyBvZiBEQyBWUE4uIEluc3RlYWQsIHRoZSBjb21iaW5hdGlvbiBvZiBleGlzdGluZyBM
M1ZQTiBhbmQgQVJQIHByb3h5IHRlY2hub2xvZ2llcyBkZXNlcnZlcyB0byBiZSBjb25zaWRlcmVk
IGFzIGFuIGV4aXN0aW5nIGNhbmRpZGF0ZSBhcHByb2FjaC4gVGhlcmVmb3JlLCB3ZSBtYXkgbmVl
ZCBhbiBpbmZvcm1hdGlvbmFsIGRyYWZ0IHdoaWNoIGRlc2NyaWJlcyBob3cgdG8gY29tYmluZSB0
aGUgTDNWUE4gYW5kIEFSUCBwcm94eSB0ZWNobm9sb2dpZXMgZm9yIHN1Ym5ldCBleHRlbnNpb24g
YXMgYSByZWZlcmVuY2UgZm9yIHRoZSBnYXAgYW5hbHlzaXMuIEluIHRoaXMgd2F5LCBpdCB3b3Vs
ZCBiZSBtb3JlIGhlbHBmdWwgZm9yIHVzIHRvIGZpbmQgd2hhdCdzIHN0aWxsIG1pc3NpbmcgaW4g
dGhpcyBjYW5kaWRhdGUgYXBwcm9hY2guDQoNCj4gCUl0IGlzIGFmdGVyIHRoaXMgYW5hbHlzaXMg
aXMgZG9uZSB0aGF0IHdlIC0gYXMgYSB3b3JraW5nIGdyb3VwIC0gd291bGQgdGhlbiBiZQ0KPiBp
biBhIHBvc2l0aW9uIHRvIG1ha2Ugc29tZSBkZWNpc2lvbnMgYXMgdG8gd2hhdCB3b3JrIG1heSBu
ZWVkIHRvIGJlIGRvbmUgZm9yDQo+IGVhY2gNCj4gY2FuZGlkYXRlIGluIG9yZGVyIHRvIG1lZXQg
dGhlIHJlcXVpcmVtZW50cyB3ZSd2ZSBkZXRlcm1pbmVkLg0KPiANCj4gCU9uY2Ugd2UndmUgZG9u
ZSB0aGF0LCB0aGVuIHdlIGNhbiBsb29rIGF0IGZhcm1pbmcgdGhlIHNwZWNpZmljIHdvcmsgb3V0
IHRvDQo+IG90aGVyIHdvcmtpbmcgZ3JvdXBzLCBvciByZS1jaGFydGVyaW5nIE5WTzMgdG8gaW5j
bHVkZSBmaXhpbmcgd2hhdCdzIG1pc3NpbmcuDQo+IA0KPiAJSWYgeW91IGFyZSBhd2FyZSBvZiBz
cGVjaWZpYyBnYXBzIGluIEwzVlBOIHRlY2hub2xvZ2llcyAtIGFnYWluc3Qgc3BlY2lmaWMNCj4g
cmVxdWlyZW1lbnRzIHRoYXQgaGF2ZSBiZWVuIGFncmVlZCBvbiBieSB0aGUgd29ya2luZyBncm91
cCAtIHRoZW4gcGxlYXNlIGxldA0KPiB1cw0KPiBrbm93IHdoYXQgdGhvc2UgZ2FwcyBhcmUgYW5k
IHdlIHdpbGwgZXZhbHVhdGUgaW5jbHVkaW5nIHRoZW0gaW4gdGhlIGdhcA0KPiBhbmFseXNpcw0K
PiBkcmFmdC4NCj4gDQo+IAlBbiBpbmZvcm1hdGlvbiBkcmFmdCBvZiB0aGUgdHlwZSB5b3UgZGVz
Y3JpYmUgaXMgbm90IGN1cnJlbnRseSBpbiBzY29wZSBmb3INCj4gTlZPMywgYXMgaXQgd291bGQg
YmUgZXNzZW50aWFsbHkgYSAic29sdXRpb24iIGRyYWZ0IGZvciB1c2luZyBMM1ZQTi4gIFdlIGNh
bid0DQo+IHN0b3ANCj4geW91IChvciBhbnlvbmUgZWxzZSkgZnJvbSB3cml0aW5nIHN1Y2ggYSBk
cmFmdCwgb2YgY291cnNlLg0KPiANCj4gCUkgdGhpbmsgeW91IChvciB3aG9ldmVyKSBzaG91bGQg
YmUgY2FyZWZ1bCwgaG93ZXZlciwgdG8gZW5zdXJlIHRoYXQgdGhpcw0KPiBkcmFmdCBpcyBhbGln
bmVkIHdpdGggcmVxdWlyZW1lbnRzIGJlaW5nIGRldmVsb3BlZCBhbmQgYWdyZWVkIHRvIGluIE5W
TzMsIG9yIGl0DQo+IGlzIHZlcnkgbGlrZWx5IHRoYXQgYW55IHN1Y2ggZHJhZnQgd2lsbCBzaW1w
bHkgYWRkIHRvIHRoZSBub2lzZSBhdCB0aGUgbW9tZW50Lg0KDQpTdXJlLCB0aGUgaW5mb3JtYXRp
b25hbCBkcmFmdCB0aGF0IEkgbWVudGlvbmVkIGFib3ZlIG5lZWRzIHRvIGJlIGFsaWduZWQgd2l0
aCB0aGUgcmVxdWlyZW1lbnRzIGJlaW5nIGRldmVsb3BlZCBhbmQgYWdyZWVkIHRvIGluIE5WTzMu
ICBIZW5jZSBpdCdzIGJldHRlciB0byBhZG9wdCB0aGlzIGRyYWZ0IGJ5IHRoZSBMM1ZQTiBXRyB3
aXRoIHRoZSByZXZpZXcgb2YgTlZPMyBXRywgSU1ITy4gDQoNCkJlc3QgcmVnYXJkcywNClhpYW9o
dQ0KDQo+IAlBbHNvLCBhbnkgc3VjaCBkcmFmdCBjb3VsZCBub3QgYmUgYWRvcHRlZCBieSB0aGUg
TlZPMyB3b3JraW5nIGdyb3VwIHVudGlsDQo+IGFmdGVyIGl0IGlzIHJlLWNoYXJ0ZXJlZCB0byB3
b3JrIG9uIHNvbHV0aW9ucywgcmVjb21tZW5kZWQgcHJhY3RpY2Ugb3INCj4gYXBwbGljYWJpbGl0
eQ0KPiB3b3JrLg0KPiANCj4gLS0NCj4gRXJpYw0KPiANCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCj4gRnJvbTogbnZvMy1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86bnZvMy1ib3VuY2Vz
QGlldGYub3JnXSBPbiBCZWhhbGYgT2YNCj4gWHV4aWFvaHUNCj4gU2VudDogVGh1cnNkYXksIEF1
Z3VzdCAwMSwgMjAxMyA0OjQ4IEFNDQo+IFRvOiBudm8zQGlldGYub3JnOyBsM3ZwbkBpZXRmLm9y
Zw0KPiBTdWJqZWN0OiBSZTogW252bzNdIEFib3V0IGdhcCBhbmFseXNpcyBvbiBMM1ZQTiBbUkZD
NDM2NV0NCj4gDQo+IEhpIGFsbCwNCj4gDQo+IEknbSBnbGFkIHRvIHNlZSB0aGF0IHRoaXMgaXNz
dWUgaXMgbWVudGlvbmVkIGluIHRoZSBOVm8zIGNoYWlycycgc2xpZGVzIGFzIHdlbGwgKGkuZS4s
DQo+IHNvbWUgcmVmZXJlbmNlcyB0byBMM1ZQTiB0ZWNobm9sb2d5LWJhc2VkIERDIFZQTiBhcHBy
b2FjaGVzIGFyZSB1c2VmdWwpLg0KPiBVbmZvcnR1bmF0ZWx5LCB0aGlzIGlzc3VlIGlzIG5vdCBk
aXNjdXNzZWQgZnVydGhlciBhZnRlciB0aGUgc3VydmV5IG9mIGFkb3B0aW9uIG9mDQo+IE5WR1JF
IGFuZCBWWExBTiBkcmFmdHMuIE15IGRvdWJ0IGlzIGluIHdoaWNoIFdHIHRoZSBMM1ZQTg0KPiB0
ZWNobm9sb2d5LWJhc2VkIERDIFZQTiBkcmFmdHMgc2hvdWxkIGJlIHB1cnN1ZWQgKEwzVlBOIFdH
IG9yIE5WbzMgV0c/KS4NCj4gDQo+IEJlc3QgcmVnYXJkcywNCj4gWGlhb2h1DQo+IA0KPiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ILeivP7IyzogbDN2cG4tYm91
bmNlc0BpZXRmLm9yZyBbbDN2cG4tYm91bmNlc0BpZXRmLm9yZ10gtPqx7SBYdXhpYW9odQ0KPiBb
eHV4aWFvaHVAaHVhd2VpLmNvbV0NCj4gt6LLzcqxvOQ6IDIwMTPE6jfUwjMxyNUgMjI6NDMNCj4g
tb06IG52bzNAaWV0Zi5vcmc7IGwzdnBuQGlldGYub3JnDQo+INb3zOI6IEFib3V0IGdhcCBhbmFs
eXNpcyBvbiBMM1ZQTiBbUkZDNDM2NV0NCj4gDQo+IEhpIGFsbCwNCj4gDQo+IEkgbm90aWNlZCB0
aGF0IEwzVlBOIFtSRkM0MzY1XSBpcyBsaXN0ZWQgYXMgb25lIG9mIHRoZSBjYW5kaWRhdGEgdGVj
aG5vbG9naWVzIGluDQo+IHRoZSBOVm8zIGdhcCBhbmFseXNpcyBkb2MuIEhvd2V2ZXIsIElNSE8s
IHRoZSBjdXJyZW50IG1lY2hhbmlzbSBkZWZpbmVkIGluDQo+IFJGQzQzNjUgYWxvbmUgY291bGRu
J3Qgc3VwcG9ydCBWTSBtb2JpbGl0eSB3aGljaCBpcyBvbmUgb2YgdGhlIGJhc2ljDQo+IHJlcXVp
cmVtZW50cyBvZiBEQyBWUE4uIEhlbmNlLCBJIGJlbGlldmUgaXQncyBtdWNoIHdvcnRod2hpbGUg
dG8gaGF2ZSBhbg0KPiBpbmZvcm1hdGlvbmFsIGRyYWZ0IGRlc2NyaWJpbmcgaG93IHRvIHJldXNl
IHRoZSBMM1ZQTiBtZWNoYW5pc20gZm9yIERDIFZQTg0KPiBiZWZvcmUgcGVyZm9ybWluZyBnYXAg
YW5hbHlzaXMgb24gdGhlIEwzVlBOIHRlY2hub2xvZ3kuDQo+IA0KPiBCZXN0IHJlZ2FyZHMsDQo+
IFhpYW9odQ0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPiBudm8zIG1haWxpbmcgbGlzdA0KPiBudm8zQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vbnZvMw0K

From eric.gray@ericsson.com  Thu Aug 29 15:34:01 2013
Return-Path: <eric.gray@ericsson.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DE8811E8195; Thu, 29 Aug 2013 15:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.245
X-Spam-Level: 
X-Spam-Status: No, score=0.245 tagged_above=-999 required=5 tests=[AWL=-2.298,  BAYES_00=-2.599, CN_BODY_35=0.339, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gu6Wwyhoe-UE; Thu, 29 Aug 2013 15:33:56 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id AC74611E8193; Thu, 29 Aug 2013 15:33:55 -0700 (PDT)
X-AuditID: c6180641-b7fe28e000000d82-c8-521fcc52581a
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 72.FA.03458.25CCF125; Fri, 30 Aug 2013 00:33:55 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0328.009; Thu, 29 Aug 2013 18:33:54 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Xuxiaohu <xuxiaohu@huawei.com>
Subject: RE: About gap analysis on L3VPN [RFC4364]
Thread-Topic: About gap analysis on L3VPN [RFC4364]
Thread-Index: AQHOo57ycfsZznfJ00S0ytMK125qDZmsfqGQ
Date: Thu, 29 Aug 2013 22:33:53 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF6432FC2@eusaamb107.ericsson.se>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DABBC@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DAE27@NKGEML512-MBS.china.huawei.com> <48E1A67CB9CA044EADFEAB87D814BFF643104B@eusaamb107.ericsson.se> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082006F1@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082006F1@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrILMWRmVeSWpSXmKPExsUyuXRPrG7wGfkggxcf2C3Ozve3eDpf0mLr +VWMDsweLUfesnosWfKTKYApissmJTUnsyy1SN8ugStj+Sbrgie+FW0t/5gaGJ94dzFyckgI mEgc2NHEBGGLSVy4t56ti5GLQ0jgKKPE1WUPWCGc5YwS0+4tAqtiE9CQOHZnLSOILSKgJHHr /GZWEJtZwE1iw/0rYHFhASOJrS1fmSFqjCUWLGpmgbCNJDpbPoLVsAioSmzs7AGL8wp4S8za 18wIsWw9k0Tvi19gyzgFwiTevfjIDmIzAp33/dQaJohl4hK3nsyHOltAYsme88wQtqjEy8f/ WCFsZYklT/azQNRrScxr+A3VqygxpfshO8RiQYmTM5+wTGAUm4Vk7CwkLbOQtMxC0rKAkWUV I0dpcWpZbrqR4SZGYLQck2Bz3MG44JPlIUZpDhYlcd4NemcChQTSE0tSs1NTC1KL4otKc1KL DzEycXBKNTBWKF3zv8ZxRuPrl60z1I+wtM+Ki354TuPN4s6bf0/KTL/2QJgx8urbr32r71RO v1ag0JITLyVjo9O57J/YVoHFzHOeO4q2pj3a35l7hIPn1oszkmsWnNrYXmTWp303u0Jg8vFN d7qsZ+7/WdxfyHJR+bbZvCs3N3zXfPQoZUrle8ZnizyjowxalFiKMxINtZiLihMB/Yh4zmQC AAA=
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 22:34:01 -0000

WGlhb2h1LA0KDQoJSSB0aGluayBJIHNlZSB3aGF0IHlvdSBhcmUgZ2V0dGluZyBhdC4NCg0KCVRo
ZSB3YXkgSSBoYWQgYW50aWNpcGF0ZWQgZG9pbmcgdGhpcyBpcyB0byBpbmNvcnBvcmF0ZSBhIGxv
dCBtb3JlIG9mIHRoZQ0KdGV4dCBmcm9tIGRyYWZ0LWJpdGFyLW52bzMtdnBuLWFwcGxpY2FiaWxp
dHkgaW4gdGhlIEdBIGRyYWZ0LiAgSWYgeW91IHJlYWQgdGhhdA0KZHJhZnQsIHlvdSB3aWxsIGZp
bmQgdGhhdCBpdCBoYXMgYSBsb3Qgb2YgdGV4dCBlZmZlY3RpdmVseSBhbmFseXppbmcgbGltaXRh
dGlvbnMgb2YgDQp2YXJpb3VzIGNhbmRpZGF0ZSBhcHByb2FjaGVzIC0gaW5jbHVkaW5nIEwzVlBO
ICh1c2luZyBCR1AvTVBMUyBJUFZQTnMpLg0KDQoJU2VjdGlvbiA3IGlzIGVzc2VudGlhbGx5IGFs
bCBhYm91dCB0aGF0LiAgTW9yZW92ZXIsIHRoZSB0ZXh0IGluIHRoYXQgZHJhZnQNCmlzIG5vdCBz
b2x1dGlvbiBzcGVjaWZpYyBhdCB0aGUgbGV2ZWwgb2YgZGV0YWlsIHRoYXQgeW91J3JlIHN1Z2dl
c3RpbmcuICBJbnN0ZWFkLCBpdA0KbGlzdHMgdGhlICJnYXBzIiAobGlzdGluZyBEeW5hbWljIFBy
b3Zpc2lvbmluZyBhbmQgVk0gTW9iaWxpdHksIGZvciBpbnN0YW5jZSkgLQ0Kd2hpY2ggaXMgd2hh
dCB3ZSBuZWVkIHRvIGRvIGluIHRoZSBHQSBkcmFmdCAoYnV0IG5vdCBmb3IgZXZlcnkgYXBwcm9h
Y2ggd2UNCmFyZSBjdXJyZW50bHkgY29uc2lkZXJpbmcpLg0KDQoJQnV0IHRoZXJlIGlzIGEgbG90
IG9mIHdvcmsgcmVxdWlyZWQgdG8gaW5jb3Jwb3JhdGUgcmVsZXZhbnQgdGV4dCBmcm9tIA0KZHJh
ZnQtYml0YXItbnZvMy12cG4tYXBwbGljYWJpbGl0eSAmIGRyYWZ0LWh5LW52bzMtdnBuLXByb3Rv
Y29sLWdhcC1hbmFseXNpcyANCmludG8gdGhlIEdBIGRyYWZ0Og0KDQogICAgbwlkcmFmdC1iaXRh
ci0uLi4gdXNlcyB0aGUgZnJhbWV3b3JrIGRyYWZ0IGZvciB0aGUgYmFzaXMgb2YgaXRzIGFuYWx5
c2lzOw0KCXRoaXMgbmVlZHMgdG8gYmUgYnJva2VuIGRvd24gaW50byBzZWN0aW9ucyBiYXNlZCBv
biByZXF1aXJlbWVudHMNCglkcmFmdHMsIHRodXMgYWxsb3dpbmcgdXMgdG8gcmVmZXIgdG8gdGhl
IGFwcHJvcHJpYXRlIHNlY3Rpb25zIGluIHRoZQ0KCUdBIHRhYmxlcy4NCiAgICBvCXdlIG5lZWQg
dG8gZGV0ZXJtaW5lIGlmIHRoZXJlIGFyZSBhbHRlcm5hdGl2ZSBMM1ZQTiBhcHByb2FjaGVzDQoJ
KG90aGVyIHRoYW4gQkdQL01QTFMgSVBWUE5zKSBhbmQgcG9zc2libHkgY29udmVyZ2Ugb24gYSBz
aW5nbGUNCgl0ZXJtIHRvIHJlcHJlc2VudCB0aGUgYXBwcm9hY2guDQogICAgbwlzb21lIG9mIHRo
ZSB0ZXh0IG5lZWRzIHRvIGJlIGNsZWFuZWQgdXAgKHJlZmVyZW5jZXMgdG8gODAyLjFRDQoJbmVl
ZCB0byBiZSB1cGRhdGVkIGFuZC9vciBzYW5pdGl6ZWQsIGZvciBpbnN0YW5jZSkuDQogICAgbwl3
ZSBuZWVkIHRvIGdldCBjb252ZXJnZW5jZSBpbiB0aGUgV0cgb24gd2hhdCBzZXQgb2YgYXBwcm9h
Y2hlcw0KCXdlJ3JlIGdvaW5nIHRvIGFuYWx5emUsIGFuZCB0byB3aGF0IGV4dGVudCB3ZSBhcmUg
Z29pbmcgdG8gYW5hbHl6ZQ0KCWVhY2ggYXBwcm9hY2gNCglvCWRyYWZ0LWJpdGFyLS4uLiBpbmNs
dWRlcyBhIG51bWJlciBvZiBWUE4vcmVsYXRlZCB0ZWNobm9sb2dpZXMNCgkJKElQIFZQTiwgVlBM
UywgVlBXUywgUEJCLVZQTFMsIEUtVlBOLCBQQkItRVZQTiwgTDJWUE4sDQoJCVZ4TEFOIC0gdG8g
bmFtZSB0aGUgb25lcyBJIHNhdyBpbiBhIGJyaWVmIHNjYW4gb2YgdGhlIGRyYWZ0KQ0KCW8JZHJh
ZnQtYml0YXItLi4uIGRvZXMgbm90IGluY2x1ZGUgTlZHUkUgYW5kIG1lbnRpb25zIFZ4TEFODQoJ
CW9ubHkgb25jZSAoaW4gcGFzc2luZykuDQoJbwlkcmFmdC1oeS0uLi4gc2VlbXMgcmVzdHJpY3Rl
ZCB0byBhIHNtYWxsZXIgc2V0IG9mIHRlY2hub2xvZ2llcw0KCQkoTDNWUE4sIFZQTFMvRVZQTikg
YW5kIGRvZXMgbm90IGluY2x1ZGUgVnhMQU4gb3IgTlZHUkUuDQoJbwlkcmFmdC1oeS0uLi4gaXMg
Zm9jdXNlZCBvbiBjb250cm9sIHBsYW5lIGFuYWx5c2lzLg0KICAgIG8Jd2UgdGhlbiBuZWVkIHRv
IGRvIHRoZSBhbmFseXNpcyBjb25zaXN0ZW50bHkgYWNyb3NzIGFsbCBhcHByb2FjaGVzDQoJdGhl
IFdHIGhhcyBhZ3JlZWQgdG8gKG9yIGNvbnZlcmdlZCBvbikuDQoNCglBcyBtdWNoIGFzIGl0IHdv
dWxkIGJlIGNvbnZlbmllbnQgdG8gaGF2ZSBhbiBpbmZvcm1hdGlvbmFsIGRyYWZ0IA0KdGhhdCB0
YWxrcyBhYm91dCB0aGUgc2V0IG9mIGVuaGFuY2VtZW50cyB0byBMM1ZQTiB0aGF0IGFyZSBuZWVk
ZWQgZm9yIGENCnF1aWNrIHJlZmVyZW5jZSBwb2ludCBpbiB0aGUgR0EgZHJhZnQsIGl0IHdvdWxk
IG5vdCBiZSBzdWZmZmljaWVudC4NCg0KCUhvd2V2ZXIsIGlmIHlvdSB3YW50ZWQgdG8gcHVyc3Vl
IHRoaXMgaW4gcGFyYWxsZWwgLSBpbiB0aGUgTDNWUE4gV0cNCmZvciBpbnN0YW5jZSAtIHRoYXQg
d291bGQgYmUgZmluZSB3aXRoIG1lLg0KDQotLQ0KRXJpYw0KDQotLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KRnJvbTogWHV4aWFvaHUgW21haWx0bzp4dXhpYW9odUBodWF3ZWkuY29tXSANClNl
bnQ6IFR1ZXNkYXksIEF1Z3VzdCAyNywgMjAxMyAxMTozMCBQTQ0KVG86IEVyaWMgR3JheTsgbnZv
M0BpZXRmLm9yZzsgbDN2cG5AaWV0Zi5vcmcNClN1YmplY3Q6IHJlOiBBYm91dCBnYXAgYW5hbHlz
aXMgb24gTDNWUE4gW1JGQzQzNjRdDQpJbXBvcnRhbmNlOiBIaWdoDQoNCkhpIEVyaWMsDQoNClRo
YW5rcyBmb3IgeW91ciBjb21tZW50cywgYW5kIHBsZWFzZSBzZWUgbXkgcmVzcG9uc2UgaW5saW5l
Lg0KDQo+IC0tLS0t08q8/tStvP4tLS0tLQ0KPiC3orz+yMs6IEVyaWMgR3JheSBbbWFpbHRvOmVy
aWMuZ3JheUBlcmljc3Nvbi5jb21dDQo+ILeiy83KsbzkOiAyMDEzxOo41MIyOMjVIDM6MjMNCj4g
ytW8/sjLOiBYdXhpYW9odTsgbnZvM0BpZXRmLm9yZzsgbDN2cG5AaWV0Zi5vcmcNCj4g1vfM4jog
UkU6IEFib3V0IGdhcCBhbmFseXNpcyBvbiBMM1ZQTiBbUkZDNDM2NV0NCj4gDQo+IFhpYW9odSwN
Cj4gDQo+IAlZb3UncmUgZ2V0dGluZyBhaGVhZCBvZiB0aGluZ3MsIGEgYml0Lg0KPiANCj4gCUl0
IGlzIG5vdCB0aGUgcHVycG9zZSBvZiB0aGUgR2FwIEFuYWx5c2lzIHRvIGRldGVybWluZSBob3cg
dG8gZml4IHRoZSBnYXBzLg0KPiBUaGUgcHVycG9zZSBvZiB0aGUgR2FwIEFuYWx5c2lzIGlzIHRv
IGNvbXBhcmUgZXhpc3RpbmcgY2FuZGlkYXRlIA0KPiBhcHByb2FjaGVzIHRvIHRoZSByZXF1aXJl
bWVudHMgYmVpbmcgZGVmaW5lZCBpbiB0aGUgTlZPMyB3b3JraW5nIGdyb3VwIA0KPiAtIHRvIGRl
dGVybWluZSB3aGVyZSB0aGUgZXhpc3RpbmcgY2FuZGlkYXRlIHRlY2hub2xvZ2llcy9hcHByb2Fj
aGVzIA0KPiBtYXkgZmFsbCBzaG9ydC4NCg0KQWdyZWUuIEhvd2V2ZXIsIHRoZSBMM1ZQTiB0ZWNo
bm9sb2d5IEFMT05FIGFzIGRlc2NyaWJlZCBpbiBbUkZDNDM2NF0gaXMgdW5zdWl0YWJsZSB0byBi
ZSBsaXN0ZWQgYXMgYSBjYW5kaWRhdGUgYXBwcm9hY2ggc2luY2UgaXQgYWxvbmUgY291bGRuJ3Qg
YWxsb3cgVk0gbWlncmF0aW9uIHdpdGhvdXQgSVAgcmVudW1iZXJpbmcsIHdoaWNoIGhhcyBiZWVu
IHJlY29nbml6ZWQgYXMgb25lIG9mIHRoZSBmdW5kYW1lbnRhbCByZXF1aXJlbWVudHMgb2YgREMg
VlBOLiBJbnN0ZWFkLCB0aGUgY29tYmluYXRpb24gb2YgZXhpc3RpbmcgTDNWUE4gYW5kIEFSUCBw
cm94eSB0ZWNobm9sb2dpZXMgZGVzZXJ2ZXMgdG8gYmUgY29uc2lkZXJlZCBhcyBhbiBleGlzdGlu
ZyBjYW5kaWRhdGUgYXBwcm9hY2guIFRoZXJlZm9yZSwgd2UgbWF5IG5lZWQgYW4gaW5mb3JtYXRp
b25hbCBkcmFmdCB3aGljaCBkZXNjcmliZXMgaG93IHRvIGNvbWJpbmUgdGhlIEwzVlBOIGFuZCBB
UlAgcHJveHkgdGVjaG5vbG9naWVzIGZvciBzdWJuZXQgZXh0ZW5zaW9uIGFzIGEgcmVmZXJlbmNl
IGZvciB0aGUgZ2FwIGFuYWx5c2lzLiBJbiB0aGlzIHdheSwgaXQgd291bGQgYmUgbW9yZSBoZWxw
ZnVsIGZvciB1cyB0byBmaW5kIHdoYXQncyBzdGlsbCBtaXNzaW5nIGluIHRoaXMgY2FuZGlkYXRl
IGFwcHJvYWNoLg0KDQo+IAlJdCBpcyBhZnRlciB0aGlzIGFuYWx5c2lzIGlzIGRvbmUgdGhhdCB3
ZSAtIGFzIGEgd29ya2luZyBncm91cCAtIA0KPiB3b3VsZCB0aGVuIGJlIGluIGEgcG9zaXRpb24g
dG8gbWFrZSBzb21lIGRlY2lzaW9ucyBhcyB0byB3aGF0IHdvcmsgbWF5IA0KPiBuZWVkIHRvIGJl
IGRvbmUgZm9yIGVhY2ggY2FuZGlkYXRlIGluIG9yZGVyIHRvIG1lZXQgdGhlIHJlcXVpcmVtZW50
cyANCj4gd2UndmUgZGV0ZXJtaW5lZC4NCj4gDQo+IAlPbmNlIHdlJ3ZlIGRvbmUgdGhhdCwgdGhl
biB3ZSBjYW4gbG9vayBhdCBmYXJtaW5nIHRoZSBzcGVjaWZpYyB3b3JrIA0KPiBvdXQgdG8gb3Ro
ZXIgd29ya2luZyBncm91cHMsIG9yIHJlLWNoYXJ0ZXJpbmcgTlZPMyB0byBpbmNsdWRlIGZpeGlu
ZyB3aGF0J3MgbWlzc2luZy4NCj4gDQo+IAlJZiB5b3UgYXJlIGF3YXJlIG9mIHNwZWNpZmljIGdh
cHMgaW4gTDNWUE4gdGVjaG5vbG9naWVzIC0gYWdhaW5zdCANCj4gc3BlY2lmaWMgcmVxdWlyZW1l
bnRzIHRoYXQgaGF2ZSBiZWVuIGFncmVlZCBvbiBieSB0aGUgd29ya2luZyBncm91cCAtIA0KPiB0
aGVuIHBsZWFzZSBsZXQgdXMga25vdyB3aGF0IHRob3NlIGdhcHMgYXJlIGFuZCB3ZSB3aWxsIGV2
YWx1YXRlIA0KPiBpbmNsdWRpbmcgdGhlbSBpbiB0aGUgZ2FwIGFuYWx5c2lzIGRyYWZ0Lg0KPiAN
Cj4gCUFuIGluZm9ybWF0aW9uIGRyYWZ0IG9mIHRoZSB0eXBlIHlvdSBkZXNjcmliZSBpcyBub3Qg
Y3VycmVudGx5IGluIA0KPiBzY29wZSBmb3IgTlZPMywgYXMgaXQgd291bGQgYmUgZXNzZW50aWFs
bHkgYSAic29sdXRpb24iIGRyYWZ0IGZvciANCj4gdXNpbmcgTDNWUE4uICBXZSBjYW4ndCBzdG9w
IHlvdSAob3IgYW55b25lIGVsc2UpIGZyb20gd3JpdGluZyBzdWNoIGEgDQo+IGRyYWZ0LCBvZiBj
b3Vyc2UuDQo+IA0KPiAJSSB0aGluayB5b3UgKG9yIHdob2V2ZXIpIHNob3VsZCBiZSBjYXJlZnVs
LCBob3dldmVyLCB0byBlbnN1cmUgdGhhdCANCj4gdGhpcyBkcmFmdCBpcyBhbGlnbmVkIHdpdGgg
cmVxdWlyZW1lbnRzIGJlaW5nIGRldmVsb3BlZCBhbmQgYWdyZWVkIHRvIA0KPiBpbiBOVk8zLCBv
ciBpdCBpcyB2ZXJ5IGxpa2VseSB0aGF0IGFueSBzdWNoIGRyYWZ0IHdpbGwgc2ltcGx5IGFkZCB0
byB0aGUgbm9pc2UgYXQgdGhlIG1vbWVudC4NCg0KU3VyZSwgdGhlIGluZm9ybWF0aW9uYWwgZHJh
ZnQgdGhhdCBJIG1lbnRpb25lZCBhYm92ZSBuZWVkcyB0byBiZSBhbGlnbmVkIHdpdGggdGhlIHJl
cXVpcmVtZW50cyBiZWluZyBkZXZlbG9wZWQgYW5kIGFncmVlZCB0byBpbiBOVk8zLiAgSGVuY2Ug
aXQncyBiZXR0ZXIgdG8gYWRvcHQgdGhpcyBkcmFmdCBieSB0aGUgTDNWUE4gV0cgd2l0aCB0aGUg
cmV2aWV3IG9mIE5WTzMgV0csIElNSE8uIA0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0KPiAJ
QWxzbywgYW55IHN1Y2ggZHJhZnQgY291bGQgbm90IGJlIGFkb3B0ZWQgYnkgdGhlIE5WTzMgd29y
a2luZyBncm91cCANCj4gdW50aWwgYWZ0ZXIgaXQgaXMgcmUtY2hhcnRlcmVkIHRvIHdvcmsgb24g
c29sdXRpb25zLCByZWNvbW1lbmRlZCANCj4gcHJhY3RpY2Ugb3IgYXBwbGljYWJpbGl0eSB3b3Jr
Lg0KPiANCj4gLS0NCj4gRXJpYw0KPiANCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4g
RnJvbTogbnZvMy1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86bnZvMy1ib3VuY2VzQGlldGYub3Jn
XSBPbiBCZWhhbGYgDQo+IE9mIFh1eGlhb2h1DQo+IFNlbnQ6IFRodXJzZGF5LCBBdWd1c3QgMDEs
IDIwMTMgNDo0OCBBTQ0KPiBUbzogbnZvM0BpZXRmLm9yZzsgbDN2cG5AaWV0Zi5vcmcNCj4gU3Vi
amVjdDogUmU6IFtudm8zXSBBYm91dCBnYXAgYW5hbHlzaXMgb24gTDNWUE4gW1JGQzQzNjVdDQo+
IA0KPiBIaSBhbGwsDQo+IA0KPiBJJ20gZ2xhZCB0byBzZWUgdGhhdCB0aGlzIGlzc3VlIGlzIG1l
bnRpb25lZCBpbiB0aGUgTlZvMyBjaGFpcnMnIA0KPiBzbGlkZXMgYXMgd2VsbCAoaS5lLiwgc29t
ZSByZWZlcmVuY2VzIHRvIEwzVlBOIHRlY2hub2xvZ3ktYmFzZWQgREMgVlBOIGFwcHJvYWNoZXMg
YXJlIHVzZWZ1bCkuDQo+IFVuZm9ydHVuYXRlbHksIHRoaXMgaXNzdWUgaXMgbm90IGRpc2N1c3Nl
ZCBmdXJ0aGVyIGFmdGVyIHRoZSBzdXJ2ZXkgb2YgDQo+IGFkb3B0aW9uIG9mIE5WR1JFIGFuZCBW
WExBTiBkcmFmdHMuIE15IGRvdWJ0IGlzIGluIHdoaWNoIFdHIHRoZSBMM1ZQTiANCj4gdGVjaG5v
bG9neS1iYXNlZCBEQyBWUE4gZHJhZnRzIHNob3VsZCBiZSBwdXJzdWVkIChMM1ZQTiBXRyBvciBO
Vm8zIFdHPykuDQo+IA0KPiBCZXN0IHJlZ2FyZHMsDQo+IFhpYW9odQ0KPiANCj4gX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiC3orz+yMs6IGwzdnBuLWJvdW5jZXNA
aWV0Zi5vcmcgW2wzdnBuLWJvdW5jZXNAaWV0Zi5vcmddILT6se0gWHV4aWFvaHUgDQo+IFt4dXhp
YW9odUBodWF3ZWkuY29tXQ0KPiC3osvNyrG85DogMjAxM8TqN9TCMzHI1SAyMjo0Mw0KPiC1vTog
bnZvM0BpZXRmLm9yZzsgbDN2cG5AaWV0Zi5vcmcNCj4g1vfM4jogQWJvdXQgZ2FwIGFuYWx5c2lz
IG9uIEwzVlBOIFtSRkM0MzY1XQ0KPiANCj4gSGkgYWxsLA0KPiANCj4gSSBub3RpY2VkIHRoYXQg
TDNWUE4gW1JGQzQzNjVdIGlzIGxpc3RlZCBhcyBvbmUgb2YgdGhlIGNhbmRpZGF0YSANCj4gdGVj
aG5vbG9naWVzIGluIHRoZSBOVm8zIGdhcCBhbmFseXNpcyBkb2MuIEhvd2V2ZXIsIElNSE8sIHRo
ZSBjdXJyZW50IA0KPiBtZWNoYW5pc20gZGVmaW5lZCBpbg0KPiBSRkM0MzY1IGFsb25lIGNvdWxk
bid0IHN1cHBvcnQgVk0gbW9iaWxpdHkgd2hpY2ggaXMgb25lIG9mIHRoZSBiYXNpYyANCj4gcmVx
dWlyZW1lbnRzIG9mIERDIFZQTi4gSGVuY2UsIEkgYmVsaWV2ZSBpdCdzIG11Y2ggd29ydGh3aGls
ZSB0byBoYXZlIA0KPiBhbiBpbmZvcm1hdGlvbmFsIGRyYWZ0IGRlc2NyaWJpbmcgaG93IHRvIHJl
dXNlIHRoZSBMM1ZQTiBtZWNoYW5pc20gZm9yIA0KPiBEQyBWUE4gYmVmb3JlIHBlcmZvcm1pbmcg
Z2FwIGFuYWx5c2lzIG9uIHRoZSBMM1ZQTiB0ZWNobm9sb2d5Lg0KPiANCj4gQmVzdCByZWdhcmRz
LA0KPiBYaWFvaHUNCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4gbnZvMyBtYWlsaW5nIGxpc3QNCj4gbnZvM0BpZXRmLm9yZw0KPiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL252bzMNCg==

From truman@versionsix.org  Thu Aug 29 13:53:38 2013
Return-Path: <truman@versionsix.org>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 015A311E8134 for <l3vpn@ietfa.amsl.com>; Thu, 29 Aug 2013 13:53:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.413
X-Spam-Level: 
X-Spam-Status: No, score=0.413 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WYYbBQgSEDPA for <l3vpn@ietfa.amsl.com>; Thu, 29 Aug 2013 13:53:37 -0700 (PDT)
Received: from mail-ee0-f51.google.com (mail-ee0-f51.google.com [74.125.83.51]) by ietfa.amsl.com (Postfix) with ESMTP id A47ED11E817D for <l3vpn@ietf.org>; Thu, 29 Aug 2013 13:53:27 -0700 (PDT)
Received: by mail-ee0-f51.google.com with SMTP id c1so492106eek.24 for <l3vpn@ietf.org>; Thu, 29 Aug 2013 13:53:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=kQqSRsKEGS7okWAhtg1fgE2poOScw4saQvV3rZqUNmA=; b=BVxXIqsNs9cM6rXqegmjB28kYXEJHbPM75IxwyCuiAAW1X7Unn/o6MoeTvmUMur8JN /WImxm90R30e7B+2V+leo30qqEV7ZwYRI84AguwVbe33Vyvdcc/IOx5MP+npjSrQvtx9 5OLuVr8S68JZ5nR2oUMSu06soU9TnOpf1QcZxqFjKYR4WORQX+oZ0dfdNja+x5g2vEia tzXLKpFjxwc5NsaRU/xs4HrI7CRwjszeJsFhTx5WDeOEqNLZg30Iv0rFnkCK+Rvfhd6H 7fGBNIE3afTUXks9iiaIOjneP8FxwdvE1mt9eoPg8nom0lSro0m+sHCPVjVImweEYkNo jCyQ==
X-Gm-Message-State: ALoCoQlrcj6SD7FLClI2D3pKQ+J1IqA2HBo7uPZvVdhKhHjNht2rwrA/QZmWgt/MW9Be2uVtYuIN
MIME-Version: 1.0
X-Received: by 10.15.74.197 with SMTP id j45mr6791933eey.40.1377809606559; Thu, 29 Aug 2013 13:53:26 -0700 (PDT)
Received: by 10.223.84.133 with HTTP; Thu, 29 Aug 2013 13:53:26 -0700 (PDT)
X-Originating-IP: [208.54.45.133]
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082006F1@NKGEML512-MBS.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DABBC@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DAE27@NKGEML512-MBS.china.huawei.com> <48E1A67CB9CA044EADFEAB87D814BFF643104B@eusaamb107.ericsson.se> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082006F1@NKGEML512-MBS.china.huawei.com>
Date: Thu, 29 Aug 2013 16:53:26 -0400
Message-ID: <CAOZewqZAsE6czLSeJB3FsqJrbUiSuOxMKbmJts=_giqcN2SwUw@mail.gmail.com>
Subject: Re: [nvo3] About gap analysis on L3VPN [RFC4364]
From: Truman Boyes <truman@versionsix.org>
To: Xuxiaohu <xuxiaohu@huawei.com>
Content-Type: multipart/alternative; boundary=001a11c398082af40f04e51c4c50
X-Mailman-Approved-At: Fri, 30 Aug 2013 00:45:16 -0700
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 20:53:38 -0000

--001a11c398082af40f04e51c4c50
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Xiaohu,

You raise a good point. The keyword is *ALONE*; without the additional
functionality added to L3VPN, it would not be a suitable candidate for DC
VPN. Items to discuss would be host-routing(ie. /32, /128), arp proxy, and
arp localisation.

Truman


On Tue, Aug 27, 2013 at 11:29 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:

> Hi Eric,
>
> Thanks for your comments, and please see my response inline.
>
> > -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> > =B7=A2=BC=FE=C8=CB: Eric Gray [mailto:eric.gray@ericsson.com]
> > =B7=A2=CB=CD=CA=B1=BC=E4: 2013=C4=EA8=D4=C228=C8=D5 3:23
> > =CA=D5=BC=FE=C8=CB: Xuxiaohu; nvo3@ietf.org; l3vpn@ietf.org
> > =D6=F7=CC=E2: RE: About gap analysis on L3VPN [RFC4365]
> >
> > Xiaohu,
> >
> >       You're getting ahead of things, a bit.
> >
> >       It is not the purpose of the Gap Analysis to determine how to fix
> the gaps.
> > The purpose of the Gap Analysis is to compare existing candidate
> approaches to
> > the
> > requirements being defined in the NVO3 working group - to determine whe=
re
> > the
> > existing candidate technologies/approaches may fall short.
>
> Agree. However, the L3VPN technology ALONE as described in [RFC4364] is
> unsuitable to be listed as a candidate approach since it alone couldn't
> allow VM migration without IP renumbering, which has been recognized as o=
ne
> of the fundamental requirements of DC VPN. Instead, the combination of
> existing L3VPN and ARP proxy technologies deserves to be considered as an
> existing candidate approach. Therefore, we may need an informational draf=
t
> which describes how to combine the L3VPN and ARP proxy technologies for
> subnet extension as a reference for the gap analysis. In this way, it wou=
ld
> be more helpful for us to find what's still missing in this candidate
> approach.
>
> >       It is after this analysis is done that we - as a working group -
> would then be
> > in a position to make some decisions as to what work may need to be don=
e
> for
> > each
> > candidate in order to meet the requirements we've determined.
> >
> >       Once we've done that, then we can look at farming the specific
> work out to
> > other working groups, or re-chartering NVO3 to include fixing what's
> missing.
> >
> >       If you are aware of specific gaps in L3VPN technologies - against
> specific
> > requirements that have been agreed on by the working group - then pleas=
e
> let
> > us
> > know what those gaps are and we will evaluate including them in the gap
> > analysis
> > draft.
> >
> >       An information draft of the type you describe is not currently in
> scope for
> > NVO3, as it would be essentially a "solution" draft for using L3VPN.  W=
e
> can't
> > stop
> > you (or anyone else) from writing such a draft, of course.
> >
> >       I think you (or whoever) should be careful, however, to ensure
> that this
> > draft is aligned with requirements being developed and agreed to in
> NVO3, or it
> > is very likely that any such draft will simply add to the noise at the
> moment.
>
> Sure, the informational draft that I mentioned above needs to be aligned
> with the requirements being developed and agreed to in NVO3.  Hence it's
> better to adopt this draft by the L3VPN WG with the review of NVO3 WG, IM=
HO.
>
> Best regards,
> Xiaohu
>
> >       Also, any such draft could not be adopted by the NVO3 working
> group until
> > after it is re-chartered to work on solutions, recommended practice or
> > applicability
> > work.
> >
> > --
> > Eric
> >
> > -----Original Message-----
> > From: nvo3-bounces@ietf.org [mailto:nvo3-bounces@ietf.org] On Behalf Of
> > Xuxiaohu
> > Sent: Thursday, August 01, 2013 4:48 AM
> > To: nvo3@ietf.org; l3vpn@ietf.org
> > Subject: Re: [nvo3] About gap analysis on L3VPN [RFC4365]
> >
> > Hi all,
> >
> > I'm glad to see that this issue is mentioned in the NVo3 chairs' slides
> as well (i.e.,
> > some references to L3VPN technology-based DC VPN approaches are useful)=
.
> > Unfortunately, this issue is not discussed further after the survey of
> adoption of
> > NVGRE and VXLAN drafts. My doubt is in which WG the L3VPN
> > technology-based DC VPN drafts should be pursued (L3VPN WG or NVo3 WG?)=
.
> >
> > Best regards,
> > Xiaohu
> >
> > ________________________________________
> > =B7=A2=BC=FE=C8=CB: l3vpn-bounces@ietf.org [l3vpn-bounces@ietf.org] =B4=
=FA=B1=ED Xuxiaohu
> > [xuxiaohu@huawei.com]
> > =B7=A2=CB=CD=CA=B1=BC=E4: 2013=C4=EA7=D4=C231=C8=D5 22:43
> > =B5=BD: nvo3@ietf.org; l3vpn@ietf.org
> > =D6=F7=CC=E2: About gap analysis on L3VPN [RFC4365]
> >
> > Hi all,
> >
> > I noticed that L3VPN [RFC4365] is listed as one of the candidata
> technologies in
> > the NVo3 gap analysis doc. However, IMHO, the current mechanism defined
> in
> > RFC4365 alone couldn't support VM mobility which is one of the basic
> > requirements of DC VPN. Hence, I believe it's much worthwhile to have a=
n
> > informational draft describing how to reuse the L3VPN mechanism for DC
> VPN
> > before performing gap analysis on the L3VPN technology.
> >
> > Best regards,
> > Xiaohu
> > _______________________________________________
> > nvo3 mailing list
> > nvo3@ietf.org
> > https://www.ietf.org/mailman/listinfo/nvo3
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>

--001a11c398082af40f04e51c4c50
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Xiaohu,&nbsp;<div><br></div><div>You raise a good point. T=
he keyword is *ALONE*; without the additional functionality added to L3VPN,=
 it would not be a suitable candidate for DC VPN. Items to discuss would be=
 host-routing(ie. /32, /128), arp proxy, and arp localisation.&nbsp;</div>
<div><br></div><div>Truman&nbsp;</div></div><div class=3D"gmail_extra"><br>=
<br><div class=3D"gmail_quote">On Tue, Aug 27, 2013 at 11:29 PM, Xuxiaohu <=
span dir=3D"ltr">&lt;<a href=3D"mailto:xuxiaohu@huawei.com" target=3D"_blan=
k">xuxiaohu@huawei.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Eric,<br>
<br>
Thanks for your comments, and please see my response inline.<br>
<br>
&gt; -----=D3=CA=BC=FE=D4=AD=BC=FE-----<br>
&gt; =B7=A2=BC=FE=C8=CB: Eric Gray [mailto:<a href=3D"mailto:eric.gray@eric=
sson.com">eric.gray@ericsson.com</a>]<br>
&gt; =B7=A2=CB=CD=CA=B1=BC=E4: 2013=C4=EA8=D4=C228=C8=D5 3:23<br>
&gt; =CA=D5=BC=FE=C8=CB: Xuxiaohu; <a href=3D"mailto:nvo3@ietf.org">nvo3@ie=
tf.org</a>; <a href=3D"mailto:l3vpn@ietf.org">l3vpn@ietf.org</a><br>
&gt; =D6=F7=CC=E2: RE: About gap analysis on L3VPN [RFC4365]<br>
&gt;<br>
&gt; Xiaohu,<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; You&#39;re getting ahead of things, a bit.<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; It is not the purpose of the Gap Analysis to dete=
rmine how to fix the gaps.<br>
&gt; The purpose of the Gap Analysis is to compare existing candidate appro=
aches to<br>
&gt; the<br>
&gt; requirements being defined in the NVO3 working group - to determine wh=
ere<br>
&gt; the<br>
&gt; existing candidate technologies/approaches may fall short.<br>
<br>
Agree. However, the L3VPN technology ALONE as described in [RFC4364] is uns=
uitable to be listed as a candidate approach since it alone couldn&#39;t al=
low VM migration without IP renumbering, which has been recognized as one o=
f the fundamental requirements of DC VPN. Instead, the combination of exist=
ing L3VPN and ARP proxy technologies deserves to be considered as an existi=
ng candidate approach. Therefore, we may need an informational draft which =
describes how to combine the L3VPN and ARP proxy technologies for subnet ex=
tension as a reference for the gap analysis. In this way, it would be more =
helpful for us to find what&#39;s still missing in this candidate approach.=
<br>

<br>
&gt; &nbsp; &nbsp; &nbsp; It is after this analysis is done that we - as a =
working group - would then be<br>
&gt; in a position to make some decisions as to what work may need to be do=
ne for<br>
&gt; each<br>
&gt; candidate in order to meet the requirements we&#39;ve determined.<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; Once we&#39;ve done that, then we can look at far=
ming the specific work out to<br>
&gt; other working groups, or re-chartering NVO3 to include fixing what&#39=
;s missing.<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; If you are aware of specific gaps in L3VPN techno=
logies - against specific<br>
&gt; requirements that have been agreed on by the working group - then plea=
se let<br>
&gt; us<br>
&gt; know what those gaps are and we will evaluate including them in the ga=
p<br>
&gt; analysis<br>
&gt; draft.<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; An information draft of the type you describe is =
not currently in scope for<br>
&gt; NVO3, as it would be essentially a &quot;solution&quot; draft for usin=
g L3VPN. &nbsp;We can&#39;t<br>
&gt; stop<br>
&gt; you (or anyone else) from writing such a draft, of course.<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; I think you (or whoever) should be careful, howev=
er, to ensure that this<br>
&gt; draft is aligned with requirements being developed and agreed to in NV=
O3, or it<br>
&gt; is very likely that any such draft will simply add to the noise at the=
 moment.<br>
<br>
Sure, the informational draft that I mentioned above needs to be aligned wi=
th the requirements being developed and agreed to in NVO3. &nbsp;Hence it&#=
39;s better to adopt this draft by the L3VPN WG with the review of NVO3 WG,=
 IMHO.<br>

<br>
Best regards,<br>
Xiaohu<br>
<br>
&gt; &nbsp; &nbsp; &nbsp; Also, any such draft could not be adopted by the =
NVO3 working group until<br>
&gt; after it is re-chartered to work on solutions, recommended practice or=
<br>
&gt; applicability<br>
&gt; work.<br>
&gt;<br>
&gt; --<br>
&gt; Eric<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:nvo3-bounces@ietf.org">nvo3-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:nvo3-bounces@ietf.org">nvo3-bounces@ietf.org</=
a>] On Behalf Of<br>
&gt; Xuxiaohu<br>
&gt; Sent: Thursday, August 01, 2013 4:48 AM<br>
&gt; To: <a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a>; <a href=3D"mai=
lto:l3vpn@ietf.org">l3vpn@ietf.org</a><br>
&gt; Subject: Re: [nvo3] About gap analysis on L3VPN [RFC4365]<br>
&gt;<br>
&gt; Hi all,<br>
&gt;<br>
&gt; I&#39;m glad to see that this issue is mentioned in the NVo3 chairs&#3=
9; slides as well (i.e.,<br>
&gt; some references to L3VPN technology-based DC VPN approaches are useful=
).<br>
&gt; Unfortunately, this issue is not discussed further after the survey of=
 adoption of<br>
&gt; NVGRE and VXLAN drafts. My doubt is in which WG the L3VPN<br>
&gt; technology-based DC VPN drafts should be pursued (L3VPN WG or NVo3 WG?=
).<br>
&gt;<br>
&gt; Best regards,<br>
&gt; Xiaohu<br>
&gt;<br>
&gt; ________________________________________<br>
&gt; =B7=A2=BC=FE=C8=CB: <a href=3D"mailto:l3vpn-bounces@ietf.org">l3vpn-bo=
unces@ietf.org</a> [<a href=3D"mailto:l3vpn-bounces@ietf.org">l3vpn-bounces=
@ietf.org</a>] =B4=FA=B1=ED Xuxiaohu<br>
&gt; [<a href=3D"mailto:xuxiaohu@huawei.com">xuxiaohu@huawei.com</a>]<br>
&gt; =B7=A2=CB=CD=CA=B1=BC=E4: 2013=C4=EA7=D4=C231=C8=D5 22:43<br>
&gt; =B5=BD: <a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a>; <a href=3D=
"mailto:l3vpn@ietf.org">l3vpn@ietf.org</a><br>
&gt; =D6=F7=CC=E2: About gap analysis on L3VPN [RFC4365]<br>
&gt;<br>
&gt; Hi all,<br>
&gt;<br>
&gt; I noticed that L3VPN [RFC4365] is listed as one of the candidata techn=
ologies in<br>
&gt; the NVo3 gap analysis doc. However, IMHO, the current mechanism define=
d in<br>
&gt; RFC4365 alone couldn&#39;t support VM mobility which is one of the bas=
ic<br>
&gt; requirements of DC VPN. Hence, I believe it&#39;s much worthwhile to h=
ave an<br>
&gt; informational draft describing how to reuse the L3VPN mechanism for DC=
 VPN<br>
&gt; before performing gap analysis on the L3VPN technology.<br>
&gt;<br>
&gt; Best regards,<br>
&gt; Xiaohu<br>
&gt; _______________________________________________<br>
&gt; nvo3 mailing list<br>
&gt; <a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/nvo3</a><br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/nvo3</a><br>
</blockquote></div><br></div>

--001a11c398082af40f04e51c4c50--

From internet-drafts@ietf.org  Fri Aug 30 08:23:42 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1D7911E8115; Fri, 30 Aug 2013 08:23:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GuTpzZoLjd1n; Fri, 30 Aug 2013 08:23:42 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD2F11E80FA; Fri, 30 Aug 2013 08:23:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-l3vpn-mvpn-mib-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130830152342.1761.86426.idtracker@ietfa.amsl.com>
Date: Fri, 30 Aug 2013 08:23:42 -0700
Cc: l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 15:23:43 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Layer 3 Virtual Private Networks Working =
Group of the IETF.

	Title           : MPLS/BGP Layer 3 VPN Multicast Management Information Ba=
se
	Author(s)       : Saud Asif
                          Andy Green
                          Sameer Gulrajani
                          Pradeep G. Jain
                          Jeffrey (Zhaohui) Zhang
	Filename        : draft-ietf-l3vpn-mvpn-mib-03.txt
	Pages           : 28
	Date            : 2013-08-29

Abstract:
   This memo defines an portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.

   In particular, it describes managed objects to configure and/or
   monitor multicast in MPLS/BGP-based Layer-3 VPN (MVPN) on an MVPN
   router.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-l3vpn-mvpn-mib

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-l3vpn-mvpn-mib-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l3vpn-mvpn-mib-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

