Return-Path: 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 E32FD3A0EEF; Wed, 8 Jul 2020 09:16:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.225 X-Spam-Level: * X-Spam-Status: No, score=1.225 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.276, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 PP-zfivdX_uK; Wed, 8 Jul 2020 09:16:06 -0700 (PDT) Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 67BC53A0ED5; Wed, 8 Jul 2020 09:16:05 -0700 (PDT) X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=50.107.91.217; From: "Susan Hares" To: "'Reshad Rahman \(rrahman\)'" , , Cc: , "'Benjamin Kaduk'" References: <004901d6553a$20e326f0$62a974d0$@ndzh.com> <268BBF05-F471-49E1-9F0C-C3E47F03B23D@cisco.com> <001701d6553f$202effe0$608cffa0$@ndzh.com> <9E6DF3E8-AFB8-4CDC-8621-BA04299AB7BE@cisco.com> In-Reply-To: <9E6DF3E8-AFB8-4CDC-8621-BA04299AB7BE@cisco.com> Date: Wed, 8 Jul 2020 12:15:58 -0400 Message-ID: <005101d65543$11779df0$3466d9d0$@ndzh.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0052_01D65521.8A686EF0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKyqZra/ByWDjwkrL20w3H89AReDQDnbJ7QAdxw3PkBfv3eWqcjGnGg Content-Language: en-us X-Antivirus: AVG (VPS 200708-4, 07/08/2020), Outbound message X-Antivirus-Status: Not-Tested X-Authenticated-User: skh@ndzh.com Archived-At: Subject: Re: [i2rs] [yang-doctors] draft-ietf-i2rs-yang-l2-network-topology X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jul 2020 16:16:08 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0052_01D65521.8A686EF0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Reshad:=20 =20 Juregen indicates my questions are not for IETF but for IEEE, and that = multiple system-macs may be implemented as a list. =20 =20 I=E2=80=99m looking at the IEEE yang model for 802-1Qcp (2018 update to = IEEE 802.1Q), but you can get the pre-release draft at (only editorial = nits are missing) at:=20 =20 http://www.ieee802.org/1/files/private/cp-drafts/d2/802-1Qcp-d2-2.pdf =20 The reason there are multiple IP addresses is that the single LAN can = have multiple IP addresses assigned to it. =20 In may routers/switches the single MAC port will have multiple virtual = ports. (cisco started this concept in the 1990s).=20 =20 Thanks for the help!=20 =20 Sue=20 =20 From: Reshad Rahman (rrahman) [mailto:rrahman@cisco.com]=20 Sent: Wednesday, July 8, 2020 12:09 PM To: Susan Hares; yang-doctors@ietf.org; i2rs@ietf.org Cc: martin.vigoureux@nokia.com; 'Benjamin Kaduk' Subject: Re: [yang-doctors] draft-ietf-i2rs-yang-l2-network-topology =20 Hi, =20 I was referring to management-address leaf-list in the same grouping = (see below). =20 I don=E2=80=99t have the expertise to answer your questions below, maybe = some YDs do. =20 Regards, Reshad. =20 grouping l2-node-attributes { description "L2 node attributes"; container l2-node-attributes { description "Contains L2 node attributes."; leaf-list management-address { type inet:ip-address; description "System management address."; } leaf sys-mac-address { type yang:mac-address; description "System MAC address."; } =20 =20 From: Susan Hares Date: Wednesday, July 8, 2020 at 11:48 AM To: "Reshad Rahman (rrahman)" , = "yang-doctors@ietf.org" , "i2rs@ietf.org" = Cc: "martin.vigoureux@nokia.com" , 'Benjamin = Kaduk' Subject: RE: [yang-doctors] draft-ietf-i2rs-yang-l2-network-topology =20 Reshad:=20 =20 Thank you for quick response. However, I=E2=80=99m confused. Where = do you see the IP address in the Yang snippet I sent? It is a MAC = Address (type yang:mac-address)? If the system port allows IP, it will = respond to the ARP request with the appropriate IP/MAC match in an ARP = reply. =20 =20 In real implementations I2rs implementers examined,=20 * L2 port with mgmt-mac-address seems to be used to only send LLDP = packets,=20 * L2 port with sys-mac-address seems to be used for management using = TCP/IP. =20 =20 If we swap the names, it did not work with the initial implementers of = the yang model. The I2RS Topology models are used for operational = management of switches and routers as logical units.=20 =20 Also, your response does not seem to match my questions:=20 =20 1) Is this the normal assumption for yang models?=20 2) If not, what is the normal assumption on system mac addresses?=20 3) Am I correct that switches with more than 1 system MAC will augment = their basic yang model with the second system MAC Address?=20 =20 I=E2=80=99m sorry to bother you but this document is being reviewed by = the IESG tomorrow (Thursday) and=20 I am the shepherd. I do not know how to answer some of the yang related = questions regarding multiple system ports to exchange management = configuration on. =20 =20 I had thought that netconf/restconf would be exchanged over the same = ports so the yang doctors would know what the normal custom should be.=20 =20 Thanks again!=20 =20 Sue =20 =20 =20 =20 =20 =20 =20 =20 =20 From: Reshad Rahman (rrahman) [mailto:rrahman@cisco.com]=20 Sent: Wednesday, July 8, 2020 11:27 AM To: Susan Hares; yang-doctors@ietf.org; i2rs@ietf.org Cc: martin.vigoureux@nokia.com; 'Benjamin Kaduk' Subject: Re: [yang-doctors] draft-ietf-i2rs-yang-l2-network-topology =20 Hi, =20 So sys-mac-address is supposed to be the MAC address of the mgmt port, = i.e. the device would respond to an ARP request for management-address = with sys-mac-address? I think use of term system might be a bit = misleading if that=E2=80=99s the case, mgmt-mac-address might be better. =20 Also, it is odd to have an IP address in an L2 grouping. =20 Disclaimer: not familiar with that draft at all, just took a look at the = L2 grouping. =20 Regards, Reshad. =20 From: yang-doctors on behalf of Susan = Hares Date: Wednesday, July 8, 2020 at 11:12 AM To: "yang-doctors@ietf.org" , "i2rs@ietf.org" = Cc: "martin.vigoureux@nokia.com" , 'Benjamin = Kaduk' Subject: [yang-doctors] draft-ietf-i2rs-yang-l2-network-topology =20 The following question was asked by Ben Kaduk during IESG review of the = following document:=20 =20 https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topology= / =20 grouping l2-node-attributes { [...] leaf sys-mac-address { type yang:mac-address; description "System MAC address."; } =20 If there are more than 1 system mac address in a switch, how would this = model handle it.=20 =20 My understanding is that most switches have 1 system mac address for = network management. Therefore, the L2 topology model supports one.=20 =20 Question for Yang Doctors:=20 =20 1) Is this the normal assumption for yang models?=20 2) If not, what is the normal assumption on system mac addresses?=20 =20 3) Am I correct that switches with more than 1 system MAC will augment = their basic yang model with the second system MAC Address.=20 =20 Thank you, Susan Hares=20 ------=_NextPart_000_0052_01D65521.8A686EF0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Reshad:

 

