[6tisch-security] IP-IP-IP example?
Thomas Watteyne <thomas.watteyne@inria.fr> Tue, 28 March 2017 15:16 UTC
Return-Path: <thomas.watteyne@inria.fr>
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 08F93128B88; Tue, 28 Mar 2017 08:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 xbchvcsHQueb; Tue, 28 Mar 2017 08:16:31 -0700 (PDT)
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8071D1289C3; Tue, 28 Mar 2017 08:16:30 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.36,236,1486422000"; d="scan'208,217";a="266587654"
Received: from mail-vk0-f45.google.com ([209.85.213.45]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 28 Mar 2017 17:16:28 +0200
Received: by mail-vk0-f45.google.com with SMTP id r69so91824403vke.2; Tue, 28 Mar 2017 08:16:28 -0700 (PDT)
X-Gm-Message-State: AFeK/H2UEZLQMhVbQsoJc+AMUYUj7XGzC2hv5oo3v6hVn9mh7FVly7koBNv8MuPAwZV6n02F+EdccoBabodAOw==
X-Received: by 10.31.73.6 with SMTP id w6mr6369016vka.137.1490714187087; Tue, 28 Mar 2017 08:16:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.194.149 with HTTP; Tue, 28 Mar 2017 08:16:06 -0700 (PDT)
From: Thomas Watteyne <thomas.watteyne@inria.fr>
Date: Tue, 28 Mar 2017 17:16:06 +0200
X-Gmail-Original-Message-ID: <CADJ9OA-PTtq6yMUjhOAyOngcrbDd-YEpOu_UOfFWTD8=csNHGQ@mail.gmail.com>
Message-ID: <CADJ9OA-PTtq6yMUjhOAyOngcrbDd-YEpOu_UOfFWTD8=csNHGQ@mail.gmail.com>
To: "6tisch@ietf.org" <6tisch@ietf.org>, "6tisch-security@ietf.org" <6tisch-security@ietf.org>
Content-Type: multipart/alternative; boundary="001a114db10a954ac8054bcbf154"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch-security/AFmmSO7U_Ao3SSNsY_w5zUmT__w>
Subject: [6tisch-security] IP-IP-IP example?
X-BeenThere: 6tisch-security@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 28 Mar 2017 15:16:33 -0000
Michael, We just discussed IP-IP-IP versus CoAP at the 6TiSCH WG meeting. I stated that: - with IP-IP-IP, all nodes in the network would need to know at least the global and link-local IPv6 addresses of the JRC, as well as the IPv6 address of the LBR. - With the CoAP proxy option, we could use (well-known?) 6LoWPAN contexts and hostnames to avoid that. You stated that my statement 1 was not correct. Could we draw up an example with all the addresses in the IP-IP-IP case, and what exactly the Pledge and Join Proxy need to know before being able to join? Thanks, Thomas
- [6tisch-security] IP-IP-IP example? Thomas Watteyne
- Re: [6tisch-security] IP-IP-IP example? Michael Richardson
- Re: [6tisch-security] IP-IP-IP example? Michael Richardson
- Re: [6tisch-security] [6tisch] IP-IP-IP example? Göran Selander