Listed below are some Points of Contact (PoCs) for United States (US) government organizations, Department of Defense (DoD) organizations, and non-government organizations including open source communities, standards development organizations (SDOs), and software development organizations (SWDOs) engaged in planning for, analyzing or deploying Internet Protocol version 6 (IPv6) networks or network infrastructure and/or developing, planning to deploy, or deploying Internet of Things (IoT) devices.
Not listed below are websites containing information answering frequently asked questions (FAQs) about topics related to IPv6 and IoT. However, such websites are listed in the IPv6 and IoT Frequently Asked Questions article.
An SWDO is an organization formed by one or more interested individuals, non-commercial organizations and commercial companies. SDOs are similar to SWDOs in many organizational aspects, but their purposes are quite different. The purpose of an SDO is to develop, publish and maintain standards and policies within a defined scope of responsibility. One purpose of an SWDO is to develop, publish, maintain, and possibly even promote the use of software (or devices and related software) within a defined scope of responsibility, and (for a few SWDOs) another purpose is to function as an SDO for that software. An SWDO may have additional purposes that are not limited to software development. The scope of any SDO or SWDO may be self-defined or their scope may be defined by a higher-level organization.
These POCs may be contacted to ask questions about and discuss issues involved in IPv6 planning, analyzing and deployment efforts or IoT developing, planning and deployment efforts. This list is not intended to be either authoritative or exhaustive.
Reminder: This information is not to be used for commercial purposes, such as promotion of products or services.
| Name | Website | Contact |
|---|---|---|
| US Federal Government | ||
| Chief Information Officers (CIO) Council Federal IPv6 Task Force |
home page (Authentication Required) |
fedv6-deploy+subscribe [at] list.nist.gov |
| Earlier Federal IPv6 (Fedv6) Task Force |
Meetings until March 2013 (Authentication Required)
|
|
| Federal IPv6 Transition Managers |
See CIO Council Federal IPv6 Task Force (above)
|
|
| Federal IPv6 Inter-Agency Working Group |
See CIO Council Federal IPv6 Task Force (above)
|
|
| General Services Administration | https://www.gsa.gov/technology/technology-products-services/it-security/internet-protocol-version-6-ipv6 |
ITCSC [at] gsa.gov |
| National Institute of Standards and Technology (NIST) | https://www.nist.gov/programs-projects/usgv6-program | usgv6-program [at] nist.gov |
|
Trusted Internet Connection (TIC) working group |
https://community.max.gov/display/Egov/Trusted+Internet+Connections |
tic [at] cisa.dhs.gov |
| Department of Defense | ||
| DREN IPv6 Team | ipv6-team [at] dren.mil | |
| DoD IPv6 Transition Crossroads |
https://intellipedia.intelink.gov/wiki/DoD_IPv6_Transition_Crossroads (Authentication Required) (no activity since 2012) |
|
| Army | ||
| Army IPv6 Transition Planning Office |
https://www.milsuite.mil/wiki/IPV6 (DoD PKI Required) (no activity since 2014) |
CIO/G6IPv6Team [at] hqda.army.mil |
| Navy | ||
| Navy IPv6 Steering Group (NISG) |
https://intellipedia.intelink.gov/wiki/Navy_IPv6 (Authentication Required) (no activity since 2014) |
Navy.IPv6.fcm [at] navy.mil |
| Air Force | ||
| Air Force IPv6 Transition Management Office (TMO) |
https://www.milsuite.mil/book/groups/ipv6-transition-management-office (DoD PKI Required) (no activity since 2014) |
afca.ipv6 [at] us.af.mil |
| Non-government Organizations | ||
| Open Source Communities | ||
| Alliance of Internet of Things Innovation | https://aioti.eu/ | Join Us |
| Cloud Native Computing Foundation (CNCF) | https;//www.cncf.io/ | Contact Us |
| Hurricane Electric Forum | https://forums.he.net/ | (None) |
| Industry IoT Consortium | https://www.iiconsortium.org/ | info [at] iiconsortium.org |
| Internet of Things Security Foundation (IoTSF) | https://www.iotsecurityfoundation.org/ | Contact Us |
| Internet2 IPv6 Working Group | https://lists.internet2.edu/sympa/info/wg-ipv6 | wg-ipv6 [at] internet2.edu |
| LinkedIn,com Groups | https://linkedin.com | After login, look though the "groups You May Like" |
| MicroSoft TechNet IPv6 Forum | https://learn.microsoft.com/en-us/search/?terms=ipv6 | (None) |
| North American Network Operators Group (NANOG) Best Current Operational Practice (NABCOP) | http://nabcop.org/ (NABCOP is defunct. Website is for reference.) | (None) |
| Rocky Mountain IPv6 Task Force (RMv6TF) |
https://www.rmv6tf.org (RMv6TF is defunct. Website is for reference.) |
https://www.rmv6tf.org/contact-us |
| Security By Design IoT Development and Certificate Framework with Front-end Access Control (IoTaC) | IoTAC | Contact |
| Standards Development Organizations | ||
| American Registry for Internet Numbers (ARIN) | https://www.arin.net | hostmaster [at] arin.net |
| Connectivity Standards Alliance (CSA-IOT) (formerly the Zigbee Alliance) | https://csa-iot.org/ | Contact |
| The European Telecommunications Standards Institute (ETSI) | https://www.etsi.org/ | info [at] etsi.org |
| Industry Network Technology Council | https://industrynetcouncil.org | Fill in the Contact Us form and click on Submit |
| Industry Specification Group on IPv6 Enhanced Innovation (ISG on IPE), under the auspices of ETSI | https://www.etsi.org/committee/1424-ipe | Isgsupport [at] etsi.org |
| Institute of Electrical and Electronic Engineers (IEEE) Internet of Things (IOT) | https://iot.ieee.org/ | Contact IEEE IOT |
| Internet Architecture Board (IAB) | https://www.iab.org | https://www.iab.org/iab-mailing-lists/ (Displays IAB mailing lists) |
| Internet Engineering Task Force (IETF) | https://www.ietf.org/ | https://www.ietf.org/contact/ |
| Internet of Things Privacy Forum | https://www.iotprivacyforum.org/ | Click on Contact and fill out the form |
| IoT Security Initiative | https://www.iotsi.org/ | At the bottom of the Overview page, complete the Contact form and submit |
| IPv6Forum | http://www.ipv6forum.org | (none) |
| Internet Society (ISOC) | https://www.internetsociety.org | https://www.internetsociety.org/contact-us |
| Mutually Agreed Norms for Routing Security (MANRS) | https://www.manrs.org/ | Contact |
| OMA Specworks IOT | https://omaspecworks.org/ | Contact Us |
| Open Connectivity Foundation (OCF) | https://openconnectivity.org/ | On the Contact Us web page, complete the form, check the Email Consent box, and click on SUBMIT |
| Software Development Organizations | ||
| Groupe Spécial Mobile (GSM) Association (GSMA) Internet of Things | https://www.gsma.com/iot | Scroll down to the Contact Us box, click on the Email icon, and send an email |
| Next Generation Internet of Things (NGIoT) | https://www.ngiot.eu/ | On the Contact web page, complete the form, check the Email Consent box, and click on SEND |
| Thread Group | https://www.threadgroup.org/ | JOIN |
This article provides an overview of 2 broad categories of networking standards: Internet Protocols (IP) and Internet of Things (IoT) protocols.
1. Internet Protocols
The authoritative source for technical standards related to IP, both IP version 4 (IPv4) and IPv6, is embodied in a set of Request for Comments (RFC) documents produced by the Internet Engineering Task Force (IETF) standards development organization (SDO), as described in these IETF RFCs:
- RFC 8711 Structure of the IETF Administrative Support Activity, Version 2.0 and
- RFC 8712 The IETF-ISOC Relationship.
Other internet standards organizations operate under the auspices of the Internet SOCiety (ISOC).
The IETF maintains a website of technical reference documents for both IPv4 and IPv6, including:
- RFC 3901 DNS IPv6 Transport Operational Guidelines,
- IETF draft document DNS IPv6 Transport Operational Guidelines,
- RFC 5952 A Recommendation for IPv6 Address Text Representation,
- RFC 6540 IPv6 Support Required for All IP-Capable Nodes requiring that all new products must support IPv6 and updates to existing products should support IPv6. This RFC further requires that IPv6 support must be equivalent or better in quality and functionality when compared to IPv4 support,
- RFC 6877 464XLAT: Combination of Stateful and Stateless Translation,
- RFC 8200 Internet Protocol, Version 6 (IPv6) Specification announcing that IPv6 was an internet standard,
- IETF draft document A Simple BGP-based Mobile Routing System for the Aeronautical Telecommunications Network,
- RFC 8504 IPv6 Node Requirements defining common functionality required in all routers and other network devices that support IPv6,
- RFC 8683 Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise Networks,
- RFC 8925 IPv6-Only-Preferred Option for DHCPv4 allowing IPv4-enabled and IPv6-only nodes to co-exist on a local area network, and
- IETF proposed standard RFC 9673 IPv6 Hop-by-Hop Options Processing Procedures specifies procedures for processing IPv6 Hop-by-Hop options in IPv6 routers and hosts.
In addition to SDOs in the United States (US), there are a number of international networking SDOs, including the European Telecommunications Standards Institute (ETSI) and the European Association for Standardizing Information and Communication Systems (ECMA). ETSI maintains a set of IPv6-related standards here, and a number of technical groups including Software Development Groups (SDG). ECMA maintains a set of data communications standards here.
The Réseaux IP Européens (RIPE) Network Coordination Centre (NCC) is one of five Regional Internet Registries (RIRs). It maintains a listing of policy documents followed by the Internet Assigned Numbers Authority (IANA) and the five RIRs. Policy documents on that listing which contain the word RIPE in the title apply only to the RIPE NCC RIR while policy documents on that listing without the word RIPE in the title apply to the IANA, the RIPE NCC RIR and the other four RIRs.
The Broadband Forum, which is an organization encompassing a wide range of Digital Subscriber Line- (DSL), Asynchronous DSL- (ADSL), and Internet Protocol/Multi-Protocol Label Switching- (IP/MPLS) networking devices, maintains IPv6-related technical reports here. In particular, see Technical Reports (TR) TR-124 Issue 9, TR-177 Issue 1 Corrigendum 1, TR-181 Issue 2 Amendment 19 Corrigendum 1, and TR-187 Issue 2 comprising BroadbandSuite 7.0 release, Dec, 2014 (also referred to as the IPv6 Toolkit, according to this press release), as well as TR-242 Issue 2, Feb 2015, and TR-296, Nov 2013.
2. Internet of Things (IoT) Protocols
This article provides a wide-ranging overview of IoT-related protocols and standards.
The IETF has published:
- RFC 4919 IPv6 over Low-Power Wireless Personal Area Networks (6LowPANs): Overview, Assumptions, Problem Statement, and Goals,
- RFC 4944 Transmission of IPv6 Packets over IEEE 802.15.4 Networks,
- RFC 6282 Compression Format for IPv6 Datagrams over IEEE 802.15.4l-Based Networks,
- RFC 6550 RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks,
- RFC 7252 Constrained Application Protocol,
- RFC 7925 Transport Layer Security (TLS)/Datagram Transport Layer Security (DTLS) Profiles for the Internet of Things,
- RFC 8025 IPv6 over Low-Power Wireless Personal Area Network (6LowPAN) Paging Dispatch,
- RFC 8138 IPv6 over Low-Power Wireless Personal Area Network (6LowPAN) Routing Header,
- RFC 8505 Registration Extensions for IPv6 Over Low-Power Wireless Personal Area Networks (6LoWPAN) Neighbor Discovery,
- RFC 8520 Manufacturer Usage Descriptions (MUD) Specification,
- RFC 8576 Internet of Things Security: State of the Art and Challenges,
- RFC 8655 Deterministic Networking Architecture,
- RFC 8928 Address-Protected Neighbor Discovery for Low-Power and Lossy Networks,
- RFC 8930 On Forwarding 6LowPAN Fragments over a Multi-Hop IPv6 Network,
- RFC 8931 IPv6 over Low-Power Wireless Personal Area Network (6LowPAN) Selective Fragment Recovery,
- RFC 9006 TCP Usage Guidance in the Internet of Things (IoT),
- RFC 9008 Using RPI Option Type Routing Header for Source Routes, and IPv6-in-IPv6 Encapsulation in the RPL Data Plane,
- RFC 9010 Routing for RPL (Routing Protocol for Low-Power and Lossy Networks) Leaves,
- RFC 9011 Static Context Header Compression and Fragmentation (SCHC) over LoRaWAN,
- RFC 9019 A Firmware Update Architecture for the Internet of Things,
- RFC 9030 An Architecture for IPv6 over the Time-Slotted Channel Hopping Mode of IEEE 802.15.4 (6TiSCH),
- RFC 9685 Listener Subscription for IPv6 Neighbor Discovery Multicast and Anycast Addresses,
- IETF draft document Reliable and Available Wireless Architecture, and
- IETF draft document Architecture Based on IPv6 and 5G for IIOT.
The IETF also maintains an IoT Topics of interest website, a blog post of IoT-related current efforts, and a blog post of MUD-related current efforts.
Wikipedia articles survey the rapidly growing Industrial Internet of Things (IIoT) and the Internet of Military Things (IoMT), sometimes referred to as the Military Internet of Things (MIoT), the Internet of Battle Things (IBT), or the Internet of Battlefield Things (IoBT).
ETSI maintains a series of Internet of Things (IoT) related standards documents.
The ECMA Technical Committee 53 (EC53) is developing and has published standards enabling the use of Javascript on IoT devices.
Individuals have also developed IoT Javascript Frameworks.
(Note: If you are just starting to think about deploying Internet Protocol version 6 (IPv6) or are still in the pre-planning phases of an IPv6 deployment, please review the Before you Begin article in the Deployment section. This will help you better understand the information provided below.)
This Overview of Lessons Learned article contains five major topics:
- Lessons learned by Organizations from countries around the world,
- Defense Research and Engineering Network (DREN) IPv6 Pilot lessons learned summaries
- DREN IPv6 Pilot lessons learned details,
- Recipients of DREN IPv6 Pilot lessons learned, and
- Lessons learned from protocol transitions prior to IPv4.
While not limited to the topic of deploying IPv6, the article 8 Lessons from 20 Years of Hype Cycles provides lessons that are relevant to the topic of deploying IPv6. Through repeated successful reuse, lessons learned become recognized as best practices that are known to produce good outcomes when followed. Some best practices are described in documents listed in the United States (US) IPv6 and IoT Policy, Guidance, and Best Practices and Non-United States IPv6 and IoT Policy, Guidance, and Best Practices articles in the General Information section. Additional best practices with an emphasis on security are described in documents in the IPv6 and IoT Security Best Practices article in the Security section.
1. Lessons learned by Organizations.
No attempt has been made to extract lessons learned by organizations that have deployed IPv6. Instead, references to original presentations, papers, studies, publications, and articles are referenced so that the lessons learned can be understood in context.
Materials referenced in this topic come from a wide variety of sources, including conference presentations, research papers, industry studies, commercial provider publications, and news media. These materials are grouped into ten subtopics:
- United States (US) Department of Defense (DoD) Organizations
- Other US Federal Government Organizations
- Networking Equipment Manufacturers, Services, and Customers
- IPv6 Internet Service Providers (ISPs)
- Academic Community
- Standards Development Organizations (SDOs) and Software Development Organizations (SWDOs)
- Non-commercial Organizations
- European and Asian IPv6 Communities
- Caribbean and Latin American Communities
- Australian IPv6 Community
- The Small Office/Home Office (SOHO)
Note: The majority of the transitions referenced in this topic were from an IPv4 (only) networking infrastructure to a dual-stack (both IPv6 and IPv4) networking infrastructure. However, a few transitions listed in subtopics 3 through 6 and subtopic 10 describe an IPv4 (only) networking infrastructure transition to an IPv6 (only) networking infrastructure.
Reports produced by the Offices of the Inspector Generals (OIG) or Government Accountability Offices (GAO) for various US government organizations referenced in the IPv6 and IoT Policy, Guidance, and Best Practices article in the General Information section also sometimes provide lessons learned. The IPv6 Network Testing Results article in the Testing section provides some lessons learned while testing IPv6 networks. The SDN Lessons Learned, Training, and Testing article in the SDN Knowledge Base section provides some lessons learned while deploying Cloud Computing using IPv6-enabled Software Defined Networking virtualization technology.
| Source | Date | Title |
|---|---|---|
|
Air Force Network Integration Center |
2012 | How the Air Force is Flying Toward IPv6 |
|
|
2012 |
|
|
Applied Research Associates, Inc. |
2009 |
|
|
DREN |
2010 |
|
|
2015 |
||
|
Defense Threat Reduction Agency |
2013 |
|
| United States Naval Academy (USNA) | 2008 | Lessons Learned in Transitioning from IPv4 to IPv6 |
1.2 Other US Federal Government Organizations.
| Source | Date | Title |
|---|---|---|
| Department of Commerce (DoC) | 2006 | Technical and Economic Assessment of Internet Protocol version 6 (IPv6) |
|
Environmental Protection Agency (EPA) |
2018 |
EPA Committed to Finding a Workaround for Every IPv6 Challenge |
|
Federal Aviation Agency (FAA) |
2011 |
|
|
Federal IPv6 (Fedv6) Task Force |
quarterly |
on-going series of Face to Face (F2F) meetings (registration required) |
|
Internal Revenue Service (IRS) |
2007 |
Government Empowering and Embracing the Kickoff of IPv6 (G.E.E.K.V.6) Invitation |
|
2007 |
G.E.E.K.V.6 Day (slides 41-117) |
|
|
2015 |
||
|
National Aeronautics and Space Administration (NASA) |
2013 |
|
| Office of Government Ethics | 2016 | OGE – IPv6 Deployment (Authentication Required) |
|
Sandia National Laboratories (SNL) |
2007 |
|
|
|
2012 |
1.3 Networking Equipment Manufacturers, Services, and Customers.
1.4 Internet Service Providers (ISPs).
| Source | Date | Title |
|---|---|---|
|
6NET colleges and universities (see Note below) |
2005 |
An IPv6 Deployment Guide (chapters 13-14) |
|
Brno University of Technology |
2011 |
Deploying IPv6 - practical problems from the campus perspective |
|
2012 |
Deploying IPv6 in University Campus Network - Practical Problems |
|
|
Carleton University |
2017 |
|
|
Georgian College |
2010 |
|
| Imperial College of London | 2016 | IPv6 Deployment at Imperial |
|
Louisiana State University |
2013 |
|
|
2017 |
||
|
McGill University |
2017 |
|
| Merit Network | 2018 | A Model For Advancing IPv6 Deployment In REN And Higher Ed Networks |
| The IPv6-Only Network | ||
| 2021 | IPv6 Readiness Program Whitepaper (registration form to download the whitepaper) | |
|
Monash University |
2008 |
|
|
Monmouth University |
2017 |
|
| Oxford University | 2010 | The State of the IPv6 Deployment |
|
Université Laurentienne |
2011 |
|
| Universiy of Buffalo | 2018 | Agile Dual-Stack Approach to Campus-Wide IPv6 Roll Out |
| University of Cambridge | 2019 | IPv6 at Cambridge |
|
University of Colorado, Denver |
2017 |
|
|
University of Hawaii |
2019 |
The IPv6-only Network: Building Networks with DNS64/NAT64/464XLAT (video available here) (click here for further details) |
| U. Hawaii IPv6 Deployment Experiences | ||
| University of Iowa | 2018 | Case Study: IPv6 at the University of Iowa |
|
University of Pennsylvania |
2018 |
Reexamining How We Build and Operate Networks |
|
Virginia Polytechnic Institute and State University (Virginia Tech) |
2011 |
IPv6 at Virginia Tech: Operational experiences from a large-scale production deployment |
| 2018 | An IPv6 Journey Two Decades in the Making | |
| 2023 | 25 Years of Production IPv6 Experience | |
|
Washington and Jefferson College |
2017 |
Note: The European 6NET project reported lessons learned by several colleges and universities, networking customers and ISPs of all sizes. The 6NET project began in 2002 and completed in Jun 2005, followed by the 6DISS project which completed in Sept 2007; followed by 6DEPLOY and 6DEPLOY-2 (www.6deploy.eu) which completed in Feb 2013. A more recent European IPv6 project was Governments Enabled with IPv6 (GEN6), which completed in May 2015. Deliverables and Presentations under the Publications tab of the GEN6 website provide additional material. The next European IPv6 project was IPv6 Framework for European Governments, which completed in 2018. Then came the European Union Internet Standards Deployment Monitoring Website project.
1.6 Standards Development Organizations (SDOs) and Software Development Organizations (SWDOs).
| Date | Title | |
|---|---|---|
| Internet Engineering Task Force (IETF) |
2012 |
Experiences from an IPv6-Only Network Request for Comments (RFC) 6586 |
|
2012 |
||
|
2013 |
Guidance for Internet Content Providers and Application Service Providers RFC 6883 |
|
| 2016 | IPv4 Declared Historic draft-howard-sunset4-v4historic-00 | |
|
2017 |
IETF: End Work on IPv4 draft-ietf-sunset4-ipv6-ietf-01 (proposed Sept 2017, withdrawn June 2018) |
|
| 2023 | IPv6 Deployment Status RFC 9386 | |
| IETF Journal | 2008 | IPv6 Deployment: Lessons from the Trenches |
1.7 Non-commercial Organizations.
| Source | Date | Title |
|---|---|---|
|
American Registry for Internet Numbers (ARIN) |
2010 |
|
|
2010 |
||
|
2016 |
IPv6 Success Stories From Companies That Have Done It (panel session highlights, full transcript and video) |
|
|
Asia Pacific Network Information Center (APNIC) |
2009 - 2013 |
IPv6 Transition Stories (presentations and videos from 14 organizations around the world) |
| 2017 | APNIC IPv6 Deployment | |
| Canadian Internet Registration Authority (CIRA) | 2011 | IPv6 adoption experience & challenges from a ccTLD operator |
|
Internet SOCiety (ISOC) Deploy360 Programme/IPv6 |
2010 - 2017 |
IPv6 Case Studies from over 17 organizations around the world |
|
2018 |
State of IPv6 Deployment 2018 | |
| Internet Systems Consortium (ISC) |
2012 |
IPv6 Migration: Some Lessons Learned (a video) |
|
National Telecommunications & Information Administration (NTIA) |
2016 |
Incentives, Benefits, Costs, and Challenges to IPv6 Implementation (initial solicitation and numerous responses received from organizations around the world) |
| San Joaquin Valley Library System | 2019 | Library Framework Setup for IPv6 |
|
Wikipedia |
On-going |
1.8 European and Asian IPv6 Communities.
| Source | Date | Title |
|---|---|---|
|
6NET networking customers and ISPs (see Note following 1.5 Academic Community category above) |
2005 |
An IPv6 Deployment Guide (chapter 12) |
| Body of European Regulators for Electronic Communications (BEREC) | 2021 | BEREC public technical workshop on IPv6 deployment across Europe |
|
Clara.net ISP |
2007 |
|
|
2009 |
||
|
Heise Online |
2011 |
|
| Government of India, Ministry of Communications & Information Technology, Department of Telecommunications | 2014 | Compendium on IPv6 Based Solutions/Architecture/Case Studies for Different Industry Verticals |
| IPv6 Framework for European Governments (see Note following 1.5 Academic Community category above) | 05/2018 09/2018 10/2018 |
Workshop 1: Identifying barriers to IPv6 Adoption (see also this 2003 presentation) Workshop 2: (cancelled) Workshop 3:: Overcoming barriers to IPv6 Adoption Workshop 4:: Lessons Learned and Next Steps |
|
Nippon Telegraph and Telephone Information Sharing Platform Laboratories |
2011 |
|
| Qatar Communications Regulatory Authority | 2021 | Qatar: a model for IPv6 Adoption |
|
Swedish Post and Telecom Agency |
2012 |
Deploying IPv6 – Internet Protocol version 6 – Practical guidance |
|
Telecom Italia ISP |
2011 |
1.9 Caribbean and Latin American Communities
| Source | Date | Title |
|---|---|---|
|
Cable & Wireless (C&W) Communications |
2018 |
Enabling Internet Access Services over IPv6 in the Caribbean |
1.10 Australian IPv6 Community
| Source | Date | Title |
|---|---|---|
|
FX Networks ISP |
2011 |
|
|
Internode ISP |
2011 |
|
|
Internet Society of Australia |
2007 |
|
|
2006-2013 |
IPv6 for e-Business (website) |
1.11 The Small Office/Home Office (SOHO).
| Operating System | Date | Title |
|---|---|---|
|
agnostic (networking emphasis) |
2016 |
|
|
BSD/Linux/Apple OS X/ Microsoft Windows |
2009 |
IPv6 for All (chapters 2 and 3) |
|
Linux |
2006 |
|
|
2010 |
||
|
2010 |
||
|
2013 |
||
|
Linux/Apple OS X/Microsoft Windows |
2017 |
2. DREN IPv6 Pilot lessons learned summaries. If you want to discover the lessons learned by the DREN dual-stack pilot during the 2003 through 2014 time period, without having to read through the detailed articles that comprise the majority of the IPv6 Knowledge Base, you have four choices:
- This presentation and accompanying white paper provides an executive overview of the DREN IPv6 Pilot. They describe challenges overcome by the DREN IPv6 Pilot.
- This article provides a mid-level review of the DREN IPv6 Pilot and lessons learned during its deployment of IPv6: DREN IPv6 Pilot — 3 years of IPv6 in the real world. This covers the history, organization, processes, and results of the DREN IPv6 Pilot as of 2006. It discusses the reasons for the success of the DREN IPv6 Pilot, and provides some details (elapsed time, hours, dollars, training) for how “success” was measured (metrics). If you are really in a hurry and only have time to look at a couple of slides, then look at slides 44-47.
- This presentation provides a mid-level assessment of the DREN IPv6 Pilot lessons learned as of 2014.
- In a series of briefings started in 2005 and continuing through 2012, more specific technical lessons learned summaries have been presented at the Internet2 Joint Techs workshops. Those briefings are available here in the “Various Presentations” section of the DREN IPv6 Backbone website (archived 2012).
3. DREN IPv6 Pilot lessons learned details. The six sections that follow the Deployment section (IP Transport, Infrastructure, Network Management, Security, Applications, and Testing) contain articles providing more detailed descriptions of the lessons learned by DREN as well as by numerous other organizations while deploying IPv6, together with informal guidelines and aides to help in deploying IPv6.
4. Recipients of DREN IPv6 Pilot lessons learned. Lessons learned have been provided by the DREN IPv6 Pilot to other organizations through conference presentations, participation in numerous DoD, Service, and other Federal organizations' working groups, and in response to questionnaires received from commercial companies and Federal organizations.
- OMB Enterprise Architecture (EA) Success Story: This information was provided to the Office of Management and Budget in response to a request and was subsequently published on their website.
- RAND survey: This information was provided to the RAND Corporation in response to a request and was subsequently incorporated into a report entitled “Security Challenges to the Use and Deployment of Disruptive Technologies”. (See Chapter 6)
- RTI International survey: Information was provided to the RTI International corporation in preparing a report for the National Institute of Standards and Technology (NIST) entitled “Department of Commerce Planning Report 05-2, IPv6 Economic Impact Assessment Final Report”, and also used in preparing a paper entitled “Could IPv6 Improve Network Security? And, If So, at What Cost?”.
- v6Transition survey: Information was provided to the v6Transition corporation in response to a request and was subsequently incorporated into a report entitled “Vol. 1: A Guide for Federal Agencies Transitioning to IPv6″. This report was the first in a series of 4 volumes published during 2006 through 2008. That series is available by going here and then clicking on World Report Series.
5. Lessons learned from protocol transitions prior to IPv4. Networks used other protocols prior to IPv4. A comprehensive summary of lessons learned during earlier protocol transitions was provided by Tony Hain here. Two important IETF RFCs specific to the transition to IPv4 are RFC 801 ”NCP/TCP Transition Plan” and RFC 942 “Transport Protocols for Department of Defense Data Networks.” They discuss basic issues and provide a few warnings against tempting shortcuts. A retrospective article on the shortcomings of the Network Control Protocol (NCP) is available. (Caution: Published on April Fools' Day, 2011!).
Organizations that believe Internet Protocol version 6 (IPv6) is not in their future cannot simply ignore it, as this article explains with a touch of irony, while this article ends with the warning: “the question is not when you should begin managing IPv6, but what should you be doing right now!”.
This article from the American Registry for Internet Numbers (ARIN) describes the business case for IPv6. This document from the Internet SOCiety (ISOC) describes some of the global trends that are driving deployment of IPv6. This article goes even further, explaining why IPv4 will not be in your future.
Organizations that believe the Internet of Things (IoT) is in their future should read this article. Even organizations that abandoned earlier efforts to transition to an IPv6-only network (such as Microsoft) will eventually make such a transition.
Even though you may have decided that your organization, network, or enclave does not need to deploy IPv6 at the present time, you cannot safely and securely ignore IPv6. IPv6 is quite likely already present on your network. As a case in point, if you have ever watched a YouTube video, you have used IPv6. If you used a cellphone to view this web page, IPv6 was used when connecting to the IPv6 Knowledge Base website, as this article explains.
The title of this article 7 points your security team needs to know about IPv6 (but probably doesn’t) speaks for itself.
The presentation Security in an IPv6 World (Myth and Reality) and the detailed series of 10 IPv6 Security Myth articles:
#1 I'm Not Running IPv6 So I Don't Have to Worry
#2 IPv6 Has Security Designed In
#3 No IPv6 NAT Means Less Security
#4 IPv6 Networks are Too Big To Scan
#5 Privacy Addresses Fix Everything
#6 IPv6 is Too New to be Attacked
#7 96 More Bits, No Magic
#8 It Supports IPv6
#9 There Aren't Any IPv6 Security Resources and
#10 Deploying IPv6 is Too Risky
discuss the risks of ignoring IPv6 and the benefits of taking action to minimize those risks.
This article Common Misconceptions about IPv6 Security (video available here) touches on the same myths and adds some new ones:
IPv6 is more/less secure than IPv4
IPv6 is IPv4 with longer addresses
IPsec makes IPv6 more secure than IPv4
Address scanning is impossible in IPv6
No NAT makes IPv6 insecure.
The articles It’s fake news and It’s fake news (cont) along with an article asserting that quantum computing successfully merges IPv4 and IPv6 to form IPv5 provide yet another perspective on IPv6. (By the way, this article explains why there was no IPv5.)
This article describes tools and techniques that can detect the presence of IPv6 on your network. The presence of undetected IPv6 on networks has long been recognized as a concern, as shown by this Federal Information Notice and this warning about Malware Tunneling in IPv6, both issued by the United States-Computer Emergency Readiness Team (US-CERT) in 2005.
The specific steps necessary to disable or uninstall IPv6 on many routers and operating systems are described in articles in the IP Transport section. As a minimum the National Institute for Standards and Technology (NIST) recommends that organizations not yet deploying IPv6 should block all incoming and outgoing IPv6 traffic (native and tunneled) on the organization's perimeter border routers or firewalls. (See Section 6.9 of NIST Special Publication 800-119, Guidelines for the Secure Deployment of IPv6, December, 2010.) These tunneling mechanisms include 6over4, 6to4, IPv6-in-IPv4, ISATAP, and tunnel brokers (which all typically use protocol 41) and the TEREDO tunneling mechanism (which typically uses UDP port 3544 to establish its tunnel). In addition, border routers or firewalls should block packets with a source or destination address prefix of 192.88.99.0/24 (the default prefix for public 6to4 anycast gateways).
Sites running a Postfix version 2.2 (or later) mail transfer agent (MTA): You must
include the following in your /etc/postfix/main.cf:
inet_protocols = ipv4
Without this line, Postfix defaults to using IPv6 for mail delivery, and when that fails
Postfix will stop trying. Postfix will not use IPv4 without it.
Internet Protocol version 6 (IPv6) is not backwards compatible with IPv4, so networks must be changed to deploy IPv6.
This IPv6 Knowledge Base Initial Introduction provides an overview of the structure of the Defense Research and Engineering (DREN) IPv6 Knowledge Base. The IPv6 Knowledge Base consists of nine major sections, with links to those sections appearing in the column on the left side of every IPv6 Knowledge Base article:
- An overview of the General Information section
- An overview of the Deployment section
- An overview of the IP Transport section
- An overview of the Infrastructure section
- An overview of the Network Management section
- An overview of the Security section
- An overview of the Applications section
- An overview of the Testing section
- An overview of the IPv6 and IoT Frequently Asked Questions (FAQ) section.
1. The General Information section contains articles covering a wide variety of information about IPv6, from policy and standards to what to do if an organization is not going to deploy IPv6, as follows:
- The IPv6 Knowledge Base Initial Introduction article you are currently reading provides an overview of the structure and scope of the IPv6 Knowledge Base.
- An IPv6 Not Needed Here!?! article briefly describing the actions that should be taken by organizations that have decided not to deploy IPv6.
- A United States (US) IPv6 and IoT Policy, Guidance, and Best Practices article providing a list of policy, guidance, and best practices documents issued by organizations inside the United States.
- A Non-United States IPv6 and IoT Policy, Guidance, and Best Practices article providing a list of policy, guidance, and best practices documents issued by organizations outside the United States.
- An Overview of Lessons Learned Deploying IPv6 article providing high-level summaries and discussions from multiple points of view of lessons learned deploying IPv6 by various United States (US) Department of Defense and other US Federal government departments and agencies, private organizations, and academia (both in the US and around the world), as well as for the home and Small Office/Home Office (SOHO) user.
- An IPv6 and IoT Networking Standards article providing a general overview of the documents that define networking standards and the organizations that develop and publish them.
- An IPv6 and IoT Points of Contact article listing communities and public forums involved in IPv6 and IoT planning and deployment efforts.
2. The Deployment section contains articles discussing various aspects of deploying IPv6, including:
- A Before you Begin article about things to consider before planning an IPv6 deployment.
- An Overview of Process which provides planning material, information about the approaches used to deploy IPv6 by organizations of all types (US Federal government departments and agencies, Internet Service Providers, businesses, and academic institutions), all sizes (from international enterprises to small businesses and individual users), and locations (in the US and around the world), and in-depth information on management, planning, and deployment processes.
- An IPv6 “Boiler Plate” Acquisitions Language article providing an overview of US and European regulations governing the acquisition process and examples of language developed by various organizations to be used in solicitations and acquisition documents.
- An IPv6 Training and Learning article providing information on training available at no cost or from commercial entities and free sources for learning about IPv6, and a limited amount of tutorial information.
- An IPv6 Transition Mechanisms article providing a quick overview of the various IPv6 transition mechanisms that are available.
- An IPv6 Software article that identifies many software products that either support IPv6 or are IP-protocol neutral.
- An IPv6 in the Home and Small Office/Home Office (SOHO) article about the IPv6 deployment process in the Home and SOHO.
3. The IP Transport section contains articles about the specifics of enabling and (when required) disabling IPv6 in many different computer operating systems (several versions of Linux, Apple macOS and OS X, Microsoft Windows, and UNIX, as well as others) and router firmware (Nokia [formerly Alcatel-Lucent], Extreme Networks, Cisco, and Juniper).
4. The Infrastructure section contains articles about the specifics of installing and configuring software that supports IPv6 infrastructure services, such as web, email, DNS, and DHCP servers. It also contains articles about selected infrastructure topics, such as cloud, VPN, and Microsoft Windows services/servers.
5. The Network Management section contains articles about planning for and deploying wide-area, enterprise, and site networks that support IPv6, guidance and examples for obtaining IPv6 address allocations, guidance and examples for Address Plans, recommended management practices, and troubleshooting tips and techniques.
6. The Security section contains articles about best practices, general and specific (Check Point, Cisco, Juniper, and several versions of software based) router and firewall firmware configuration guides, Internet Protocol Security, Trusted Internet Connection, and Windows Internet Connection Sharing.
7. The Applications section contains articles providing guidance for and examples of developing, enabling, and testing applications software to support IPv6, specifics of configuring and using IPv6 web browsers, and describing IPv6 support in selected applications such as Java and Kerberos.
8. The Testing section contains articles about IPv6 product and network test techniques in general, formal IPv6 product test programs and the testing results they provide, and IPv6 network testing results.
9. The IPv6 and IoT Frequently Asked Questions (FAQ) section provides information about topics of interest to people new to IPv6 and IoT, including information about this IPv6 Knowledge Base and other websites that provide general information about IPv6 and IoT, information about the deployment status of IPv6, and information about developing or enabling applications to support IPv6.
