IETF Logo Mail Archive

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

Qin Wu <bill.wu@huawei.com> Wed, 13 September 2017 10:19 UTC

Return-Path: <bill.wu@huawei.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 D79E9133029 for <l3sm@ietfa.amsl.com>; Wed, 13 Sep 2017 03:19:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 WigVeHYMqkgz for <l3sm@ietfa.amsl.com>; Wed, 13 Sep 2017 03:19:07 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF819132D8E for <l3sm@ietf.org>; Wed, 13 Sep 2017 03:19:06 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DVJ14073; Wed, 13 Sep 2017 10:19:04 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 13 Sep 2017 11:19:02 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.219]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Wed, 13 Sep 2017 18:18:58 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Benoit Claise <bclaise@cisco.com>, David Ball <daviball@cisco.com>, "Jan Lindblad (jlindbla)" <jlindbla@cisco.com>
CC: l3sm <l3sm@ietf.org>, adrian <adrian@olddog.co.uk>
Thread-Topic: [L3sm] New Version Notification for draft-wu-l3sm-rfc8049bis-03.txt
Thread-Index: AQHTJvl1LUN8x/LDjUWvHXDkwgSGUKKnpP4ggAfVTYCAAR3wEIAAlZcA//8yNwCAAF2VAIAB5yXQ
Date: Wed, 13 Sep 2017 10:18:58 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9AB1404C@nkgeml513-mbx.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA9AAFC86C@nkgeml513-mbx.china.huawei.com> <b85886fa-7f8f-3e56-a8cb-7d72c4828fba@cisco.com> <B8F9A780D330094D99AF023C5877DABA9AB0DDDD@nkgeml513-mbx.china.huawei.com> <B5B3032C-A0CB-4BD0-9497-191F2554F723@cisco.com> <a1067e3b-3d3c-e964-70ab-5432663a69f8@cisco.com> <9e9c1527-08a9-bcef-c463-892bd9ed2f87@cisco.com>
In-Reply-To: <9e9c1527-08a9-bcef-c463-892bd9ed2f87@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.79.163]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9AB1404Cnkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.59B90618.0092, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.219, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 3559a394797ae8daebdfca3b7d662411
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/6f_ZvuByfB61Z_U7ACBBOGTXJ_0>
Subject: Re: [L3sm] New Version Notification for draft-wu-l3sm-rfc8049bis-03.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, 13 Sep 2017 10:19:09 -0000

Update done now.
https://www.ietf.org/rfcdiff?url1=draft-wu-l3sm-rfc8049bis-03&url2=draft-wu-l3sm-rfc8049bis-04

-Qin
发件人: Benoit Claise [mailto:bclaise@cisco.com]
发送时间: 2017年9月12日 21:13
收件人: David Ball; Jan Lindblad (jlindbla); Qin Wu
抄送: l3sm; adrian
主题: Re: [L3sm] New Version Notification for draft-wu-l3sm-rfc8049bis-03.txt

Dear all,

I was about the click the "IETF LC" call button, but I understand from Qin that a new document version will be produced.
I'll then click this button when the next version is posted.

Regards, B.

Completely agree.  In the case in question (address-allocation-type leaves), no value means "IPv4/IPv6 is not enabled for this site-network-access".



    David

On 12/09/2017 07:54, Jan Lindblad (jlindbla) wrote:
Qin, team,


  *
For the address-allocation-type leaves, I saw you removed the default (as agreed) but also added 'mandatory true' (which was not discussed).  Making these leaves mandatory does not address the problem - if anything, it makes it worse.  (Issue 15 from draft-02)
[Qin]: Fine to me, it looks we need to seek balance between making all parameters mandatory and making all parameters optional. I hope Jan will be happy with these changes.

Sometimes mandatory true is needed to make a sane model, but mandatory elements also tend to make a model clunky, examples large etc. So I generally like optional elements. The problem with optional elements is people tend to forget that it may not be obvious what a system is supposed to do when there is no value specified. Adding a default or text in the description is therefore important. At the end of the day, we're writing a contract. For interoperability to happen, there must be no holes in the contract that are open to (differing) interpretation.

So sure, you can have optional elements (this should even be the normal case), and they don't need to have a default statement. But if so, *describe* what it means; what the system is supposed to do. No value is also a value.

Best,
/jan




--

David Ball

<daviball@cisco.com><mailto:daviball@cisco.com>

v2.23.0 | Report a Bug | By Email