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/[email protected]/
[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 ]
Randy Bush
randy at psg.com
Mon Jan 3 18:51:12 CET 2022
mornin' job > Regardless of the cause of the dysfunctionality, I think the Database > Working Group is the appropriate forum to discuss the problem of being > unable to use the geofeed RPSL attribute in database objects. my point is that i think the wg already did. ncc legal, in post-wg review, added this restriction. i.e. we have run the process already. i really like the ncc legal folk, so would be happy to join you in a zoom or two to explore the issues with them. but this is not a hill on which i am inclined to shed blood. randy --- randy at psg.com `gpg --locate-external-keys --auto-key-locate wkd randy at psg.com` signatures are back, thanks to dmarc header butchery
- 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 ]