September 1995 - Test - lists.nanog.org

skey @ Nanog
by Steven J. Richardson 11 Sep '95

11 Sep '95

FYI: I have an IRIX binary of "key" on ctc21 in /usr/people/nanog/bin. Steve Richardson/Merit

1 0

Re: Other flapping prefixes. Compare and contrast.
by owen＠DeLong.SJ.CA.US 11 Sep '95

11 Sep '95

I disagree with your position completely Mike. None of what is below is what I would consider "bashing". Instead, it is a straightforward and honest display of what is breaking large parts of the Internet with a request that it be solved. I consider it highly constructive. It is absolutely ridiculous that there are providers that still flap routes, especially one the size of PSI, for dialup customers. Owen > Can we stop this bashing right here, Sean? I don't believe that this list > is the adequate forum four such childish behaviour. I have a collection > of your past emails and I am rather fed up withthis. > > Can Sean be removed from the list? These are not contributions in any > sense of constructivity at all. > > Sprint can very well chose a different person to make their corporate > views known on an nanog scale.Mike > > > > Mike > > > On Mon, 11 Sep 1995, Sean Doran wrote: > > > > > There were several other providers who got notes from > > me about prefixes that were flapping every several seconds > > or thereabouts. The tally so far: > > > > Polite "we have a ticket open and will get someone to fix > > things" from three providers (thanks ANS, BBN, EBONE). > > > > A trio of no-answer-yets, one of which has since been > > fixed, one of which will be fixed since I have the > > advantage of sharing a room with the routing guru > > of the NSP in question and the bigger advantage of > > not needing nearly as much sleep. :-) > > > > The third no-answer-yet is from a smaller provider in > > Europe, and I expect they'll get back to me in their morning. > > > > Finally, there was the previous reply. > > > > Sean. > > > > P.S.: Oh, I also have to thank Pushpendra Mohta of CERFNET > > who replied to an earlier note personally with an > > explanation of what was going on. > > > > > > ------------------------------------------------------------------- > Michael F. Nittmann mn(a)ios.com > Senior Network Architect ------------ > IDT/IOS - Internet Online Services ---------- > 294 State Street -------- > Hackensack, NJ 07601 ------ > ---- > +1 (201) 928 1000 xt. 500 -- > +1 (201) 928 1057 FAX +1 (201) 441 5861 Pager \/ > >

1 0

Flapping prefixes and dialup networks. Discuss.
by Sean Doran 11 Sep '95

11 Sep '95

Hi. I sent a network provider (who shall remain protected by a pseudonym like "AS 174") a brief note stating that they had a prefix that was flapping rather heavily throughout the day. I cut and pasted a show ip bgp on the route, pointing out that the prefix flaps on the order of once a minute and was happily being dampened. (cf. my comments Monday afternoon on dampening). BGP routing table entry for 204.4.27.0 255.255.255.0, version 656911 Paths: (2 available, no best path) 1239 174 (history entry) 144.228.101.1 (metric 15) from 144.228.50.6 (144.228.56.1) Origin IGP, metric 1, localpref 90, external Dampinfo: penalty 2915, flapped 199 times in 3:27:31 1239 174 (history entry) 144.228.101.1 (metric 15) from 144.228.50.3 (144.228.53.1) Origin IGP, metric 1, localpref 90, external Dampinfo: penalty 2917, flapped 198 times in 3:27:07 I also asked this nameless service provider to kindly check into this somewhat excessive amount of flap with a view to seeing how it could be made to flap less. Here was the reply. Hopefully saner and more patient folks than me might point out to service provider X that announcing to the entire world when a dialup user comes and goes is not healthy for the Internet, and it shouldn't happen, particularly not at this rate. Why I am not quite in the, "it doesn't matter, they'll be dampened" frame of mind will get explained during the NANOG session. Sean. - -- >From nisc(a)psi.com Sun Sep 10 18:12:58 1995 From: PSI NISC <nisc(a)psi.com> To: Sean Doran <smd(a)icp.net> Subject: nisc-03292 (ticket update) badly flapping prefix (204.4.27/24) Ticket #nisc-03292 09/10/95-18:12:08 silvera SUBJECT: badly flapping prefix (204.4.27/24) Posted by: Aaron Silver ---------- Sean, The customer that this network belongs to is a dial-up customer, and as such, when his connection is up, we broadcast his network IP, and stop broadcasting when he disables his connection. We are unable to prevent his route from propagating in the face of what could be frequent log-in/log-outs. Aaron Silver PSI Customer Support

