Re: SAILing LAPs

[David Farmer <[e-mail]>]

On Wed, Jun 20, 2018 at 7:23 AM, Alexandre Petrescu <
[e-mail]> wrote:
...

> We know BSD implements various lengths for IIDs, including 64 and 63, for
> SLAAC.
>

Unfortunatly, this is not a good thing, this a rogue inplementation in my
opinion. However, this a symptom of a bigger problem as I see it; the
current way we IPv6 specifys this is not well understood by most
implementers or operators. SLAAC [RFC4862] and ND[RRFC4861] are seemingly
in conflic with the Addressing Archeture [RFC4291] and I belive because it
is not explaine well. Making the overall situation incomprehensible to most
people, this is what I want to fix, not changing the 64-bit boundry.

We also know linux kernel does not support any other length than 64.  An
> effort of a kernel programmer of approximately 3 days could not make linux
> kernel accept plen 65 and self-configure an address.  I am still looking
> for someone for help.
>

This is partually becase how to intrupret staticly configure IPv6 addresss
was not clearly defined, BSD and other early implementations alloed any
prefix length to be statically configured, I think because thier
implementations began before 64-bit was landed on as the boundry, and most
implementations just coppied BSD.  This is why I wnat to see a clear
execption for staticlly defined addresses with any length of subnet and
therefore IID.  Otherwise many if not most implementations of not in
compliance with IPv6's specifications. Again part of the confusion people
have.

Alternatively, this IoT Router's Qualcomm modem does not _want_ to allow
> DHCPv6 Prefix Delegation outgoing UDP port number 547.  They are what can
> be qualified as stubborn :-)
>
> For me, this is kind of an urgent matter.  We build a prototype onboard
> IoT Router to connect a car on cellular network.  It does 64share, and
> further down the car network there is L2 bridging too.  However, deeper
> inside there are further IP subnets - webcam and others.  IPv6 can not
> reach them.
>
> If by end of July I dont get this 65plen and 63IIDlen working then my
> onboard IPv6 design definitely has a conceptual flaw.
>

I think many of us have told you that design has conceptual flaws.


> I find this Internet Draft to be a little help in the right direction -
> encouraging.
>
> Alex
>
> Le 20/06/2018 à 06:47, Brian E Carpenter a écrit :
>
>> A new version with an additional term defined, following a suggestion
>> by Mark Smith.
>>
>> Again: this draft doesn't discuss the issues. Its only goal is to give us
>> some better terminology.
>>
>>      Brian
>>
>> -------- Forwarded Message --------
>> Subject: I-D Action: draft-carpenter-6man-lap-01.txt
>> Date: Tue, 19 Jun 2018 21:45:09 -0700
>> From: [e-mail]
>> Reply-To: [e-mail]
>> To: [e-mail]
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>>          Title           : The Longest Acceptable Prefix for IPv6 Links
>>          Author          : Brian Carpenter
>>         Filename        : draft-carpenter-6man-lap-01.txt
>>         Pages           : 4
>>         Date            : 2018-06-19
>>
>> Abstract:
>>     This document introduces the concepts of a Longest Acceptable Prefix
>>     (LAP) and a Shortest Acceptable Identifier Length (SAIL) for an IPv6
>>     link.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-carpenter-6man-lap/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-carpenter-6man-lap-01
>> https://datatracker.ietf.org/doc/html/draft-carpenter-6man-lap-01
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-carpenter-6man-lap-01
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> [e-mail]
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [e-mail]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



-- 
===============================================
David Farmer               Email:[e-mail]
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: [phone]
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================