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

mohamed.boucadair@orange.com Wed, 25 May 2022 06:14 UTC

Return-Path: <mohamed.boucadair@orange.com>
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 C1CA4C5670BB for <v6ops@ietfa.amsl.com>; Tue, 24 May 2022 23:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.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 09X6GXl7R5YO for <v6ops@ietfa.amsl.com>; Tue, 24 May 2022 23:14:34 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (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 8ED19C3D154A for <v6ops@ietf.org>; Tue, 24 May 2022 23:14:34 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr25.francetelecom.fr (ESMTP service) with ESMTPS id 4L7LPh364pzCrNG; Wed, 25 May 2022 08:14:32 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1653459272; bh=CohHKW0m7lN9/9pUAP3MTJLLTA/TkXIg28/Mqf/4zCw=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=ajc0NY66J1Sc4AW1/0ig137D52hCpET/w9o+AkNEBci+Nsmqq9i7GIxlt7PienK+K Lb/M1nOtMcAGI61ePCdegGT0IWvvgrCkU+bOnzaE3t+wT6+PxMDNCaZrsXJyXcr8Lj xSoPdr7fQynEjhEfkvE7p+2Qhg0Dt7ik215yYU+KOcjnx/W6AH2tPLypXyiB603noX VqRaoAN2WPqqXc7QBNv9GG229d3oJQENm+riCmq+4NZLXx8fjI0aVdgS/1MSQpxFc+ dwpvGtdIcXMEB+6N/295RIRcAehqYZF68DBu8Lnek4A5unGqAT3Rb4ea5B1rdexklt dalFaE93Y7w5g==
From: mohamed.boucadair@orange.com
To: Tomoyuki Sahara <tsahara=40iij.ad.jp@dmarc.ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
CC: RFC Errata System <rfc-editor@rfc-editor.org>, "jhw@apple.com" <jhw@apple.com>
Thread-Topic: [v6ops] [Editorial Errata Reported] RFC6092 (6979)
Thread-Index: AQHYb44Mpv7j2HHUykW30aj9wOsns60vF+Mg
Content-Class:
Date: Wed, 25 May 2022 06:14:31 +0000
Message-ID: <30251_1653459272_628DC948_30251_59_1_2ab6962903ae4970a41817d843dea049@orange.com>
References: <20220524053348.4CC18F5D82@rfcpa.amsl.com> <31207_1653371685_628C7325_31207_489_1_6754b7b25e294d88845685d9b98b2943@orange.com> <6F17B4FE-677B-408A-B3BF-4F0C8BA0E9F7@iij.ad.jp>
In-Reply-To: <6F17B4FE-677B-408A-B3BF-4F0C8BA0E9F7@iij.ad.jp>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-05-25T05:51:44Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=86a1f599-6e80-4c1e-a98f-d20df80b3a30; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.26.52]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Kh2HLk_SSHXeGX2KS1vw88YHxAs>
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: Wed, 25 May 2022 06:14:38 -0000

Hi Tomoyuki,

The excerpt you provided below (and its counterpart in 3415, Section 17) explains exactly why the intent of the OLD text is clear enough. 

Cheers,
Med

> -----Message d'origine-----
> De : v6ops <v6ops-bounces@ietf.org> De la part de Tomoyuki Sahara
> Envoyé : mardi 24 mai 2022 18:48
> À : v6ops@ietf.org
> Cc : RFC Errata System <rfc-editor@rfc-editor.org>; jhw@apple.com
> Objet : Re: [v6ops] [Editorial Errata Reported] RFC6092 (6979)
> 
> 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
> 
> 
> 
> _______________________________________________
> 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.