[mpls] Comments on draft-rekhter-mpls-pim-sm-over-mldp

"IJsbrand Wijnands (iwijnand)" <iwijnand@cisco.com> Wed, 21 August 2013 15:44 UTC

Return-Path: <iwijnand@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E68F11E8223 for <mpls@ietfa.amsl.com>; Wed, 21 Aug 2013 08:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 UmX8PuIvuJ8n for <mpls@ietfa.amsl.com>; Wed, 21 Aug 2013 08:44:20 -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 B202111E8107 for <mpls@ietf.org>; Wed, 21 Aug 2013 08:44:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3122; q=dns/txt; s=iport; t=1377099860; x=1378309460; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Ro+PINuCEsXpRvHtT+qVIwbWFoQGtipd/18QXy4YjQo=; b=mRpVdJ3vQ3QNNIxZM33fOMb1iGSFLSj5U368FK9NKcf8RtWeP8PBDXiQ /mGgJYqSKJIqqFCW9X/ylTcaDSX6SISxiZG5v3M/58NeVDTnagpQZJmhy KiIpdHq2NGP9wyV9w/23iEodFetpocH+xDCFIxWkztnaPfcgw6R6Tcdu8 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqgFAKPfFFKtJXG9/2dsb2JhbABagwU1Ub9kgR8WbQeCJAEBAQMBAQEBNzEDBgUFCQICASoUEBsMCyUCBA4FCBOHbwYMrVoEBI8IEIEIMQeDG3kDqTqDHYFyOQ
X-IronPort-AV: E=Sophos;i="4.89,928,1367971200"; d="scan'208";a="250044940"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-6.cisco.com with ESMTP; 21 Aug 2013 15:44:19 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r7LFiJJw012718 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 21 Aug 2013 15:44:19 GMT
Received: from xmb-aln-x14.cisco.com ([169.254.8.172]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Wed, 21 Aug 2013 10:44:19 -0500
From: "IJsbrand Wijnands (iwijnand)" <iwijnand@cisco.com>
To: "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: Comments on draft-rekhter-mpls-pim-sm-over-mldp
Thread-Index: AQHOnoVMwyh2C5bFv029J29aw104pQ==
Date: Wed, 21 Aug 2013 15:44:18 +0000
Message-ID: <F79F1E8B5C93724392072F18B3E9FB9301CB7ECC@xmb-aln-x14.cisco.com>
References: <521475A6.7080002@pi.nu>
In-Reply-To: <521475A6.7080002@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.55.191.147]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C958C7BA9B008040B3D3E3B9ACF3D8D2@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>
Subject: [mpls] Comments on draft-rekhter-mpls-pim-sm-over-mldp
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 15:44:25 -0000

Dear WG,

Before deciding whether to accept draft-rekhter-mpls-pim-sm-over-mldp as a WG draft, we need to understand how it is positioned against several other drafts that address the same topic.

There are several other drafts that address the same topic, see draft-ietf-mpls-seamless-mcast-04, section 6.3. "PIM-SM in ASM mode for Global Table Multicast" and draft-zzhang-l3vpn-mvpn-global-table-mcast-00. These drafts provide full support for both the ASM and SSM modes of PIM, and also support the use of mLDP in the core.

Draft-rekhter-mpls-pim-sm-over-mldp augments the mldp-in-band signalling procedures so that they can be used in environments where dynamic multicast source discovery is required. It does this by adding back some of the MVPN BGP signalling, using a combination of BGP signalling and mLDP in-band signalling. The question is whether this is really useful. If BGP multicast signaling needs to be used anyway, why not just use the solution from the seamless-mcast or global-table-mcast drafts? What's the point of combining it with mLDP in-band signalling? The main advantage of using mLDP in-band signaling is that it doesn't require any additional multicast signalling protocols in the core. 

Before we accept draft-rekhter-mpls-pim-sm-over-mldp as a WG document we should determine whether there are any Service Providers who actually want to deploy the combination of mLDP in-band signalling and BGP multicast signalling.

Thx,

Ice.


On 21 Aug 2013, at 10:09, Loa Andersson <loa@pi.nu>
wrote:

> Working Group,
> 
> The authors of draft-rekhter-mpls-pim-sm-over-mldp has told the
> working group chairs that the draft is ready to be adopted as a working
> group document.
> 
> Before we start the mpls-rt review and the poll for adoption we will do
> an IPR poll.
> 
> This mail starts that IPR poll.
> 
> Are you aware of any IPR that applies to draft-rekhter-mpls-pim-
> sm-over-mldp?
> 
> If so, has this IPR been disclosed in compliance with IETF IPR rules
> (see RFCs 3979, 4879, 3669 and 5378 for more details).
> 
> If you are listed as a document author or contributor please respond to
> this email regardless of whether or not you are aware of any relevant
> IPR. *The response needs to be sent to the MPLS wg mailing list.* The documents will not advance to the next stage until a response
> has been received from each author and contributor.
> 
> If you are on the MPLS WG email list but are not listed as an author or
> contributor, then please explicitly respond only if you are aware of any
> IPR that has not yet been disclosed in conformance with IETF rules.
> 
> 
> Thanks, Loa
> (as MPLS WG co-chair)
> -- 
> 
> 
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls