- As World Runs Out of IP Addresses, Switch to IPv6 Nears (New York Times)
- The History of the RIRs (Flash)
- Expanding the Internet: From IPv4 to IPv6 (YouTube)
- IPv4 Exhaustion
![[PDF]](http://solomon.ipv6.club.tw/Images/pdf.gif)
(3.3MB)
- IP Address in China (APNIC 2004)
- Statistics of IPv4 & IPv6 Allocation (TWNIC)
- Y. Rekhter, T. Li, "An Architecture for IP Address Allocation with CIDR", IETF RFC 1518, September 1993.
- Y. Rekhter, "CIDR and Classful Routing, IETF RFC 1817, August 1995.
- K. Hubbard, M. Kosters, D. Conrad, D. Karrenberg, J. Postel, "Internet Registry IP Allocation Guidelines", IETF BCP0012, November 1996.
- RFC 1715 - The H Ratio for Address Assignment Efficiency
- RFC 3194 - The Host-Density Ratio for Address Assignment Efficiency (An update on the H ratio)
- RFC 3022 - Traditional IP Network Address Translator
(Traditional NAT)
- This document describes the mechanism of Basic NAT (Network Address Translator) and NAPT (Network Address Port Translation). It includes sample code for checksum adjustment of TCP/UDP/IP/ICMP.
- RFC 2993 - Architectural Implications of NAT
- RFC 2663 - IP Network Address Translator (NAT) Terminology and Considerations
- RFC 3235 - Network Address Translator (NAT)-Friendly Application Design Guidelines
- D. McPherson, B. Dykes, "VLAN Aggregation for Efficient IP Address Allocation, IETF RFC 3069, February 2001.
-
RFC 1918 - Address Allocation for Private Internets (BCP 5)
Internet Assigned Numbers Authority (IANA) has three blocks of IP address space for private networks- 10.0.0.0/8 (a single class A network)
- 172.16.0.0/12 (16 contiguous class B networks)
- 192.168.0.0/16 (256 contiguous class C networks)
- [Lab] Building your NAT box
- RFC 3927 - IPv4 Link Local 169.254/16 (Apple/Microsoft/Sun)
- RFC 3330 - Special-Use IPv4 Addresses
- RFC 1958 - Architectural Principles of the Internet
- RFC 2775 - Internet Transparency
(3.1MB)]
- Internet Society, A Brief History of the Internet and Related Networks
- Robert M. Hinden, "IP next generation overview", Communications of the ACM, Volume 39 , Issue 6 (June 1996), pp. 61 - 71.
- IPv6 Addressing
[ (341KB)]
-
RFC 4291
(obsoleted
RFC 3513)
- IPv6 Addressing Architecture
- IPv4-compatible address is deprecated.
- RFC 4007 - IPv6 Scoped Address Architecture
- RFC 3587 - IPv6 Global Unicast Address Format
- RFC 3177 - Recommended IPv6 Addressing Allocation
- RFC 4692 - Considerations on the IPv6 Host Density Metric (HD-Ratio)
- RFC 3849 - IPv6 Address Prefix Reserved for Documentation (2001:DB8::/32)
- RFC
3879 - Deprecating Site Local Addresses
- The idea of a "site" is vague.
- Consider a multi-homed site.
- Consider mobile hosts, which can be successively connected to multiple sites.
- RFC 4193 -
Unique Local IPv6 Unicast Addresses
- Site border routers and firewalls should be configured to not forward any packets with Local IPv6 source or destination addresses outside of the site.
- The default behavior of these devices should be to install a "reject" route for these prefixes.
- D. Thaler, M. Handley, D. Estrin, "The Internet Multicast Address Allocation Architecture", IETF RFC 2908, September 2000.
- B. Haberman, "Allocation Guidelines for IPv6 Multicast Addresses", IETF RFC 3307, August 2002.
- IAB, "IAB/IESG Recommendations on IPv6 Address Allocations to Sites, IETF RFC 3177, September 2001.
- R. Fink, R. Hinden, "6bone (IPv6 Testing Address Allocation) Phaseout", IETF RFC 3701, March 2004.
- IPv6 Unicast Address Assignments in IANA
- IEEE OUI MAC address
- T. Narten, "Neighbor discovery and stateless autoconfiguration in IPv6", IEEE Internet Computing, Vol. 3 No.4, pp.54-62, July/August 1999.
(394KB)]
- RFC 1671 - IPng White Paper on Transition and Other Considerations.
- RFC 4213 - Transition Mechanisms for IPv6 Hosts and Routers. (Dual Stack and Configured Tunnel) (Obsoletes RFC 2893)
- RFC 2185 - Routing Aspects of IPv6 Transition
- RFC 3750 - Unmanaged Networks IPv6 Transition Scenarios
- RFC 3904 - Evaluation of IPv6 Transition Mechanisms for Unmanaged Networks.
- RFC 4038 - Application Aspects of IPv6 Transition.
- RFC 5211 - An Internet Transition Plan
- RFC 1853 - IP in IP Tunneling
- [Lab] Confiuring IPv6 TUnnels and
Routing Table on Windows XP, Utunbu Linux, FreeBSD by Miss
Kuljaree from PSU, Thailand.
- Windows 7: Suppose the following is the network topology.
+-------+ Host 1 | | Host 2 2001::F ----- 2001::E + Router+ 2001::C ----- 2001::D | | +-------+
- netsh interface ipv6
- add v6v4tunnel "T1" (Host IPv4 address) (Router addr)
- add address "T1" 2001::F
- add route 2001::C/127 "T1"
- If Host 2 does not respond to ICMPv6 Echo Request (this can
be verified from the Router), on Windows 7 you can run
Control Panels - Windows Firewall - Advanced Settings, then
choose Inbound rule - New Rule - Custom - All programs -
Protocol type: ICMPv6.
- Remark: Probably you don't need to create a new rule. Locate the Inbound Rules for "File and Printer Sharing (Echo Request - ICMPV6-in), and enable the ones corresponding to "Domain" and "Public".
- Windows 7: Suppose the following is the network topology.
- [Lab] Create IPv6 Tunnels Manually.
- Group students into groups. Each group has 3 or 4 students.
- Discuss the IPv6 address assignment policy in your group.
- Configure your computers to establish IPv6 tunnels between each pair of computers in your group.
- There is no routing protocol yet, so you have to establish IPv6 tunnels between each pair of computer.
- Try to ping each other.
- Remember that there may be hosts under your router.
- RFC 5214 - Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
- RFC 3053 - IPv6 Tunnel Broker
- [Lab] 6to4 Tunnel
- RFC 3056 - Connection of IPv6 Domains via IPv4 Clouds
-
RFC 3068
- An Anycast Prefix for 6to4 Relay Routers
- 192.88.99.1
- Briefing of NCU IPv6 6to4 Tunnel (local copy), A IPv6 Aware/pass-thru NAT for Rapid Deployment and Transition (TANet 2010 paper)
- Y. Hei and K. Yamazaki, " Traffic analysis and worldwide operation of open 6to4 relays for IPv6 deployment", Proceedings of 2004 International Symposium on Applications and the Internet (SAINT 2004), pp.265-268.
- RFC 6343 - Advisory Guidelines for 6to4 Deployment
- [Internet Draft] Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status draft-ietf-v6ops-6to4-to-historic-03
-
Microsoft Internet Protocol Version 6 (IPv6)
- IPv6 - Harvesting a Mature Technology, Brian E Carpenter, IBM, November 2006.
- IPv6 Forum Roadmap & Vision 2010
- Translation
- DNS Issues:
- RFC 3596 - DNS Extensions to Support IP Version 6
- RFC 2874 - DNS Extensions to Support IPv6 Address Aggregation and Renumbering
- RFc 3152 - Delegation of IP6.ARPA (Obsoleted by RFC 3596)
- IPv6 AAAA DNS Whitelisting Implications draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
- Socket Programming in Java
- socketClient.java
- socketServer.java
- Linux Network Programming, Part 1, Linux Journal, 1998.
- RFC 3484 - Default Address Selection for IPv6
- IETF Introduction
- S. Bradner, "The Internet Standards Process", IETF BCP 0009, October 1996.
- RFC 2223 - Instructions to RFC Authors.
- Formats of an RFC document.
- BCP 22 - Guide for Internet Standards Writers
- Characteristics that make standards coherent, unambiguous, and easy to interpret
- Implementing IPSec in IPv6 Security, Cisco.
- Securing with IPsec on IPv6 Networks, Microsoft.
- RFC 4218 - Threats Relating to IPv6 Multihoming Solutions
- RFC 4891 - Using IPsec to Secure IPv6-in-IPv4 Tunnels
