Re: about violation of standards

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 26 April 2019 09:17 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8043120389 for <ipv6@ietfa.amsl.com>; Fri, 26 Apr 2019 02:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.633
X-Spam-Level:
X-Spam-Status: No, score=-1.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] autolearn=no 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 bu9cwnF_UD5R for <ipv6@ietfa.amsl.com>; Fri, 26 Apr 2019 02:17:51 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 82A7F120312 for <ipv6@ietf.org>; Fri, 26 Apr 2019 02:17:37 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3Q9HZBg007604; Fri, 26 Apr 2019 11:17:35 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7A57C201FAF; Fri, 26 Apr 2019 11:17:35 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 68464201B05; Fri, 26 Apr 2019 11:17:35 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3Q9HZ86007192; Fri, 26 Apr 2019 11:17:35 +0200
Subject: Re: about violation of standards
To: ek@loon.com, Yucel Guven <yucel.guven@gmail.com>
Cc: IPv6 <ipv6@ietf.org>, 神明達哉 <jinmei@wide.ad.jp>
References: <bb7f7606-2adf-e669-8bcd-e41f17800782@gmail.com> <CAJE_bqd9frqX5-yeVPj8MYXpZ4737HqK1gmfD9cQV3A-Ea5HrQ@mail.gmail.com> <CAKQ4NaWLGh3f_dN6WVNnYs9fKL8=vfpnShAK8AczPo8LE8LjFA@mail.gmail.com> <43399e1f-d60a-f678-abf3-eb69defd962c@gmail.com> <CAKQ4NaUGvPxSOAD-+FTxcq3ghUkWbOwR82G-GAG9kDCT+gBzTQ@mail.gmail.com> <CAAedzxo+5J=f1sf+gEJXm+aN7AJJUgasxsBd36JYm6GuuFfi=w@mail.gmail.com> <CAKQ4NaVwzE2-D2nxAqh4-W15MwfLEwYTrYA-VXpnXz56LLgBnQ@mail.gmail.com> <CAAedzxowiMaY2W8cjSD8NmeJg48G_h7+0u5Hi3QPSMtO4zfZwQ@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <79d20d30-3e91-f36b-371d-0f95472341b1@gmail.com>
Date: Fri, 26 Apr 2019 11:17:35 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CAAedzxowiMaY2W8cjSD8NmeJg48G_h7+0u5Hi3QPSMtO4zfZwQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vJXWWKH93Ap5CEuOGYNlT6sVJEM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2019 09:17:53 -0000


Le 25/04/2019 à 18:46, Erik Kline a écrit :
> I not sure I see any standards violation and therefore I don't see any 
> need to update any standards.

Let me show this: RFC4291 requires 54 0 bits between fe80::/10 and 
fe80::IID/64.

Do you see a problem in this?

> Every interface had the default link-local prefix assigned (fe80::/64).  
> No problem.

Right.

> Every interface also had another prefx, fe80:ifindex::/64, configured.  

ifindex is the Interface Index?

I need the Subnet ID there, not the Interface Index.

The Interface Index of eth1 on a PC is '1' and distinct than the 
Interface Index of eth2 on another PC, both in same Ethernet.

One couldnt ping fe80:1::1/64 from fe80:2::1/64 on the same Ethernet cable.

Alex

> This prefix is also link-local because it's from within fe80::/10.
> 
> I see no problem here.  I don't see that any standards need to be 
> updated, bis'ed, amended, or tweaked.

> 
> On Thu, 25 Apr 2019 at 08:05, Yucel Guven <yucel.guven@gmail.com 
> <mailto:yucel.guven@gmail.com>> wrote:
> 
>     Nothing prevents me, I'm sure it also works with other linux
>     distributions.
> 
>     But, do you mean that it worked in your linux,
>     and in fact "RFC is not compatible" with your machine's OS?
> 
>     Then;
>     What prevents you from opening your word processor
>     and from proposing/writing your ideas
>     into a document that is called a 'draft'?
> 
>