[Sidrops] Opsdir telechat review of draft-ietf-sidrops-ov-egress-02

Linda Dunbar via Datatracker <noreply@ietf.org> Wed, 01 April 2020 19:36 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-sidrops-ov-egress.all@ietf.org, sidrops@ietf.org, last-call@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <158576979679.30652.11243360019367571918@ietfa.amsl.com>
Reply-To: Linda Dunbar <linda.dunbar@futurewei.com>
Date: Wed, 01 Apr 2020 12:36:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/BqLWWiAfC3jZ_29XHqgS3O4yG88>
Subject: [Sidrops] Opsdir telechat review of draft-ietf-sidrops-ov-egress-02

Reviewer: Linda Dunbar
Review result: Ready

I have reviewed this document as part of the Ops area directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the Ops area directors.
Document editors and WG chairs should treat these comments just like any other
last call comments.

I think the document is ready and precise.

Just one minor comment:
The document emphasizes the  importance of origin validation in eBGP egress
policies, explaining specifics of correct implementation. I just wish it adds
the examples described by Chris Morrow on the mailing list on the  use cases
that explain why the mechanism described in the document is necessary because
not everyone is as smart and knowledgeable as the authors.

My two cents.
Linda Dunbar

[Sidrops] Opsdir telechat review of draft-ietf-si… Linda Dunbar via Datatracker