Ron Broersma presented on his organization's experiences deploying IPv6 and the challenges they faced. Some of the major issues included lack of feature parity between IPv4 and IPv6 implementations, vendors not fully supporting IPv6, and issues with privacy addresses and rogue router advertisements. He also discussed the operational complexity of managing dual-stack networks and provided an update on progress deploying IPv6 within the U.S. government. Key lessons learned included gaining hands-on operational experience with IPv6 before extensive planning and addressing common mistakes in initial addressing plans.
Possible futures for the internet: Sander Steffann, IPv6 specialist, co-chair...IPv6no
Possible futures for the internet: Sander Steffann, IPv6 specialist, co-chair, RIPE Address Policy Working group
IKT-Norge IPv6 forum IPV6 konferanse 23 & 24 mai 2011
Bei der Adressarchitektur von IPv4 beinhaltet eine IP-Adresse zwei Informationen über einen Knoten (genaugenommen ein Interface): erstens die Adresse des Interfaces (Host-ID) und zweitens die Information, wie das Interface mit dem Netzwerk verbunden ist (Subnetz). Dies ändert sich mit IPv6 nicht, ausser dass der Adressraum viel grösser ist. Dies führt zu grösseren Herausforderungen in komplexen Netzwerken, insbesondere wenn Anforderungen an Multi-Homing oder Mobilität vorliegen.
LISP (Locator/ID Separation Protocol) ist eine neue Routingarchitektur mit einer neuen Adressierungsstruktur. Dabei wird die Identität eines Gerätes, auch Endpoint Identifier genannt (EID), von seiner Position im Netzwerk, auch Routing Locator (RLOC) genannt, in zwei separate Adressräume unterteilt.
Die Präsentation geht auf verschiedene Use Cases, insbesondere die Migration von IPv4 auf IPv6 mit LISP ein.
Possible futures for the internet: Sander Steffann, IPv6 specialist, co-chair...IPv6no
Possible futures for the internet: Sander Steffann, IPv6 specialist, co-chair, RIPE Address Policy Working group
IKT-Norge IPv6 forum IPV6 konferanse 23 & 24 mai 2011
Bei der Adressarchitektur von IPv4 beinhaltet eine IP-Adresse zwei Informationen über einen Knoten (genaugenommen ein Interface): erstens die Adresse des Interfaces (Host-ID) und zweitens die Information, wie das Interface mit dem Netzwerk verbunden ist (Subnetz). Dies ändert sich mit IPv6 nicht, ausser dass der Adressraum viel grösser ist. Dies führt zu grösseren Herausforderungen in komplexen Netzwerken, insbesondere wenn Anforderungen an Multi-Homing oder Mobilität vorliegen.
LISP (Locator/ID Separation Protocol) ist eine neue Routingarchitektur mit einer neuen Adressierungsstruktur. Dabei wird die Identität eines Gerätes, auch Endpoint Identifier genannt (EID), von seiner Position im Netzwerk, auch Routing Locator (RLOC) genannt, in zwei separate Adressräume unterteilt.
Die Präsentation geht auf verschiedene Use Cases, insbesondere die Migration von IPv4 auf IPv6 mit LISP ein.
Enterprise networks using private IPv4 address space might not feel the need to migrate to IPv6. They are wrong and might be faced with severe consequences in the future.
Discussion slides for the SIP forum IPv6 task group conference call 12/12/12 covering issues with SIP DNS, SIP and locating next hop in a dual stack world and issues with Server Based ALG decisions for media paths.
Ein Anlass des www.swissipv6council.ch
Referentin: Nathalie Trenaman, RIPE NCC
Nathalie Trenaman von RIPE wird in ihrem Referat Best Practices zur Adressierung vermitteln und aufzeigen, wie Firmen zu ihrem IPv6 Range kommen. Die definitive Agenda wird so bald wie möglich bekannt gegeben.
Das Referat wird in Englisch gehalten.
18:00 Uhr
Begrüssung durch Silvia Hagen, Präsidentin Swiss IPv6 Council
18:05 Uhr
Nathalie Trenaman, RIPE
Inhalt:
1. Teil
IPv6 Adressierung
Wie muss ich ein IPv6 Netzwerk konzeptionell aufsetzen?
2. Teil
Policies
Vorstellung der Möglichkeiten für Unternehmen, sich die IPv6 Adressen zu sichern
Wer bekommt welche Ranges?
Wie muss man sich bewerben?
Q&A
Über RIPE NCC
RIPE NCC is the Regional Internet Registry responsible for IPv6 distribution in Europe, Middle East and Central Asia. We build awareness among all Internet stakeholders of the need to deploy IPv6. At this moment, RIPE NCC has over 10.000 members. 69% of these members have a block of IPv6 addresses. The first hurdle of an IPv6 deployment is building a scalable IPv6 addressing plan. Since there are so many addresses and distribution is done in subnets, a lot of engineers and architects see this phase of the deployment as one of the most challenging. Nathalie will shine a light on current best practices, taking into account different transitioning mechanisms and end users.
A presentation that tries to set an IPv6 agenda for the SIP community. VoIP and IPv6 is a natural match. If we want unified communication to be truly global and unified - we need to build solutions on IPv6 and not Ipv4.
IPv6 configuration at CSCS
● Dual Stack approach
● Static addressing for networking equipment and servers
● Dynamic addressing for PC and guest networks
– Auto configuration with SLAAC
● But we still rely on DHCPv4 to distribute DNS
– Tests ongoing for:
● Distributing DNS via RA (RDNSS, RFC6106)
● DHCPv6
IPv6 deployment
5
● Configure the network part and FW/ACLs
– Test
● Configure IPv6 on the systems
– Test
– At this point the system uses IPv6 and IPv4 for outgoing
connections
● Publish the AAAA resource record into the DNS with short TTL
– If test is succesful: set normal TTL for the RR AAAA
– Now the system is fully IPv6 enabled
IPv6 lessons learned
7
● Some network devices send out RA even if they shouldn't
– Impact: machines get IPv6 global address
● Disable SLAAC autoconfiguration on all the servers
● Rogue RA:
– Impact: default gateway changed! No IPv6 connectivity anymore..
● Filter RA messages at the network level
● IPv6 ACL: be careful not to filter NS/ND messages
– Impact: you may break IPv6 connectivity
● On IPv6 ARP is replaced by ICMPv6 NS and ICMPv6 ND messages
● Firewall IPv6 limitations (CLI config needed, WebGUI not ready)
● Services not listening on IPv6. Remember to configure ssh, httpd, etc to
listen also on IPv6
COLO: COarse-grain LOck-stepping Virtual Machines for Non-stop ServiceThe Linux Foundation
Virtual machine (VM) replication (replicating the state of a primary VM running on a primary node to a secondary VM running on a secondary node) is a well known technique for providing application-agnostic, non-stop service. Unfortunately, existing VM replication approaches suffer from excessive replication overhead and, for client-server systems, there is really no need for the secondary VM to match its machine state with the primary VM at all times.
In this paper, we propose COLO (COarse-grain LOck-stepping virtual machine solution for non-stop service), a generic and highly efficient non-stop service solution, based on on-demand VM replication. COLO monitors the output responses of the primary and secondary VMs. COLO considers the secondary VM a valid replica of the primary VM, as long as network responses generated by the secondary VM match that of the primary. The primary VM state is propagated to the secondary VM, if and only if outputs from the secondary and primary servers no longer match.
2015 update: SIP and IPv6 issues - staying Happy in SIPOlle E Johansson
What's the state of SIP and IPv6?
- An update I gave at the Netnod spring Meeting 2015.
Nothing much is happening, despite the fact that we have proven real issues with dual stacks in SIP.
Yes, IPv6 is Real! How To Make Your Apps Work (And Be As Fast As Possible) Dan York
A talk I gave at Vermont CodeCamp 11 on September 28, 2019.
---- Abstract ----
How well do your applications or websites work over IPv6? As the world runs out of IPv4 addresses, new mobile networks are being deployed as “IPv6-only” with IPv6-to-IPv4 gateways at the edge of those networks. The result is that apps and sites that work natively over IPv6 will be faster for users than apps and sites stuck on only IPv4. Many leading services have already made this transition, and Apple now requires IPv6 for all apps in their AppStore. In this session, you’ll learn about tips and tools to successfully migrate your applications and sites to work over both IPv4 and IPv6. Bring your questions and concerns - and sharing of success stories would be welcome, too.
As with any new technology, IPv6 requires a learning curve for network managers and IT administration and operations personnel. This presentation covers many of the current best practices for approaching and progressing with an IPv6 deployment.
SIP and DNS - federation, failover, load balancing and moreOlle E Johansson
SIP use DNS to find a server for a specific URI, like sip:alice@example.com. With DNS a SIP service can provide failover, load balancing and much more. SIP without DNS is a broken solution. SIP and DNS rocks!
Hands-on Experience with IPv6 Routing and ServicesCisco Canada
This IPv6 basic and advanced lab will provide you an opportunity to configure, troubleshoot, design and implement IPv6 network using IPv6 technologies and features such as; IPv6 addressing, IPv6 neighbor discovery, HSRPv6, static routing, OSPFv3, EIGRPv6 and BGPv6. You will be provided with a scenario made up with an IPv4 network where you will get the opportunity to configure and implement IPv6 based on the requirements and needs on the network. For e.g where would you deploy dual stack, where it make sense to do tunneling and how to deploy an IPv6 routing protocols without impacting your existing Network infrastructure.
Enterprise networks using private IPv4 address space might not feel the need to migrate to IPv6. They are wrong and might be faced with severe consequences in the future.
Discussion slides for the SIP forum IPv6 task group conference call 12/12/12 covering issues with SIP DNS, SIP and locating next hop in a dual stack world and issues with Server Based ALG decisions for media paths.
Ein Anlass des www.swissipv6council.ch
Referentin: Nathalie Trenaman, RIPE NCC
Nathalie Trenaman von RIPE wird in ihrem Referat Best Practices zur Adressierung vermitteln und aufzeigen, wie Firmen zu ihrem IPv6 Range kommen. Die definitive Agenda wird so bald wie möglich bekannt gegeben.
Das Referat wird in Englisch gehalten.
18:00 Uhr
Begrüssung durch Silvia Hagen, Präsidentin Swiss IPv6 Council
18:05 Uhr
Nathalie Trenaman, RIPE
Inhalt:
1. Teil
IPv6 Adressierung
Wie muss ich ein IPv6 Netzwerk konzeptionell aufsetzen?
2. Teil
Policies
Vorstellung der Möglichkeiten für Unternehmen, sich die IPv6 Adressen zu sichern
Wer bekommt welche Ranges?
Wie muss man sich bewerben?
Q&A
Über RIPE NCC
RIPE NCC is the Regional Internet Registry responsible for IPv6 distribution in Europe, Middle East and Central Asia. We build awareness among all Internet stakeholders of the need to deploy IPv6. At this moment, RIPE NCC has over 10.000 members. 69% of these members have a block of IPv6 addresses. The first hurdle of an IPv6 deployment is building a scalable IPv6 addressing plan. Since there are so many addresses and distribution is done in subnets, a lot of engineers and architects see this phase of the deployment as one of the most challenging. Nathalie will shine a light on current best practices, taking into account different transitioning mechanisms and end users.
A presentation that tries to set an IPv6 agenda for the SIP community. VoIP and IPv6 is a natural match. If we want unified communication to be truly global and unified - we need to build solutions on IPv6 and not Ipv4.
IPv6 configuration at CSCS
● Dual Stack approach
● Static addressing for networking equipment and servers
● Dynamic addressing for PC and guest networks
– Auto configuration with SLAAC
● But we still rely on DHCPv4 to distribute DNS
– Tests ongoing for:
● Distributing DNS via RA (RDNSS, RFC6106)
● DHCPv6
IPv6 deployment
5
● Configure the network part and FW/ACLs
– Test
● Configure IPv6 on the systems
– Test
– At this point the system uses IPv6 and IPv4 for outgoing
connections
● Publish the AAAA resource record into the DNS with short TTL
– If test is succesful: set normal TTL for the RR AAAA
– Now the system is fully IPv6 enabled
IPv6 lessons learned
7
● Some network devices send out RA even if they shouldn't
– Impact: machines get IPv6 global address
● Disable SLAAC autoconfiguration on all the servers
● Rogue RA:
– Impact: default gateway changed! No IPv6 connectivity anymore..
● Filter RA messages at the network level
● IPv6 ACL: be careful not to filter NS/ND messages
– Impact: you may break IPv6 connectivity
● On IPv6 ARP is replaced by ICMPv6 NS and ICMPv6 ND messages
● Firewall IPv6 limitations (CLI config needed, WebGUI not ready)
● Services not listening on IPv6. Remember to configure ssh, httpd, etc to
listen also on IPv6
COLO: COarse-grain LOck-stepping Virtual Machines for Non-stop ServiceThe Linux Foundation
Virtual machine (VM) replication (replicating the state of a primary VM running on a primary node to a secondary VM running on a secondary node) is a well known technique for providing application-agnostic, non-stop service. Unfortunately, existing VM replication approaches suffer from excessive replication overhead and, for client-server systems, there is really no need for the secondary VM to match its machine state with the primary VM at all times.
In this paper, we propose COLO (COarse-grain LOck-stepping virtual machine solution for non-stop service), a generic and highly efficient non-stop service solution, based on on-demand VM replication. COLO monitors the output responses of the primary and secondary VMs. COLO considers the secondary VM a valid replica of the primary VM, as long as network responses generated by the secondary VM match that of the primary. The primary VM state is propagated to the secondary VM, if and only if outputs from the secondary and primary servers no longer match.
2015 update: SIP and IPv6 issues - staying Happy in SIPOlle E Johansson
What's the state of SIP and IPv6?
- An update I gave at the Netnod spring Meeting 2015.
Nothing much is happening, despite the fact that we have proven real issues with dual stacks in SIP.
Yes, IPv6 is Real! How To Make Your Apps Work (And Be As Fast As Possible) Dan York
A talk I gave at Vermont CodeCamp 11 on September 28, 2019.
---- Abstract ----
How well do your applications or websites work over IPv6? As the world runs out of IPv4 addresses, new mobile networks are being deployed as “IPv6-only” with IPv6-to-IPv4 gateways at the edge of those networks. The result is that apps and sites that work natively over IPv6 will be faster for users than apps and sites stuck on only IPv4. Many leading services have already made this transition, and Apple now requires IPv6 for all apps in their AppStore. In this session, you’ll learn about tips and tools to successfully migrate your applications and sites to work over both IPv4 and IPv6. Bring your questions and concerns - and sharing of success stories would be welcome, too.
As with any new technology, IPv6 requires a learning curve for network managers and IT administration and operations personnel. This presentation covers many of the current best practices for approaching and progressing with an IPv6 deployment.
SIP and DNS - federation, failover, load balancing and moreOlle E Johansson
SIP use DNS to find a server for a specific URI, like sip:alice@example.com. With DNS a SIP service can provide failover, load balancing and much more. SIP without DNS is a broken solution. SIP and DNS rocks!
Hands-on Experience with IPv6 Routing and ServicesCisco Canada
This IPv6 basic and advanced lab will provide you an opportunity to configure, troubleshoot, design and implement IPv6 network using IPv6 technologies and features such as; IPv6 addressing, IPv6 neighbor discovery, HSRPv6, static routing, OSPFv3, EIGRPv6 and BGPv6. You will be provided with a scenario made up with an IPv4 network where you will get the opportunity to configure and implement IPv6 based on the requirements and needs on the network. For e.g where would you deploy dual stack, where it make sense to do tunneling and how to deploy an IPv6 routing protocols without impacting your existing Network infrastructure.
This session focuses on IPv6 deployment options for the enterprise and commercial network manager, with in-depth information about IPv6 configuration and transition methods. IPv6 deployment considerations for specific areas of the network such as campus, WAN or branch, remote access, and data center are discussed. The session features best practices for deploying IPv6 with a variety of associated technologies and operating systems.
Einbrüche, Viren, Trojaner, machen auch unter IPv6 nicht Halt. Als Marktführer im Bereich Unified-Threat-Management (UTM) entwickelt Fortinet umfassende Sicherheitslösungen zur Bekämpfung solcher Bedrohungen - für IPv4 und IPv6 Netzwerke. Der Workshop orientierte Vortrag zeigt die Notwendigkeit von umfassenden Security Lösungen bei der Migration zu IPv6 auf.
4. IPv6 Security - Workshop mit Live Demo - Marco Senn FortinetDigicomp Academy AG
Einbrüche, Viren, Trojaner, machen auch unter IPv6 nicht Halt. Als Marktführer im Bereich Unified-Threat-Management (UTM) entwickelt Fortinet umfassende Sicherheitslösungen zur Bekämpfung solcher Bedrohungen - für IPv4 und IPv6 Netzwerke. Der Workshop orientierte Vortrag zeigt die Notwendigkeit von umfassenden Security Lösungen bei der Migration zu IPv6 auf.
IETF IPv6 Activities Report by Cathy Aronson at ARIN 36. Presentation and webcast archive available at: https://www.arin.net/participate/meetings/reports/ARIN_36/ppm.html
Troubleshooting Dual-Protocol Networks and Systems by Scott Hogg at gogoNET L...gogo6
gogo6 IPv6 Video Series. Event, presentation and speaker details below:
EVENT
gogoNET LIVE! 3: Enterprise wide Migration. http://gogonetlive.com
November 12 – 14, 2012 at San Jose State University, California
Agenda: http://gogonetlive.com/4105/gogonetlive3-agenda.asp
PRESENTATION
Troubleshooting Dual-Protocol Networks and Systems
Abstract: http://www.gogo6.com/profiles/blogs/my-presentation-at-gogonet-live-3-troubleshooting-in-a-dual-stack
Presentation video: http://www.gogo6.com/video/troubleshooting-dual-protocol-networks-and-systems-by-scott-hogg
Interview video: http://www.gogo6.com/video/interview-with-scott-hogg-at-gogonet-live-3-ipv6-conference
SPEAKER
Scott Hogg - Director of Advanced Technology Services, GTRI
Bio/Profile: http://www.gogo6.com/profile/ScottHogg986
MORE
Learn more about IPv6 on the gogoNET social network
http://www.gogo6.com
Get free IPv6 connectivity with Freenet6
http://www.gogo6.com/Freenet6
Subscribe to the gogo6 IPv6 Channel on YouTube
http://www.youtube.com/subscription_center?add_user=gogo6videos
Follow gogo6 on Twitter
http://twitter.com/gogo6inc
Like gogo6 on Facebook
http://www.facebook.com/pages/IPv6-products-community-and-services-gogo6/161626696777
50 billion connected wireless devices... IPv6, anyone?: Fredrik Garneij, Syst...IPv6no
50 billion connected wireless devices... IPv6, anyone?: Fredrik Garneij, Systems Manager, Ericsson
IKT-Norge IPv6 forum IPV6 konferanse 23 & 24 mai 2011
Mobile Broadband and IPv6 in Slovenia: Jan Zorz, Co-Founder Go6 Institute og ...IPv6no
Mobile Broadband and IPv6 in Slovenia: Jan Zorz, Co-Founder Go6 Institute og aktiv bidragsyter i RIPE-community
IKT-Norge IPv6 forum IPV6 konferanse 23 & 24 mai 2011
IPv6 - The Time Is Now: Latif Ladid, President, IPv6 forumIPv6no
IPv6 - The Time Is Now. Resistance is Futile & IPv6 Ready program: Latif Ladid, President, IPv6 forum
IKT-Norge IPv6 forum IPV6 konferanse 23 & 24 mai 2011
Fra IPv4 til IPv6 bakgrunn og historie: Hans Petter Holen, IT Direktør, Visma...IPv6no
Fra IPv4 til IPv6 bakgrunn og historie: Hans Petter Holen, IT-direktør, Visma & ICANN Address Council
IKT-Norge IPv6 forum IPV6 konferanse 23 & 24 mai 2011
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Search and Society: Reimagining Information Access for Radical Futures
Ron Broersma dren-stavanger-22 nov2011
1. Enterprise IPv6 Deployment Experiences
- and -
Deployment to U.S. Government
Norwegian IPv6 Conference
22Nov, 2011
Stavanger, Norway
Ron Broersma
DREN Chief Engineer
SPAWAR Network Security Manager
Federal IPv6 Task Force
ron@spawar.navy.mil
3. The major issues for us
• Lack of IPv6/IPv4 feature parity
– taking too long to get there
• Vendors not eating own dogfood
– but starting to turn around
• Rogue RAs
– set router priority to “high” as workaround
• Privacy Addresses (RFC4941)
– no good solution yet
• MacOSX 10.6
– but starting to get much better (10.6.8, 10.7)
• Network Management over IPv6
• Operational Complexity
22-Nov-2011 3
4. Lack of “feature parity”
• “feature parity” between IPv4 and IPv6 is
something we expect in all products.
– If the device supports a capability in IPv4, we
want it to support that same capability in IPv6.
• Nobody delivers feature parity today.
– Some vendors are working to fix this.
• Until we achieve feature parity...
– IPv6 is something less than IPv4
– You may need to re-engineer your network to
accommodate missing features.
22-Nov-2011 4
5. Privacy Addresses (RFC 4941)
• Incompatible with many Enterprise environments
– Need address stability for many reasons
•Logging, Forensics, DNS stability, ACLs, etc.
• Enabled by default in Windows
– Breaks plug-n-play because we have to visit every Windows
machine to disable this feature.
• Just added in Mac OS X “Lion”.
• Now default in latest openSuSE (12.1)
• Ubuntuthinking about making it default.
[Privacy addresses] are horrible and I hope nobody really uses them, but they're better than NAT.
… Owen DeLong, Hurricane Electric
22-Nov-2011 5
6. Living with Privacy addresses
• Where your clients support DHCPv6, use that to
assign addresses
– No DHCPv6 client support in Windows XP, Mac OSX before 10.7
(Lion), etc.
• If all your Windows systems are in Active Directory,
use GPO to disable privacy addresses
• Options for other systems:
– configure system to disable privacy addresses
• registry setting in Windows (see below)
– configure addresses statically on the hosts
– keep a historical record of all MAC address to IPv6 address
mappings for every host, for correlation in IDS and forensics tools
netsh interface ipv6 set privacy state=disabled store=persistent
netsh interface ipv6 set global randomizeidentifiers=disabled store=persistent
22-Nov-2011 6
7. Rogue Router Advertisements
See RFC 6104
• Router Advertisements (RAs) inform hosts of the default
router/gateway
• Windows systems with Internet Connection Sharing (ICS)
enabled, and IPv6 enabled, will announce itself as the
default router using RAs (“Rogue RAs”).
– VERY common problem
• Hosts then start sending all their default traffic to the
Windows system
• Workaround: set router preference to “high” (RFC 4191)
– Doesn’t work on JunOS
• Long term: “RA Guard” (RFC 6105) or SeND (RFC 3971)
22-Nov-2011 7
8. Network Management
• Can you do all your network management over
IPv6?
• Not yet, but very soon
• Most products cannot be managed over IPv6-only
• Goal: IPv6-only on management LAN by January
2011
• already removed all IPv4 configuration from all layer-2
switches
• changed vendors in some cases
• eliminated old hardware that will never support IPv6
• awaiting software updates to resolve last remaining
issues
22-Nov-2011 8
10. Operational Complexity
• Added complexity increases security risk
• dual-stack can be more complex than IPv4
alone
• example: firewalls
– are all your policies equivalent?
– how do you keep them in sync?
– twice as much work?
This may incentivize us to shut down IPv4 sooner than later
22-Nov-2011 11
11. World IPv6 day
• For DREN and SPAWAR, nothing new to turn
on for the day
– every day is IPv6 day for us
• What does it look like from an enterprise
perspective, where ALL clients (users) are
dual-stack?
22-Nov-2011 12
12. Percentage of Internet
traffic over IPv6
• 1% (2009, before Google whitelisting)
• 2.5% (Google whitelisted)
• 10% (late Jan 2010, Youtube added)
• World IPv6 day… (peak at 68%)
22-Nov-2011 13
13. After IPv6 day
• Percentages across a day (5 min averages):
22-Nov-2011 14
14. After IPv6 day
• Past week (hourly averages):
• Month (daily averages):
22-Nov-2011 15
15. Many enterprises have not
started their IPv6 deployment
• Reasons:
– Lack of incentives and resources
– Other higher priorities (improving security)
– It all seems overwhelming, and don't know where to start.
– No “business case”
• My answer:
– If you haven't started, you're late and at risk
– It doesn't take additional resources if you do it right.
– For U.S. Federal agencies, there is a new mandate.
– Don't waste time on developing a business case.
• Its a matter of business continuity.
– “Don't be afraid to break some glass”
22-Nov-2011 16
17. US Federal Agencies
• Earlier mandates didn’t work
• New mandate to IPv6-enable public facing
services by Sept 2012
• Transition managers assigned in each agency
• Lots of planning, with little or no operational
experience
• Addressing plans have problems
• Almost no progress on actually IPv6-enabling
anything
• Major Carriers are not ready
– even though they claim otherwise in public
• World IPv6 Day – missed opportunities
22-Nov-2011 18
18. US GovtDeployment Status
http://usgv6-deploymon.antd.nist.gov
(or just search for “USG IPv6 Status”)
22-Nov-2011 19
19. Something is missing:
IPv6 Operational Experience
• Lots of planning is underway
– transition planning
– address planning
• Much of this planning is done by individuals who
have never touched an IPv6 packet
• Too much energy is being wasted on plans that are
flawed, because they are not based on operational
experience
• It is more important to turn on IPv6 now and start
moving some IPv6 traffic, than it is to have a
complete plan
22-Nov-2011 20
20. Some Lessons Learned
• Gain operational IPv6 experience before putting too
much effort into enterprise-wide planning
• Addressing Plans
– everyone makes the same mistakes
• Go native (dual stack)
• Start from outside, and work in
– focus now on public facing services
• There will be challenges (surprises) along the way
• You can automate the DNS updates
• It doesn’t require significant resources, if you start
early and leverage tech refresh
22-Nov-2011 21
21. Addressing Plans
• Without sufficient operational experience with IPv6
deployment, you WILL get it wrong at first.
– usually takes the 3rd time to get it right
• Planners are hindered by IPv4-thinking
– being conservative with address space
– thinking “hosts” instead of “subnets”
22-Nov-2011 22
22. Addressing Plans
• Common mistakes
– Doing other than /64 for subnets
• Didn’t read RFC 4291 nor 5375
– Thinking that the addressing plan has to be
perfect the first time
• because you can’t afford to re-address
– Choosing allocations for sites based on size of site
• because /48 for all sites is too wasteful
– Justification “upwards”, instead of pre-allocation
“downwards”
– Host-centric allocation instead of subnet-centric
22-Nov-2011 23
23. Making the paradigm shift
• You may be un-qualified to develop an IPv6
addressing plan if you think:
– /64 for subnets is wasteful
– /64 for point-to-point links is wasteful
– /48 for small sites is wasteful
22-Nov-2011 24
24. Once again…
When doing an address plan, a major driver in IPv4
was efficiency and conservation
In IPv6, efficiency and conservation is NOT a major
driver, but instead it is all about better alignment
with network topology, accommodation of security
architecture, and operational simplicity through
standardization
22-Nov-2011 25
25. Addressing Plans
• After operational experience, you realize:
– you never have to “grow” subnets, so you don’t need to
accommodate that situation
– if you don’t use /64’s for subnets, you can’t do SLAAC, DHCPv6,
Multicast with Embedded-RP, etc.
– there is a huge opportunity to align addressing with security
topology, to simplify ACLs
– you can better align subneting and aggregation with existing
topology
– it is a bad idea to embed IPv4 addresses in IPv6
– nibble (4 bit) boundaries align better with PTR records
– every interface has multiple IPv6 addresses
– internal aggregation is not as important as you initially thought
– you can do a lot of pre-allocation
22-Nov-2011 26
26. Feedback received after I
presented the above
• From one of the Federal Agency Engineers:
– “using /64 everywhere including point-to-point
links is crazy”
– “RFCs aren’t rules... There will be new RFCs”
– “wait with deploying IPv6 until these problems are
worked out”
– “If everybody in the world did what the presenter
did, then we will indeed run out of IPv6
addresses”
– “I hope all agencies don’t follow his aggressive
recommendations like sheep”
22-Nov-2011 27
27. Other common mistakes
• Working from inside out
• Thinking that “native IPv6” means that you
have to disable IPv4
• Too much use of translators
• Missed opportunities
22-Nov-2011 28
28. Final Thoughts, Summary
• Only use providers and suppliers that have a
good IPv6 story
• IPv6 is ready for deployment to the Enterprise
• Most important to IPv6-enable the public
Internet now
• Large bureaucracies have major challenges
ahead
– we need to help, and it may also require standards
cast into strong policy
22-Nov-2011 29
30. Benefits of IPv6 today
(examples)
• Addressing
– can better map subnets to reality
– can align with security topology, simplifying ACLs
– sparse addressing (harder to scan/map)
– never have to worry about “growing” a subnet to hold new
machines
– auto-configuration, plug-n-play
– universal subnet size, no surprises, no operator confusion,
no bitmath
– shorter addresses in some cases
– at home: multiple subnets rather than single IP that you
have to NAT
• Multicast is simpler
– embedded RP
– no MSDP
22-Nov-2011 31