Hackerspace" <lvl1@googlegroups.com>
Received: by 10.180.104.33 with SMTP id gb1mr1937265wib.1.1347823538704;
        Sun, 16 Sep 2012 12:25:38 -0700 (PDT)
X-BeenThere: lvl1@googlegroups.com
Received: by 10.180.103.170 with SMTP id fx10ls2171091wib.0.canary; Sun, 16
 Sep 2012 12:25:37 -0700 (PDT)
Received: by 10.180.105.2 with SMTP id gi2mr1109170wib.4.1347823537697;
        Sun, 16 Sep 2012 12:25:37 -0700 (PDT)
Received: by 10.180.105.2 with SMTP id gi2mr1109169wib.4.1347823537684;
        Sun, 16 Sep 2012 12:25:37 -0700 (PDT)
Return-Path: <barton...@gmail.com>
Received: from mail-we0-f176.google.com (mail-we0-f176.google.com [74.125.82.176])
        by gmr-mx.google.com with ESMTPS id em7si1393045wib.2.2012.09.16.12.25.37
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sun, 16 Sep 2012 12:25:37 -0700 (PDT)
Received-SPF: pass (google.com: domain of barton...@gmail.com designates 74.125.82.176 as permitted sender) client-ip=74.125.82.176;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of barton...@gmail.com designates 74.125.82.176 as permitted sender) smtp.mail=barton...@gmail.com; dkim=pass header...@gmail.com
Received: by weyu3 with SMTP id u3so3442538wey.7
        for <lvl1@googlegroups.com>; Sun, 16 Sep 2012 12:25:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=Vm8S6IUhsLFeuZRqLpd5lpIGYOJnEjEiouwHSeWIFPE=;
        b=ljySx04XioV57l4IY7dq9jnomlM9AzJEFN10s3bwIioY03+PmdTTBiPHVijLK5fqX7
         WrClaArpo6Qqk6XB/QGsOKeAoSSpP6T8Ez8D4LkX8XR4pL+x7fBSCvIfXF2PWFlxgYjk
         QDj0znxEA+ipYjGrxgwK9UE3X4F+d21GFYJojH9CyXjlTn1MG06QZoI8Q7t/abQeM1se
         /hr61TpRDxTvfBegOpWe2k4qqNvJirLYFgPh7N5TjNHZr9q8BQSFB0LwX/W2HUUSq4WJ
         4FiXsG02gKDbRcqE1QTw53/1LUczyBXWqdk1Wv1yvOMvb+DTbKIwQqfb5lFGKon5RTo3
         rH1w==
MIME-Version: 1.0
Received: by 10.216.228.130 with SMTP id f2mr4761471weq.7.1347823537489; Sun,
 16 Sep 2012 12:25:37 -0700 (PDT)
Received: by 10.216.65.137 with HTTP; Sun, 16 Sep 2012 12:25:37 -0700 (PDT)
Date: Sun, 16 Sep 2012 15:25:37 -0400
Message-ID: <CAGvtssKNbYtOhDc=mQ2uzHAwye5LHsGfn=HeJ2ifdtDi=H4...@mail.gmail.com>
Subject: Suggested discussion topic: IPv4 address exhaustion and IPv6 adoption
From: Barton Chittenden <barton...@gmail.com>
To: kyoss-discuss <kyoss-disc...@kyoss.org>, lvl1@googlegroups.com
Content-Type: multipart/alternative; boundary=0016e6d641562c05e404c9d69f17

--0016e6d641562c05e404c9d69f17
Content-Type: text/plain; charset=ISO-8859-1

On September 14, RIPE NCC, the European regional internet registry, started
allocating IP addresses from its last /8 address block. This is the
beginning of the end of the allocation of the IPv4 address space (i.e.
addresses of the form xxx.xxx.xxx.xxx) as we know it. Allocation of IPv4
addresses in Europe is now strictly rationed.

ARIN (American Registry of Internet Numbers) will be down to its last /8 by
this time next year.

