This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/

[db-wg] geofeed issue: can't add geofeed attribute to PI /48

• Previous message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
• Next message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Job Snijders job at sobornost.net
Thu Feb 24 13:19:12 CET 2022

Hi Ed,

On Mon, Feb 21, 2022 at 03:56:00PM +0100, Edward Shryane wrote:
> Accordingly, we will allow "geofeed:" on ALLOCATED PA or top-level
> ASSIGNED PI (for IPv4) and ALLOCATED-BY-RIR on top-level ASSIGNED PI
> (for IPv6).

For completeness sake, can you clarify which types of objects (under the
new rules) are NOT eligible to specify the 'geofeed:' RPSL attribute?

Kind regards,

Job

• Previous message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
• Next message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]