1 / 6

IETF 88, Nov 2013 Authors: Shwetha Bhandari ( Cisco)

DHCPv4 and DHCPv6 Access-Network-Identifier Options ( draft -ietf- dhc-access-network-identifier- 01). IETF 88, Nov 2013 Authors: Shwetha Bhandari ( Cisco) Sri Gundavelli (Cisco) Jouni Korhonen (Broadcom) Mark Grayson (Cisco). Overview: Access N etwork Information(ANI).

cecily
Download Presentation

IETF 88, Nov 2013 Authors: Shwetha Bhandari ( Cisco)

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. DHCPv4 and DHCPv6 Access-Network-Identifier Options(draft-ietf-dhc-access-network-identifier-01) IETF 88, Nov 2013 Authors: Shwetha Bhandari (Cisco) Sri Gundavelli(Cisco) JouniKorhonen(Broadcom) Mark Grayson (Cisco)

  2. Overview: Access Network Information(ANI) • Primary Access Network Information • Access-Network-Type – 802.11, Ethernet etc. • Network-Identifier – e.g. SSID, Access Point name, BSSID/AP MAC address • Operator-Identifier – e.g. the realm of the access network operator using domain name encoding.

  3. Access Network Information in DHCP • The draft defines new option in DHCPv4, to be inserted by: • Client : access network information option with sub-options • Relay : Option 82 Sub options to carry - Access-Network-Type, Network-Identifier, Operator-Identifier • New options in DHCPv6 • To carry access network information • Can be added either in Relay-Forward or Client initiated messages by Relay and Clients respectively

  4. Motivation/Use Case • In many deployments there is a need to provide differentiated services based on the access network attachment. For example: • The service treatment may be different when a node is attached to a access network owned by the home operator than when owned by a roaming partner. • The service treatment can also be different based on the configured SSID in case of IEEE 802.11 based access networks. • Shared access networks i.e. radio access & access points owned and possibly operated by other entity than the owner of a access gateway . This draft defines DHCP options to relay this information from access towards the gateway and server.

  5. Changes from 00-01 • Added DHCPv6 option and DHCPv4 sub-option to carry Access Point’s BSSID

  6. Next Steps.. • Request review from workgroup • Prepare for workgroup last call?

More Related