DOCSLIB.ORG

Ipv4 and Ipv6 – Icons and Terminology

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Ipv4 and Ipv6 – Icons and Terminology IPv6 in Enterprise Unified Communications Networks BRKCOL-2020 Tony Mulchrone - Technical Marketing Engineer Cisco Collaboration Technology Group Agenda IPv6 Addressing summary IPv6 and UC Networks summary IPv6 Addressing and Cisco devices DHCP and DNS for IPv6 IPv6 Campus and WAN Deployment Options IPv6 UC Configuration CUCM IPv6 Device Configuration Parameters and Media Handling Other IPv6 Design Considerations IPv6 UC Deployment Guidelines Summary Why Deploy IPv6 ? • IPv6 deployment is primarily driven by IPv4 address space exhaustio • The number of applications, devices, services requiring IP addresses is rapidly increasing as the world becomes more and more IP centric • Addresses in IPv6 are 128 bits long versus 32 bits IPv4 address. The larger address space avoids the potential exhaustion of IP addresses without need for Network Address Translation. • By avoiding the need for complex sub-netting scheme, IPv6 addressing space easier to understand, making administration of medium and larger networks simpler. • IPv6 hosts can be configured automatically using Stateless Address Auto- Configuration (SLACC) when connected to a routed IPv6 network using ICMPv6 router discovery messages. BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 4 IPv6 Addressing Space IPv4 = 32 bits IPv6 = 128 bits • IPv4 uses 32 bits • = ~ 4,200,000,000 possible addressable nodes • CIDR and NAT techniques used to make the best possible use of address space • IPv6 uses 128 bits • = 340,282,366,920,938,463,463,374,607,431,768,211,456 nodes • = 52 Trillion Trillion addresses per person in the world • = More than enough • Allows for scalable, simple and easily understandable addressing schemes BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 5 IPv6 Address Format • An IPv6 address is composed of 8 sets of 16 bit hexadecimal values, 128 bits in length • 2001:0db8:1234:5678:9abc:def0:1234:5678 • 16 bit hex values are separated by colons (:) • Abbreviation is possible Leading zeros can be omitted Consecutive zeros in contiguous blocks can be represented by (::) • 2001:0db8:0000:130F:0000:0000:087C:140B • becomes • 2001:0db8:0:130F::87C:140B Double colons can only appear once in the address • Network prefix representation like IPv4 CIDR --- • e.g. 2001:db8:12::/64 BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 6 IPv6 Address Network and Host IDs Network ID Host ID XXXX:XXXX:XXXX:XXXX:YYYY:YYYY:YYYY:YYYY 64 Bits 64 Bits IPv6 Unicast addresses use 64 bits for the Network ID and 64 00 90 27 17 FC 0F bits for the Host ID The Host ID can be auto-configured by : 00 90 27 17 FC 0F 1) Using a randomly generated number, or FF FE 2) By using the (Extended Unique Identifier) EUI-64 format. 00 90 27 FF FE 17 FC 0F This format expands the 48 bit MAC address to 64 bits by 1 = Unique ID inserting FFFE into the middle 16 bits. Cisco commonly uses 000000U0 Where U= this Host ID format. 0 = Not Unique U = 1 3) The host ID can also be assigned using DHCPv6 or manually configured 02 90 27 FF FE 17 FC 0F BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 7 IPv6 - Addressing Model • Addresses are assigned to interfaces • An Interface is expected to have multiple addresses • Addresses have “scope” Link Local Unique Local Global Global Unique Local Link Local BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 8 Primary Types of IPv6 Address • Unicast Address Identifies a single node/interface. Traffic destined to a Unicast address is forwarded to a single interface • Multicast Address Identifies a group of nodes/interfaces. Traffic destined to a Multicast address is forwarded to all the nodes in the group • No more Broadcast addresses Too resource intensive, IPv6 uses Multicast addresses instead BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 9 Link-Local Unicast Addresses 128 Bits Remaining 54 Bits Interface ID 1111 1110 10 FE80::/10 10 Bits Link-Local Addresses are : • Mandatory addresses - used exclusively for communication between two IPv6 devices on the same link. • Automatically assigned by the device as soon as IPv6 is enabled • Only Link Specific scope – not routed • Remaining 54 bits of network ID are typically zero but could be set to any manually configured value • Interface ID has the same meaning for all unicast addresses, 64 bits long using the EUI-64 format • Example - FE80:0000:0000:0000:0987:65FF:FE01:2345 • Generally represented as FE80::987:65FF:FE01:2345 BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 10 Unique-Local Unicast Addresses 128 Bits 1 Global ID 40 Bits Interface ID 1111 110 Subnet ID FD00::/7 16 Bits 7 Bits 1 Bit : L = 1 Locally assigned; L = 0 Future Use Unique-Local Addresses are : • Analogous to Private IPv4 addresses (e.g. 10.1.1.254) • Not Routable on the Internet – (would require IPv6 NAT) • Global IDs do not have to be aggregated • Subnet IDs are defined by the administrator of the local domain • Subnet IDs typically use a hierarchical addressing plan to allow for route summarization • Interface ID has the same meaning for all unicast addresses, 64 bits long using the EUI-64 format • Example - FD00:aaaa:bbbb:CCCC:0987:65FF:FE01:2345 BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 11 Global Unicast Addresses Network ID RIR ISP LAN Host 3 21 Bits 24 Bits 16 Bits 64 Bits Global Prefix TLA NLA SLA Interface ID 001 /24 /48 /64 Global Unicast Addresses are : • Routable / reachable across the Internet • Identified by their 3 high level bits set to 001 ( 2000::/3 ) • Global Routing Prefix assigned to Regional Internet Registries by Internet Assigned Numbers Authority (IANA) – Next Level Aggregator (NLA) assigned to ISP • Site Level Aggregator (Subnet ID) assigned to a customer by their Service Provider • Example - 2001:0DB8:BBBB:CCCC:0987:65FF:FE01:2345 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public IPv6 Multicast Addresses 128 Bits 8-bits 4-bits 4-bits 112-bits 1111 1111 Lifetime Scope Group-ID Lifetime Scope 0 If Permanent 1 Node 1 If Temporary 2 Link 5 Site 8 Organization E Global IP multicast addresses have a prefix FF00::/8 (1111 1111) The second octet defines the lifetime and scope of the multicast address Used for Router Advertisements, DHCP, Multicast Applications Multicast addresses are always destination addresses BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 13 Some Well-Known Multicast Addresses Address Scope Meaning FF01::1 Node-Local Same Node FF02::1 Link-Local All Nodes on a Link FF01::2 Node-Local Same Router FF02::2 Link-Local All Routers on a Link FF05::2 Site-Local All Routers on Intranet FF02::1:FFXX:XXXX Link-Local Solicited-Node More details at http://www.iana.org/assignments/ipv6-multicast-addresses Solicited Node Addresses - Used for Neighbor Discovery and Duplicate Address Detection © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public Agenda IPv6 Addressing summary IPv6 and UC Networks summary IPv6 Addressing and Cisco devices DHCP and DNS for IPv6 IPv6 Campus and WAN Deployment Options IPv6 UC Configuration CUCM IPv6 Device Configuration Parameters and Media Handling Other IPv6 Design Considerations IPv6 UC Deployment Guidelines Summary IPv4 and IPv6 – Icons and Terminology v4 IPv4 Only Device communicates with and understands IPv4 addresses only v6 IPv6 Only Device communicates with and understands IPv6 addresses only v4 v6 Dual Stack (IPv4 and IPv6) with ANAT This device communicates with and understands both IPv4 and IPv6 addresses and can also negotiate the use of either IPv4 or IPv6 for media v4 v6 IPv6 Aware Device communicates with IPv4 addresses, but can receive and understand IPv6 addresses embedded in Application PDUs – Typically used by applications which use IPv4 to transport IPv6 information BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 16 IPv4 and IPv6 Product Support UC11.X - Summary (1 of 2) • v4 v6 v4 v6 Call Control CUCM 7.1(2)+ IM & P Services 10.5(1) – External Connections only e.g. federation CUBE 12.4(22)T+ CUCME 8.0+ v4 v6 v4 v6 • Cisco IP Phones 7906G, 7911G, 7931G, 7941G, 7941GE, 7942G, 7945G, 7961G, 7961GE, 7962G, 7965G, 7970G, 7971G-GE, 7975G 6901, 6911, 6921, 6922, 6941, 6942, 6945, 6946, 6961, 6962 3905, 7821, 7841, 7845, 7861, 8961, 9951, 9971 SIP based Cisco Telepresence Endpoints: C20, C40, C60, C90, MX Series, DX Series, EX Series, SX20, SX60 BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 17 IPv4 and IPv6 Product Support UC11.X - Summary (2 of 2) • Gateways v4 v6 v4 v6 IOS SIP Gateways – ISR G2 , ASR SCCP/SIP Analogue Gateways – VG Gateway platforms SCCP FXS ports on ISR G2 routers IOS software and harwdare MTPs for IPv4 - IPv6 RTP Media conversion CUBE IPv4 to IPv6 voice interworking v4 v6 v4 v6 • CUCM SIP Trunks IPv4/IPv6 signalling, ANAT for Dual stack media negotiation v4 v6 v4 v6 • Applications Unity Connection – IPv4, IPv4/IPv6 ANAT Cisco WebEx Meeting Server – IPv4, IPv4/IPv6 ANAT for Web/Audio connections only. Cisco Prime Collaboration Suite – IPv4, IPv6 Aware Cisco Meeting Server - IPv4, IPv6 Cisco Telepresence Server - IPv4, IPv4/IPv6 ANAT; Cisco TP Conductor – IPv4 BRKCOL-2020 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 18 IPv6 Capable UC Devices – Summary SIP Trunks H323 ICT Trunks v4 v6 v4 v6 v4 IPv4/IPv6 IPv4 Only Jabber SRST Mobile v4 v4 Clients Soft CUCME (SCCP Phones only) Phones v4 SCCP ISR v4 v6 v4 v6 Analogue Ports SIP TelePresence CUBE / SIP VG Analogue Endpoints v4 v6 v4 v6 v4 v6 Gateways Gateways Cisco Expressway C/E Newer SIP Older SCCP based Phones v4 v6 based Phones v4 v4 Older SIP based MGCP/ H323 Newer SCCP v4 v6 Gateways based Phones Phones v4 v4 BRKCOL-2020 © 2017 Cisco and/or its affiliates.
Load more

