- Test - lists.nanog.org

Re: Operations training materials
by Sean Doran 24 Apr '95

24 Apr '95

>Christian Huitema Please do not invoke the names of IAB folks as routing authorities on the NANOG mailing list. Thank you. Sean.

2 1

Re: Has PSI been assigned network 1?
by sob＠academ.com 24 Apr '95

24 Apr '95

For DNS to be usable, folks have to permit TCP DNS to work. I know of some service providers that filter TCP DNS connections. UDP packets are not big enough for many responses from an whois-type request. -- Stan | Academ Consulting Services |internet: sob(a)academ.com Olan | For more info on academ, see this |uucp: bcm!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.

4 3

Re: Has PSI been assigned network 1?
by Vadim Antonov 24 Apr '95

24 Apr '95

Well, there is a big _if_: if things will work w/o RADB (and they will, for no sane provider will use RADB as the sole source of exterior information at peering points, not for at least before it became the proven and stable service) -- people will forget to update things, cut the corners, etc. NACRs were so big headache that our implementation people dance around when they hear that there won't be any NACRs. RADB got to be easy to use to become real. The e-mail interface of NACRs is close to uselessness, and too big headache to deal with. Waiting time on processing is simply ridiculous. There should be a host accepting telnet sessions for on-line updates (which have to be installed *immediately*, so whoever added a network can test connectivity and go ahead). There should be well-defined and useful interface to service providers databases. It should be secure. RADB should be able to implement _existing_ routing policies, not the subset which can be defined in RIPE-81 (it currently can't, there are places which use a lot of _very_ hairy stuff). Without that i do not see RADB being successful or useful beyond the point of filtering updates from particularly obnoxious peers. --vadim From: Guy Middleton <guy(a)ghost.uunet.ca> To: avg(a)sprint.net, curtis(a)ans.net, jerry(a)fc.net Subject: Re: Has PSI been assigned network 1? Cc: nanog(a)merit.edu, prs(a)isi.edu Message-Id: <95Apr18.213028edt.53028-1(a)ghost.uunet.ca> Date: Tue, 18 Apr 1995 21:30:28 -0400 > Curtis, you are able to do that only because all others were > legally bound to fill your database. > > I'm not sure people will be spending their resources on > populating database for somebody else's benefit. > > (And RADB already has lots of garbadge in it). Once the RADB is in general use, we can expect that networks other than ANS will use it to generate route-filters. There is an interconnect point already using the CA*net registry, for example. Any active use of the RADB creates an incentive to ensure that it is accurate.

5 5

Re: Has PSI been assigned network 1?
by jgs＠aads.net 24 Apr '95

24 Apr '95

[trimmed individuals from cc list] At 8:32 AM 4/24/95, Michael F. Nittmann wrote: >Route holdowns: > >los pobres paquetos: that's just the beauty and purpose of routing >protocols to propagate the info so that los pobres paquetos don't clog >the pipe with the goal of being dropped. Routing protocols propagate the info at some granularity. You inevitably have to choose a granularity smaller than which you don't care to propagate trivial little facts about reachability, though. Traditionally, the grain of routing was the classful net, and no one propagated information about subnets or host routes in their external routing. For example, if I turned off my workstation, a telnet attempt would send packets all the way from you to my border before you got an unreachable. So dynamic routing has never provided full disclosure of the exact topology. It provides a useful approximation. Part of what you have to decide is the tradeoff between routing load and how much information it is really useful to propagate. Pipe clog is not likely to be a big issue for TCP connections at any rate (as I think someone else observed) since they back off pretty fast. Also, note that with CIDR the same kind of behavior is already built in to the architecture: If you are advertising foo/16 and your customer foo/24 drops off the face of the earth, are you going to send a withdraw? I think not. Packets for foo/24 get hauled to your border before you send an unreachable. This has not yet caused the death of the net as we know it. >To hold routes eternally down is not good: what if the customer >disconnects that network? I don't want to be notified by all leaf >networks when they will hickup or disconnect for good. I don't understand this point: You don't want to have to have to change your router configuration even if you lose a customer? I have a hard time believing that this is what you mean. Many people have made good arguments for why you need to do dynamic routing with multi-homed customers, but I have never yet seen a convincing reason not to hold down stubs. --John Scudder

