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

David Ball <daviball@cisco.com> Wed, 30 August 2017 11:09 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 48B87132EED for <l3sm@ietfa.amsl.com>; Wed, 30 Aug 2017 04:09:23 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 YHqZAiLrHe6s for <l3sm@ietfa.amsl.com>; Wed, 30 Aug 2017 04:09:22 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 917E6132EEC for <l3sm@ietf.org>; Wed, 30 Aug 2017 04:09:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2949; q=dns/txt; s=iport; t=1504091361; x=1505300961; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=KEAfkjpJJp3ioIZVy+dPwNX7lacscFZqUBMPsJKe+fc=; b=lNoe1KENkS3MQayyg35o6ZIdss2bt7JD+W56Y4WRf5DpNWKRQLifwQUO m5+Gnb7+dI/L6/9qOXQrWoYDYFi5hjPMgAHL52rYX7UXqCgU+AHz6SqQO mMFuigWDYi8v6w2nl78RpPqLkvZxmVZiE3pmOI0YAmsRPpBY14Y+HlP54 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CvBAAAmqZZ/xbLJq1eGQEBAQEBAQEBAQEBBwEBAQEBhVODd4sSkHUikGmHUIVHAoRlFAECAQEBAQEBAWsohRkBAgMjVAIQCwQKCioCAlcGAQwGAgEBii2tUIInJ4sfAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYMqg1CCDguCcogIgmEBBKBslEyLUocZjVCIczYhgQ0yIQgcFYdlPzaKbQEBAQ
X-IronPort-AV: E=Sophos;i="5.41,448,1498521600"; d="scan'208,217";a="657124717"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Aug 2017 11:09:17 +0000
Received: from [10.63.68.124] ([10.63.68.124]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v7UB9GQg016164; Wed, 30 Aug 2017 11:09:17 GMT
To: Qin Wu <bill.wu@huawei.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Cc: Stephane Litkowski <stephane.litkowski@orange.com>, Kenichi Ogaki <ke-oogaki@kddi.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
References: <B8F9A780D330094D99AF023C5877DABA9AA5D7A2@nkgeml513-mbx.china.huawei.com> <c76328ad-b71e-b2a3-92a4-b02beac2be7d@cisco.com> <B8F9A780D330094D99AF023C5877DABA9AAB78D5@nkgeml513-mbx.china.huawei.com> <e3289dda-b54f-6001-d4df-4ad6f43cbc91@cisco.com> <B8F9A780D330094D99AF023C5877DABA9AACC436@nkgeml513-mbx.china.huawei.com> <6acab373-d50e-674e-1f8a-b95363ae7e4b@cisco.com> <B8F9A780D330094D99AF023C5877DABA9AAD04B2@nkgeml513-mbx.china.huawei.com> <bbb82618-18c6-70d1-9a3d-a4cade93535f@cisco.com> <B8F9A780D330094D99AF023C5877DABA9AAD9734@nkgeml513-mbx.china.huawei.com>
From: David Ball <daviball@cisco.com>
Message-ID: <c5973f02-1d11-9424-62d3-f8e5e8bf5316@cisco.com>
Date: Wed, 30 Aug 2017 12:09:16 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA9AAD9734@nkgeml513-mbx.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------3819175EA9E039DF80C9BA6F"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/0muyBW7I11-N1GNFdy42XG-lZjA>
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, 30 Aug 2017 11:09:23 -0000

Hi Qin,

On 28/08/2017 11:13, Qin Wu wrote:
>
> [DB3] I completely agree; my point is to provide some information to 
> the customer about how the service might behave if they request a 
> particular value for the MTU.
>
> [Qin-3]: I prefer to keep as it does, but if you insist, we can 
> consider to add something like this:
>
> “if the requested svc-mtu cannot be fulfilled, the management system 
> should return a error message indicating the fulfillment is not 
> possible.  How this SHOULD be communicated by the SP to the customer 
> via a mechanism that is out of scope for this document.”
>

This doesn't really address my point.  What does it mean for the 
requested svc-mtu to be fulfilled?  What behaviour is the customer 
actually requesting by setting this leaf to a particular value?


     David

-- 
David Ball
<daviball@cisco.com>