Re: [shim6] IPv6 multihoming
Vlad Ion <vlad.thoth@gmail.com> Tue, 26 January 2010 17:20 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 501DF3A690D for <shim6@core3.amsl.com>; Tue, 26 Jan 2010 09:20:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.237
X-Spam-Level:
X-Spam-Status: No, score=-2.237 tagged_above=-999 required=5 tests=[AWL=-1.793, BAYES_00=-2.599, 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 Zwl-kaQOuOzR for <shim6@core3.amsl.com>; Tue, 26 Jan 2010 09:20:47 -0800 (PST)
Received: from mail-yx0-f192.google.com (mail-yx0-f192.google.com [209.85.210.192]) by core3.amsl.com (Postfix) with ESMTP id 0C5603A6907 for <shim6@ietf.org>; Tue, 26 Jan 2010 09:20:46 -0800 (PST)
Received: by yxe30 with SMTP id 30so2497107yxe.29 for <shim6@ietf.org>; Tue, 26 Jan 2010 09:20:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=Rrc9EXUKxRXsQQqWhfN2ZcnIQJQiSc5Togr0h5tcxbU=; b=lbK6RByjObtihG2qpDYNdwKUBLuaaIAPM3jYyu9YTNHH16lbIl/UbmMM8SeQaLZoea eiqrbD3rM7uyXmiOTyzKDe5r+aInCr7m450gX/bfJ9hsDRemnSQGj2ABN5Wye1xzjoi9 pBHsyqnFNC3jti9LEmTFlG4KQKnhjRCmbX0TU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=V+eQcQxN549ZUlpHMsWYD7YNKxlyRiGy12vpKpPlJoaB1G9LtsYhPAazcE037n/Wso 40JSp73gk2rxPyb+ozHcw2Vr1nUy1rL581BYLiY1jMJx1guWJPxk16z5b6BaLTS7pefm 2RGjFszH2IXybnSnYhrfP5cFwqsiRouov2eJc=
MIME-Version: 1.0
Received: by 10.103.87.28 with SMTP id p28mr4198341mul.83.1264526453249; Tue, 26 Jan 2010 09:20:53 -0800 (PST)
In-Reply-To: <8582c31a1001260806w4b62cc50wf887a8f87a9a7700@mail.gmail.com>
References: <a5456ccb1001250055y26928d3ar954c1799716cd3a9@mail.gmail.com> <8582c31a1001260806w4b62cc50wf887a8f87a9a7700@mail.gmail.com>
Date: Tue, 26 Jan 2010 19:20:53 +0200
Message-ID: <a5456ccb1001260920t662155abv37c971dd7c8caa51@mail.gmail.com>
From: Vlad Ion <vlad.thoth@gmail.com>
To: shim6@ietf.org, v6ops@ops.ietf.org
Content-Type: multipart/alternative; boundary="0016e65c7f680e18db047e14823c"
Subject: Re: [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: Tue, 26 Jan 2010 17:20:48 -0000
Hi Ethern, The idea of having people who own v4 space to announce it in v6 form and perform the local translation between those 2 was to encourage and provide an additional incentive to whoever deploys a v6 island because they'll have direct access to the full internet in v6 form without needing to deploy something like 6to4 to access the v6 internet and a nat-pt to access the v4 internet. BR, Vlad On Tue, Jan 26, 2010 at 6:06 PM, Ethern M., Lin <ethern@ascc.net> wrote: > Hi Vlad, > > This issue is assuming that everyone can get the public IPv4 IP, > right? But how can you guarantee that everyone can get the public IPv4 > IP without any problem? If not, I don't think your idea work although > I am admire your spirit to push IPv6 and solve the multi-homing issue > in IPv6. > > cheers, > Ethern > > On Mon, Jan 25, 2010 at 4:55 PM, Vlad Ion <vlad.thoth@gmail.com> wrote: > > 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