Re: [Anima] Michael: IANA request for GRASP registry missing from BRSKI text

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 06 November 2020 22:34 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 AAD1F3A0DE2 for <anima@ietfa.amsl.com>; Fri, 6 Nov 2020 14:34:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.345
X-Spam-Level:
X-Spam-Status: No, score=-2.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.247, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 QmNskFUhE159 for <anima@ietfa.amsl.com>; Fri, 6 Nov 2020 14:33:52 -0800 (PST)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEE1C3A0DDB for <anima@ietf.org>; Fri, 6 Nov 2020 14:33:47 -0800 (PST)
Received: by mail-pf1-x42d.google.com with SMTP id e7so2694688pfn.12 for <anima@ietf.org>; Fri, 06 Nov 2020 14:33:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=EBl9olXEThC+DkP8z2Gp4MtIkrDOLXVpVx7wLecmz+Y=; b=IY9/on5261+GnDeoa8WBLJ777cYrgPgK6MB0pdeISb5jC8MwbarJhBUF1M50VsHB3s XKF8tMgGkxykOj8xQTqJBaNLP/k7m6uVC+eOV/kEf0QFVf7Mjr+P1qXWKKbPoVDcUDRo GT7zDIDUfzQawOWZvpYynU6JhMI0AY8ualRyvwXu3bGnDTSVDRCA+U2dQqXCBgnEjaJ1 lg5WOGG1g1sEXItsOlGjmkeE+cg/Sx+D7b18iOaYlrFuIgq0K5W0DDRPVMwASPrpnmw0 mUrm2eox3Sdoc2Ij0wPEmcdajYbATb8ZiEvBGuC/APlEdS2gJvRoIT2QL85qPJAZtRxL bECg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=EBl9olXEThC+DkP8z2Gp4MtIkrDOLXVpVx7wLecmz+Y=; b=TTgi5ZBFbgDS6BFeSkYcUhE6qbSkMAY1lNX/Dec0ewMuw2ZQ4hfgKy1g01xSSjT/g+ DSE7beUyPytlPQ6C4DogABJmLD6qh67SxH4Eycxxnat5GiP3smXq8PqL3Ss+hm44whMX AMz82PVu/W6DpiwOLON5m1LmLe0KQF+lS/TCE23zo1427xEEvlSjqO57zfbUtaNCBQuS RLto5cRrNkYbGto5ho54c80VpwpZa6eeOB/b32a3MsEsFOJNSlK5ppsSpywAnTEsjvkV mY6YlotjqiG/xEHn38cTV2w5O/Qu/0EcCQEMHWsFEYiN2EisixIiMwxLPBZx5rGWRKb1 aOUA==
X-Gm-Message-State: AOAM530O1Qrro3VU5gZqyXUYzFKlJpTNvVa9jT1MjLIJs6kGOY2R8Lwc LmNdgRMPfpEnY8gegnYNgzUjFNzwwbkpjA==
X-Google-Smtp-Source: ABdhPJzMXlEOYUJARzeK7wQpnJOH80Gp9GDfwC+p7w5g5ytHW0VeTeQHOhO3C5HfIghLCIDJ92R+yA==
X-Received: by 2002:a63:3c1b:: with SMTP id j27mr3440733pga.79.1604702026259; Fri, 06 Nov 2020 14:33:46 -0800 (PST)
Received: from [192.168.178.20] ([151.210.130.0]) by smtp.gmail.com with ESMTPSA id o9sm3969818pjh.6.2020.11.06.14.33.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Nov 2020 14:33:45 -0800 (PST)
To: Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
Cc: Toerless Eckert <tte@cs.fau.de>, warren@kumari.net
References: <20201106162446.GB48249@faui48f.informatik.uni-erlangen.de> <27682.1604697321@localhost>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <f7fe5fb7-a4b3-c688-49f4-2d60dfde4846@gmail.com>
Date: Sat, 7 Nov 2020 11:33:41 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <27682.1604697321@localhost>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0NgrliviHyEy3evtyjxKPk_VS8M>
Subject: Re: [Anima] Michael: IANA request for GRASP registry missing from BRSKI text
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 06 Nov 2020 22:34:02 -0000

Yes, the registry has been there for some time:
https://www.iana.org/assignments/grasp-parameters/grasp-parameters.xhtml#objective-names and guess who is the expert?

Regards
   Brian

On 07-Nov-20 10:15, Michael Richardson wrote:
> 
> Toerless Eckert <tte@cs.fau.de> wrote:
>     > Am i completeley confused, or did we miss until now the IANA request in BRSKI for
>     > the new entries AN_Proxy and AN_join_registrar ?
> 
> I dunno what happened.
> But, you are exactly right.
> Who to blame? when in doubt? clearly, BLAME CANADA.
> 
> It wasn't until my third reading of:
>   grasp-15, section 6, https://datatracker.ietf.org/doc/html/draft-ietf-anima-grasp-15#section-6
> 
> that I saw that GRASP actually does create a _GRASP Objective Names Tables_.
> I was going to complain that there was no registry created, but it just
> didn't have it's own heading:
> 
>    GRASP Objective Names Table.  The values in this table are UTF-8
>    strings which MUST NOT include a colon (":"), according to
>    Section 2.10.1.  Future values MUST be assigned using the
>    Specification Required policy defined by [RFC8126].
> 
>    To assist expert review of a new objective, the specification should
>    include a precise description of the format of the new objective,
>    with sufficient explanation of its semantics to allow independent
>    implementations.  See Section 2.10.3 for more details.  If the new
>    objective is similar in name or purpose to a previously registered
>    objective, the specification should explain why a new objective is
>    justified.
> 
>     > I was just checking IANA actions for ACP and did not see these two in the GRASP
>     > registry:
> 
>     > https://www.ietf.org/archive/id/draft-ietf-anima-bootstrapping-keyinfra-44.txt
> 
>     > Not sure about the process, e.g.: if "specification required" (GRASP registry)
>     > mandates the IANA text in the BRSKI RFC... I fear it does ? If three is an easier
>     > way as having Warren approve another rev... ?
> 
> I think that the text has to go in.
> Warren needs to approve the change, and IANA needs to review, and then the
> text needs to go in now or at AUTH48, depending upon where the RPC really is.
> 
> I have version -45 ready to post, diffs are at:
> 
> I think that this is non-constroversial, does not require a WG LC, and can
> slide in at AUTH48, but as it required IANA review, it's better if it happens
> sooner.
> 
> It looks like the YANG is now 2-3 characters too long in places, so I've also
> rewrapped that.  The base64 in the examples will also need to be reflowed
> ick.
> 
> https://www.ietf.org/rfcdiff?url1=draft-ietf-anima-bootstrapping-keyinfra-44&url2=https://raw.githubusercontent.com/anima-wg/anima-bootstrap/master/dtbootstrap-anima-keyinfra.txt
> 
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
> 
> 
> 
> 
> 
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
>