- 該是正視IPv6的時候了
- As World Runs Out of IP Addresses, Switch to IPv6 Nears (New York Times)
- Steven J. Vaughan-Nichols, The next-generation Internet protocol IPv6 gets real, ZDNet, February 12, 2014.
- IP Address in China (APNIC 2004)
- Lucie Smith and Ian Lipner, "Free Pool of IPv4 Address Space Depleted". Number Resource Organization, 3 February 2011.
- RFC 1715 - The H Ratio for Address Assignment Efficiency
- [Lecture] IPv4 Exhaustion
![[PDF]](http://solomon.ipv6.club.tw/Images/pdf.gif)
(3.3MB)
- W. George, C. Donley, C. Liljenstolpe, and L. Howard, "IPv6 Support Required for All IP-Capable Nodes", BCP 177, RFC 6540, April 2012.
-
Microsoft Internet Protocol Version 6 (IPv6)
- IPv6 - Harvesting a Mature Technology, Brian E Carpenter, IBM, November 2006.
- IPv6 at IBM
- [Video] IPv6 - Google
- [Flash] The History of the RIRs
- [YouTube] Expanding the Internet: From IPv4 to IPv6
- [Flash] APNIC IPv6 Informational Multimedia
- APNIC IPv6 Program
- 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 (RFC2050), November 1996.
- RFC 3194 - The Host-Density Ratio for Address Assignment Efficiency (An update on the H ratio)
- RFC 4692 - Considerations on the IPv6 Host Density Metric (HD-Ratio)
- Cost of Static IPv4 Address
- IP Masquerade and Network Address Translation
- 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.
- W. Stallings, IPv6: the new Internet protocol, IEEE Communications Magazine, Vol. 34, No. 7, pp.96-108, Jul. 1996. doi:10.1109/35.526895
- RFC 7126 - Recommendations on Filtering of IPv4 Packets Containing IPv4 Options
- IPv6 header format
- Wireshark filter
- C struct in handling pcap files
- Q: What will happen for SLAAC if my address is occupied by someone else?
- IPv6 Addressing
[ (341KB)]
-
RFC 4291
(obsoleted
RFC 3513)
- IPv6 Addressing Architecture
- IPv4-compatible address is deprecated.
- RFC 5952 - A Recommendation for IPv6 Address Text Representation
- RFC 4007 - IPv6 Scoped Address Architecture
- RFC 7136 - Significance of IPv6 Interface Identifiers (Updates RFC 4291)
- RFC 3041 - Privacy Extensions for Stateless Address Autoconfiguration in IPv6 (Obsoleted by RFC 4941)
- RFC 4941 - Privacy Extensions for Stateless Address Autoconfiguration in IPv6 (Obsolete RFC 3041)
- RFC 3587 - IPv6 Global Unicast Address Format
- RFC 3177 - Recommended IPv6 Addressing Allocation
- RFC 3849 - IPv6 Address Prefix Reserved for Documentation (2001:DB8::/32)
-
RFC 5737 - IPv4 Address Blocks Reserved for Documentation
- 192.0.2.0/24
- 198.51.100.0/24
- 203.0.113.0/24
- 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.
- 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
- Ibrahim Haddad,
"Linux
IPv6: which one to deploy?", Linux Journal, Volume 2002
Issue 96, April 2002.
- Although the conclusion is outdated, the University of New Hampshire InterOperability Lab IPv6 Test Description document it mentioned is worthy of a look if you want to develop your own IPv6 stack.
- T. Narten, "Neighbor discovery and stateless autoconfiguration in IPv6", IEEE Internet Computing, Vol. 3 No.4, pp.54-62, July/August 1999.
- IEEE OUI MAC address
(394KB)]
- H. Esaki, IPv6 integration and coexistence strategies for next-generation networks, IEEE Communications Magazine, Vol. 42, No. 1, pp.88-96, Jan. 2004. doi:10.1109/MCOM.2004.1262167
- D. G. Waddington, Realizing the transition to IPv6, IEEE Communications Magazine, Vol. 40, No. 6, pp.138-147, June 2002. doi:10.1109/MCOM.2002.1007420
- 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.
- Implementing Tunneling for IPv6, Cisco.
- [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
- RFC 5572 - IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP)
- [Lab] Configuration Guide of Tunnel Broker
- HiNet IPv6 Tunnel Broker (gogo6CLIENT)
- Tunnel
Broker in ASCC
- Download gogoCLIENT from Hexago
- Connect to the Tunnel Broker tb2.ipv6.ascc.net, because anonymous.freenet6.net is in Canada.
- SixXS - IPv6 Tunnel Broker
- Tunnel Broker List for IPv6 Day
- Tunnel Brokers which require end points to possess public IPv4 addresses:
- [Lab] 6to4 Tunnel
- RFC 3056 - Connection of IPv6 Domains via IPv4 Clouds
- 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
- IPv6 Forum Roadmap & Vision 2010
- Translation
- [Internet Draft] Yamagata, I., Shirasaki, Y., Nakagawa, A., Yamaguchi, J., and H. Ashida, "NAT444", draft-shirasaki-nat444-06, July 2012. (local copy)
- RFC 6269 - Issues with IP Address Sharing
- RFC 7021 - Assessing the Impact of Carrier-Grade NAT on Network Applications
- RFC 3596 - DNS Extensions to Support IP Version 6
- The IP protocol version used for querying resource records is independent of the protocol version of the resource records; e.g., IPv4 transport can be used to query IPv6 records and vice versa.
- RFC 3152 - Delegation of IP6.ARPA (Obsoleted by RFC 3596)
- RFC 1886 - Delegation of IP6.INT (Obsolete by RFC 3596)
- (HISTORIC) RFC 2874 - DNS Extensions to Support IPv6 Address Aggregation and Renumbering
- RFC 6563 - Moving A6 to Historic Status
- RFC 6106 - IPv6 Router Advertisement Options for DNS Configuration
- IPv6 AAAA DNS Whitelisting Implications draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
- Ringline IPv6 DNS 設定解說 (local copy)
- Microsoft TechNet Recursive and Iterative Queries
- [Lab] DNS Entries for IPv6
- [Lab] Dynamic DNS (DDNS)
- Jun-ichiro itojun Hagino, IPv6 Network Programming
- Linux Network Programming, Part 1, Linux Journal, 1998.
- RFC 3484 - Default Address Selection for IPv6
- RIPng
- OSPFv3
- BGPv4
-
RFC 3068
- An Anycast Prefix for 6to4 Relay Routers
- 192.88.99.1
- Multicast
- RFC 2375 - IPv6 Multicast Address Assignments
- D. Thaler, M. Handley, D. Estrin, "The Internet Multicast Address Allocation Architecture", IETF RFC 2908, September 2000.
- RFC 3810 - Multicast Listener Discovery Version 2 (MLDv2) for IPv6
- B. Haberman, "Allocation Guidelines for IPv6 Multicast Addresses", IETF RFC 3307, August 2002.
- IPv4 Multihoming Practices and Limitations (RFC 4116)
- Architectural Approaches to Multi-Homing for IPv6 (RFC 4177)
- Threats relating to IPv6 Multihoming Solutions (RFC 4218)
- Things MULTI6 Developers Should Think About (RFC 4219)
- RFC 7123 - Security Implications of IPv6 on IPv4 Networks
- Implementing First Hop Security in IPv6, Cisco
- Implementing IPsec in IPv6 Security, Cisco.
- RFC 3972 - Cryptographically Generated Addresses (CGA)
- RFC 3964 - Security Considerations for 6to4
- 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
- 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
- Ryan Measel, IPv6 Compression Techniques and Performance, Master Thesis, Drexel University, February 2011.
- RFC 4944
- RFC 6282
- Caldeira, J.M.L.P. ; Rodrigues, J.J.P.C. ; Lorenz, P. Toward ubiquitous mobility solutions for body sensor networks on healthcare, IEEE Communications Magazine, Vol. 50, No. 5, pp.108-105, May 2012. doi:10.1109/MCOM.2012.6194390
- Fadlullah, Z.M. ; Fouda, M.M. ; Kato, N. ; Takeuchi, A. Toward intelligent machine-to-machine communications in smart grid, IEEE Communications Magazine, Vol. 49, No. 4, pp.60-65, April 2011. doi:10.1109/MCOM.2011.5741147
- Jun Zheng, D. Simplot-Ryl, C. Bisdikian and H.T. Mouftah, The Internet of Things, IEEE Communications Magazine, Vol. 49, No. 11, pp.30-31, November 2011. doi:10.1109/MCOM.2011.6069706
- Ganti, R.K. ; Fan Ye ; Hui Lei Mobile crowdsensing: current state and future challenges, IEEE Communications Magazine, Vol. 49, No. 11, pp.32-39, November 2011. doi:10.1109/MCOM.2011.6069707
- Gluhak, A. ; Krco, S. ; Nati, M. ; Pfisterer, D. A survey on facilities for experimental internet of things research, IEEE Communications Magazine, Vol. 49, No. 11, pp.58-67, November 2011. doi:10.1109/MCOM.2011.6069710
- Pan, J. ; Paul, S. ; Jain, R. A survey of the research on future internet architectures, IEEE Communications Magazine, Vol. 49, No. 7, pp.26-36, July 2011. doi:10.1109/MCOM.2011.5936152
- JeongGil Ko, Connecting low-power and lossy networks to the internet, IEEE Communications Magazine, Vol. 49, No. 4, pp. 96-101, April 2011. doi:10.1109/MCOM.2011.5741163
- Aminul Haque Chowdhury, Route-over vs mesh-under routing in 6LoWPAN, Proceedings of the 2009 International Conference on Wireless Communications and Mobile Computing (IWCMC '09), pp. 1208-1212 , New York, USA, 2009.
- E. Kim, D. Kaspar, C. Gomez and C. Bormann, Problem Statement and Requirements for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Routing, RFC 6606, May 2012
