Re: [core-parameters] Core content-format number allocation
peter van der Stok <stokcons@xs4all.nl> Fri, 25 May 2018 09:44 UTC
Return-Path: <stokcons@xs4all.nl>
X-Original-To: core-parameters@ietfa.amsl.com
Delivered-To: core-parameters@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FCCD12D953; Fri, 25 May 2018 02:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 5s47fBsE1bbI; Fri, 25 May 2018 02:44:01 -0700 (PDT)
Received: from lb3-smtp-cloud9.xs4all.net (lb3-smtp-cloud9.xs4all.net [194.109.24.30]) (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 68DE6124B0A; Fri, 25 May 2018 02:44:00 -0700 (PDT)
Received: from webmail.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:195]) by smtp-cloud9.xs4all.net with ESMTPA id M9GOfwv6rRSWtM9GOfQ8Xs; Fri, 25 May 2018 11:43:58 +0200
Received: from AMontpellier-654-1-155-119.w90-0.abo.wanadoo.fr ([90.0.250.119]) by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Fri, 25 May 2018 11:43:56 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Date: Fri, 25 May 2018 11:43:56 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: Klaus Hartke <hartke@projectcool.de>
Cc: consultancy@vanderstok.org, Hannes Tschofenig <hannes.tschofenig@gmx.net>, core-parameters@ietf.org, draft-ietf-ace-coap-est@ietf.org
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <CAAzbHvZuaFNPf0KNG4UpDzd_fmHC1OZbegvKu7NpEsdax9NUMg@mail.gmail.com>
References: <636715d9568fb16b0dc779773fc99f89@xs4all.nl> <CAAzbHvZ4CGgG6L5ZkaBF_JPN7d=o=XuWCETLF8-k7BP7KtYb=A@mail.gmail.com> <24ec93bb245164263df36d81aaf10c43@xs4all.nl> <CAAzbHvZuaFNPf0KNG4UpDzd_fmHC1OZbegvKu7NpEsdax9NUMg@mail.gmail.com>
Message-ID: <daeee2305e8c503bf02b03632c60813f@xs4all.nl>
X-Sender: stokcons@xs4all.nl
User-Agent: XS4ALL Webmail
X-CMAE-Envelope: MS4wfJa/fgEvHvlASyb42q8QPhBwOzR9pqQx7yI5NkdZanInc1gFPYwZ3O8loZfsJN0DQ+FGN0Wzu5NYWy/4QB+3MZfPC3RfCKzwHIP/BR5fugEPCuTP23C4 anTcczRXrKI36qtkZmq2f/+s1KHYnvWMnDSbiGzZvpDgsmXKyWw12GJdWUOFaTLJ8b7PJnxqMp33KkSIfhGTNarip3XEFHX9dbyAbRibYXz0DeWn2SMgvzXW X3AYdEjzH05AaUSrIjg4n/TEEHpWrSzaE6/kKNvylmB9p1HzMYJf/zLQAqmhqAU787wlRzTwR13KOuP3B0270QohCn2/JwLPg2nd/qdPwhuu+K3YxwpEi0pt IYydRA95daxh/hoPMYw0ZPmDKuS8NTAgGQl1TMbmxw8UXrVJgdbVhnZl26t13v7vsjhZS1DZ
Archived-At: <https://mailarchive.ietf.org/arch/msg/core-parameters/udD40SCHroOMsLEQdZWh2k_fylQ>
Subject: Re: [core-parameters] Core content-format number allocation
X-BeenThere: core-parameters@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Expert review of CoAP parameters." <core-parameters.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core-parameters>, <mailto:core-parameters-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core-parameters/>
List-Post: <mailto:core-parameters@ietf.org>
List-Help: <mailto:core-parameters-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core-parameters>, <mailto:core-parameters-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2018 09:44:03 -0000
Hi Klaus, the updated table. some reactions to your very useful remarks further below. many thanks, greetings, Peter - application/pkcs7-mime; smime-type=“server-generated-key"; Encoding ="identity"; ID = TBD1; Reference = RFC5751, RFC7030, RFC7231 - application/pkcs7-mime; smime-type=“certs-only”; Encoding = "identity"; ID = TBD2; Reference = RFC5751, RFC7231 - application/pkcs7-mime; smime-type=“CMC-request”; Encoding = "identity"; ID = TBD3; Reference = RFC5751, RFC5273, RFC7231 - application/pkcs7-mime; smime-type=“CMC-response”; Encoding = "identity"; ID = TBD4; Reference = RFC5751, RFC5273, RFC7231 - application/pkcs8; Encoding = "identity"; ID = TBD5; Reference = RFC5958, RFC7231 - application/csrattrs; Encoding = "identity"; ID = TBD6; Reference = RFC7030, RFC7231 - application/pkcs10; Encoding = "identity"; ID = TBD7; Reference = RFC5967, RFC7231 Klaus Hartke schreef op 2018-05-25 11:22: > What about “CMC-Response”? thanks, I missed that one. > > There’s a registry for “smime-type” values at > https://www.iana.org/assignments/media-type-sub-parameters/media-type-sub-parameters.xhtml#smime > Would it make sense to simply allocate a Content-Format ID to each of > them? I prefer to only specify those used in RFC7030 > > The media type and the content coding are orthogonal. However, > “binary” is not a valid content coding. (It’s really confusing > that the column is labeled “Encoding”; content coding is what is > meant.) Possible content codings are listed in > https://www.iana.org/assignments/http-parameters/http-parameters.xhtml#content-coding > You probably want the “identity“ content coding. You are right. looks most probable one. > > “application/pkcs8” and the other two media types don’t have the > “smime-type” parameter defined, so just remove that bit. > > Otherwise the table looks good to me. > > Klaus > > On Fri 25. May 2018 at 10:58, peter van der Stok <stokcons@xs4all.nl> > wrote: > >> HI Klaus, >> >> Thanks for the quick reaction, and thanks for pointing out some >> existing >> other smime types. >> I did a search in RFC 7030, and came up with other necessary smime >> types. >> >> Below the table as required for est-coap draft: (I will change the >> draft >> accordingly) >> >> - application/pkcs7-mime; smime-type=“server-generated-key”; >> Encoding = >> "binary"; ID = TBD1; Reference = RFC5751, RFC7030 >> - application/pkcs7-mime; smime-type=“certs-only”; Encoding = >> "binary"; >> ID = TBD2; Reference = RFC5751 >> - application/pkcs7-mime; smime-type=“CMC-request”; Encoding = >> "binary"; >> ID = TBD3; Reference = RFC5751, RFC5273 >> - application/pkcs8; smime-type = ---; Encoding = "binary"; ID = >> TBD4; >> Reference = RFC5958 >> - application/csrattrs; smime-type = ---; Encoding = "binary"; ID = >> TBD5; Reference = RFC7030 >> - application/pkcs10; smime-type = ---; Encoding = "binary"; ID = >> TBD6; >> Reference = RFC5967 >> >> I expect the Encoding is orthogonal to the media type and smime type >> >> specification. >> >> Many thanks, >> >> peter >> >> Klaus Hartke schreef op 2018-05-25 09:48: >>> Hi Peter, >>> >>> I see you’re requesting Content-Format IDs for the following >>> existing media types: >>> >>> - application/pkcs7-mime >>> - application/pkcs8 >>> - application/csrattrs >>> - application/pkcs10 >>> >>> A Content-Format is the combination of a media type and a content >>> coding. Please specify the content coding(s) you want to use with >> each >>> media type. The possible set of content codings can be found at >>> >> > https://www.iana.org/assignments/http-parameters/http-parameters.xhtml#content-coding >>> >>> Please format your request as a table that looks like Table 9 in >>> https://tools.ietf.org/html/rfc7252#section-12.3 (one row for each >>> combination of a media type and a content coding) >>> >>> It seems “application/pkcs7-mime“ actually does define a media >>> type parameter, “smime-type ”. RFC 5751 says: >>> >>> Because there are several types of application/pkcs7-mime >> objects, >>> a >>> sending agent SHOULD do as much as possible to help a receiving >>> agent >>> know about the contents of the object without forcing the >> receiving >>> agent to decode the ASN.1 for the object. The Content-Type >> header >>> field of all application/pkcs7-mime objects SHOULD include the >>> optional "smime-type" parameter, as described in the following >>> sections. >>> >>> So it seems the parameter is more or less required. Do you want to >>> register a Content-Format ID for each defined smime-type value? >> Then >>> the list of media types (that need to be paired with a content >> coding) >>> looks like this: >>> >>> - application/pkcs7-mime; smime-type=“enveloped-data” >>> - application/pkcs7-mime; smime-type=“signed-data” >>> - application/pkcs7-mime; smime-type=“certs-only” >>> - application/pkcs7-mime; smime-type=“compressed-data” >>> - application/pkcs8 >>> - application/csrattrs >>> - application/pkcs10 >>> >>> Klaus >>> >>> On Fri 25. May 2018 at 09:27, peter van der Stok >> <stokcons@xs4all.nl> >>> wrote: >>> >>>> Dear core parameter experts, >>>> >>>> In draft-ietf-ace-coap-est we want to allocate content format >>>> numbers to >>>> 4 already existing media formats. >>>> LWM2M people are implementing the est-coaps specification and >> want >>>> to >>>> deploy it as quickly as possible. >>>> Therefore, they need to know the allocated numbers to write into >>>> their >>>> code. >>>> An early allocation before publication of the draft as RFC will >> be >>>> appreciated. >>>> >>>> Below the IANA text from the draft, using TBD1 - TBD4 as >> allocated >>>> numbers. >>>> >>>> Many thanks, >>>> >>>> peter >>>> >>>> >>> >> > __________________________________________________________________________________________________________ >>>> >>>> 8.1. Content-Format registry >>>> >>>> Additions to the sub-registry "CoAP Content-Formats", within the >>>> "CoRE Parameters" registry are needed for the below media types. >>>> These can be registered either in the Expert Review range >>>> (0-255) or >>>> IETF Review range (256-9999). >>>> >>>> 1. >>>> >>>> * application/pkcs7-mime >>>> * Type name: application >>>> * Subtype name: pkcs7-mime >>>> * ID: TBD1 >>>> * Required parameters: None >>>> * Optional parameters: None >>>> * Encoding considerations: binary >>>> * Security considerations: As defined in this specification >>>> * Published specification: [RFC5751] >>>> * Applications that use this media type: EST >>>> >>>> 2. >>>> >>>> * application/pkcs8 >>>> * Type name: application >>>> * Subtype name: pkcs8 >>>> * ID: TBD2 >>>> * Required parameters: None >>>> * Optional parameters: None >>>> * Encoding considerations: binary >>>> * Security considerations: As defined in this specification >>>> * Published specification: [RFC5958] >>>> * Applications that use this media type: EST >>>> >>>> 3. >>>> >>>> * application/csrattrs >>>> * Type name: application >>>> * Subtype name: csrattrs >>>> * ID: TBD3 >>>> * Required parameters: None >>>> * Optional parameters: None >>>> * Encoding considerations: binary >>>> * Security considerations: As defined in this specification >>>> * Published specification: [RFC7030] >>>> * Applications that use this media type: EST >>>> >>>> 4. >>>> >>>> * application/pkcs10 >>>> * Type name: application >>>> * Subtype name: pkcs10 >>>> * ID: TBD4 >>>> * Required parameters: None >>>> * Optional parameters: None >>>> * Encoding considerations: binar >>>> * Security considerations: As defined in this specification >>>> * Published specification: [RFC5967] >>>> * Applications that use this media type: EST >>>> >>>> >>> >> > ___________________________________________________________________________________________ >>>> >>>> -- >>>> Peter van der Stok >>>> vanderstok consultancy >>>> mailto: consultancy@vanderstok.org >>>> www: www.vanderstok.org [1] [1] >>>> tel NL: +31(0)492474673 F: +33(0)966015248 >>>> >>>> _______________________________________________ >>>> core-parameters mailing list >>>> core-parameters@ietf.org >>>> https://www.ietf.org/mailman/listinfo/core-parameters >>> >>> >>> Links: >>> ------ >>> [1] http://www.vanderstok.org > > > Links: > ------ > [1] http://www.vanderstok.org
- [core-parameters] Core content-format number allo… peter van der Stok
- Re: [core-parameters] Core content-format number … Klaus Hartke
- Re: [core-parameters] Core content-format number … peter van der Stok
- Re: [core-parameters] Core content-format number … Klaus Hartke
- Re: [core-parameters] Core content-format number … peter van der Stok
- Re: [core-parameters] Core content-format number … Klaus Hartke
- Re: [core-parameters] Core content-format number … Esko Dijk