[lisp] Opsdir last call review of draft-ietf-lisp-pubsub-10

Al Morton via Datatracker <noreply@ietf.org> Sun, 22 January 2023 15:02 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Al Morton via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-lisp-pubsub.all@ietf.org, last-call@ietf.org, lisp@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <167439973284.4231.10140476710314446378@ietfa.amsl.com>
Reply-To: Al Morton <acmorton@att.com>
Date: Sun, 22 Jan 2023 07:02:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/Eqvox_0STsMFO8izPrTINvIMP_E>
Subject: [lisp] Opsdir last call review of draft-ietf-lisp-pubsub-10

Reviewer: Al Morton
Review result: Ready

This is the OPS-DIR review of draft-ietf-lisp-pubsub, version 10.

The memo describes an extension to the request/reply based Locator/ID
Separation Protocol (LISP) control plane. "... a Publish/Subscribe (PubSub)
extension in which the Mapping System can notify ITRs/RTRs/PITRs about mapping
changes." This extension allows faster mapping changes that can be managed
within the Mapping system itself.

Conditions for deployment and the extension itself are clearly described. The
memo contains a section on current deployment experiences: these are all
positive, especially in cases where performance is improved in scenarios
involving mobility. It seems likely that operational issues, if any, would have
been revealed in the deployments (which are on-going for some time).

I noted that the LISP RFC has been updated very recently:
https://www.rfc-editor.org/rfc/rfc9301.html; this indicates appreciable
operational experience with the protocol and continued use/interest.

Nits:
...PubSub offers faster converge due to...
suggest  s/converge/convergence/

regards,
Al

[lisp] Opsdir last call review of draft-ietf-lisp… Al Morton via Datatracker
Re: [lisp] Opsdir last call review of draft-ietf-… mohamed.boucadair