Re: appropriate length of fe80:: prefix and new IP-over-foo drafts
Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 31 January 2019 18:30 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 177B8130E7B for <ipv6@ietfa.amsl.com>; Thu, 31 Jan 2019 10:30:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] 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 l-uUsBEy3M3Q for <ipv6@ietfa.amsl.com>; Thu, 31 Jan 2019 10:30:48 -0800 (PST)
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 F1729130E78 for <ipv6@ietf.org>; Thu, 31 Jan 2019 10:30:47 -0800 (PST)
Received: from nephilia.intra.cea.fr (nephilia.intra.cea.fr [132.166.88.33]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x0VIUjlL047590; Thu, 31 Jan 2019 19:30:45 +0100
Received: from nephilia.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 9E5EE1C4212; Thu, 31 Jan 2019 19:30:45 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by nephilia.intra.cea.fr (Postfix) with ESMTP id 86C9D1C40CC; Thu, 31 Jan 2019 19:30:45 +0100 (CET)
Received: from [10.8.68.18] ([10.8.68.18]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x0VIUibh015922; Thu, 31 Jan 2019 19:30:44 +0100
Subject: Re: appropriate length of fe80:: prefix and new IP-over-foo drafts
To: 神明達哉 <jinmei@wide.ad.jp>
Cc: Fernando Gont <fgont@si6networks.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Mark Smith <markzzzsmith@gmail.com>, IPv6 IPv6 List <ipv6@ietf.org>, phessler@openbsd.org
References: <6d9657d0-803c-fcb2-ddb9-13f707bdfd47@gmail.com> <0af59661-ed8b-cd25-1125-468604edee53@gmail.com> <1df7d774-fe97-2feb-444a-94992cb89581@gmail.com> <CAJE_bqfVkFkvxVto67VGhjDK61ob6wxZXCRObtmwpr3GSyenfw@mail.gmail.com> <2def076d-b6bf-d84f-152b-d1d9277e9e73@gmail.com> <CAKQ4NaUW5-VY=TMjh0Ap01KTg4=An8=EXH_ej40nW=GM1kUL4w@mail.gmail.com> <c54b9702-1c6f-e5ae-971d-7d3ef443d994@gmail.com> <CAO42Z2wPAF6YCwsb+f0BXMEOKdFSiiFRNop=ChvKFPW32UepBA@mail.gmail.com> <e2a1a5c4-832f-744e-db69-2100c32fb59e@gmail.com> <c0d25c47-4684-8e1b-518d-2b00b41b9ed5@gmail.com> <6b712b9f-9a72-86a1-eab0-262b54962de8@si6networks.com> <62f2709f-5167-b884-d0e3-9a42d1eb4027@gmail.com> <207325ab-f42a-c775-459f-0c07ccc19116@si6networks.com> <6a91176d-5348-31c6-392f-a8ce03f161ab@gmail.com> <4472303b-6b60-b90d-6a24-ac98a8111e5c@si6networks.com> <86bd1106-1189-c2a2-eaa2-788818035c3b@gmail.com> <CAJE_bqfsO67Cju3nDfcXdS4L6OcOFWOCWJh4mDKPA1X6WDdiAw@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <38029735-a6fa-9f38-eaca-73ddf75881d0@gmail.com>
Date: Thu, 31 Jan 2019 19:30:43 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <CAJE_bqfsO67Cju3nDfcXdS4L6OcOFWOCWJh4mDKPA1X6WDdiAw@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/7TXZqaPeycjfCytSwDYrgBEVVLc>
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: Thu, 31 Jan 2019 18:30:51 -0000
Le 31/01/2019 à 18:43, 神明達哉 a écrit : > At Thu, 31 Jan 2019 14:00:04 +0100, > Alexandre Petrescu <alexandre.petrescu@gmail.com > <mailto:alexandre.petrescu@gmail.com>> wrote: > > > >> Ah? according to which spec do the BSD implementers put bits in the > > >> range 16-64? > > > > > > They don't send those bits on the wire. But they do use those bits as > > > described. -- According to no spec. If the link-local prefix is assumed > > > to be /64, then you're free to use those bits *internally* as you wish. > > > That's what BSDs do. Jinmei is quite likely in a better position ot > > > comment on this. > > > > I would like to kindly ask Jinmei to make sure to keep that internal > > such that to not forbid the end user to ifconfig add fe80:1::1/63 > > I don't think it's up to me anymore, but just to explain the current > state of art: > - an end user of a BSD box can't use fe80:1::1 as a "link-local" address > - BSD hosts generally drop incoming packets whose source or > destination address matches fe80::/10 and contains a non-0 value in > bits 15-31 (like fe80:1::1) > > Basically it doesn't allow an IPv6 address that matches fe80::/10 > unless it conforms to following format specified in RFC4291: > > 2.5.6. Link-Local IPv6 Unicast Addresses > > Link-Local addresses are for use on a single link. Link-Local > addresses have the following format: > > | 10 | > | bits | 54 bits | 64 bits | > +----------+-------------------------+----------------------------+ > |1111111010| 0 | interface ID | > +----------+-------------------------+----------------------------+ > > The BSD implementation conforms to the RFC. If someone wants to > violate the standard, they can freely do so, but they cannot assume > it's interoperable with other standard-compliant implementations. > That's a consequence of violating the standard. > > I previously stated I was already done with this discussion, so I'll > stop here. Anyone can freely hate this specification, but if it's not > even about an attempt of updating that specification (which is my > understanding of the previous cycle of this discussion), I don't think > it's a productive way of using my time to participate in it. jinmei, Thank you very much for the clarification. I appreciate it. Now I understand very much of our earlier discussions. This situation is extremely worth considering. In linux I must use fe80:1::1. In BSD I cant. Let us see how we can see further beyond the blocking situation. Alex > > -- > jinmei
- SLAAC RFC4862 - appropriate length of fe80:: pref… Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … 神明達哉
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Brian E Carpenter
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … 神明達哉
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Ole Troan
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Ole Troan
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Philip Homburg
- Re: RFC7217 'opaque and stable IIDs' Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Ole Troan
- Re: RFC7217 'opaque and stable IIDs' Ole Troan
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Philip Homburg
- Re: RFC7217 'opaque and stable IIDs' Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Ole Troan
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Philip Homburg
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Ole Troan
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: RFC7217 'opaque and stable IIDs' 神明達哉
- Re:interop - SLAAC RFC4862 - appropriate length o… Alexandre Petrescu
- Re: interop - SLAAC RFC4862 - appropriate length … Ole Troan
- Re: interop - SLAAC RFC4862 - appropriate length … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … 神明達哉
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Fred Baker
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Musa Stephen Honlue
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Dennis Ferguson
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Sander Steffann
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Ole Troan
- RE: SLAAC RFC4862 - appropriate length of fe80:: … Lubashev, Igor
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Mark Smith
- RE: SLAAC RFC4862 - appropriate length of fe80:: … Lubashev, Igor
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Yucel Guven
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Brian E Carpenter
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Yucel Guven
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Brian E Carpenter
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Fred Baker
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Ole Troan
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Ole Troan
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Yucel Guven
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Yucel Guven
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Sander Steffann
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Sander Steffann
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Sander Steffann
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Yucel Guven
- RE: SLAAC RFC4862 - appropriate length of fe80:: … Lubashev, Igor
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Yucel Guven
- RE: SLAAC RFC4862 - appropriate length of fe80:: … Lubashev, Igor
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Yucel Guven
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- RE: SLAAC RFC4862 - appropriate length of fe80:: … Lubashev, Igor
- RE: SLAAC RFC4862 - appropriate length of fe80:: … Lubashev, Igor
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Brian E Carpenter
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Yucel Guven
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Yucel Guven
- Re: SLAAC RFC4862 - appropriate length of fe80:: … 神明達哉
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Brian E Carpenter
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Matthew Petach
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Mark Smith
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Brian E Carpenter
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Ole Troan
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Simon Hobson
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Mark Smith
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Mark Smith
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Simon Hobson
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Fred Baker
- RE: SLAAC RFC4862 - appropriate length of fe80:: … Lubashev, Igor
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Brian E Carpenter
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Mark Smith
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Mark Smith
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Mark Smith
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Yucel Guven
- Re: SLAAC RFC4862 - appropriate length of fe80:: … 神明達哉
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- Re: SLAAC RFC4862 - appropriate length of fe80:: … Alexandre Petrescu
- appropriate length of fe80:: prefix and new IP-ov… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Mark Smith
- Re: appropriate length of fe80:: prefix and new I… Brian E Carpenter
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Fernando Gont
- Re: appropriate length of fe80:: prefix and new I… Fernando Gont
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Fernando Gont
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Fernando Gont
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… 神明達哉
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Brian E Carpenter
- Re: appropriate length of fe80:: prefix - new ver… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Brian E Carpenter
- Re: appropriate length of fe80:: prefix and new I… Gyan Mishra
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu
- Re: appropriate length of fe80:: prefix and new I… Gyan Mishra
- Re: appropriate length of fe80:: prefix and new I… Alexandre Petrescu