IETF Logo Mail Archive

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

Michael Richardson <mcr@sandelman.ca> Sun, 13 November 2016 23:08 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: 6tisch-security@ietfa.amsl.com
Delivered-To: 6tisch-security@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33E701296A9; Sun, 13 Nov 2016 15:08:36 -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 VVcoQ-4kD2yd; Sun, 13 Nov 2016 15:08:34 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DCDA1296A8; Sun, 13 Nov 2016 15:08:26 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [182.172.168.109]) by relay.sandelman.ca (Postfix) with ESMTPS id DC6FD1F906; Sun, 13 Nov 2016 23:08:24 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 8B7DE321D; Sun, 13 Nov 2016 18:08:21 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-reply-to: <12808a8a-5de1-c6cb-3f96-945573041ee4@gmail.com>
References: <20351.1476971471@obiwan.sandelman.ca> <0343d14c-5b18-b821-c9ad-d77fb7dae490@gmail.com> <12808a8a-5de1-c6cb-3f96-945573041ee4@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Thu, 27 Oct 2016 14:00:44 +1300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <24909.1479078501.1@dooku.sandelman.ca>
Date: Mon, 14 Nov 2016 08:08:21 +0900
Message-ID: <24910.1479078501@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch-security/pwgiC8262Sx51x350_AdRjV-MOs>
Cc: anima-bootstrap <anima-bootstrap@ietf.org>, 6tisch-security <6tisch-security@ietf.org>
Subject: Re: [6tisch-security] [Anima-bootstrap] 6tisch join -01 documented posted
X-BeenThere: 6tisch-security@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Extended Design Team for 6TiSCH security architecture <6tisch-security.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch-security>, <mailto:6tisch-security-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch-security/>
List-Post: <mailto:6tisch-security@ietf.org>
List-Help: <mailto:6tisch-security-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch-security>, <mailto:6tisch-security-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Nov 2016 23:08:36 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > My model was that the proxy would get all the floods available and
    > choose the one it liked best, based on the available method and
    > distance, using the weight and priority as for mDNS. (Personally I
    > think the mDNS stuff is overkill, but Toerless suggested we should be
    > feature-equivalent.)

I never proposed that the Proxy would learn of the registrar via mDNS, btw.

    > 2. Your CDDL looks OK to me. The format and semantics of the value
    > field of a GRASP objective are completely flexible, so I don't see a
    > problem with the first "request" to the Registrar being [IID,
    > join-method]. The reply from the registrar could be [IID,
    > another-join-method] if it didn't like the first one proposed. Once
    > either side receives a join-method it likes, it would send
    > [M_END,,[O_ACCEPT]] and we're done.

    > 3. Mini-question, is this really IPv6-specific? If not I'd prefer a
    > name that flags it as an AN infrastructure objective, e.g. "AN_Join"

okay.  The problem in 6tisch for proxy<->registrar communication (admission
control) is the TCP stack required.

v2.23.0 | Report a Bug | By Email