1 0

Re: Has PSI been assigned network 1?
by Vadim Antonov 24 Apr '95

24 Apr '95

Daniel, it shows that you live in the world where 1000+ internet service providers isn't reality yet :) A half of them has to be explained how route announcement is different from broadcasting. Forget about good citizenship -- they may be willing but they must be educated first. --vadim > Vadim Antonov <avg(a)sprint.net> writes: > > Routing Registry w/o means to enforce won't be able to keep > a resemblance of accurate data (not with the modus operandi of > most providers in US). We fundamentally disagree here. I agree that the more the RR is used for actual configurations, the better the data will be. I disagree that "enforcement" is necessary. I disagree that "enforcement" by RS is necessary. I observe that reasonable quality data can be gathered even when the only incentive is good citizenship and nice diagnostic tools. Daniel

2 1

Re: Operations training materials
by geoffw＠nexsys.net 24 Apr '95

24 Apr '95

> Class is in session, time to do homework! Here is a list of reading/reference > materials that will be used this term. Note that it will be modified as > the term progresses. > > (Go for it. Geoff has volunteered space and assistance) > > --bill > Well I'm waiting, I'll start a page as soon as I start getting info. Folks can mail me off-line if they want. geoffw

2 1

Operations training materials
by Michael Dillon 23 Apr '95

23 Apr '95

On Sun, 23 Apr 1995 elliot(a)ghost.uunet.ca wrote: > On Sat, 22 Apr 1995, Michael Dillon wrote: > >Right now it is possible for each new operations person at a new ISP to > >hunt through all the RFC's for relevant documents, look through the IETF > >mailing lists for relevant lists and then hunt through those lists for > >relevant messages, etc.... However, it would be far more efficient to > >have one technically skilled researcher do this and distill the important > >info for the rest of us. > > Ah, so you want someone else to do your homework for you? Not for me, I've done my homework. Unfortunately, I no longer have many of the "texbooks" nor a coherent record of all my sources of info so if I wanted to train another person it would be like reinventing the wheel. :-( > I believe that the general feeling in the Internet community that it's > essential not only to have such information, but also to be able to > understand the sources from which the information is derived; following > the IETF mailing lists and understanding relevant RFCs is part of what > makes a "good" operator. Agreed. This is the beauty of publishing tutorial materials on the Web; you can have direct links to the RELEVANT source materials including the important IETF lists and list archives. > The Internet is constantly changing, and in order to keep up, an operator > *must* understand new RFCs and mailing list discussion *as they occur*. > There's no time to wait for some to write a book simplifying things for you... Not a book, more like a table of contents with introductory summaries. Consider that most new ISP's don't even know what IETF is, don't know what NANOG is, have never heard of BGP, etc.... They may have experience with UNIX and TCP/IP Lan's or with BBSes and I have come across more than a few who have little more than DOS experience. These people are LOOKING for a book to help them but there are no such books. They are looking for a newsgroup to help them but there are no such newsgroups. They are even looking for a mailing list, but there is no single mailing list that covers what you need to know. Given that a WWW site as I have envisioned did exist, those who know would have a quick and easy answer to all operational questions. "Go and read the stuff at http://...... and then if you need to know more, ask me." Michael Dillon Voice: +1-604-549-1036 Network Operations Fax: +1-604-542-4130 Okanagan Internet Junction Internet: michael(a)junction.net http://www.junction.net - The Okanagan's 1st full-service Internet provider

3 3

Re: Has PSI been assigned network 1?
by Vadim Antonov 23 Apr '95

23 Apr '95

Bill Manning wrote: >Even with a route registry, you have no way of knowing, apriora, that >the registration is correct. There have already been "helpful" attempts >to register information for others w/o their consent. Yep. >In general, it depends on religious registration in whois and/or rwhois, >the distributed IRR and PGP. Here is a brief summary: > Basically, I have made a proposal to have the Internic set an > example by registering all delegations in whois/RWhois and > signing the delegation. > All down-stream ISPs should do the same (register delegations > in RWhois and sign any downstream delegations) > When a custodian wishes to register a delegation for routing, > they sign the request. There is a MUCH simplier solution. First, use DNS instead of centralized WHOIS database. DNS already has IN-ADDR.ARPA zones with PTR RRs and it is nothing to add TXT RRs with contact etc information. Delegation of authority is done the same way as it's done with IN-ADDR zones. The mechanism is in place and works. InterNIC delegates /8 or /16 zones to providers, providers delegate /16s and /24s to other providers or customers. Since end-users will keep their contact information in their primary servers, right on premises, the likelihood of it being up-to-date is much higher -- simply because every time the LAN administrator will add or remove a host he'll see it. --vadim

3 3

Re: Has PSI been assigned network 1?
by Vadim Antonov 23 Apr '95

23 Apr '95

No, the problem is that operational people only about 50% native English speakers, and most hate writing :) I keep buzzing our management that we need a good technical writer to put engineering knowledge into undesrstandable English. --vadim From: salo(a)msc.edu (Tim Salo) Date: Sun, 23 Apr 1995 00:17:37 -0500 To: G.Huston(a)aarnet.edu.au Subject: Re: Has PSI been assigned network 1? Cc: nanog(a)merit.edu > From: Geoff Huston <G.Huston(a)aarnet.edu.au> > Subject: Re: Has PSI been assigned network 1? > To: michael(a)okjunc.junction.net > Date: Sat, 22 Apr 1995 18:00:09 +1000 (EST) > Cc: nanog(a)merit.edu, rps(a)isi.edu > [...] > After some years being associated with the IEPG the observation I have > to make is that the operations folk who really do understand how the > Internet is glued together are way too busy keeping it strung together > to do anything else. > [...] So, the operational folks are too busy to transfer their knowledge to new recruits (who might actually help them keep the Net running), and then the experienced operational folks wonder why they are so busy? Something doesn't seem quite right with this picture... -tjs

