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 ]

Randy Bush randy at psg.com
Tue Jan 4 19:18:23 CET 2022

[ i wanted to write to you off-list, but illegal header mangling by the
  list software prevented it. ]

> 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

i suspect some confusion caused by the term "end user."  i do not expect
there are many assignments of /48s to individual human beings.  i
suspect that what was meant by end "user was" more in the realm of a PoP,
or head end, or ...

end users in the PII sense tend to be given /56../64

randy

• 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 ]