33 Years of the Digest ... founded August 21, 1981
Copyright © 2014 E. William Horne. All Rights Reserved.
The Telecom Digest for Sep 6, 2014
|Messages in this Issue:|
|Re: R.I.P. Patrick Townson, September 24, 1942 - August 9, 2014||(Koos van den Hout)|
|Ready for IPv6? No, not really.||(Garrett Wollman)|
Previous Issue (Or search the Telecom Digest archives to go back further)
Mills of the Gods! They grind exceedingly slow; they grind exceedingly fine. - Juvenal
See the bottom of this issue for subscription and archive details.
|Date: Fri, 5 Sep 2014 07:31:58 +0000 (UTC) From: Koos van den Hout <email@example.com> To: firstname.lastname@example.org. Subject: Re: R.I.P. Patrick Townson, September 24, 1942 - August 9, 2014 Message-ID: <email@example.com> Bill Horne <firstname.lastname@example.org> wrote in <20140902193614.GA8829@telecom.csail.mit.edu>: > I'd like to write a better story about Pat than what's availalbe now, > so anyone with details on his education, life, relationships, > accomplishments, and family is welcome to send them to my personal > address. I think the Telecom Digest is one of Pat's biggest and longest-running accomplishments. The biggest compliment for this that I know can be found at http://1997.webhistory.org/www.lists/www-talk.1993q1/0241.html Tim Berners-Lee forwarding a suggestion to make the telecom digest available on the web in order to *promote the web*. Koos -- Koos van den Hout, PGP keyid DSS/1024 0xF0D7C263 via keyservers email@example.com IPv6: Think ::/0, act ::1. http://idefix.net/ Are you ready to start supporting IPv6?|
|Date: Sat, 6 Sep 2014 02:13:12 +0000 (UTC)
From: firstname.lastname@example.org (Garrett Wollman)
Subject: Ready for IPv6? No, not really.
In article <email@example.com>,
Koos van den Hout <firstname.lastname@example.org> wrote:
>email@example.com IPv6: Think ::/0, act ::1.
>Are you ready to start supporting IPv6?
This .signature hit a bit of a raw nerve today. I thought I was ready
to support IPv6 years ago. Then along came "privacy" addresses and
threw all of that right out the window. I don't want to repeat my
rant here, so please see my blog post about why IPv6 as currently
specified and implemented is unsuitable for use on anything but small
or very tightly controlled networks:
Everything I write about could be fixed -- indeed, could have been
prevented -- but the software vendors who decided that turning on
"privacy" addresses would make it seem as if they were doing a good
thing should have talked with the network hardware vendors (who would
have told them that this was insane). We'll probably end up using
DHCPv6 (and turning on DHCP snooping to block clients that don't
use a DHCP-assigned IPv6 address) but we don't yet have the ability to
A reasonable alternative to "privacy" addresses -- depending on the
threat model -- would be either Cryptographically Generated Addresses
or generating the interface ID as a 62-bit truncated hash of (prefix,
MAC-48) rather than a random number, so that it would at least be
stable and traceable within the domain of a single network operator.
TELECOM Digest is an electronic journal devoted mostly to telecom- munications topics. It is circulated anywhere there is email, in addition to Usenet, where it appears as the moderated newsgroup 'comp.dcom.telecom'.
TELECOM Digest is a not-for-profit educational service offered to the Internet by Bill Horne.
The Telecom Digest is moderated by Bill Horne.
43 Deerfield Road
Sharon MA 02067-2301
bill at horne dot net
This Digest is the oldest continuing e-journal about telecomm- unications on the Internet, having been founded in August, 1981 and published continuously since then. Our archives are available for your review/research. We believe we are the oldest e-zine/mailing list on the internet in any category! URL information: http://telecom-digest.org Copyright © 2014 E. William Horne. All rights reserved.
Finally, the Digest is funded by gifts from generous readers such as yourself. Thank you!
All opinions expressed herein are deemed to be those of the author. Any organizations listed are for identification purposes only and messages should not be considered any official expression by the organization.