Re: [netmod] Add network instance name on interface, IPv4, IPv6

"Acee Lindem (acee)" <acee@cisco.com> Mon, 05 August 2019 16:46 UTC

Return-Path: <acee@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 155BF1202C9; Mon, 5 Aug 2019 09:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=JAKNrOz9; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=f4TwRzrG
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 0bv7mW8Yw6tf; Mon, 5 Aug 2019 09:46:49 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E8E11202B0; Mon, 5 Aug 2019 09:46:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19771; q=dns/txt; s=iport; t=1565023609; x=1566233209; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Nxb/RXu3CXqGZzB/L9+5zSx//ZJS3ky3B1L82Eib1cE=; b=JAKNrOz9YPaks9MwVWd6sYDYRgZKcvxFkiJoZim3QkBwt9cCWsqCMzye wW3osGjAMZU612i0Bmd8I9sb6T1TAYsFZVsLAYBwB+5P0M9IPDLp4PQhk h2R+CcVqYukM4UvwFYszcZNlCoS0zp7E7d5U5BhoIg+hiFBRa+DRVMkPd M=;
IronPort-PHdr: =?us-ascii?q?9a23=3A3PKc3hBzBKHWE8ejX5MMUyQJPHJ1sqjoPgMT9p?= =?us-ascii?q?ssgq5PdaLm5Zn5IUjD/qgw3kTRU9Dd7PRJw6rNvqbsVHZIwK7JsWtKMdRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXETwIfPCZC0hF8MEX1hgrDm2?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAACbXEhd/5FdJa1mGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUwQBAQEBAQsBgRUvJCwDbVUgBAsqhB6DRwOEUoZcglu?= =?us-ascii?q?JV4krhFeBLoEkA1QJAQEBDAEBLQIBAYQ/AheCWCM0CQ4BAwEBBAEBAgEGbYU?= =?us-ascii?q?eDIVKAQEBAQMSEQQZAQE3AQ8CAQgOAwMBAisCAgIfER0IAQEEAQ0FIoMAAYE?= =?us-ascii?q?dTQMdAQKhBwKBOIhgcX8zgnoBAQWFBg0LghMJgTQBi2IXgX+BOB+CHi4+ghq?= =?us-ascii?q?CSoJrMoImjwmFBCOWNEAJAoIbkCeDdxuYKY1HiVCOIAIEAgQFAg4BAQWBUDi?= =?us-ascii?q?BWHAVZQGCQYJCg3GKU3KBKY0TAQE?=
X-IronPort-AV: E=Sophos;i="5.64,350,1559520000"; d="scan'208,217";a="610154215"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Aug 2019 16:46:47 +0000
Received: from XCH-ALN-018.cisco.com (xch-aln-018.cisco.com [173.36.7.28]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x75Gkl2C004585 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 5 Aug 2019 16:46:47 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-018.cisco.com (173.36.7.28) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 5 Aug 2019 11:46:46 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 5 Aug 2019 12:46:45 -0400
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 5 Aug 2019 11:46:45 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hiUDwxWOa4XOdFFbL1TvyZQ8/kEVmH27hMPpPHHJbqgiKv7paSP4NlZyM+/4j3PhetA3L3ZuIeoyztGj6mM9N2243cYgx+YrsPlaeSnpdqXiyFj818rmpSB5HVwftc9u+CkOE5S+Qnxys2F72UWYXVCOysl5sGxDKhvw3Z0cttAXZHkjY9CntxKaGnMnugi021G6A+Gt3wEruVGQgxZh5xj9a8ilmQWcjYN64dHzWt8IJAKtyhJLJfRnD8upsfq5F32GQ2ENjpMD4UF782YKDTRBd/7GhDjcSYPNnyP3lg11eaD4aHNvNbWuFF2JJBOzw36jJFGPz+hSIG/0Fwl8kQ==
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=Nxb/RXu3CXqGZzB/L9+5zSx//ZJS3ky3B1L82Eib1cE=; b=F0U6r/oOBiXfeh1Kk7mF8uk1YWVWt0C6fKKKBP+QeiU9z8etgH/Gp2WDI/qvXQNL9u2ldz+wK9mxPptrQhPgpi0ZLmCPmin465kdS+lRcGK7UZVFR5cT+uSER0r9Vv8K3psmwovDcBrgaiDBRNpsOiyiVmePVWRni3+d5vwyi4+jbUxLNOXtVa3V0rMQIMg5VAv8znFyH7YKQLsgkHzaAkSTIU3kkVy/pVbto3zOT4sTSN6uO9gT9RrpFOxVc47YJtdBXukYex07+/tgP3Ci/DtqLzXnVotmYtYCT/5M/cmk9w5YL+RTfhDj4jpO3Vh6zdnoHWBp7566lVMfQzo6Cw==
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=Nxb/RXu3CXqGZzB/L9+5zSx//ZJS3ky3B1L82Eib1cE=; b=f4TwRzrGUWt3Qdakuk3NxXaaqG1ROspjZgawM7kPuih1FJL6WHCmwyabMLA47ejEbBmSarFM9EeaSRAR5I//Te7idZ8gJtcjyvItGoSLnFzl60a0dv0/o77YPwtqz44ZCbMjVQMbPVvXnQXGLX15/ssX9Gm/49PZOYPu0DMmo1M=
Received: from MN2PR11MB4221.namprd11.prod.outlook.com (52.135.38.14) by MN2PR11MB3856.namprd11.prod.outlook.com (20.178.251.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2136.20; Mon, 5 Aug 2019 16:46:44 +0000
Received: from MN2PR11MB4221.namprd11.prod.outlook.com ([fe80::859c:f271:3be2:74e0]) by MN2PR11MB4221.namprd11.prod.outlook.com ([fe80::859c:f271:3be2:74e0%3]) with mapi id 15.20.2136.018; Mon, 5 Aug 2019 16:46:44 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Qin Wu <bill.wu@huawei.com>, "draft-ietf-rtgwg-ni-model.all@ietf.org" <draft-ietf-rtgwg-ni-model.all@ietf.org>
CC: RTGWG <rtgwg@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>, "Wangleilei (DOPRA SSP)" <wangleilei@huawei.com>
Thread-Topic: Add network instance name on interface, IPv4, IPv6
Thread-Index: AdVLk710rBBNwCAdSAaU2eImV7sW6f//8C+A
Date: Mon, 5 Aug 2019 16:46:44 +0000
Message-ID: <3BA052DB-49A2-4E4C-B6AC-2CB72F7EFA72@cisco.com>
References: <B8F9A780D330094D99AF023C5877DABAA9283A10@dggeml511-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAA9283A10@dggeml511-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [2001:420:c0c4:1001::2f]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 87ccf311-2e99-4bed-d50b-08d719c47fac
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3856;
x-ms-traffictypediagnostic: MN2PR11MB3856:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB3856D312E0078BF0F491FE35C2DA0@MN2PR11MB3856.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 01208B1E18
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(366004)(136003)(39860400002)(346002)(396003)(189003)(199004)(46003)(6486002)(99286004)(6116002)(86362001)(66476007)(64756008)(66446008)(66556008)(54896002)(6512007)(229853002)(6246003)(2501003)(66946007)(76116006)(33656002)(110136005)(2906002)(6306002)(53936002)(4326008)(6436002)(54906003)(36756003)(76176011)(478600001)(81166006)(256004)(81156014)(25786009)(71190400001)(5660300002)(486006)(8936002)(2616005)(476003)(11346002)(8676002)(446003)(102836004)(71200400001)(9326002)(68736007)(53546011)(14454004)(186003)(316002)(7736002)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3856; H:MN2PR11MB4221.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: vYDJPQyKcLySHrFEZIgmH+n3Nf/5eEicO2050PYlUsIFaqU4iXYDEmhU82WSBZIOnX2MRTzE6r+hk02ncI63ZHE0kDQlN02Lk3gOR4Blu9XDXc1OchUAEnhyUkgx4AXdE/PF9G1BHefY9oAVLLN5OMCPJCQtlxRo58XzpRE2o6ovW0MDB7wP9iznpaPcR6AbyjwYq6EdjbRwJWntvEcLoETMnQGPNI6OWmBqfKLi0miYeCKtPB/BWrmcK9XS1Z8boDNrMULs+XE8I7gMVxVxtRrkUTl4UxIToCw3YYhWfS/Ml44lCav00rq97LHm3QrHtNtHgJxE+4IkwGc/GlBGvjUV8XqqmBImy/2faMCOh1gbwpfws11uHoYQ1h9cjCY1aH1nxAo58BuKLlWvu+eAu2HkZg4I9SbK5duOgF1QRLU=
Content-Type: multipart/alternative; boundary="_000_3BA052DB49A24E4CB6AC2CB72F7EFA72ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 87ccf311-2e99-4bed-d50b-08d719c47fac
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Aug 2019 16:46:44.0613 (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: acee@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3856
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.28, xch-aln-018.cisco.com
X-Outbound-Node: rcdn-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/jtCo8i55RaadOUqpTzH8AyXvnYw>
Subject: Re: [netmod] Add network instance name on interface, IPv4, IPv6
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2019 16:47:04 -0000

Hi Qin,

From: Qin Wu <bill.wu@huawei.com>;
Date: Monday, August 5, 2019 at 10:11 AM
To: "draft-ietf-rtgwg-ni-model.all@ietf.org"; <draft-ietf-rtgwg-ni-model.all@ietf.org>;
Cc: Routing WG <rtgwg@ietf.org>;, "netmod@ietf.org"; <netmod@ietf.org>;, "Wangleilei (DOPRA SSP)" <wangleilei@huawei.com>;
Subject: Add network instance name on interface, IPv4, IPv6
Resent-From: <alias-bounces@ietf.org>;
Resent-To: <lberger@labn.net>;, Christian Hopps <chopps@chopps.org>;, Acee Lindem <acee@cisco.com>;, Dean Bogdanovic <ivandean@gmail.com>;, <xufeng_liu@jabil.com>;, <chrisbowers.ietf@gmail.com>;, Jeff Tantsura <jefftant.ietf@gmail.com>;, Yingzhen Qu <yingzhen.ietf@gmail.com>;, Alia Atlas <akatlas@gmail.com>;, Martin Vigoureux <martin.vigoureux@nokia.com>;, Deborah Brungard <db3546@att.com>;, Alvaro Retana <aretana.ietf@gmail.com>;, Yingzhen Qu <yingzhen.ietf@gmail.com>;
Resent-Date: Monday, August 5, 2019 at 10:11 AM

Hi, authors:

In RFC8529, the bind-network-instance-name leaf provides the association between an interface and its associated NI.

However it is not clear to me why the same association between Ipv4/Ipv6 type and its association NI

Should be provided as well? See model structure snippet defined in RFC8529 as follows:
“
   augment /if:interfaces/if:interface:
     +--rw bind-ni-name?   -> /network-instances/network-instance/name
   augment /if:interfaces/if:interface/ip:ipv4:
     +--rw bind-ni-name?   -> /network-instances/network-instance/name
   augment /if:interfaces/if:interface/ip:ipv6:
     +--rw bind-ni-name?   -> /network-instances/network-instance/name
“

So the question is

Can we add different NI name for IPv4/IPv6 type? Isn’t IPv4 type and IPv6 type and interface pointing to the same NI name?

Why IPv4 type and IPv6 type in IP data model can not inherit the same NI name from the interface model since IP Data model is an extension to Interface Data Model?



The model allows the IPv4/IPv6 level of granularity for network-instance specification. However, many, if not most, implementations do not. My memory is hazy as to which implementation(s) supports this.

Thanks,
Acee








Suppose we configure interface and associated IP addresses and assign this interface to a NI,
Which configuration snippet is correct:
Option A:
{
"name": "eth1",
"type": "iana-if-type:ethernetCsmacd",
"ietf-ip:ipv4": {
"address": [
{
"ip": "192.0.2.11",
"prefix-length": 24
}
]
"ietf-network-instance:bind-network-instance-name": "vrf-red"
},
"ietf-ip:ipv6": {
"address": [
{
"ip": "2001:db8:0:2::11",
"prefix-length": 64
}
]
"ietf-network-instance:bind-network-instance-name": "vrf-red"
},
"ietf-network-instance:bind-network-instance-name": "vrf-red"
},
Option B:
{
"name": "eth1",
"type": "iana-if-type:ethernetCsmacd",
"ietf-ip:ipv4": {
"address": [
{
"ip": "192.0.2.11",
"prefix-length": 24
}
]
},
"ietf-ip:ipv6": {
"address": [
{
"ip": "2001:db8:0:2::11",
"prefix-length": 64
}
]
},
"ietf-network-instance:bind-network-instance-name": "vrf-red"
},

-Qin