[v6ops] Re: 464XLAT-only networks

[Lorenzo Colitti <[e-mail]>]

getaddrinfo will still issue IPv6 queries because it decides whether to do
so based on addresses configured, not routes configured.

On Fri, 25 Oct 2024, 19:57 Soni "It/Its" L., <[e-mail]> wrote:

> with an explicit route for the nat64 prefix?
>
> On 2024-10-25 07:42, Lorenzo Colitti wrote:
>
> If it doesn't have a default route, how is it going to reach the nat64
> prefix?
>
> On Fri, 25 Oct 2024, 19:30 Soni "It/Its" L., <[e-mail]>
> wrote:
>
>> if it doesn't have GUAs or a default route (is a default route required
>> in SLAAC? can't remember), why would it do any of that?
>>
>> On 2024-10-24 22:27, Lorenzo Colitti wrote:
>>
>> The problem with such a network is that the host doesn't know that the
>> IPv6 internet is reachable. Because IPv6 stacks generally prefer IPv6 over
>> IPv6, that typically results in high latency and failures. Here are the
>> first three problems I can think of:
>>
>>    - Client code that cannot fall back from IPv6 to IPv4 won't work
>>    - getaddrinfo will always issue AAAA lookups as well as A lookups,
>>    slowing down DNS lookups
>>    - HE implementations that bias towards IPv6 (which I think is
>>    suggested or required by the RFC) will encounter latency penalties.
>>
>> There are probably more.
>>
>> On Thu, Oct 24, 2024 at 7:33 PM Soni L. <[e-mail]> wrote:
>>
>>> we would like to propose a bastardization of IPv6-only networks and
>>> 464XLAT: the 464XLAT-only network.
>>>
>>> it's a network that doesn't provide access to the IPv6 internet, but
>>> does provide access to the IPv4 internet via 464XLAT.
>>>
>>> thoughts?
>>> _______________________________________________
>>> v6ops mailing list -- [e-mail]
>>> To unsubscribe send an email to [e-mail]
>>>
>>
>> --
>> plural system (tend to say 'we'), it/she/they, it instead of you
>>
>>
> --
> plural system (tend to say 'we'), it/she/they, it instead of you
>
>