IETF Logo Mail Archive

Re: [mpls] MPLS-RT review of draft-rekhter-mpls-pim-sm-over-mldp

Jeff Tantsura <jeff.tantsura@ericsson.com> Tue, 01 October 2013 17:40 UTC

Return-Path: <jeff.tantsura@ericsson.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 E988521F9D9A for <mpls@ietfa.amsl.com>; Tue, 1 Oct 2013 10:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.426
X-Spam-Level:
X-Spam-Status: No, score=-2.426 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_00=-2.599]
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 TQf+juiifdTc for <mpls@ietfa.amsl.com>; Tue, 1 Oct 2013 10:40:18 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2EC8611E81AD for <mpls@ietf.org>; Tue, 1 Oct 2013 10:40:14 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-e8-524b08fed16d
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id A5.C0.09414.EF80B425; Tue, 1 Oct 2013 19:40:14 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0328.009; Tue, 1 Oct 2013 13:40:08 -0400
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: IJsbrand Wijnands <ice@cisco.com>, Yakov Rekhter <yakov@juniper.net>
Thread-Topic: [mpls] MPLS-RT review of draft-rekhter-mpls-pim-sm-over-mldp
Thread-Index: AQHOujN53rA+7VpjRZKFJsZDTsXmk5nXTLGAgAinJwA=
Date: Tue, 01 Oct 2013 17:40:08 +0000
Message-ID: <60DEDD93F5E54B4AB55647B8B6C74839946E8E@eusaamb109.ericsson.se>
In-Reply-To: <CAC675E9-E3EC-4ECC-9D79-BB6592B1165A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.5.121010
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3E5D18D6F1A49C46AB43E1425586B916@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupgkeLIzCtJLcpLzFFi42KZXLonUPcfh3eQweV+LYvmr94Wr+bcYbZY cfoZs8X3S0tYLG4tXclqcfzHN3YHNo8pvzeyeuycdZfdY8mSn0we15uusnt8ufyZLYA1issm JTUnsyy1SN8ugSvjcf95loL/AhXrJixgaWCcz9fFyMkhIWAicXl7OyOELSZx4d56ti5GLg4h gaOMEv/2nYJyljFKPJ9zmhWkik3AQOL/t+MsILaIgIfE/e1zmUCKmAW+MEp03V3OBpIQFvCU +HR9N3MXIwdQkZfElp2pEPVWEssXfWUGsVkEVCQ+7XwNVs4r4C3R3XAQ7ApOAVuJnjv32EFs RqCLvp9awwRiMwuIS9x6Mp8J4lIBiSV7zjND2KISLx//A7tNVEBPou3YGXaIuLLE9zmPWCB6 dSQW7P7EBmFbS+z8dZQVwtaWWLbwNTPEDYISJ2c+YZnAKD4LybpZSNpnIWmfhaR9FpL2BYys qxg5SotTy3LTjQw2MQJj85gEm+4Oxj0vLQ8xSnOwKInzfnnrHCQkkJ5YkpqdmlqQWhRfVJqT WnyIkYmDU6qBcak1/5+LwVMri3WEJz+xObty9rLe4JzJz/JaCgRm8zJ6KBV2Xdk4/8P/af6/ mZdXLzywb+qMMPmgGXkTn/R9q2+tlNMTni72KLBFds6FREXf3VN3JrA/vdT++pdD6RnXI2zH uSedP/1PdUpFQpLFCwe2s2WzOD8eX9buZLKm/1PAbqWMlOMLmZRYijMSDbWYi4oTAQlaqkub AgAA
Cc: "mpls@ietf.org" <mpls@ietf.org>, "draft-rekhter-mpls-pim-sm-over-mldp@tools.ietf.org" <draft-rekhter-mpls-pim-sm-over-mldp@tools.ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, Lizhong Jin <lizho.jin@gmail.com>
Subject: Re: [mpls] MPLS-RT review of 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: Tue, 01 Oct 2013 17:40:24 -0000

Hi,

I seem to agree with Ice.
My personal experience is that when people migrate from IP multicast to
MPLS multicast and deploy mLDP going to in-band signaling is a very
natural step as it preserves semantics and mode of operation of IP
Multicast while bringing all the advantages of MPLS. Complexity of BGP
signaling is often taken in consideration when it is compared to mLDP
in-band.

I'd really like to ask people who are deploying and operating Multicast
(not selling it) :) to speak up

Cheers,
Jeff


-----Original Message-----
From: IJsbrand Wijnands <ice@cisco.com>
Date: Wednesday, September 25, 2013 3:31 PM
To: Yakov Rekhter <yakov@juniper.net>
Cc: "mpls@ietf.org" <mpls@ietf.org>,
"draft-rekhter-mpls-pim-sm-over-mldp@tools.ietf.org"
<draft-rekhter-mpls-pim-sm-over-mldp@tools.ietf.org>,
"mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, Lizhong Jin
<lizho.jin@gmail.com>
Subject: Re: [mpls] MPLS-RT review of draft-rekhter-mpls-pim-sm-over-mldp

>Yakov,
>
>> I can not comment on whether it is "more natural to follow the
>>mechanism 
>> in draft-ietf-mpls-seamless-mcast".
>
>I think the question is, is there a need for a solution that combines
>mLDP in-band signalling with BGP AD. What is the advantage of this
>solution compared to what is already defined in
>draft-ietf-mpls-seamless-mcast? I can see that it does not require Leaf
>auto-discovery routes, but is that an advantage? Moreover, most customers
>like mLDP in-band signalling because it does not depend on BGP AD.
>
>> auto-discovery routes. Moreover, draft-rekhter-mpls-pim-sm-over-mldp
>> spells out that in certain deployment scenarios even Source Active
>> auto-discovery routes would not be used.
>
>Do you mean like what is documented in
>draft-wijnands-mpls-mldp-in-band-wildcard-encoding-00 section 3? Is the
>solution in draft-wijnands not a better way to support that since it does
>not require new Opaque TLV encodings and covers both global table and VRF
>support?
>
>Thx,
>
>Ice.
>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls

v2.23.0 | Report a Bug | By Email