[ris-int] RE: Three things...
Matthew Williams matthew at ripe.net
Wed Jul 28 19:55:14 CEST 2004
1. Excellent stuff. Much obliged. 2. Great that we're on the same page there :) 3. ACK Cheers, Matthew > -----Original Message----- > From: Dave Knight [mailto:dknight at ripe.net] > Sent: 28 July 2004 18:59 > To: Matthew Williams > Cc: ris-int at ripe.net; 'Arife Vural'; k-anycast at ripe.net > Subject: RE: Three things... > > > At 18:16 28/07/2004 +0200, Matthew Williams wrote: > >Hi Dave, > > > >See below: > > > > > > > > > >1. Flashing RIS (~we need peers etc etc) in K-anycast > > > peering ack (SED > > > >do > > > >RIS peering reqs) > > > > > > We can do that. We can add your blurb to the bottom of: > > > /home/kroot/doc/peer-info Let me know what you want to put there. > > > > > > >Something like this? Or is it too much? > > I don't really have an opinion ;) > Here's what I did: > > Peering Details > -------------------------------------------------------------- > -------------- > Location IXP IP Route-Set Type > --------------- --------------- --------------- > --------------- ------- > London XchangePoint 217.79.160.94 RS-KROOT-LINX Global > Amsterdam AMS-IX 195.69.144.240 RS-KROOT-AMS-IX Global > NL-IX 194.153.154.80 > RS-KROOT-AMS-IX Global > Athens AIX 195.130.89.220 RS-KROOT-GRNET Local > Qatar QTEL 212.77.199.187 RS-KROOT Local > -------------------------------------------------------------- > -------------- > > Peering Policy > -------------------------------------------------------------- > -------------- > We advertise only our own routes in AS25152. We will update > our aut-num object in the RIPE Whois Database and kindly > request you to update your aut-num object also. We will not > to enter into a formal peering contract. At our Global mirror > instances we accept any routes offered including transit. At > our Local mirror instances we want to limit visibility of our > advertisements and will likely use the well known no-export > BGP community, if you would like to override this in order to > advertise this route to your downstream customers let us know > in advance. In the event of problems caused by leaked > advertisements our policy is to shut down peerings and ask > questions later. The remarks at the end of our AS25152 > aut-num object hold the authoritative list of locations at > which AS25152 is peering and which of those locations is > considered Global or Local. > -------------------------------------------------------------- > -------------- > > Contact Info > -------------------------------------------------------------- > -------------- > Support: <kroot-ops at ripe.net> | NOC Phone: +31 20 535 4400 > Peering: <k-peering at ripe.net> | NOC Email: <ops at ripe.net> > WWW: <http://k.root-servers.org> | > -------------------------------------------------------------- > -------------- > > DNS Monitoring (dnsmon) & Test Traffic Measurements (TTM) > -------------------------------------------------------------- > -------------- > - Home Page: <http://dnsmon.ripe.net/> > - Server View: <http://dnsmon.ripe.net/dns-servmon/server/> > - TTM General Information: <http://www.ripe.net/ttm/> > -------------------------------------------------------------- > -------------- > > Routing Information Service (RIS) > -------------------------------------------------------------- > -------------- > - myASn beta: <http://www.ris.ripe.net/myasn.html> > - Other Tools: <http://www.ripe.net/ris/query.html> > - RIS General Information: <http://www.ripe.net/ris/> > > You can support the RIS by donating a BGP feed. For a list of > peering locations, see URL: > <http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi> > Please send your peering request to rispeering at ripe.net. > -------------------------------------------------------------- > -------------- > > > > > I intend to do some work on making peerings management easier for > > > RIPENCC,RIS,KROOT,AS112 > > > >Good move. As you know, SED will handle peering requests for the RIS. > >There should possibly be more coordination, especially > >RIS/myASn and K. > > That's the plan. > > > > following RIPE49. I will no doubt call a meeting when this gets > > > started to look at everyones > > > requirements before taking this to SED. > > > > > > >2. myASn accounts (also by SED in the future) sync w/ > > > K-anycast peering > > > >requests (monitor no-export compliance) > > > > > > I have been ignoring myASn stuff at the moment. We don't > have time > > > to do anything with it before RIPE49. I look forward to spending > > > some time getting it all sorted shortly thereafter though :) > > > > > > When is it planned that the current development effort > ends and goes > > > into production? > > > >SED will take over v.1 of myASn by the second week in Aug. I'd say > >announcement time would be around 1st of Sept, well before R49, > >but that's ultimately SED's call. > > Fair enough. > > > > >3. When will you announce me to contacts ? ;) > > > > > > Heh, almost there. I have been getting all status up to date and > > > reorganising things on the iii pages. I will shortly get to > > > announcing you .. honest :) > > > >Okay, just bug when you need me. I'll monitor mail exchanges > as much as > >I can. > > Cool beans :-) > > Cheers, > dave >
[ Ris-int Archives ]