1 0

Re: Operations training materials
by geoffw＠nexsys.net 23 Apr '95

23 Apr '95

> On Sat, 22 Apr 1995, Randy Bush wrote: > > > > Not for me, I've done my homework. Unfortunately, I no longer have > > > many of the "texbooks" nor a coherent record of all my sources of info > > > so if I wanted to train another person it would be like reinventing the > > > wheel. :-( > > > > Well then. Money meet mouth, mouth money. Jeez! > > Look Randy, this thread started out with people from Sprint and ANS? > talking about the efforts involved in getting new operations people on > stream and pointing out that they simply couldn't provide any training > for their new ISP customers. > > What I'm trying to point out is that there is more than one way to skin a > cat, i.e. writing a tutorial for the WWW is a far more cost effective > training tool than trying to do one-on-one with each new ISP that signs > on. My perspective is that of someone who has just climbed most of the > steepest part of the learning curve and who has noticed that many of my > peers (new ISP's) haven't got a clue and don't know where to find the info. > > I point them at http://www.isoc.org, http://www.merit.edu, > http://www.ripe.net and http://www.internic.net but they still have to go > rooting around in there looking for the key items in a mass of > information that is of lesser utility. There is no map! The source > documents are nice to have, but without a map you don't even know if you > are looking at the right ones! OK folks, I'll step to the plate (sorta :) I'll host the site on my website (v-site.net) and act as the co-ordinator, evaluator, since I haven't climbed completely out of the learning curve I should be a good evaluator :) Currently I'm reading this book called "Routing on the Internet" by Christian Huitema, it's not bad and will explain Interior Routing Protocols pretty well, it even has a chapter on "policy based routing" but obviously it is incomplete, still It's a start. If you send me URL's and other bit's of advice, I'll try to organize it into a coherent browseable mass. geoffw

2 1