3 2

one more
by Sean Doran 11 Sep '95

11 Sep '95

Oh, and thanks to Joe Charbonneau <jose(a)net99.net> who has also sent a note pointing out that a flapping prefix from them has been fixed. Sean.

2 1

May 1995 note update
by sob＠academ.com 11 Sep '95

11 Sep '95

Well, I didn't get it all done before the meeting today. Sigh. I will continue to get it done this week. -- Stan | Academ Consulting Services |internet: sob(a)academ.com Olan | For more info on academ, see this |uucp: amdahl!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.

1 0

MBone broadcast of Monday's and Tuesday's Meetings.
by Matt Mathis 10 Sep '95

10 Sep '95

The meetings on Monday and Tuesday will be multicast. See "NANOG" under sd for the details. We successfully tested full duplex operation through the PA system, and expect to be able to include the MBone audience in the discussion, contingent on the good behavior of the MBone itself. One warning: We will be running with "net mutes mike", to permit people on the MBone to interject comments. The downside to this is that if anyone leaves a mike open, it will disrupt the meeting. Please no not unmute you mike or depend on "VOX" unless you are actively participating in the conversation. Open mikes will be silenced on our end, effectively removing you from the discussion. Thanks, --MM--

1 0

Re: What do you use interdomain routing for?
by nordlund＠databank.com 08 Sep '95

08 Sep '95

> >HI, > >We are looking at requirements for interdomain routing, and are >interested to know what you use it for. For instance, do you use >interdomain routing to select transit carriers for some traffic in >preference to other carriers. Neal What do you mean by "interdomain" routing? Is this inter ASN routing? Or is this OSPF Interarea routing? > >Are there policies that you would like to be able to implement that you are >unable to because of limitations in the available protocols? How much >would you be willing to slow down your forwarding rates in order to >have the capability? > >Please send me your answers and I'll summarize. > > --Neal > Dave Nordlund Dir of Technical Svcs Databank, Inc 913/842-6699 1473 Hwy 40 nordlund(a)databank.com Lawrence, KS 66044 "Your Key to the Internet

1 0

Fwd: You have been removed from the list
by MBYRON10＠aol.com 08 Sep '95

08 Sep '95

