Re: [L3sm] New Version Notification for draft-wu-l3sm-rfc8049bis-02.txt

David Ball <daviball@cisco.com> Wed, 23 August 2017 11:47 UTC

Return-Path: <daviball@cisco.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B91FC132392 for <l3sm@ietfa.amsl.com>; Wed, 23 Aug 2017 04:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 8-3iS1_N0rzM for <l3sm@ietfa.amsl.com>; Wed, 23 Aug 2017 04:47:43 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 354151321DC for <l3sm@ietf.org>; Wed, 23 Aug 2017 04:47:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3344; q=dns/txt; s=iport; t=1503488863; x=1504698463; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=cunf1QCLbIoFqQWpCoS9gNVZOtXPyA1ty4MTtucLKIk=; b=JoRY0SK4VzETEE5TZXXMoV8C3DbTbWFBsSuCxY7Mul1r0jl7671bflUr RYL2SrRXWYk+dtOv9o3MdJ2ZYoZLf8YgKRK0zsCbQzByWm++DAGr665sB pypFzvinO0keHif3SS6c+lsGCwuq0cjptMz6KKgm0HUTEVydjifedzMjw 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DwAQCJap1Z/xbLJq1cGgEBAQECAQEBAQgBAQEBhD6BFY8IkHQiliSCEiyFGwKFBBYBAgEBAQEBAQFrKIUYAQEBAQIBIw8BBT8CBQcECxEEAQEDAiMDAgJGCQgGAQwGAgEBiiUIEK4WgiaLbwEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQ2CHYNOgg4LgnGEUwEBgzGCYQEEoFiURItOhxaNPohwJgEwgQoyIQgcFUmFHBeBaD82AYhOgjIBAQE
X-IronPort-AV: E=Sophos;i="5.41,416,1498521600"; d="scan'208";a="654135443"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Aug 2017 11:47:38 +0000
Received: from [10.63.68.123] ([10.63.68.123]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v7NBlcZK026827; Wed, 23 Aug 2017 11:47:38 GMT
To: "Ogaki, Kenichi" <ke-oogaki@kddi.com>, 'Qin Wu' <bill.wu@huawei.com>, l3sm@ietf.org
Cc: 'Stephane Litkowski' <stephane.litkowski@orange.com>, adrian@olddog.co.uk
References: <B8F9A780D330094D99AF023C5877DABA9AA5D7A2@nkgeml513-mbx.china.huawei.com> <c76328ad-b71e-b2a3-92a4-b02beac2be7d@cisco.com> <B8F9A780D330094D99AF023C5877DABA9AABA8A4@nkgeml513-mbx.china.huawei.com> <00f001d31b2f$541e6f90$fc5b4eb0$@kddi.com>
From: David Ball <daviball@cisco.com>
Message-ID: <7e9655f5-3ae8-11a1-6904-2ab75eb0b1a2@cisco.com>
Date: Wed, 23 Aug 2017 12:47:38 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <00f001d31b2f$541e6f90$fc5b4eb0$@kddi.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/5PpZ6Z-cIlEDyancD4CZjOcFa-g>
Subject: Re: [L3sm] New Version Notification for draft-wu-l3sm-rfc8049bis-02.txt
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Wed, 23 Aug 2017 11:47:46 -0000

On 22/08/2017 11:13, Ogaki, Kenichi wrote:

> Hi Qin,
>
>>       2. For the connection addresses, the provider's IP address/mask:
> As for dhcp related provider-addresses and the masks, these are not what SP provides, but the subnet which the customer requests to specify the leased address subnet. Then, these must be configurable.

So you're saying even when DHCP is used, the customer can request that 
addresses will be allocated from a specific subnet?  That's not 
something I've heard of, but ok. :)  These leaves should definitely be 
optional in that case, as the more normal case is that the customer does 
not request a specific subnet.  Also this use case needs to be mentioned 
in the description for those leaves.

     David

>
> Thanks,
> Kenichi
>
> -----Original Message-----
> From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of Qin Wu
> Sent: Monday, August 21, 2017 5:39 PM
> To: David Ball; l3sm@ietf.org
> Cc: Stephane Litkowski; Kenichi Ogaki; adrian@olddog.co.uk
> Subject: Re: [L3sm] New Version Notification for draft-wu-l3sm-rfc8049bis-02.txt
>
>> 11. In accordance with the clarified scope, parts of the model that correspond
>>        with information provided by the SP need to be marked with "config false".
>>        I've identified the following, but there might be more.
>>       1. The list of profiles of various types (i.e. l3vpn-service/vpn-profiles)
>>       2. For the connection addresses, the provider's IP address/mask:
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv4/provider-dhcp/provider-address
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv4/provider-dhcp/mask
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv4/dhcp-relay/provider-address
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv4/dhcp-relay/mask
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv4/addresses/provider-address
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv4/addresses/mask
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv6/provider-dhcp/provider-address
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv6/provider-dhcp/mask
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv6/dhcp-relay/provider-address
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv6/dhcp-relay/mask
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv6/addresses/provider-address
>>      • l3vpn-service/sites/site/site-network-accesses/site-network-access/ip-connection/ipv6/addresses/mask
>   
>
> That sounds reasonable.
>
> [Qin]: One more comment, we can not put ‘config false’ for l3vpn-service/vpn-profiles, since Config true leafrefs MUST NOT refer to config false data
>
> This issue was discussed before, see discussion available at:
>
> https://www.ietf.org/mail-archive/web/l3sm/current/msg00683.html
>
>
>

-- 
David Ball
<daviball@cisco.com>