Dear Tom,

On Wed, Apr 30, 2025 at 10:03:38PM +1000, Tom Harrison wrote:
> On Wed, Apr 23, 2025 at 04:23:35PM -0300, Paolo Lucente wrote:
> > This email begins a two-week WGLC on:
> > 
> >     Near Real Time Mirroring (NRTM) version 4
> >     https://datatracker.ietf.org/doc/draft-ietf-grow-nrtm-v4/06/
> > 
> > Abstract: 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
> >    the Routing Policy Specification Language (RPSL), between each other.
> > 
> > The implementation report can be reviewed here:
> > https://wiki.ietf.org/en/group/grow/implementations/draft-ietf-grow-nrtm-v4
> > 
> > Please take time to review this draft and post comments by May 8th 2025.
> > 
> > Questions, suggestions, supportive comments, and objections are welcomed.
> > 
> > In parallel there will be another email shortly for the IPR poll.
> 
> I've read this document and support publication.  Some small
> suggestions:
> 
>  - It's not clear why compression via gzip is a first-class element of
>    this specification.  A more general approach would be to note that
>    compressed data can be requested and provided by way of the
>    Accept-Encoding HTTP header.

Operational experience suggests that this type of data is quite unwieldy
in uncompressed form both 'in transit' as well as 'at rest', to the
point that making it a first-class aspect merely is a continuation of
established practises.

For example both ftp://ftp.apnic.net/pub/apnic/dbase/data and
ftp://ftp.radb.net/radb/dbase do not rely on the availability
opportunistic compressed encoding in the transport layer.

>  - Re "[t]he timestamp MUST be an [RFC3339] timestamp", limiting the
>    time-offset component to "Z" will simplify the parsing operation a
>    bit.

Oh, great suggestion! Mandating UTC (Zulu) timestamps will simplify
operator debugging life significantly.

Kind regards,

Job

_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to