[Sidrops] Rtgdir last call review of draft-ietf-sidrops-lta-use-cases-05

Stewart Bryant via Datatracker <noreply@ietf.org> Thu, 18 April 2019 21:48 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
Cc: sidrops@ietf.org, ietf@ietf.org, draft-ietf-sidrops-lta-use-cases.all@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <155562409732.25526.1571500373372550686@ietfa.amsl.com>
Date: Thu, 18 Apr 2019 14:48:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/iuV7FBiic6ps9ca47Vvj6DGQRzU>
Subject: [Sidrops] Rtgdir last call review of draft-ietf-sidrops-lta-use-cases-05

Reviewer: Stewart Bryant
Review result: Has Nits

This is a well written document.

There are a couple of nits that need addressing but otherwise it is ready to publish.

============

6.  Security Considerations

   Though the above use cases are all constrained to local contexts,
   they violate the model of a single global PKI, albeit to meet real
   operational needs.  Hence they MUST be implemented to assure the
   local constraint.

SB> I can see why RFC2119 language is used, and it seems correct to use it,
however Nits is complaining that there is no RFC2119 boilerplate.

=========

   [I-D.ietf-sidr-bgpsec-overview]
              Lepinski, M. and S. Turner, "An Overview of BGPSEC",
              draft-ietf-sidr-bgpsec-overview-02 (work in progress), May
              2012.

SB> Nits asks if you mean this version or -08?

[Sidrops] Rtgdir last call review of draft-ietf-s… Stewart Bryant via Datatracker
Re: [Sidrops] Rtgdir last call review of draft-ie… Randy Bush
Re: [Sidrops] Rtgdir last call review of draft-ie… Randy Bush
Re: [Sidrops] Rtgdir last call review of draft-ie… Joel Jaeggli
Re: [Sidrops] Rtgdir last call review of draft-ie… Randy Bush