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

"Rob Wilton (rwilton)" <rwilton@cisco.com> Fri, 11 September 2020 11:45 UTC

Return-Path: <rwilton@cisco.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 8B07B3A0F33; Fri, 11 Sep 2020 04:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level:
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 header.b=ZGSHicxo; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Nd4jphny
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 BDdmPNT51xqt; Fri, 11 Sep 2020 04:45:22 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B1EC3A0F32; Fri, 11 Sep 2020 04:45:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13848; q=dns/txt; s=iport; t=1599824722; x=1601034322; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=tGtcbQI/AYRvOTGaK02OPiNoYjhMqXl/+YFm0N+M6eo=; b=ZGSHicxosDnZXLsH6ImUUW8NhaOgs5wQwBA8xzTPyPbsnHxx3qFKKX4m jM/txeKGxfHp0zULyE7iW8PJdp7Ma+qg7PjuKLmN0f2HLgIxYZAvcyVjq R+sH81B+GJ4bWensPqeTa8G2hsw6JD4JYUBc/7bnk3arhFGMUanhOUtYV 0=;
IronPort-PHdr: =?us-ascii?q?9a23=3AV/nT8B2VeCC1FCoRsmDT+zVfbzU7u7jyIg8e44?= =?us-ascii?q?YmjLQLaKm44pD+JxWFv6dnkFTOW4PW4O4CgO3T4OjsWm0FtJCGtn1KMJlBTA?= =?us-ascii?q?QMhshemQs8SNWEBkv2IL+PDWQ6Ec1OWUUj8yS9Nk5YS8zibFrUpHC58XgZHR?= =?us-ascii?q?CsfQZwL/7+T4jVicn/3uuu+prVNgNPgjf1Yb57IBis6wvLscxDiop5IaF3wR?= =?us-ascii?q?zM8XY=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DABQAnYltf/5BdJa1ZBhwBAQEBAQE?= =?us-ascii?q?HAQESAQEEBAEBQIFPgVJRB3BZLywKhC6DRgONaIECl2+BQoERA1ULAQEBDQE?= =?us-ascii?q?BGA0IAgQBAYRLAheCDAIkOBMCAwEBCwEBBQEBAQIBBgRthVwMhXIBAQEBAwE?= =?us-ascii?q?BEBERDAEBBScLAQsEAgEGAhEEAQEDAiMDAgICJQsUAQgIAQEEAQ0FCAwFCYM?= =?us-ascii?q?FgksDLgEDC5d2kGkCgTmIYXaBMoMBAQEFMIEDARNBgx4YghADBoEOKoFcgRW?= =?us-ascii?q?DaYJBhBEbgUE/gRFDghg1PoJcAQEBAQEBgSYBEgEREoMVM4Itj2MgAzGCcIE?= =?us-ascii?q?ZiHiZTQqCZYhsi15thSKDCTiJO4U2jjGSW4FwiGWVDAIEAgQFAg4BAQWBayN?= =?us-ascii?q?nWBEHcBU7gjUBATJQFwINjh8MFxSDOoUUhUJ0AjUCBgEJAQEDCXyMJASBMQG?= =?us-ascii?q?BEAEB?=
X-IronPort-AV: E=Sophos;i="5.76,415,1592870400"; d="scan'208";a="828011241"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Sep 2020 11:45:20 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 08BBjKvn019506 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 11 Sep 2020 11:45:20 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 11 Sep 2020 06:45:20 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 11 Sep 2020 06:45:19 -0500
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Fri, 11 Sep 2020 06:45:19 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bee15LKjOUTgC7YAzTyphfPZHZsoO5x3UGqXEKo3Tj7gE6JLw/cX7dEcsr+wzxA4w4Dkff6bd8uRk7N6b7FKyjWJLjJfBGvJaMX9szCk9rqY0qAiH55DDUd3nCKL/Rj5Uf0tqQrIvxlN6Q5OiuDjoUTKXZjOFcsE5eI06xINMouK4E7gM6Vn9RhBDB8KmryRmSgC53duMywFKA566S2S8w3zylpNA2EM6N+iU/wS/HCZjRlU9ggSqquL9XVAWZx9WdQH962crSzT4wtFsSAbw/BvZ+fxdH4D4bhL4wwTH0SuYpZiELbbZNIO4uCRtMaOx47HbkqYGiVtHDED6bJ2EA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tGtcbQI/AYRvOTGaK02OPiNoYjhMqXl/+YFm0N+M6eo=; b=XIMN4+WZ6TA9jbDhVFEV15/pF/VTIOV1hh01sypWX2UxYmYx80m6bVpQM3dlW34NVt0eHfKKZLKAzBC9dxQrC8y9fotouoqmtEMynQjp9b4A+29x7H1WCcBz3x3YUcIItDCURI16gNDShYxeUPtOWrGFd7pxznWz8VgXQaq7dg/x1NQ3GZJ77v/830adO17y7YdS3zxOHEVVfk9BuuOdHHGO3SJfQK2TU10dYwifeJaTrri6F4lim7L+gfux+YftceakYjoGtJn7xEksp51xnkAWTIsxSr5t51Y2xa1nYAYlbMeYZuT2WSnpEd9snsPXinNHVdf3WCGf4YAVj1JChA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tGtcbQI/AYRvOTGaK02OPiNoYjhMqXl/+YFm0N+M6eo=; b=Nd4jphnyGydJeu7tyAdbvWtQNswzYpll06KrBF+mo7r4L3unKbbeyBoItMMu/1KdESGPd3tdhtFCyZLl12IBOntfnTHktepUhuTbIw3rFMXIuH5cZf/hC5NlpmmYZx4Nmnu+zp1fsI/ItkLoD0fujNZScwAtT+yU4WYcQNJ41f0=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (2603:10b6:208:190::17) by BL0PR11MB3250.namprd11.prod.outlook.com (2603:10b6:208:63::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16; Fri, 11 Sep 2020 11:45:18 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::4d3f:f3e:add7:dfc1]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::4d3f:f3e:add7:dfc1%3]) with mapi id 15.20.3370.017; Fri, 11 Sep 2020 11:45:18 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: tom petch <ietfc@btconnect.com>, Qin Wu <bill.wu@huawei.com>, "Magnus Westerlund" <magnus.westerlund@ericsson.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+I6GSssN0oQCCeBiwfQsHn3gAU3EGaAAErRZA=
Date: Fri, 11 Sep 2020 11:45:18 +0000
Message-ID: <MN2PR11MB436695F999FAF85815F46472B5240@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <B8F9A780D330094D99AF023C5877DABAAD9B2809@dggeml511-mbs.china.huawei.com> <AM7PR07MB62487A65285D04F688C67D92A0240@AM7PR07MB6248.eurprd07.prod.outlook.com>
In-Reply-To: <AM7PR07MB62487A65285D04F688C67D92A0240@AM7PR07MB6248.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: btconnect.com; dkim=none (message not signed) header.d=none;btconnect.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [82.12.233.180]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f491e53b-d554-4cb0-833f-08d856482835
x-ms-traffictypediagnostic: BL0PR11MB3250:
x-microsoft-antispam-prvs: <BL0PR11MB3250C109552CCF8846B7D4C7B5240@BL0PR11MB3250.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: s8Jd6PCg8SzSXb6L7m6qFkDt7amuyCNpmX9SCuT/ZVJgXYyQfvdFgk8wGE7INloFnB6J6cvnwl+AL/h8IdSwYyPEUNqFkOvsAQ4gOUYvYP04BCOd8KX8PqZ/2Ep8sd9hX+rHI4fy6vXFv15tWmKbqT/C0bwnF9r1EhwIqVOcI24JnoEQrdpnDZoY6iqTyBKxN72bpQ1Dpwr8P6s5941lyEXQ7TA+gCtSH2NJQce2qLel8OVuJR4IDYQG6CkP78LvPGSCYJCxSSvzGvspXUNUhV7PaM3ppKwMbxyafRT6wHt+BGNRiz9ndvoN7qKtQo0onuFpY41Oiyk18i/tOeKRaPXTJGOYgaApB0WA01fOSwBfUl8oZDxihbxo0mxtKeHzjGXMRh22fZwGhlG7GUdgbw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR11MB4366.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(346002)(376002)(39860400002)(136003)(366004)(396003)(186003)(296002)(966005)(2906002)(9686003)(52536014)(5660300002)(55016002)(478600001)(86362001)(4326008)(53546011)(316002)(8676002)(26005)(71200400001)(6506007)(76116006)(54906003)(110136005)(7696005)(64756008)(66476007)(66946007)(8936002)(66446008)(66556008)(33656002)(83380400001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: UukXjRrSmoDvCi8O7nX0rngx+otaVoxnXSQWom6JBoV7KHfUXwz7t6PfnSIWTpjndpgH/5Za1P+g5ukZNdlZ0xKOFX3rU+DazJ6GB2EClAHWAAHE0PH+TyKPTLwpJVcgo+BBK7nqhC4GTwnpefrDCxPODr1C1znW53pHphQEpftr8UMH7AlEBarTGdZT4X07ceTB1dbh/O+DuaL66eKMi6tGnrxv6LvcPwwlK8MLYydFGRpvgvYfMQkKIxzi4hNpNhOQ0Pw4GyO2w3uY/PXRe3gXR2X3moz77Gkzrztv8F8zAX3D3RWbIQ1qqmUgCb8ISInVoZ9fDEJtYzV0SUCjxuND0nr5UhkdGK12daxAmtJllmviXnam+B13jUlrihg4Zvt5qJ2xm4IdecRrQUs9p59BmW7HXIGRLw+uEhD3GkAbkEeF/aI/JJF69Ap+ndI9Lb36VQs1SzXGpQ9qINgvoonkK8S11qXcH/IqLaxlvq/asSIiSHQaYm7ulubk9xw0CkotLu82iB3Vv5aIw5WtCET2KABushFNyuBubehhG7m2CdFJfwqsX6ES2YdNJ292BsYMr2gJbeLwTNpv1uKGisbYZWnYxcAd1aqkzGLuAHnX8BNzKRQbAukhjB/TaOsd3f8foQYvrG7VWCeaiUqcPw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR11MB4366.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f491e53b-d554-4cb0-833f-08d856482835
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Sep 2020 11:45:18.2766 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ciYTNnUaApa46U+1SJ2IRZrHqaeubGZBxrB0LOsyBJdV/4+TwPZTMaSDnn6gyCuY5m7LQSEaPVS4tC/aIUfKwg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR11MB3250
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/sm87pkRVNaZmQ8Y4Hz8q7o6IdjI>
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 11:45:25 -0000

Hi All,

This was on the agenda to be discussed in the IEEE Yangsters meeting on Weds 9th, but unfortunately that meeting was cancelled at short notice.  I'm hopefully that this can be discussed in next week's Yangsters meeting (16th).
	
My hope is for an agreement in that meeting that sufficient review has been down and any necessary changes have been made, such that the document can continue to progress in IETF without requiring any formal liaison statement between IEEE and IETF.

I attend the Yangsters meetings on a semi-regular basis anyway, plan to attend next week, and was intending to feedback the meeting conclusions via Martin.

Regards,
Rob


> -----Original Message-----
> From: tom petch <ietfc@btconnect.com>
> Sent: 11 September 2020 12:22
> To: Qin Wu <bill.wu@huawei.com>om>; Magnus Westerlund
> <magnus.westerlund@ericsson.com>om>; Rob Wilton (rwilton)
> <rwilton@cisco.com>om>; shares@ndzh.com
> Cc: draft-ietf-i2rs-yang-l2-network-topology@ietf.org; i2rs@ietf.org;
> 'Martin Vigoureux' <martin.vigoureux@nokia.com>om>; i2rs-chairs@ietf.org
> Subject: Re: Magnus Westerlund's Discuss on draft-ietf-i2rs-yang-l2-
> network-topology-14: (with DISCUSS)
> 
> 
> 
> ________________________________________
> From: Qin Wu <bill.wu@huawei.com>
> Sent: 11 September 2020 02:01
> To: tom petch; Magnus Westerlund; Rob Wilton (rwilton); shares@ndzh.com
> Cc: draft-ietf-i2rs-yang-l2-network-topology@ietf.org; i2rs@ietf.org;
> 'Martin Vigoureux'; i2rs-chairs@ietf.org
> Subject: RE: Magnus Westerlund's Discuss on draft-ietf-i2rs-yang-l2-
> network-topology-14: (with DISCUSS)
> 
> 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!
> 
> <tp>
> Qin
> The e-mail that caught my eye was from Glenn Parsons 26aug20 to the I2RS
> list pointing out that we were getting informal feedback from an
> individual (which I think is fine) but it does, for me, have a subtext
> that the IEEE commonly has more formal procedures than the IETF, and wants
> us to recognise that this is informal and that we could request a formal
> response via a liaison if the IETF wanted to.  So I think it fine to
> incorporate the information that Don has provided but it would be going
> too far to say 'This is what the IEEE says' because the IEEE has not said
> anything in this exchange of e-mail, only put us in touch with an
> individual.  Equally I would think it wrong to ascribe comments to the
> IEEE, rather to Don.
> 
> It was Eric that raised the issue of IEEE involvement back in July so he
> is one that needs to know this while Benjamin also raised questions of how
> IEEE 802.1Q handled some unusual looking objects and Sue mentioned the
> possibility of a Liaison and Alvaro then said that a formal liaison was
> not needed so I see those as the key actors who need to know we took the
> informal route.
> 
> Technically I have not caught up with all the detail that Don provided and
> will likely have to read IEEE 802.1Q before I do ie we will likely have an
> RFC published before I get there!
> 
> Tom Petch
> 
> -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