Re: [6lo] mic comment about layers

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 20 July 2015 19:04 UTC

Return-Path: <alexandru.petrescu@gmail.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 2660E1B303F for <6lo@ietfa.amsl.com>; Mon, 20 Jul 2015 12:04:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 2sZV-Phv2zad for <6lo@ietfa.amsl.com>; Mon, 20 Jul 2015 12:04:08 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF2C61B3025 for <6lo@ietf.org>; Mon, 20 Jul 2015 12:03:58 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t6KJ3sXQ002788; Mon, 20 Jul 2015 21:03:54 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0C9EA205225; Mon, 20 Jul 2015 21:07:27 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 012EC2050AF; Mon, 20 Jul 2015 21:07:27 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.87]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t6KJ3oN2030647; Mon, 20 Jul 2015 21:03:53 +0200
To: Kerry Lynn <kerlyn@ieee.org>
References: <55AD2FE5.8040602@gmail.com> <CABOxzu1H-Qq0eO1xCxXs6MmMwwhBaVNTnsDd3-UJNZ_VSt7zjA@mail.gmail.com> <55AD3227.6040208@gmail.com> <CABOxzu3JY++zbbqY_XQPC0jfq1fTkzuo8RfqxoZp=p19D6APmg@mail.gmail.com>
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Message-ID: <55AD4615.1020404@gmail.com>
Date: Mon, 20 Jul 2015 21:03:49 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <CABOxzu3JY++zbbqY_XQPC0jfq1fTkzuo8RfqxoZp=p19D6APmg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/6lo/oHk1KRd6HoqC2PvRCpR9MT_zKjw>
Cc: "6lo@ietf.org" <6lo@ietf.org>
Subject: Re: [6lo] mic comment about layers
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, 20 Jul 2015 19:04:10 -0000


Le 20/07/2015 19:47, Kerry Lynn a écrit :
> On Mon, Jul 20, 2015 at 1:38 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>>
> wrote:
>
>
>
> Le 20/07/2015 19:34, Kerry Lynn a écrit :
>
> On Mon, Jul 20, 2015 at 1:29 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>
> <mailto:alexandru.petrescu@gmail.com
> <mailto:alexandru.petrescu@gmail.com>>> wrote:
>
> Hello,
>
> I wanted to make a comment at the mic about layering, during the IANA
> registry discussion.
>
> As I hear the discussion about liaison with ITU, it looks to me as a
> ping-pong of statements.
>
> Who is responsible to allocate these codepoints - IANA or ITU?
>
> Even if IANA makes a registry for it, are we sure that ITU will not
> allocate in the future other codepoints beyond what IANA allocates?
> And, should we care?
>
> My oppinion on this is that IANA should not allocate numbers to
> whatever runs below IPv6 headers.
>
> http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtml
>
>
>
> That is a reflection of what IEEE controls.  It's IEEE who controls,
> and IANA 'mirrors' it.
>
> <kel> Yes, sorry - I should have provided more context.  It seems
> there's a well defined process [RFC 7042] for coordination between
> IEEE and IETF and expert review is required.  Perhaps something
> similar can be worked out in this case. </kel>

I agree with that RFC mentioning, thanks.

But the advancement doesnt look promissing to me.  Let me say why.

Ralph (liaison, all due respect), expressed that ITU requested an answer
in 1week time. (IMHO and not only mine this is way too short to figure
out in a consensual way).  And proposed an answer saying (1) future IANA
allocations do not break G-9x specs and (2) to be figured out.

Somebody with ITU experience said G-990_5_ should be considered as well,
that _5_ seemed to be a surprise to the group.

At this point, it is not clear what is (2) in Ralph's thinking.  And it
is not clear - in case IANA creates registry - whether or not ITU agrees
that IANA takes control of this space.

I think we could try to agree whether or not we should state upfront
that this is not under the authority of IANA.  My personal oppinion is
to let ITU take control of it.  This is a matter below IP.

In that sense, ITU may make a requirement on IEEE to write a MAC layer,
over which, in the end, IP could run.

I really dont think it is an IETF's group's business (any other than
6man WG) to control and redefine IPv6 and all the layers below it.

Yours,

Alex

> I dont have the same feeling that the same happens between ITU and
> 6lo here.  It looks more like a competition between who allocates
> what.  The format of it is not agreed either.
>
> And - worse - the 6lo WG does not seem to be queried oppinion, but
> imposed decisions.
>
> This is not a way to move forward, I fully disagree.
>
> Alex
>
>
>
> Let the underlying layers (below IP) offer IEEE-like interfaces, with
> EtherTypes.  That's what works.
>
> Alex
>
>
> _______________________________________________ 6lo mailing list
> 6lo@ietf.org <mailto:6lo@ietf.org> <mailto:6lo@ietf.org
> <mailto:6lo@ietf.org>> https://www.ietf.org/mailman/listinfo/6lo
>
>
>
>