Re: [netmod] New Version Notification for draft-wwz-netmod-yang-tunnel-cfg-00.txt
"Aijun Wang" <wangaijun@tsinghua.org.cn> Thu, 16 July 2015 02:31 UTC
Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 472941B350C for <netmod@ietfa.amsl.com>; Wed, 15 Jul 2015 19:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level:
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_210=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_29=0.6, T_FILL_THIS_FORM_SHORT=0.01, 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 XErzqkfbEMVF for <netmod@ietfa.amsl.com>; Wed, 15 Jul 2015 19:31:10 -0700 (PDT)
Received: from tsinghua.org.cn (mail.tsinghua.org.cn [211.151.65.103]) by ietfa.amsl.com (Postfix) with ESMTP id 890CB1B3503 for <netmod@ietf.org>; Wed, 15 Jul 2015 19:31:06 -0700 (PDT)
Received: from ctbriwangaij (unknown [219.142.69.76]) by app1 (Coremail) with SMTP id Z0GX06C7tgHq9qZV17MqCw==.49520S2; Thu, 16 Jul 2015 08:12:41 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Qin Wu' <bill.wu@huawei.com>, netmod@ietf.org
References: <00de01d0b7a1$323339e0$9699ada0$@org.cn> <B8F9A780D330094D99AF023C5877DABA847C35F3@nkgeml501-mbs.china.huawei.com> <004b01d0bed1$eb2558c0$c1700a40$@org.cn> <B8F9A780D330094D99AF023C5877DABA847C5BD6@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA847C5BD6@nkgeml501-mbs.china.huawei.com>
Date: Thu, 16 Jul 2015 10:30:19 +0800
Message-ID: <007201d0bf6f$64eb6d50$2ec247f0$@org.cn>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0073_01D0BFB2.730EAD50"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHQvq4XZV95oTjfskWTpLL6pUXaNJ3cGd0wgABLsHCAAOw54A==
Content-Language: zh-cn
X-CM-TRANSID: Z0GX06C7tgHq9qZV17MqCw==.49520S2
X-Coremail-Antispam: 1U3129KBjvJXoWxWFy3tryUZw1UKryfCrW8Crg_yoWrAw1rpF W5GFZ8Kr4DGr1rCan7Za18Xw4Y9393K3y5uFn5G3y8A345Jry3Zryjk3yayF47CrWrXr1j vrWj93WUuayDZ3DanT9S1TB71UUUUUUv73VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjPqb7 Iv0xC_Jr1lb4IE77IF4wAFF20E14v26r1j6r4UM7C26xCjj4IEI4klw4CSwwAFxVCaYxvI 4VCIwcAKzIAtM2AExVA0xI801c8C04v7McIj6x8ErcxFaVAv8VW8AwACY4xI64xv4xAvw2 CEb4CIw280cs4lx4CE17CEb7AF67AKxVWUXVWUAjIFyTuYvjfUFE_MDUUUU
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/UHbcxNC_JxMgBHSSxYmW3rqIR0Y>
Subject: Re: [netmod] New Version Notification for draft-wwz-netmod-yang-tunnel-cfg-00.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2015 02:31:16 -0000
Hi, Qin, I think the answer from Robert to Mahesh on July 14(please see the detail on the attached mail) best describes the key point of " draft-wilton-netmod-intf-ext-yang-00": ".... Yes, I agree that a better name would be helpful, and definitely welcome suggestions. The problem is that the module doesn't just apply to physical interfaces. Quite a lot of the properties apply to any interface on a router/switch, and some of the properties I would think could apply to any network interface (e.g. MTU). Perhaps something related to lower-layer-interface-extensions?....". The above statement show clearly the main concern of " draft-wilton-netmod-intf-ext-yang-00", which is different from the " draft-wwz-netmod-yang-tunnel-cfg-00.txt" . The latter draft concern mainly the "upper-layer-interface-extensions". Some characteristics may have same name, but different denotation(for example "MTU", it has different value in lower-layer-interface and upper-layer-interface). >From the model user viewpoint, it is benefit to separate the lower-layer-interface and upper-layer-interface into two yang models, we should clarify with deep consideration the belonging of the seeming "over-lapping" characteristics, although there is not much of them from these two drafts now. Aijun Wang China Telecom Corporation Limited Beijing Research Institute Intelligent Network Product Line Tel : 010-58552347 Mobile: 13301168517 -----Original Message----- From: Qin Wu [mailto:bill.wu@huawei.com] Sent: Wednesday, July 15, 2015 7:38 PM To: Aijun Wang; netmod@ietf.org Subject: RE: [netmod] New Version Notification for draft-wwz-netmod-yang-tunnel-cfg-00.txt Aijun: Please see my reply to Robert, I am afraid draft-wilton-netmod-intf-ext-yang-00 is not limited to describe common l2 characteristic of the interface. Then tunnel interface in draft-wwz-netmod-yang-tunnel-cfg-00 and interface extension proposed in draft-wilton-netmod-intf-ext-yang-00 share some Common properties, so what is the better model design? Place all the properties in one place under tunnel interface or move these properties in In the same level as other properties defined under if:interface? -Qin -----邮件原件----- 发件人: Aijun Wang [mailto:wangaijun@tsinghua.org.cn] 发送时间: 2015年7月15日 15:43 收件人: Qin Wu; netmod@ietf.org 主题: RE: [netmod] New Version Notification for draft-wwz-netmod-yang-tunnel-cfg-00.txt Hi, Qin: Thanks for your comments first. Below is my answer to your question: 1. As you pointed out, " draft-wilton-netmod-intf-ext-yang-00" focuses mainly on the common layer 2 characteristic of one interface, it augments the ietf: if-interface yang model and compensates the characteristic of one physical interface. 2. Draft "draft-wwz-netmod-yang-tunnel-cfg-00.txt" designs the general tunnel interface model on top of the physical interface model, It covers and references the characteristics defined both in basic ietf: if-interface and its augment layer2 characteristic model, for example that defined in "draft-wilton-netmod-intf-ext-yang-00". Do the above descriptions clarify the relationship between them? Best Regards. Aijun Wang China Telecom Corporation Limited Beijing Research Institute Intelligent Network Product Line -----Original Message----- From: Qin Wu [mailto:bill.wu@huawei.com] Sent: Wednesday, July 15, 2015 11:27 AM To: Aijun Wang; netmod@ietf.org Subject: RE: [netmod] New Version Notification for draft-wwz-netmod-yang-tunnel-cfg-00.txt Authors: I think this draft will be useful when we consider to choose and configure large number of different technology specific tunnels that share a lot of common properties. One question I have here is how this draft is related to draft-wilton-netmod-intf-ext-yang-00? If my understanding is correct, your draft is about interface extension for tunneling management. draft-wilton-netmod-intf-ext-yang-00 focuses on interface extension for L2 sub-interface. But two draft follows two different model design, you specify common properties within tunnel container while draft-wilton-netmod-intf-ext-yang-00 specifies common properties directly within if:interface. -Qin -----邮件原件----- 发件人: netmod [mailto:netmod-bounces@ietf.org] 代表 Aijun Wang 发送时间: 2015年7月6日 12:07 收件人: netmod@ietf.org 主题: [netmod] New Version Notification for draft-wwz-netmod-yang-tunnel-cfg-00.txt Hi, all: We submitted one new draft (https://tools.ietf.org/html/draft-wwz-netmod-yang-tunnel-cfg-00) that described one general model for the tunnel services used within service provider network. It summaries the common characteristic of the current various tunnel protocols and can be used as one fundamental model for the specific tunnel technology. Any feedback is welcome. Best Regard. -----Original Message----- From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] Sent: Friday, July 03, 2015 4:21 PM To: Zitao Wang; Yan Zhuang; Aijun Wang; Zhuangyan; Zitao Wang; Aijun Wang Subject: New Version Notification for draft-wwz-netmod-yang-tunnel-cfg-00.txt A new version of I-D, draft-wwz-netmod-yang-tunnel-cfg-00.txt has been successfully submitted by Zitao Wang and posted to the IETF repository. Name: draft-wwz-netmod-yang-tunnel-cfg Revision: 00 Title: YANG Data Model for Tunnel Management Document date: 2015-07-03 Group: Individual Submission Pages: 21 URL: https://www.ietf.org/internet-drafts/draft-wwz-netmod-yang-tunnel-cfg-00.txt Status: https://datatracker.ietf.org/doc/draft-wwz-netmod-yang-tunnel-cfg/ Htmlized: https://tools.ietf.org/html/draft-wwz-netmod-yang-tunnel-cfg-00 Abstract: This document defines a YANG data model for the configuration and management of generic tunnels. The data model includes configuration data and state data. And it can serve as a base model which is augmented with technology-specific details in other, more specific tunnel models. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
--- Begin Message ---Hi Mahesh, Thanks for the comments. Please see inline ... On 14/07/2015 17:21, Mahesh Jethanandani wrote: Robert, I have read your draft and consider it useful for folks who are trying to use/configure/monitor particular characteristics of a physical interface. While it is an extension of the interfaces module, a lot of modules are extensions of the interface module. A more appropriate name would probably help convey the contents of the module. How about physical-interface-extensions or phys-intr-ext for short? Yes, I agree that a better name would be helpful, and definitely welcome suggestions. The problem is that the module doesn't just apply to physical interfaces. Quite a lot of the properties apply to any interface on a router/switch, and some of the properties I would think could apply to any network interface (e.g. MTU). Perhaps something related to lower-layer-interface-extensions? More comments on the draft. 3.2. Is there a counter kept for the actual short transition changes that were suppressed? Yes, there should be. I had initially concentrated on the config side, but probably operation data needs to be considered as well. 3.6 The general suggestion in YANG is to provide for one way to do things, and leave other ways of specifying or configuring to extensions/deviations etc. With that in mind, I would think keeping one leaf for MTU that is the max. size of the layer 2 frame including header and payload would make sense. OK. Yes, I think that I'm coming to the same conclusion: Although having a single MTU value will make it harder to implement for some vendors, it makes it easier for users of the YANG module. 4. I am not a particular fan of creating yet another module for ethernet-like interfaces, when I assume there is going to be a ethernet-interface module. Is there something in this module that cannot be minimally represented by a more general IEEE ethernet-interface module? I don't envisage there needing to be any additional configuration in the Ethernet-like module beyond what is already there - possibly some Ethernet framing related statistics. There are a few reasons that I put this in a separate module to ethernet: 1) It doesn't just apply to 802.3 Ethernet interfaces, but any interfaces that use Ethernet framing. 2) I wasn't sure whether the IEEE 802.3 WG would want to standardize a module that covers other interface types beyond native Ethernet. 3) There is already an etherlike.mib (although that only covers stats that applies to any Ethernet framed interfaces). Is your primary concern over the fact that this module is too small to justify its independent existence? Thanks, Rob Thanks. On Jul 8, 2015, at 9:11 AM, Robert Wilton <rwilton@cisco.com> wrote: Hi, I have submitted a new draft for provides several augmentations to the ietf if:interfaces to define configuration YANG for basic interface parameters that are commonly supported on network devices. E.g. it is includes leaves such as bandwidth, carrier delay, dampening, loopback, mtu, & sub-interface parent ref, and configurable interface MAC addresses. I am hoping that this draft could be adopted and standardized by the netmod WG. https://datatracker.ietf.org/doc/draft-wilton-netmod-intf-ext-yang/ Any comments or feedback is appreciated. Potential points of interest/discussion may be: - Is it acceptable to define standard YANG for features that are not backed by any formal standard if they are commonly implemented? - We've tried to restrict the leaves to just the interface types (using when if:type = ...) that the configuration applies to rather than adding them to all interfaces. Feedback would be welcome on whether this approach is a good idea/maintainable. - For MTU, I've defined two different MTU leaves because devices program interface MTU in different ways based on whether the configured MTU value includes the L2 header overhead or not. Is this a reasonable approach? Thanks, Rob _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod Mahesh Jethanandani mjethanandani@gmail.com--- End Message ---
- [netmod] New Version Notification for draft-wwz-n… Aijun Wang
- Re: [netmod] New Version Notification for draft-w… Qin Wu
- Re: [netmod] New Version Notification for draft-w… wangzitao
- Re: [netmod] New Version Notification for draft-w… Aijun Wang
- Re: [netmod] New Version Notification for draft-w… Qin Wu
- Re: [netmod] New Version Notification for draft-w… Aijun Wang