[26185] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: RPSL announcement text

daemon@ATHENA.MIT.EDU (Alex P. Rudnev)
Wed Dec 8 16:04:57 1999

Date: Wed, 8 Dec 1999 23:36:32 +0300 (MSK)
From: "Alex P. Rudnev" <alex@virgin.relcom.eu.net>
To: Simon Lockhart <simonl@rd.bbc.co.uk>
Cc: Gerald Andrew Winters <gerald@merit.edu>, irrd-team@merit.edu,
	nanog@merit.edu
In-Reply-To: <27922.944684926@sunf25>
Message-ID: <Pine.SUN.4.10.9912082335160.4892-100000@virgin.relcom.eu.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu


I'v checked a more docs; may be I was wrong because 90% of this programs
requested whois data are not sesitive to the RIPE181-RPSL data change.

If so, sorry.

Alex.


On Wed, 8 Dec 1999, Simon Lockhart wrote:

> Date: Wed, 08 Dec 1999 20:28:46 +0000
> From: Simon Lockhart <simonl@rd.bbc.co.uk>
> To: Alex P. Rudnev <alex@virgin.relcom.eu.net>
> Cc: Gerald Andrew Winters <gerald@merit.edu>, irrd-team@merit.edu,
     nanog@merit.edu
> Subject: Re: RPSL announcement text 
> 
> >And so on. If some product is not 100% Y2K ready, it does not mean it can't work
> >in 2000 year. And vice versa, btw.
> >
> >may be, someone from nanog have some statistic showing how people are stopping
> >to use old ripe181 server and begin to use new one? If really a few use old
> >interface, I apologize.
> 
> More to the point, if there's such a Y2k problem with this 
> software/protocol/format, then why aren't RIPE (the original authors) 
> running around changing to RPSL?
> 
> Simon
> -- 
> Simon Lockhart                       |   Tel: +44 (0)1737 839676 
> Internet Engineering Manager         |   Fax: +44 (0)1737 839516 
> BBC Internet Services                | Email: Simon.Lockhart@bbc.co.uk 
> Kingswood Warren,Tadworth,Surrey,UK  |   URL: http://support.bbc.co.uk/
> 
> 
> 

Aleksei Roudnev,
(+1 415) 585-3489 /San Francisco CA/



home help back first fref pref prev next nref lref last post