[core] early registration of content format specifid in est-coaps

Peter van der Stok <stokcons@bbhmail.nl> Thu, 19 July 2018 23:50 UTC

Return-Path: <stokcons@bbhmail.nl>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F479130E60; Thu, 19 Jul 2018 16:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 sN-w9EGyXKrv; Thu, 19 Jul 2018 16:50:11 -0700 (PDT)
Received: from smtprelay.hostedemail.com (smtprelay0144.hostedemail.com [216.40.44.144]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFA22130E43; Thu, 19 Jul 2018 16:50:11 -0700 (PDT)
Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay06.hostedemail.com (Postfix) with ESMTP id 5B22A180188A7; Thu, 19 Jul 2018 23:50:10 +0000 (UTC)
X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C
X-Spam-Summary: 50, 0, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :::::::, RULES_HIT:41:72:152:355:379:582:800:962:967:969:973:983:988:989:1152:1189:1208:1221:1260:1263:1313:1314:1345:1431:1436:1437:1516:1517:1518:1534:1541:1568:1575:1588:1589:1592:1594:1711:1714:1730:1776:1792:2525:2527:2561:2564:2682:2685:2829:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3586:3740:3865:3866:3867:3870:3871:3872:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4321:4605:4659:5007:6261:6298:6659:6678:6684:7903:8603:9015:9025:9177:9388:10004:10215:10400:10848:11232:11658:11914:12043:12295:12555:12679:12895:12986:13139:13141:13161:13199:13229:13230:13439:13846:13972:14181:14721:21080:21433:21451:21625:21691:30012:30045:30048:30054:30076, 0, RBL:216.40.42.5:@bbhmail.nl:.lbl8.mailshell.net-62.8.55.100 66.201.201.201, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral, Custom_rules:0:0:0, LFtime:25, LUA_SUMMARY:none
X-HE-Tag: plant38_1e8dd93f02520
X-Filterd-Recvd-Size: 3321
Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf01.hostedemail.com (Postfix) with ESMTPA; Thu, 19 Jul 2018 23:50:09 +0000 (UTC)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_094e18dc25450f30a45085bb29a4eed2"
Date: Thu, 19 Jul 2018 20:50:09 -0300
From: Peter van der Stok <stokcons@bbhmail.nl>
To: carsten bormann <cabo@tzi.org>, Jaime Jiménez <jaime.jimenez@ericsson.com>
Cc: Ace <ace-bounces@ietf.org>, Core <core@ietf.org>
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
Message-ID: <d78972d83b8c55e15116548f78a4fbda@bbhmail.nl>
X-Sender: stokcons@bbhmail.nl
User-Agent: Roundcube Webmail/1.2.7
X-Originating-IP: [31.133.147.176]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/kQwjsA6ncif2Z-cj_DANGJ2epfY>
Subject: [core] early registration of content format specifid in est-coaps
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2018 23:50:15 -0000

Dear CoRE co-chairs,

Given the advanced state of the implementation of est-coaps, it  is
requested that the content-format specified in
draft-ietf-core-multipart-ct is
registered early before the draft has become RFC.
That permits to fill in the definite content-format codes in the
implementation code.

The required content-format is specified below 

   | application/multict     | -      |  C-F nr  |
[I-D.ietf-core-multipart-ct]                  |
   Many thanks,

Peter 
-- 
Peter van der Stok
vanderstok consultancy
mailto: consultancy@vanderstok.org
www: www.vanderstok.org [1]
tel NL: +31(0)492474673     F: +33(0)966015248 

Links:
------
[1] http://www.vanderstok.org