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 ]
denis walker
ripedenis at gmail.com
Tue Jan 4 11:59:12 CET 2022
Hi Peter Just out of interest, in terms of privacy and identifying individuals, is a /48 PI any different to a /48 PA assignment? Is PI used more for business than by individuals perhaps? cheers denis co-chair DB-WG On Tue, 4 Jan 2022 at 10:39, Peter Hessler via db-wg <db-wg at ripe.net> wrote: > > On 2022 Jan 04 (Tue) at 10:28:04 +0100 (+0100), denis walker via db-wg wrote: > :Hi all > : > :If people want to add geofeed for smaller sizes this runs the risk of > :maintaining a dual system, "geofeed:" and "remarks: geofeed". We could > :end up with "remarks:" values being parsed as they used to be for > :abuse contacts before we added "abuse-c:". > : > :My understanding was that a "geofeed:" could be added to a smaller > :prefix and in the referenced url add data for any prefix you wish, > :including a /48. > : > :Just for reference, for those of you who use the "geofeed:" attribute, > :how many want to add data for a /48? Is this a wide scale issue or a > :corner case? > : > > I have several /48 PI allocations, and would like to add geofeed > attributes to them. Since they are not children of a larger allocation > I control, I currently cannot add a geofeed attribute to them. > > Additionally, a /48 is the smallest acceptable size in the DFZ and I can > easily see people wanting to list geofeeds for those announcements. > > > :cheers > :denis > :co-chair DB-WG > : > :On Tue, 4 Jan 2022 at 10:00, Edward Shryane via db-wg <db-wg at ripe.net> wrote: > :> > :> Hi Cynthia, > :> > :> > On 3 Jan 2022, at 19:44, Cynthia Revström <me at cynthia.re> wrote: > :> > > :> > This seems weird, I would assume it should be greater than 48, not > :> > greater than or equal to 48. > :> > > :> > Ed, can you confirm if this is intended or not? > :> > > :> > :> We currently only allow "geofeed:" to be added to IPv6 prefixes *smaller* than /48, the message is consistent (i.e. greater than or equal to /48 is *not* allowed). > :> > :> We are following Legal's recommendation not to allow geofeed to be added for assignments that are reasonably assumed to be related to one individual user. > :> > :> The /48 prefix size is the maximum size suggested in the "BCOP for Operators: IPv6 prefix assignment for end-users": https://www.ripe.net/publications/docs/ripe-690#4-2--prefix-assignment-options > :> > :> Regards > :> Ed > :> > :> > :> -- > :> > :> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ > : > :-- > : > :To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ > > -- > Cleaning your house while your kids are still growing is like > shoveling the walk before it stops snowing. > -- Phyllis Diller > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/
- 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 ]