North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: The IESG Approved the Expansion of the AS Number Registry

  • From: Roland Dobbins
  • Date: Fri Dec 01 14:16:21 2006
  • Authentication-results: sj-dkim-8; [email protected]; dkim=pass (sig from verified; );
  • Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=948; t=1164998947; x=1165862947;c=relaxed/relaxed; s=sjdkim8002;h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;; [email protected];z=From:=20Roland=20Dobbins=20<[email protected]>|Subject:=20Re=3A=20The=20IESG=20Approved=20the=20Expansion=20of=20the=20AS=20Number=20Registry|Sender:=20;bh=coEk6ITJphwqmOZmZb++VkJGgB5HHgEix9w7g01SgwA=;b=hn/+ca1KDF6H/Rph4rcWI+fN17JNzHfvv1RiYo9EdK6sjo4wSkcWd4/FPPKYRofSKeWO81MpGdqakWOOJEbYhIjIQZ2wXnQdVxwTwU1WDa1phVprV2mjLpvG72aAeVls;

On Dec 1, 2006, at 4:50 AM, Andy Davidson wrote:

RIPE will be accepting requests for 32-bit ASNs from 1/1/07, according to an email to ncc-services two weeks ago. It does not feel too early to start to understand what we must do to as a community to guarantee ubiquity of reachable networks.
Is there any possibility we can now get a block of ASNs set aside for documentation purposes, akin to and/or the TEST network? A block of ASNs for this purpose would be very helpful for folks writing docs, would reduce the possibility of 'cut-and-paste hijacking', and would also allow more accurate documentation (many products and tools have special handling for the designated private ASNs which make documentation difficult).

Roland Dobbins <[email protected]> // 408.527.6376 voice

All battles are perpetual.

-- Milton Friedman