[shim6] IPv6 multihoming
Vlad Ion <vlad.thoth@gmail.com> Mon, 25 January 2010 08:55 UTC
Return-Path: <vlad.thoth@gmail.com>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9CF953A68FF for <shim6@core3.amsl.com>; Mon, 25 Jan 2010 00:55:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.045
X-Spam-Level: *
X-Spam-Status: No, score=1.045 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, FRT_BELOW2=2.154, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gTO+P3aQPFuW for <shim6@core3.amsl.com>; Mon, 25 Jan 2010 00:55:42 -0800 (PST)
Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by core3.amsl.com (Postfix) with ESMTP id 5F1C53A68B3 for <shim6@ietf.org>; Mon, 25 Jan 2010 00:55:42 -0800 (PST)
Received: by fxm7 with SMTP id 7so1759664fxm.28 for <shim6@ietf.org>; Mon, 25 Jan 2010 00:55:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=czFdx1+ZHfwpEG6J0fg8jRyL7HsIDFSCgMnuDZkBVTs=; b=Crz4tizXVyTU7pqBTjOfsuXdHKJQPKsqPGqXtHNN9npv2hSXtxna9DWt+IATaf29p2 wr4sROhoznrRhBDXcjP+PAfYHBFCZlRQ3bf9dZaLc01it4RvjTl3q3Ey7x4cY/hU3Xi0 QCZN35vEYTxvfpxLH7b7/wRIiOVpClmYs0Uuc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ZcnySXAH7AsvNfGAkv46+4LsPfc4Z3zpn1uSvDtq6R06X39nPhiWX0VpIf/JgEtaVn yMDMrc+r74CEefg+SctNxDqUaVZ3XjkhzLkdYaJR1EHD9NA7KOht72UY9b98VUh20arR vP+2OO95wZqOL2x0+4SiNOuKel+VuY/DQZj5Y=
MIME-Version: 1.0
Received: by 10.103.84.6 with SMTP id m6mr3202145mul.41.1264409742480; Mon, 25 Jan 2010 00:55:42 -0800 (PST)
Date: Mon, 25 Jan 2010 10:55:42 +0200
Message-ID: <a5456ccb1001250055y26928d3ar954c1799716cd3a9@mail.gmail.com>
From: Vlad Ion <vlad.thoth@gmail.com>
To: shim6@ietf.org, v6ops@ops.ietf.org
Content-Type: multipart/alternative; boundary="0016e65ae9148d1818047df955bf"
Subject: [shim6] IPv6 multihoming
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2010 08:55:43 -0000
Hi, For a year now whenever it comes to IPv6 telco implementations I keep facing 2 problems so I was hoping you can guide me towards find a group that deals with these issues or discussion solutions. The 2 problems are related to IPv6 multi-homing and access to the internet in IPv6 format for a quick transitions from v4 to v6. Also I need some guidance as to what needs to be done for a draft document proposal to be created about the proposed solutions mentioned bellow and who needs to be involved in this process. As far as multi-homing goes in IPv6 the solution discussion generated by using provider-independent address space like mentioned in draft-hain-ipv6-pi-addr-10 seems too complicated to implement efficiently and generates a lot of unnecessary work. Because IPv6 will never really be adopted by ISPs, telco and enterprises until it offers a feasible multi-homing solution my proposal is that some solutions are redefined such as provider independent address space and the 6to4 standard. I propose that the 6to4 ip conversion space from ipv4 addresses to 2002::ipv6 space will be redefined as provider independent address space. This way whoever wants to implement ipv6 with multi-homing can simply redefine their existing IPv4 addresses in IPv6 6to4 format and have multi-homing in ipv6. Everyone already uses ipv4 multi-homing with success so I see no point in defining a new addressing system for v6 when everyone can simply use the same v4 address space for multi-homing but converted in 6to4 format. Also, another issue faced by whoever uses IPv6 is that access to the internet in v6 format is limited so a proposal has to be made to the RIRs to offer incentives such as free IPv6 space for anyone who implements 6to4 relay routers and advertises their existing v4 space in v6 format along with the newly received free v6 space. I believe that as long as ietf gets involved and a rfc is written on these 2 proposals starting with the redefining of the provider independent address space and its inclusion in the 6to4 format things will be a lot more compact and give some additional momentum to the IPv6 migration process. Best regards and I hope to hear from you soon, Vlad Ion Siemens PSE IP backbone design engineer
- [shim6] IPv6 multihoming Vlad Ion
- Re: [shim6] IPv6 multihoming Mohacsi Janos
- Re: [shim6] IPv6 multihoming Vlad Ion
- Re: [shim6] IPv6 multihoming Mikael Abrahamsson
- Re: [shim6] IPv6 multihoming Vlad Ion
- Re: [shim6] IPv6 multihoming Mikael Abrahamsson
- Re: [shim6] IPv6 multihoming Patrick W. Gilmore
- Re: [shim6] IPv6 multihoming Vlad Ion
- Re: [shim6] IPv6 multihoming Vlad Ion
- Re: [shim6] IPv6 multihoming Vlad Ion
- Re: [shim6] IPv6 multihoming Vlad Ion
- Re: [shim6] IPv6 multihoming Gert Doering
- Re: [shim6] IPv6 multihoming Ethern M., Lin