[core-parameters] Core content-format number allocation

peter van der Stok <stokcons@xs4all.nl> Fri, 25 May 2018 07:27 UTC

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>
User-Agent: XS4ALL Webmail
Archived-At: <https://mailarchive.ietf.org/arch/msg/core-parameters/E1EPbOFmyq-5JZyjDc5RsVvDfl8>
Subject: [core-parameters] Core content-format number allocation
Precedence: list

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

[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