The long term solution to this problem is to start using IPv6 addresses,
which are essentially unlimited (The address space is so large that you
could assign about a thousand times the current internet address space to
each cell of every one of the 7 billion people on earth).

The problem of switching to IPv6 is a chicken-and-egg problem: internet
users won't switch to IPv6 addresses because there are very few sites that
they can connect to which use IPv6, and no content providers use IPv6
addresses because no-one visits via IPv6. Most ISPs don't provide IPv6
addresses (or if they do, no-one realizes that they do).

There are some short-term solutions, but they destroy the point-to-point
nature of the internet which can cause problems.

I have a decent handle on what's happening and why, but I have zero
experience with setting up a network using IPv6... in many ways, it should
be transparent (as IPv4 is... you connect your computer to a router via
cat5 cable or wireless, and you're connected). Obviously, it's not *quite* that
easy, if it was, we would all be using IPv6 and we wouldn't be worrying
about running out of address space.

I was wondering if some of the local network gurus could give a talk about
this:


   - A primer on IP addresses in general
   - What physical steps do I need to take to set up an IPv6 network? (e.g.
   a LAN).
   - Are there any issues involved with running both IPv4 and IPv6 on the
   same network?
   - How do I connect to the internet via IPv6?
   - Will my ISP provide IPv6 addresses?
   - Are there security issues involved with using IPv6, and if so, how do
   I fix these?
   - ...

Any takers? I would be willing to do the presentation, but, as I said, I
have *zero* practical experience, and I think that the topic deserves more
than hand-waving.

--Barton

--0016e6d641562c05e404c9d69f17
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On September 14, RIPE NCC, the European regional internet registry, started=
 allocating IP addresses from its last /8 address block. This is the beginn=
ing of the end of the allocation of the IPv4 address space (i.e. addresses =
of the form xxx.xxx.xxx.xxx) as we know it. Allocation of IPv4 addresses in=
 Europe is now strictly rationed.<div>

<br></div><div>ARIN (American Registry of Internet Numbers) will be down to=
 its last /8 by this time next year.</div><div><br></div><div>The long term=
 solution to this problem is to start using IPv6 addresses, which are essen=
tially unlimited (The address space is so large that you could assign about=
 a thousand times the current internet address space to each cell of every =
one of the 7 billion people on earth).</div>

<div><br></div><div>The problem of switching to IPv6 is a chicken-and-egg p=
roblem: internet users won&#39;t switch to IPv6 addresses because there are=
 very few sites that they can connect to which use IPv6, and no content pro=
viders use IPv6 addresses because no-one visits via IPv6. Most ISPs don&#39=
;t provide IPv6 addresses (or if they do, no-one realizes that they do).</d=
iv>

<div><br></div><div>There are some short-term solutions, but they destroy t=
he point-to-point nature of the internet which can cause problems.</div><di=
v><br></div><div>I have a decent handle on what&#39;s happening and why, bu=
t I have zero experience with setting up a network using IPv6... in many wa=
ys, it should be transparent (as IPv4 is... you connect your computer to a =
router via cat5 cable or wireless, and you&#39;re connected). Obviously, it=
&#39;s not <i>quite</i>=A0that easy, if it was, we would all be using IPv6 =
and we wouldn&#39;t be worrying about running out of address space.</div>
<div><br></div><div>I was wondering if some of the local network gurus coul=
d give a talk about this:</div><div><br></div><div><ul><li>A primer on IP a=
ddresses in general</li><li>What physical steps do I need to take to set up=
 an IPv6 network? (e.g. a LAN).</li>
<li>Are there any issues involved with running both IPv4 and IPv6 on the sa=
me network?</li><li>How do I connect to the internet via IPv6?</li><li>Will=
 my ISP provide IPv6 addresses?</li><li>Are there security issues involved =
with using IPv6, and if so, how do I fix these?</li>
<li>...</li></ul><div>Any takers? I would be willing to do the presentation=
, but, as I said, I have <i>zero</i> practical experience, and I think that=
 the topic deserves more than hand-waving.</div></div><div><br></div><div>
--Barton</div>

--0016e6d641562c05e404c9d69f17--