IETF Logo Mail Archive

Re: [core] 🔔 CoRE Working Group Adoption call for draft-hartke-t2trg-coral-09 and draft-hartke-t2trg-ciri-03

Jim Schaad <ietf@augustcellars.com> Tue, 16 July 2019 20:31 UTC

Return-Path: <ietf@augustcellars.com>
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 6A65D12016B for <core@ietfa.amsl.com>; Tue, 16 Jul 2019 13:31:53 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 jRt2O_j5K8Dg for <core@ietfa.amsl.com>; Tue, 16 Jul 2019 13:31:51 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E266E120186 for <core@ietf.org>; Tue, 16 Jul 2019 13:31:50 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 16 Jul 2019 13:31:43 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'core' <core@ietf.org>
References: <ACEC036C-0CD3-40DF-BABF-0EC6B5DDD2F9@tzi.org>
In-Reply-To: <ACEC036C-0CD3-40DF-BABF-0EC6B5DDD2F9@tzi.org>
Date: Tue, 16 Jul 2019 13:31:42 -0700
Message-ID: <022501d53c15$7bbea890$733bf9b0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQJ/Sn7iOT6VVQKumVHpLfjU9rjC16V5leLg
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Qg-3FQDPtrg4ql44JyVUnVdVhhM>
Subject: Re: [core] 🔔 CoRE Working Group Adoption call for draft-hartke-t2trg-coral-09 and draft-hartke-t2trg-ciri-03
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 16 Jul 2019 20:31:55 -0000

Big +1 - These documents make a lot of sense.

-----Original Message-----
From: core <core-bounces@ietf.org> On Behalf Of Carsten Bormann
Sent: Tuesday, July 16, 2019 12:12 PM
To: core <core@ietf.org>
Subject: [core] 🔔 CoRE Working Group Adoption call for draft-hartke-t2trg-coral-09 and draft-hartke-t2trg-ciri-03

In Prague, we said we were going to adopt the two base CoRAL specifications (which are currently marked as T2TRG drafts) as CoRE working group items.  We didn’t do the validation on the mailing list yet, which this working group adoption call is about.

Among other things, the adoption of these drafts is intended to fill the hole left when we put draft-ietf-core-links-json on hold.  So if you want to comment on the WG adoption, please also keep this aspect in mind, even if it could also be handled in a more orthogonal way (which you could recommend).

This starts a one-week working group adoption call.
(Normally we wouldn’t run a WG call that partially overlaps an IETF, but this time there is plenty of opportunity to think about CoRAL during the IETF, including the hackathon and the side meeting on core applications before the first of our two WG meetings.)

This is a formal call for adoption of draft-hartke-t2trg-coral-09 and draft-hartke-t2trg-ciri-03 as WG documents of the CoRE WG.
If you have read the drafts and support adopting them, please say so.
If you see a problem with adopting them as a WG document, please tell us.
For both, remember that WG adoption does not mean that we already have consensus on all the details(*), just that this is the right working document to address the issue (and that we should address the issue in the first place); you are encouraged to mention any issues that you already know.
Please respond to core@ietf.org, or exceptionally to core-chairs@ietf.org (for off-list comments).

This formal WG adoption call runs until the end of July 23rd so we can pick up the results at the CoRE meeting on July 25th.

Grüße, Carsten

(*) the most bikeshed issue (also relevant for the new draft name) appears to be whether CIRIs, which aren’t really IRIs that much, should rather be called CoRIs or maybe CRIs or even something completely different.  Please comment on this most important branding issue under https://github.com/ektrah/coral/issues/18 if you care.

_______________________________________________
core mailing list
core@ietf.org
https://www.ietf.org/mailman/listinfo/core

v2.23.0 | Report a Bug | By Email