1 / 8

WGLC Results for draft-ietf-mip6-hiopt-02.txt

WGLC Results for draft-ietf-mip6-hiopt-02.txt. HeeJin Jang Alper Yegin JinHyeock Choi Samsung AIT Kuntal Chowdhury Starent Networks. Contents. Changes Comments & Resolutions during WGLC Ongoing Issues. Changes.

lana-raymond
Download Presentation

WGLC Results for draft-ietf-mip6-hiopt-02.txt

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. WGLC Results for draft-ietf-mip6-hiopt-02.txt HeeJin Jang Alper Yegin JinHyeock Choi Samsung AIT Kuntal Chowdhury Starent Networks

  2. Contents • Changes • Comments & Resolutions during WGLC • Ongoing Issues

  3. Changes • Description related to DHCP (MIP6 Relay Agent option) was moved to hiopt draft from the bootstrapping-integrated draft. • We defined a sub-option in HN Information option and moved detailed fields into it for the consistency of the format with the MIP6 Relay Agent option. • New Id-type (2) is defined in HN Identifier option to indicate that MN has no preference for the requested target network.

  4. Comments & Resolutions (1/2) • MN should be able to request the target network which is not home network nor visited network. • We’ll extend the id-type 1 to support MSP which has trust roaming relationship with MN’s MSA as well as MSA (=Home MSP). • The retrieval of Multiple HA information should be supported. • It is allowed by using multiple sub-options in the HN Information option. • Additionally it will be mentioned that AAAH may return more than one HA for each of the MSPs in the bootstrapping-integrated draft. • How does the NAS/DHCP relay map a DHCP request from a specific MN to the cached HN information? • Mapping for a specific MN information in DHCP relay is not specific issue for hiopt draft but a generic issue with the RFC4014.

  5. Comments & Resolutions (2/2) • What is the conceptual data structure of the cache in the NAS/DHCP relay and any default value for caching? • It’s implementation specific details and leaves the specific value as a configuration option. • What should NAS/DHCP relay do if NAS cannot find valid HN information for MN in its cache? • In such case, the NAS/DHCP relays simply will not include the OPTION_MIP6-RELAY-Option in the Relay-Forward message. • The DHCP server will return HN Information option with the 0-length data if it does not have the corresponding information either.

  6. Ongoing Issues (1/2) • Issue #1: Support for the various types of the requested HA to specify HA service type. (0=MIPv6, 1=DS-MIPv6, 2=NEMO,...) • We will define new field for the HA service type in HN Identifier & Information options in next version. • Issue #2: How is the lifetime of HoA MN gets bootstrapped managed? Will it be refreshed by DHCP server? • HoA is assigned by stateless DHCP not by stateful DHCP and provided without lifetime.

  7. Ongoing Issues (2/2) • Issue #3: Setting both id-type to 0 (ASP) and the HN Identifier to the target MSP has no sense even for minimum transaction. If the Id-type is 0, the HN Identifier should be always 0 for clarity. • For this, we’ll revise the draft as follows • When the id-type is 0, HN Identifier is always set to 0. • When the id-type is 1, then HN Identifier is set to the target FQDN. • If MN wants to retrieve HN information from both ASP and target MSP with a single transaction, it should request with both of sub-options in a HN Identifier option.

  8. Any Questions?

More Related