Re: [media-types] [IANA #1275306] Request for +cose registration in the Structured Syntax Suffixes registry
Darrel Miller <darrel@tavis.ca> Tue, 04 July 2023 14:52 UTC
Return-Path: <darrel@tavis.ca>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECAB4C14F693 for <media-types@ietfa.amsl.com>; Tue, 4 Jul 2023 07:52:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tavisdev.onmicrosoft.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OUZxssM3yzqe for <media-types@ietfa.amsl.com>; Tue, 4 Jul 2023 07:52:47 -0700 (PDT)
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10on2061.outbound.protection.outlook.com [40.107.94.61]) (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 98333C14EB17 for <media-types@ietf.org>; Tue, 4 Jul 2023 07:52:47 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YY4B9u93+uwymAwxXyRtXTzT07yqEWCyPsFRWcgLcZV9DWiN85fVfpLXnx9LLaQ7wA4SI1eg6PJLIZcMkq6atTsFI2dot4wlz3xn6s9Z5yQ3Rl/D9Yp8jG/WfwDno+i/WXgPlOtu0QXLhTCvF81z1uh63TMBT/VBJQCazyaaRWUNe1FowVkw5YTdkwLHwVK8rjEyC/4O/DGrf78wWXDFmEuxjBLdjR3wxXR7rL12mJWOy1CVmCjUwl+qr2pqnm1EFDHOKTKbgQzLirRMyPzGfhKiIUJub54qsLDWkRKoZqhKwBbOQcIPE7Tt7p20K6+BSJE7CNhv0RPzsM0VxLL/RQ==
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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=ZKLMdyoTHZSmOr+nm79uB4SyQgqtHV8UXFBaexflfYk=; b=YKtBFVzsPoMsDzrYoWmJA5cmWh2BULfsM7DjDb63mw6ZdWrp40Q0OeSkY+RtzZy2eGYTWOP71yLvYK5EChEQELP2mLV0us2lRMalpTmIPplOFeMwEm66ECv0mjQvNx6mxm/iOzzAsdrz87ChLgVEq7uuY+QBuYk0HUxjjhwVKiLvJqjP8irCdMZy0sMoLtr/2L8fidMAIVXnP8BQ0pzDpIznN+6ni42mWUNtHeSRqZBWanBGKriwIgSUDBh3B2LbPJHSXCTIiqA31piGCULCyPiFhaX2z2/No56Cf1twMMTrF9nU9O/twajx0jJRagiU6CvbpWazLDDyezZBW5pIhg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=tavis.ca; dmarc=pass action=none header.from=tavis.ca; dkim=pass header.d=tavis.ca; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tavisdev.onmicrosoft.com; s=selector2-tavisdev-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZKLMdyoTHZSmOr+nm79uB4SyQgqtHV8UXFBaexflfYk=; b=OXIeTSyo4FWafDapNDXdiHfRl5JXtSKomVyqqLnLw3KO8x+VEERt4X8NIjg0bmt+tzkoxQl/LlBbgfxKNipa/ogkD2Mh2hpYhb4ktbodughh+yIy8N9j+OVQFQW8aFKiby13Z+FYKaQTux9zVMwRq6PqmZJYZGAmlGE35wiPEVM=
Received: from DM6PR01MB5964.prod.exchangelabs.com (2603:10b6:5:202::33) by CO1PR01MB6792.prod.exchangelabs.com (2603:10b6:303:d5::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6565.17; Tue, 4 Jul 2023 14:52:46 +0000
Received: from DM6PR01MB5964.prod.exchangelabs.com ([fe80::83b6:51cb:2ad:b5c4]) by DM6PR01MB5964.prod.exchangelabs.com ([fe80::83b6:51cb:2ad:b5c4%7]) with mapi id 15.20.6544.024; Tue, 4 Jul 2023 14:52:45 +0000
From: Darrel Miller <darrel@tavis.ca>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>, "iana-mime-comment@iana.org" <iana-mime-comment@iana.org>
CC: "media-types@ietf.org" <media-types@ietf.org>
Thread-Topic: [media-types] [IANA #1275306] Request for +cose registration in the Structured Syntax Suffixes registry
Thread-Index: AQHZpUuarX2O901RtUSLMihCoYLOyq+XYot2gAaFHAGACt2NqIAAeIwAgACExiI=
Date: Tue, 04 Jul 2023 14:52:45 +0000
Message-ID: <DM6PR01MB596461E0EA220DF436298F6FA32EA@DM6PR01MB5964.prod.exchangelabs.com>
References: <RT-Ticket-1275306@icann.org> <DU0P190MB1978B178D63C6065786D2B65FD22A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <rt-5.0.3-160711-1687467205-1618.1275306-9-0@icann.org> <DM6PR01MB596439428661C390293C5EE8A322A@DM6PR01MB5964.prod.exchangelabs.com> <DM6PR01MB5964D56F0C46C1DB008A78E6A327A@DM6PR01MB5964.prod.exchangelabs.com> <rt-5.0.3-490449-1687832022-228.1275306-9-0@icann.org> <rt-5.0.3-1532165-1688427685-890.1275306-9-0@icann.org> <DU0P190MB1978A7349D70D8BF98BF702CFD2EA@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
In-Reply-To: <DU0P190MB1978A7349D70D8BF98BF702CFD2EA@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=tavis.ca;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: DM6PR01MB5964:EE_|CO1PR01MB6792:EE_
x-ms-office365-filtering-correlation-id: 41f88ebc-d436-40b0-eb87-08db7c9e53fb
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: z1oVxNGQFxGsOPfhE9cE92aTR49shy9hWkC3sbZ7fJ7RAWtjE5tfSGw9jeeevLDRB8p6T8YAWPFECAjkXgKFzI0jUV8f/z0lhZLzqfhYXY0t31YZHTZEgn73+VOjQ6OgLhmXQQtmwl9x3k02/ppmMlo1Y2J7TrUHVELxK2kSCaOTim4ZHJvFAkb/VU5BaFdcF9V5LLrVFWGI3kervMNETBUuQQ29BIHT4LO3+wZ5fXT6eOh/rCh4cmo4Y/LibiFY35KuICgmcC3M5s9kWec+wDs78t7gNdU95hNBzc9zDv7BLnMH9UtM/pmmMLAszoO0IzM5DwOWle6BvnRDCPOXBYjBB/1CQL6YzqRWHK9ljJbSc3usFcp+8oXKeSritw46neAYP+kl9qariOseaql14CGwd/XTiUu5oHxnZGAMD7bJgsL2MFWXepGaR1evRlA5SRV3sv7S1NbZz8UUuMg5fh82WXMWfBn1FRumB3hAZQAyGsBwUNydKONB8B5h0yGC7piG0SemYQEI7QZityW/VhEGaQ7x3Yofez8DGdvrxnrmBPSfseMKtTP7/lWYIrAnQqi5u/Uxguu9/qB5cH0u3c5OQLiR57fkHegekPyZ5nQ=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR01MB5964.prod.exchangelabs.com; PTR:; CAT:NONE; SFS:(13230028)(346002)(366004)(396003)(136003)(39830400003)(376002)(451199021)(41300700001)(7696005)(966005)(8936002)(8676002)(4326008)(5660300002)(6506007)(53546011)(76116006)(52536014)(91956017)(316002)(71200400001)(478600001)(26005)(19627405001)(186003)(110136005)(9686003)(66476007)(66556008)(64756008)(66946007)(84970400001)(66446008)(66899021)(2906002)(83380400001)(66574015)(55016003)(38070700005)(33656002)(86362001)(38100700002)(122000001)(166002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: MoM9p93SqaNnOzQ8dbCK1Cxm+qnqfW/vJxSiBMBuKEtpBWwk+UIxQuUML0rebRspDJONF1DpanTxAsOa2NrQXVtkwvuLGeW3mqJH+JnTCmKVM07W5AQE6YswUc232zHVKfCWxaEvpS+rChtw3uhc0WtJjIJgNpd2lE4sWUa8INDMwqAvHw6Wm2MxogbZ2Tsq9yTHf+JPBQzWifctsmpDRPyCrfsi5sYHXIWjHnMBYPT24oX4wKe2+X3Y0QzaSAY83dB7798M4iGkpwyCEOMziuFjsBO/sLmSZ2J5mavEeKWE1iWiS5fnYw3HNXpT5eCSmXDXo2fMZf/Rcd5j1dmlltOsNTzxUunz0yTGwIgNSUgyehEvFUrt8WnWPQtz9GF+bhcjqJ5R+U2RE0CdG6e2iZhHBl1Ff3IffWfVbqOk/oFj6Pf+4S55dxb9++Acjks3Cz86M2P1DGZL8tQKODwRfXEjCE+Q+BWI4YA91ps4OUHiN0V5RXBkuHkO0H7qZpJa8vocL8SOWzqE94bD3PvcuG0Yws0PGJhVZrN4NbmgOjIv5Iy78hX4+cTY+P5j08qHZnR6gXePBQvXla6xmW5JVSeorajN3epVpbZnHtHz25tOApeEc4mW13A8+WptoPdQUXDsZS7e/4gyrYwYu07VSxbPNK+UWpZdMRXeLkd1njaPe8/KVSr2mFSH4DiUVeffepGwVj2dFLs1qs287oi1/vjtjHJM4j5psFOQmols2nnMzmk48o9jU7BwF+J9naVzGV+XUVLStGoUvn6Lttt6CCcq3EuanwuGg+INID98nklI5Y5ZQDZuBbmeS1SrrggQ9tIN6xiloORrAxJaSd5uP0DyS2+84hMAF980qRnKXib7tB03aPBxV58e+6H7UIp1W1S77kkBiC+JkbQI7Z9s+xzn16FLqWOHSBcrXbYHp/waZbcTkuJcaKEMuPQ4fjOyR4dTdhMJZ6kySFAxOdMV+mUEnkap2XGGrOv/26UDMjUG3llq/0K4jpZLjYB7Akq5UjU1kCYB8gQUqoU54HBRJM9DIvX/99i3+mStMF4j2LIgPCYCf3xPGERdmXnmHPE012QAq8t3g0EepelUbu8JX7Ooozc9C0k4dxUA4DCUJc5gWyqKtSHtnvNmpZPBVC7h7Bt2AXpXzXmCZmZUExNHAHx60FCz5ZRpFLXaXQcugi2jNlXBhCX6RabvXhRX6u5JJvgqh3zDwiynB/HyKuKX42WT89G8FReEUowqWjNHJhAodt0VU3PldbPxl3x+cRTzlXbIvGGNRkXP99lHeLex9t4JEuzwyDP9PTOu+ZfUHrWxykh30sLNQNFKltXbpdOutZ7ztLqQdWrTyjvxBCO2MnFtjpAQwOh/rdFyyFX+DwQ6QEnO8IMJ8whzeM8kIe4fTpLC15mow+7YWS9IKx6/odUKz1o27aD8do6niL+MizE77rZN1wPokkR8Nf2PMn+IEnnZ3NwwCYrMQG8xn4H4gLyJEHXeA3K1pBoH4dXeWkP5WdqMDt66a5pOu8T4rM5D6oVf0xVJ4o0qfafqoJnMogSp0JJ2+SxKNF+wPFGgVvQ=
Content-Type: multipart/alternative; boundary="_000_DM6PR01MB596461E0EA220DF436298F6FA32EADM6PR01MB5964prod_"
MIME-Version: 1.0
X-OriginatorOrg: tavis.ca
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR01MB5964.prod.exchangelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 41f88ebc-d436-40b0-eb87-08db7c9e53fb
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jul 2023 14:52:45.8411 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8cea02ec-9788-4bac-a19b-3e782a3e9bb0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: LHSzSwxttCko64g7rCA83F1IoENxquoJC9C7Egkx2tUax41qrcQxIyaOfEfnr8Yu
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR01MB6792
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/11DZ2sHMIy-4E52MrCp1Dy7IQg4>
Subject: Re: [media-types] [IANA #1275306] Request for +cose registration in the Structured Syntax Suffixes registry
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2023 14:52:52 -0000
Esko, Thank you for the clarification on the use of the cose-type parameter. Based on the fact that the structured syntax suffix only required "Expert Review" and not "Specification Required", I think the submission of the template falls under the "alone" clause in this statement: > The template may be contained in an Internet Draft, alone or as part of some other protocol specification. Based on this reading I think what you have provided so far is sufficient to complete the registration. Darrel ________________________________ From: Esko Dijk <esko.dijk@iotconsultancy.nl> Sent: Tuesday, July 4, 2023 2:53 AM To: iana-mime-comment@iana.org <iana-mime-comment@iana.org> Cc: Darrel Miller <darrel@tavis.ca>; media-types@ietf.org <media-types@ietf.org> Subject: RE: [media-types] [IANA #1275306] Request for +cose registration in the Structured Syntax Suffixes registry To me it also looks like only Section 6 would apply to a suffix registration; and in particular step 2 there does require a document. So for the +cose registration request we can include this registration in the next revision of draft-ietf-anima-constrained-voucher and the current request can be closed! Thanks for the input so far. On the policy: The "Specification Required" policy is slightly stronger than "Expert Review + step 2", since it requires a "permanent and readily available" document. While the existing "Expert Review + step 2" requires effectively "any document which will be treated as an IETF Contribution" which is not necessarily permanent, or readily available. (Is an I-D that expires 'permanent'? Seems not.) So the procedure could be left as is, in principle. Esko -----Original Message----- From: media-types <media-types-bounces@ietf.org> On Behalf Of Amanda Baber via RT Sent: Tuesday, July 4, 2023 01:41 Cc: darrel@tavis.ca; media-types@ietf.org Subject: [media-types] [IANA #1275306] Request for +cose registration in the Structured Syntax Suffixes registry Hi Darrel, A couple of questions about this: On Tue Jun 27 02:13:42 2023, darrel@tavis.ca wrote: > Amanda, > > Upon reading further on this topic, the media type registration rules > around IETF specifications in the standards tree are very clear. > > > The registration proposal MUST be published as an RFC. > https://www.rfc-editor.org/rfc/rfc6838#section-3.1 > > I see no indication that registration of a structured syntax suffix > can avoid this step. I was under the impression that the Section 3 applies only to media types. Section 3.1 refers to media types and the duties of the media type reviewer(s), but never to suffixes or suffix reviewers. For example, if the registration is included in a document meant for publication as an independent-stream RFC: the IESG makes a one-time decision on whether the registration submitter represents a recognized standards-related organization; after that, a Media Types Reviewer (Designated Expert or a group of Designated Experts) performs the Expert Review as specified in this document. Rules for suffix registrations are laid out in Section 6, which allows for an I-D or another type of document: 2. If there is no entry for their suffix scheme, fill out the template (specified in Section 6.2) and include that with the media type registration. The template may be contained in an Internet Draft, alone or as part of some other protocol specification. The template may also be submitted in some other form (as part of another document or as a stand-alone document), but the contents will be treated as an "IETF Contribution" under the guidelines of BCP 78 [RFC5378]. If I'm reading this correctly, this raises another question: at https://www.iana.org/assignments/media-type-structured-suffix, we say that the registration procedure is Expert Review. Should this be listed as Specification Required (which requires both a publicly-available spec and expert review) instead? You can see definitions of Expert Review and Specification Required in Sections 4.5 and 4.6 of RFC 8126: https://www.rfc-editor.org/rfc/rfc8126.html#section-4 How should we describe the registration procedure for suffixes? Should this request be closed for now? thanks, Amanda > Darrel > > ________________________________ > From: media-types <media-types-bounces@ietf.org> on behalf of Darrel > Miller <darrel@tavis.ca> > Sent: Thursday, June 22, 2023 6:20 PM > > Hi Amanda, > > Yes, I can review by that date. > > My reading of the registration procedures here https://www.rfc- > editor.org/rfc/rfc6838#section-6 indicates that template must be > included in some other document. And if the IETF is the change > controller, then that document should be an IETF document. I do not > believe it is sufficient to list RFC9052. If we cannot point to a > document then the registry becomes the source of truth, and we are > talking about going and making text cleanup changes to the suffix > registry. It doesn't feel right to have a source of truth that can be > edited. > > Darrel > > ________________________________ > From: Amanda Baber via RT <iana-mime-comment@iana.org> > Sent: Thursday, June 22, 2023 4:53 PM > Cc: Darrel Miller <darrel@tavis.ca>; media-types@ietf.org <media- > types@ietf.org> > Subject: [IANA #1275306] Request for +cose registration in the > Structured Syntax Suffixes registry > > Hi Darrel, > > Can you review this request for us by July 6th? > > This question may be for both you and Alexey: is it possible to list > the IESG as the change controller (this would actually have to be > changed to the IETF, per current guidance) and RFC 9052 as the > reference if that document doesn't explicitly make the registration? > > thanks, > Amanda > > ===== > > Hello, > > I would like to request the following registration. It has been sent > to the media-types WG list already, and had some (limited) discussion > but no input from experts yet. > > Email thread on media-types: > https://mailarchive.ietf.org/arch/msg/media- > types/aoat1ILh0oqhNjWRka0HoijwxjQ/ > > Registry: https://www.iana.org/assignments/media-type-structured- > suffix/media-type-structured-suffix.xhtml > > Template info: > > Name: application/cose > > +suffix: +cose > > References: https://www.rfc-editor.org/info/std96 (RFC9052) > > Encoding considerations: COSE is always encoded as CBOR, which is > binary > > Interoperability considerations: None > > Fragment identifier considerations: N/A > > Security considerations: as per RFC9052, section 12 > > Contact: IETF COSE WG > > Author/Change controller: IESG > > > Best regards > > Esko > > IoTconsultancy.nl | Email/Teams: esko.dijk@iotconsultancy.nl | > +31 6 2385 8339 _______________________________________________ media-types mailing list media-types@ietf.org https://www.ietf.org/mailman/listinfo/media-types
- [media-types] [IANA #1275306] Request for +cose r… Amanda Baber via RT
- Re: [media-types] [IANA #1275306] Request for +co… Darrel Miller
- Re: [media-types] [IANA #1275306] Request for +co… Darrel Miller
- Re: [media-types] [IANA #1275306] Request for +co… Orie Steele
- Re: [media-types] [IANA #1275306] Request for +co… Darrel Miller
- Re: [media-types] [IANA #1275306] Request for +co… Darrel Miller
- Re: [media-types] [IANA #1275306] Request for +co… Esko Dijk
- [media-types] [IANA #1275306] Request for +cose r… Amanda Baber via RT
- Re: [media-types] [IANA #1275306] Request for +co… Esko Dijk
- Re: [media-types] [IANA #1275306] Request for +co… Darrel Miller
- Re: [media-types] [IANA #1275306] Request for +co… Esko Dijk
- Re: [media-types] [IANA #1275306] Request for +co… Esko Dijk
- Re: [media-types] [IANA #1275306] Request for +co… Darrel Miller