[core-parameters] Core content-format number allocation

peter van der Stok <stokcons@xs4all.nl> Fri, 25 May 2018 07:27 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 7AB57126BFD; Fri, 25 May 2018 00:27:16 -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 6smjzvQ24-gA; Fri, 25 May 2018 00:27:14 -0700 (PDT)
Received: from lb2-smtp-cloud8.xs4all.net (lb2-smtp-cloud8.xs4all.net [194.109.24.25]) (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 1838112420B; Fri, 25 May 2018 00:27:13 -0700 (PDT)
Received: from webmail.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:215]) by smtp-cloud8.xs4all.net with ESMTPA id M780fSAMuL2mtM780fBwXG; Fri, 25 May 2018 09:27:12 +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 09:27:08 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 25 May 2018 09:27:08 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: core-parameters@ietf.org
Cc: draft-ietf-ace-coap-est@ietf.org, Hannes Tschofenig <hannes.tschofenig@gmx.net>
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
Message-ID: <636715d9568fb16b0dc779773fc99f89@xs4all.nl>
X-Sender: stokcons@xs4all.nl
User-Agent: XS4ALL Webmail
X-CMAE-Envelope: MS4wfDfxB6Qt7ihBtvSaUSE8NTT3mzOVW20+AmmNJy+COCmh1g9oCIXBZKiBZphSC5rLPJEtPSETAkLtOdnv2n/bU1EceBvD1gBOBY36mZRPY2aIJG57Udd6 DvDMbZ3jyLqESzlcm/GWou3mnkC4A2CF/RQWjW1T2yp1j12T2O7G6AK9s0y+PQJG/2b++gaXRPpDqHlonbDGT7LIDRtY8A0+kTP51tLfTPhnPJequWPkSzot vO6nEJDZWcZmA7G8YDI+AAMPWc7IDQ5MdxG2bL07pOfEfsUPg5J/LvJIacUZ+leE
Archived-At: <https://mailarchive.ietf.org/arch/msg/core-parameters/E1EPbOFmyq-5JZyjDc5RsVvDfl8>
Subject: [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 07:27:17 -0000

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
tel NL: +31(0)492474673     F: +33(0)966015248