Re: [dhcwg] New Draft for Mobile information

Bernie Volz <bevolz@gmail.com> Fri, 25 August 2023 16:41 UTC

Return-Path: <bevolz@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DDFCC1522AB for <dhcwg@ietfa.amsl.com>; Fri, 25 Aug 2023 09:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.213
X-Spam-Level:
X-Spam-Status: No, score=-1.213 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Vis425JgxIE for <dhcwg@ietfa.amsl.com>; Fri, 25 Aug 2023 09:41:50 -0700 (PDT)
Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A375EC1519A9 for <dhcwg@ietf.org>; Fri, 25 Aug 2023 09:41:50 -0700 (PDT)
Received: by mail-qv1-xf2e.google.com with SMTP id 6a1803df08f44-64a0176b1easo6377426d6.3 for <dhcwg@ietf.org>; Fri, 25 Aug 2023 09:41:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692981709; x=1693586509; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=NQuEJh4YMOYq1XWmF0ukpPsPSdhPyTulLEh1dXMbQRg=; b=sfbi+FSgKyGQ5GpRf42tFChynvkBljMUW4qHESijD+JT8s4CK6FzihhG5Z6zZoBw8a 4ZxoyiZ6sCFhYqyZsdKVU7p1Jlss141qwk+opcqBRC902d6cHVKGeCnWy0lfZAwjnPwD eQIrTinuzciA2kGhAaDnSekmW5rgf4hCresQJ8eCNNbw2nFJw3jWhowUkwYgVWHQtEXX jXsIRVuYiGCwQ9Xuf5nua/Sf+x91QpEmodAErfMym0RwFJLSMdb/yk8HpgLeJ1NU7/M/ XENL75Rl2QNY2JuraPxxpJM5sO1hWnxFbhJBTV9/D/jalmuNgHfROVhS349OR+SXjIAu z7CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692981709; x=1693586509; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=NQuEJh4YMOYq1XWmF0ukpPsPSdhPyTulLEh1dXMbQRg=; b=iEPxSIVTdXJWA/f+Gwe8V+bqu8mvR9xvt66BKMxffothrCcLNERwkuGGI8zYbTTPav wt4XK9XinvB31dQrMqpK5v99g3+G7uSnCwILOnX67GBNSyQ1TKvrX3GG4Mdr+qOQqGGE D+w5JL12a83YiplgzExzoVGS2rwcAUyD3Putmh358FJ/3cjWr2fUoA5MYJvkyhc8WSFu nwgTxd44kJPRx4jpOC2LTyLcBCmR7SArU480eH5cgwNg9SYX/Knabrh7SLrnB2Yd0yGf QgpW9gBkqG/kX4SZQ4u/wpM7iL2/46eQxxVm71HrFvFF3VSNRJUXssZ2+QC8cYrj7eE7 Ia0w==
X-Gm-Message-State: AOJu0YwTZAzkyDfdCeYp5QlLLXDXKidiyIaaMUURVg9k6sW+nB2xWPUn KHvkFBJkghQYqfdAKg8219DB1BNKUA==
X-Google-Smtp-Source: AGHT+IGEG0XyYjJu7eTR9q9yBtRon/HakcVfnj3tjzYaVhNfK+KDANyz+BUOdtbCJrrvN8M7/pA6SA==
X-Received: by 2002:a0c:b3dc:0:b0:63f:7d58:669c with SMTP id b28-20020a0cb3dc000000b0063f7d58669cmr1889675qvf.61.1692981709294; Fri, 25 Aug 2023 09:41:49 -0700 (PDT)
Received: from smtpclient.apple (d-24-233-121-124.nh.cpe.atlanticbb.net. [24.233.121.124]) by smtp.gmail.com with ESMTPSA id i13-20020a0cf48d000000b0063cf9478fddsm661479qvm.128.2023.08.25.09.41.48 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Aug 2023 09:41:48 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-1A726050-B92B-4C8C-9889-7DBD6B6ED06D"
Content-Transfer-Encoding: 7bit
From: Bernie Volz <bevolz@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Fri, 25 Aug 2023 12:41:37 -0400
Message-Id: <1B1BADF2-9EDC-42EA-B316-D88AF0880BAC@gmail.com>
References: <23C92011-1529-402E-ADCC-5DE1EBF9E99F@comcast.com>
Cc: dhcwg@ietf.org, "Muthusamy, Saravanan" <saravanan_muthusamy@comcast.com>
In-Reply-To: <23C92011-1529-402E-ADCC-5DE1EBF9E99F@comcast.com>
To: "Lee, Yiu" <yiu_lee=40comcast.com@dmarc.ietf.org>
X-Mailer: iPad Mail (20G75)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/2jxCYxMsOoU-E_ZL93-KsTN2MMA>
Subject: Re: [dhcwg] New Draft for Mobile information
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Aug 2023 16:41:54 -0000

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$" title="https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-muthusamy-dhc-mobile-sub-info-00.txt__;!!CQl3mcHX2A!De4IOekuFyc81zwWUz6pUGPsVy2Uu3BGwxuYRMDLsyzm-wu8T6Qt5ZxVDHNhlgln06BePNYKDRh-QIvYG-VEUr3chg$" rel="nofollow">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$" title="https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-muthusamy-dhc-mobile-sub-info/__;!!CQl3mcHX2A!De4IOekuFyc81zwWUz6pUGPsVy2Uu3BGwxuYRMDLsyzm-wu8T6Qt5ZxVDHNhlgln06BePNYKDRh-QIvYG-UQzIZ2qw$" rel="nofollow">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$" title="https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-muthusamy-dhc-mobile-sub-info__;!!CQl3mcHX2A!De4IOekuFyc81zwWUz6pUGPsVy2Uu3BGwxuYRMDLsyzm-wu8T6Qt5ZxVDHNhlgln06BePNYKDRh-QIvYG-Vpjl-yEQ$" rel="nofollow">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