Re: [Last-Call] Intdir last call review of draft-ietf-opsawg-9092-update-06

[Russ Housley <[e-mail]>]

RFC 9092 includes a normative reference to RFC 8805.The shepherd writeup for draft-ietf-opsawg-finding-geofeeds (which eventually became RFC 8805) calls out this downref.

The downward references were referenced in the Last Call:
https://mailarchive.ietf.org/arch/search/?q=draft-ietf-opsawg-finding-geofeeds

At this point, RFC 5485 and RFC 8805 should have been added to the downref registry; however I do not see either of them here https://datatracker.ietf.org/doc/downref

I hope the OPS AD can correct this now.

Russ


> On Nov 20, 2023, at 6:36 AM, Sheng Jiang via Datatracker <[e-mail]> wrote:
> 
> Reviewer: Sheng Jiang
> Review result: Ready with Nits
> 
> I have reviewed this document as part of the IntArea directorate's ongoing
> effort to review all IETF documents being processed by the IESG. Comments that
> are not addressed in last call may be included in AD reviews during the IESG
> review. Document editors and WG chairs should treat these comments just like
> any other last call comments.
> 
> Document: draft-ietf-opsawg-9092-update-06
> Reviewer: Sheng Jiang
> Review Date: 2023-11-20
> Result: Ready with Nits
> 
> This Standards Track document specifies how to augment the 
> Routing Policy Specification Language inetnum: class to 
> refer specifically to geofeed data files and describes an 
> optional scheme that uses the Resource Public Key 
> Infrastructure to authenticate the geofeed datafiles. It intends
> to obsolete RFC 9092. It is well written and almost ready with 
> several Nits regarding to references, see beloww.
> 
> Obsolete normative reference: RFC 2818 (Obsoleted by RFC 9110)
> Obsolete normative reference: RFC 6486 (Obsoleted by RFC 9286)
> Downref: Normative reference to an Informational RFC: RFC 8805