On 2 August 2017 at 13:06, Arnold Nipper <arn...@nipper.de> wrote: > On 02.08.2017 11:40, Job Snijders wrote: > > > If we look at a record like https://peeringdb.com/net/1045, what do the > > values behind "IPv4 Prefixes" (250000) and "IPv6 prefixes" (25000) > > actually mean? > > > > Is this the number of prefixes NTT will announce to any EBGP neighbor? > > Or to some EBGP neighbors? Or is this the recommended maximum prefix > > limit for IPv4 and IPv6? > > > > Perhaps the website would benefit from changing "IPv4 Prefixes" to > > "Recommended IPv4 Prefix limit" - however that phrasing is slightly too > > long to neatly fit in the column. (I'm not advocating to change the > > field names in the API) > > > > If we make it shorter: "Max IPv6 Prefixes" I feel that the semantics yet > > again are somewhat ambiguous. Ideas? > > > > Leave it as it is and add an (i) tag which explains in more detail what > the meaning of this field is. > > Ideally there would be a description of *all* fields used in PeeringDB. > > > Personally I always read "IPv4/6 prefixes" as ""Recommended IPv4/6 > Prefix limit" >
Wouldn't an user friendly explanation of all the possible fields registrants can fill in information into. Have a page/section at http://docs.peeringdb.com documenting what the field is intended for ? Kind Regards Christoffer
_______________________________________________ User-discuss mailing list User-discuss@lists.peeringdb.com http://lists.peeringdb.com/cgi-bin/mailman/listinfo/user-discuss
