Re: [6lo] draft-chairs-6lo-dispatch-iana-registry-00.txt

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 27 July 2015 00:58 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 287C91A8F50 for <6lo@ietfa.amsl.com>; Sun, 26 Jul 2015 17:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 EmlrtWOCGKuy for <6lo@ietfa.amsl.com>; Sun, 26 Jul 2015 17:58:43 -0700 (PDT)
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 CFA361A8F44 for <6lo@ietf.org>; Sun, 26 Jul 2015 17:58:42 -0700 (PDT)
Received: from sandelman.ca (dooku.dawson.sandelman.ca [IPv6:2607:f0b0:f:b:219:d2ff:fec0:9f1e]) by relay.sandelman.ca (Postfix) with ESMTPS id 194D322081 for <6lo@ietf.org>; Sun, 26 Jul 2015 20:58:41 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 87DB2627F1; Sun, 26 Jul 2015 17:31:44 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "6lo@ietf.org" <6lo@ietf.org>
In-reply-to: <99D8C20E-15F8-4F9E-9098-02EB5B510489@cisco.com>
References: <ECA43DA70480A3498E43C3471FB2E1F01C39990C@eusaamb103.ericsson.se> <CAO6tK45NVtbN4gON+fcQA=xzzV0Wd00Jqgo78i6LP5QV_j71Sg@mail.gmail.com> <ECA43DA70480A3498E43C3471FB2E1F01C39B48B@eusaamb103.ericsson.se> <CAO6tK474ga37g29Ope8XxsPB67iBpsSAsPhXqXfMcyvCm6_+xg@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD849F0A949@xmb-rcd-x01.cisco.com> <CADrU+d+syP9pGPnvLkhTNJXDKOA+SonF2Vrco93SfcYP85-SRQ@mail.gmail.com> <ECA43DA70480A3498E43C3471FB2E1F02222915D@eusaamb103.ericsson.se>, <CADrU+d+a-pE6cGQn9WXzxg8eJ-h2Cv73q6jXQ8ZrKMB3Y+WNFw@mail.gmail.com> <99D8C20E-15F8-4F9E-9098-02EB5B510489@cisco.com>
Comments: In-reply-to "Pascal Thubert (pthubert)" <pthubert@cisco.com> message dated "Tue, 21 Jul 2015 06:45:53 -0000."
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Sun, 26 Jul 2015 17:31:44 -0400
Message-ID: <11227.1437946304@dooku.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/6lo/f9hLP-7ZZNqNpwU_OA7KnRwx1jE>
Subject: Re: [6lo] draft-chairs-6lo-dispatch-iana-registry-00.txt
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2015 00:58:44 -0000

Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
    > My suggestions are:

    > - rename ESC to something like "Guest protocols" and carve space that
    > external entities can administer on their own, starting with ITU.

My understanding is that IANA will take care of the space, so I don't think
we should call it "guest" protocols; they are just (layer-2) "protocols"

    > - provide guidance on NALP before anyone uses it like ITU did with
    > ESC. My recommendation there would be the NALP is defined only when
    > used in the first octet of the payload to distinguish an alien
    > protocol. This will allow to reuse the dispatch space inside a 6lo
    > packet when we run out of space.

I am in favour of specifying rules before we need them, but not too far in
advance.  As such, I suggest that we establish IANA guidance for the space.

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