Re: [OPSAWG] WG consensus call for the IANA early assignment //RE: Adoption poll for draft-lear-ietf-netmod-mud-04
Eliot Lear <lear@cisco.com> Mon, 29 August 2016 12:37 UTC
Return-Path: <lear@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5D8412D529; Mon, 29 Aug 2016 05:37:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.07
X-Spam-Level:
X-Spam-Status: No, score=-15.07 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-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
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 hr95f-0CGHTn; Mon, 29 Aug 2016 05:37:01 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3005012D14F; Mon, 29 Aug 2016 05:36:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8815; q=dns/txt; s=iport; t=1472474220; x=1473683820; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=yr1FoiTUJkyrdbV/sNP/sGQT7nVydFDkotAOyM7QBVY=; b=K+T96hcHTmkSJUM9O63C3DREb/y5LSi5X5tkl8ltPtvjcXFAe5Bv0id7 AAtgO+pClbwDn3bjl2oLw5L0sJuEFIkzkWBENDAWawo/g5uNAlBs03XV9 Y41DD2zRT1T/V5NHxcK6i6C+EhuGzTG/UpoQNtJQl7EgAAfwL/nHPW2dU Q=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AAAQCNK8RX/xbLJq1WBhkBAQEBAQEBAQEBAYMpAQEBAQF1KlKNLqp3ggEZC4UvSgKBexQBAgEBAQEBAQFeJ4RhAQEBAwEBAQEaBkgDCwULCxEDAQEBASMEAwICJx8JCAYBCQMGAgEBiDQIDq4Jjy4BAQEBAQEBAQEBAQEBAQEBAQEBAQEOCQWIJoFSgQOEEhEBDi6CYoJaBYgtBoVxiyuDPoFziXqJW4V6jESDeR42gmeBNzo0hC2CHwEBAQ
X-IronPort-AV: E=Sophos;i="5.28,596,1464652800"; d="asc'?scan'208";a="644318038"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Aug 2016 12:36:57 +0000
Received: from [10.61.196.191] ([10.61.196.191]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u7TCavWQ031667; Mon, 29 Aug 2016 12:36:57 GMT
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, Kent Watsen <kwatsen@juniper.net>, Zhoutianran <zhoutianran@huawei.com>, Warren Kumari <warren@kumari.net>
References: <3FCB4CBE-6885-4708-AD21-4D4B2D1AA7EE@juniper.net> <b29fd26d-70d0-7690-f5b0-55a6c8742ce3@cisco.com> <e52ab82c-9e33-78a2-2e13-840be6e9409c@bwijnen.net>
From: Eliot Lear <lear@cisco.com>
Message-ID: <ec1c6f59-c22d-25ba-90fc-0c860a3e3b22@cisco.com>
Date: Mon, 29 Aug 2016 14:36:56 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <e52ab82c-9e33-78a2-2e13-840be6e9409c@bwijnen.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="fXbqQCMkhmfLodasbf6nC4N0svRaFIhhD"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/donU_Twsn7aGNp5XRenAp2J_VC4>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, "opsawg-chairs@ietf.org" <opsawg-chairs@ietf.org>
Subject: Re: [OPSAWG] WG consensus call for the IANA early assignment //RE: Adoption poll for draft-lear-ietf-netmod-mud-04
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2016 12:37:03 -0000
Hi Bert, On 8/29/16 1:58 PM, Bert Wijnen (IETF) wrote: > So, do you want early assignments for all the registries that > are listed under your IANA considerations? > > There are quite a few as far as I can tell. > All but one of them are simply a way to emit the URL. Unless we really think the URL is going to change, and there isn't that much there to change, there's not much risk. I don't think it's a big deal to wait on the media type, and I could envision some changes to the model. In fact I have one proposal I'm pondering. Eliot > Bert > > On 25/08/16 20:36, Eliot Lear wrote: >> Hi Kent, >> >> We're doing some open source and would like to make it easier for >> those who are coding to have to do a little less REcoding. I >> doubt very much we're going to see much change in the content or >> format the URL or the option. That's what most of the requests are >> for. Where I expect we will see change is in the content of the YANG >> file. There we have the option to bump the version # in the >> URL if we think there has been any real uptake of earlier versions. >> >> Fair enough? >> >> Eliot >> >> >> On 8/25/16 7:27 PM, Kent Watsen wrote: >>> >>> >>> >>> Why is an early assignment being requested? I think it unusual, >>> especially for a draft that was just adopted, and no >>> justification is given for why it’s needed other than “to assist >>> with interoperable development”... >>> >>> >>> >>> Kent >>> >>> >>> >>> *From: *OPSAWG <opsawg-bounces@ietf.org> on behalf of Zhoutianran >>> <zhoutianran@huawei.com> >>> *Date: *Tuesday, August 23, 2016 at 5:46 AM >>> *To: *Eliot Lear <lear@cisco.com>, Warren Kumari <warren@kumari.net> >>> *Cc: *"opsawg@ietf.org" <opsawg@ietf.org>, "opsawg-chairs@ietf.org" >>> <opsawg-chairs@ietf.org> >>> *Subject: *[OPSAWG] WG consensus call for the IANA early assignment >>> //RE: Adoption poll for draft-lear-ietf-netmod-mud-04 >>> >>> >>> >>> Hi All, >>> >>> >>> >>> Since the authors of the draft-ietf-opsawg-mud-00 asked for the >>> early assignment for various registries from IANA, I would like to >>> ask the WG consensus. >>> >>> >>> >>> There will be 1 week since today. You can express your support or >>> objection. >>> >>> >>> >>> If there is no objection, I would like to request from the WG. >>> >>> >>> >>> The following is a list of IANA considerations copied from the draft. >>> >>> >>> >>> >>> >>> Best, >>> >>> Tianran >>> >>> >>> >>> ------------------------------------- >>> >>> >>> >>> 15. IANA Considerations >>> >>> >>> >>> 15.1. DHCPv4 and DHCPv6 Options >>> >>> >>> >>> IANA is requested to allocated the DHCPv4 and v6 options as >>> specified >>> >>> in Section 9. >>> >>> >>> >>> 15.2. PKIX Extensions >>> >>> >>> >>> The IANA is requested to assign a value for id-pe-mud-uri in the >>> "SMI >>> >>> Security for PKIX Certificate Extension" Registry. Its use is >>> >>> specified in Section 10. >>> >>> >>> >>> 15.3. Well Known URI Suffix >>> >>> >>> >>> The IANA is requested to register the URL suffix of "mud" as >>> follows: >>> >>> >>> >>> o URI Suffix: "mud" o Specification documents: this document o >>> >>> Related information: n/a >>> >>> >>> >>> 15.4. MIME Media-type Registration for MUD files >>> >>> >>> >>> The following media-type is defined for transfer of MUD file: >>> >>> >>> >>> o Type name: application >>> >>> o Subtype name: mud+json >>> >>> o Required parameters: n/a >>> >>> o Optional parameters: n/a >>> >>> o Encoding considerations: 8bit; application/mud+json values >>> >>> are represented as a JSON object; UTF-8 encoding SHOULD be >>> >>> employed. >>> >>> o Security considerations: See {{secon}} of this document. >>> >>> o Interoperability considerations: n/a >>> >>> o Published specification: this document >>> >>> o Applications that use this media type: MUD controllers as >>> >>> specified by this document. >>> >>> o Fragment identifier considerations: n/a >>> >>> o Additional information: >>> >>> >>> >>> Magic number(s): n/a >>> >>> File extension(s): n/a >>> >>> Macintosh file type code(s): n/a >>> >>> >>> >>> o Person & email address to contact for further information: >>> >>> Eliot Lear <lear@cisco.com>, Ralph Droms <rdroms@cisco.com> >>> >>> o Intended usage: COMMON >>> >>> o Restrictions on usage: none >>> >>> >>> >>> o Author: Eliot Lear <lear@cisco.com>, Ralph Droms >>> <rdroms@cisco.com> >>> >>> o Change controller: IESG >>> >>> o Provisional registration? (standards tree only): No. >>> >>> >>> >>> >>> >>> 15.5. LLDP IANA TLV Subtype Registry >>> >>> >>> >>> IANA is requested to create a new registry for IANA Link Layer >>> >>> Discovery Protocol (LLDP) TLV subtype values. The recommended >>> policy >>> >>> for this registry is Expert Review. The maximum number of >>> entries in >>> >>> the registry is 256. >>> >>> >>> >>> IANA is required to populate the initial registry with the value: >>> >>> >>> >>> LLDP subtype value = 1 >>> >>> >>> >>> Description = the Manufacturer Usage Description (MUD) Uniform >>> >>> Resource Locator (URL) >>> >>> >>> >>> Reference = < this document > >>> >>> >>> >>> >>> >>> >>> >>> *From:*Eliot Lear [mailto:lear@cisco.com] >>> *Sent:* Monday, August 22, 2016 7:04 PM >>> *To:* Warren Kumari >>> *Cc:* Zhoutianran; opsawg@ietf.org; opsawg-chairs@ietf.org >>> *Subject:* Re: Adoption poll for draft-lear-ietf-netmod-mud-04 >>> >>> >>> >>> Hi Warren, Tianran, and all, >>> >>> >>> >>> On 8/17/16 4:17 PM, Warren Kumari wrote: >>> >>> >>> >>> >>> Second, and hopefully not that more of a controversy, I >>> would like to >>> request early IANA assignments to assist with interoperable >>> development. These would be listed in the IANA >>> considerations section >>> of the current draft. If we need a WG draft to make this >>> happen, that's >>> fine with me, but we should do a quick rev after the >>> assignments. >>> >>> >>> >>> I believe that this *can* be accomplished without it being a WG >>> doc, but it is better / cleaner / easier if we make it a WG >>> doc and then ask for early assistant. We are fine with lots of >>> revisions / it being submitted and then quickly revised. >>> >>> >>> Just following up on this point: we'd like to request early >>> assignment from IANA for the various registries. Does that go through >>> the chairs or the authors at this point? >>> >>> Thanks, >>> >>> Eliot >>> >> >> >> >> _______________________________________________ >> OPSAWG mailing list >> OPSAWG@ietf.org >> https://www.ietf.org/mailman/listinfo/opsawg >> >
- Re: [OPSAWG] WG consensus call for the IANA early… Kent Watsen
- Re: [OPSAWG] WG consensus call for the IANA early… Eliot Lear
- Re: [OPSAWG] WG consensus call for the IANA early… Kent Watsen
- Re: [OPSAWG] WG consensus call for the IANA early… Eliot Lear
- Re: [OPSAWG] WG consensus call for the IANA early… Bert Wijnen (IETF)
- Re: [OPSAWG] WG consensus call for the IANA early… Eliot Lear
- Re: [OPSAWG] WG consensus call for the IANA early… Warren Kumari
- Re: [OPSAWG] WG consensus call for the IANA early… Kent Watsen
- Re: [OPSAWG] WG consensus call for the IANA early… Zhoutianran
- Re: [OPSAWG] WG consensus call for the IANA early… Warren Kumari
- Re: [OPSAWG] WG consensus call for the IANA early… Warren Kumari
- Re: [OPSAWG] WG consensus call for the IANA early… joel jaeggli