[lisp] Opsdir last call review of draft-ietf-lisp-rfc6830bis-16

Scott Bradner <sob@sobco.com> Tue, 28 August 2018 12:54 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Scott Bradner <sob@sobco.com>
To: ops-dir@ietf.org
Cc: draft-ietf-lisp-rfc6830bis.all@ietf.org, ietf@ietf.org, lisp@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153546084779.23731.3772960451880909496@ietfa.amsl.com>
Date: Tue, 28 Aug 2018 05:54:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/YZmMoT8dQH5k9-vv2bQb0ifzRoo>
Subject: [lisp] Opsdir last call review of draft-ietf-lisp-rfc6830bis-16

Reviewer: Scott Bradner
Review result: Ready

I performed an OPS-DIR review of The Locator/ID Separation Protocol (LISP)
(draft-ietf-lisp-rfc6830bis-16) This ID is the result of a bifurcation of RFC
6830 as such review of the basic technology is OBE. (i.e. RFC 6830 was
published years ago – any deep technology review should have been done then.)
The ID does make some changes to the technology described in RFC 6830 but the
changes do not present any operations related issues that I can see.

The version I was asked to review did not have a “Changes since RFC 6830”
section (as all RFCs that update or obsolete other RFCs should have) but that
has been fixed so I have no additional issues.

[lisp] Opsdir last call review of draft-ietf-lisp… Scott Bradner
Re: [lisp] Opsdir last call review of draft-ietf-… Dino Farinacci
Re: [lisp] [OPS-DIR] Opsdir last call review of d… Warren Kumari