IETF Logo Mail Archive

Re: Regarding draft-wijnands-mpls-mldp-vpn-in-band-signaling-00

Jeff Tantsura <jeff.tantsura@ericsson.com> Tue, 21 February 2012 07:14 UTC

Return-Path: <jeff.tantsura@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 78A7A21F8504 for <l3vpn@ietfa.amsl.com>; Mon, 20 Feb 2012 23:14:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.204
X-Spam-Level:
X-Spam-Status: No, score=-6.204 tagged_above=-999 required=5 tests=[AWL=-0.205, BAYES_00=-2.599, 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 HRftFdATdsPy for <l3vpn@ietfa.amsl.com>; Mon, 20 Feb 2012 23:14:51 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 8F6C021F8501 for <l3vpn@ietf.org>; Mon, 20 Feb 2012 23:14:51 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q1L7EnAk003149 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Feb 2012 01:14:50 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.140]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 21 Feb 2012 02:14:49 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: IJsbrand Wijnands <ice@cisco.com>, L3VPN mailing list <l3vpn@ietf.org>
Date: Tue, 21 Feb 2012 02:14:54 -0500
Subject: Re: Regarding draft-wijnands-mpls-mldp-vpn-in-band-signaling-00
Thread-Topic: Regarding draft-wijnands-mpls-mldp-vpn-in-band-signaling-00
Thread-Index: AczwaH7V06nBnrTzQ96ycOMdq0kW8Q==
Message-ID: <CB688416.A392%jeff.tantsura@ericsson.com>
In-Reply-To: <1D70D757A2C9D54D83B4CBD7625FA80EA96F22@MISOUT7MSGUSR9I.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 21 Feb 2012 07:14:52 -0000

I support progress of this document as WG document in the MPLS WG.
-- 
Regards,
Jeff



>
>> -----Original Message-----
>> From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf
>> Of IJsbrand Wijnands
>> Sent: Friday, February 10, 2012 6:19 AM
>> To: L3VPN mailing list
>> Subject: Regarding draft-wijnands-mpls-mldp-vpn-in-band-signaling-00
>> 
>> 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 L3VPN. 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 not 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 network, following similar procedures and rationale
>> as described in draft-ietf-mpls-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,
>> 
>> Thx,
>> 
>> The authors.
>

v2.23.0 | Report a Bug | By Email