Re: [ieee-ietf-coord] Aid with draft-ietf-i2rs-yang-l2-network-topology-14

Russ Housley <housley@vigilsec.com> Wed, 08 July 2020 18:40 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D51E3A0793 for <ieee-ietf-coord@ietfa.amsl.com>; Wed, 8 Jul 2020 11:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 JdDzX8AaG9nK for <ieee-ietf-coord@ietfa.amsl.com>; Wed, 8 Jul 2020 11:40:33 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F0633A078A for <ieee-ietf-coord@ietf.org>; Wed, 8 Jul 2020 11:40:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id A2583300B04 for <ieee-ietf-coord@ietf.org>; Wed, 8 Jul 2020 14:40:30 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id aiMCi9QuTuB4 for <ieee-ietf-coord@ietf.org>; Wed, 8 Jul 2020 14:40:28 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-72-66-113-56.washdc.fios.verizon.net [72.66.113.56]) by mail.smeinc.net (Postfix) with ESMTPSA id A80DF300464; Wed, 8 Jul 2020 14:40:28 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <DED6CF06-1241-4ED9-8388-C458A7D68AA8@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8C074A51-2115-450C-BF42-1FC858A483AC"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Wed, 8 Jul 2020 14:40:29 -0400
In-Reply-To: <009e01d6554d$c89662f0$59c328d0$@ndzh.com>
Cc: draft-ietf-i2rs-yang-l2-network-topology@ietf.org
To: "<ieee-ietf-coord@ietf.org>" <ieee-ietf-coord@ietf.org>
References: <009e01d6554d$c89662f0$59c328d0$@ndzh.com>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/qJ9jFqLm_07iv0ZwSoXFuYzdrPo>
Subject: Re: [ieee-ietf-coord] Aid with draft-ietf-i2rs-yang-l2-network-topology-14
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jul 2020 18:40:36 -0000

This document is on the IESG agenda for tomorrow (2020-07-09), so a prompt response would be most helpful to avoid delay.

Russ


> On Jul 8, 2020, at 1:32 PM, Susan Hares <shares@ndzh.com> wrote:
> 
> Greetings IEEE and IETF coordination team: 
>  
> https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topology/ <https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topology/>
>  
> is being reviewed by the IESG for publication as an RFC.  It is being proposed by the I2RS WG.
> This draft provides a Yang model for L2 logical topologies that is being combined with L3 logical network models.  This model is being implemented by 3+ vendors.   In this process, we have the following questions that overlap between IEEE and IETF.   
>  
> 1) Regarding system management  MAC Address – 
>  
> Where in 802.1Q-2018 do I find the Yang model for the system management port for a switch? 
> By system management, I mean that port that configuration information is exchanged about.   I do not mean the port that sends LLDP packets. 
>  
> http://ieee802.org/1/files/public/YANGs/ieee802-dot1q-bridge.yang <http://ieee802.org/1/files/public/YANGs/ieee802-dot1q-bridge.yang>
>  
> 2)  Where can I find the latest status of yang models for the time sensitive work in 802.1? 
>  
> This model considers an L2 port as a termination point which is “in  use” for traffic, blocking traffic, down (due to hardware) or some other function.   We wish to determine if time sensitive configurations will provide another concept for port.  A general explanation would be helpful. 
>  
> 3) Would liaison give me  reading on what status the following references should be in
> draft-ietf-i2rs-yang-l2-network-topology?  
>  
> Ben Kaduk suggests that: 
>   a) Normative --> informative   RFC3688 and RFC7951 
>   b) Informative--> normative: [IEEE802.1Qcp], RFC7348
>  
> I’d appreciate your joint opinion on these matters.   We are trying to follow the best common practices of both IEEE and IETF in this draft.  
>  
> Susan Hares
> Co-chair I2RS
> Shepherd for draft-ietf-i2rs-yang-l2-network-topology
>  
> _______________________________________________
> ieee-ietf-coord mailing list
> ieee-ietf-coord@ietf.org <mailto:ieee-ietf-coord@ietf.org>
> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>