[PDB-gov] Voting eligibility

bill manning azuremesa at gmail.com
Fri Nov 20 15:52:08 PST 2015

Ok, so this is enlightening.  What is the point of placing non-peering data
into a peeringDataBase?  Is this because peering involves more than just an
abstract layer3 (BGP) policy constraint?  Peering, as used historically as
"meet-me" space to cross connect and the policy is the cross-connect
contract?  If so, then some of us (well me) have been too narrowly focused
on the L3/BGP point.
But this "layer violation" has lead to a flurry of emails.  And for me, it
has been enlightening.  So Sorry to make some of you winch at how long it
took me to see this other facet.  Are there others?

On Fri, Nov 20, 2015 at 2:51 PM, Chris Caputo <secretary at peeringdb.com>

> As written, ASNs are not the basis of membership criteria.  PeeringDB
> serves more than networks/ASNs.  As written, colocation facilities and
> IXPs are also able to be members.  Any organization with an active (ie.,
> not banned) PeeringDB record, is able to be a member.
> If folks want to make ASNs be the basis of membership criteria, then in
> doing so they would be disenfranchising many existing users of PeeringDB.
> Chris
> _______________________________________________
> Pdb-gov mailing list
> Pdb-gov at lists.peeringdb.com
> http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.peeringdb.com/pipermail/pdb-gov/attachments/20151120/b6c96786/attachment.html>

More information about the Pdb-gov mailing list