Re: [core] Fwd: New Version Notification for draft-groves-core-rfc6690up-00.txt

Christian Amsüss <c.amsuess@energyharvesting.at> Thu, 10 November 2016 16:05 UTC

Return-Path: <c.amsuess@energyharvesting.at>
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 E008F12943B for <core@ietfa.amsl.com>; Thu, 10 Nov 2016 08:05:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 JYUSZ-lm-7R9 for <core@ietfa.amsl.com>; Thu, 10 Nov 2016 08:05:04 -0800 (PST)
Received: from prometheus.amsuess.com (alt.prometheus.amsuess.com [IPv6:2a01:4f8:190:3064::3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DBDB12973A for <core@ietf.org>; Thu, 10 Nov 2016 08:05:03 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8001:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id B73FC401E0; Thu, 10 Nov 2016 17:04:59 +0100 (CET)
Received: from poseidon-mailbox.amsuess.com (poseidon-mailbox.amsuess.com [10.13.13.231]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 52AA31BB; Thu, 10 Nov 2016 17:04:53 +0100 (CET)
Received: from hephaistos.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 760823D1; Thu, 10 Nov 2016 17:04:52 +0100 (CET)
Received: (nullmailer pid 32319 invoked by uid 1000); Thu, 10 Nov 2016 16:04:51 -0000
Date: Thu, 10 Nov 2016 17:04:51 +0100
From: Christian Amsüss <c.amsuess@energyharvesting.at>
To: Christian Groves <Christian.Groves@nteczone.com>
Message-ID: <20161110160451.5k3lqxfxonwj7nne@hephaistos.amsuess.com>
References: <147669921707.4489.15070761418407896856.idtracker@ietfa.amsl.com> <7a174518-1ab8-103a-ca19-100d523ef706@nteczone.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="p4ok6a6j3vvmresm"
Content-Disposition: inline
In-Reply-To: <7a174518-1ab8-103a-ca19-100d523ef706@nteczone.com>
User-Agent: NeoMutt/20161104 (1.7.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/7Nl4d47gPiUA37gM7Z69KpIbvqI>
Cc: core <core@ietf.org>
Subject: Re: [core] Fwd: New Version Notification for draft-groves-core-rfc6690up-00.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
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, 10 Nov 2016 16:05:11 -0000

Hello,

> [The prefix] MUST be followed by a ".".

the "core" prefix claimed in RFC6690 already violates that rule. Should
it be mentioned explicitly as an exception? Should the IETF "hand back"
all "core[^.]" to IANA?

Best regards
Christian

-- 
Christian Amsüss                      | Energy Harvesting Solutions GmbH
founder, system architect             | headquarter:
mailto:c.amsuess@energyharvesting.at  | Arbeitergasse 15, A-4400 Steyr
tel:+43-664-97-90-6-39                | http://www.energyharvesting.at/
                                      | ATU68476614