IETF Logo Mail Archive

Re: [Anima-bootstrap] 6tisch join -01 documented posted

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 15 November 2016 01:02 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 315021295A0; Mon, 14 Nov 2016 17:02:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 fgb6U3D8oiuQ; Mon, 14 Nov 2016 17:02:53 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D631129411; Mon, 14 Nov 2016 17:02:53 -0800 (PST)
Received: from dooku.sandelman.ca (dhcp-8d96.meeting.ietf.org [31.133.141.150]) by relay.sandelman.ca (Postfix) with ESMTPS id B0DBC1F91A; Tue, 15 Nov 2016 01:02:51 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 3C3E91928; Mon, 14 Nov 2016 20:02:49 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-reply-to: <51679334-5725-7279-cdaf-c3866d5f2bd0@gmail.com>
References: <20351.1476971471@obiwan.sandelman.ca> <0343d14c-5b18-b821-c9ad-d77fb7dae490@gmail.com> <12808a8a-5de1-c6cb-3f96-945573041ee4@gmail.com> <24910.1479078501@dooku.sandelman.ca> <efb2a1b9-a5b2-9e38-abd5-1c8031d9f1cd@gmail.com> <5562.1479107882@dooku.sandelman.ca> <51679334-5725-7279-cdaf-c3866d5f2bd0@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Tue, 15 Nov 2016 08:28:25 +1300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Tue, 15 Nov 2016 10:02:49 +0900
Message-ID: <4807.1479171769@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima-bootstrap/VGibfBDzpkAAAX7C-yFTcsRY_iA>
Cc: anima-bootstrap <anima-bootstrap@ietf.org>, 6tisch-security <6tisch-security@ietf.org>
Subject: Re: [Anima-bootstrap] 6tisch join -01 documented posted
X-BeenThere: anima-bootstrap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Tue, 15 Nov 2016 01:02:54 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> These are the interactions, and I will try to give some names to the various
    >> interactions in a future document, but suggestions most welcome.
    >>
    >> 1) pledge <-> Join Assistant (JA)
    >> Discovery of JA:   mDNS and/or M_FLOOD

    > Is Join Assistant the agreed terminology (instead of Proxy)?

I prefer it, and it's the accepted 6tisch terminology, but I don't think that
ANIMA has agreed to use that term, and is using Proxy.

    >> 2) Join Assistant *discovery* of Registrar
    >> in 6tisch, omitted, will be provisioned
    >> in ANIMA, uses GRASP M_DISCOVERY

    > Is it permissible for the Registrar to act as its own Join Assistant
    > for on-link neighbors? (I can't see why not.)

Yes, these are roles, not machines.

    >> 3) Join Assistant tentative admission control (used in 6tisch, to provide
    >> {optional?} "move along" feedback.).
    >> 6tisch, currently M_REQ_NEG/M_END over *TCP*, need to be fixed.
    >>
    >> 4) pledge <-> Registrar.
    >> in ANIMA, this is pledge---TCP/HTTPS---> Registrar (RFC7030)
    >> in 6tisch-zero-touch, this is Registrar ---CoAP/DTLS--> pledge [maybe EDHOC]
    >> (CoMI: draft-ietf-netconf-keystore-00 )
    >> in 6tisch-minimal-security, this is pledge-->CoAP/EDHOC--> Registrar
    >>

    > Thanks, a useful summary.

I'd like to give a name to each exchange.  BRSKI is clearly covers #4, but
arguably, it covers all four interactions, and #4 is the BRSKI mode of EST.



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

v2.23.0 | Report a Bug | By Email