[PDB-tech] API - question about ixlan and netix

[Arnold Nipper]

On 22.06.2015 18:36, Mike Hammett wrote:
> Most networks I work with are too lazy to create all of the PeeringDB
> entries. I do like the ability for an IX to enter in the information and
> the network just has to confirm it for it to actually be viewable to the
> public.
> 

That's the way how it will work. However they will have at least to tick
a box once.


Arnold

> 
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
> 
> <https://www.facebook.com/ICSIL><https://plus.google.com/+IntelligentComputingSolutionsDeKalb><https://www.linkedin.com/company/intelligent-computing-solutions><https://twitter.com/ICSIL>
> 
> Midwest Internet Exchange
> http://www.midwest-ix.com
> 
> <https://www.facebook.com/mdwestix><https://www.linkedin.com/company/midwest-internet-exchange><https://twitter.com/mdwestix>
> 
> ------------------------------------------------------------------------
> *From: *"Arnold Nipper" <arnold.nipper at de-cix.net>
> *To: *"Stefan Neufeind" <peeringdb at stefan-neufeind.de>,
> pdb-tech at lists.peeringdb.com
> *Sent: *Monday, June 22, 2015 11:20:52 AM
> *Subject: *Re: [PDB-tech] API - question about ixlan and netix
> 
> Stefan,
> 
> On 22.06.2015 08:57, Stefan Neufeind wrote:
>> Am 22.06.2015 um 07:03 schrieb Andy Linton:
>>> Matt,
>>>
>>> I can see that you currently have a way of enumerating peers for the
>>> beta web page e.g. if I look at:
>>>
>>> https://beta.peeringdb.com/ix/132
>>>
>>> I can see there are 31 "Peers at this Exchange Point" (which of course
>>> is those who have bothered to add themselves to Peering DB)
>>
>> [...]
>>
>> This brings me back to a thought from a while ago:
>> Would it make sense to maybe consider allowing "IXP-owners" to update
>> the list of their participants as well? That would mean adding members
>> and updating their details for this particular IXP.
>> And maybe even for the case where networks are not yet listed at all in
>> PeeringDB being able to add "minimal" records to be able to add those to
>> the IXP-list as well? Somebody could later register to PeeringDB and
>> claim ownership of an already existing minimal entry or so.
>>
>> If you think that might make sense, I'll be happy to add that as two
>> feature-requests on Github.
>>
> 
> pls keep in mind thaat PeeringDB follows a strict ownership-of-data
> rule. That means it's up to the networks to decide whether they want to
> be listed as an IXP member or not. There might be several reasons why a
> network wants to be not listed. Otoh networks will not be any longer
> allowed to put in IP addresses as these data "belongs" to the IXP. Thus
> iff network and IP agree an entry will be visible. This should also
> remove any stale entries if the IXP takes care for its data. When in
> full production PeeringDB 2.0 will really rock!
> 
> 
> Best regards
> Arnold (with my PeeringDB admin hat on)
> -- 
> Arnold Nipper
> CTO/COO and Co-Founder
> 
> DE-CIX Management GmbH | Lindleystrasse 12 | 60314 Frankfurt am Main |
> Germany | www.de-cix.net | Phone +49 69 1730902 22 |
> Mobile +49 172 2650958 | Fax +49 69 4056 2716 |
> arnold.nipper at de-cix.net | Geschaeftsfuehrer Harald A. Summa |
> Registergericht AG Koeln HRB 51135
> 
> 
> _______________________________________________
> Pdb-tech mailing list
> Pdb-tech at lists.peeringdb.com
> http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech
> 
> 
> 
> _______________________________________________
> Pdb-tech mailing list
> Pdb-tech at lists.peeringdb.com
> http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech
> 


-- 
Arnold Nipper
CTO/COO and Co-Founder

DE-CIX Management GmbH | Lindleystrasse 12 | 60314 Frankfurt am Main |
Germany | www.de-cix.net | Phone +49 69 1730902 22 |
Mobile +49 172 2650958 | Fax +49 69 4056 2716 |
arnold.nipper at de-cix.net | Geschaeftsfuehrer Harald A. Summa |
Registergericht AG Koeln HRB 51135

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: OpenPGP digital signature
URL: <http://lists.peeringdb.com/pipermail/pdb-tech/attachments/20150622/3c3a139b/attachment.sig>