Re: [dhcwg] Murray Kucherawy's No Objection on draft-ietf-dhc-dhcpv6-yang-24: (with COMMENT) Fri, 17 December 2021 13:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E94F03A0FE0; Fri, 17 Dec 2021 05:26:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Status: No, score=-2.096 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dCUCK_fuhTNc; Fri, 17 Dec 2021 05:25:59 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2DEB93A0FDC; Fri, 17 Dec 2021 05:25:59 -0800 (PST)
Received: from (unknown [xx.xx.xx.70]) (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 (ESMTP service) with ESMTPS id 4JFqVr4Rcdz1yH1; Fri, 17 Dec 2021 14:25:56 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1639747556; bh=/8U+H6gUDiQ3Aw3VsUQLKXMT2dgu1lxq2xMgWOzjqTU=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=eYTapXZ8ay4TTfcnFoyhhhwjYWUMeW3l9vizGrCL0ODI7N5vvxfvQUNRPZY23gOQ7 utehEEp7Nt406XFCaZFgQZCy+PXbHnVXUx852jjfGWhRdJJ3itXTV88iitK/RTTjAj tpYR6bSTREqaFSrWxxAP010Myp3XqGWu1H8p7yM/n2xlMXVp+do4mDKgdSzOF4jL9k 1h5+8q5WIP+i8HFhKkwPQ4TvqC6VSrUD0/G/S7MiUth6aecoTaiV2/4cNypTOk06v+ 1V1615ZiCsEvVhbSeUetut/WLsluihAq7FJbkJ8/+MbdE94MDd8CA+lwzYw3Lxo5LK 2CydWSJn+1ufg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (ESMTP service) with ESMTPS id 4JFqVr3b5DzDq83; Fri, 17 Dec 2021 14:25:56 +0100 (CET)
To: Murray Kucherawy <>, "" <>
CC: "" <>, "" <>, The IESG <>
Thread-Topic: [dhcwg] Murray Kucherawy's No Objection on draft-ietf-dhc-dhcpv6-yang-24: (with COMMENT)
Thread-Index: AQHX8cxJuiOLWRrbdUuSARdrZ4AwGqw2qatw
Date: Fri, 17 Dec 2021 13:25:55 +0000
Message-ID: <27305_1639747556_61BC8FE4_27305_172_9_787AE7BB302AE849A7480A190F8B9330354673EA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2021-12-17T13:04:39Z; 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=4f21ec13-6349-498b-a23b-dc7bbcde9b26; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [dhcwg] Murray Kucherawy's No Objection on draft-ietf-dhc-dhcpv6-yang-24: (with COMMENT)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Dynamic Host Configuration <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 17 Dec 2021 13:26:07 -0000

Hi Murray,

RFC 3319 does not need to be listed as normative as it is cited in an example module. 

RFC 8987 is OK to be cited as informative given that it does only specify a requirement. It does not specify the inputs/outputs. That's consistent with rfc8407#section-3.9:

   If the reference statement identifies an informative reference that
   identifies a separate document, a corresponding informative reference
   to that document MAY appear in the Informative References section. 

BTW, the I-D has to cite 8987 in the core text. 


> -----Message d'origine-----
> De : dhcwg <> De la part de Murray Kucherawy via
> Datatracker
> Envoyé : mercredi 15 décembre 2021 16:56
> À : The IESG <>
> Cc :;;
> Objet : [dhcwg] Murray Kucherawy's No Objection on draft-ietf-dhc-dhcpv6-
> yang-24: (with COMMENT)
> Murray Kucherawy has entered the following ballot position for
> draft-ietf-dhc-dhcpv6-yang-24: No Objection
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> Please refer to
> for more information about how to handle DISCUSS and COMMENT positions.
> The document, along with other ballot positions, can be found here:
> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
> I suggest breaking Section 6 into two subsections, one for each batch of
> registry operations.
> A possibly ignorant question about YANG modules: Since RFCs 3319 and 8987
> are referenced from within the module itself, shouldn't they be normative
> references?
> _______________________________________________
> dhcwg mailing list


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.