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] Re: [address-policy-wg] DRAFT: RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6
- Previous message (by thread): [ipv6-wg] Re: [address-policy-wg] DRAFT: RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6
- Next message (by thread): [ipv6-wg] Re: [address-policy-wg] DRAFT: RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
JORDI PALET MARTINEZ
jordi.palet at consulintel.es
Thu Oct 18 18:03:08 CEST 2007
End users are every day smarter. They realize that some peer to peer applications, on-lime-gaming, etc., works better some times or in some ISPs, and they end-up guessing that it is because they are able to use IPv6 end-to-end, doing *real* peer-to-peer. And it happens that some ISPs offer transition services that improve that, others not, so end-users end up replacing their ISPs and this is going to be more and more frequent, because this is already happening as more and more people uses Vista. Regarding the comment on the IPv6 traffic. There is a big misconception here, and I can prove it. We developed a tool to measure *REAL* IPv6 traffic, not just *NATIVE*. Because today, it is clear that a very very very low % is native, because almost none of the ISPs offer native IPv6 to the last mile, it is quite obvious. However, the increase on transition (encapsulated) IPv6 traffic is something happening in *ALL* the networks, despite those networks don't have *ANY* IPv6 support. GEANT may offer dual stack, but if the universities don't offer IPv6 to the desktop, then the OSs are using transition mechanisms, without users noticing it ! Regards, Jordi > De: Tim Streater <tim.streater at dante.org.uk> > Responder a: <address-policy-wg-admin at ripe.net> > Fecha: Thu, 18 Oct 2007 11:31:10 +0100 > Para: Sascha Lenz <slz at baycix.de>, Address Policy WG > <address-policy-wg at ripe.net> > CC: <ipv6-wg at ripe.net> > Asunto: Re: [address-policy-wg] DRAFT: RIPE Community Resolution on IPv4 > Depletion and Deployment of IPv6 > > At 10:49 18/10/2007, Sascha Lenz wrote: >> Hi, >> >> Patrick Vande Walle schrieb: >>> Florian Weimer wrote: >>>> * Gert Doering: >>>> >>>>> 2) We urge network operators and Internet Service Providers (ISPs) to >>>>> deploy IPv6 across their networks as soon as possible. This deployment >>>>> must include providing IPv6 access to End Users and ensuring services are >>>>> accessible by IPv6. >>>>> >>>> Shouldn't this paragraph target RIPE members specifically? Or, put >>>> differently, why are end users and software vendors excluded? >>>> >>> Speaking as an end user, which probably does not qualify me as being >>> part of the "RIPE Community": >>> Agree with Florian's comments, and I would add hardware vendors to the >>> list. As long as there are no commodity CPEs supporting IPv6, there is >>> no incentive for ISPs to deploy IPv6 to their end users, especially >>> those targetting the home users. >> >> even though the statement cannot be more than political "blah-blah" without >> any real outcome :-), i want to join in that the wording SHOULD include at >> least vendors end end-suer, since they are the biggest problem (point of >> view: a Consultant). >> Probably "network operators" is meant to include end-users, but that's not >> clear enough. >> And i also see vendors as part of "the community" here, but probably they >> don't think they are addressed without explicitely mentioning it :-) >> >> ISPs won't start deploying IPv6 more widely without end-users requiring it >> and vendors have a full (as in COMPLETE, WORKING) set of IPv6 capable >> devices, including SOHO CPEs. > > End users won't require it; they know little about v4 and v6 and only care > about their applications working and being able to reach the hosts/sites they > want to reach. When some parts of the Internet are only reachable via v6 > *that* is when users will > want to know why and will kick their ISPs, who will hasten to get their act > together and will then kick their upstreams. > > We have a fully v6-compliant network already - and little traffic. > >> ...heck, i already have one upstream explicitely SHUTTING DOWN its IPv6 >> (testbed) service (Allocation returned) without any production replacement >> since noone wants to have IPv6 connectivity...yes, big german business/resale >> ISP ... scary. > > > -- Tim > ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
- Previous message (by thread): [ipv6-wg] Re: [address-policy-wg] DRAFT: RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6
- Next message (by thread): [ipv6-wg] Re: [address-policy-wg] DRAFT: RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]