Re: [MBONED] MBoned: Re: WG Review: L3VPN Service Model (l3sm)

Benoit Claise <bclaise@cisco.com> Wed, 18 March 2015 15:11 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B38E71A1A60; Wed, 18 Mar 2015 08:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 ZmDmHW-GqTRB; Wed, 18 Mar 2015 08:11:52 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC8CC1A1A48; Wed, 18 Mar 2015 08:11:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1101; q=dns/txt; s=iport; t=1426691511; x=1427901111; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=i2GIlvJczEkHiftPTuWkraZvrP/hVaiTY5dhOipJP88=; b=HOb7H6yDKGlTzp7uHjOupKwASP+TdTBghUYzr28oBSSiXUULOaey6v9N oZizBwDUFDNTIz02AggogbZBjP1R69mh4xGExyDfX2vp6pBsKcFyNSakw 7ZM5aZVCVVsxWmXvbxg5IYrGfo3xu3e3uk0b4ZYpCGdnQhe6SnG9Z1aR2 A=;
X-IronPort-AV: E=Sophos;i="5.11,423,1422921600"; d="scan'208";a="408967805"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 18 Mar 2015 15:11:50 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t2IFBnP8010048; Wed, 18 Mar 2015 15:11:49 GMT
Message-ID: <550995B5.7050409@cisco.com>
Date: Wed, 18 Mar 2015 16:11:49 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Jeffrey Haas <jhaas@pfrc.org>, Toerless Eckert <eckert@cisco.com>
References: <20150306165456.GT16454@cisco.com> <20150306182749.GF9388@pfrc>
In-Reply-To: <20150306182749.GF9388@pfrc>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mboned/f3vW-EFEQwaOCg-egJMUsb79MMw>
Cc: mboned@ietf.org, pim@ietf.org
Subject: Re: [MBONED] MBoned: Re: WG Review: L3VPN Service Model (l3sm)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2015 15:11:53 -0000

Jeff,
> [note I am only subscribed to mboned and may have missed related comments
> elsewhere.]
>
> Toerless,
>
> On Fri, Mar 06, 2015 at 08:54:56AM -0800, Toerless Eckert wrote:
>> Any thoughts on this ? Anybody from mboned planning to contribute to
>> this work to ensure that L3VPN multicast would be represented in the
>> data model created ?
> FWIW, I'd ask Benoit for clarification on what he's including in l3vpn.  It
> may be possible that he's targeting *unicast* l3vpn only and had not
> considered multicast l3vpn.
It's not what I'm targeting or not, it's more about the type of 
questions operators ask to their customers when enabling services.
Note that I see multicast services in 
http://datatracker.ietf.org/doc/draft-l3vpn-service-yang/

Regards, Benoit
> I've copied Benoit for that clarification.
>
> For my part, I consider the two problems to be of completely different
> levels of service complexity and while we probably want to try to leverage
> similar components in the service models as possible, they may not have
> many.
>
> -- Jeff
>
> .
>