From Daniel.Karrenberg at ripe.net Fri Jul 1 12:06:44 1994 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Fri, 01 Jul 1994 12:06:44 +0200 Subject: New at the RIPE NCC: Mirjam Kuehne Message-ID: <9407011006.AA12189@reif.ripe.net> Today the RIPE NCC welcomes Mirjam Kuehne as new junior administrative staff member. Mirjam joins us from TU Berlin where she has both graduated as a MSc. computer science and worked in an international project in the field of knowledge representation. Mirjam will join Anne Lord, Geert Jan and myself in providing the NCC's core services from today. This will provide much needed relief. I ask all of you to welcome Mirjam and to help him get used to his new responsibilities quickly. Our current trainee Geza Turchanyi will leave us on the 15th of this month. Anyone interested in a traineeship for 3-6 months at the NCC is invited to contact us. The PRIDE and NCC staff work as one team. So it is quite possible that you might deal with Marten or Tony on NCC matters occasionally. If you have any further questions, please do not hesitate to contact us. Regards Daniel Karrenberg RIPE NCC Manager From nipper at xlink.net Fri Jul 1 17:31:19 1994 From: nipper at xlink.net (Arnold Nipper) Date: Fri, 1 Jul 1994 17:31:19 +0200 (MET DST) Subject: New at the RIPE NCC: Mirjam Kuehne In-Reply-To: <9407011006.AA12189@reif.ripe.net> from "Daniel Karrenberg" at Jul 1, 94 12:06:44 pm Message-ID: <"xlink100.x.385:01.06.94.15.31.30"@xlink.net> Welcome Mirjam, Daniel Karrenberg wrote: > > > Today the RIPE NCC welcomes Mirjam Kuehne as new junior administrative > staff member. Mirjam joins us from TU Berlin where she has both > graduated as a MSc. computer science and worked in an international > project in the field of knowledge representation. > > Mirjam will join Anne Lord, Geert Jan and myself in providing the NCC's > core services from today. This will provide much needed relief. I ask > all of you to welcome Mirjam and to help him get used to his new Hmmh, Mirjam sounds like a women's name, so I 'm a little confused to read "him" ... > responsibilities quickly. > > Our current trainee Geza Turchanyi will leave us on the 15th of this > month. Anyone interested in a traineeship for 3-6 months at the NCC is > invited to contact us. > > The PRIDE and NCC staff work as one team. So it is quite possible that > you might deal with Marten or Tony on NCC matters occasionally. > > If you have any further questions, please do not hesitate to contact us. > > Regards > > Daniel Karrenberg > RIPE NCC Manager -- Arnold Nipper / email: nipper at xlink.net NTG Netzwerk und Telematic GmbH \/ phone: +49 721 9652 0 Geschaeftsbereich XLINK /\ LINK fax: +49 721 9652 210 Vincenz-Priessnitz-Str. 3 /_______ D-76131 Karlsruhe, Germany From Daniel.Karrenberg at ripe.net Mon Jul 4 17:12:33 1994 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Mon, 04 Jul 1994 17:12:33 +0200 Subject: New at the RIPE NCC: Mirjam Kuehne In-Reply-To: Your message of Fri, 01 Jul 1994 17:31:19 MDT. <"xlink100.x.385:01.06.94.15.31.30"@xlink.net> Message-ID: <9407041512.AA00522@reif.ripe.net> > Arnold Nipper writes: > Hmmh, Mirjam sounds like a women's name, so I 'm a little confused to read > "him" ... OK. I admit I copied the welcome paragraph from an earlier mail and somehow accidentally undid the s/him/her/. Mirjam definitely is of the finimine gender. Daniel PS: Thou shalt never send mails to large lists late on Friday. ;-) From Daniel.Karrenberg at ripe.net Tue Jul 19 10:12:55 1994 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 19 Jul 1994 10:12:55 +0200 Subject: AS number assignment criteria Message-ID: <9407190812.AA17952@reif.ripe.net> Just a quick one about assigning AS numbers. The reasons for ASN requests we get can be categorised as follows: 1 - "Because the router manual says we need one." Needs no further explanation, does it? 2 - "To identify routing processes for internal routing." Some isolated networks run multiple IGPs and seek unique numbers to identify them. 3 - "To identify single-homed ASes." They connect to a service provider or to another enterprise and use external routing. The other end tells them they need an ASN. Strictly speaking they do not need one, because they can only have one external policy. 4 - "To identify multi-homed ASes." These really need one because they have a unique external policy. So far we have never assigned ASNs to categories 1 and 2. I see no reason why we should either. We have assigned ASNs to some in category 3 because their service provider required it for their management purposes. We have always assigned ASNs to category 4. The question now is: Should we assign ASNs to those in category 3 who request it because their ISP requires it? This is a potentially large number. Opinions? Daniel From Marten.Terpstra at ripe.net Tue Jul 19 11:31:38 1994 From: Marten.Terpstra at ripe.net (Marten Terpstra) Date: Tue, 19 Jul 1994 11:31:38 +0200 Subject: AS number assignment criteria In-Reply-To: Your message of Tue, 19 Jul 1994 10:12:55 MDT. <9407190812.AA17952@reif.ripe.net> Message-ID: <9407190931.AA00436@rijp.ripe.net> * 3 - "To identify single-homed ASes." * They connect to a service provider or to another enterprise and * use external routing. The other end tells them they need an ASN. * Strictly speaking they do not need one, because they can only have * one external policy. * The question now is: Should we assign ASNs to those in category 3 * who request it because their ISP requires it? * This is a potentially large number. * * Opinions? Potentially the ISP can request an AS because it can enforce a stricter policy on its client than on its own AS. It can for instance say that the customer AS will not be announced to XX where the AS of the provider itself could be announced to XX. Unlikely, but a different policy possibly needing an AS...... -Marten From Daniel.Karrenberg at ripe.net Tue Jul 19 12:06:35 1994 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 19 Jul 1994 12:06:35 +0200 Subject: AS number assignment criteria In-Reply-To: Your message of Tue, 19 Jul 1994 11:31:38 MDT. <9407190931.AA00436@rijp.ripe.net> Message-ID: <9407191006.AA00693@reif.ripe.net> > Marten Terpstra writes: > > * 3 - "To identify single-homed ASes." > * They connect to a service provider or to another enterprise and > * use external routing. The other end tells them they need an ASN. > * Strictly speaking they do not need one, because they can only have > * one external policy. > > * The question now is: Should we assign ASNs to those in category 3 > * who request it because their ISP requires it? > * This is a potentially large number. > * > * Opinions? > > Potentially the ISP can request an AS because it can enforce a > stricter policy on its client than on its own AS. It can for instance > say that the customer AS will not be announced to XX where the AS of > the provider itself could be announced to XX. Unlikely, but a > different policy possibly needing an AS...... Right. From keith at pipex.net Tue Jul 19 15:04:53 1994 From: keith at pipex.net (Keith Mitchell) Date: Tue, 19 Jul 1994 14:04:53 +0100 Subject: AS number assignment criteria In-Reply-To: <9407190931.AA00436@rijp.ripe.net> Message-ID: <199407191304.OAA22637@pipe.pipex.net> In <9407190931.AA00436 at rijp.ripe.net>, wrote: > * 3 - "To identify single-homed ASes." > * They connect to a service provider or to another enterprise and > * use external routing. The other end tells them they need an ASN. > * Strictly speaking they do not need one, because they can only have > * one external policy. > > * The question now is: Should we assign ASNs to those in category 3 > * who request it because their ISP requires it? > * This is a potentially large number. > * > * Opinions? > > Potentially the ISP can request an AS because it can enforce a > stricter policy on its client than on its own AS. It can for instance > say that the customer AS will not be announced to XX where the AS of > the provider itself could be announced to XX. Unlikely, but a > different policy possibly needing an AS...... I tend to agree with Marten here. We have a number of down-stream providers who buy transit from us, and find it virtually essential to be able to distinguish their routes from ours using AS number, to provide a clean adminstrative boundary. An example of Marten's principle (to pick a hot topic :-), is where the downstream provider is not a CIX member, but the upstream one is. I think therefore the rule is that category 3 sites can receive an AS number if they are a re-seller of some kind, rather than just a retail customer. In practice, a resale provider might well be expected to set up peerings with other providers on their own in the future, so putting an AS number in now also helps future-proof things. Of course, it can often be hard to define "re-seller" or "provider"in some circumstances, I suppose an alternative rule could be that they need to have some minimum number of aggregates to qualify, it is clearly worthless to set all this up if they only have one. Keith Mitchell Network Manager Public IP Exchange keith at pipex.net 216 The Science Park keith at unipalm.co.uk Cambridge, UK Phone: +44 223-250120 Fax: +44 223-250121 PIPEX is a subsidiary of Unipalm Group PLC