[Anima] reserving SRV.* for GRASP Object Names --- (was Re: [IANA #1050768] expert review for draft-ietf-anima-autonomic-control-plane)

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 21 February 2018 21:54 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBEC0124C27 for <anima@ietfa.amsl.com>; Wed, 21 Feb 2018 13:54:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 RdHILhLq-Ejl for <anima@ietfa.amsl.com>; Wed, 21 Feb 2018 13:54:55 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B491120725 for <anima@ietf.org>; Wed, 21 Feb 2018 13:54:54 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 20C3F20091 for <anima@ietf.org>; Wed, 21 Feb 2018 17:02:17 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C5940806C2 for <anima@ietf.org>; Wed, 21 Feb 2018 16:54:53 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-Reply-To: <dcbe4b0d-a3ce-aac4-6816-fdca2dae7392@gmail.com>
References: <RT-Ticket-1050768@icann.org> <rt-4.2.9-11995-1519174154-705.1050768-7-0@icann.org> <rt-4.2.9-11994-1519174342-961.1050768-7-0@icann.org> <23627.1519182392@obiwan.sandelman.ca> <dcbe4b0d-a3ce-aac4-6816-fdca2dae7392@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 21 Feb 2018 16:54:53 -0500
Message-ID: <26183.1519250093@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ZjVJErXw-LMcRqTJzpAZZ_e2kc8>
Subject: [Anima] reserving SRV.* for GRASP Object Names --- (was Re: [IANA #1050768] expert review for draft-ietf-anima-autonomic-control-plane)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2018 21:54:57 -0000

Hi, WG.

I'm the designated expert reviewer for GRASP Object Names.
IANA asked me to look at autonomic-control-plane.  What fun!

I had NO problems with AN_ACP or SRV.est, but the following paragraph surprised me:

>    Note that the objective format "SRV.<service-name>" is intended to be
>    used for any <service-name> that is an [RFC6335] registered service
>    name.  This is a proposed update to the GRASP registry subject to
>    future work and only mentioned here for informational purposed to
>    explain the unique format of the objective name.

I think that if we want to reserve SRV.* for RFC6335 services, then we should
do exactly that.

The ship hasn't quite sailed on GRASP-15, because it's in gonna be in MISREF
on a bunch of other documents.  It could be done in GRASP-15, or in ACP; I
don't think that IANA cares, but it would less surprising to have it in
GRASP-15.  I don't know if it's been through AUTH48, I suspect not?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-