Re: [GLOBAL-V6] IPV4 to IPv6 migration
- To: Mohsen Souissi <mohsen.souissi at nic dot fr>
- Subject: Re: [GLOBAL-V6] IPV4 to IPv6 migration
- From: Jeroen Massar <jeroen at unfix dot org>
- Date: Tue, 03 Jun 2008 18:13:04 +0200
- Cc: global-v6 at lists dot apnic dot net
- Delivered-to: global-v6 at mailman dot apnic dot net
- In-reply-to: <20080603155020.GB82734 at kerkenna dot nic dot fr>
- List-archive: <http://mailman.apnic.net/mailing-lists/global-v6>
- List-help: <mailto:email@example.com?subject=help>
- List-id: Discussion of new global IPv6 policy development <global-v6.lists.apnic.net>
- List-post: <mailto:firstname.lastname@example.org>
- List-subscribe: <http://mailman.apnic.net/mailman/listinfo/global-v6>, <mailto:email@example.com?subject=subscribe>
- List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/global-v6>, <mailto:firstname.lastname@example.org?subject=unsubscribe>
- Openpgp: id=333E7C23
- Organization: Unfix
- References: <C4694F4D.4A86email@example.com> <firstname.lastname@example.org> <0A120AB3-94C6-4950-9F42-CF97CB121979@virtualized.org> <4844BB30.email@example.com> <F5EB56D9-88D7-4958-A31A-41564B77E829@virtualized.org> <48454E83.firstname.lastname@example.org> <20080603155020.GB82734@kerkenna.nic.fr>
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20080421 Lightning/0.8 Thunderbird/188.8.131.52 Mnenhy/0.7.5.666
Mohsen Souissi wrote:
On 03 Jun, Jeroen Massar wrote: | David Conrad wrote: | [..]| >It's a bit sad that we didn't take the opportunity to define a new API | >that would return 'network handles' | | SCTP & HIP. Please look at these.==> Without any intention to revive an old controversy, and without calling it an "API" per se, RFC2874 (A6, made experimental by RFC 3363) attempted to address that issue, at least partially. Still today, I don't think that the benefits of A6 outbalance its costs.
A6's are very useful to migrate a host quickly in DNS, as it avoids 'editting' a lot, but then existing connections would still break. I don't see how A6 actually solves any problem, except where remote entities are controlling prefixes which they delegate to customers; updating A6 records does not update hosts though.
SCTP and HIP both handle that a host, during a session, renumbers and keep the session alive, completely transparent to the application, (unless it wants to know about it that is).
Description: OpenPGP digital signature