Recommended publications
  • SIP Software for Avaya 1200 Series IP Deskphones-Administration
    SIP Software for Avaya 1200 Series IP Deskphones-Administration Release 4.4 NN43170-601 Issue 06.05 Standard July 2015 © 2015 Avaya Inc. list of Heritage Nortel Products located at http://support.avaya.com/ All Rights Reserved. LicenseInfo under the link “Heritage Nortel Products” or such successor site as designated by Avaya. For Heritage Nortel Notice Software, Avaya grants You a license to use Heritage Nortel While reasonable efforts have been made to ensure that the Software provided hereunder solely to the extent of the authorized information in this document is complete and accurate at the time of activation or authorized usage level, solely for the purpose specified printing, Avaya assumes no liability for any errors. Avaya reserves in the Documentation, and solely as embedded in, for execution on, the right to make changes and corrections to the information in this or for communication with Avaya equipment. Charges for Heritage document without the obligation to notify any person or organization Nortel Software may be based on extent of activation or use of such changes. authorized as specified in an order or invoice. Documentation disclaimer Copyright “Documentation” means information published by Avaya in varying Except where expressly stated otherwise, no use should be made of mediums which may include product information, operating materials on this site, the Documentation, Software, Hosted Service, instructions and performance specifications that Avaya may generally or hardware provided by Avaya. All content on this site, the make available to users of its products and Hosted Services. documentation, Hosted Service, and the product provided by Avaya Documentation does not include marketing materials.
    [Show full text]
  • Using PANA for Mobile Ipv6 Bootstrapping Julien Bournelle, Jean-Michel Combes, Maryline Laurent, Sondes Larafa
    Using PANA for mobile IPv6 bootstrapping Julien Bournelle, Jean-Michel Combes, Maryline Laurent, Sondes Larafa To cite this version: Julien Bournelle, Jean-Michel Combes, Maryline Laurent, Sondes Larafa. Using PANA for mobile IPv6 bootstrapping. NETWORKING 2007 : 6th international IFIP-TC6 networking conference on ad hoc and sensor networks, wireless networks, next generation Internet, May 2007, Atlanta, United States. pp.345 - 355, 10.1007/978-3-540-72606-7_30. hal-01328113 HAL Id: hal-01328113 https://hal.archives-ouvertes.fr/hal-01328113 Submitted on 7 Jun 2016 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Using PANA for Mobile IPv6 Bootstrapping Julien Bournelle1, Jean-Michel Combes2, Maryline Laurent-Maknavicius1, Sondes Larafa1 1 GET/INT, 9 rue Charles Fourier, 91011 Evry, France 2 France Telecom R&D, 38/40 rue du General Leclerc, 92784 Issy-Les-Moulineaux, France Abstract One of the current challenge of the Mo- 2 Mobile IPv6 Overview bile IPv6 Working Group at the IETF is to dynami- As it stands in [1], an IPv6 Mobile Node (MN) is cally assign to a Mobile Node its Home Agent, Home uniquely identi¯ed by its Home Address (HoA), and Address and to setup necessary security associations.
    [Show full text]
  • Spirent AION
    DATASHEET Spirent AION Spirent TestCenter Broadband Access Standard and Advanced Bundles, Carrier • Enhanced Realism—Spirent Ethernet Bundle TestCenter Access test solution Overview emulates real world broadband subscriber behaviors, Triple Play Spirent AION is a flexible delivery platform that enables users to achieve improved services, and failure scenarios deployment and provisioning for all their cloud and network testing needs. It is designed to deliver ultimate flexibility in how Spirent TestCenter platforms are • Improved Testing Capacity— purchased and utilized. accomplish more in less lab space The extended platform combines a wealth of industry-leading test solutions with a with the highest number of emulated flexible licensing architecture to support a wide range of next-generation solution- subscribers and user planes per port based domain applications. and port density AION offers a centralized management hub to help leverage software and hardware • Reduced Test Time—set up tests functionalities across all lab users and locations for a simplified management and quickly and easily to validate decision-making process: system performance in realistic, unstable environments rather than • Flexible purchasing options available via subscription, consumption-based, and perpetual plans, with the ability to license different bandwidth, scale, and protocol bundles. an environment optimized for pure performance • Flexible deployment options offered include cloud-delivery, on-prem, and laptop-hosted licensing services. • Detailed Analysis—Data
    [Show full text]
  • LANCOM Datasheet
    LANCOM Operating System (LCOS) 10.40 Top performance and efficiency for your SD-WAN A Next-generation SD-WAN – LANCOM High Scalability VPN (HSVPN) greatly improves efficiency as it requires fewer VPN tunnels A A fresh look & feel – WEBconfig has been completely redesigned for an intuitive and modern appearance A Multicast routing – new possibilities with multimedia applications in LANCOM infrastructures DATASHEET LANCOM Operating System General Feature Overview Firewall IPv4/IPv6 Stateful inspection, IP packet filter with port ranges, object-oriented rule definition. IPv4 Masking (NAT/PAT) of TCP, UDP, ICMP, FTP, PPTP, H.323, Net-Meeting, IRC and IPSec; DNS forwarding. Extended port forwarding and N:N mapping. Support for up to 256 contexts with individual IP networks, VLANs and interfaces, bandwidth management, QoS and VLAN prioritization for VoIP and VoWLAN Operating modes LAN protocols ARP, Proxy ARP, IPv4, ICMP, UDP, TCP, TFTP, RIP-1, RIP-2, DHCP, DNS, SNMP, HTTP, HTTPS, SSH, Telnet and SIP, BOOTP, NTP/SNTP, NetBIOS, RADIUS, TACAS+, LANCAPI, VRRP, STP/RSTP, IGMP, IPv6, DHCPv6, SLAAC, MLD, NDP, ICMPv6 WAN protocols (Ethernet) PPPoE, PPTP (PAC or PNS) and Plain Ethernet (with and without DHCP), RIP-1, RIP-2, IPv6CP, 6to4 Tunnel, 6in4 Tunnel, 6rd Tunnel, DHCPv6, SLAAC, L2TPv3 for Ethernet Pseudowires Multiprotocol router IPv4/IPv6 router, NAT/Reverse NAT (IP- masquerading), DHCPv4/DHCPv6 server, DHCPv4/DHCPv6 client, DHCPv4/DHCPv6 relay server, DNS server, PPPoE client / Multi-PPPoE, ML-PPP, PPTP (PAC and PNS), NetBIOS proxy, DynDNS client,
    [Show full text]
  • Technical Security Guideline on Deploying Ipv6
    Draft Recommendation ITU-T X.1037 (X.ipv6-secguide) Technical security guideline on deploying IPv6 Summary The Internet protocol version 6 (IPv6) is intended to provide many built-in benefits such as large address space, mobility, and quality of service (QoS), because it is a new protocol and operates in some different ways than Internet protocol version 4 (IPv4), both foreseeable and unforeseeable security issues will arise. Many new functions or requirements of IPv6, i.e., automatic configuration of interfaces, mandatory Internet protocol security (IPSec), mandatory multicast, multiple Internet protocol (IP) addresses and many new rules for routing, can be abused for compromising computer systems or networks. Considering the above circumstances, Recommendation ITU-T X.1037 provides a set of technical security guides for telecommunication organizations to implement and deploy IPv6 environment. The content of this Recommendation focuses on how to securely deploy network facilities for telecommunication organizations and how to ensure security operations for the IPv6 environment. Keywords ???? - 2 - CONTENTS 1 Scope ............................................................................................................................. 3 2 References ..................................................................................................................... 3 3 Definitions .................................................................................................................... 4 3.1 Terms defined elsewhere ...............................................................................
    [Show full text]
  • Junos® OS Ipv6 Neighbor Discovery User Guide Copyright © 2021 Juniper Networks, Inc
    Junos® OS IPv6 Neighbor Discovery User Guide Published 2021-09-23 ii Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. Junos® OS IPv6 Neighbor Discovery User Guide Copyright © 2021 Juniper Networks, Inc. All rights reserved. The information in this document is current as of the date on the title page. YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036. END USER LICENSE AGREEMENT The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement ("EULA") posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA. iii Table of Contents About This Guide | vii
    [Show full text]
  • 8544 Computer Networking Hardware Operations
    Computer Networking Hardware Operations III 8544/18 weeks Table of Contents Acknowledgments ................................................................................................................................... 2 Course Description .................................................................................................................................. 3 Task Essentials Table .............................................................................................................................. 3 Curriculum Framework ........................................................................................................................... 6 Exploring Basic Device Configuration ..................................................................................................... 6 Describing Switching Concepts ............................................................................................................... 7 Understanding Virtual Local Area Networks (VLANs) ............................................................................ 8 Troubleshooting Inter-VLAN Routing ..................................................................................................... 9 Describing Spanning Tree Protocol (STP) ............................................................................................. 10 Exploring EtherChannel ........................................................................................................................ 10 Describing Dynamic Host Configuration Protocol
    [Show full text]
  • Ipv6 Access Services: Dhcpv6 Relay Agent
    IPv6 Access Services: DHCPv6 Relay Agent A Dynamic Host Configuration Protocol for IPv6 (DHCPv6) relay agent, which may reside on the client's link, is used to relay messages between the client and the server. • Finding Feature Information, page 1 • Information About IPv6 Access Services: DHCPv6 Relay Agent, page 1 • How to Configure IPv6 Access Services: DHCPv6 Relay Agent, page 5 • Configuration Examples for IPv6 Access Services: DHCPv6 Relay Agent, page 6 • Additional References, page 6 • Feature Information for IPv6 Access Services: DHCPv6 Relay Agent, page 7 Finding Feature Information Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Information About IPv6 Access Services: DHCPv6 Relay Agent DHCPv6 Relay Agent A DHCPv6 relay agent, which may reside on the client’s link, is used to relay messages between the client and the server. The DHCPv6 relay agent operation is transparent to the client. A DHCPv6 client locates a DHCPv6 server using a reserved, link-scoped multicast address. For direct communication between the DHCPv6 client and the DHCPv6 server, both of them must be attached to the same link.
    [Show full text]
  • CERN Dhcpv6 Implementation
    CERN DHCPv6 implementation WLCG Workshop 2017 - Manchester 21st of June 2017 [email protected] Why DHCPv6 and not SLAAC CERN DHCP[v6] servers offer a lease only to registered MAC addresses, because of: - device tracking for - user’s own security - user traceability - user support - DNS and Firewall automation - static address assignment (optional) 2 DHCPv6 client-server exchange 1. The client sends a Solicit message to the All_DHCP_Relay_Agents_and_Servers multicast address, requesting the assignment of addresses and other configuration information 2. The server responds with a Reply message that contains the confirmed addresses and configuration. Each address assigned to the client has associated preferred and valid lifetime … 3a. Periodically, the client sends a Renew message to the server to request an extension of the lifetimes of an address 3b. The server sends a Reply message to the client with the new lifetimes, allowing the client to continue to use the address without interruption [RFC3315] 3 DHCPv6 Options - IPv6 address, OPTION_IAADDR [RFC3315] - DHCPv6 timers: - preferred-lifetime (time a valid address is preferred) - valid-lifetime (time an address remains in valid state) [RFC2462] - DNS servers, OPTION_DNS_SERVERS [RFC3646] Other options exist 4 DHCPv6 client-server exchange # tcpdump -i eth0 -vvv -n ip6 and port 547 3:52:22.644967 IP6 (hlim 60, next-header UDP (17) payload length: 106) 2001:db8:305:10::2.dhcpv6-server > 2001:db8:1000::9.dhcpv6-server: [udp sum ok] dhcp6 relay-fwd (linkaddr=2001:db8:221:5::1 peeraddr=fe80::16:3eff:fe01:b3a1
    [Show full text]
  • Basic Attacks and Mitigation Strategies
    Basic Attacks and Mitigation Strategies Christopher Werny <[email protected]> www.ernw.de Who am I ¬ Network geek, working as security researcher for ¬ Germany based ERNW GmbH Independent Deep technical knowledge Structured (assessment) approach Business reasonable recommendations We understand corporate ¬ Blog: www.insinuator.net ¬ Conference: www.troopers.de #2 www.ernw.de Agenda ¬ Refresher about Link-Layer Behavior of IPv6 ¬ Basic IPv6 Security Assumptions ¬ Attacks inside a Layer 2 Domain ¬ Mitigation Strategies ¬ Attacks from Outside ¬ Mitigation Strategies ¬ Conclusion www.ernw.de ICMPv6 ¬ ICMPv6 is the new version of ICMP. It was first specified in RFC 2462, latest in RFC 4443. ¬ ICMPv6 includes “traditional" ICMP functions, functionalities of IGMP (RFC 1112), IGMPv2 (RFC 2236) and extensions of the type "Multicast Listener Discovery” (MLD) for IPv6. ¬ Additionally ICMPv6 includes the Neighbor Discovery Protocol (RFC 2461, updated by RFC 4861). ¬ ICMPv6 is an integral part of every IPv6 implementation; every IPv6 stack must include ICMPv6. ¬ ICMPv6 has the next-header value 58. www.ernw.de Overall ICMPv6 Header Format 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Code | Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Message Body + | | ¬ Type: specifies the type of the message and also describes the format of the message. ¬ Code: Using this field, whose interpretation depends on the type, other
    [Show full text]
  • Data-Over-Cable Service Interface Specifications Ipv4 and Ipv6
    Data-Over-Cable Service Interface Specifications IPv4 and IPv6 eRouter Specification CM-SP-eRouter-I18-160317 ISSUED Notice This DOCSIS® specification is the result of a cooperative effort undertaken at the direction of Cable Television Laboratories, Inc. for the benefit of the cable industry and its customers. You may download, copy, distribute, and reference the documents herein only for the purpose of developing products or services in accordance with such documents, and educational use. Except as granted by CableLabs® in a separate written license agreement, no license is granted to modify the documents herein (except via the Engineering Change process), or to use, copy, modify or distribute the documents for any other purpose. This document may contain references to other documents not owned or controlled by CableLabs. Use and understanding of this document may require access to such other documents. Designing, manufacturing, distributing, using, selling, or servicing products, or providing services, based on this document may require intellectual property licenses from third parties for technology referenced in this document. To the extent this document contains or refers to documents of third-parties, you agree to abide by the terms of any licenses associated with such third party documents, including open source licenses, if any. Cable Television Laboratories, Inc., 2006-2016 CM-SP-eRouter-I18-160317 Data-Over-Cable Service Interface Specifications DISCLAIMER This document is furnished on an "AS IS" basis and neither CableLabs nor its members provides any representation or warranty, express or implied, regarding the accuracy, completeness, noninfringement, or fitness for a particular purpose of this document, or any document referenced herein.
    [Show full text]
  • Privacy and Security of DHCP Unique Identifiers
    International Journal for Information Security Research (IJISR), Volume 2, Issue 2, June 2012 Privacy and Security of DHCP Unique Identifiers Stephen Groat1,2 Matthew Dunlop1,2 Randy Marchany1 Joseph Tront2 Information Technology Security Office and Lab1 Bradley Department of Electrical and Computer Engineering2 Virginia Polytechnic Institute and State University (Virginia Tech), Blacksburg, VA 24061, USA Abstract As protection against the current privacy weaknesses To make the transition from IPv4 to IPv6 easier, of StateLess Address AutoConfiguration (SLAAC) in the many network administrators are using StateLess Address Internet Protocol version 6 (IPv6), network administrat- AutoConfiguration (SLAAC) to configure addresses on ors may choose to deploy the new Dynamic Host their networks. SLAAC eases the administrative burden of Configuration Protocol for IPv6 (DHCPv6). Similar to managing the more than 1.8·1019 possible nodes on a the Dynamic Host Configuration Protocol (DHCP) for the single subnet. SLAAC allows for nodes to configure the Internet Protocol version 4 (IPv4), DHCPv6 uses a client- interface identifier (IID), or last 64 bits, of their address server model to manage addresses in networks, providing independently. While this method eases the burden on stateful address assignment. While DHCPv6 can be network administrators, the static configuration used by configured to assign randomly distributed addresses to many common IPv6 network implementations threatens clients, the DHCP Unique Identifier (DUID) was the privacy of users [6]. designed to identify uniquely identify clients to servers The static IID used in SLAAC is globally available and remains static to clients as they move between and exposes a host to geotemporal tracking and traffic different subnets and networks.
    [Show full text]