Re: [OPSAWG] Murray Kucherawy's Discuss on draft-ietf-opsawg-finding-geofeeds-12: (with DISCUSS and COMMENT)

[Murray S. Kucherawy]

On Thu, May 20, 2021 at 5:34 AM Randy Bush  wrote:

> > I may have missed something, but why does Section 5 advocate for use
> > of HTTPS to fetch geofeed files in the second paragraph, and then FTP
> > in the seventh?
>
> the former is for getting one file through direct reference.  the latter
> is bulk transfer of the totality of the repository's data through bulk
> query.
>

Ah, thanks, I did miss that subtlety.  I suggest something like this to
spell it out for people like me:

OLD:

   To minimize the load on RIR whois [RFC3912
] services, use of the
   RIR's FTP [RFC0959 ]
services SHOULD be the preferred access.  This
   also provides bulk access instead of fetching by brute force search
   through the IP space.

NEW:

   To minimize the load on RIR whois [RFC3912
] services, use of the
   RIR's FTP [RFC0959 ]
services SHOULD be the preferred access for
   retrieval of the entire repository.  This provides bulk access
   instead of fetching by brute force search through the IP space.

-MSK
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

Re: [OPSAWG] Murray Kucherawy's Discuss on draft-ietf-opsawg-finding-geofeeds-12: (with DISCUSS and COMMENT)

[Randy Bush]

> I may have missed something, but why does Section 5 advocate for use
> of HTTPS to fetch geofeed files in the second paragraph, and then FTP
> in the seventh?

the former is for getting one file through direct reference.  the latter
is bulk transfer of the totality of the repository's data through bulk
query.

> In Section 5, "https" should be "HTTPS" since you're describing a
> protocol and not a URI scheme (or if you meant to do the latter,
> please say so).

sure

randy

___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg