[Anima-bootstrap] converging on some common terminology

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 20 January 2017 15:26 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E9787129961; Fri, 20 Jan 2017 07:26:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.1
X-Spam-Status: No, score=-5.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id OvcE20dWtJn1; Fri, 20 Jan 2017 07:26:09 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B5EF129BDC; Fri, 20 Jan 2017 07:26:09 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca []) by tuna.sandelman.ca (Postfix) with ESMTP id F11DCE1E4; Fri, 20 Jan 2017 10:46:07 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 03837636BB; Fri, 20 Jan 2017 10:26:08 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org, 6tisch@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6+dev; 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: Fri, 20 Jan 2017 10:26:07 -0500
Message-ID: <2978.1484925967@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima-bootstrap/Iqsosf7pBgOeep4UL0C73mSUSKQ>
Cc: anima-bootstrap <anima-bootstrap@ietf.org>, netconf@ietf.org, 6tisch-security@ietf.org
Subject: [Anima-bootstrap] converging on some common terminology
X-BeenThere: anima-bootstrap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: anima@ietf.org, 6tisch@ietf.org
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <anima-bootstrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-bootstrap/>
List-Post: <mailto:anima-bootstrap@ietf.org>
List-Help: <mailto:anima-bootstrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2017 15:26:11 -0000

At the 6tisch-security design team call and then on the anima bootstrap call
on Tuesday, we discussed merging of terminology as an important step to
getting all the bootstrap ideas together.

These are the terms which we have concluded on:

1) PLEDGE.      replaces Joining Node and "New Node"
2) JOIN PROXY.  replaces Join Assistant and bare "Proxy"
3) JOIN REGISTRAR (and Coordinator). Replaces bare "Registrar", and JCE.
                   The "Coordinator" part is considered a seperate,
                   co-located, but optional role.

4) MASA.        remains the same.
5) vendor provided interface that MASA uses to talk to remains unnamed.

Here are the proposals therefore:

ANIMA, dtbootstrap document.
        was already using PLEDGE. (KEEP IT)
        PROXY -> JOIN PROXY.
        REGISTRAR -> officially, "Join Registrar", maybe be shortened
                     in the text to "Registrar" where this is unambiguous.

6tisch-dtsecurity ("Phase one") and 6tisch-minimal security ("One-Touch/Phase two"):

Was using Joining Node    --> Pledge.
Was using Join Assistant  --> Join Proxy
Was using Joint Coordination Entity (JCE)  -> Join Registrar and Coordinator.
Adds term MASA.

Additional terms which we need to import:

  1) "drop ship"
  2) "imprint",
  3) "enrollment",
  4) "audit token", "ownership token"  <- from draft-ietf-anima-voucher.

There also some discussion about the terminology used by 802.15.10:
      "mesh root"  <- has a coordinator role and a registrar role as I
      understand it.

We asked if: Registrar and Coordinator always co-located?
We thought so, but there could be exceptions, and it might be out of scope.

1) ANIMA documents to update terms, and be authoritative for terms.
2) 6tisch documents to update terms, pointing at ANIMA and 6tisch terminology.
3) 6tisch terminology document to include the terms as being imported from ANIMA.
4) netconf: probably just adjust terminology to point at when they terms are
            the same as ANIMA, or when they are different.

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