Re: [i2rs] [yang-doctors] draft-ietf-i2rs-yang-l2-network-topology

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Thu, 09 July 2020 02:52 UTC

Return-Path: <rrahman@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 21CC43A0D1B; Wed, 8 Jul 2020 19:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 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, HTML_MESSAGE=0.001, 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=MO6kp0fU; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=nNY618UI
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 dnSi-5kWh65n; Wed, 8 Jul 2020 19:52:27 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CFA03A0D17; Wed, 8 Jul 2020 19:52:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=54617; q=dns/txt; s=iport; t=1594263147; x=1595472747; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=RW2wM1xilGTRBluE7rdHLHVND7KqXFz9U+aNaRZkFAE=; b=MO6kp0fU/VKctsxP+h8lbguObURkCvdff7y3+xtCk92QwkyNCyJ4RQDK SkmKe78PBxsGPFDahvWha9Nuj1fpONSqJvCyV5rjJ/r8pweA4W7D44YKd 8GBnHvS/TbRuq8gQoHbSDp+m/Pw4pnmOwI98nJAsmTkvedTzcagWCpSD1 8=;
X-IronPort-AV: E=Sophos;i="5.75,330,1589241600"; d="scan'208,217";a="781115430"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 Jul 2020 02:52:01 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 0692q1v0027387 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 9 Jul 2020 02:52:01 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 8 Jul 2020 21:52:00 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 8 Jul 2020 22:51:59 -0400
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 8 Jul 2020 21:51:59 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OOxdDxnzBw5r8fECoYTQDawus7FCi0AHqgGQpKIvEkm4Vt52MmtNOVtKrGSIhtS4B+4A7CLAC8FaRluKF8t2I9apT0WZJC+4h2pl4VoAeBc6b5/5famSlt3AYthvu0f26+YSKMgWZUmjBJsOhA/6VUUObAxXD4V27IU+MCpByNtED/5swMkmfVH3zU5/MVy2jliFoP2rDSSggck+owH5+Ux2NUXT7TbZA3yA/qKsPrKFOO/rEiWhe03VA1P/VUoGtvga+1oGfGO+Egrssy57IynRgRVKIPQyh0vyIpNQfkuIcEygwCE511x2DtWYXeAs51cfHsTun5izzvoqZC+aQQ==
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=RW2wM1xilGTRBluE7rdHLHVND7KqXFz9U+aNaRZkFAE=; b=SHvR2DZkqnsKfVvOpzHe6H0oi9BJUg7cJxlNd+bDVjpxVThesy69E3X78Lo+iBnyDzJHtUjNqMzyU2QO63P751/p8eGE4D87tO1pf7TRJdAou73lDelSKlYdqwHrFTsybEbv8r4nDG9js0CIGYhzDuBNeJQGe5bh1Bpg8JkLdHL+ZxEzyTzJXbYV6oEm5VShZmOAvb7wtwzmw+eSZeZ65GHGTsVBvf259LbvtrExk8B7eq8fP1feGcbUhO8uqvP2WusYrRd1HNz6hlLhiKJF8bxbJn15uXIZBT0xxB7JR/qo0jmIdOw7teL3PAD02Vu4Sr7Fk4iO96vY/M9yslSjfA==
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=RW2wM1xilGTRBluE7rdHLHVND7KqXFz9U+aNaRZkFAE=; b=nNY618UI5HFmEoxB71uSZujYDgCEuDBWUAFPHixZM+3wxGA3yECgDcpadwN+awhn7/SJKqauWUOI8D6zGyoSKV0iL0e+dM6RsdR4Jr/F5H7ts/dNIV/AGm4ZbPn6TqGXkfpLKu24NdqaLXzlSaG5HnsoEPUbJ05y0yxPIpDEAy4=
Received: from BN6PR11MB3875.namprd11.prod.outlook.com (2603:10b6:405:80::37) by BN6PR11MB1234.namprd11.prod.outlook.com (2603:10b6:404:47::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.27; Thu, 9 Jul 2020 02:51:58 +0000
Received: from BN6PR11MB3875.namprd11.prod.outlook.com ([fe80::3076:a505:335e:a8ff]) by BN6PR11MB3875.namprd11.prod.outlook.com ([fe80::3076:a505:335e:a8ff%6]) with mapi id 15.20.3174.021; Thu, 9 Jul 2020 02:51:58 +0000
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Qin Wu <bill.wu@huawei.com>, Susan Hares <shares@ndzh.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>
Thread-Topic: [yang-doctors] draft-ietf-i2rs-yang-l2-network-topology
Thread-Index: AdZVmRKBXKEIf8PiTXi2b7rIs690E///wpyA
Date: Thu, 9 Jul 2020 02:51:58 +0000
Message-ID: <315210A4-5C22-4C86-ACCE-0E86BA609EBC@cisco.com>
References: <B8F9A780D330094D99AF023C5877DABAAD819120@dggeml531-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAAD819120@dggeml531-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.37.20051002
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [142.113.229.50]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 058bf224-59b0-49a1-33f7-08d823b30c1f
x-ms-traffictypediagnostic: BN6PR11MB1234:
x-microsoft-antispam-prvs: <BN6PR11MB123463414EEC499F05D5A2AAAB640@BN6PR11MB1234.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 04599F3534
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: WZJHdAF7D/wDM+r6UHCMNjlHdSHCOMyBH9STxqV1Lb/7wdtYml3ubajZAY2znKoCZq+f01PK+sPkMI70S4tiPwds/v0hJd2Wl+2r1AWrnSm0dYOHNC+a3cD6TEpO0b5n1h3qkYxuN629Rphze8hbmhMbfQJ5OsCa7zUAq1Bsrqw8qhUK7hK9Q7UHHV/gHsGJNzLUpkMRo5ZmVtRm1xuNnXaDQcmFMTS2/8HF+RfGVm55bWgcfyXzt97dbrHaj3ZNus+ehkamfop+bW+Gdp1fMMQLXGt9BFBMi1HUUp48fQtugOuhX2yHil11PbfFL4H/+Zo+exJ6Tjjnv6a8zPuRAwyuWJ1cbkP3xp+o3shq00/4zjzelDMPwpjVokeH27KmXU3z+bM/LvE/76aweOdNAg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN6PR11MB3875.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(366004)(396003)(376002)(346002)(136003)(39860400002)(2906002)(6512007)(36756003)(54906003)(316002)(86362001)(4326008)(110136005)(966005)(478600001)(6486002)(5660300002)(9326002)(6506007)(76116006)(91956017)(2616005)(53546011)(66476007)(166002)(71200400001)(66946007)(26005)(66556008)(186003)(66446008)(64756008)(8936002)(83380400001)(8676002)(33656002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: GuRaFIHoQvoSmXer5BdfEF3melpktJEOSYrUVBoe0v20vDdIjeb9b6D9EszKtIe0wW05JYxOZKgrKEjs7IGopU3nmCHaG6tRVXLei6MkUA0mgU565TFie/5szBS3SyHaXlXIs3MnU1IMthAAMBgQGSju7chpD1hIh8Qu+rw9oil+dg/V9ngkR6uJUAlVAjXy5cmfAsFUP33EDk9dXlVrwXgmg6u8MNuTQGl7Dh0Sr313qXAlpRha8vUbhGUfYRbgDW7qqmsmbqkFhazPTYneOMzY/CRTJKe3vNhmOr3n1DUCoYcchJhPkcaNYlgA1yOvwCvfVZvpXmR7etf5Oa4BFgbRjsr7kw96WoKOUTI46NfuwBw7MxweP/yBfWzNc9d8EuzFzY/+mggtwnQs5/pFzqRFTGq19JuOAYZ4e9t8Mx0WsB98dSlV3rWsxg7ChUn3cGd/M4FzJmcSElf+Iy1s+dBP0Dbsc/XZ4sqh+mhGAO893JrHdGLA3ZsSzskB9kmi
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_315210A45C224C86ACCE0E86BA609EBCciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN6PR11MB3875.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 058bf224-59b0-49a1-33f7-08d823b30c1f
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jul 2020 02:51:58.1225 (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: L5o8VovQ+b02mCO4PFUpGkGl1UwbAZkAbepAONKvjAQajKPhMjcd18QOdhPj+b89gZIazf/F6XKWzuAPa798EA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1234
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/F0uiFUvNTuTmWRq_ANpPq3SrLkE>
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\)" <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: Thu, 09 Jul 2020 02:52:30 -0000

Hi Qin,

I don’t think this needs feature since it’s pretty common. It’s just IP address (L3) in l2-attributes grouping that I found odd, maybe that grouping should have different name (i.e. not L2 specific). But since I haven’t been involved with this document at all, I probably shouldn’t be making suggestions.

Regards,
Reshad.

From: Qin Wu <bill.wu@huawei.com>
Date: Wednesday, July 8, 2020 at 10:39 PM
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>om>, Susan Hares <shares@ndzh.com>om>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>rg>, "i2rs@ietf.org" <i2rs@ietf.org>
Cc: "martin.vigoureux@nokia.com" <martin.vigoureux@nokia.com>om>, 'Benjamin Kaduk' <kaduk@mit.edu>
Subject: RE: [yang-doctors] draft-ietf-i2rs-yang-l2-network-topology

Reshad:
The management IP address is used by the administrator to get access to L2 device. It is just listed as a node attribute. We could add feature to make it optional if you think needed.

-Qin
发件人: i2rs [mailto:i2rs-bounces@ietf.org] 代表 Reshad Rahman (rrahman)
发送时间: 2020年7月9日 0:20
收件人: Susan Hares <shares@ndzh.com>om>; yang-doctors@ietf.org; i2rs@ietf.org
抄送: martin.vigoureux@nokia.com; 'Benjamin Kaduk' <kaduk@mit.edu>
主题: Re: [i2rs] [yang-doctors] draft-ietf-i2rs-yang-l2-network-topology

Thanks Sue. I wasn’t questioning the need for multiple IP addresses, I just found it odd to have IP address(es) in an L2 grouping.

Regards,
Reshad.

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

Reshad:

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

I’m 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:

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

The reason there are multiple IP addresses is that the single LAN can have multiple IP addresses assigned to it.
In may routers/switches the single MAC port will have multiple virtual ports.  (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<mailto:yang-doctors@ietf.org>; i2rs@ietf.org<mailto:i2rs@ietf.org>
Cc: martin.vigoureux@nokia.com<mailto: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’t 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
           "Contains L2 node attributes.";
<snip>
         leaf-list management-address {
           type inet:ip-address;
           description
             "System management address.";
         }
         leaf sys-mac-address {
           type yang:mac-address;
           description
             "System MAC address.";
         }


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

Reshad:

Thank you for quick response.   However, I’m 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’m 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<mailto:yang-doctors@ietf.org>; i2rs@ietf.org<mailto:i2rs@ietf.org>
Cc: martin.vigoureux@nokia.com<mailto: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’s 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<mailto:yang-doctors-bounces@ietf.org>> on behalf of Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Wednesday, July 8, 2020 at 11:12 AM
To: "yang-doctors@ietf.org<mailto:yang-doctors@ietf.org>" <yang-doctors@ietf.org<mailto:yang-doctors@ietf.org>>, "i2rs@ietf.org<mailto:i2rs@ietf.org>" <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Cc: "martin.vigoureux@nokia.com<mailto:martin.vigoureux@nokia.com>" <martin.vigoureux@nokia.com<mailto:martin.vigoureux@nokia.com>>, 'Benjamin Kaduk' <kaduk@mit.edu<mailto: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-network-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