Re: [v6ops] [Editorial Errata Reported] RFC6092 (6979)

Tomoyuki Sahara <tsahara@iij.ad.jp> Tue, 24 May 2022 16:48 UTC

Return-Path: <tsahara@iij.ad.jp>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD26C1D3C56; Tue, 24 May 2022 09:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iij.ad.jp
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 epcsTy-4mjwQ; Tue, 24 May 2022 09:48:17 -0700 (PDT)
Received: from omgo.iij.ad.jp (mo1801.iij.ad.jp [202.32.225.115]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 3706FC1D3C55; Tue, 24 May 2022 09:48:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iij.ad.jp; h=Content-Type: Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding: Message-Id:References:To;i=tsahara@iij.ad.jp;s=omgo2;t=1653410892;x= 1654620492; bh=Pt59RYmnj8K4wC1fvvvIqNAiFBiNjv8B+2873MJBn6Y=; b=YvDhs+3W0+XTB7h4 Coxf0I0YtJ+sL2/eBWkxN40OlKIUG06NkTnjqctxqXQmCutDntCRm47Lx92bsn+1Z8OQLyqmuZVgs mt5Hq/SpsIL+9VDk5n9hRFM+dhtzNdqi196+jpvvAEPFwHrpkkk6Dc03nCuQdAeSDKwbwF9amonr+ N6o6y7RK6NKue9iEWLb/TEhaVWD7zYml6BLrkO/cuALktyhgVPKKyZZvgiUTHmrcrC0XFUjT0Iyst W59vhgH9A8XAdRcgptb5s+kiIn6JebunYGNW07QsAd0bPSrUpzsiTgW5vNycQ73oKc5EKd2CgZdWC SaQnrsaTmW1w6JX3tw==;
Received: by omgo.iij.ad.jp (of-mo1801) id 24OGmC61017207; Wed, 25 May 2022 01:48:12 +0900
X-ENVID: IIJ
X-Iguazu-Qid: C8Ibd2VQyx7QoIVpsu
X-Iguazu-QSIG: v=2; s=0; t=1653410892; q=C8Ibd2VQyx7QoIVpsv; m=PCYzMNuqvgrQTxl+i9FV4KO/Epg02XP0WxOWvsBbD1M=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Tomoyuki Sahara <tsahara@iij.ad.jp>
In-Reply-To: <31207_1653371685_628C7325_31207_489_1_6754b7b25e294d88845685d9b98b2943@orange.com>
Date: Wed, 25 May 2022 01:48:10 +0900
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, "jhw@apple.com" <jhw@apple.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F17B4FE-677B-408A-B3BF-4F0C8BA0E9F7@iij.ad.jp>
References: <20220524053348.4CC18F5D82@rfcpa.amsl.com> <31207_1653371685_628C7325_31207_489_1_6754b7b25e294d88845685d9b98b2943@orange.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/rWTmyFYazZUdepBObdPyhgzZpR8>
Subject: Re: [v6ops] [Editorial Errata Reported] RFC6092 (6979)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2022 16:48:21 -0000

Hi,

It is not very clear what types of messages must not be
processed.

DHCPv6 "server discovery" process is defined in Section 18
of RFC8415:

   ... The client does this by sending the Solicit message
   (see Section 18.2.1) to the All_DHCP_Relay_Agents_and_Servers
   multicast address and collecting Advertise messages from the servers
   that respond to the client's message; the client then selects a
   server from which it wants to obtain configuration information.  This
   process is referred to as server discovery.

Only two messages are used in this server discovery process.
The message that servers receive is Solicit.  So "DHCPv6
discovery packets" in REC-9 should be Solicit messages.


By the way, why only discovery packets must not be processed?
I think any DHCPv6 messages received on exterior interfaces
must not be processed by DHCPv6 server or relay agent in CPE.


Thanks,
Tomoyuki


> On May 24, 2022, at 14:54, mohamed.boucadair@orange.com wrote:
> 
> Hi all, 
> 
> The original text is correct. It does not refer to the name of the message, but to the descriptive process.
> 
> Cheers,
> Med
> 
>> -----Message d'origine-----
>> De : v6ops <v6ops-bounces@ietf.org> De la part de RFC Errata
>> System
>> Envoyé : mardi 24 mai 2022 07:34
>> À : rfc-editor@rfc-editor.org
>> Cc : v6ops@ietf.org; jhw@apple.com
>> Objet : [v6ops] [Editorial Errata Reported] RFC6092 (6979)
>> 
>> The following errata report has been submitted for RFC6092,
>> "Recommended Simple Security Capabilities in Customer Premises
>> Equipment (CPE) for Providing Residential IPv6 Internet Service".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid6979
>> 
>> --------------------------------------
>> Type: Editorial
>> Reported by: Tomoyuki Sahara <tsahara@iij.ad.jp>
>> 
>> Section: 3.1
>> 
>> Original Text
>> -------------
>>   REC-9: Inbound DHCPv6 discovery packets [RFC3315] received on
>>   exterior interfaces MUST NOT be processed by any integrated
>> DHCPv6
>>   server or relay agent.
>> 
>> 
>> Corrected Text
>> --------------
>>   REC-9: Inbound DHCPv6 Solicit messages [RFC3315] received on
>>   exterior interfaces MUST NOT be processed by any integrated
>> DHCPv6
>>   server or relay agent.
>> 
>> 
>> Notes
>> -----
>> "discovery" packet, more precisely DHCPDISCOVER message, is
>> defined in DHCPv4 but it is not defined in DHCPv6.
>> DHCPv6 clients send "Solicit" messages to discover DHCPv6 servers
>> or relay agents.
>> 
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary,
>> please use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party can log
>> in to change the status and edit the report, if necessary.
>> 
>> --------------------------------------
>> RFC6092 (draft-ietf-v6ops-cpe-simple-security-16)
>> --------------------------------------
>> Title               : Recommended Simple Security Capabilities in
>> Customer Premises Equipment (CPE) for Providing Residential IPv6
>> Internet Service
>> Publication Date    : January 2011
>> Author(s)           : J. Woodyatt, Ed.
>> Category            : INFORMATIONAL
>> Source              : IPv6 Operations
>> Area                : Operations and Management
>> Stream              : IETF
>> Verifying Party     : IESG
>> 
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> 
> _________________________________________________________________________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops