IETF Logo Mail Archive

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

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Tue, 21 February 2012 12:32 UTC

Return-Path: <rajiva@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 C123E21F8795 for <l3vpn@ietfa.amsl.com>; Tue, 21 Feb 2012 04:32:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.004
X-Spam-Level:
X-Spam-Status: No, score=-7.004 tagged_above=-999 required=5 tests=[AWL=-0.468, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
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 zAvK-okHjELW for <l3vpn@ietfa.amsl.com>; Tue, 21 Feb 2012 04:32:44 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id D547921F86BD for <l3vpn@ietf.org>; Tue, 21 Feb 2012 04:32:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rajiva@cisco.com; l=2487; q=dns/txt; s=iport; t=1329827565; x=1331037165; h=subject:references:content-transfer-encoding:from: in-reply-to:message-id:date:to:cc:mime-version; bh=XKXUDvwVCn28RQQ+F6sA+Yy7vO4X/IHGpGZAE3QRLu8=; b=Ojmg6JlJT67wu+wv7iXFrty66YtZjmb0xgmf5nPuXq2rvKAdcYd/rJEB odmf5zp6Ndn5TRrlxgsztiqGPuw3mg2Rm590xOT0IvEXy8AAsYAjjX4up mTczeEMgHOFiLl+DBlf+pTDjKOBqvuekB4tY++p3PNwA2kX0hVkBZcx07 Q=;
X-IronPort-AV: E=Sophos;i="4.73,457,1325462400"; d="scan'208";a="60562861"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-2.cisco.com with ESMTP; 21 Feb 2012 12:32:44 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id q1LCWirm020310; Tue, 21 Feb 2012 12:32:44 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 21 Feb 2012 06:32:44 -0600
Received: from 72.163.62.136 ([72.163.62.136]) by XMB-RCD-111.cisco.com ([72.163.62.153]) with Microsoft Exchange Server HTTP-DAV ; Tue, 21 Feb 2012 12:32:43 +0000
Subject: Re: Regarding draft-wijnands-mpls-mldp-vpn-in-band-signaling-00
References: <CB688416.A392%jeff.tantsura@ericsson.com>
Content-Transfer-Encoding: quoted-printable
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
Content-Type: text/plain; charset="us-ascii"
Thread-Topic: Regarding draft-wijnands-mpls-mldp-vpn-in-band-signaling-00
Thread-Index: AczwlOi/5uvq02h6RieFa2myPdZLtg==
In-Reply-To: <CB688416.A392%jeff.tantsura@ericsson.com>
Message-ID: <21C0E50D-99D6-467D-922B-3B263767002C@cisco.com>
Date: Tue, 21 Feb 2012 07:32:41 -0500
To: Jeff Tantsura <jeff.tantsura@ericsson.com>
MIME-Version: 1.0 (1.0)
X-OriginalArrivalTime: 21 Feb 2012 12:32:44.0323 (UTC) FILETIME=[E9158730:01CCF094]
Cc: L3VPN mailing list <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, 21 Feb 2012 12:32:48 -0000

Support.

Cheers,
Rajiv

Sent from my Phone

On Feb 21, 2012, at 2:14 AM, "Jeff Tantsura" <jeff.tantsura@ericsson.com> wrote:

> 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