Re: [v6ops] AWS ipv6-only features

On Fri, 26 Nov 2021, 07:41 Clark Gaylord, <cgaylord@vt.edu> wrote:

> Yeah AWS hold their cards close and don't seem to engage the community,
> but they do have decent IPv6 coverage across the services. Notwithstanding
> that the whole VPC concept has the whiff of ancient days about it; tonight
> we're gonna network like it's 1999!
>
> EC2 as part of the address is a great idea. I am so stealing that (can't
> believe I haven't thought of it.)
>

It's a terrible idea. The "Unique" in ULA is on purpose.

Getting IPv6 private addressing right
https://blog.apnic.net/2020/05/20/getting-ipv6-private-addressing-right/

>
> On Thu, Nov 25, 2021, 15:09 Mark Smith <markzzzsmith@gmail.com> wrote:
>
>>
>>
>> On Thu, 25 Nov 2021, 23:51 Ca By, <cb.list6@gmail.com> wrote:
>>
>>> Fyi, aws has gone beyond perfunctory ipv6 support and has released a
>>> series of enhancements, with a focus on ipv6-only scenarios, including
>>> nat64 / dns64
>>>
>>>
>>> https://aws.amazon.com/about-aws/whats-new/2021/11/aws-nat64-dns64-communication-ipv6-ipv4-services/
>>>
>>> AWS has lapped Google and Azure in advanced network features, which is
>>> really surprising given the early muscle Google developed at IPv6 launch
>>> and a stronger need to differentiate …
>>>
>>
>> AWS failed to do ULAs properly. 'ec2' could be a random global ID, but
>> unlikely when their service is "EC2".
>>
>> Matters more here because they're exposing that to all of their tenants.
>> I think GUAs would have been better for these internal all tenant services.
>>
>> I've never seen AWS participate here in 20 years, unlike G and M.
>>
>>
>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>