Re: [i2rs] Magnus Westerlund's Discuss on draft-ietf-i2rs-yang-l2-network-topology-14: (with DISCUSS)

Qin Wu <bill.wu@huawei.com> Fri, 11 September 2020 01:02 UTC

Return-Path: <bill.wu@huawei.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 5FA7D3A0FA8; Thu, 10 Sep 2020 18:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, 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 8wzy8ANyXFby; Thu, 10 Sep 2020 18:02:32 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0ECF3A095D; Thu, 10 Sep 2020 18:02:31 -0700 (PDT)
Received: from lhreml701-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 0977FB5ABEF49C69301B; Fri, 11 Sep 2020 02:02:29 +0100 (IST)
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Fri, 11 Sep 2020 02:02:28 +0100
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1913.5 via Frontend Transport; Fri, 11 Sep 2020 02:02:28 +0100
Received: from DGGEML511-MBS.china.huawei.com ([169.254.4.186]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0487.000; Fri, 11 Sep 2020 09:01:17 +0800
From: Qin Wu <bill.wu@huawei.com>
To: tom petch <ietfc@btconnect.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, "shares@ndzh.com" <shares@ndzh.com>
CC: "draft-ietf-i2rs-yang-l2-network-topology@ietf.org" <draft-ietf-i2rs-yang-l2-network-topology@ietf.org>, "i2rs@ietf.org" <i2rs@ietf.org>, 'Martin Vigoureux' <martin.vigoureux@nokia.com>, "i2rs-chairs@ietf.org" <i2rs-chairs@ietf.org>
Thread-Topic: Magnus Westerlund's Discuss on draft-ietf-i2rs-yang-l2-network-topology-14: (with DISCUSS)
Thread-Index: AdaH1t+I6GSssN0oQCCeBiwfQsHn3g==
Date: Fri, 11 Sep 2020 01:01:16 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAAD9B2809@dggeml511-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.101.103]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/KARw0B9X3nIRT1nKh-GJTqsUyNY>
Subject: Re: [i2rs] Magnus Westerlund's Discuss on draft-ietf-i2rs-yang-l2-network-topology-14: (with DISCUSS)
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: Fri, 11 Sep 2020 01:02:35 -0000

Thanks Tom for feedback and clarification, not actually familiar with IEEE process and just thought IEEE 802.1 is assigned to do the formal job. Maybe I missed anything and will check my AD.
If you have any suggestion, please also let us know, thanks!

-Qin
-----邮件原件-----
发件人: tom petch [mailto:ietfc@btconnect.com] 
发送时间: 2020年9月11日 0:12
收件人: Qin Wu <bill.wu@huawei.com>om>; Magnus Westerlund <magnus.westerlund@ericsson.com>om>; Rob Wilton (rwilton) <rwilton@cisco.com>om>; shares@ndzh.com
抄送: draft-ietf-i2rs-yang-l2-network-topology@ietf.org; i2rs@ietf.org; 'Martin Vigoureux' <martin.vigoureux@nokia.com>om>; i2rs-chairs@ietf.org
主题: Re: Magnus Westerlund's Discuss on draft-ietf-i2rs-yang-l2-network-topology-14: (with DISCUSS)

From: i2rs <i2rs-bounces@ietf.org> on behalf of Qin Wu <bill.wu@huawei.com>
Sent: 10 September 2020 15:02

Hi, Magnus and Rob:
Thanks to Sue for helping reaching IEEE community, we have received IEEE802.1 Feedback on draft-ietf-i2rs-yang-l2-network-topology-15

<tp>
Well yes, but as the chain of e-mails makes clear this is informal feedback from an individual in IEEE 802.1 YANGsters group and not a formal liaison response (which I expect is fine).  My sense is that the IEEE has a somewhat different view of Bridge ID and VLAN ID to that which I held beforehand from IETF I-D and will look at other uses of VLAN ID, in particular, in a different light as a result.  Perhaps it is time I re-read 802.1Q!

Tom Petch







https://mailarchive.ietf.org/arch/msg/i2rs/NtnhmhouhLbSv6nU2xX_wFw0to8/
and address them in v-17 and v-18
https://mailarchive.ietf.org/arch/msg/i2rs/NzDVHfaWhSgt167AXf-ay_pqRH8/
The latest update is available at:
https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topology/
Let us know if you can clear the DISCUSS now, thanks.

