Voir la vidéo sur http://www.youtube.com/watch?v=tVzz_CSFs8A
Laurent Toutain (Télécom Bretagne) présente "La frange polymorphe de l'Internet" lors de la Journée du Conseil scientifique de l'Afnic 2013 (JCSA2013), le 9 juillet 2013 dans les locaux de Télécom ParisTech.
How to build and use GTPing to generate GTP traffic for testing without eNB, SPGW etc. This work was done as part of the preparation of SRv6 mobile user plane POC at SRv6 Consortium, Data plane Study Group, which is a group of people interested in SRv6.
The document provides an overview of 6RD (IPv6 Rapid Deployment), describing how it was developed from 6to4 to allow ISPs to deliver IPv6 connectivity to customers over their existing IPv4 networks using a stateless encapsulation method, and details the key components and configuration parameters needed for implementing 6RD including the 6RD prefix, IPv4 common bits, and border relay address.
SRv6 Mobile User Plane : Initial POC and ImplementationKentaro Ebisawa
SRv6 Mobile Uplane POC results and findings talked at ENOG55 @Nigata http://enog.jp/archives/2014
SRv6 functions: T.M.Tmap, End.M.GTP4.E using VPP and P4 on Tofino switch.
The document describes the design of p4srv6, a P4 program that implements SRv6 (Segment Routing for IPv6) functions. It discusses p4srv6's pipeline design based on the v1model.p4 architecture and includes details on the parser, ingress control, transit and end tables for SRv6, and handling of variable length SID lists. It also provides examples of configuring p4srv6 for GTP to SRv6 encapsulation and decapsulation.
The document discusses configuring GTP tunnels on Linux using the libgtpnl library. Key points:
- Linux kernels since 4.7 include GTP tunnel endpoint functionality in the gtp.c driver
- Libgtpnl provides tools to configure GTP tunnels via netlink without a control plane
- Configuration involves creating veth interfaces, loopbacks, GTP devices, and tunnels between endpoints using TEIDs and IP addresses
BGP: Whats so special about the number 512?GeoffHuston
It was reported that parts of the Internet crashed when the number of routes in the Internet's Inter-domain routing table (BGP) exceeded 512K routes. This presentation looks at the growth of the Internet's routing table and how this correlates to the capacity and speed of memory in hardware routers.
How to build and use GTPing to generate GTP traffic for testing without eNB, SPGW etc. This work was done as part of the preparation of SRv6 mobile user plane POC at SRv6 Consortium, Data plane Study Group, which is a group of people interested in SRv6.
The document provides an overview of 6RD (IPv6 Rapid Deployment), describing how it was developed from 6to4 to allow ISPs to deliver IPv6 connectivity to customers over their existing IPv4 networks using a stateless encapsulation method, and details the key components and configuration parameters needed for implementing 6RD including the 6RD prefix, IPv4 common bits, and border relay address.
SRv6 Mobile User Plane : Initial POC and ImplementationKentaro Ebisawa
SRv6 Mobile Uplane POC results and findings talked at ENOG55 @Nigata http://enog.jp/archives/2014
SRv6 functions: T.M.Tmap, End.M.GTP4.E using VPP and P4 on Tofino switch.
The document describes the design of p4srv6, a P4 program that implements SRv6 (Segment Routing for IPv6) functions. It discusses p4srv6's pipeline design based on the v1model.p4 architecture and includes details on the parser, ingress control, transit and end tables for SRv6, and handling of variable length SID lists. It also provides examples of configuring p4srv6 for GTP to SRv6 encapsulation and decapsulation.
The document discusses configuring GTP tunnels on Linux using the libgtpnl library. Key points:
- Linux kernels since 4.7 include GTP tunnel endpoint functionality in the gtp.c driver
- Libgtpnl provides tools to configure GTP tunnels via netlink without a control plane
- Configuration involves creating veth interfaces, loopbacks, GTP devices, and tunnels between endpoints using TEIDs and IP addresses
BGP: Whats so special about the number 512?GeoffHuston
It was reported that parts of the Internet crashed when the number of routes in the Internet's Inter-domain routing table (BGP) exceeded 512K routes. This presentation looks at the growth of the Internet's routing table and how this correlates to the capacity and speed of memory in hardware routers.
An experiment was conducted using stateless NAT64 to connect an IPv6-only network to an IPv4-only network at a conference with 350 attendees and 550 devices. TAYGA, an open-source stateless NAT64 implementation, was used to provide one-to-one mapping between IPv6 hosts and IPv4 addresses. DNS64 was also implemented to provide synthetic DNS responses. The results showed no noticeable performance degradation compared to the dual-stack network, and popular applications like Skype and Dropbox worked successfully, demonstrating stateless NAT64 can be a viable solution.
This slides deck presents mobile network protocol interworking idea of which the mobile networking IDs in GTP-U are mapped into IPv6 address with SRv6 concept in stateless. We adopt VPP as the target platform for prototyping the SRv6/GTP-U stateless translation. IETF104 hackathon was the venue where we hacked VPP to implement it.
PLNOG 9: Donald E. Eastlake 3rd - Transparent Interconnection of Lost of Links PROIDEA
The document provides a high-level overview of TRILL (Transparent Interconnection of Lots of Links) by Donald Eastlake, including:
- TRILL terminates spanning tree protocols and provides least cost unicast paths and multipathing capabilities for higher throughput.
- The history of TRILL from its inception in 2004 to its standardization by the IETF in 2010.
- Two examples showing how TRILL can improve performance and redundancy in bridged campus networks and data center networks compared to spanning tree.
Moved to https://speakerdeck.com/ebiken/zebra-srv6-cli-on-linux-dataplane-enog-number-49
Introduction to SRv6, Linux SRv6 implementation and how to add SRv6 CLI to Zebra 2.0 Open Source Network Operation Stack.
Presented at ENOG (Echigo NOG) #49.
Things I wish I had known about IPv6 before I startedFaelix Ltd
The document discusses things the author wishes they had known about IPv6 before starting to implement it for their small provider network. It covers IPv6 justification in terms of IPv4 address scarcity and rising costs, advice on IPv6 addressing plans and transition technologies, and gotchas like IPv6 neighbor discovery exhaustion issues. The author advocates for embracing IPv6 to avoid expensive IPv4 solutions and make the most of the large IPv6 allocations provided.
This document discusses IPv6 transition and the state of IPv6 adoption. It notes that while IPv4 address exhaustion is a real issue, users do not care and prefer NAT for security. Transition requires cooperation across users, ISPs, devices and content. Statistics show rapid growth of IPv6 adoption by major networks worldwide in the last two years. Full transition to IPv6 is needed to enable unlimited connectivity for cloud/mobile internet and the internet of things going forward.
464XLAT Tutorial, by Masataka Mawatari.
Presented at the APNIC 40 "Hypes? Fanfares? Fads? Wading through the muddy IPv6 puddle" session, Wed 9 Sep 2015.
Lightweight 4-over-6: One step further Dual-Stack Lite Networks (RIPE 76)Igalia
This document discusses lightweight 4over6 (lw4o6), an IPv6 transition technology. It describes lw4o6 as moving network address translation (NAT) to customer premises equipment (CPE) and using softwire mappings between IPv4 and IPv6 addresses. Open-source implementations of lw4o6 are available in Snabb and FD.io VPP. Experimental results show that lw4o6 can support a variety of applications.
This document provides an overview of 6LoWPAN (IPv6 over Low-Power Wireless Personal Area Networks), which allows IP to be implemented on IEEE 802.15.4 low-power wireless networks. It describes how 6LoWPAN compresses IPv6 and higher-level protocol headers to address constraints of low-power wireless networks like small packet sizes. Key techniques include header compression, mesh routing at the link layer under the IP topology, and leveraging existing IP standards to meet requirements of long device lifetimes on limited energy in highly embedded environments.
Presentation of the Conference paper: "Empirical Analysis of IPv6 Transition Technologies Using the IPv6 Network Evaluation Testbed" in Tridentcom 2014, Guangzhou , China
This document summarizes the IPv6 infrastructure of ASNet and ASIX6 in Taiwan. It provides details on:
1) ASNet's IPv6 network status, including allocated addresses, campus networks, peering routers, and services provided.
2) ASIX6, the IPv6 internet exchange, its purpose to provide global IPv6 connectivity for participants and minimize costs. It describes members and peering arrangements.
3) Procedures for joining the peering including estimating connection methods, providing contact information, discussing peering policies and protocols. Performance testing tools are also listed.
The document discusses the need for organizations to deploy IPv6 in order to avoid business continuity risks as IPv4 addresses run out. It provides guidance on requesting IPv6 address space and deploying IPv6 routing within an organization's network. It also addresses common excuses for not deploying IPv6 and notes that initial IPv6 deployment takes less than one day of work. The document aims to convince readers that IPv6 deployment is straightforward and urgently needed.
CodiLime Tech Talk - Adam Kułagowski: IPv6 - introductionCodiLime
IPv6 was created to address the limited address space of IPv4 as global IPv4 address allocation was running out. Some of the key differences between IPv4 and IPv6 include IPv6's significantly larger 128-bit address space compared to IPv4's 32-bit addresses, as well as changes to areas like packet headers, fragmentation, and neighbor discovery. Transition technologies like dual stack, NAT64, and DS-Lite were developed to help transition from IPv4 to IPv6, while ensuring IPv6 connectivity even for networks and devices that still use IPv4. Fully enabling IPv6 requires changes to network infrastructure like firewalls, routers, and switches to support the new protocol.
Segment Routing provides simplified packet forwarding by encoding forwarding instructions as segments rather than per-flow state. This document compares different encodings of segments: 32-bit segments encoded directly in MPLS or UDP over IPv4/IPv6 (SRoMPLS, SRoUDP); and 128-bit segments encoded in a new IPv6 extension header (SRv6). SRoMPLS and SRoUDP are well-suited for brownfield networks as they can reuse existing MPLS and IP infrastructure with minimal overhead. SRv6 is designed for native IPv6 but has higher overhead. All approaches simplify operations but have different performance implications depending on the network environment.
The document discusses how the number 512 relates to routing table sizes on Cisco and Brocade networking equipment. It analyzes growth trends in IPv4 and IPv6 BGP routing tables based on historical data. While absolute sizes are increasing, the annual growth rates have slowed slightly. Projections indicate routing tables could continue growing within the capabilities of current router technologies for the foreseeable future if trends continue.
Many network operators still struggle with which type of data-plane encoding they should use for segment routing. The world is hyper-connected and we can’t afford to be late to deliver 5G. Using IPv6, MPLS (or even IPv4) data-plane encoding keeps us moving forward.
Bruno Decraene - Improving network availability through the graceful shutdown...PROIDEA
This document proposes a solution called "BGP graceful shutdown" to improve network availability when shutting down BGP sessions. It does so by allowing a graceful transition of traffic to an alternate path before fully removing the route, if an alternate path exists. The solution aims to minimize packet loss during the shutdown process. It involves preconfiguring policies on routers to tag outgoing routes for shutdown with a community and set local preference to 0 to redirect traffic. Evaluation on a test bed showed it can achieve the goal of zero packet loss compared to an abrupt route removal.
Webinar topic: BGP on RouterOS7 - Part 1
Presenter: Achmad Mardiansyah & M. Taufik Nurhuda
In this webinar series, How BGP on RouterOS7 works
Please share your feedback or webinar ideas here: http://bit.ly/glcfeedback
Check our schedule for future events: https://www.glcnetworks.com/en/schedule/
Follow our social media for updates: Facebook, Instagram, YouTube Channel, and telegram also discord
Recording available on Youtube
https://youtu.be/CYTHOlY4WU0
The document provides an introduction to computer networks and GNU/Linux. It discusses network models including OSI and TCP/IP models. Common network protocols like Ethernet, IP, TCP and UDP are explained. Standard organizations that develop network standards like IETF, IEEE and ITU are presented. Network hardware components like network interface cards and switches are described. The document is intended as a lecture on basic computer networking concepts.
Richard Li discusses limitations of IPv4 and IPv6 for 5G, B5G, and 6G mobile network applications. He notes that IPv4/IPv6 yields huge bandwidth waste for mMTC, UCBC, HCS, and short texts due to large packet overhead. Additionally, IPv4/IPv6 cannot guarantee key performance indicators like latency and packet loss required for uRLLC and RTBC. As an alternative, Li proposes an incremental evolution of IPv4/IPv6 that includes flexible addressing systems, geography-based addressing, and integration of satellite and terrestrial networks to expand its applicability for future applications and services.
An experiment was conducted using stateless NAT64 to connect an IPv6-only network to an IPv4-only network at a conference with 350 attendees and 550 devices. TAYGA, an open-source stateless NAT64 implementation, was used to provide one-to-one mapping between IPv6 hosts and IPv4 addresses. DNS64 was also implemented to provide synthetic DNS responses. The results showed no noticeable performance degradation compared to the dual-stack network, and popular applications like Skype and Dropbox worked successfully, demonstrating stateless NAT64 can be a viable solution.
This slides deck presents mobile network protocol interworking idea of which the mobile networking IDs in GTP-U are mapped into IPv6 address with SRv6 concept in stateless. We adopt VPP as the target platform for prototyping the SRv6/GTP-U stateless translation. IETF104 hackathon was the venue where we hacked VPP to implement it.
PLNOG 9: Donald E. Eastlake 3rd - Transparent Interconnection of Lost of Links PROIDEA
The document provides a high-level overview of TRILL (Transparent Interconnection of Lots of Links) by Donald Eastlake, including:
- TRILL terminates spanning tree protocols and provides least cost unicast paths and multipathing capabilities for higher throughput.
- The history of TRILL from its inception in 2004 to its standardization by the IETF in 2010.
- Two examples showing how TRILL can improve performance and redundancy in bridged campus networks and data center networks compared to spanning tree.
Moved to https://speakerdeck.com/ebiken/zebra-srv6-cli-on-linux-dataplane-enog-number-49
Introduction to SRv6, Linux SRv6 implementation and how to add SRv6 CLI to Zebra 2.0 Open Source Network Operation Stack.
Presented at ENOG (Echigo NOG) #49.
Things I wish I had known about IPv6 before I startedFaelix Ltd
The document discusses things the author wishes they had known about IPv6 before starting to implement it for their small provider network. It covers IPv6 justification in terms of IPv4 address scarcity and rising costs, advice on IPv6 addressing plans and transition technologies, and gotchas like IPv6 neighbor discovery exhaustion issues. The author advocates for embracing IPv6 to avoid expensive IPv4 solutions and make the most of the large IPv6 allocations provided.
This document discusses IPv6 transition and the state of IPv6 adoption. It notes that while IPv4 address exhaustion is a real issue, users do not care and prefer NAT for security. Transition requires cooperation across users, ISPs, devices and content. Statistics show rapid growth of IPv6 adoption by major networks worldwide in the last two years. Full transition to IPv6 is needed to enable unlimited connectivity for cloud/mobile internet and the internet of things going forward.
464XLAT Tutorial, by Masataka Mawatari.
Presented at the APNIC 40 "Hypes? Fanfares? Fads? Wading through the muddy IPv6 puddle" session, Wed 9 Sep 2015.
Lightweight 4-over-6: One step further Dual-Stack Lite Networks (RIPE 76)Igalia
This document discusses lightweight 4over6 (lw4o6), an IPv6 transition technology. It describes lw4o6 as moving network address translation (NAT) to customer premises equipment (CPE) and using softwire mappings between IPv4 and IPv6 addresses. Open-source implementations of lw4o6 are available in Snabb and FD.io VPP. Experimental results show that lw4o6 can support a variety of applications.
This document provides an overview of 6LoWPAN (IPv6 over Low-Power Wireless Personal Area Networks), which allows IP to be implemented on IEEE 802.15.4 low-power wireless networks. It describes how 6LoWPAN compresses IPv6 and higher-level protocol headers to address constraints of low-power wireless networks like small packet sizes. Key techniques include header compression, mesh routing at the link layer under the IP topology, and leveraging existing IP standards to meet requirements of long device lifetimes on limited energy in highly embedded environments.
Presentation of the Conference paper: "Empirical Analysis of IPv6 Transition Technologies Using the IPv6 Network Evaluation Testbed" in Tridentcom 2014, Guangzhou , China
This document summarizes the IPv6 infrastructure of ASNet and ASIX6 in Taiwan. It provides details on:
1) ASNet's IPv6 network status, including allocated addresses, campus networks, peering routers, and services provided.
2) ASIX6, the IPv6 internet exchange, its purpose to provide global IPv6 connectivity for participants and minimize costs. It describes members and peering arrangements.
3) Procedures for joining the peering including estimating connection methods, providing contact information, discussing peering policies and protocols. Performance testing tools are also listed.
The document discusses the need for organizations to deploy IPv6 in order to avoid business continuity risks as IPv4 addresses run out. It provides guidance on requesting IPv6 address space and deploying IPv6 routing within an organization's network. It also addresses common excuses for not deploying IPv6 and notes that initial IPv6 deployment takes less than one day of work. The document aims to convince readers that IPv6 deployment is straightforward and urgently needed.
CodiLime Tech Talk - Adam Kułagowski: IPv6 - introductionCodiLime
IPv6 was created to address the limited address space of IPv4 as global IPv4 address allocation was running out. Some of the key differences between IPv4 and IPv6 include IPv6's significantly larger 128-bit address space compared to IPv4's 32-bit addresses, as well as changes to areas like packet headers, fragmentation, and neighbor discovery. Transition technologies like dual stack, NAT64, and DS-Lite were developed to help transition from IPv4 to IPv6, while ensuring IPv6 connectivity even for networks and devices that still use IPv4. Fully enabling IPv6 requires changes to network infrastructure like firewalls, routers, and switches to support the new protocol.
Segment Routing provides simplified packet forwarding by encoding forwarding instructions as segments rather than per-flow state. This document compares different encodings of segments: 32-bit segments encoded directly in MPLS or UDP over IPv4/IPv6 (SRoMPLS, SRoUDP); and 128-bit segments encoded in a new IPv6 extension header (SRv6). SRoMPLS and SRoUDP are well-suited for brownfield networks as they can reuse existing MPLS and IP infrastructure with minimal overhead. SRv6 is designed for native IPv6 but has higher overhead. All approaches simplify operations but have different performance implications depending on the network environment.
The document discusses how the number 512 relates to routing table sizes on Cisco and Brocade networking equipment. It analyzes growth trends in IPv4 and IPv6 BGP routing tables based on historical data. While absolute sizes are increasing, the annual growth rates have slowed slightly. Projections indicate routing tables could continue growing within the capabilities of current router technologies for the foreseeable future if trends continue.
Many network operators still struggle with which type of data-plane encoding they should use for segment routing. The world is hyper-connected and we can’t afford to be late to deliver 5G. Using IPv6, MPLS (or even IPv4) data-plane encoding keeps us moving forward.
Bruno Decraene - Improving network availability through the graceful shutdown...PROIDEA
This document proposes a solution called "BGP graceful shutdown" to improve network availability when shutting down BGP sessions. It does so by allowing a graceful transition of traffic to an alternate path before fully removing the route, if an alternate path exists. The solution aims to minimize packet loss during the shutdown process. It involves preconfiguring policies on routers to tag outgoing routes for shutdown with a community and set local preference to 0 to redirect traffic. Evaluation on a test bed showed it can achieve the goal of zero packet loss compared to an abrupt route removal.
Webinar topic: BGP on RouterOS7 - Part 1
Presenter: Achmad Mardiansyah & M. Taufik Nurhuda
In this webinar series, How BGP on RouterOS7 works
Please share your feedback or webinar ideas here: http://bit.ly/glcfeedback
Check our schedule for future events: https://www.glcnetworks.com/en/schedule/
Follow our social media for updates: Facebook, Instagram, YouTube Channel, and telegram also discord
Recording available on Youtube
https://youtu.be/CYTHOlY4WU0
The document provides an introduction to computer networks and GNU/Linux. It discusses network models including OSI and TCP/IP models. Common network protocols like Ethernet, IP, TCP and UDP are explained. Standard organizations that develop network standards like IETF, IEEE and ITU are presented. Network hardware components like network interface cards and switches are described. The document is intended as a lecture on basic computer networking concepts.
Richard Li discusses limitations of IPv4 and IPv6 for 5G, B5G, and 6G mobile network applications. He notes that IPv4/IPv6 yields huge bandwidth waste for mMTC, UCBC, HCS, and short texts due to large packet overhead. Additionally, IPv4/IPv6 cannot guarantee key performance indicators like latency and packet loss required for uRLLC and RTBC. As an alternative, Li proposes an incremental evolution of IPv4/IPv6 that includes flexible addressing systems, geography-based addressing, and integration of satellite and terrestrial networks to expand its applicability for future applications and services.
Webinar topic: MPLS on Router OS V7 - Part 1
Presenter: Achmad Mardiansyah & M. Taufik Nurhuda
In this webinar series, How MPLS on Router OS V7 works
Please share your feedback or webinar ideas here: http://bit.ly/glcfeedback
Check our schedule for future events: https://www.glcnetworks.com/en/schedule/
Follow our social media for updates: Facebook, Instagram, YouTube Channel, and telegram also discord
Recording available on Youtube
https://youtu.be/SvZrYNA0-rQ
Academia Service Network: IPv6 Status ReportEthern Lin
This document summarizes the IPv6 status of ASNet, the Academia Sinica network in Taiwan. It provides details on ASNet's IPv6 addressing and infrastructure, including peering with commercial and academic networks domestically and internationally. It also describes NICI's 2004 project to construct an IPv6 Internet Exchange to promote IPv6 adoption among ISPs and provide IPv6 testing environments.
Webinar topic: Internet Protocol Deep-Dive
Presenter: Achmad Mardiansyah
In this webinar series, we discussed about Internet Protocol Deep-Dive
Please share your feedback or webinar ideas here: http://bit.ly/glcfeedback
Check our schedule for future events: https://www.glcnetworks.com/en/schedule/
Follow our social media for updates: Facebook, Instagram, YouTube Channel, and telegram also discord
Recording available on Youtube
https://youtu.be/u8_FxpNfqAs
The Cisco Catalyst 3560-CX series WS-3560CX-12PD-S is a fanless, compact Ethernet switch with 12 Gigabit Ethernet ports and 2 Gigabit uplink ports plus 2 10G SFP+ uplinks. It provides 240W of PoE+ power and has a forwarding bandwidth of 34Gbps. The switch has a quiet, fanless design to provide flexible mounting options in space-constrained areas.
How our Cloudy Mindsets Approached Physical RoutersSteffen Gebert
The document discusses how EMnify integrated a pair of Juniper routers into their existing cloud-based workflows and monitoring tools. They deployed the routers using Ansible playbooks for configuration management and leveraged existing tools like Prometheus, Grafana, and CloudWatch for monitoring metrics, logs, and alerts. While the integration worked well, they note some challenges around testing configurations and limitations of the monitoring tools for high data volumes. The overall approach focused on minimizing new processes and tools by bridging the routers into their existing cloud-centric tooling.
Webinar topic: OSPF On Router OS7
Presenter: Achmad Mardiansyah & M. Taufik Nurhuda
In this webinar series, How OSPF On Router OS7
Please share your feedback or webinar ideas here: http://bit.ly/glcfeedback
Check our schedule for future events: https://www.glcnetworks.com/en/schedule/
Follow our social media for updates: Facebook, Instagram, YouTube Channel, and telegram also discord
Recording available on Youtube
https://youtu.be/nuByFdZHvAg
IPv4 addresses are nearly exhausted while IPv6 provides a vast address space to support continued Internet growth. While IPv4 and IPv6 can coexist, IPv6 adoption is needed as the only sustainable solution. Global metrics show increasing IPv6 deployment over time through allocations, routing entries, and user access, though challenges remain around applications, skills, and justification. RIRs and IETF are committed to IPv6 to maintain the openness and development of the Internet.
BGP is a popular routing protocol used in the Data Center (DC). But as the protocol that powers the Internet, it also comes armed with a lot of sophistication that scares many who think a CCIE or CCNA is required to even understand it.
Watch this presentation and learn:
*How BGP fits in the DC with specific use cases
*How to configure and manage BGP traditionally and via new methods
Проектировка IPv6-оnly датацентра в Яндексе. Никита ШироковYandex
This document discusses IPv6-only data centers at Yandex. It notes that they transitioned to IPv6-only internally due to running out of public IPv4 addresses. Their WAN, firewalls, load balancers, and services have all been optimized for and transitioned to IPv6. They discussed initial designs for IPv6-only data center networks including separate backbone and fastbone networks. Some challenges discussed include lack of checks inside IPv6 tunnels, lack of support for 6to4 in load balancers, and needing to decapsulate traffic. They also discussed solutions for services that still need IPv4 connectivity like downloading content or using public DNS resolvers.
Today's Internet faces severe challenges including:
* IPv4 address exhaustion
* explosion of BGP tables and IP routing tables
* exponential traffic growth (which might not be a problem after all)
This document discusses strategies for traffic engineering using BGP. It begins by outlining reasons for performing traffic engineering such as managing capacity demands and circuit costs. It then discusses how complexity arises when networks grow. Real examples of traffic engineering needs are provided. The document outlines approaches for internal network traffic engineering and challenges with inter-domain traffic engineering since full control is not present. It stresses the importance of collecting data on traffic flows to inform traffic engineering strategies. Specific tools for collecting this data like NetFlow, IPFIX, sFlow, log files and AS-Stats are described. The document concludes by covering techniques for outbound and inbound traffic engineering using tools like local preference, AS path prepending, selective prefix announcements and understanding traffic sinks.
Similar to JCSA2013 04 Laurent Toutain - La frange polymorphe de l'Internet (20)
L’Afnic publie désormais un bilan trimestriel de ses procédures alternatives de résolution de litiges. Découverte de l’étude de ce premier trimestre 2015.
Securing Internet communications end-to-end with the DANE protocolAfnic
Highlighting the fact that securing communications over the Internet is more important than ever before, Afnic launches an issue paper on the DANE protocol
Sécuriser les communications sur Internet de bout-en-bout avec le protocole DANEAfnic
Alors que la sécurisation des communications sur Internet n’a jamais été autant d’actualité, l’Afnic lance un dossier thématique consacré au protocole DANE
AFNIC just published a Practical Guide to DNSSEC deployment: this implementation and deployment manual provides practical guidance for DNS hosts to configure DNSSEC on their infrastructure;
L'Afnic vient de publier un guide pratique de déploiement de DNSSEC : ce manuel de mise en œuvre et de déploiement permet d’aider concrètement les hébergeurs de DNS à configurer DNSSEC sur leurs infrastructures. Plus d'information sur http://www.afnic.fr/fr/l-afnic-en-bref/actualites/actualites-generales/7380/show/l-afnic-s-engage-dans-la-promotion-de-dnssec-2.html
The document discusses the life cycle of .FR domain names. Domain names are registered for 1 to 10 years and must be renewed before expiration to remain active. Domain names that are not renewed on time will first be put on hold, then deleted and made available for new registration after a certain waiting period if not renewed by the original owner.
Voir cette présentation en vidéo sur http://www.youtube.com/watch?v=mLQT_i-Lgsk
Isabelle Chrisment (Inria) présente "L'initiative PLATON (PLATeforme d'Observation de l'interNet) lors de la Journée du Conseil scientifique de l'Afnic 2013 (JCSA2013), le 9 juillet 2013 dans les locaux de Télécom ParisTech.
JCSA2013 07 Pierre Lorinquer & Samia M'timet - Observatoire de la résilience ...Afnic
Voir la présentation en vidéo sur http://www.youtube.com/watch?v=lhkAtsCm6fw
Pierre Lorinquer (ANSSI) et Samia M'Timet (Afnic) présentent l'essentiel de l'Observatoire 2012 de la résilience de l'Internet en France lors de la Journée du Conseil scientifique de l'Afnic 2013 (JCSA2013), le 9 juillet 2013 dans les locaux de Télécom ParisTech.
L'Observaoire en question est en ligne sr http://www.afnic.fr/fr/l-afnic-en-bref/actualites/actualites-generales/7126/show/l-observatoire-sur-la-resilience-de-l-internet-francais-publie-son-rapport-2012-2.html
JCSA2013 06 Luigi Iannone - Le protocole LISP ("Locator/Identifier Sepration ...Afnic
Voir la présentation en vidéo sur http://www.youtube.com/watch?v=Om1zqb2VuPM
Luigi Iannone (Télécom ParisTech) présente "Vers un renforcement de l'architecture Internet : le protocole LISP ("Locator/Identifier Separation Protocol")" lors de la Journée du Conseil scientifique de l'Afnic 2013 (JCSA2013), le 9 juillet 2013 dans les locaux de Télécom ParisTech.
JCSA2013 05 Pascal Thubert - La frange polymorphe de l'InternetAfnic
Pascal Thubert (Cisco) présente "La frange polymorphe de l'Internet" lors de la Journée du Conseil scientifique de l'Afnic 2013 (JCSA2013), le 9 juillet 2013 dans les locaux de Télécom ParisTech.
JCSA2013 03 Christian Jacquenet - Nouveau shéma d'acheminement de trafic déte...Afnic
Retrouvez la vidéo en français sur http://www.youtube.com/watch?v=3ezs-JDac0k
Christian Jacquenet (Orange Labs) présente "Un nouveau shéma d'acheminement de trafic déterministe" lors de la Journée du Conseil scientifique de l'Afnic 2013 (JCSA2013), le 9 juillet 2013 dans les locaux de Télécom ParisTech.
JCSA2013 01 Tutoriel Stéphane Bortzmeyer "Tout réseau a besoin d'identificate...Afnic
Voir la vidéo de cette présentation sur http://www.youtube.com/watch?v=HW1gkg8D7s8
Stéphane Bortzmeyer (Ingénieur R&D à l'Afnic) présente son tutoriel "Tout réseau a besoin d'identificateurs. Lesquels choisir ?" lors de la Journée du Conseil scientifique de l'Afnic 2013 (JCSA2013), le 9 juillet 2013 dans les locaux de Télécom ParisTech.
Au sujet de ce tutoriel, Stéphane Bortzmeyer indique :
Dans tout réseau, il faut identifier les objets (machines, humains, programmes en cours
d'exécution, fichiers, etc.). Cela a toujours mené à des très longs débats. Par exemple, dans les cours universitaires classiques, mais aussi dans des normes techniques comme le RFC 791, on trouve de savantes définitions des noms, des adresses, des routes, définitions que je trouve imparfaites et qui, surtout, ne collent pas du tout avec la réalité de l'Internet. On entend aussi souvent des erreurs comme de prétendre qu'un URL indique où se trouve une ressource (rien n'est plus faux). Il vaut donc mieux adopter une autre perspective, celle des propriétés.
Plutôt que d'essayer de définir la différence entre un nom et une adresse, ou de reprendre le débat philosophique entre URL et URN, attachons-nous à déterminer les propriétés des différents types d'identificateurs et voyons lesquelles sont importantes pour chaque cas d'usage.
La discussion est d'autant plus importante que, si certains identificateurs n'ont qu'on rôle technique et sont largement cachés à l'utilisateur (pensons aux adresses MAC par exemple), d'autres sont un vecteur d'identité.
Sur l'Internet, vous n'êtes pas Jean Dupont, né le 3 octobre 1978 à Bois-le-Roi, vous êtes "jdupont43" sur Twitter, vous êtes jean.dupont.fr, vous êtes jeannot@gmail.com, et
ces identificateurs, qui apparaissent à tous, sont votre identité. La première partie de l'exposé portera donc sur ces vecteurs d'identité. Quel est notre futur ?
Quelle identité sera la principale ? Aurons-nous une pluralité d'identités ou bien Facebook sera t-il le seul fournisseur d'identité (comme c'est le cas aujourd'hui pour certaines entreprises qui mettent leur identifiant Facebook sur leurs cartes de visite et publicités) ? Les identités seront-elles basées sur un système centralisé comme Facebook, sur un système arborescent comme les noms de domaine (avec, par exemple, la technologie WebFinger) ou sur autre chose ?
La deuxième partie sera consacrée aux identificateurs fondés sur le contenu. Popularisés par les magnets (utilisés notamment par BitTorrent), normalisés sous la forme des URI "ni", quelle place prendront-ils dans le bestiaire des identificateurs ? Des systèmes de résolution efficaces seront-ils mis en place pour ces identificateurs ?
The document discusses the introduction of new generic top-level domains (gTLDs) by the Internet Corporation for Assigned Names and Numbers (ICANN). It notes that while most domain names use .com and country code TLDs, ICANN's new gTLD program will allow for greater diversification. The new gTLDs will launch starting in late 2013, with some targeting specific regions, communities or industries. However, uptake of new gTLDs will depend on promotion efforts and whether users find them intuitive. The document analyzes challenges around establishing new gTLDs and ensuring users understand and adopt them.
Observatoire sur la résilience Internet en France-2012Afnic
Créé par l’Afnic & l’ANSSI, il a pour objectifs de définir puis de mesurer des indicateurs représentatifs de la résilience de l'Internet français.
Plus d'information sur http://www.afnic.fr/fr/l-afnic-en-bref/actualites/actualites-generales/7126/show/l-observatoire-sur-la-resilience-de-l-internet-francais-publie-son-rapport-2012-2.html
Afnic Public Consultation overview on the Opening of 1 and 2 charactersAfnic
This document provides an overview of a public consultation conducted by Afnic, the .fr registry, regarding opening registration of 1 and 2 character domain names under .fr. The consultation gathered opinions on possible opening procedures and naming restrictions through an online survey. Most discussion of the consultation was positive on social media. Contributions recommended a sunrise period to protect rights holders, special high pricing to prevent speculation, and limited naming restrictions. In general, the consultation suggested opening with a sunrise period, dissuasive pricing, and limited restrictions for 1 and 2 character .fr domains.
20 Comprehensive Checklist of Designing and Developing a WebsitePixlogix Infotech
Dive into the world of Website Designing and Developing with Pixlogix! Looking to create a stunning online presence? Look no further! Our comprehensive checklist covers everything you need to know to craft a website that stands out. From user-friendly design to seamless functionality, we've got you covered. Don't miss out on this invaluable resource! Check out our checklist now at Pixlogix and start your journey towards a captivating online presence today.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Introducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...Zilliz
Join us to introduce Milvus Lite, a vector database that can run on notebooks and laptops, share the same API with Milvus, and integrate with every popular GenAI framework. This webinar is perfect for developers seeking easy-to-use, well-integrated vector databases for their GenAI apps.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
31. Network Working Group Mike O’Dell
Internet-Draft UUNET Technologies
1997/02/24 01:32:32GMT
GSE - An Alternate Addressing Architecture for IPv6
<draft-ietf-ipngwg-gseaddr-00.txt>
The 16 byte IPv6 address is split into 3 pieces:
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Routing Goop | STP| End System Designator |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
6+ bytes 2 bytes 8 bytes
Routing Goop signifies where the Site attaches to the Global Internet. The Site
Topology Partition (STP) is Site-private "LAN segment" information. The End System
Designator (ESD) specifies an interface on an end-system.
Rewriting IPv6 addresses by Site Border Routers is by far the most controversial,
but also most critical part of this proposal. To control the complexity
of routing information which must be managed within a Site and to
isolate end systems and interior routers from external topology
changes, the RG of some addresses is modified by Site Border Routers.
Packets exiting a site have the RG for the Site egress point inserted into source addresses,
while packets entering a Site have the RG in all destination addresses replaced with a
canonical prefix signifying "within this Site" (the "Site-local prefix").
page 7 JCSA 2013 Paris 9 Juillet
32. Network Working Group Mike O’Dell
Internet-Draft UUNET Technologies
1997/02/24 01:32:32GMT
GSE - An Alternate Addressing Architecture for IPv6
<draft-ietf-ipngwg-gseaddr-00.txt>
The 16 byte IPv6 address is split into 3 pieces:
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Routing Goop | STP| End System Designator |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
6+ bytes 2 bytes 8 bytes
Routing Goop signifies where the Site attaches to the Global Internet. The Site
Topology Partition (STP) is Site-private "LAN segment" information. The End System
Designator (ESD) specifies an interface on an end-system.
Rewriting IPv6 addresses by Site Border Routers is by far the most controversial,
but also most critical part of this proposal. To control the complexity
of routing information which must be managed within a Site and to
isolate end systems and interior routers from external topology
changes, the RG of some addresses is modified by Site Border Routers.
Packets exiting a site have the RG for the Site egress point inserted into source addresses,
while packets entering a Site have the RG in all destination addresses replaced with a
canonical prefix signifying "within this Site" (the "Site-local prefix").
In 1997: cannot guaranty unique ESD (IID) for global Internet
page 7 JCSA 2013 Paris 9 Juillet
33. Network Working Group Mike O’Dell
Internet-Draft UUNET Technologies
1997/02/24 01:32:32GMT
GSE - An Alternate Addressing Architecture for IPv6
<draft-ietf-ipngwg-gseaddr-00.txt>
The 16 byte IPv6 address is split into 3 pieces:
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Routing Goop | STP| End System Designator |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
6+ bytes 2 bytes 8 bytes
Routing Goop signifies where the Site attaches to the Global Internet. The Site
Topology Partition (STP) is Site-private "LAN segment" information. The End System
Designator (ESD) specifies an interface on an end-system.
Rewriting IPv6 addresses by Site Border Routers is by far the most controversial,
but also most critical part of this proposal. To control the complexity
of routing information which must be managed within a Site and to
isolate end systems and interior routers from external topology
changes, the RG of some addresses is modified by Site Border Routers.
Packets exiting a site have the RG for the Site egress point inserted into source addresses,
while packets entering a Site have the RG in all destination addresses replaced with a
canonical prefix signifying "within this Site" (the "Site-local prefix").
In 1997: cannot guaranty unique ESD (IID) for global Internet
Possible with LoWPAN Network: IID is unique in this area
page 7 JCSA 2013 Paris 9 Juillet
35. L7
L2
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IPIP
IP
IP
IP
IP
IP
IP
I
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
I
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP IP
IP IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IPIP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IPIP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
IP
page 8 JCSA 2013 Paris 9 Juillet
38. Ethernet IPv6
Destination Address
Source Address
Protocol
6 Di↵Serv
Payload Length Next header Hop Limit
Source Address
Destination Address
Flow Label
page 10 JCSA 2013 Paris 9 Juillet
39. Ethernet IPv6
Destination Address
Source Address
Protocol
6 Di↵Serv
Payload Length Next header Hop Limit
Source Address
Destination Address
Flow Label
Minimum InformationMinimum Information
page 10 JCSA 2013 Paris 9 Juillet
40. Ethernet IPv6
Destination Address
Source Address
Protocol
6 Di↵Serv
Payload Length Next header Hop Limit
Source Address
Destination Address
Flow Label
Minimum InformationMinimum Information
May Evolve though other stan-
dards:
- IEEE 802.11, IEEE 802.16, ...
- MACinMAC
page 10 JCSA 2013 Paris 9 Juillet
41. Ethernet IPv6
Destination Address
Source Address
Protocol
6 Di↵Serv
Payload Length Next header Hop Limit
Source Address
Destination Address
Flow Label
Minimum InformationMinimum Information
May Evolve though other stan-
dards:
- IEEE 802.11, IEEE 802.16, ...
- MACinMAC
Fixed header, no evolution.
- Extensions are designed for this !
) Wrong design ?
- Internet is no more homogeneous
page 10 JCSA 2013 Paris 9 Juillet
57. RIPv6 6LoWPAN
Extensions
RFC 2460: With one exception, extension headers are
not examined or processed by any node along a packet’s delivery path , until
the packet reaches the node (or each of the set of nodes, in the case of multicast)
identified in the Destination Address field of the IPv6 header.
page 13 JCSA 2013 Paris 9 Juillet
58. Upward tra c: DoDAG
Breaking the Hourglass
11
21 22
31 32 33
41 42 43 44
51 52 53 54 55
Preferred
Parent
page 14 JCSA 2013 Paris 9 Juillet
59. Upward tra c: DoDAG
Breaking the Hourglass
11
21 22
31 32 33
41 42 43 44
51 52 53 54 55
Preferred
Parent
IPv6
forwarding plan
Hop
by
Hop
L4
page 14 JCSA 2013 Paris 9 Juillet