I don't understand I am receiving your post fine? The bounce must be someones misstake! Fwd-2 ______________________________________ Subj: PGP authentication for the RADB Date: Thu, Sep 7, 1995 12:53 PM EDT From: renaud(a)MERIT.EDU X-From: renaud(a)MERIT.EDU (Brian Renaud) Sender: renaud(a)MERIT.EDU Resent-from: nanog(a)MERIT.EDU Reply-to: renaud(a)MERIT.EDU To: nanog(a)MERIT.EDU The RADB now supports authentication using PGP-based digital signatures. If you want to use this feature, there are three things you must do: * Register your public key with the RA. * Modify your maintainer object to reflect your use of digital signatures * Sign (via PGP) your RADB transactions. 1. Registering your public key with the RA. You must send your public key to the RA for inclusion onto our PGP keyring. Use the "pgp -kxa" command to generate a copy of your public key suitable for mailing, then mail the resultant file to db-admin(a)ra.net. For example: % pgp -kxa smith(a)ra.net pubkey ... % mail -s 'please register my public key' db-admin(a)ra.net < pubkey.asc You may use one of two methods of verification: * Fax a copy of a photographic identification (passport or drivers license) to: RADB public key verification +1 313 747 3185 please write your PGP fingerprint and email address on the fax * Attend an RA sponsored key signing session at NANOG or IETF. You will need to bring a copy of your public key with a PGP fingerprint and photo identification. (This will be verification via the identification you bring, rather than having two other people agree that you are who you say you are.) We will be holding a key signing at NANOG on Monday, September 11 at 5:00. If that time is not convenient, you can also accost RA team members at random and present them with with the appropriate information. 2. Modifications to the maintainer object There is a new authentication option for the maintainer object. The syntax for it is: auth: PGP-FROM {PGP User Id} For example, auth: PGP-FROM John Smith <smith(a)ra.net> 3. Signing your RADB transactions You will need to PGP-sign each transaction you send to auto-dbm(a)ra.net. Use the "pgp -sta" command to do this. For example: % pgp -sta -u smith(a)ra.net routes ... % mail -s 'route updates' auto-dbm(a)ra.net < routes.asc ----------------------- Headers -------------------------------- >From nanog-request(a)MERIT.EDU Thu Sep 7 12:54:50 1995 Return-Path: nanog-request(a)MERIT.EDU Received: from merit.edu (merit.edu [35.1.1.42]) by emin04.mail.aol.com (8.6.12/8.6.12) with ESMTP id MAA03037 for <MBYRON10(a)aol.com>; Thu, 7 Sep 1995 12:54:37 -0400 Received: (from slist@localhost) by merit.edu (8.6.12/merit-2.0) id LAA03917; Thu, 7 Sep 1995 11:52:35 -0400 Resent-Date: Thu, 7 Sep 1995 11:52:35 -0400 Message-Id: <199509071552.LAA21225(a)home.merit.edu> From: Brian Renaud <renaud(a)MERIT.EDU> To: nanog(a)MERIT.EDU Subject: PGP authentication for the RADB Reply-To: renaud(a)MERIT.EDU Date: Thu, 07 Sep 1995 11:52:31 -0400 Sender: renaud(a)MERIT.EDU Resent-Message-ID: <"obcC1.0.5z.2LnJm"@merit.edu> Resent-From: nanog(a)MERIT.EDU X-Mailing-List: <nanog(a)MERIT.EDU> archive/latest/24 X-Loop: nanog(a)MERIT.EDU Precedence: list Resent-Sender: nanog-request(a)MERIT.EDU --------------------- Forwarded message: From: nanog-request(a)MERIT.EDU To: MBYRON10(a)aol.com Date: 95-09-07 12:38:12 EDT Your mail address MBYRON10(a)aol.com has been removed from the nanog(a)MERIT.EDU mailinglist. It generated an excessive amount of bounced mails. Before sending in a subscription request to nanog-request(a)MERIT.EDU again, please ensure that this problem has been resolved. When in doubt, ask your system administrator or send mail to "postmaster". The last one of those bounced mails has been quoted below: >From MAILER-DAEMON Thu Sep 7 12:10:01 1995 >Received: from localhost (localhost) by merit.edu (8.6.12/merit-2.0) with internal id MAA03450; Thu, 7 Sep 1995 12:10:01 -0400 >Date: Thu, 7 Sep 1995 12:10:01 -0400 >From: Mail Delivery Subsystem <MAILER-DAEMON> >Subject: Returned mail: User unknown >Message-Id: <199509071610.MAA03450(a)merit.edu> >To: nanog-request(a)MERIT.EDU > >The original message was received at Thu, 7 Sep 1995 11:42:00 -0400 >from slist@localhost > > ----- The following addresses had delivery problems ----- >tom(a)news1.mnsinc.com (unrecoverable error) > > ----- Transcript of session follows ----- >edm(a)nwnexus.wa.com... Deferred: Connection timed out during initial connection with nwnexus.wa.com. >... while talking to zippy.cais.net.: >>>> RCPT To:<tom(a)zippy.cais.net> ><<< 550 <tom(a)zippy.cais.net>... User unknown >550 tom(a)news1.mnsinc.com... User unknown >noah(a)gxl.woodtech.com... Deferred: Connection timed out during initial connection with gxl.woodtech.com. >451 bob@databank.com,nordlund@databank.com... reply: read error from exodus.databank.com. >451 NEAL_CASTAGNOLI@novell.com,RHADDOCK@novell.com... timeout waiting for input during client greeting >451 NEAL_CASTAGNOLI@novell.com,RHADDOCK@novell.com... reply: read error from umx-hub.novell.com. >NEAL_CASTAGNOLI@novell.com,RHADDOCK@novell.com... Deferred: Connection timed out during initial connection with ums-hub.novell.com. >451 MBYRON10(a)aol.com... reply: read error from mail05.mail.aol.com. >MBYRON10(a)aol.com... Deferred: Connection reset by peer during client greeting with mail05.mail.aol.com. > > ----- Message header follows ----- >Return-Path: nanog-request(a)MERIT.EDU >Received: (from slist@localhost) by merit.edu (8.6.12/merit-2.0) id LAA03439; Thu, 7 Sep 1995 11:42:00 -0400 >Resent-Date: Thu, 7 Sep 1995 11:42:00 -0400 >Date: Thu, 7 Sep 95 11:35:17 -0400 >From: nrm1838(a)rserver3.dsac.dla.mil (James Cassell) >Message-Id: <9509071535.AA02406(a)rserver3.dsac.dla.mil> >X-Mailer: Ez-Mail v4.4 <Date: Thu, 07 Sep 95 11:41:31 nrm1838> >To: nanog(a)MERIT.EDU >Subject: Re: Pittsburgh directions >Old-Status: N >Resent-Message-ID: <"Rj0Gu.0.hr.7BnJm"@merit.edu> >Resent-From: nanog(a)MERIT.EDU >X-Mailing-List: <nanog(a)MERIT.EDU> archive/latest/23 >X-Loop: nanog(a)MERIT.EDU >Precedence: list >Resent-Sender: nanog-request(a)MERIT.EDU > > ----- Message body suppressed ----- >

