|
Size: 1167
Comment: Document Node646
|
Size: 2567
Comment: current info + more background
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| '''IPv6 Address Allocations''' | = IPv6 Addresses = |
| Line 3: | Line 3: |
|
The most popular IPv6 tunnel broker seems to be http://www.freenet6.net/. Note that their tunnel routing servers are located in New York City, and may not be the most efficient endpoint. Contact KeeganQuinn if you're interested in a /64 with a Portland-based endpoint. Test your IPv6 connecivity by visiting http://www.ipv6.org/ - it will tell you if you're looking at that page over IPv4 or IPv6. This is a list of global scope IPv6 addresses for other PTP'ers to have some place interesting to reach on the "IPv6 Internet". |
[[TableOfContents]] |
| Line 10: | Line 6: |
|
|| Owner || IPv6 || Notes || || Don Park || 3ffe:b80:9ce:1::1/64 || || || KeeganQuinn || 3ffe:bc0:449:1::1/48 || Glad to delegate /64 subnets to nodes; over 65,000 available || || The Basement (["Node471"]) || 3ffe:bc0:449:471::1/64 || Delegation from KeeganQuinn || || CapposCafe (["Node491"]) || 3ffe:bc0:449:491::1/64 || Delegation from KeeganQuinn || || WSMF (["Node236"])|| 3ffe:bc0:449:236::1/64 || Delegation from KeeganQuinn || || ["Node646"] || 2001:5c0:8316::/48 || From ["Freenet6"] || |
== What and Why == |
| Line 18: | Line 8: |
| Also, don't forget NetworkAddressAllocations documents the PTP's IPv4 address space. |
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. == Servers == All CoreServer systems are accessible via IPv6. Consult the DNS for current addresses. || '''Host''' || '''Providers''' || || `bone.personaltelco.net` || ["6to4"] only || || `cornerstone.personaltelco.net` || ["6to4"] only || || `donk.personaltelco.net` || [http://www.sixxs.net SixXS] + ["6to4"] || == Nodes == This section lists nodes which are known to provide IPv6 service. === Formal Allocations === 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. === Independent === 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` || ---- CategoryDocumentation CategoryEducation CategoryMan CategoryNetwork CategoryDamnYouKeegan |
IPv6 Addresses
What and Why
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.
Servers
All CoreServer systems are accessible via IPv6. Consult the DNS for current addresses.
Host |
Providers |
bone.personaltelco.net |
["6to4"] only |
cornerstone.personaltelco.net |
["6to4"] only |
donk.personaltelco.net |
[http://www.sixxs.net SixXS] + ["6to4"] |
Nodes
This section lists nodes which are known to provide IPv6 service.
Formal Allocations
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.
Independent
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 |
CategoryDocumentation CategoryEducation CategoryMan CategoryNetwork CategoryDamnYouKeegan