Differences between revisions 9 and 12 (spanning 3 versions)

IPv6 Addresses

Overview

This page acts as a registry to help manage subnet allocations within the 2001:4830:1248::/48 block which is reserved for PersonalTelco. See ["IPv6"] for background information.

History

Once upon a time, there was a long-running debate about the correct way of handling IPv6 addresses in the DNS, which mostly resulted in those addresses being left out of DNS entirely. That meant that you could generally only establish an IPv6 connection by using a literal address; this page was originally used to publish those literal addresses.

That debate has since reached a conclusion. In DNS, AAAA records with IPv6 addresses now sit alongside A records with IPv4 addresses, allowing transparent, automatic usage of IPv6 connections when possible. As a result, it is no longer necessary to use literal IPv6 addresses except in rare situations; likewise, it is no longer necessary to list literal addresses here.

Guidelines

This page should be managed much like to the NetworkAddressAllocations page which acts as a registry for the allocation of assorted IPv4 subnets for Portland-based IPv4 sites within a /16 block.

In contrast to the IPv4 allocations page, all addresses listed here are global-scope and must be routed at a central point. In other words, NetworkAddressAllocations is an authoritative registry, but this list should be considered more of a quick reference; the central router is the real authority.

Subnets

Node	Network (CIDR)	Tunnel (CIDR)
Reserved for CoreServer use	`2001:4830:1248::/64`
["NodeTB"]	`2001:4830:1248:1700::/64`	`2001:4830:1248::1700:1/112`
["NodeTB151"]	`2001:4830:1248:1740::/64`	`2001:4830:1248::1740:1/112`
["NodeLuckyLabNW"]	`2001:4830:1248:1800::/64`	`2001:4830:1248::1800:1/112`
["NodeEcotrust"]	`2001:4830:1248:2600::/64`	`2001:4830:1248::2600:1/112`
["NodeHawthorne"]	`2001:4830:1248:6400::/64`	`2001:4830:1248::6400:1/112`

Hosts

Host	Address (CIDR)
`donk`	`2001:4830:1248::/128`
`cornerstone`	`2001:4830:1248::1:1/112`
`bone`	`2001:4830:1248::2:1/112`
`spartan`	`2001:4830:1248::6:1/112`

CategoryDocumentation CategoryEducation CategoryMan CategoryNetwork CategoryDamnYouKeegan

-  ← Revision 9 as of 2007-09-02 14:10:07 →
  Size: 2567
  Editor: KeeganQuinn
  Comment: current info + more background
+  ← Revision 12 as of 2007-11-18 18:34:07 →
  Size: 2589
  Editor: solution
  Comment: more subnets
-Deletions are marked like this.
+Additions are marked like this.
 Line 6:
-== What and Why ==
+== Overview ==
 Line 8:
-This page contains PTP-related IPv6 addresses. See ["IPv6"] for background information.



Once upon a time, there was a long-running debate about the correct way of handling IPv6 addresses in the DNS, which mostly resulted in those addresses being left out of DNS entirely. That meant that you could generally only establish an IPv6 connection by using a literal address. That debate has since reached a conclusion; in DNS, `AAAA` records with IPv6 addresses now sit alongside `A` records with IPv4 addresses, allowing transparent, automatic usage of IPv6 connections when possible.



This page currently serves as a reflection of progress with the deployment of IPv6 in the context of Personal Telco.

It is no longer necessary to use literal IPv6 addresses except in rare situations, so they are generally not listed here after they have been recorded in the DNS.



See also the '''Formal Allocations''' section below.
+This page acts as a registry to help manage subnet allocations within the `2001:4830:1248::/48` block which is reserved for PersonalTelco. See ["IPv6"] for background information.
-Line 18:
+Line 11:
-== Servers ==
+== History ==
-Line 20:
+Line 13:
-All CoreServer systems are accessible via IPv6. Consult the DNS for current addresses.
+Once upon a time, there was a long-running debate about the correct way of handling IPv6 addresses in the DNS, which mostly resulted in those addresses being left out of DNS entirely. That meant that you could generally only establish an IPv6 connection by using a literal address; this page was originally used to publish those literal addresses.
-Line 22:
+Line 15:
-|| '''Host'''                      || '''Providers'''                         ||

|| `bone.personaltelco.net`        || ["6to4"] only                           ||

|| `cornerstone.personaltelco.net` || ["6to4"] only                           ||

|| `donk.personaltelco.net`        || [http://www.sixxs.net SixXS] + ["6to4"] ||
+That debate has since reached a conclusion. In DNS, `AAAA` records with IPv6 addresses now sit alongside `A` records with IPv4 addresses, allowing transparent, automatic usage of IPv6 connections when possible. As a result, it is no longer necessary to use literal IPv6 addresses except in rare situations; likewise, it is no longer necessary to list literal addresses here.
-Line 28:
+Line 18:
-== Nodes ==
+== Guidelines ==
-Line 30:
+Line 20:
-This section lists nodes which are known to provide IPv6 service.
+This page should be managed much like to the NetworkAddressAllocations page which acts as a registry for the allocation of assorted IPv4 subnets for Portland-based IPv4 sites within a `/16` block.



In contrast to the IPv4 allocations page, all addresses listed here are global-scope and must be routed at a central point. In other words, NetworkAddressAllocations is an authoritative registry, but this list should be considered more of a quick reference; the central router is the real authority.
-Line 33:
+Line 25:
-=== Formal Allocations ===
+== Subnets ==
-Line 35:
+Line 27:
-Eventually this page will be used as a registry for the allocation of `/64` subnets for Portland-based IPv6 sites within a `/48` block designated for this purpose. It will be managed much like to the NetworkAddressAllocations page which acts as a registry for the allocation of assorted IPv4 subnets for Portland-based IPv4 sites within a `/16` block.



In contrast to the IPv4 allocations page, all addresses listed here are global-scope and must be routed at a central point. In other words, NetworkAddressAllocations is an authoritative registry, while this list should be considered more of a quick reference; the central router is the real authority.
+|| '''Node'''                  || '''Network (CIDR)'''       || '''Tunnel (CIDR)'''          ||

|| Reserved for CoreServer use || `2001:4830:1248::/64`      ||                              ||

|| ["NodeTB"]                  || `2001:4830:1248:1700::/64` || `2001:4830:1248::1700:1/112` ||

|| ["NodeTB151"]               || `2001:4830:1248:1740::/64` || `2001:4830:1248::1740:1/112` ||

|| ["NodeLuckyLabNW"]          || `2001:4830:1248:1800::/64` || `2001:4830:1248::1800:1/112` ||

|| ["NodeEcotrust"]            || `2001:4830:1248:2600::/64` || `2001:4830:1248::2600:1/112` ||

|| ["NodeHawthorne"]           || `2001:4830:1248:6400::/64` || `2001:4830:1248::6400:1/112` ||
-Line 40:
+Line 36:
-=== Independent ===
+== Hosts ==
-Line 42:
+Line 38:
-These nodes provide IPv6 service independently, without the use of addresses or routes provided by Personal Telco.



|| '''Node'''    || '''Addresses + subnet bits'''        ||

|| ["NodeTB151"] || `2002:407a:c6a8:1::1/64` ||
+|| '''Host'''    || '''Address (CIDR)'''      ||

|| `donk`        || `2001:4830:1248::/128`    ||

|| `cornerstone` || `2001:4830:1248::1:1/112` ||

|| `bone`        || `2001:4830:1248::2:1/112` ||

|| `spartan`     || `2001:4830:1248::6:1/112` ||