RE: Merging RRP and Whois

Unfortunately, that didn't make as much sense as I thought it did...

What I was trying get at was the there are a number of RRP/EPP
implementations that are/will be exclusively private in nature. It *can* be
a public implementation, but currently, I know of none. Whois on the other
hand is mostly used in a public manner. There are private implementations,
but again, most are public. Anyways, my point is that merging the two will
lead to a point where one or the other must become more public or more
private in nature. In some of the implementations that we manage this would
be a good thing, in others, it would be a bad thing. I for one would prefer
to keep things a little bit simpler than what this arrangement implies....

<  -----Original Message-----
<  From: [email protected] [mailto:[email protected]]On
<  Behalf Of Ross Wm. Rader
<  Sent: Wednesday, January 24, 2001 2:50 PM
<  To: George Belotsky; Patrik Fältström; Paul George
<  Cc: [email protected]; [email protected]
<  Subject: RE: Merging RRP and Whois
<
<
<  Isn't the RRP (and therefore, won't the EPP likely be) a semi-private
<  protocol, whereas whois is inherently public in nature?
<
<  <  -----Original Message-----
<  <  From: [email protected]
<  <  [mailto:[email protected]]On Behalf Of George Belotsky
<  <  Sent: Wednesday, January 24, 2001 2:00 PM
<  <  To: Patrik Fältström; Paul George
<  <  Cc: [email protected]; [email protected]
<  <  Subject: Re: Merging RRP and Whois
<  <
<  <
<  <  It would not be necessary to run the new protocol on port 43.  The new
<  <  protocol, however, should become the standard for future Whois-type
<  <  queries.
<  <
<  <  Backwards compatibility with the current Whois should definitely be
<  <  maintained.  Fortunately, with the current Whois standard this is not
<  <  a problem.
<  <
<  <  The existing protocol on port 43 can remain as long as needed.  All
<  <  future extensions, however, should be to the new protocol.  In this
<  <  way, we would avoid forcing the development of incompatible and
<  <  diverging methods for accessing the same data.  We would also avoid
<  <  having to solve twice a large set set of very difficult problems, such
<  <  as authentication, security, privacy and internationalization.
<  <
<  <
<  <
<  <  On Wed, Jan 24, 2001 at 07:25:11PM +0100, Patrik Fältström wrote:
<  <  > At 12.37 -0500 01-01-24, George Belotsky wrote:
<  <  > >It would not take too much effort to simply use the Whois-like
<  <  > >features (perhaps with a little extension) of the RRP to
<  provide Whois
<  <  > >services to end users.
<  <  >
<  <  > I think this is a VERY interesting path that you should consider
<  <  > seriously! Including anonymous access, and ability for registrants
<  <  > (yes, registrants) to because of data protection laws
<  update whatever
<  <  > is necessary in the registry database in the case of a thick
<  <  > registry.  Also, this connection might be needed also for DNSSEC key
<  <  > signing issues...
<  <  >
<  <  > I.e. if you do a protocol, and need overlapping functions,
<  see if you
<  <  > should not do _one_...
<  <  >
<  <  > What goes on port 43 is a completely different story, and it should
<  <  > stay that way.
<  <  >
<  <  >    paf -- with my AD hat on as you can see in the signature
<  <  >
<  <  >
<  <  > --
<  <  > Patrik Fältström <[email protected]>       Internet Engineering
<  Task Force
<  <  > Area Director, Applications Area
http://www.ietf.org
<  > Phone: (Stockholm) +46-8-4494212            (San Jose) +1-408-525-0940
<  >         PGP: 2DFC AAF6 16F0 F276 7843  2DC1 BC79 51D9 7D25 B8DC
<
<  --
<  -----------------------------
<  George Belotsky
<  Senior Software Architect
<  Register.com, inc.
<  [email protected]
<  212-798-9127 (phone)
<  212-798-9876 (fax)