Re: [dhcwg] New Draft for Mobile information

To respond your last comment, we do not propose to extend any protocol. Our primary objective is to allow the network to signal the client via simple mechanism(s) with a URL to securely exchange mobile sub info IF the client agrees to do so.

From: dhcwg <dhcwg-bounces@ietf.org> on behalf of Bernie Volz <bevolz@gmail.com>
Date: Friday, August 25, 2023 at 12:41
To: "Lee, Yiu" <yiu_lee=40comcast.com@dmarc.ietf.org>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Muthusamy, Saravanan" <saravanan_muthusamy@comcast.com>
Subject: Re: [dhcwg] New Draft for Mobile information

A few comments (with wg chair hat off).

Typos/issues in draft:

For dhcpv4 and v6 option, you forgot to change option name:

option-code:  The Captive-Portal DHCPv6 Option (TBD) (two octet).

And, the following paragraph is not needed:

   As the maximum length of the URI that can be carried in IPv4 DHCP is

   255 bytes, URIs longer than this SHOULD NOT be provisioned via IPv6

   RA options.

See RFC 3396 as that supports options with data greater than 255 bytes. Your draft should reference it for v4 in section 2.3, and then paragraph can be removed. As well as text in 2.2.

Section 2.1 could mention Option Request Option for dhcpv6?

Further action on thr draft:

As this draft follows RFC7227 and these are “simple” data options, the work can be done by another WG more aligned with the underlying technology (if there is one). The DHC wg charter has:

Definitions of new DHCP options that are delivered using standard
mechanisms with documented semantics are not considered a protocol
extension and thus are generally outside of scope for the DHC WG. Such
options should be defined within their respective WGs or sponsored by an
appropriate AD and reviewed by DHCP experts in the Internet Area
Directorate.

- Bernie Volz

On Aug 25, 2023, at 11:35 AM, Lee, Yiu <yiu_lee=40comcast.com@dmarc.ietf.org> wrote:
Dear DHC WG,

We submitted a draft to define a new option to exchange the mobile subscription information between client and network over DHCP and RA. The use case is to provide consistent network services when a mobile client switch from mobile network to a private network (usually home network) that uses simple PSK (e.g., WPA3) and doesn’t support EAP-AKA. Comments are welcome.

A new version of Internet-Draft draft-muthusamy-dhc-mobile-sub-info-00.txt has
been successfully submitted by Yiu L. Lee and posted to the
IETF repository.

Name:     draft-muthusamy-dhc-mobile-sub-info
Revision: 00
Title:    Mobile Subscription Info in DHCP and Router Advertisement
Date:     2023-08-25
Group:    Individual Submission
Pages:    7
URL:      https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-muthusamy-dhc-mobile-sub-info-00.txt__;!!CQl3mcHX2A!De4IOekuFyc81zwWUz6pUGPsVy2Uu3BGwxuYRMDLsyzm-wu8T6Qt5ZxVDHNhlgln06BePNYKDRh-QIvYG-VEUr3chg$<https://urldefense.com/v3/__https:/www.ietf.org/archive/id/draft-muthusamy-dhc-mobile-sub-info-00.txt__;!!CQl3mcHX2A!De4IOekuFyc81zwWUz6pUGPsVy2Uu3BGwxuYRMDLsyzm-wu8T6Qt5ZxVDHNhlgln06BePNYKDRh-QIvYG-VEUr3chg$>
Status:   https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-muthusamy-dhc-mobile-sub-info/__;!!CQl3mcHX2A!De4IOekuFyc81zwWUz6pUGPsVy2Uu3BGwxuYRMDLsyzm-wu8T6Qt5ZxVDHNhlgln06BePNYKDRh-QIvYG-UQzIZ2qw$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-muthusamy-dhc-mobile-sub-info/__;!!CQl3mcHX2A!De4IOekuFyc81zwWUz6pUGPsVy2Uu3BGwxuYRMDLsyzm-wu8T6Qt5ZxVDHNhlgln06BePNYKDRh-QIvYG-UQzIZ2qw$>
HTMLized: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-muthusamy-dhc-mobile-sub-info__;!!CQl3mcHX2A!De4IOekuFyc81zwWUz6pUGPsVy2Uu3BGwxuYRMDLsyzm-wu8T6Qt5ZxVDHNhlgln06BePNYKDRh-QIvYG-Vpjl-yEQ$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-muthusamy-dhc-mobile-sub-info__;!!CQl3mcHX2A!De4IOekuFyc81zwWUz6pUGPsVy2Uu3BGwxuYRMDLsyzm-wu8T6Qt5ZxVDHNhlgln06BePNYKDRh-QIvYG-Vpjl-yEQ$>

Thanks,
Yiu and Saravanan

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/dhcwg__;!!CQl3mcHX2A!AlMXXIrI51D-NeBwXYFPb6FB9FRY-Ck6Q1C-QLGFaaNJTvaViNMkXW1h8o8vZEuD4GPmKC7MwuiQdA$>