[Lsr] Secdir last call review of draft-ietf-lsr-ospf-prefix-originator-09

Watson Ladd via Datatracker <noreply@ietf.org> Sat, 20 March 2021 05:32 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Watson Ladd via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-lsr-ospf-prefix-originator.all@ietf.org, last-call@ietf.org, lsr@ietf.org, watsonbladd@gmail.com
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161621836770.16465.11678374336820664293@ietfa.amsl.com>
Reply-To: Watson Ladd <watsonbladd@gmail.com>
Date: Fri, 19 Mar 2021 22:32:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/eoJKJ2fy189coEorvm85tjymMw0>
Subject: [Lsr] Secdir last call review of draft-ietf-lsr-ospf-prefix-originator-09

Reviewer: Watson Ladd
Review result: Ready

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

The summary of the review is Ready.

This document describes a small extension to OSPF to include 
information of the originating router for a prefix, which otherwise
would be lost as the prefix proceeds to be readvertised. This information
is quite useful when determining what is going on under trying circumstances.

Sincerely,
Watson Ladd

[Lsr] Secdir last call review of draft-ietf-lsr-o… Watson Ladd via Datatracker
Re: [Lsr] Secdir last call review of draft-ietf-l… Ketan Talaulikar (ketant)