-Qin (on behalf of authors)
-----邮件原件-----
发件人: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
发送时间: 2020年7月10日 1:25
收件人: shares@ndzh.com; iesg@ietf.org
抄送: draft-ietf-i2rs-yang-l2-network-topology@ietf.org; i2rs-chairs@ietf.org; i2rs@ietf.org
主题: RE: Magnus Westerlund's Discuss on draft-ietf-i2rs-yang-l2-network-topology-14: (with DISCUSS)

Hi,

Sue, I raised a discuss on this just to ensure that IESG would discuss the issue today. I raised it based on the Glenn Parsons request on the IEEE-IETF mailing list and that there where apparently some confusion.

So I don't really know which failures did occur in this case. I think it would be good to analyze it. I would suspect a combination of issues. Likely including that turn over among AD makes people loose history and process.

>From my personal perspective, I as AD would appreciate a WG chairs that 
>reach
out to the AD when they thing there might be need for coordination with external bodies. I understand that for this document they might not be as clear.

Cheers

Magnus Westerlund



> -----Original Message-----
> From: Susan Hares <shares@ndzh.com>
> Sent: den 9 juli 2020 16:28
> To: Magnus Westerlund <magnus.westerlund@ericsson.com>om>; 'The IESG'
> <iesg@ietf.org>
> Cc: draft-ietf-i2rs-yang-l2-network-topology@ietf.org; 
> i2rs-chairs@ietf.org; i2rs@ietf.org
> Subject: RE: Magnus Westerlund's Discuss on 
> draft-ietf-i2rs-yang-l2-network-
> topology-14: (with DISCUSS)
>
> Magnus:
>
> Thank you for raising this process discuss.
>
> The authors and I strong desire the I2RS model to be a NM management 
> model that imports the appropriate things from IEEE.
>
> I have two points you should add to your process discuss:
>
> 1) Where did the coordination instructions change for the WG chair?
>
> In the midst of the discussion within the IESG would you please 
> consider how to provide better instructions for the lowly chair and authors on this
> topic.   In
> the past, the IESG sent information to IEEE-IETF.    (I was scribe during
> the
> first meeting of the IETF-IESG over the TRILL issue).   I was the TRILL
> chair for
> the last years of the TRILL WGs life.   I have participated in the IEEE
> 802.1 and
> IETF during the TRILL issue when we were trying to resolve a common
> management for TRILL between IEEE and IETF.   During that time, it was
> important that a few focused voices discussed issues regarding TRILL.  
> It would help me to understand when this transitioned to chairs being 
> able to send requests to the IEEE-IETF coordination list.
>
> We also asked for numerous reviews by Yang Doctors who were 
> knowledgeable regarding IETF.  I delayed publication request several times
> until it appeared all issues were resolved.   This "sudden" surprise is
> indeed
> amazing since the L2 is 5 years old.  It is older than the 
> 8021Qcp-2018 official models.
>
>
> 2) Why are I2RS topology models are not seen as Network Management by 
> the IEEE.
>
> These are virtual topology models used by open source platforms for 
> management.  (E.g. Open Daylight).
>
> Sue
>
> -----Original Message-----
> From: Magnus Westerlund via Datatracker [mailto:noreply@ietf.org]
> Sent: Thursday, July 9, 2020 7:44 AM
> To: The IESG
> Cc: draft-ietf-i2rs-yang-l2-network-topology@ietf.org; 
> i2rs-chairs@ietf.org; i2rs@ietf.org
> Subject: Magnus Westerlund's Discuss on 
> draft-ietf-i2rs-yang-l2-network-
> topology-14: (with DISCUSS)
>
> Magnus Westerlund has entered the following ballot position for
> draft-ietf-i2rs-yang-l2-network-topology-14: Discuss
>
> When responding, please keep the subject line intact and reply to all 
> email addresses included in the To and CC lines. (Feel free to cut 
> this introductory paragraph, however.)
>
>
> Please refer to 
> https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topol
> ogy/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> This is a process discuss.
>
> There apparently have been a failure to coordinate this with IEEE per 
> discussion on the IETF-IEEE mailing list.
>
> Glenn Parsons requested that this was deferred to give IEEE time to 
> review it at their plenary next week. I think this time should be 
> given before approving this document.
>
>
>
>
>

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