IETF Logo Mail Archive

Re: [6tisch-security] [6tisch] transporting Router Advertisements in Extended Beacons: draft-richardson-6lo-ra-in-ie

Thomas Watteyne <thomas.watteyne@inria.fr> Mon, 24 October 2016 22:44 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 8B459129ADD; Mon, 24 Oct 2016 15:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.33
X-Spam-Level:
X-Spam-Status: No, score=-7.33 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.431] 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 yVwHM-qCcPY0; Mon, 24 Oct 2016 15:44:39 -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 782AC129ACF; Mon, 24 Oct 2016 15:44:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.31,543,1473112800"; d="scan'208,217";a="242167228"
Received: from mail-wm0-f46.google.com ([74.125.82.46]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 25 Oct 2016 00:44:36 +0200
Received: by mail-wm0-f46.google.com with SMTP id d199so14038586wmd.0; Mon, 24 Oct 2016 15:44:37 -0700 (PDT)
X-Gm-Message-State: ABUngvc2grMmHRALBh1xfyf9C7yNGmYjKYhGpxy7f3S3ptuA1INfqj6BFKRbF0WlWrTsEs0E1JG5cRLuv3o14g==
X-Received: by 10.194.78.195 with SMTP id d3mr99384wjx.96.1477349076882; Mon, 24 Oct 2016 15:44:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.179.19 with HTTP; Mon, 24 Oct 2016 15:44:16 -0700 (PDT)
In-Reply-To: <11163.1476884967@obiwan.sandelman.ca>
References: <147680041580.30853.17692159482786173917.idtracker@ietfa.amsl.com> <12199.1476807186@obiwan.sandelman.ca> <11163.1476884967@obiwan.sandelman.ca>
From: Thomas Watteyne <thomas.watteyne@inria.fr>
Date: Tue, 25 Oct 2016 00:44:16 +0200
X-Gmail-Original-Message-ID: <CADJ9OA8AVTSDvtAg+WqEHcrfi5aGCXR2OGouZuu+W+GQQi3ymA@mail.gmail.com>
Message-ID: <CADJ9OA8AVTSDvtAg+WqEHcrfi5aGCXR2OGouZuu+W+GQQi3ymA@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="047d7bfd0010efe04c053fa422c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch-security/EYcV4dwYBebSTL6R5n-Et0oiR2s>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, "6tisch-security@ietf.org" <6tisch-security@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
Subject: Re: [6tisch-security] [6tisch] transporting Router Advertisements in Extended Beacons: draft-richardson-6lo-ra-in-ie
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: Mon, 24 Oct 2016 22:44:42 -0000

Michael,

Cool! Some editorial remarks:

OLD
extended beacon
NEW
enhanced beacon

Could the draft be generic enough to allow for RPL DIOs to be carried in an
EB?



On Wed, Oct 19, 2016 at 3:49 PM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> to reply to myself
>
> Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>     > This will contain a copy of the 16-byte DODAGID so that a very sleepy
>     > node returning to operation would be able to identify which beacon
>     > belongs to which network.  A joining node will have no idea which
>     > DODAGID it wants, and a maliciously sent beacon could have any manner
>     > is superfuge here.  Nodes which have already joined the network
> SHOULD
>     > be able to authenticate the beacons.  However, this is one of the
>     > larger objects in the 56 bytes that I describe, and maybe it is
>     > excessive to store so many bytes here.
>
> I realized today that the RA probably also needs to carry the ABRO to be
> useful to secured hosts.  Such hosts will still have to unicast as RS to
> get
> the PIO from a router.  I'm sure that we don't want to put the PIO into an
> unencrypted EB/RA.
>
> The ARBO has the 6LBR address which is often, but not always the same as
> the
> DODAGID.   It can equally well be used to identify the network.
>
>     > I want to attempt to apply RFC7400 (GHC) to this, the savings will be
>     > probably on the order of ten bytes of zeroes.
>
> So far, the savings I got with GHC was 4 bytes.  I posted an update to the
> git repo.  (     https://github.com/ietf-roll/6lo-ra-in-ie )
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch
>
>


-- 
_______________________________________

Thomas Watteyne, PhD
Research Scientist & Innovator, Inria
Sr Networking Design Eng, Linear Tech
Founder & co-lead, UC Berkeley OpenWSN
Co-chair, IETF 6TiSCH

www.thomaswatteyne.com
_______________________________________

v2.23.0 | Report a Bug | By Email