Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.txt - Extended to 8/30/2019

"Susan Hares" <shares@ndzh.com> Mon, 19 August 2019 18:16 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2659812083A for <i2rs@ietfa.amsl.com>; Mon, 19 Aug 2019 11:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.947
X-Spam-Level:
X-Spam-Status: No, score=0.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 4KOt1NgXZOn4 for <i2rs@ietfa.amsl.com>; Mon, 19 Aug 2019 11:16:07 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81F9012018B for <i2rs@ietf.org>; Mon, 19 Aug 2019 11:16:07 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.25.185.146;
From: "Susan Hares" <shares@ndzh.com>
To: "'Qin Wu'" <bill.wu@huawei.com>, "'tom petch'" <ietfc@btconnect.com>, <i2rs@ietf.org>
Cc: <russ@riw.us>
Date: Mon, 19 Aug 2019 14:15:58 -0400
Message-ID: <012801d556ba$26ed2840$74c778c0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdVWugUopJYG1STVTJSHn4jV8n8OFg==
Content-Language: en-us
X-Antivirus: AVG (VPS 190819-4, 08/19/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/74Xvn38Buam5ZbjBghPs_miiiNk>
Subject: Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.txt - Extended to 8/30/2019
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2019 18:16:09 -0000

Tom and Qin:

During the summer as an chair, I am a bit more flexible on the closing for
WGs.    This WG LC was to close by this week, but I will extended it 2 weeks
to allow two things to  happen: 
1) RTGWG to provide WG LC 
2) I2RS members to address Qin's changes to address Tom Petch's comments. 

Cheerily, Sue Hares 

-----Original Message-----
From: Qin Wu [mailto:bill.wu@huawei.com] 
Sent: Monday, August 19, 2019 1:04 AM
To: tom petch; Susan Hares; i2rs@ietf.org
Cc: russ@riw.us
Subject: RE: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.txt

Hi, Tom:
Thank for your valuable review. See comments inline below.
-----邮件原件-----
发件人: i2rs [mailto:i2rs-bounces@ietf.org] 代表 tom petch
发送时间: 2019年8月16日 20:00
收件人: Susan Hares <shares@ndzh.com>om>; i2rs@ietf.org
抄送: russ@riw.us
主题: Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.txt

Not ready

The text says
    /*Consider udpating this part to make use of
draft-ietf-softwire-iftunnel*/ Well yes, consider it and come to a
conclusion otherwise I cannot see how this is ready to advance.
[Qin]: Good catch, will fix this. The idea is to align with RFC7224 and
reuse iana-interface-type.

The YANG module contains many references - good - but they are not in the
I-D references; again, not ready to advance.  I see

4761
4762
6325
6326
7348

802.1ad
802.1ah
802.1Q

[Qin]:Fixed.
IANA considerations references RFC7950 - RFC 6020 is better here as all that
RFC7950 says is go see RFC6020.
[Qin]:Agree, will update based on your suggestion.

OLD

       This version of this YANG module is part of
       draft-ietf-i2rs-yang-l2-network-topo-07;

NEW
       This version of this YANG module is part of
        "RFC XXXX: A YANG Data Model for Layer-2 Network Topologies"

[Qin]:Fixed.
You also have this unsuitable reference twice in the state module
[Qin]:Fixed.
The state module lacks references for the imports [Qin]:Fixed.
The state module description clause seems misleading; it is only the state
part of a module when NMDA is not supported.
[Qin]:Fixed.
Appendix A - is it Normative?  The customary convention is the Appendices
are not unless stated otherwise and there is no statement here.
[Qin]:No, will make this clear.
'An Example' does not use the addresses set aside for documentation
[Qin]:Good catch, will use RFC7042 recommended address range.
What is the closing date for this Last call?

Tom Petch

----- Original Message -----
From: "Susan Hares" <shares@ndzh.com>
To: <i2rs@ietf.org>
Cc: <russ@riw.us>
Sent: Friday, August 09, 2019 4:42 PM


> Greetings:
>
>
>
> This draft on L2 network topology has been reviewed by the I2RS WG 3
times.
>
> However, in discussion with the ADs it is deemed appropriate to do one
more
>
> WG LC and include any input from rtgwg or grow.
>
>
>
> Please indicate whether you support publication of this document.
>
> In your comments, please indicate "support" or no "support".
>
>
>
> If you feel there issues that need to be resolved,
>
> Please indicate whether these issues are editorial,
>
> Yang syntax, or technical content.
>
>
>
> It would be helpful to indicate whether you know of
>
> Network deployments or potential network deployments of this draft.
>
>
>
> Cheerily,
>
>
>
> Sue Hares
>
>
>
>


------------------------------------------------------------------------
--------


> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>

_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs