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/[email protected]/

[ipv6-wg at ripe.net] 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)

• Previous message (by thread): [ipv6-wg at ripe.net] 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)
• Next message (by thread): [ipv6-wg at ripe.net] 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Iljitsch van Beijnum iljitsch at muada.com
Thu Jul 22 16:35:52 CEST 2004

On 22-jul-04, at 16:12, Gert Doering wrote:

>> It will take some time to get rid of the "ancient" operating systems 
>> and
>> as long as they exist, ip6.int. might be necessary.

> Let's break these as quickly as possible.  So that people will *notice*
> that their crappy libraries need fixing.

Ok, but only if we give all the root servers an IPv6 address and allow 
them to go over the 512 byte limit for udp responses too. If we're 
going to break things, let's break something people will notice.

• Previous message (by thread): [ipv6-wg at ripe.net] 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)
• Next message (by thread): [ipv6-wg at ripe.net] 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]