Archive for the ‘Internet’ Category

ARIN 2010 Election Candidates Announced

Tuesday, August 31st, 2010

My work as part of the ARIN NomCom this year has concluded, and I’m happy to see that the final slate of candidates was announced today:

Elections for two (2) seats on the ARIN Board of Trustees and five (5)
seats on the ARIN Advisory Council will be held online 6-16 October.

The following candidates have agreed to run for office:

Board of Trustees:
* Vinton Cerf, Google, Inc.
* Lee Howard, Time Warner Cable
* Aaron Hughes, 6connect, Inc
* Paul Vixie, Internet Systems Consortium

Advisory Council:
* Cathy Aronson, Cascadeo Corporation
* Jim Deleskie, Tata
* Owen DeLong, Hurricane Electric
* David Divins, Carpathia Hosting
* Wes George, Sprint
* Gary Giesen, Advanced Knowledge Networks
* Chris Grundemann, TW Telecom
* Martin Hannigan, Akamai Technologies, Inc.
* William Herrin, ITT
* Scott Leibrand, Internap
* Andrew Mentges, Jumpline Inc
* John Springer, Inland Telephone
* Tom Zeller, Indiana University

Many of the candidates will address the membership on 6 October at
ARIN’s Public Policy and Members Meeting in Atlanta. These speeches,
brief biographies and a form to voice support for candidates can be
found online at ARIN Election Headquarters:

https://www.arin.net/app/election/

Good luck to all of the candidates, and thank you for your offer of service to the ARIN community.

RFC 5952: Recommended IPv6 Representation

Friday, August 20th, 2010

There’s a new IETF document published today, RFC 5952 “A Recommendation for IPv6 Address Text Representation”. It does us the favor of standardizing the text representation of IPv6 addresses, which is otherwise subject to various syntactically-correct yet inconsistent shorthands. To summarize the recommendation:

  • Handling Leading Zeros in a 16-Bit Field – Leading zeros MUST be suppressed.
  • Shorten as Much as Possible – The use of the symbol “::” MUST be used to its maximum capability.
  • Handling One 16-Bit 0 Field – The symbol “::” MUST NOT be used to shorten just one 16-bit 0 field.
  • Choice in Placement of “::”
    • When there is an alternative choice in the placement of a “::”, the longest run of consecutive 16-bit 0 fields MUST be shortened.
    • When the length of the consecutive 16-bit 0 fields are equal, the first sequence of zero bits MUST be shortened.
  • Lowercase – The characters “a”, “b”, “c”, “d”, “e”, and “f” in an IPv6 address MUST be represented in lowercase.

Broadband vs. Internet Speed: Not So Fast

Wednesday, August 18th, 2010

An email I received this afternoon contained a forwarded link to an article entitled “Conflating broadband speed with Internet speed is misleading“. The article makes a valid point that access capacity (“Broadband speed”) isn’t the same thing as end-to-end throughput (“Internet speed”). Clearly this difference is valuable for consumers to understand, and is a critically important distinction in the Network Neutrality debate.

Which is why I’m disappointed in the article; sadly, it oversimplifies the issue to the point of covering up critical details.  The comparison to fax technology is imperfect, maybe even flawed. It conjures an incorrect conclusion in the mind of a reader. And the material result of this is to avoid a discussion of provider responsibility for effective bandwidth.

To be clear, end-to-end throughput across a network is affected by everything in between the two hosts (computers) that are communicating. It is affected by the equipment, configurations, and interconnects. It is also affected by the capability of the transport protocols, round-trip latency, packet overhead, and more. In this regard, the article is correct to say that effective bandwidth shouldn’t be compared directly to broadband access capacity. But likewise, to compare the effective bandwidth to the coding rates of fax machines is a vast oversimplification.

Looking at the factors that might affect end-to-end performance, a number of those are directly in the hands of the network provider.  The access link (i.e. broadband connection) to the customer is just the first component.  It terminates in an edge / aggregation network that is probably oversubscribed.  The edge networks may be interconnected across a backbone, with its own bandwidth constraints and physical distance inefficiency.  And Internet connectivity, to the backbone or to the edge network directly, is enabled by a number of peering and/or transit connections that are not necessarily equal.  This isn’t even considering the possibility of NAT, security, or bandwidth management devices that might constrain effective throughput.

When all is accounted for, there may be a considerable oversubscription rate.  Not that oversubscription is inherently bad; most users aren’t using 100% of their bandwidth at the same moment in time, allowing the provider to time-multiplex their users without causing negative performance.  And this oversubscription allows the provider to make money in an otherwise low-margin business.  But because it’s hard to determine how oversubscribed a provider is, they’re often tempted to push costs lower by oversubscribing more.  (Which is evident when providers get irritated by increasing usage, such as P2P traffic, by their customers.)  Further, the Internet transit connections might be acquired on-the-cheap, offering lower quality network paths (read: more oversubscription, more latency).  And the effect of these choices directly accrues against end-to-end performance.

Now, to be clear, I’m not advocating regulation of how service providers build their networks.  It should be up to each business to determine for themselves what is an effective network topology, interconnect strategy, oversubscription rates, etc.  But to focus the entire network debate on the access connections while ignoring the complex network that interconnects those to the Internet is misleading.

ARIN 2010 Elections

Wednesday, August 4th, 2010

I’m pleased to be serving on the Nomination Committee (NomCom) for ARIN this year, helping identify the slate of candidates for the Board of Trustees and the Advisory Council elections. From the call for nominations:

ARIN is issuing an open call for General Members in good standing to nominate candidates for two (2) seats on the Board of Trustees, five (5) seats on the Advisory Council, and one (1) seat on the Number Resource Organization (NRO) Number Council that become open when current terms expire on 31 December 2010.

The Board of Trustees and Advisory Council election has a Nomination Committee (NomCom) that is responsible for identifying, recruiting, and certifying a properly selected slate of candidates to be placed in nomination before the membership for election. This year’s NomCom members are: Board of Trustee members Paul Andersen and Scott Bradner, Advisory Council members Heather Schiller and Bill Sandiford, and general member volunteers Bill Manning, Justin Clutter, and Benson Schliesser. Paul Andersen is serving as NomCom Chair.

New Board, Advisory Council, and NRO NC terms begin 1 January 2011. The two Board seats opening are held by Paul Vixie and Lee Howard. The five Advisory Council seats opening are currently held by: Cathy Aronson, Marla Azinger, Owen DeLong, Scott Leibrand, and Tom Zeller. ARIN Board and Advisory Council incumbents may be re-elected for consecutive terms. Jason Schiller’s seat for the NRO NC also became open this year. Please note that the NRO Number Council representatives now fulfill the role of ICANN’s ASO Address Council.

Nominations close on Monday 9 August at 17:00 (EDT, I believe) so act quickly if interested. For more information, please see https://www.arin.net/app/election/.

Level(3) Found God, Bought Metro Fiber

Wednesday, February 17th, 2010

I just read a great post on the Telecom Straight Shooter blog about Level(3)’s business.  Excerpt:

…all applications will originate and terminate in a metropolitan market with local access along with their associated revenues.  Long haul pipes are in vast quantity with plenty of inventory buried in the ground. In all fairness, however, if you are going to build a long haul network, you don’t undergo the expense to put only one pipe in the ground.

Metropolitan markets are 10x more expensive to build, operate and install than a long haul network. You actually require more fiber to be deployed in a metro setting in order to support stuffed, long haul dumb pipes from long haul networks dumping packets at a carrier hotel for metro distribution or third party interconnection facilities.