Re: [RTG-DIR] RtgDir review: draft-ietf-opsawg-l3sm-l3nm-10

mohamed.boucadair@orange.com Fri, 03 September 2021 05:27 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30BF63A13A5; Thu, 2 Sep 2021 22:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-JYiauRKyiu; Thu, 2 Sep 2021 22:27:20 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2670D3A139E; Thu, 2 Sep 2021 22:27:17 -0700 (PDT)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) (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 opfedar25.francetelecom.fr (ESMTP service) with ESMTPS id 4H15ry6b5yz8v5n; Fri, 3 Sep 2021 07:27:14 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1630646834; bh=4LJv5peu+4NaCP9In3ExCRPaPB2/V8+VX8ukhHFntKY=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=LWvdcdQSdoMobD3BXLKfmu/moZIr93Eg+g4Vli0WDB0HDqEp58tuIfVhwReMBKbZM ckbJh7C4tsi++rIvm3Eb+9W7b9ELh0IqDBvs36/YWXXUxwrkmz0d4k+b5/I5dbYWF0 BjeJ4kfFaTSS+S9HoxNiMDKAn0ggmzEyHZCrtqhe6ch9fMuMafkQ49JOLGaAgf2v2X dRjiiOM9PbtCII30t1qyuTwKqGn5QcqpporRd1DBp2LmcI5hDR4YvEkWrUI6wNxk/F uh3LfixA49kiPGJBZgCJCGQCQR31EiufwVNa6uWv/N2805IYbHziRp81Rp56pmwz4f GAF9TR97JZZiw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar07.francetelecom.fr (ESMTP service) with ESMTPS id 4H15ry5GcLz5vN8; Fri, 3 Sep 2021 07:27:14 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: "Andrew G. Malis" <agmalis@gmail.com>, "<rtg-ads@ietf.org>" <rtg-ads@ietf.org>
CC: Routing Directorate <rtg-dir@ietf.org>, "draft-ietf-opsawg-l3sm-l3nm.all@ietf.org" <draft-ietf-opsawg-l3sm-l3nm.all@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: RtgDir review: draft-ietf-opsawg-l3sm-l3nm-10
Thread-Index: AQHXfY0PjRQbcDLA8Um+Y4ZZr/4DCKuSDKBw
Date: Fri, 03 Sep 2021 05:27:13 +0000
Message-ID: <12223_1630646834_6131B232_12223_46_1_787AE7BB302AE849A7480A190F8B9330353E838D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <CAA=duU2UZWo+R2=w-hLyHdY7-ob1qBv4BugD5_A++83B+5i5zA@mail.gmail.com>
In-Reply-To: <CAA=duU2UZWo+R2=w-hLyHdY7-ob1qBv4BugD5_A++83B+5i5zA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B9330353E838DOPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/fveLErmLOPt1SUraT8fhBPrgHsQ>
Subject: Re: [RTG-DIR] RtgDir review: draft-ietf-opsawg-l3sm-l3nm-10
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Sep 2021 05:27:27 -0000

Hi Andy,

Many thanks for the review. Much appreciated.

The review will be acked in the next iteration as you can see in the diff: https://tinyurl.com/l3nm-latest

Cheers,
Med

De : Andrew G. Malis [mailto:agmalis@gmail.com]
Envoyé : mardi 20 juillet 2021 19:31
À : <rtg-ads@ietf.org> <rtg-ads@ietf.org>
Cc : Routing Directorate <rtg-dir@ietf.org>; draft-ietf-opsawg-l3sm-l3nm.all@ietf.org; opsawg@ietf.org
Objet : RtgDir review: draft-ietf-opsawg-l3sm-l3nm-10

Hello,

I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft.

Document: draft-ietf-opsawg-l3sm-l3nm-10
Reviewer: Andy Malis
Review Date: 2021-07-20
IETF LC End Date: 2021-08-06
Intended Status: Proposed Standard

Summary:

No issues found. This document is ready for publication.

Comments:

This draft has been through 11 revisions and has been twice reviewed by the Yang Doctors. All of its normative references save one have already been published, and the one draft normative reference is also in IETF Last Call. In addition, the very useful Appendix B shows that there are at least four publicly-announced implementations in various stages of progress. This all indicates the maturity of this draft as it enters IETF Last Call.

I found the commentary and model overview easy to read, and if I were writing an implementation, I would certainly appreciate the provisioning examples in Appendix A.

I also appreciated the comparison to RFC 8299.

Although I'm not a SECDIR reviewer, I found the Security Considerations section to be substantive.

To conclude, I consider this draft ready for publication.

Regards,
Andy


_________________________________________________________________________________________________________________________

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.