Juregen indicates my = questions are not for IETF but for IEEE, and that multiple system-macs = may be implemented as a list.=C2=A0 =C2=A0

 

I=E2=80=99m looking at = the IEEE=C2=A0 yang model for 802-1Qcp (2018 update to IEEE 802.1Q), but = you can get the pre-release draft at (only editorial nits are missing) = at:

 

http://www.ieee802.org/1/files/private/cp-drafts/d2/802-1Qcp-d2-2.p= df

 

The reason there are multiple IP addresses is that the = single LAN can have multiple IP addresses assigned to it.=C2=A0=C2=A0 =

In may routers/switches the single = MAC port will have multiple virtual ports. =C2=A0(cisco started this = concept in the 1990s).

 

Thanks for = the help!

 

Sue =

 

From:= = Reshad Rahman (rrahman) [mailto:rrahman@cisco.com]
Sent: = Wednesday, July 8, 2020 12:09 PM
To: Susan Hares; = yang-doctors@ietf.org; i2rs@ietf.org
Cc: = martin.vigoureux@nokia.com; 'Benjamin Kaduk'
Subject: Re: = [yang-doctors] = draft-ietf-i2rs-yang-l2-network-topology

 

Hi,

 

I was = referring to management-address leaf-list in the same grouping (see = below).

 

I = don=E2=80=99t have the expertise to answer your questions below, maybe = some YDs do.

 

Regards,

