go6.si

Francoski ISP Free.fr implementiral 6rd sistem na Cisco opremi…

JanZorz — Fri, 03 Sep 2010 08:01:53 +0000

Free.fr, francoski ISP, ki je razvil in implementiral prvo verzijo 6rd sistema za uvedbo IPv6 na IPv4 dostopovnem omrežju je sedaj svoj 6rd servis preselil iz domačih “iznajdb” na Cisco opremo, kjer je 6rd profesionalno implementiran in pripravljen na zahteve produkcijskega omrežja…

Free.fr je za potrebe prve uvedbe 6rd naredil “home-brewed” sistem, ki je doprinesel veliko k spoznanjem, kako je treba 6rd sistem razviti da bo uporaben. Cisco je vsa ta znanja in izkušnje združil skupaj in v svojo opremo postavil novo verzijo 6rd, ki je namenjena za “carrier-grade” naročnike in uporabnike.

Press release.

Jan Žorž

ITU je uvrstil Zavod go6.si med svetovne reference na področju IPv6…

JanZorz — Thu, 02 Sep 2010 09:38:03 +0000

Go6.si se je znašel med ITU (International Telecommunication Union) referencami, katere so navedene na njihovem IPv6 delu academy.itu.int portala, zapisani smo pod rubriko “Resources shared by regional and national organizations” …

Zapisali so nas med velike mednarodne organizacije, ki prispevajo k uvedbi IPv6, na kar smo lahko ponosni, ni nam pa čisto zares jasno, kako smo na ta spisek prišli:

AfriNIC IPv6 resource
APNIC IPv6 Program resources
APNIC – ICONS IPv6 Wiki
American Registry for Internet Numbers (ARIN) IPv6 Wiki resources and material
Asia Pacific IPv6 Task Force resources
European IPv6 Task Force collaborative IPv6 Portal resources
European Commission DG IPv6 resources
IPv6 Brazil resources (Portuguese)(English)
IPv6 e-learning course (Portuguese)
LACNIC IPv6 portal (English)(Portuguese)(Spanish)
Renater France IPv6 resources (English)(French)
go6.si IPv6 resources (Slovanian)

Zanimivo…

ITU poizkuša svoje interese uveljaviti tudi v IPv6 svetu, kjer pod pretvezo, da smo IPv4 naslovni prostor razdelili nespametno in sedaj za države v razvoju ni več naslovov na voljo hočejo svoj IPv6 kos pogače zase. Predlagajo, da se jim dodeli enako velik naslovni prostor IPv6 kot ostalim RIR-om, katerega bodo oni delili po njihovem ključu in ga modro prihranili za države v razvoju, ko se bodo nekoč razvile in potrebovale IPv6 naslovni prostor. Pozabljajo, da z vsemi sredstvi, katera imamo na voljo na planetu ne moremo niti administrativno razdeliti IPv6 naslovnega prostora v nekaj 10 tisoč letih in da IPv6 ne bo zmanjkalo v tem civilizacijkem ciklusu.

