[ipwave] IPv6-over-foo and Addressing Architecture (was Re: [Int-dir] Intdir early review of draft-ietf-ipwave-ipv6-over-80211ocb-34 - options for fe80::/10 vs fe80::/64)

Suresh Krishnan <Suresh@kaloom.com> Thu, 11 April 2019 13:26 UTC

Return-Path: <Suresh@kaloom.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8862E12029F; Thu, 11 Apr 2019 06:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kaloom.com
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 gSV8_eq3YHHS; Thu, 11 Apr 2019 06:26:44 -0700 (PDT)
Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670124.outbound.protection.outlook.com [40.107.67.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD98512028A; Thu, 11 Apr 2019 06:26:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kaloom.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=L7kq69D8pwcAFRKBEKFgM3R8Orb0mfFAPEzrODc/E9w=; b=pqONiZFZ7u1U7EmjtcOuT1k0IEdlOwHBu1h6q/lalVfke37QquoP7t1zMuE2T5RIbrTTvOjmVgSVRQkBXu/vy0lKdszUcIY1RcuFp2hTVRvV7CbXGF6J29lMtdOFBU9eDSmVdsQ8Ekhb8ndrr6b+e0wX1AZ/tNYx9EEXSQqz+eY=
Received: from YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM (52.132.44.159) by YTOPR0101MB2218.CANPRD01.PROD.OUTLOOK.COM (52.132.49.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.16; Thu, 11 Apr 2019 13:26:41 +0000
Received: from YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM ([fe80::7d75:b044:39b8:d47e]) by YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM ([fe80::7d75:b044:39b8:d47e%5]) with mapi id 15.20.1771.016; Thu, 11 Apr 2019 13:26:41 +0000
From: Suresh Krishnan <Suresh@kaloom.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
CC: Ole Troan <otroan@employees.org>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, "its@ietf.org" <its@ietf.org>, "int-dir@ietf.org" <int-dir@ietf.org>, 神明達哉 <jinmei@wide.ad.jp>, "draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org" <draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: IPv6-over-foo and Addressing Architecture (was Re: [Int-dir] Intdir early review of draft-ietf-ipwave-ipv6-over-80211ocb-34 - options for fe80::/10 vs fe80::/64)
Thread-Index: AQHU8GozwhWthi0jE0OSfC2zXKNnSA==
Date: Thu, 11 Apr 2019 13:26:41 +0000
Message-ID: <7AC9CCFC-278E-4B8A-A992-056D9C3F57EB@kaloom.com>
References: <155169869045.5118.3508360720339540639@ietfa.amsl.com> <94941ef0-d0df-e8fe-091b-2e616f595eba@gmail.com> <c052e7a9-9acd-ecdd-9273-3142644dc5cd@gmail.com> <386b9f4c-f9b5-900c-817a-95df68226ed9@gmail.com> <cc9564f5-b049-fa99-31a4-98a9c9c1261a@gmail.com> <856F277E-8F26-48BC-9C57-70DC61AA4E06@employees.org> <c91328aa-72e4-c0be-ec86-5bfd57f79009@gmail.com> <1BF2A47E-3672-462B-A4EC-77C59D9F0CEA@employees.org> <2ba71d54-8f2f-1681-3b2a-1eda04a0abf9@gmail.com> <B618E1B8-1E01-4966-97B2-AAF5FC6FE38A@employees.org> <bf83d3c2-a161-310f-98f4-158a097314a6@gmail.com> <D1A09E57-11E2-4FBC-8263-D8349FBFB454@employees.org> <MN2PR11MB3565A36F02B010B12E709ABED82E0@MN2PR11MB3565.namprd11.prod.outlook.com> <39c49adc-65b2-bfa8-4f97-b1216d7a71a4@gmail.com> <CAJE_bqf0+JjX81TeoqmirgKw4KnHoJdkCmgBx0nfu+-OeWPP3A@mail.gmail.com> <c878f52b-2ce9-7a83-5867-38d7565cd0f2@gmail.com> <c59e6e7a-0adb-7d24-50e7-3ffda6013ad5@cea.fr> <6601B81C-80E4-4CD4-8F4D-627B4208F151@employees.org> <5fbbad0e-cd27-2017-36ec-de8da1a5a9f0@gmail.com>
In-Reply-To: <5fbbad0e-cd27-2017-36ec-de8da1a5a9f0@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Suresh@kaloom.com;
x-originating-ip: [45.19.110.76]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 531637b8-95d2-4a4c-bcc1-08d6be81559e
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:YTOPR0101MB2218;
x-ms-traffictypediagnostic: YTOPR0101MB2218:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <YTOPR0101MB221808F9B20F5E59FD367CF3B42F0@YTOPR0101MB2218.CANPRD01.PROD.OUTLOOK.COM>
x-forefront-prvs: 00046D390F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(366004)(346002)(39840400004)(396003)(376002)(43544003)(199004)(189003)(105586002)(72206003)(316002)(26005)(186003)(6506007)(102836004)(53546011)(93886005)(25786009)(486006)(476003)(11346002)(2616005)(3846002)(6116002)(6306002)(106356001)(80792005)(81166006)(53936002)(97736004)(33656002)(8936002)(81156014)(2906002)(36756003)(66066001)(6512007)(446003)(76176011)(6486002)(6436002)(14454004)(4326008)(5660300002)(8676002)(6916009)(71190400001)(68736007)(71200400001)(83716004)(7736002)(256004)(305945005)(14444005)(966005)(99286004)(508600001)(54906003)(86362001)(66574012)(82746002); DIR:OUT; SFP:1102; SCL:1; SRVR:YTOPR0101MB2218; H:YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: kaloom.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Fe7BPpFmGBj8NsRom8X0biIaYMxLBj/+FF8k1M+Blnd5o/cUb7C0sljbGJYxRNZYyK37QOHEUW3faVFU5Rf8c5YkFLiJWD1mey6A0xWTFr0fmmMjQR9Mq1Y3akIV5HvPvAtDkAxkiM0J+9Zi+FDscKf0ZPOShQxnL47MGS2O7NYuj9nGf2qwjosB37egpVocx1d6RpHLx9SD6ph5eMY4Hep4ZQ2VcQMGLw/zN6YIv/CnQ0g7owbe5S4+fBO5I5GG98y63IySmBp/qbdXOZx+Qi88Qk8KUQ7+HKIKiU77Q7todoAhtmtLW2z5CB31C2SLgsBrbwHo2EDRsArq+XdtzzOCrDDEwI1j1DJkxfKRi2K/nujtO3c3xfNGbf7rxFQIebGLqM4xoBqdGY7JUonIxlMjUw7e098N8SgKHctL4PU=
Content-Type: text/plain; charset="utf-8"
Content-ID: <99C4F0BF73B1FA47A475F596749B4B6C@CANPRD01.PROD.OUTLOOK.COM>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: kaloom.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 531637b8-95d2-4a4c-bcc1-08d6be81559e
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2019 13:26:41.4637 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 47d58e26-f796-48e8-ac40-1c365c204513
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB2218
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/BylnM7A5yWjI15m8aqNNKvCpnC8>
Subject: [ipwave] IPv6-over-foo and Addressing Architecture (was Re: [Int-dir] Intdir early review of draft-ietf-ipwave-ipv6-over-80211ocb-34 - options for fe80::/10 vs fe80::/64)
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2019 13:26:47 -0000

Hi Alex,

> On Apr 11, 2019, at 7:53 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
> 
> Le 11/04/2019 à 13:38, Ole Troan a écrit :
>>>>> I actually don't know if "this ipv6-over-80211ocb spec needs
>>>>> to rely on the use of a non-0 value in the intermediate 54
>>>>> bits", btw. If that's not the case, it's much safer and less
>>>>> controversial to just not mention it (either in the form of "LL
>>>>> prefix length" or more explicitly).  I guess that's also what
>>>>> others are suggesting (and I agree with them in that sense).
>>> There is the option of being silent about the prefix length of IPv6
>>> LLs in the IPv6-over-OCB document.
>>> There is the option of mentioning "fe80::/10", but with "Updates
>>> 4291 section X" in the header of the 1st page.
>>> There is the option of proving by implementation that fe80:1::1/32
>>> on OCB is not harmful to others.
>> Two of these options will likely prohibit consensus being reqched on
>> this document. I encourage you to carefully consider how to best
>> spend your time and the time of the particpants in the involved set
>> of working groups.
> 
> YEs, thank you for the advice Ole.  I need to take care how to spend my time.  Maybe try to avoid taking on directions that are known to be dead ended.
> 
> I read your message as a warning that I take seriously.  For that, I would like to ask you whether you make this suggestion as a WG Chair of 6man WG?  Or as a contributor to other WGs?

<AD Hat On>
I would like to look at this from a different angle. It is clear from the current standards that you need to be using fe80::/64 to form the LL address as the IPv6 address architecture requires the IID to be 64 bits long (for non b000 prefixes) and SLAAC requires the prefix and the IID lengths to add up to 128. If you want this changed, I don’t think this is the document where you should do it. The *burden of proof is on you* to show why the status quo does not work in this case and IMHO it has not been meet. 

I would request that you keep the link-local prefix length discussion out of this draft, and in 6man where it belongs. Here is the thread that you started in January this year in 6man

https://mailarchive.ietf.org/arch/msg/ipv6/SD0OSOxFe9UGExX84u_CQSdfOsM

and the associated draft

https://datatracker.ietf.org/doc/draft-petrescu-6man-ll-prefix-len/

If you wish to pursue this topic further, please do so with *that* draft. An IP-over-foo document is not a place to do such a major architectural change.

Thanks
Suresh