1 / 9

Enhancing IPv6 Address Tracking Through Auto-Configured DHCP Solutions

This document proposes a solution for effectively conveying SLAAC or statically assigned IPv6 addresses to backend systems, addressing key use cases such as IP address logging, tracking, and compliance while minimizing host changes, especially in BYOD environments. The solution utilizes enhanced DHCPv6 messaging to facilitate the transmission of IP:MAC bindings from the first hop router to the DHCP server. It proposes new DHCP options for client binding acknowledgments and emphasizes the importance of DHCP in storing IP-MAC binding information for efficient network management.

dora
Télécharger la présentation

Enhancing IPv6 Address Tracking Through Auto-Configured DHCP Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tracking Static/AutoConfiguredIPv6 Addresses draft-asati-dhc-ipv6-autoconfig-address-tracking IETF 86 Rajiv Asati Dan Wing

  2. Agenda Motivation Solution Next step

  3. Motivation • Need a way to convey SLAAC (or Static) assigned IPv6 addresses to the backend for various Use-Cases: • IP address Logging • IP address Tracking • Compliance • Avoid host changes/dependency (note BYOD)

  4. Solution DHCP Server Client_Binding Message First Hop Router Host Devices • First Hop Router conveys the “Neighbor Cache” entries to the backend using DHCPv6 • New DHCPv6 messages and new DHCP option defined • Add an IP:MAC binding entry

  5. Solution • Host Behavior • No changes required. • Router Behavior • Uses the DHCP message to send one or more IP:MAC bindings (from Neighbor cache) to the DHCP server • Server Behavior • Receives/Stores the IP:MAC bindings

  6. Solution – DHCP Message & Option Message +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RECORD-CLIENTBINDING-ACK| transaction-id | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | : Client-Binding-Ack-options : | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Option +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | OPTION_CLIENT_BINDING | option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | : Client Identifier (variable) : : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Lifetime (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | : IPv6 Addresses (n x 16 octets) : | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  7. Next Steps • Request additional WG review & feedback • Already had some discussion on the mailing list • Already had good interest off-list • Welcome Contribution/Participation • Solicit usefulness/WG Adoption

  8. Solution – Why DHCP? If DHCP is used for address assignment, then DHCP server already records the IP:MAC binding per host DHCP server has been the de facto placeholder for storing the IP-MAC binding information

More Related