Re: [L3sm] [l3sm] #5 (draft-ltsd-l3sm-l3vpn-service-model): Multicast Support for L3VPN service
"l3sm issue tracker" <trac+l3sm@tools.ietf.org> Tue, 01 December 2015 09:44 UTC
Return-Path: <trac+l3sm@tools.ietf.org>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 233E71B39FA for <l3sm@ietfa.amsl.com>; Tue, 1 Dec 2015 01:44:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level:
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_12=0.6, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c8bj3roXZQbf for <l3sm@ietfa.amsl.com>; Tue, 1 Dec 2015 01:44:19 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 103471B39FC for <l3sm@ietf.org>; Tue, 1 Dec 2015 01:44:19 -0800 (PST)
Received: from localhost ([::1]:34046 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+l3sm@tools.ietf.org>) id 1a3hTu-0003Ny-P1; Tue, 01 Dec 2015 01:44:18 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: l3sm issue tracker <trac+l3sm@tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org, bill.wu@huawei.com
X-Trac-Project: l3sm
Date: Tue, 01 Dec 2015 09:44:18 -0000
X-URL: https://tools.ietf.org/l3sm/
X-Trac-Ticket-URL: https://trac.tools.ietf.org/wg/l3sm/trac/ticket/5#comment:1
Message-ID: <073.f0ffe1908fa5a5ac3ae51e2ac8fef51f@tools.ietf.org>
References: <058.5c4321db51ad8ec753f5ee16f27d8519@tools.ietf.org>
X-Trac-Ticket-ID: 5
In-Reply-To: <058.5c4321db51ad8ec753f5ee16f27d8519@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org, bill.wu@huawei.com, l3sm@ietf.org
X-SA-Exim-Mail-From: trac+l3sm@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: draft-ltsd-l3sm-l3vpn-service-model@ietf.org
Resent-Message-Id: <20151201094419.103471B39FC@ietfa.amsl.com>
Resent-Date: Tue, 01 Dec 2015 01:44:19 -0800
Resent-From: trac+l3sm@tools.ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3sm/-giPfgtbrlM0XCPovR9Ho60mHMs>
Cc: l3sm@ietf.org
Subject: Re: [L3sm] [l3sm] #5 (draft-ltsd-l3sm-l3vpn-service-model): Multicast Support for L3VPN service
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.15
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2015 09:44:20 -0000
#5: Multicast Support for L3VPN service Comment (by bill.wu@huawei.com): Here is Stephane's proposed change for the multicast part : VPN config : | +--rw multicast | +--rw tree-flavor* identityref | +--rw rp | +--rw rp-group-mapping* [rp-address group] | | +--rw rp-address union | | +--rw provider-managed | | | +--rw enabled? boolean | | | +--rw anycast-rp? boolean | | +--rw group union | +--rw rp-discovery? identityref We can define a list of RP to group mapping. This is useful when : • Static RP is used and RP is managed by customer => provider- managed set to false • RP is managed by provider, if this case , we also need to know from customer if anycast RP is required. But I’m wondering if it is necessary or not, from a technical point of view yes, from an abstraction point of view, does the customer care if we use anycast RP or just RP redundancy through the discovery mechanism ? Maybe we can just rename anycast-RP to redundant-RP. In case of provider-managed, I expect the OSS to place the RP in the provider network, maybe we need to add some constraint here also … If the customer does anycast RP (customer managed RP), IMO, it should be transparent for the provider ? • Note that the proposal allows for some groups to be managed by provider and some others by customer. Site config : | +--rw multicast | +--rw multicast-site-type? enumeration | +--rw multicast-transport-protocol | | +--rw ipv4? boolean | | +--rw ipv6? boolean | +--rw protocol-type? In the site config, I added the protocol-type, which refers to “host” “router” or “both”. “Host” means some hosts are connected to the provider network (so requires IGMP or MLD), “Router” means hosts are behind a customer router (so need of PIM), “both” means need to enable both IGMP/MLD and PIM. You can also review his proposal from the following link: https://mailarchive.ietf.org/arch/msg/l3sm/NklHSPuYTj4bnHLBWWeEVdxghi0 Replying to [ticket:5 bill.wu@…]: > Eric C Rosen commented on Multicast support for L3VPN service and believed specify the RPA in the service model is not enough > and he proposed to contain the complete set of customer group-to-rp mapping and he also proposed service model to specify who offers RP service > > Stephane made a proposal based on his suggetion and share on the list for broad review and haven't recieved any feedback on the list. Therefore the proposal hasn't been incorporated into v(-01) yet. -- -------------------------------------+------------------------------------- Reporter: bill.wu@huawei.com | Owner: draft-ltsd-l3sm-l3vpn- Type: enhancement | service-model@tools.ietf.org Priority: minor | Status: new Component: draft-ltsd-l3sm-l3vpn- | Milestone: service-model | Version: Severity: - | Resolution: Keywords: Multicast | -------------------------------------+------------------------------------- Ticket URL: <https://trac.tools.ietf.org/wg/l3sm/trac/ticket/5#comment:1> l3sm <https://tools.ietf.org/l3sm/>
- [L3sm] [l3sm] #5 (draft-ltsd-l3sm-l3vpn-service-m… l3sm issue tracker
- Re: [L3sm] [l3sm] #5 (draft-ltsd-l3sm-l3vpn-servi… l3sm issue tracker
- Re: [L3sm] [l3sm] #5 (l3vpn-service-model): Multi… l3sm issue tracker