Pretveza je dobra, vprašanje pa je, če bodo uspeli. S tem, ko bi ITU uvedel razdeljevanje IPv6 naslovnega prostora po njihovem sistemu, to je hierarhičen (ITU -> NRO (National Registry Organisation) -> LIR (Local internet registry) bi lahko po vseh državah dobili IPv6 naslove iz nacionalnega registra, kar pomeni počasno ukinjanje RIR modela kot takšnega, ki trenutno zelo dobro deluje.

Pa to hočemo?

Jan Žorž

P.S: ITU-ju pa vseeno hvala za takšno čast, nismo pričakovali da nas bodo uvrstili med tako pomembne organizacije

go6 RSS feed smo prestavili na FeedBurner…

JanZorz — Thu, 02 Sep 2010 07:33:37 +0000

RSS feed smo prestavili na feedburner, kar prinaša določene dobre in slabe lastnosti. Prosim, da vsi, ki ste naročeni na RSS preverite, ali vam RSS še deluje (na nekaterih bralnikih prehod ni transparenten, ampak se morajo še enkrat prijaviti) in če vam slučajno ne deluje vas vabim, da se prijavite še enkrat…

Stari naslov http://go6.si/?feed=rss2 še vedno deluje, le da se preusmeri na http://feeds.feedburner.com/go6si , kjer si pa lahko izberete več formatov za različne odjemalce, med drugim tudi klasičen XML format, v katerem je RSS deloval do sedaj.

Opravičujemo se za morebitne nevšečnosti.

Jan Žorž

Mikrotik in IPv6 BGP…

JanZorz — Wed, 01 Sep 2010 11:29:34 +0000

Po hardverski napaki dosedanjega BGP usmerjevalnika za 2a02:e8::/32, ki je temeljil na PC+Linux+Quagga smo presedlali na Mikrotik platformo in IPv6 alokacijo Domence/go6 oznanili iz Mikrotik routerja…

Zadeva je delala skoraj iz prvega poskusa, paziti je treba edino na nekaj specifik; če ne oznanjamo “directly connected” ali “static routes” ali kaj podobnega in v “BGP networks” dodamo IPv6 naslovni prostor, katerega bi radi oznanjali, se ta ne objavlja dokler nimamo postavljene vsaj ene route lokalno, torej smo naredili eno dummy routo /32 na link-local tako da se je naslovni prostor začel oglaševati. Druga zadeva, katero moramo paziti je pa to, da pri postavitvi BGP seje po defaultu uporablja IP protokol, ki pa ni IPv6. To je treba posebej specificirati.

Zadeva deluje že več kot kakšen teden stabilno, ne opažamo kakšnih anomalij.

Hvala podjetju Virtua za donacijo Mikrotik usmerjevalnika in Ragnarju iz Amisa za support na drugi strani BGP sessiona, that was easy, was it?

Jan Žorž

Astec podaljšal članstvo v go6…

JanZorz — Tue, 31 Aug 2010 08:08:28 +0000

Podjetje Astec, integrator sistemskih rešitev in eden prvih članov go6 platforme je podaljšal članstvo v zavodu go6. Veseli smo izkazanega zaupanja in nadaljevanja skupne IPv6 poti…

S podjetjem Astec smo v preteklem letu zelo lepo sodelovali na IPv6 summit dogodkih ter tudi izven in veseli smo njihovega doprinosa k razvoju idej in projektov na področju IPv6, tako integracijskih rešitev kot tudi izobraževalnega programa. Astec je že začel ponujati IPv6 izobraževanje imenovano “IPv6 Boot camp“, ki poteka v idiličnem okolju Krvavca.

Upam, da se bo sodelovanje nadaljevalo vsaj v takšnem ritmu, hvala za zaupanje in podporo.

za go6, Jan Žorž

Arhiv: “Astec postal prvi uradni član go6″

Vyatta 6.1 pridobila “IPv6 ready – phase 2″ certifikat.

JanZorz — Sun, 29 Aug 2010 19:37:51 +0000

Programska rešitev za usmerjanje (routing) in varnost (firewall) Vyatta je v verziji 6.1 opravila rigorozno testiranje in pridobila certifikat “phase 2” po programu IPv6 ready, kar pomeni čez 450 opravljenih testov…

Vyatta je brezplačni sistem, katerega snamemo iz spletne strani proizvajalca ter namestimo na strojno opremo, ki bazira na PC platformi. Vyatta zahteva plačilo za zahtevnejše funkcionalnosti in podporo, a osnovna funkcionalnost je brezplačna.

Nova rešitev za IPv6, večinoma za testne namene in laboratorijska okolja ter manjše SOHO rešitve, za high-performance core routing okolja pa včasih malenkost vprašljiva kar se performans tiče. Sicer pa se mora vsak odloči sam, glede na svoje potrebe (Vyatta je na svojem spletnem mestu zapisala “Vyatta + Quad Core Intel Xeon 5500 series forwards traffic at 20 Gbps”)…

Certificiranje je vsekakor dobrodošlo, saj to odpira nove opcije za postavitev IPv6 v vse več okoljih.

Jan Žorž

Erion IPv6 izobraževanje v Sloveniji…

JanZorz — Sat, 28 Aug 2010 09:26:52 +0000

Sredi oktobra se bo prvič v Sloveniji odvijalo IPv6 izobraževanje podjetja Erion, predaval bo David Holder…

Erion je podjetje, ki se z IPv6 izobraževanjem ukvarja že več kot 10 let, David Holder je o tem tudi predaval na našem 3. Slo IPv6 summitu. David je popeljal skozi izobraževanje velika svetovna podjetja, tokrat prihaja k nam in skupaj s podjetjem QSTC/CHS so razpisali prvi tečaj.

Več o izobraževanju:

http://www.qstc.com/en/news/detajl/?id=80

http://www.qstc.com/en/trainings/detajl/?id=77

Jan

Nizozemski XS4ALL uvedel IPv6 za vse svoje končne uporabnike…

JanZorz — Fri, 27 Aug 2010 09:39:15 +0000

Nizozemski ponudnik dostopa do interneta XS4ALL je zaključil s pilotom testiranja IPv6 na vzorcu 1000 uporabnikov in se je po zelo dobrih rezultatih odločil, da IPv6 vpelje za vse uporabnike njihovega omrežja (XS4ALL ima okoli 300.000 naročnikov). Upam, da bomo kmalu lahko tudi pri nas videli prve operaterje in ponudnike dostopa do interneta, ki se bodo odločili za takšen korak…

Marco Hogewoning je press release v nizozemskem jeziku objavil kar preko Facebook strani, po emailu sem pa dobil angleško verzijo, ki je dovolj zgovorna: “mi imamo IPv6 do uporabnika v produkciji, kaj pa vi?”

XS4ALL Press release: IPv6 available for all, starting today (XS4ALL OFFERS IPv6 TO ALL CUSTOMERS)

Bo to vzpodbuda za katerega od slovenskih ISPjev?

Jan Žorž

First results of our suggestion to search engines…

JanZorz — Thu, 26 Aug 2010 09:32:40 +0000

Appology first to our Slovenian readers, this article really needs to be in english language because all this became bigger than we expected. As you probably noticed, our suggestion of “Proposed IPv6 impact on search engine scoring algorithms” got massive attention around the world, mainly because of mention in news secton on IPv6ActNow portal…

When IPv6ActNow published new entry in news section, go6.si server started to get massive amount of traffic and hits to that article, directly from them and also from other sites, that republished the article from IPv6ActNow.

We got massive feedback on proposed change, mostly very positive and some of brave fellows also left pubblic comment below the article (appreciate that, need more comments).

We also received 1 not supportive mail from very influential person in IPv6 advocacy world, that I highly respect and appreciate his opinion – and would like to share this oposing view with the audience for triggering further discussion:

“I don’t support it – it’s a content vs. transport issue. I’m very pro v6 (which you know); but I think this is like crossing the beams and should not be done.”

Looking from this perspective, I might partially agree, but is this really entirely true? I mean, how “pure” and “brave” we must be in situation like it is in IPv6 deployment world?

I will not publish all supportive comments, because of too many emails with similar message: “go for it, it’s brilliant idea”…

We got attention from highest powers of *the search engine* (thnx also to Latif Ladid and David Holder among others, that sent an email with go6.si link in it to *the search engine* folks) and all I can say currently is that they are reviewing our proposal and debating the possible negative effects of it.

I wrote some additional explanation and some my personal views of it inside email debate with Latif and Vint, let’s see how all this turns out.

I would like to thank you all for massive attention and feedback, great to hear that proposed change is very well accepted and have so much consensus in very wide Internet community. We wait for searche engine decisions now.

Jan Zorz

P.S: I had a quick look of who’s reading the proposal over which protocol in apache logfile; 27% over IPv6 and 73% over IPv4. Quite nice, is it?

Suggestion for Internet search engines: “Proposed IPv6 impact on search engine scoring algorithms”

JanZorz — Mon, 23 Aug 2010 09:14:37 +0000

At IETF76 in Maastricht I had a long discussion with Sander Steffann, IPv6 advocate and RIPE Address Policy WG co-chair. We talked about my idea, how could Google and all other search engines really trigger massive transition of internet content (and content providers) to IPv6. After long discussion Sander managed to put the idea into text…

We would also like to invite influential end experienced decision makers, working at Internet search engines (specially *the search engine*) to read this proposal carefully – so if somebody knows well one of this guys, feel free to point them at following text:

Abstract
Deployment and adoption of IPv6 is slow at this point in time. This can be a risk for future growth of the internet. One of the observed obstacles is that content providers are waiting for IPv6 viewers, and viewers are waiting for IPv6 content. We propose a slight change the search engine scoring algorithms to stimulate content providers to make their content accessible over IPv6.

Proposed change
We propose that search engines check whether a website is available over both IPv4 and IPv6. Having the same content available over both lower level protocols is the situation that will give the IPv4 to IPv6 transition the largest chance of succeeding. The way to determine if a website has ‘good’ IPv4 and IPv6 support is an implementation detail of the search engine.

Websites that are available over both protocols should then get some kind of bonus when compared to websites available over only IPv4 or IPv6. One possible idea is to use this as a tiebreaker when two pages get the same score based on the original scoring algorithm. Another possibility is to give the website a 5% bonus in the scoring algorithm. This choice is an implementation detail of the search engine.

The search engine operator should then make it publicly known that IPv6 support will have a positive impact on the search engine scoring algorithm.

Pros
This will stimulate website owners to make their websites available over IPv6, which benefits the whole internet community. For cases where the website owner makes use of services from a separate website hoster this hoster will also be stimulated to support IPv6. It will also send a signal that the search engine operator sees IPv6 support as being important for the future of the internet. Improving the future internet is also in the best interest of the search engine operator itself, as their business is based on the content available on the internet.

Cons
This proposal changes the scoring algorithm of the search engine, which is a very important part of the quality that the search engine provides. Using IPv6 support only as a tiebreaker or as a small component in this algorithm minimizes the impact. Another con can be that the public will see the search engine operator as pushing a technology instead of focussing on returning the search results that are ‘best’ for the end user. A counter argument to this can be that making content available over IPv6 is in the long term in the users best interest.

Thanx to Sander for taking my thoughts into text, I think it’s clear enough as is. With this move, everybody is a winner, nobody looses anything – “Search engine” is considered user friendly, taking care of their future experience and content providers would start rushing to deploy IPv6 to be just a step in front of their competitors. Done deal

Comments and debate warmly welcome!

Jan Zorz, go6.si