This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] IPv4-mapped addresses in AAAA records (was: RIPE 88, presentations and a co chair change..)
- Previous message (by thread): [ipv6-wg] IPv4-mapped addresses in AAAA records
- Next message (by thread): [ipv6-wg] IPv4-mapped addresses in AAAA records (was: RIPE 88, presentations and a co chair change..)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael Richardson
mcr+ietf at sandelman.ca
Wed Mar 27 04:34:41 CET 2024
My take home from this github incident is that one should do IPv6 deployment first, and then treat IPv4 as a subset via mapped IPv4 addresses. (Open)SSH had been using the mapped addresses for ages, and they showed up that way for ages. It has stopped for unknown reasons. -- Michael Richardson <mcr+IETF at sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =- *I*LIKE*TRAINS* -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 487 bytes Desc: not available URL: </ripe/mail/archives/ipv6-wg/attachments/20240327/73ddd1e1/attachment.sig>
- Previous message (by thread): [ipv6-wg] IPv4-mapped addresses in AAAA records
- Next message (by thread): [ipv6-wg] IPv4-mapped addresses in AAAA records (was: RIPE 88, presentations and a co chair change..)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]