Difference between revisions of "MOOC:Ressources"

From Livre IPv6

(vidéo)
(Internet Usage)
 
(26 intermediate revisions by 2 users not shown)
Line 19: Line 19:
  
 
===RFC===
 
===RFC===
 +
Référence <strike>barrée</strike> si reprise dans une séquence
 +
 +
* RFC 8956 Dissemination of Flow Specification Rules  for IPv6
 +
* RFC 8883 ICMPv6 Errors for Discarding Packets Due to Processing Limits
 +
*  RFC 8781  Discovering PREF64 in Router Advertisements
 +
* RFC 8754 on IPv6 Segment Routing Header (SRH)
 +
* RFC 8504: IPv6 Node Requirements([http://www.bortzmeyer.org/8504.html Bortzmeyer])
 +
* RFC 8501: Reverse DNS in IPv6 for Internet Service Providers ([http://www.bortzmeyer.org/8501.html Bortzmeyer])
 +
* RFC 8415:  Dynamic Host Configuration Protocol for IPv6 (DHCPv6) ([http://www.bortzmeyer.org/8415.html Bortzmeyer])
 +
* RFC 8201 Path MTU Discovery for IP version 6 ([http://www.bortzmeyer.org/8201.html Bortzmeyer])
 +
* RFC 8200 Internet Protocol, Version 6 (IPv6) Specification ([http://www.bortzmeyer.org/8200.html Bortzmeyer])
 +
* RFC 8021: Generation of IPv6 Atomic Fragments Considered Harmful ([http://www.bortzmeyer.org/8021.html Bortzmeyer])
 
* RFC 7608 IPv6 Prefix Length Recommendation for Forwarding  
 
* RFC 7608 IPv6 Prefix Length Recommendation for Forwarding  
 
* RFC 7600 IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)  
 
* RFC 7600 IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)  
 
* RFC 7599 Mapping of Address and Port using Translation (MAP-T)  
 
* RFC 7599 Mapping of Address and Port using Translation (MAP-T)  
 
* RFC 7596 Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
 
* RFC 7596 Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
 +
* RFC 7421 Analysis of the 64-bit Boundary in IPv6 Addressing ([http://www.bortzmeyer.org/7421.html Bortzmeyer])
 +
* RFC 7411 Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast Handovers
 +
* RFC 7404 Using Only Link-Local Addressing inside an IPv6 Network ([http://www.bortzmeyer.org/7404.html Bortzmeyer])
 
* RFC 7381 Enterprise IPv6 Deployment Guidelines ([http://www.bortzmeyer.org/7381 Bortzmeyer])
 
* RFC 7381 Enterprise IPv6 Deployment Guidelines ([http://www.bortzmeyer.org/7381 Bortzmeyer])
 +
* RFC 7368 IPv6 Home Networking Architecture Principles
 +
* RFC 7346 IPv6 Multicast Address Scopes
 
* RFC 7269 NAT64 Deployment Options and Experience ([http://www.bortzmeyer.org/7269 Bortzmeyer])
 
* RFC 7269 NAT64 Deployment Options and Experience ([http://www.bortzmeyer.org/7269 Bortzmeyer])
 +
* RFC 7227 Guidelines for Creating New DHCPv6 Options
 
* RFC 7225 Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP)  ([http://www.bortzmeyer.org/7225 Bortzmeyer])
 
* RFC 7225 Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP)  ([http://www.bortzmeyer.org/7225 Bortzmeyer])
 +
* RFC 7219 SEcure Neighbor Discovery (SEND)  Source Address Validation Improvement (SAVI)
 +
* RFC 7217 A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC) ([http://www.bortzmeyer.org/7217.html Bortzmeyer])
 +
* RFC 7148 Prefix Delegation Support for Proxy Mobile IPv6
 +
* RFC 7136 Significance of IPv6 Interface Identifiers ([http://www.bortzmeyer.org/7136.html Bortzmeyer])
 
* RFC 7123 Security Implications of IPv6 on IPv4 Networks ([http://www.bortzmeyer.org/7123 Bortzmeyer])
 
* RFC 7123 Security Implications of IPv6 on IPv4 Networks ([http://www.bortzmeyer.org/7123 Bortzmeyer])
 +
* RFC 7112 Implications of Oversized IPv6 Header Chains
 +
* RFC 7098 Using the IPv6 Flow Label for Load Balancing in Server Farms
 +
* RFC 7084 Basic Requirements for IPv6 Customer Edge Routers
 
* RFC 7059 A Comparison of IPv6-over-IPv4 Tunnel Mechanisms ([http://www.bortzmeyer.org/7059 Bortzmeyer])
 
* RFC 7059 A Comparison of IPv6-over-IPv4 Tunnel Mechanisms ([http://www.bortzmeyer.org/7059 Bortzmeyer])
 
* RFC 7051 Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix  
 
* RFC 7051 Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix  
 
* RFC 7050 Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis ([http://www.bortzmeyer.org/7050 Bortzmeyer])
 
* RFC 7050 Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis ([http://www.bortzmeyer.org/7050 Bortzmeyer])
 +
* RFC 7048 Neighbor Unreachability Detection Is Too Impatient
 +
* RFC 7045 Transmission and Processing of IPv6 Extension Headers
 
* RFC 7040 Public IPv4-over-IPv6 Access Network  
 
* RFC 7040 Public IPv4-over-IPv6 Access Network  
 +
* RFC 7010 IPv6 Site Renumbering Gap Analysis ([http://www.bortzmeyer.org/7010.html Bortzmeyer])
 +
* RFC 6980 Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery
 +
* RFC 6948 Some Measurements on World IPv6 Day from an End-User Perspective ([http://www.bortzmeyer.org/6948.html Bortzmeyer])
 +
* RFC 6946 Processing of IPv6 "Atomic" Fragments
 +
* RFC 6936 Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums
 
* RFC 6935 IPv6 and UDP Checksums for Tunneled Packets ([http://www.bortzmeyer.org/6935 Bortzmeyer])
 
* RFC 6935 IPv6 and UDP Checksums for Tunneled Packets ([http://www.bortzmeyer.org/6935 Bortzmeyer])
 
* RFC 6908 Deployment Considerations for Dual-Stack Lite ([http://www.bortzmeyer.org/6908 Bortzmeyer])
 
* RFC 6908 Deployment Considerations for Dual-Stack Lite ([http://www.bortzmeyer.org/6908 Bortzmeyer])
 +
* RFC 6890  Special-Purpose IP Address Registries ([http://www.bortzmeyer.org/6890.html Bortzmeyer])
 
* RFC 6889 Analysis of Stateful 64 Translation  
 
* RFC 6889 Analysis of Stateful 64 Translation  
 +
* RFC 6879 IPv6 Enterprise Network Renumbering Scenarios,  Considerations, and Methods ([http://www.bortzmeyer.org/6879.html Bortzmeyer])
 
* RFC 6877 464XLAT: Combination of Stateful and Stateless Translation
 
* RFC 6877 464XLAT: Combination of Stateful and Stateless Translation
 +
* RFC 6874 Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers ([http://www.bortzmeyer.org/6874.html Bortzmeyer])
 +
* RFC 6866 Problem Statement for Renumbering IPv6 Hosts  with Static Addresses in Enterprise Networks ([http://www.bortzmeyer.org/6866.html Bortzmeyer])
 
* RFC 6791 Stateless Source Address Mapping for ICMPv6 Packets
 
* RFC 6791 Stateless Source Address Mapping for ICMPv6 Packets
 
* RFC 6782 Wireline Incremental IPv6 ([http://www.bortzmeyer.org/6782 Bortzmeyer])
 
* RFC 6782 Wireline Incremental IPv6 ([http://www.bortzmeyer.org/6782 Bortzmeyer])
 +
* RFC 6752 Issues with Private IP Addressing in the Internet
 
* RFC 6732 6to4 Provider Managed Tunnels
 
* RFC 6732 6to4 Provider Managed Tunnels
 +
* RFC 6724 Default Address Selection for Internet Protocol Version 6 (IPv6) ([http://www.bortzmeyer.org/6724.html Bortzmeyer])
 +
* RFC 6611 Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario
 
* RFC 6586 Experiences from an IPv6-Only Network  ([http://www.bortzmeyer.org/6586 Bortzmeyer])
 
* RFC 6586 Experiences from an IPv6-Only Network  ([http://www.bortzmeyer.org/6586 Bortzmeyer])
 
* RFC 6654 Gateway-Initiated IPv6 Rapid Deployment on IPv4 Infrastructures (GI 6rd)  
 
* RFC 6654 Gateway-Initiated IPv6 Rapid Deployment on IPv4 Infrastructures (GI 6rd)  
 
* RFC 6589 Considerations for Transitioning Content to IPv6 ([http://www.bortzmeyer.org/6589 Bortzmeyer])
 
* RFC 6589 Considerations for Transitioning Content to IPv6 ([http://www.bortzmeyer.org/6589 Bortzmeyer])
 +
* RFC 6586 Experiences from an IPv6-Only Network
 +
* RFC 6583 Operational Neighbor Discovery Problems
 +
* RFC 6564 A Uniform Format for IPv6 Extension Headers
 
* RFC 6555 Happy Eyeballs: Success with Dual-Stack Hosts ([http://www.bortzmeyer.org/6555.html Bortzmeyer])
 
* RFC 6555 Happy Eyeballs: Success with Dual-Stack Hosts ([http://www.bortzmeyer.org/6555.html Bortzmeyer])
 +
* RFC 6543 Reserved IPv6 Interface Identifier for Proxy Mobile IPv6
 +
* RFC 6540 IPv6 Support Required for All IP-Capable Nodes
 +
* RFC 6496 Secure Proxy ND Support for SEcure Neighbor Discovery (SEND)
 +
* RFC 6437 IPv6 Flow Label Specification, voir aussi RFC  6438, RFC 6436
 +
* RFC 6434 IPv6 Node Requirements
 
* RFC 6384  An FTP Application Layer Gateway (ALG) for IPv6-to-IPv4 Translation  
 
* RFC 6384  An FTP Application Layer Gateway (ALG) for IPv6-to-IPv4 Translation  
 +
* <strike>RFC 6346 The Address plus Port (A+P) Approach to the IPv4 Address Shortage ([http://www.bortzmeyer.org/6346.html Bortzmeyer])</strike>
 
* RFC 6343 Advisory Guidelines for 6to4 Deployment
 
* RFC 6343 Advisory Guidelines for 6to4 Deployment
 +
* RFC 6342 Mobile Networks Considerations for IPv6 Deployment, aussi RFC 6212
 
* RFC 6334 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option    for Dual-Stack Lite ([http://www.bortzmeyer.org/6334 Bortzmeyer])
 
* RFC 6334 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option    for Dual-Stack Lite ([http://www.bortzmeyer.org/6334 Bortzmeyer])
 
* RFC 6333 Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion ([http://www.bortzmeyer.org/6333 Bortzmeyer])
 
* RFC 6333 Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion ([http://www.bortzmeyer.org/6333 Bortzmeyer])
 
* RFC 6324 Routing Loop Attack Using IPv6 Automatic Tunnels  
 
* RFC 6324 Routing Loop Attack Using IPv6 Automatic Tunnels  
 +
* RFC 6301  A Survey of Mobility Support in the Internet
 +
* RFC 6294 Survey of Proposed Use Cases for the IPv6 Flow Label
 +
* RFC 6275 Mobility Support in IPv6
 +
* RFC 6221 Lightweight DHCPv6 Relay Agent
 +
* RFC 6204 Basic Requirements for IPv6 Customer Edge Routers
 
* RFC 6180 Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment ([http://www.bortzmeyer.org/6180 Bortzmeyer])
 
* RFC 6180 Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment ([http://www.bortzmeyer.org/6180 Bortzmeyer])
 +
* RFC 6177 IPv6 Address Assignment to End Sites ([http://www.bortzmeyer.org/6177.html Bortzmeyer])
 +
* RFC 6164 Using 127-Bit IPv6 Prefixes on Inter-Router Links ([http://www.bortzmeyer.org/6164.html Bortzmeyer])
 
* RFC 6147 DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers ([http://www.bortzmeyer.org/6147 Bortzmeyer])
 
* RFC 6147 DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers ([http://www.bortzmeyer.org/6147 Bortzmeyer])
 
* RFC 6146 Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers ([http://www.bortzmeyer.org/6146 Bortzmeyer])
 
* RFC 6146 Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers ([http://www.bortzmeyer.org/6146 Bortzmeyer])
Line 53: Line 109:
 
* RFC 6144 Framework for IPv4/IPv6 Translation ([http://www.bortzmeyer.org/6144 Bortzmeyer])
 
* RFC 6144 Framework for IPv4/IPv6 Translation ([http://www.bortzmeyer.org/6144 Bortzmeyer])
 
* RFC 6127 IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios  
 
* RFC 6127 IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios  
 +
* RFC 6106 IPv6 Router Advertisement Options for DNS Configuration
 
* RFC 6104: Rogue IPv6 Router Advertisement Problem Statement
 
* RFC 6104: Rogue IPv6 Router Advertisement Problem Statement
 
* RFC 6092: Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service [http://www.bortzmeyer.org/6092 Bortzmeyer])
 
* RFC 6092: Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service [http://www.bortzmeyer.org/6092 Bortzmeyer])
 +
* RFC 6085 Address Mapping of IPv6 Multicast Packets on Ethernet
 
* RFC 6081 Teredo Extensions  
 
* RFC 6081 Teredo Extensions  
 
* RFC 6052 IPv6 Addressing of IPv4/IPv6 Translators ([http://www.bortzmeyer.org/6052 Bortzmeyer])
 
* RFC 6052 IPv6 Addressing of IPv4/IPv6 Translators ([http://www.bortzmeyer.org/6052 Bortzmeyer])
 
* RFC 6036 Emerging Service Provider Scenarios for IPv6 Deployment ([http://www.bortzmeyer.org/6036 Bortzmeyer])
 
* RFC 6036 Emerging Service Provider Scenarios for IPv6 Deployment ([http://www.bortzmeyer.org/6036 Bortzmeyer])
 +
* RFC 5952 A Recommendation for IPv6 Address Text Representation ([http://www.bortzmeyer.org/5952.html Bortzmeyer])
 +
* RFC 5942 IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes
 +
* RFC 5902 IAB Thoughts on IPv6 Network Address Translation ([http://www.bortzmeyer.org/5902 Bortzmeyer])
 +
* RFC 5722 Handling of Overlapping IPv6 Fragments
 
* RFC 5569 IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) ([http://www.bortzmeyer.org/5569 Bortzmeyer])
 
* RFC 5569 IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) ([http://www.bortzmeyer.org/5569 Bortzmeyer])
 
* RFC 5572 IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP) ([http://www.bortzmeyer.org/5572 Bortzmeyer])
 
* RFC 5572 IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP) ([http://www.bortzmeyer.org/5572 Bortzmeyer])
* RFC 5902 IAB Thoughts on IPv6 Network Address Translation ([http://www.bortzmeyer.org/5902 Bortzmeyer])
+
* RFC 5453 Reserved IPv6 Interface Identifiers ([http://www.bortzmeyer.org/5453.html Bortzmeyer])
 +
* RFC 5375 IPv6 Unicast Address Assignment Considerations ([http://www.bortzmeyer.org/5375.html Bortzmeyer])
 
* RFC 5214 Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)  
 
* RFC 5214 Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)  
 +
* RFC 5156 Special-Use IPv6 Addresses ([http://www.bortzmeyer.org/5156.html Bortzmeyer])
 
* RFC 4966 Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status
 
* RFC 4966 Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status
 +
* RFC 4944 Transmission of IPv6 Packets over IEEE 802.15.4 Networks
 
* RFC 4925 Softwire Problem Statement ([http://www.bortzmeyer.org/4925 Bortzmeyer])
 
* RFC 4925 Softwire Problem Statement ([http://www.bortzmeyer.org/4925 Bortzmeyer])
 
* RFC 4864 Local Network Protection for IPv6 ([http://www.bortzmeyer.org/4864 Bortzmeyer])
 
* RFC 4864 Local Network Protection for IPv6 ([http://www.bortzmeyer.org/4864 Bortzmeyer])
 +
* RFC 4862 IPv6 Stateless Address Autoconfiguration
 +
* RFC 4821 Packetization Layer Path MTU Discovery ([[http://www.bortzmeyer.org/4821.html Bortzmeyer]])
 
* RFC 4380 Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)
 
* RFC 4380 Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)
 
* RFC 4213 Transition Mechanisms for IPv6 Hosts and Routers  ([http://www.bortzmeyer.org/4213 Bortzmeyer])
 
* RFC 4213 Transition Mechanisms for IPv6 Hosts and Routers  ([http://www.bortzmeyer.org/4213 Bortzmeyer])
Line 93: Line 160:
 
*  The IPv6 Portal [http://www.ipv6tf.org url]
 
*  The IPv6 Portal [http://www.ipv6tf.org url]
 
* Lothaire Yarding "Yet Another Ipv6 to the Next Generation", Université de Lorraine, Lothaire, par Julien Vaubourg [http://julien.vaubourg.com/files/lothaire-yarding_ipv6.pdf Lothaire Yarding]
 
* Lothaire Yarding "Yet Another Ipv6 to the Next Generation", Université de Lorraine, Lothaire, par Julien Vaubourg [http://julien.vaubourg.com/files/lothaire-yarding_ipv6.pdf Lothaire Yarding]
 
+
* LinkedIn Learning : [https://www.linkedin.com/learning/decouvrir-ipv6/ Découvrir IPv6 (Cours conçu par : Rudi Bruchez)]
 
* A titre de demonstration, il y a ce site: http://www.fredbovy.com/modulation/Modules.html qui présente quelques animations
 
* A titre de demonstration, il y a ce site: http://www.fredbovy.com/modulation/Modules.html qui présente quelques animations
 +
 +
===Adressage===
 +
 +
* http://www.cbtnuggets.com/it-training-videos/course/cbtn_ipv6 (Vidéos comprehensives mais non-gratuites de Keith )
 +
* https://www.youtube.com/channel/UCrCh8p6p2UZC18vqSBhN_sA (chaîne Youtube de Keith)
 +
* [https://www.youtube.com/watch?v=rljkNMySmuM&index=1&list=PL7FBD333BAB233A44 Keith Barker "Make Sense of an IPv6 Address"]
 +
* [https://www.youtube.com/watch?v=lNev5bboMnM&index=2&list=PL7FBD333BAB233A44 Keith Barker "Lov'n the Link Local Address"]
 +
* [https://tools.ietf.org/html/draft-ietf-6man-why64-08  IETF Draft - Analysis of the 64-bit Boundary in IPv6 Addressing]
 +
* [https://community.infoblox.com/blogs/2015/01/09/do-you-really-need-subnet-calculator-ipv6 Do you really need an IPv6 subnet calculator ?]
 +
* [http://www.ripe.net/lir-services/training/material/basic-ipv6-training-course/Basic-IPv6-Addressing-Plan-With-Possible-Solutions.pdf Exercice du RIPE sur la définition d'un plan d'adressage]
 +
* CISCO. (2008). [http://www.cisco.com/web/strategy/docs/gov/IPv6_WP.pdf IPv6 Addressing White Paper].
 +
* [http://bcop.nanog.org/images/6/62/BCOP-IPv6_Subnetting.pdf NANOG BCOP IPv6 Subnetting]
 +
* http://www.cabrillo.edu/~rgraziani/ipv6.html (Un des meilleurs sites dédié à IPv6)
  
 
===vidéo===
 
===vidéo===
Line 101: Line 181:
 
* [https://www.youtube.com/results?search_query=alantalkstech Vidéos alantalkstech sur Youtube] de spirent
 
* [https://www.youtube.com/results?search_query=alantalkstech Vidéos alantalkstech sur Youtube] de spirent
 
* [https://www.youtube.com/results?search_query=IPv6+Ipv4&search_sort=video_view_count Les vidéos IPv6 sur Youtube]
 
* [https://www.youtube.com/results?search_query=IPv6+Ipv4&search_sort=video_view_count Les vidéos IPv6 sur Youtube]
 +
* [https://www.ripe.net/support/training/videos/ipv6/transition-mechanisms IPv6 Transition Mechanisms] by RIPE
 +
 +
=== Presse. - rapport ===
 +
 +
* [https://thenewstack.io/kubernetes-warms-up-to-ipv6/ Kubernetes Warms Up to IPv6]
 +
*[https://www.numerama.com/tech/529644-ipv6-en-france-le-regulateur-des-telecoms-appelle-a-sy-mettre-de-toute-urgence.html IPv6 en France : le régulateur des télécoms appelle à s’y mettre de « toute urgence »] Numerama juin 2019
 +
* [https://www.arcep.fr/la-regulation/grands-dossiers-internet-et-numerique/lipv6/suivi-epuisement-adresses-ipv4.html Suivi de l'épuisement des adresses IPv4] par l'ARCEP
 +
* [https://www.zdnet.fr/actualites/ipv4-la-penurie-d-adresses-disponibles-c-est-pour-novembre-2019-39891627.htm Une "Task force" créée par l'Arcep] zdnet octobre 2019
 +
*[https://www.zdnet.fr/pratique/quelles-recommandations-pour-migrer-vers-ipv6-39860280.htm Quelques recommandations pour migrer vers l'IPv6] zdnet octobre 2019
 +
* [https://www.universfreebox.com/article/51128/IPV4-la-penurie-s-accelere-moins-de-3-millions-d-adresses-disponibles IPV4 : la pénurie s’accélère, moins de 3 millions d’adresses disponibles] Univers FreeBox Juillet 2019
 +
* [https://www.lemagit.fr/actualites/252468059/Penurie-IPv4-comment-lInternet-europeen-sombre-dans-les-magouilles Pénurie IPv4 : comment l’Internet européen sombre dans les magouilles] LeMagIT Aout 2019<br>Une critique d'IPv6
 +
*  Zergy (2015) Article en ligne [http://blog.zergy.net/index.php?article2/ipocalypse Ipocalypse]
 +
* Col, P. (2016). ZDNet. [http://www.zdnet.fr/actualites/ipv6-avertissement-solennel-du-ripe-39837614.htm IPv6 : avertissement solennel du RIPE].
 +
 +
===  Internet Usage ===
 +
 +
* Cisco 2018-2023 [https://www.cisco.com/c/en/us/solutions/collateral/executive-perspectives/annual-internet-report/white-paper-c11-741490.html Cisco Annual Internet Report]
  
 +
* Baromètre annuel de la transition vers IPv6 en France (ARCEP - 2021) [https://www.arcep.fr/cartes-et-donnees/nos-publications-chiffrees/transition-ipv6/barometre-annuel-de-la-transition-vers-ipv6-en-france.html Lien]
  
 
=== TP ===
 
=== TP ===
 
* JOOL [http://jool.mx/en/index.html] un code alternatif à Tayga  (NAT64)
 
* JOOL [http://jool.mx/en/index.html] un code alternatif à Tayga  (NAT64)

Latest revision as of 06:49, 4 May 2022

> MOOC>Contenu>Ressources


Ressources bibliographiques

Articles

  • Bernstein, Daniel J. The IPv6 mess.
  • . Cui Y., Wu P., Xu M., et al., “4over6: Network Layer Virtualization for IPv4-IPv6 Coexistence,” IEEE Network, October 2012.

Livres

  • Graziani, R. (2012). Ed.: Cisco Press. BookOnLine IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6
  • liste sur la page de Pascal Anelli
  • Migrating to IPv6: A Practical Guide to Implementing IPv6 in Mobile and FIxed network Par Marc Blanchet

IETF WG

RFC

Référence barrée si reprise dans une séquence

  • RFC 8956 Dissemination of Flow Specification Rules for IPv6
  • RFC 8883 ICMPv6 Errors for Discarding Packets Due to Processing Limits
  • RFC 8781 Discovering PREF64 in Router Advertisements
  • RFC 8754 on IPv6 Segment Routing Header (SRH)
  • RFC 8504: IPv6 Node Requirements(Bortzmeyer)
  • RFC 8501: Reverse DNS in IPv6 for Internet Service Providers (Bortzmeyer)
  • RFC 8415: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (Bortzmeyer)
  • RFC 8201 Path MTU Discovery for IP version 6 (Bortzmeyer)
  • RFC 8200 Internet Protocol, Version 6 (IPv6) Specification (Bortzmeyer)
  • RFC 8021: Generation of IPv6 Atomic Fragments Considered Harmful (Bortzmeyer)
  • RFC 7608 IPv6 Prefix Length Recommendation for Forwarding
  • RFC 7600 IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)
  • RFC 7599 Mapping of Address and Port using Translation (MAP-T)
  • RFC 7596 Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
  • RFC 7421 Analysis of the 64-bit Boundary in IPv6 Addressing (Bortzmeyer)
  • RFC 7411 Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast Handovers
  • RFC 7404 Using Only Link-Local Addressing inside an IPv6 Network (Bortzmeyer)
  • RFC 7381 Enterprise IPv6 Deployment Guidelines (Bortzmeyer)
  • RFC 7368 IPv6 Home Networking Architecture Principles
  • RFC 7346 IPv6 Multicast Address Scopes
  • RFC 7269 NAT64 Deployment Options and Experience (Bortzmeyer)
  • RFC 7227 Guidelines for Creating New DHCPv6 Options
  • RFC 7225 Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP) (Bortzmeyer)
  • RFC 7219 SEcure Neighbor Discovery (SEND) Source Address Validation Improvement (SAVI)
  • RFC 7217 A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC) (Bortzmeyer)
  • RFC 7148 Prefix Delegation Support for Proxy Mobile IPv6
  • RFC 7136 Significance of IPv6 Interface Identifiers (Bortzmeyer)
  • RFC 7123 Security Implications of IPv6 on IPv4 Networks (Bortzmeyer)
  • RFC 7112 Implications of Oversized IPv6 Header Chains
  • RFC 7098 Using the IPv6 Flow Label for Load Balancing in Server Farms
  • RFC 7084 Basic Requirements for IPv6 Customer Edge Routers
  • RFC 7059 A Comparison of IPv6-over-IPv4 Tunnel Mechanisms (Bortzmeyer)
  • RFC 7051 Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix
  • RFC 7050 Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis (Bortzmeyer)
  • RFC 7048 Neighbor Unreachability Detection Is Too Impatient
  • RFC 7045 Transmission and Processing of IPv6 Extension Headers
  • RFC 7040 Public IPv4-over-IPv6 Access Network
  • RFC 7010 IPv6 Site Renumbering Gap Analysis (Bortzmeyer)
  • RFC 6980 Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery
  • RFC 6948 Some Measurements on World IPv6 Day from an End-User Perspective (Bortzmeyer)
  • RFC 6946 Processing of IPv6 "Atomic" Fragments
  • RFC 6936 Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums
  • RFC 6935 IPv6 and UDP Checksums for Tunneled Packets (Bortzmeyer)
  • RFC 6908 Deployment Considerations for Dual-Stack Lite (Bortzmeyer)
  • RFC 6890 Special-Purpose IP Address Registries (Bortzmeyer)
  • RFC 6889 Analysis of Stateful 64 Translation
  • RFC 6879 IPv6 Enterprise Network Renumbering Scenarios, Considerations, and Methods (Bortzmeyer)
  • RFC 6877 464XLAT: Combination of Stateful and Stateless Translation
  • RFC 6874 Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers (Bortzmeyer)
  • RFC 6866 Problem Statement for Renumbering IPv6 Hosts with Static Addresses in Enterprise Networks (Bortzmeyer)
  • RFC 6791 Stateless Source Address Mapping for ICMPv6 Packets
  • RFC 6782 Wireline Incremental IPv6 (Bortzmeyer)
  • RFC 6752 Issues with Private IP Addressing in the Internet
  • RFC 6732 6to4 Provider Managed Tunnels
  • RFC 6724 Default Address Selection for Internet Protocol Version 6 (IPv6) (Bortzmeyer)
  • RFC 6611 Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario
  • RFC 6586 Experiences from an IPv6-Only Network (Bortzmeyer)
  • RFC 6654 Gateway-Initiated IPv6 Rapid Deployment on IPv4 Infrastructures (GI 6rd)
  • RFC 6589 Considerations for Transitioning Content to IPv6 (Bortzmeyer)
  • RFC 6586 Experiences from an IPv6-Only Network
  • RFC 6583 Operational Neighbor Discovery Problems
  • RFC 6564 A Uniform Format for IPv6 Extension Headers
  • RFC 6555 Happy Eyeballs: Success with Dual-Stack Hosts (Bortzmeyer)
  • RFC 6543 Reserved IPv6 Interface Identifier for Proxy Mobile IPv6
  • RFC 6540 IPv6 Support Required for All IP-Capable Nodes
  • RFC 6496 Secure Proxy ND Support for SEcure Neighbor Discovery (SEND)
  • RFC 6437 IPv6 Flow Label Specification, voir aussi RFC 6438, RFC 6436
  • RFC 6434 IPv6 Node Requirements
  • RFC 6384 An FTP Application Layer Gateway (ALG) for IPv6-to-IPv4 Translation
  • RFC 6346 The Address plus Port (A+P) Approach to the IPv4 Address Shortage (Bortzmeyer)
  • RFC 6343 Advisory Guidelines for 6to4 Deployment
  • RFC 6342 Mobile Networks Considerations for IPv6 Deployment, aussi RFC 6212
  • RFC 6334 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite (Bortzmeyer)
  • RFC 6333 Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion (Bortzmeyer)
  • RFC 6324 Routing Loop Attack Using IPv6 Automatic Tunnels
  • RFC 6301 A Survey of Mobility Support in the Internet
  • RFC 6294 Survey of Proposed Use Cases for the IPv6 Flow Label
  • RFC 6275 Mobility Support in IPv6
  • RFC 6221 Lightweight DHCPv6 Relay Agent
  • RFC 6204 Basic Requirements for IPv6 Customer Edge Routers
  • RFC 6180 Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment (Bortzmeyer)
  • RFC 6177 IPv6 Address Assignment to End Sites (Bortzmeyer)
  • RFC 6164 Using 127-Bit IPv6 Prefixes on Inter-Router Links (Bortzmeyer)
  • RFC 6147 DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers (Bortzmeyer)
  • RFC 6146 Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers (Bortzmeyer)
  • RFC 6145 IP/ICMP Translation Algorithm (Bortzmeyer)
  • RFC 6144 Framework for IPv4/IPv6 Translation (Bortzmeyer)
  • RFC 6127 IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios
  • RFC 6106 IPv6 Router Advertisement Options for DNS Configuration
  • RFC 6104: Rogue IPv6 Router Advertisement Problem Statement
  • RFC 6092: Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service Bortzmeyer)
  • RFC 6085 Address Mapping of IPv6 Multicast Packets on Ethernet
  • RFC 6081 Teredo Extensions
  • RFC 6052 IPv6 Addressing of IPv4/IPv6 Translators (Bortzmeyer)
  • RFC 6036 Emerging Service Provider Scenarios for IPv6 Deployment (Bortzmeyer)
  • RFC 5952 A Recommendation for IPv6 Address Text Representation (Bortzmeyer)
  • RFC 5942 IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes
  • RFC 5902 IAB Thoughts on IPv6 Network Address Translation (Bortzmeyer)
  • RFC 5722 Handling of Overlapping IPv6 Fragments
  • RFC 5569 IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) (Bortzmeyer)
  • RFC 5572 IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP) (Bortzmeyer)
  • RFC 5453 Reserved IPv6 Interface Identifiers (Bortzmeyer)
  • RFC 5375 IPv6 Unicast Address Assignment Considerations (Bortzmeyer)
  • RFC 5214 Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
  • RFC 5156 Special-Use IPv6 Addresses (Bortzmeyer)
  • RFC 4966 Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status
  • RFC 4944 Transmission of IPv6 Packets over IEEE 802.15.4 Networks
  • RFC 4925 Softwire Problem Statement (Bortzmeyer)
  • RFC 4864 Local Network Protection for IPv6 (Bortzmeyer)
  • RFC 4862 IPv6 Stateless Address Autoconfiguration
  • RFC 4821 Packetization Layer Path MTU Discovery ([Bortzmeyer])
  • RFC 4380 Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)
  • RFC 4213 Transition Mechanisms for IPv6 Hosts and Routers (Bortzmeyer)

Support du G6

Références générales

Adressage

vidéo

Presse. - rapport

Internet Usage

  • Baromètre annuel de la transition vers IPv6 en France (ARCEP - 2021) Lien

TP

  • JOOL [2] un code alternatif à Tayga (NAT64)
Personal tools