Re: [Idr] [RTG-DIR] Rtgdir early review of draft-ietf-idr-bgp-car-02

Ben Niven-Jenkins <ben@niven-jenkins.co.uk> Mon, 31 July 2023 20:15 UTC

Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD58C15152F; Mon, 31 Jul 2023 13:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.206
X-Spam-Level:
X-Spam-Status: No, score=-4.206 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 4nH2W52MrUUI; Mon, 31 Jul 2023 13:15:09 -0700 (PDT)
Received: from mx2.mythic-beasts.com (mx2.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18508C15198B; Mon, 31 Jul 2023 13:15:06 -0700 (PDT)
Received: by mailhub-hex-d.mythic-beasts.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <ben@niven-jenkins.co.uk>) id 1qQZIG-004Tk1-RC; Mon, 31 Jul 2023 21:15:05 +0100
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Message-Id: <3552AF3B-CFB3-4D34-9AC7-2FA3BCCD1607@niven-jenkins.co.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_AE1A4041-586D-416B-953A-1159C701DF72"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\))
Date: Mon, 31 Jul 2023 21:15:00 +0100
In-Reply-To: <169083336446.19263.6512979191896134032@ietfa.amsl.com>
Cc: rtg-dir@ietf.org, draft-ietf-idr-bgp-car.all@ietf.org, idr@ietf.org
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
References: <169083336446.19263.6512979191896134032@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3696.120.41.1.3)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/VFIgyFYmzi7kW7Yl6kmDT6W1kxQ>
Subject: Re: [Idr] [RTG-DIR] Rtgdir early review of draft-ietf-idr-bgp-car-02
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2023 20:15:10 -0000


> On 31 Jul 2023, at 20:56, Ben Niven-Jenkins via Datatracker <noreply@ietf.org> wrote:
> 
> Reviewer: Ben Niven-Jenkins
> Review result: Has Issues
> 
> Hello
> 
> I have been selected to do a routing directorate “early” review of this draft.
> https://datatracker.ietf.org/doc/draft-ietf-mpls-rfc3107bis/

Of course I meant https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-car/ <https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-car/> :-)

Ben

> 
> The routing directorate will, on request from the working group chair, perform
> an “early” review of a draft before it is submitted for publication to the
> IESG. The early review can be performed at any time during the draft’s lifetime
> as a working group document. The purpose of the early review depends on the
> stage that the document has reached.
> 
> For more information about the Routing Directorate, please see
> https://wiki.ietf.org/en/group/rtg/RtgDir
> 
> Document: draft-ietf-idr-bgp-car-02
> Reviewer: Ben Niven-Jenkins
> Review Date: 31 July 2023
> Intended Status: Experimental
> 
> Summary:
> I have some minor concerns about this document that I think should be resolved
> before it is submitted to the IESG.
> 
> Comments:
> The document provides lots of details in the main sections and examples in the
> appendices. I think that is generally ready to be published. The only
> suggestion I would have is to provide a short overview introducing BGP CAR and
> color aware routing before leaping into terminology and the details of the BGP
> CAR SAFI. Expanding the introduction section with an extra paragraph or two
> would be sufficient.
> 
> Thanks
> Ben
> 
> 
>