IRRd-Discuss

[Gerald Andrew Winters]

Diarmuid,

This is a bug and thanks for bringing it to our attention.  I will
post to the group when it is fixed.  Thanks.

--jerry

> 
> Gerald,
> 
> I have noticed that when I query for inet-rtr objects (e.g 198.32.136.78) on
> whois-rpsl.radb.net I do not get any route server information returned to me
> (attributes rs-in: and rs-out: ) . In fact I do not seem to be even getting
> an inet-rtr object returned to me. Has route server information been
> translated in to RPSL syntax? 
> 
> Diarmuid Flynn
> 
> -----Original Message-----
> From: Gerald Andrew Winters [mailto:gerald@merit.edu]
> Sent: Tuesday, August 24, 1999 7:58 PM
> To: irrd-discuss@merit.edu
> Cc: irrd-team@merit.edu
> Subject: RPSL test machine changes...
> 
> 
> 
> Sorry about the email glitch.  Let me try again with
> a more descriptive subject (RPSL expermimental machine changes).
> 
> > Hello,
> > 
> > Just a quick note.  Port 43 on whois-rpsl.radb.net
> > has been retired and replaced with by port 4443, 
> > the current RPSL test port.
> > 
> > This means very simply that the RPSL test port has been 
> > moved from port 4443 to 43 on the same machine, whois-rpsl.radb.net.
> > 
> > We have been getting a steady stream of comments and 
> > suggestions from RPSL testers and want to encourage others
> > to inpect their converted RIPE181 objects in source RADB-CONV
> > and to experiment by sending updates to auto-rpsl@radb.net.
> > Please remember, the complete conversion to RPSL will most occur 
> > likely by the end of October so time is running short.
> > 
> > --jerry
> > 
> > 
> > 
> > 
> 
>