1 / 8

Dynamic Allocation of Shared IPv4 Addresses - IETF 90 Overview

This document outlines the management of shared IPv4 address leases for more efficient allocation using DHCPv4 in conjunction with DHCPv6. It introduces the use of OPTION_V4_PORTPARAMS, enhancing client/server interactions and behaviors. Key improvements focus on address sharing mechanisms and the selection logic using PSID for allocations. It emphasizes compatibility with existing operations and sets clear behaviors for both clients and servers, including the MUST renew and release processes. This draft aims to facilitate the better use of valuable IPv4 addresses.

sukey
Download Presentation

Dynamic Allocation of Shared IPv4 Addresses - IETF 90 Overview

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. IETF 90 Dynamic Allocation of Shared IPv4 Addressesdraft-ietf-dhc-dynamic-shared-v4allocation-01 Q. Sun, Y. Cui, I. Farrer, Y. Lee, Q. Sun, M. Boucadair IETF 90, Toronto

  2. IETF 90 Overview • Dynamic management of shared IPv4 address leases • Through the combination of IPv4 address and OPTION_V4_PORTPARAMS • Relevant for use with DHCPv4 over DHCPv6 • Enables more efficient use of scarce IPv4 addresses • Changes since adopted • NOT an update to RFC2131 • Improvement of client/server behaviors • Compatibility with normal client/server

  3. IETF 90 Further specifics on Behaviors • Client: • MUST renew and release with theoption • When receiving multiple replies, selects the one it prefers • Server: • MUST implement a mechanism for address sharing through address and port-leasing • Specify the logic to select an address with PSID for allocation, similar to that of address selection in RFC2131 • Remove the statement that PSID is related to client state determination • Reserves WKPs from allocation to clients

  4. IETF 90 Client/Sever Logic for the option

  5. IETF 90 Next step • Request WG’s review • WGLC?

  6. IETF 90 Server-Client Interactions • Include OPTION_PORTPARAMSV4, Client-ID in related DHCPv4 messages • Transported within DHCPv4-query/DHCPv4-response messages over an IPv6 network

  7. IETF 90 DHCPv4 Port Parameters Option • OPTION_PORTPARAMSV4 format • Similar format to OPTION_S46_PORTPARAMS in draft-ietf-softwire-map-dhcp-06

  8. IETF 90 Logic for Interworking with non-shared DHCPv4oDHCPv6 Servers? • A client’s DISCOVER doesn’t contain OPTION_V4_PORTPARAMS, and times out. Either: • Available full IPv4 addresses have run out, or • All servers ONLY support address sharing • Client then requests an IPv4 address withOPTION_V4_PORTPARAMS in PRL Is this behavior necessary?

More Related