Re: [Softwires] [Int-area] AD sponsoring draft-thaler-iftype-reg-02

Dave Thaler <dthaler@microsoft.com> Mon, 08 July 2019 23:20 UTC

Return-Path: <dthaler@microsoft.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1417112037D; Mon, 8 Jul 2019 16:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 lpphrVOj2La4; Mon, 8 Jul 2019 16:20:32 -0700 (PDT)
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-eopbgr720108.outbound.protection.outlook.com [40.107.72.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44639120364; Mon, 8 Jul 2019 16:20:32 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=S/nQ5dKmaDkECn1orNWMDJfrqE1RCIpFjB8XVprMs2kFF2WiAE1BmUxumhG6wxD8lkonECmwvqmwWB6i+q4mlUmzvTl2r+kIVHZJJ8EwcvxmHW7wltKr9M2aqN2xuNNPYTDqNAA4SZTkgUyObavlGnWneWkEVxRaawOb7yoLk331/IoBSR6sFolq3SRhFngWO5GeShWXdirwY5uplW5POC488OSR3lNsu9pdBRuOtOnAnBzOEzy8TzxUQmtWoPLgPtLA8+YdPFyzDmd99RBy8uvsQoEjEayngYO99pgbSClu+/3JEyAPqNK0LK6bj23IqlfeZXRILmz+Qz314+TO4w==
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=i2NdUXxZw2XWVuprZS6ALt6drrTg38h+r0BT6++aS8A=; b=a1b8Ow4NXxSMSNWm7KWrj6FBRXJ99+j1lQoo6jJietr961vmTAssoCs4YjX0UKXXZ0Vhny1znWxt5DUxUBl57WgKHyengGxSL5i0DPAq9fc3duzZ+zeDZHi0+BoTVfC76soBZ1Z64Gso2hUGqyHGzYhLFNm9nViP9kEDOYfW7RTvEAg35SA6vNW2Gtkw3LG2OKJ+PwfjA9/NFS6ceEFOagHziu/E/ji0OzkiT4BTVOz29j1AtRq+RJ3nblTvq5iAVJwFYOthwcooXUIfXx5zwAk908YASw7X94UluBKr0prCSYNU557ebPOPxeE/VP+d52OqI2wrYONu2DI2vatKXA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=microsoft.com;dmarc=pass action=none header.from=microsoft.com;dkim=pass header.d=microsoft.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=i2NdUXxZw2XWVuprZS6ALt6drrTg38h+r0BT6++aS8A=; b=G2EYyPWDL6ZEGLSKSPNq6mLf/zVT658NvWxzu9RNlO+FQD//irCg+/eABEdX9OSWIZSWsDEtyaFX7sMw+vBAjPd4croF3RvBs3fH85wAKKaw4nK75y1mr+agrrtFeTjKvfIEvx9PpcRJCFr/DF9zEDVLjGA3V5PZN/eZB6vDk9k=
Received: from MWHPR21MB0784.namprd21.prod.outlook.com (10.173.51.150) by MWHPR21MB0144.namprd21.prod.outlook.com (10.173.52.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2073.2; Mon, 8 Jul 2019 23:20:30 +0000
Received: from MWHPR21MB0784.namprd21.prod.outlook.com ([fe80::69c0:8cb:908c:f221]) by MWHPR21MB0784.namprd21.prod.outlook.com ([fe80::69c0:8cb:908c:f221%8]) with mapi id 15.20.2094.001; Mon, 8 Jul 2019 23:20:30 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org>, Suresh Krishnan <Suresh@kaloom.com>, int-area <int-area@ietf.org>, 6man <ipv6@ietf.org>, dhcwg <dhcwg@ietf.org>, V6 Ops List <v6ops@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: [Int-area] AD sponsoring draft-thaler-iftype-reg-02
Thread-Index: AQHVIUvM9WEXtmDvEkCRovcCdcQgcKa8iIaAgAT7kjA=
Date: Mon, 8 Jul 2019 23:20:30 +0000
Message-ID: <MWHPR21MB0784475D021E1337D2600232A3F60@MWHPR21MB0784.namprd21.prod.outlook.com>
References: <75825363-B4BA-4F94-A935-B87F474F06C9@kaloom.com> <019801d522ce$34bff3a0$4001a8c0@gateway.2wire.net> <BN6PR21MB0497AE6B319A4879D041AA81A3F50@BN6PR21MB0497.namprd21.prod.outlook.com>
In-Reply-To: <BN6PR21MB0497AE6B319A4879D041AA81A3F50@BN6PR21MB0497.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=dthaler@ntdev.microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2019-07-05T19:17:02.2121879Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=a3b4b581-53d2-45cd-a339-063f355f76bd; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dthaler@microsoft.com;
x-originating-ip: [2001:4898:80e8:8:10d2:dc8f:6397:1757]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7bcb5bd5-81e4-4863-2f26-08d703fade84
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:MWHPR21MB0144;
x-ms-traffictypediagnostic: MWHPR21MB0144:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <MWHPR21MB01441A9DDA1585FBFE06E9B0A3F60@MWHPR21MB0144.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 00922518D8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(376002)(396003)(346002)(366004)(39860400002)(199004)(189003)(53754006)(13464003)(45074003)(54094003)(51444003)(43544003)(99286004)(22452003)(186003)(110136005)(316002)(446003)(6506007)(7696005)(11346002)(8990500004)(2906002)(256004)(476003)(53936002)(71190400001)(102836004)(53546011)(486006)(6246003)(236005)(68736007)(54896002)(9686003)(33656002)(74316002)(55016002)(6306002)(966005)(478600001)(81166006)(73956011)(8936002)(81156014)(8676002)(7736002)(10290500003)(76176011)(64756008)(46003)(66556008)(2501003)(66946007)(229853002)(66446008)(6436002)(76116006)(10090500001)(66476007)(25786009)(5660300002)(606006)(52536014)(790700001)(6116002)(2201001)(86362001)(71200400001)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR21MB0144; H:MWHPR21MB0784.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: EaoibYoKgI7IWv9vKCJlFsz8LjbxP3DtPz/KoyG6c2mS5IxrPAS2o+qZns6nor3q8dXgVpUfIJM2iXdV4Z5pXPob7MkVePxTOEMQqOtceEjou4jMcJOJi2psKNgzP0Nb5rH+ygKtETPEgxOUx2J6IIGc/FqOal5afVGx9ewXXRgKISFIyN8upMEO3HE1ELV6w/SSZ2BFp9aPrFShz8Q5tg6Lw5UvFQ1DStmY6QSrVs4QOZJ762mpWU2aYFuXlsYA1JECJe9dG+qyMxXuqY/LT4NQNKLlTiix+pl4FG7UDEbfagDJG7WJvr4s3n42cIydyY0OvnGQSafQmnyYk5iuMbjehAPV6adKTAguMKlb/1qUuXNa2FzMK9kcBaM19GPl+dzJ7VzxrBSAW0ghzR2LDfYf5ulAZTMvXymmE102S0s=
Content-Type: multipart/alternative; boundary="_000_MWHPR21MB0784475D021E1337D2600232A3F60MWHPR21MB0784namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7bcb5bd5-81e4-4863-2f26-08d703fade84
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jul 2019 23:20:30.4957 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: dthaler@ntdev.microsoft.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0144
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/GZMWXJ9HeP6s0fhIdlje3WJ5vtQ>
Subject: Re: [Softwires] [Int-area] AD sponsoring draft-thaler-iftype-reg-02
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jul 2019 23:20:50 -0000

FYI, draft-thaler-iftype-reg-04 is now posted and incorporates changes based on
feedback from Med, Tom, Suresh, and others.

Diffs from -02 can be seen at
https://tools.ietf.org/rfcdiff?url1=draft-thaler-iftype-reg-02.txt&url2=draft-thaler-iftype-reg-04.txt

Dave

From: Softwires <softwires-bounces@ietf.org> On Behalf Of Dave Thaler
Sent: Friday, July 5, 2019 12:17 PM
To: tom petch <ietfc@btconnect.com>om>; Suresh Krishnan <Suresh@kaloom.com>om>; int-area <int-area@ietf.org>rg>; 6man <ipv6@ietf.org>rg>; dhcwg <dhcwg@ietf.org>rg>; V6 Ops List <v6ops@ietf.org>rg>; opsawg@ietf.org; softwires@ietf.org
Subject: Re: [Softwires] [Int-area] AD sponsoring draft-thaler-iftype-reg-02




-----Original Message-----
From: dhcwg <dhcwg-bounces@ietf.org<mailto:dhcwg-bounces@ietf.org>> On Behalf Of tom petch
Sent: Friday, June 14, 2019 9:28 AM
To: Suresh Krishnan <Suresh@kaloom.com<mailto:Suresh@kaloom.com>>; int-area <int-area@ietf.org<mailto:int-area@ietf.org>>; 6man <ipv6@ietf.org<mailto:ipv6@ietf.org>>; dhcwg <dhcwg@ietf.org<mailto:dhcwg@ietf.org>>; V6 Ops List <v6ops@ietf.org<mailto:v6ops@ietf.org>>; opsawg@ietf.org<mailto:opsawg@ietf.org>; softwires@ietf.org<mailto:softwires@ietf.org>
Subject: Re: [dhcwg] [Int-area] AD sponsoring draft-thaler-iftype-reg-02



Suresh



The concern I have is that it muddies the waters further on the standing of tunnels so while I think that its proposals for ifType per se are fine, I would like it to make explicit that tunnels are out-of-scope at this time.



Tunnels are certainly not out-of-scope.  There's two existing registries (interface types and tunnel types), and this draft documents existing registration process, and some process clarifications to address points of process confusion and ease process friction today.





I have been trying to reconcile the workings of softwire, in creating a tunnel YANG module, with the existing IANA structure and failing.  I believe that is because the current status of tunnels is unclear.  Thus the softwire I-D refers to a registry that does not exist



Yes it does.   The software I-D does not create any new registry.   It only creates another format for retrieving the contents of an existing registry.  Many registries are retrievable in multiple formats (XML, excel, txt, etc.).   This registry is no different.



What I can do is add a paragraph explaining the use of multiple formats for the interface type and tunnel type registries, to make it clear that each format is not a separate registry, just like getting the TCP port registry in XML vs excel is not two different registries.



Dave



(as such) although the URL that the softwire I-D does. I think the timing unfortunate in that IMHO the softwires I-D will get pressed ahead before this work can complete, so quite what this I-D then says about tunnels will be coloured by what then exists for tunnels.



So this I-D should make clear what a tunnel is, when it is not an interface, but otherwise declaring tunnels out-of-scope, for a future I-D to do a comparable job for tunnels, setting up a tunnel registry from which MIB modules, YANG modules and anything else can be derived (as long as the relevant data is supplied - SMI needs integers, YANG does not, which I-Ds do not always recognise although the Designated Experts can take care of that).



Finally, when I first encountered this I-D I asked on NETCONF and NETMOD WG lists if anyone knew of it, where it was being worked on and got no reply - which surprised me.  I note that you have not copied them although they were involved in making the interface type registry what it currently is when creating the YANG module for interface types.  I wonder if other WG have an interest, CCAMP or TEAS perhaps.  I agree that int-area is the WG best equipped to work on it and that it needs working on.



Tom Petch



----- Original Message -----

From: "Suresh Krishnan" <Suresh@kaloom.com<mailto:Suresh@kaloom.com>>

To: "int-area" <int-area@ietf.org<mailto:int-area@ietf.org>>; "6man" <ipv6@ietf.org<mailto:ipv6@ietf.org>>; "dhcwg"

<dhcwg@ietf.org<mailto:dhcwg@ietf.org>>; "V6 Ops List" <v6ops@ietf.org<mailto:v6ops@ietf.org>>; <opsawg@ietf.org<mailto:opsawg@ietf.org>>; <softwires@ietf.org<mailto:softwires@ietf.org>>

Sent: Wednesday, June 12, 2019 7:22 PM



Hi all,

  I would like to AD sponsor the following draft that provides guidelines for definition of new interface types in the IANA IfType registries



https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-thaler-iftype-reg-02&amp;data=02%7C01%7Cdthaler%40microsoft.com%7Cbd9080f665064f564d3608d6f0e55a88%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961265202763707&amp;sdata=HM5asXOFnSuzPaCR4k4kopqsIHLLdnqZ7PDuu8hPJM4%3D&amp;reserved=0<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-thaler-iftype-reg-02&data=02%7C01%7Cdthaler%40microsoft.com%7C7f0bb0e13ad444ffbfe208d7017dd4cd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636979512288910008&sdata=Oiu3BLoPvkbcNQN4XA5ih7YnnWeb9bzn7WLP4nJ%2FSCM%3D&reserved=0>



If you have any concerns either with the contents of the draft, or about me AD sponsoring it please let me know before 2019/06/26.



Thanks

Suresh



NOTE: I have CCed: all the working groups that I thought could be potentially interested in this work. If you think I have missed out some WG(s) please let me know.







------------------------------------------------------------------------

--------





> _______________________________________________

> Int-area mailing list

> Int-area@ietf.org<mailto:Int-area@ietf.org>

> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww<https://www>ww>.

> ietf.org%2Fmailman%2Flistinfo%2Fint-area&amp;data=02%7C01%7Cdthaler%40

> microsoft.com%7Cbd9080f665064f564d3608d6f0e55a88%7C72f988bf86f141af91a

> b2d7cd011db47%7C1%7C0%7C636961265202763707&amp;sdata=znz7EZ1q%2FwIQUJC

> gYZTWfY2H4C7tN6qFhJubCVWxWzc%3D&amp;reserved=0

>



_______________________________________________

dhcwg mailing list

dhcwg@ietf.org<mailto:dhcwg@ietf.org>

https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fdhcwg&amp;data=02%7C01%7Cdthaler%40microsoft.com%7Cbd9080f665064f564d3608d6f0e55a88%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961265202763707&amp;sdata=OJvbRDz%2FCIlVF3hWR30KCs0cRgi9KmtnYLHKbHSeJzc%3D&amp;reserved=0<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fdhcwg&data=02%7C01%7Cdthaler%40microsoft.com%7C7f0bb0e13ad444ffbfe208d7017dd4cd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636979512288919998&sdata=%2FIXOjXLKQ9Ciq2dQNd5zF69bVqpvHogJO6B9GfrlNtg%3D&reserved=0>