From david.freedman@uk.clara.net Fri Apr 13 09:26:07 2012 Return-Path: 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 6719E21F8811 for ; Fri, 13 Apr 2012 09:26:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.583 X-Spam-Level: X-Spam-Status: No, score=-0.583 tagged_above=-999 required=5 tests=[AWL=0.465, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.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 ceCQgrCNem+0 for ; Fri, 13 Apr 2012 09:26:07 -0700 (PDT) Received: from staff01.mail.eu.clara.net (staff01.mail.eu.clara.net [IPv6:2001:a88:0:fff7::54]) by ietfa.amsl.com (Postfix) with ESMTP id BE99421F8810 for ; Fri, 13 Apr 2012 09:26:06 -0700 (PDT) Received: from [195.157.10.59] (port=31507 helo=SRVGREXCAS04.claranet.local) by staff01.mail.eu.clara.net (staff01.mail.eu.clara.net [80.168.65.54]:25) with esmtps (TLS-1.0:RSA_AES_128_CBC_SHA1:16) id 1SIjK0-00030S-6H for l3vpn@ietf.org (return-path ); Fri, 13 Apr 2012 16:26:05 +0000 Received: from SRVGREXMB03.claranet.local ([10.75.5.26]) by SRVGREXCAS04.claranet.local ([fe80::95c2:9976:e52:fe51%11]) with mapi id 14.01.0339.001; Fri, 13 Apr 2012 17:26:04 +0100 From: David Freedman To: "l3vpn@ietf.org" Subject: Re: draft-freedman-l3vpn-ospf2-4364-ce-00.txt (was Re: RFC4577 Question) Thread-Topic: draft-freedman-l3vpn-ospf2-4364-ce-00.txt (was Re: RFC4577 Question) Thread-Index: AQHM9wyu47Qu7U4z006zqZ6KwGRdx5aZNh8A Date: Fri, 13 Apr 2012 16:26:03 +0000 Message-ID: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.14.0.111121 x-originating-ip: [172.18.6.3] Content-Type: text/plain; charset="us-ascii" Content-ID: <0CA4DCF7C4BCE2439A0A8A2998B2B987@claranet.local> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BorderScout-Spam: 0.00 X-BorderScout-Virus: clean X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2012 16:26:07 -0000 Hi, I've had no feedback on this (good or bad) so I intend to ask the chairs to poll for whether the document could be adopted by the working group. David. On 29/02/2012 18:05, "David Freedman" wrote: >Dear All, > >After speaking with Ben, I've decided to publish a document on what >changes to RFC4577 behaviour I believe >should occur in order to adapt this standard for operation between CE/C >routers, I am seeking feedback on this work. > >I am also aware of draft-ietf-l3vpn-ospfv3-pece-11 and would ask that in >addition, the authors of this document also step forward >and comment as to whether they feel any of this could be applicable to >their efforts. > >Regards, > >David Freedman > > > >On 29/02/2012 16:18, "internet-drafts@ietf.org" >wrote: > >>A new version of I-D, draft-freedman-l3vpn-ospf2-4364-ce-00.txt has been >>successfully submitted by David Freedman and posted to the IETF >>repository. >> >>Filename: draft-freedman-l3vpn-ospf2-4364-ce >>Revision: 00 >>Title: OSPF Version 2 as the Customer Edge/Customer Protocol for >>BGP/MPLS IP VPNs >>Creation date: 2012-02-29 >>WG ID: Individual Submission >>Number of pages: 11 >> >>Abstract: >> RFC4577 (OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP >> VPNs) proposes a mechanism for the use of the Open Shortest Path >> First V2 ("OSPF") protocol between the Provider Edge ("PE") >> and Customer Edge ("CE") routers within a BGP/MPLS IP Virtual Private >> Network ("IP/VPN", RFC4364). >> >> The standard provides for use of such a provider VPN to join >> discontiguous locations together, preserving the OSPF area and domain >> behaviour. >> >> This document describes a technique for utilising the same, IPVPN >> network infrastructure without the requirement to enable the OSPF >> protocol on the PE/CE interface and thus relieve the PE router of >> OSPF duties. >> >> =20 >> =20 >> >> >>The IETF Secretariat > From internet-drafts@ietf.org Thu Apr 19 11:51:06 2012 Return-Path: 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 27A7121F861D; Thu, 19 Apr 2012 11:51:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.498 X-Spam-Level: X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, 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 wHzpI31vUBUb; Thu, 19 Apr 2012 11:50:58 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE77121F85F1; Thu, 19 Apr 2012 11:50:56 -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-virtual-hub-01.txt X-Test-IDTracker: no X-IETF-IDTracker: 4.00 Message-ID: <20120419185055.20185.26217.idtracker@ietfa.amsl.com> Date: Thu, 19 Apr 2012 11:50:55 -0700 Cc: l3vpn@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2012 18:51:06 -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 Work= ing Group of the IETF. Title : Virtual Hub-and-Spoke in BGP/MPLS VPNs Author(s) : Huajin Jeng James Uttaro Luay Jalil Bruno Decraene Yakov Rekhter Rahul Aggarwal Filename : draft-ietf-l3vpn-virtual-hub-01.txt Pages : 22 Date : 2012-04-19 With BGP/MPLS VPNs any-to-any connectivity among sites of a given Virtual Private Network would require each Provider Edge router that has one or more of these sites connected to it to hold all the routes of that Virtual Private Network. The approach described in this document allows to reduce the number of Provider Edge routers that have to maintain all these routes by requiring only a subset of these routers to maintain all these routes. Furthermore, when Provider Edge routers use ingress replication to carry multicast traffic of VPN customers, the approach described in this document could allow to reduce bandwidth inefficiency associated with ingress replication, and to redistribute the replication load among Provider Edge routers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-virtual-hub-01.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-l3vpn-virtual-hub-01.txt From stbryant@cisco.com Fri Apr 20 07:15:40 2012 Return-Path: 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 7563321F8735; Fri, 20 Apr 2012 07:15:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.255 X-Spam-Level: X-Spam-Status: No, score=-110.255 tagged_above=-999 required=5 tests=[AWL=-0.256, BAYES_00=-2.599, 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 f+DXwGy7w5l8; Fri, 20 Apr 2012 07:15:39 -0700 (PDT) Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC4A21F871E; Fri, 20 Apr 2012 07:15:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=483; q=dns/txt; s=iport; t=1334931338; x=1336140938; h=message-id:date:from:reply-to:mime-version:to:cc:subject: content-transfer-encoding; bh=iyicn5gtMwlehF9gJIv9x9jW27qH0I0PkbyHiFcFzL4=; b=IioZ867NICjoN4NwuIUnunhpCAON1a75k6h/OO5LsZBmRW624tEWihKH ZOq1ED98SnYadEz97lkuSEbrJo97u3AgG4gFlGbH5DN3+iMVxNdaDeMwS jFHWnU/JHPwDP+aYxcpPRooEThe+QXab0eM3aVO5EIeXeHeCfHA4ACJPU c=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EAFNvkU+Q/khM/2dsb2JhbABEsTiBB4IiAQIjQAE8FhgDAgECAS8cAQwBBQIBAR6HbZpngz8QgU6bFpBnBJV5jlSBAmeCaA X-IronPort-AV: E=Sophos;i="4.75,453,1330905600"; d="scan'208";a="71384632" Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 20 Apr 2012 14:15:32 +0000 Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q3KEFVGq005117; Fri, 20 Apr 2012 14:15:32 GMT Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q3KEFU0V027884; Fri, 20 Apr 2012 15:15:31 +0100 (BST) Message-ID: <4F916F82.6050105@cisco.com> Date: Fri, 20 Apr 2012 15:15:30 +0100 From: Stewart Bryant User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: L3VPN WG mailing list , thomas.morin@orange.com, "'Martin Vigoureux'" Subject: L3VPN Chairs Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Adrian Farrel , "iesg@ietf.org" X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: stbryant@cisco.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2012 14:15:40 -0000 I would like to announce that I am appointing : Thomas Morin and Martin Vigoureux as chairs of the L3VPN Working group. I would like to thank them for agreeing to take on this responsibility and would request that you support them as they get up to speed with completing the existing L3VPN work and considering how the WG addresses the new technical challenges in this area. Regards Stewart From marshall.eubanks@gmail.com Fri Apr 20 09:42:21 2012 Return-Path: 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 7C1A121F8644; Fri, 20 Apr 2012 09:42:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.281 X-Spam-Level: X-Spam-Status: No, score=-103.281 tagged_above=-999 required=5 tests=[AWL=-0.282, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, 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 WI6m96pme-Sf; Fri, 20 Apr 2012 09:42:21 -0700 (PDT) Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 79C6821F863B; Fri, 20 Apr 2012 09:42:20 -0700 (PDT) Received: by lbgc1 with SMTP id c1so3288689lbg.31 for ; Fri, 20 Apr 2012 09:42:19 -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 :content-type; bh=xQTWzKDbo5nh5otkAQv9auX8sV3d1CAUU556dCT7ztE=; b=dNb21dIn2wb5UxZyugnE9Kn6G7EAgYjg4QDeY7dZHON5hhiI2F+TKaIaxsuwtvN847 kY9HPZ8i0Q8XVl13EQ6aF4+QlU755h0aQbJgUpwcjR/3hG+qi/ofoZF0O+wzwhpBEuGB oiX5l/YaVNzmOtnPpy25UFCy6+G7Bd09YgT0k3+Exe3jSHurPP+1WSE48LliH5T6c3F6 MAggaaAR/BBgqmvRuH0bijqdEtgdyajRRpkkUFRG4SjyzVf5XbSSNdxFLB4YRru4e5E7 PtxoqqWgxPxj4U1F7NasM/nM7AOn7/ltOb6DvkhNES76LKeD06LqSvRadCol0yleTxy+ 9MxQ== MIME-Version: 1.0 Received: by 10.152.162.68 with SMTP id xy4mr6983396lab.49.1334940139363; Fri, 20 Apr 2012 09:42:19 -0700 (PDT) Received: by 10.112.46.4 with HTTP; Fri, 20 Apr 2012 09:42:19 -0700 (PDT) In-Reply-To: <4F916F82.6050105@cisco.com> References: <4F916F82.6050105@cisco.com> Date: Fri, 20 Apr 2012 12:42:19 -0400 Message-ID: Subject: Re: L3VPN Chairs From: Marshall Eubanks To: L3VPN WG mailing list , thomas.morin@orange.com, Martin Vigoureux , Adrian Farrel , "iesg@ietf.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2012 16:42:21 -0000 On Fri, Apr 20, 2012 at 10:15 AM, Stewart Bryant wrote: > > I would like to announce that I am appointing : > > Thomas Morin > > and > > Martin Vigoureux > > as chairs of the L3VPN Working group. > Good luck! If there is anything I can do to help (and I am sure this applies to the other prior co-chairs), please let me know. Regards Marshall > I would like to thank them for agreeing to take on this > responsibility and would request that you support them > as they get up to speed with completing the existing > L3VPN work and considering how the WG addresses > the new technical challenges in this area. > > Regards > > Stewart > > From yakov@juniper.net Sun Apr 22 06:32:18 2012 Return-Path: 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 9A9E521F8456 for ; Sun, 22 Apr 2012 06:32:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.779 X-Spam-Level: X-Spam-Status: No, score=-105.779 tagged_above=-999 required=5 tests=[AWL=0.220, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, 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 a-+z+HTIr1aw for ; Sun, 22 Apr 2012 06:32:17 -0700 (PDT) Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 61A3021F844C for ; Sun, 22 Apr 2012 06:32:17 -0700 (PDT) Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKT5QIYN45oLamUQ2gZMmEpSU3TY6lRhjL@postini.com; Sun, 22 Apr 2012 06:32:17 PDT Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB01-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 22 Apr 2012 06:32:00 -0700 Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id q3MDVx122253; Sun, 22 Apr 2012 06:31:59 -0700 (PDT) (envelope-from yakov@juniper.net) Message-ID: <201204221331.q3MDVx122253@magenta.juniper.net> To: IJsbrand Wijnands Subject: Re: Regarding draft-wijnands-mpls-mldp-vpn-in-band-signaling-00 In-Reply-To: <6EABF66C-AF44-49D6-AA8F-728C894ED957@cisco.com> References: <6EABF66C-AF44-49D6-AA8F-728C894ED957@cisco.com> X-MH-In-Reply-To: IJsbrand Wijnands message dated "Fri, 10 Feb 2012 12:19:25 +0100." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <18071.1335101519.1@juniper.net> Date: Sun, 22 Apr 2012 06:31:59 -0700 From: Yakov Rekhter Cc: L3VPN mailing list X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Apr 2012 13:32:18 -0000 Ice, > Dear L3VPN, > > We presented draft-wijnands-mpls-mldp-vpn-in-band-signaling-00 to > the MPLS WG last IETF in Taipei and received a comment that this > should be discussed in L3 VPN. As it looks there is not going to > be a L3VPN meeting in Paris, for that reason I'm sending out this > email to solicit input on this draft. > > This draft describes a solution to be used in a VPN environment, > but it is no t intended to be used as a generic solution for Multicast > VPNs. It is for specific deployments where traffic is bundled in > 'service' VPNs within a Providers n etwork, following similar > procedures and rationale as described in draft-ietf-m > pls-mldp-in-band-signaling-05. These VPNs are not generic customer > VPNs, but used to transport content such as IPTV or financial data > through a Providers network. > > The basic idea is that the ingress PE's VRF RD is added to the mLDP > FEC opaque encoding to make it unique and VPN specific. This follows > the same model as described in draft-ietf-mpls-mldp-recurs-fec-04 > section 3. We had a similar discussion regarding the use of the > RD in the opaque encoding and decided to accept it as WG document > in the MPLS WG. > > Some may say this solution does not follow the multicast procedures > as documented in draft-ietf-l3vpn-2547bis-mcast-10, and for that > reason should not be allowed. > > However, > > 1. This is not any different from draft-ietf-mpls-mldp-recurs-fec-04 > section 3. > 2. This draft is driven by customer interest. > 3. This solution relies on existing IP-VPN BGP procedures without > additional extensions. > > For that reason we like to see > draft-wijnands-mpls-mldp-vpn-in-band-signaling-00 progress as > WG document in the MPLS WG. > > We welcome your feedback, > As you asked for feedback, here are few commends on the draft: 1. The following should be added to Abstract and Introduction: Procedures specified in this draft are not compatible with the standard MVPN procedures, as specified in [RFC6513, RFC6514]. Thus, a PE router that implements procedures specified in this draft would not be able to interoperate with a PE router that implements the standard MVPN procedures. 2. From the draft: For a variety of reasons (discussed in [I-D.ietf-l3vpn-2547bis-mcast]), this is not a suitable for a general purpose multicast VPN solution. The above is a bit confusing/misleading. The reason why this solution is not suitable for a general purpose multicast VPN solution is that it does not meet some of the mandatory requirements for multicast VPN solution, as stated in rfc4834. With this in mind I would like the authors to replace the above with the following: The solution described in this draft is not suitable for a general purpose multicast VPN solution, as it does not meet multiple mandatory requirements for multicast VPNs specified in [rfc4834], such as (a) scalability, (b) support for MVPN customers running ASM, (c) support for extranets, (d) support for tunneling technologies other than mLDP, etc.. 3. From the draft: But the procedures described herein are much simpler than the general purpose MVPN procedures, This is just a matter of opinion, and as such should be removed from the draft. 4. From the draft: Due to the 1-1 mapping and the multicast source and group information being encoded in the mLDP FEC, there is deterministic mapping beween the multicast tree and the mLDP LSP in the core network. This improves and simplifies fault resolution. There is nothing in the general purpose MVPN procedures that would prevent the same. Thus the same fault resolution could be done with the general purpose MVPN procedures. With this in mind I propose either (a) to delete the above text, or (b) keep the above text, and add the following to the above text: The same fault resolution could be accomplished with the general purpose MVPN procedures. 5. From the draft: In order to use the mLDP in-band signaling procedures for a particular group address in a particular VPN, the Provider Edge (PE) routers that attach to that VPN MUST be configured with a range of multicast group addresses for which mLDP in-band signaling is to be enabled. This configuration is per VRF ("Virtual Routing and Forwarding table", defined in [RFC4364]). For those groups, and those groups only, the procedures of this document are used instead of the general purpose Multicast VPN procedures. This configuration must be present in all PE routers that attach to sites containing senders or receivers for the given set of group addresses. First of all, the document should spell out that configuring on a PE "a range of multicast group addresses for which mLDP in-band signaling is to be enabled" requires coordination between a customer and a service provider. Second, the document needs spell out the procedures for groups that are not in this range. E.g., should traffic to these groups be discarded ? Should this traffic be handled using standard MVPN procedures ? Something else ? 6. As I said before, this draft, as you said above, "describes a solution to be used in a VPN environment". Thus it is outside the scope of the MPLS WG (as VPN is outside the charter of that WG). If the authors want to progress this draft as a WG document, then they should ask L3VPN WG to progress it as an L3VPN WG document (as VPN is within the charter of that WG). Yakov. From thomas.morin@orange.com Mon Apr 23 06:32:53 2012 Return-Path: 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 D180D21F863D for ; Mon, 23 Apr 2012 06:32:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.874 X-Spam-Level: X-Spam-Status: No, score=-5.874 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, 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 nELif7uKzHDl for ; Mon, 23 Apr 2012 06:32:53 -0700 (PDT) Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by ietfa.amsl.com (Postfix) with ESMTP id 17EBD21F84EB for ; Mon, 23 Apr 2012 06:32:53 -0700 (PDT) Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 2F36B1074008; Mon, 23 Apr 2012 15:44:52 +0200 (CEST) Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id 26CC41074007; Mon, 23 Apr 2012 15:44:52 +0200 (CEST) Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Mon, 23 Apr 2012 15:32:52 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from 10.193.21.179 ([10.193.21.179]) by ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) via Exchange Front-End Server owa.rd.francetelecom.fr ([10.192.128.53]) with Microsoft Exchange Server HTTP-DAV ; Mon, 23 Apr 2012 13:32:50 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Organization: France Telecom Orange User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 Content-class: urn:content-classes:message Subject: Re: L3VPN Chairs Date: Mon, 23 Apr 2012 15:33:29 +0200 Message-ID: In-Reply-To: <4F916F82.6050105@cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: L3VPN Chairs Thread-Index: Ac0hVZRgxarDman2QfOr4f/oyCzTMw== References: <4F916F82.6050105@cisco.com> From: To: X-OriginalArrivalTime: 23 Apr 2012 13:32:52.0001 (UTC) FILETIME=[950A0110:01CD2155] Cc: adrian@olddog.co.uk, l3vpn@ietf.org X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Apr 2012 13:32:53 -0000 VGhhbmsgeW91IFN0ZXdhcnQuDQoNCldlIHdhbnQgdG8gdGhhbmsgTWFyc2hhbGwgYW5kIEJlbiBm b3IgdGhlaXIgd29yayBhcyBsM3ZwbiBjby1jaGFpcnMNCmR1cmluZyB0aGUgcGFzdCAyLTMgeWVh cnMsIGFuZCBtb3JlIGdlbmVyYWxseSBhbGwgY29udHJpYnV0b3JzLiBUaGUgdGFzaw0KaXMgZ3Jl YXQsIGFuZCB3ZSdyZSBsb29raW5nIGZvcndhcmQgdG8gd29ya2luZyB3aXRoIHlvdSBhbGwuDQoN CkJ5IHRoZSB3YXksIHNpbmNlIGRvaW5nIHRoZSB3aG9sZSBtZWV0aW5ncyBpbiBGcmVuY2ggbWln aHQgYmUgYSBiaXQgb2YgYQ0KY2hhbGxlbmdlLCB3ZSdsbCBzdGljayB0byBlbmdsaXNoLiBIb3dl dmVyLCBwbGVhc2UgdGFrZSBjYXJlIG9mIHByb3Blcmx5DQpuYXNhbGl6aW5nIHRoZSAnaW4nIGlu IE1hcnRpbiBbyZvMg10gYW5kIG5vdCBwcm9ub3VuY2luZyB0aGUgJ3MnIGluIFRob21hcy4NCg0K TWFydGluIGFuZCBUaG9tYXMNCg0KDQoyMDEyLTA0LTIwLCBTdGV3YXJ0IEJyeWFudDoNCj4NCj4g SSB3b3VsZCBsaWtlIHRvIGFubm91bmNlIHRoYXQgSSBhbSBhcHBvaW50aW5nIDoNCj4NCj4gVGhv bWFzIE1vcmluIDx0aG9tYXMubW9yaW5Ab3JhbmdlLmNvbT4NCj4NCj4gYW5kDQo+DQo+IE1hcnRp biBWaWdvdXJldXggPG1hcnRpbi52aWdvdXJldXhAYWxjYXRlbC1sdWNlbnQuY29tPg0KPg0KPiBh cyBjaGFpcnMgb2YgdGhlIEwzVlBOIFdvcmtpbmcgZ3JvdXAuDQo+DQo+IEkgd291bGQgbGlrZSB0 byB0aGFuayB0aGVtIGZvciBhZ3JlZWluZyB0byB0YWtlIG9uIHRoaXMNCj4gcmVzcG9uc2liaWxp dHkgYW5kIHdvdWxkIHJlcXVlc3QgdGhhdCB5b3Ugc3VwcG9ydCB0aGVtIGFzIHRoZXkgZ2V0IHVw DQo+IHRvIHNwZWVkIHdpdGggY29tcGxldGluZyB0aGUgZXhpc3RpbmcgTDNWUE4gd29yayBhbmQg Y29uc2lkZXJpbmcgaG93DQo+IHRoZSBXRyBhZGRyZXNzZXMgdGhlIG5ldyB0ZWNobmljYWwgY2hh bGxlbmdlcyBpbiB0aGlzIGFyZWEuDQo+DQo+IFJlZ2FyZHMNCj4NCj4gU3Rld2FydA0KPg0KPg0K