Re: [6tisch] Optimizing Neighbor Discovery during the join process

Michael Richardson <mcr@sandelman.ca> Tue, 24 April 2018 19:56 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E670612D940 for <6tisch@ietfa.amsl.com>; Tue, 24 Apr 2018 12:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 iC3NLY1iTYD3 for <6tisch@ietfa.amsl.com>; Tue, 24 Apr 2018 12:56:23 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B04A12D87B for <6tisch@ietf.org>; Tue, 24 Apr 2018 12:56:23 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 45BE520091 for <6tisch@ietf.org>; Tue, 24 Apr 2018 16:07:21 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 216EE25F0; Tue, 24 Apr 2018 15:56:17 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 1F2DC25EC for <6tisch@ietf.org>; Tue, 24 Apr 2018 15:56:17 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: "6tisch@ietf.org" <6tisch@ietf.org>
In-Reply-To: <95a2f6bc762e4525a4cc3e1346e4c13a@XCH-RCD-001.cisco.com>
References: <CANDGjydvR4LOKeeHFhCyPJD0oxEuvPmr9PAscynvdMP=wN+M4Q@mail.gmail.com> <29874.1524068339@obiwan.sandelman.ca> <CANDGjycEV0MubBrdnMhOQnnT1-880zEtwhF9ksYXqLGYtW2vtg@mail.gmail.com> <13313.1524071815@obiwan.sandelman.ca> <CANDGjydvR78KfSFMMDHB+qZMCYKkYhptNbbm06L8vSRG5xwgZA@mail.gmail.com> <1619f902f03a430dae00b41835f7753c@XCH-RCD-001.cisco.com> <30356.1524159468@obiwan.sandelman.ca> <3715ef0239e84dc2a132a526ad272f2c@XCH-RCD-001.cisco.com> <28684.1524247107@obiwan.sandelman.ca> <95a2f6bc762e4525a4cc3e1346e4c13a@XCH-RCD-001.cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+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: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 24 Apr 2018 15:56:17 -0400
Message-ID: <18664.1524599777@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/2R2KDhIc2_R9FM9-9ilsPPDxmkI>
Subject: Re: [6tisch] Optimizing Neighbor Discovery during the join process
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2018 19:56:25 -0000

Diff: https://www.ietf.org/rfcdiff?url2=draft-richardson-6tisch-enrollment-enhanced-beacon-01

Pascal, Mališa, I have made the following changes to the Enhanced beacon draft:

                         1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |   TBD-XXX     |R|P| res |  proxy prio |    rank priority      |
    +-+-+-+-+-+-+-+-+-+-------------+-------------+-----------------+
    | pan priority  |                                               |
    +---------------+                                               +
    |                           Join Proxy lower-64                 |
    +                        (present if P=1)                       +
    |                                                               |
    +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |               |                                               |
    +-+-+-+-+-+-+-+-+                                               +
    |                           network ID                          |
    +                   variable length, up to 16 bytes             +
    ~                                                               ~
    +                                                               +
    |                                                               |
    +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |               |
    +-+-+-+-+-+-+-+-+


Perhaps someone can come up with a better description than "lower-64".
I guess maybe IID would appropriate?
I also changed the networkID to be variable length, up to 16 bytes as
we discussed in person.
I have again changed the number of bits allocated to rank priority.

What I hope is that by moving this stuff out of 6tisch-minimal security,
offering the optimization to get rid of the ND process in a 802.15.4 specific document, 
that the 6tisch-minimal-security can remain mute about this.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [