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] proposal: new attribute 'geofeed:'

Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
Next message (by thread): [db-wg] proposal: new attribute 'geofeed:'

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

Sander Steffann sander at steffann.nl
Mon Jan 4 07:01:52 CET 2021

Hi Denis,

> Would you say a possible Solution statement could be as simple as:
> 
> Implement a new "geofeed:" attribute in the INETNUM and INET6NUM
> objects based on the IETF draft
> https://datatracker.ietf.org/doc/draft-ietf-opsawg-finding-geofeeds/
> On deployment update any objects in the RIPE Database containing a
> "remarks: Geofeed" with a correctly formatted url into a "geofeed:"
> attribute.

Sounds simple enough 🙂

Let's implement!
Sander

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: </ripe/mail/archives/db-wg/attachments/20210104/91b73169/attachment.sig>

Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
Next message (by thread): [db-wg] proposal: new attribute 'geofeed:'

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

[ db-wg Archives ]