IETF Logo Mail Archive

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

Paul Duffy <paduffy@cisco.com> Mon, 27 July 2015 12:06 UTC

Return-Path: <paduffy@cisco.com>
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 C87E51B2C4A for <6lo@ietfa.amsl.com>; Mon, 27 Jul 2015 05:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 DuKSDSmOUOJT for <6lo@ietfa.amsl.com>; Mon, 27 Jul 2015 05:06:42 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84DD41A90AD for <6lo@ietf.org>; Mon, 27 Jul 2015 05:06:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5898; q=dns/txt; s=iport; t=1437998802; x=1439208402; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to; bh=yrWAPQRuzCia6IsGpvpWl3JQ04+sftTrBW1L6riRuXw=; b=VroMZiz9mPDRylSadOtwGIiImENAQm92ua88NY+DHmheGvGTTZVZRLRu IEBiNqIybGeMB22OsyGEwgRWen2lkXWIMahKWM3Jo/RcdUkSOZCFToJzD wh3ksQX5ELw5DWnQswNiwtY2iBFvCirsq+xUzMFghQGvJLFeZ5jj875EX Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BJAwAoHrZV/49dJa1bgxVUabwXCYFtAQmCQ4M2AoE5OBQBAQEBAQEBgQqEJAEBBAEBAWsKEQsYCRYIBwkDAgECARUfERMGAgEBiCoNwRSPAQEBAQEBBQEBAQEaBItOhQ4XhBUFlGmMQYhSkFQmhBkiMYJMAQEB
X-IronPort-AV: E=Sophos;i="5.15,553,1432598400"; d="scan'208,217";a="172850212"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 27 Jul 2015 12:06:41 +0000
Received: from [10.86.241.22] (che-vpn-cluster-1-277.cisco.com [10.86.241.22]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t6RC6fGG016725 for <6lo@ietf.org>; Mon, 27 Jul 2015 12:06:41 GMT
Message-ID: <55B61ED0.3040202@cisco.com>
Date: Mon, 27 Jul 2015 08:06:40 -0400
From: Paul Duffy <paduffy@cisco.com>
Organization: Cisco Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: 6lo@ietf.org
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> <OF61676A88.654202A5-ONC1257E8A.00367D84-C1257E8A.00373682@notes.edfgdf.fr> <5B0B0A9D-5EEC-45B6-BA84-DD2C871A3C4B@gmail.com> <CAO6tK450n1RqTEnrSrHBUacxmesjBc73C=WEckbwLszWD94Oqw@mail.gmail.com> <11308.1437946470@dooku.sandelman.ca> <CADrU+dLXY7f5jLB4eQ16j-6R2JXSwavfW0DtRCow1ejRLBg9eQ@mail.gmail.com>
In-Reply-To: <CADrU+dLXY7f5jLB4eQ16j-6R2JXSwavfW0DtRCow1ejRLBg9eQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------060405030303070403060002"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6lo/l3KRw3bZWBOl_oO1hBZMcSFLMIw>
Subject: Re: [6lo] draft-chairs-6lo-dispatch-iana-registry-00.txt
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: paduffy@cisco.com
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 12:06:46 -0000

+1

On 7/27/2015 5:48 AM, Robert Cragie wrote:
> Hi Michael,
>
> I think Jonathan's recommendation is the right one. Most importantly, 
> the uses as defined in G.9903 or G.9905 are not related to 6LoWPAN in 
> any way as broadly speaking they are command frames for a mesh-under 
> protocol. For that reason, I would say that "private use" is actually 
> quite appropriate and highlights the fact that NALP frames should 
> probably have been used here.
>
> Robert
>
> On 26 July 2015 at 22:34, Michael Richardson <mcr+ietf@sandelman.ca 
> <mailto:mcr+ietf@sandelman.ca>> wrote:
>
>
>     Jonathan Hui <jonhui@nestlabs.com <mailto:jonhui@nestlabs.com>> wrote:
>         > If we designate the relevant ESC region as for Private Use
>     (possibly
>         > with a note that ITU-T makes use of that range), then there
>     is no need
>         > to provide further description of their use.
>
>     I don't think that "Private Use" in an appropriate description of
>     how ITU-T
>     uses this space.   Private Use means that I use it for my own network,
>     and I never tell anyone else about how/when I use it.
>     In particular, I don't write specifications for others to follow.
>
>
>     --
>     Michael Richardson <mcr+IETF@sandelman.ca
>     <mailto:mcr%2BIETF@sandelman.ca>>, Sandelman Software Works
>      -= IPv6 IoT consulting =-
>
>
>
>
>     _______________________________________________
>     6lo mailing list
>     6lo@ietf.org <mailto:6lo@ietf.org>
>     https://www.ietf.org/mailman/listinfo/6lo
>
>
>
>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo

v2.23.0 | Report a Bug | By Email