Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)

[Mark Andrews <[e-mail]>]

> On 8 Jan 2021, at 12:43, Ted Lemon <[e-mail]> wrote:
> 
> Who determines what names to use?  What is the scope of the names? How is uniqueness guaranteed in that scope?

One would recommend using suffix names that are already registered to the organisation, individual in the DNS.
The example names I used where using the individuals suffix (id.au) but the idea is to leverage the existing global DNS to provide uniqueness.  If you don’t have a domain name generate a random 160 bit number and base32 encode it (like NSEC3) or similar and append .home.arpa to it.  If you are publishing into the global DNS you have a registered name to use as a suffix.  If you aren’t publishing into the global DNS you need to ensure the names don’t clash with any in the global DNS, <label>.home.arpa qualifies.   If you don’t like home.arpa, register a another name to be the default suffix labels.

>> On Jan 7, 2021, at 20:18, Mark Andrews <[e-mail]> wrote:
>> 
>> 
>> 
>>> On 8 Jan 2021, at 02:08, Ted Lemon <[e-mail]> wrote:
>>> 
>>>> On Jan 7, 2021, at 9:55 AM, Philip Homburg <[e-mail]> wrote:
>>>> I can see a few benefits of Mark's proposal. One is that it is good to
>>>> have a standard representation of information. In particular,
>>>> Mark's proposal would make it possible to have a master zone file that has
>>>> both public and private DNS entries. Then a split-DNS server could serve
>>>> only the public data to the outside world. 
>>> 
>>> That’s a good point, although it would still be a good point if this were just a feature of the zone file and not of the wire format.
>>> 
>>>> At the same time, I think it would be great if we can put link-local addresses
>>>> in DNS. 
>>> 
>>> That sounds like a really heavy lift.
>>> 
>>>> It may tie in nicely with scope IDs in socket addresses. If a DNS
>>>> record specifies that is valid only on a VPN link, then maybe we can already
>>>> tie the address to that link. No need to change applications, it can be
>>>> hidden in the stub resolver.
>>> 
>>> Now we need to standardize a way to identify links. This is a Hard Problem. I say this based on experience, not supposition. HNCP tried to do this, not as successfully as I’d hoped. I’ve been working on it for the Thread Border Router work, and haven’t come up with a general solution. Sure, if you have a data center and a managed multi-subnet LAN, and you can just type in configurations, this works, but most networks aren’t like that.  I think the VPN case is probably tractable, but it’s really hard to see a path to broad adoption for this idea.
>> 
>> 
>> My idea would be that there would also be a RA option(s) which advertised the names in the SA records that where applicable to the link.  Implicit to that is that there would be a API that allows getaddrinfo() to retrieve the
>> RA options for individual links and for all links on the node.  getaddrinfo() would use the later.  The former would be used to construct UPDATE requests for the DNS etc.  LLSANAME (link-local SA name), ULASANAM (ULA SA name), and perhaps others.
>> 
>>> If there is a path to broad adoption, it probably involves bottom-up work, not top-down design. Most of the ideas I’ve had about this that I think are practicable are very context-dependent. E.g., you can identify that you are on the same link because you received a link-scoped multicast.
>>> 
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> [e-mail]
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>> 
>> -- 
>> Mark Andrews, ISC
>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>> PHONE: [phone]              INTERNET: [e-mail]
>> 

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: [phone]              INTERNET: [e-mail]