1 0

What do you use interdomain routing for?
by Neal Castagnoli 07 Sep '95

07 Sep '95

HI, We are looking at requirements for interdomain routing, and are interested to know what you use it for. For instance, do you use interdomain routing to select transit carriers for some traffic in preference to other carriers. Are there policies that you would like to be able to implement that you are unable to because of limitations in the available protocols? How much would you be willing to slow down your forwarding rates in order to have the capability? Please send me your answers and I'll summarize. --Neal

1 0

PGP authentication for the RADB
by Brian Renaud 07 Sep '95

07 Sep '95

The RADB now supports authentication using PGP-based digital signatures. If you want to use this feature, there are three things you must do: * Register your public key with the RA. * Modify your maintainer object to reflect your use of digital signatures * Sign (via PGP) your RADB transactions. 1. Registering your public key with the RA. You must send your public key to the RA for inclusion onto our PGP keyring. Use the "pgp -kxa" command to generate a copy of your public key suitable for mailing, then mail the resultant file to db-admin(a)ra.net. For example: % pgp -kxa smith(a)ra.net pubkey ... % mail -s 'please register my public key' db-admin(a)ra.net < pubkey.asc You may use one of two methods of verification: * Fax a copy of a photographic identification (passport or drivers license) to: RADB public key verification +1 313 747 3185 please write your PGP fingerprint and email address on the fax * Attend an RA sponsored key signing session at NANOG or IETF. You will need to bring a copy of your public key with a PGP fingerprint and photo identification. (This will be verification via the identification you bring, rather than having two other people agree that you are who you say you are.) We will be holding a key signing at NANOG on Monday, September 11 at 5:00. If that time is not convenient, you can also accost RA team members at random and present them with with the appropriate information. 2. Modifications to the maintainer object There is a new authentication option for the maintainer object. The syntax for it is: auth: PGP-FROM {PGP User Id} For example, auth: PGP-FROM John Smith <smith(a)ra.net> 3. Signing your RADB transactions You will need to PGP-sign each transaction you send to auto-dbm(a)ra.net. Use the "pgp -sta" command to do this. For example: % pgp -sta -u smith(a)ra.net routes ... % mail -s 'route updates' auto-dbm(a)ra.net < routes.asc

1 0