Hello all,

FYI, following up on various discussions and the BoF we had on this list about 
NRTMv4 and NWI-12, a draft has now been submitted. If you’re interested in 
discussing further details of the proposed protocol, do send your questions and 
comments to that mailing list.

Sasha

Forwarded message:
> From: Sasha Romijn
> To: [email protected]
> Subject: [GROW] draft-spaghetti-grow-nrtm-v4-00
> Date: Fri, 04 Feb 2022 13:04:48 +0100
>
> Hello,
>
> We’ve submitted a draft for the Near Real Time Mirroring Protocol (NRTM) 
> version 4: https://datatracker.ietf.org/doc/draft-spaghetti-grow-nrtm-v4/
>
> This document specifies a one-way synchronization protocol for Internet 
> Routing Registry (IRR) records. The protocol allows instances of IRR database 
> servers to mirror IRR records, specified in in the Routing Policy 
> Specification Language (RPSL), between each other.
>
> NRTMv4 is intended as a replacement of current synchronization methods mainly 
> based on FTP downloads and NRTM version 3, which have many problems that are 
> addressed in NRTMv4.
>
> The need for this originated from experiences by users of IRRD v4, and 
> discussions in the RIPE Database working group, tracked under NWI-12:
> https://www.ripe.net/ripe/mail/archives/db-wg/2020-November/006720.html
>
> The broad strokes of this draft were previously discussed in a BoF in the 
> RIPE Database wg, which included several operators of IRR databases, and 
> responses were overall positive. I am also the maintainer of IRRD v4, one of 
> the most widely used IRR database servers, and will implement it in there.
>
> I’m proposing this draft for adoption by this working group. I would also be 
> happy to present it in the IETF 113 session.
>
> Sasha Romijn
>
> _______________________________________________
> GROW mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/grow

-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/db-wg

Reply via email to