Reshad.

 

     grouping l2-node-attributes = {

       = description

         = "L2 node attributes";

       container = l2-node-attributes {

         = description

         &= nbsp; "Contains L2 node attributes.";

<snip>

         = leaf-list management-address {

         &= nbsp; type inet:ip-address;

         &= nbsp; description

         &= nbsp;   "System management = address.";

         = }

         leaf = sys-mac-address {

         &= nbsp; type yang:mac-address;

         &= nbsp; description

         &= nbsp;   "System MAC = address.";

         = }

 

 

From: Susan Hares = <shares@ndzh.com>
Date: Wednesday, July 8, 2020 at 11:48 = AM
To: "Reshad Rahman (rrahman)" = <rrahman@cisco.com>, "yang-doctors@ietf.org" = <yang-doctors@ietf.org>, "i2rs@ietf.org" = <i2rs@ietf.org>
Cc: = "martin.vigoureux@nokia.com" = <martin.vigoureux@nokia.com>, 'Benjamin Kaduk' = <kaduk@mit.edu>
Subject: RE: [yang-doctors] = draft-ietf-i2rs-yang-l2-network-topology

=

 

Reshad: =

 

Thank you for quick response.  =  However, I=E2=80=99m confused.   Where do you see the IP = address in the Yang snippet I sent?  It is a MAC Address = (type yang:mac-address)?  If the system = port allows IP, it will respond to the ARP request with the appropriate = IP/MAC match in an ARP reply.   

 

In real implementations I2rs = implementers examined,

  • L2 port with mgmt-mac-address seems to be used = to only send LLDP packets,
  • L2 port with sys-mac-address seems to be used = for management using TCP/IP. 

 

If we swap the names, it did not work with the initial = implementers of the yang model.  The  I2RS Topology models are = used for operational management of switches and routers as logical = units.

 

Also, your response does not seem = to match my questions:

 

1) Is this the = normal assumption for yang models?

2) If not, what is = the normal assumption on system mac addresses?

3) Am I correct that = switches with more than 1 system MAC will augment their basic yang model = with the second system MAC Address?

 

I=E2=80=99m sorry to = bother you but this document is being reviewed by the IESG  = tomorrow (Thursday) and

I am the shepherd. =  I do not know how to answer some of the yang related questions = regarding multiple system ports to exchange management configuration = on. 

 

I had thought that = netconf/restconf would be exchanged over the same ports so the yang = doctors would know what the normal custom should be.

 

Thanks again! =

 

Sue =  

 

 

 

 

 

 

 

 

From:= Reshad = Rahman (rrahman) [mailto:rrahman@cisco.com]
Sent: Wednesday, = July 8, 2020 11:27 AM
To: Susan Hares; yang-doctors@ietf.org; = i2rs@ietf.org
Cc: martin.vigoureux@nokia.com; 'Benjamin = Kaduk'
Subject: Re: [yang-doctors] = draft-ietf-i2rs-yang-l2-network-topology

 

Hi,

 

So sys-mac-address is supposed to be = the MAC address of the mgmt port, i.e. the device would respond to an = ARP request for management-address with sys-mac-address? I think use of = term system might be a bit misleading if that=E2=80=99s the case, = mgmt-mac-address might be better.

 

Also, it is odd to have an IP address = in an L2 grouping.

 

Disclaimer: not familiar with that = draft at all, just took a look at the L2 grouping.

 

Regards,

Reshad.

 

From: yang-doctors = <yang-doctors-bounces@ietf.org> on behalf of Susan Hares = <shares@ndzh.com>
Date: Wednesday, July 8, 2020 at 11:12 = AM
To: "yang-doctors@ietf.org" = <yang-doctors@ietf.org>, "i2rs@ietf.org" = <i2rs@ietf.org>
Cc: = "martin.vigoureux@nokia.com" = <martin.vigoureux@nokia.com>, 'Benjamin Kaduk' = <kaduk@mit.edu>
Subject: [yang-doctors] = draft-ietf-i2rs-yang-l2-network-topology

 

The following question was asked by = Ben Kaduk during IESG review of the following document: =

 

https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-netwo= rk-topology/

 

     grouping l2-node-attributes = {

         = [...]

         leaf = sys-mac-address {

          = type yang:mac-address;

          = description

          =    "System MAC address.";

         = }

 

If there are more than 1 system mac address in a = switch, how would this model handle it.

 

My understanding is that most switches have 1 system = mac address for network management.  Therefore, the L2 topology = model supports one.

 

Question for Yang Doctors:

 

1) Is this the normal assumption for yang models? =

2) If = not, what is the normal assumption on system mac addresses?

 

3) Am I correct that switches with more than 1 system = MAC will augment their basic yang model with the second system MAC = Address.

 

Thank you, Susan Hares

------=_NextPart_000_0052_01D65521.8A686EF0--