From Ted.Hardie@nominum.com  Thu Jul 11 19:49:41 2002
From: Ted.Hardie@nominum.com (Ted Hardie)
Date: Thu, 11 Jul 2002 11:49:41 -0700
Subject: [Ietf-not43] Note taker?
Message-ID: <20020711114941.B53225@shell.nominum.com>

Is there anyone who would be willing to volunteer as a note taker for
our WG session in Yokohama?  I would personally appreciate it very
much,
		regards,
			Ted Hardie



From leifj@it.su.se  Thu Jul 18 01:47:39 2002
From: leifj@it.su.se (Leif Johansson)
Date: Thu, 18 Jul 2002 02:47:39 +0200
Subject: [Ietf-not43] background reading
Message-ID: <3D36102B.8040202@it.su.se>

I mentioned the NEEDS-project (not by name) at the wg meeting today. The 
NEEDS project
was funded by nordunet2 and can be seen as a cultural decendant to 
TISDAG mentioned by
Leslie. The aim of the project was to build an index-based (as in 
LDAP-referrals) whitepages
directory in the nordic countries. In NEEDS we spent some money on 
lawyers to figure out how
to "get around" the requirements placed on projects like NEEDS by EC 
privacy legislation.

Project URL: http://www.katalog.uninett.no/needs/

One of the deliverables, Privacy Aspects of the NEEDS project 
<http://www.katalog.uninett.no/needs/deliverables/Privacy_Aspects_of_the_NEEDS_project.pdf> 
might be useful reading when
thinking about privacy in the crisp requirements document.

The gist of this document is that one way to deal with privacy is to 
push the requirement on
user notification as far down the index structure as possible and create 
contracts between the
index operators and the indexed organisations where privacy req. are set 
down. That way the
index operators are protected from liability and the indexed org are 
stuck with dealing with
user notification which they have to do anyway.

Remember when reading the document that we had a real lawyer and a EC 
privacy expert
doing this.

How does this relate to protocol requirements? I don't know yet. Maybe 
it means that since there
is a way to solve the privacy issue you may not need protocol support. 
Maybe.

            MVH leifj


From bortzmeyer@nic.fr  Mon Jul 22 16:04:48 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Mon, 22 Jul 2002 17:04:48 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
Message-ID: <20020722150448.GA16795@nic.fr>

Since the list is very quiet and since I wasn't able to attend the
Yokohama meeting, a bit of opinion.

I did not see a mention of this information service:

http://www.adamsnames.tc/api/xmlrpc.html

in the mailing list archives.

A part of it, the domquery and may be conquery procedures, are
directly related to the work of this WG. Any opinion, any user? I'm
specially interested by the fact that it relies on a standard
protocol, for which there are many libraries already available. With
this API, I can write a "whois" client in a few minutes.




From anewton@verisignlabs.com  Mon Jul 22 16:30:57 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: 22 Jul 2002 11:30:57 -0400
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020722150448.GA16795@nic.fr>
References: <20020722150448.GA16795@nic.fr>
Message-ID: <1027351858.19047.45.camel@zedonthego.admin.cto.netsol.com>

At first glance, this appears to be more like the work being done in the
PROVREG WG than in this one.  Plus I think we are aiming to solve a
couple more problems?

I wonder why they didn't decide to use EPP?

-andy

On Mon, 2002-07-22 at 11:04, Stephane Bortzmeyer wrote:
> Since the list is very quiet and since I wasn't able to attend the
> Yokohama meeting, a bit of opinion.
> 
> I did not see a mention of this information service:
> 
> http://www.adamsnames.tc/api/xmlrpc.html
> 
> in the mailing list archives.
> 
> A part of it, the domquery and may be conquery procedures, are
> directly related to the work of this WG. Any opinion, any user? I'm
> specially interested by the fact that it relies on a standard
> protocol, for which there are many libraries already available. With
> this API, I can write a "whois" client in a few minutes.
> 
> 
> 
> _______________________________________________
> Ietf-not43 mailing list
> Ietf-not43@lists.verisignlabs.com
> http://lists.verisignlabs.com/mailman/listinfo/ietf-not43



From wessorh@ar.com  Mon Jul 22 17:02:55 2002
From: wessorh@ar.com (Rick Wesson)
Date: Mon, 22 Jul 2002 09:02:55 -0700 (PDT)
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <1027351858.19047.45.camel@zedonthego.admin.cto.netsol.com>
Message-ID: <Pine.LNX.4.33.0207220857580.25245-100000@flash.ar.com>


andy,

actually its not at all like the epp work in PROVREG, epp is a protocol
for registries to talk to registrars over, epp is not no has it ever been
used to talk to registrants. although they are all simular they each have
different requirements.

This thread does beg the question... has anyone identified reasons not to
pull from the structures defined in epp?

-rick



On 22 Jul 2002, Andrew Newton wrote:

> At first glance, this appears to be more like the work being done in the
> PROVREG WG than in this one.  Plus I think we are aiming to solve a
> couple more problems?
>
> I wonder why they didn't decide to use EPP?
>
> -andy
>
> On Mon, 2002-07-22 at 11:04, Stephane Bortzmeyer wrote:
> > Since the list is very quiet and since I wasn't able to attend the
> > Yokohama meeting, a bit of opinion.
> >
> > I did not see a mention of this information service:
> >
> > http://www.adamsnames.tc/api/xmlrpc.html
> >
> > in the mailing list archives.
> >
> > A part of it, the domquery and may be conquery procedures, are
> > directly related to the work of this WG. Any opinion, any user? I'm
> > specially interested by the fact that it relies on a standard
> > protocol, for which there are many libraries already available. With
> > this API, I can write a "whois" client in a few minutes.
> >
> >
> >
> > _______________________________________________
> > Ietf-not43 mailing list
> > Ietf-not43@lists.verisignlabs.com
> > http://lists.verisignlabs.com/mailman/listinfo/ietf-not43
>
>
> _______________________________________________
> Ietf-not43 mailing list
> Ietf-not43@lists.verisignlabs.com
> http://lists.verisignlabs.com/mailman/listinfo/ietf-not43
>


From patrick@gandi.net  Mon Jul 22 17:16:48 2002
From: patrick@gandi.net (Patrick)
Date: Mon, 22 Jul 2002 18:16:48 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <Pine.LNX.4.33.0207220857580.25245-100000@flash.ar.com>
References: <1027351858.19047.45.camel@zedonthego.admin.cto.netsol.com> <Pine.LNX.4.33.0207220857580.25245-100000@flash.ar.com>
Message-ID: <20020722161648.GL740@nohope.patoche.org>

On Mon, Jul 22, 2002 at 09:02:55AM -0700, Rick Wesson took time to write:
> actually its not at all like the epp work in PROVREG, epp is a protocol
> for registries to talk to registrars over, epp is not no has it ever been
> used to talk to registrants. although they are all simular they each have
> different requirements.

But close enough I think...

> This thread does beg the question... has anyone identified reasons not to
> pull from the structures defined in epp?

... so that we (Gandi) will work on providing access to data to some
of our customers using EPP. We will see what turns out.

After all, EPP stands for Extensible Provisioning Protocol 
so Registrant provisioning Objects should only be one extension as
another one ;-)

As for the reasons, I think it is probably historical, since EPP is
very young after all.
On http://www.adamsnames.tc/api/xmlrpc.html it's written:
Last Modified: Wed Apr 11 08:06:03 2001
at which time EPP was not so defined as it is now.

Otherwise I agree that this WG is far further than just XMLRPC or
EPP.

Patrick.

From anewton@verisignlabs.com  Mon Jul 22 18:44:58 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: 22 Jul 2002 13:44:58 -0400
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020722161648.GL740@nohope.patoche.org>
References: <1027351858.19047.45.camel@zedonthego.admin.cto.netsol.com>
 <Pine.LNX.4.33.0207220857580.25245-100000@flash.ar.com>
 <20020722161648.GL740@nohope.patoche.org>
Message-ID: <1027359899.19047.163.camel@zedonthego.admin.cto.netsol.com>

On Mon, 2002-07-22 at 12:16, Patrick wrote:
> On Mon, Jul 22, 2002 at 09:02:55AM -0700, Rick Wesson took time to write:
> > actually its not at all like the epp work in PROVREG, epp is a protocol
> > for registries to talk to registrars over, epp is not no has it ever been
> > used to talk to registrants. although they are all simular they each have
> > different requirements.
> 
> But close enough I think...
> 
[..snip..]
> 
> ... so that we (Gandi) will work on providing access to data to some
> of our customers using EPP. We will see what turns out.
> 
> After all, EPP stands for Extensible Provisioning Protocol 
> so Registrant provisioning Objects should only be one extension as
> another one ;-)

And perhaps this may have been what James Seng was talking about when he
gave his OPP presentation (though, he may have conceptualized a few more
nodes in his network graph than is needed for this particular use case).

-andy


From patrick@gandi.net  Mon Jul 22 19:20:27 2002
From: patrick@gandi.net (Patrick)
Date: Mon, 22 Jul 2002 20:20:27 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <1027359899.19047.163.camel@zedonthego.admin.cto.netsol.com>
References: <1027351858.19047.45.camel@zedonthego.admin.cto.netsol.com> <Pine.LNX.4.33.0207220857580.25245-100000@flash.ar.com> <20020722161648.GL740@nohope.patoche.org> <1027359899.19047.163.camel@zedonthego.admin.cto.netsol.com>
Message-ID: <20020722182027.GS740@nohope.patoche.org>

On Mon, Jul 22, 2002 at 01:44:58PM -0400, Andrew Newton took time to write:
> And perhaps this may have been what James Seng was talking about when he
> gave his OPP presentation (though, he may have conceptualized a few more
> nodes in his network graph than is needed for this particular use case).

Any link/reference for this presentation ?

Patrick.

From shollenbeck@verisign.com  Mon Jul 22 19:39:55 2002
From: shollenbeck@verisign.com (Hollenbeck, Scott)
Date: Mon, 22 Jul 2002 14:39:55 -0400
Subject: [Ietf-not43] XML-RPC for an information service?
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189BC8E@vsvapostal3.prod.netsol.com>

> -----Original Message-----
> From: Patrick [mailto:patrick@gandi.net]
> Sent: Monday, July 22, 2002 2:20 PM
> To: ietf-not43@lists.verisignlabs.com
> Subject: Re: [Ietf-not43] XML-RPC for an information service?
> 
> 
> On Mon, Jul 22, 2002 at 01:44:58PM -0400, Andrew Newton took 
> time to write:
> > And perhaps this may have been what James Seng was talking 
> about when he
> > gave his OPP presentation (though, he may have 
> conceptualized a few more
> > nodes in his network graph than is needed for this 
> particular use case).
> 
> Any link/reference for this presentation ?

James gave his presentation at the London (IETF-51) IETF meeting, described
here:

http://www.ietf.org/proceedings/01aug/51-28.htm#P3724_193588

I don't see a copy of his slides with the minutes, though.

-Scott-

From edlewis@arin.net  Mon Jul 22 19:46:42 2002
From: edlewis@arin.net (Edward Lewis)
Date: Mon, 22 Jul 2002 14:46:42 -0400
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020722182027.GS740@nohope.patoche.org>
References: <1027351858.19047.45.camel@zedonthego.admin.cto.netsol.com>
 <Pine.LNX.4.33.0207220857580.25245-100000@flash.ar.com>
 <20020722161648.GL740@nohope.patoche.org>
 <1027359899.19047.163.camel@zedonthego.admin.cto.netsol.com>
 <20020722182027.GS740@nohope.patoche.org>
Message-ID: <a05111b00b96202c1e8e9@[208.58.208.145]>

At 8:20 PM +0200 7/22/02, Patrick wrote:
>Any link/reference for this presentation ?

No...

 From http://www.ietf.org/proceedings/01aug/index.html:

2. OPP Presentation - James Sang
Slides unavailable.

Mark Nottingham - Did you use existing XML protocol rather than 
develop a new DTD?

JS - Other author needs to answer. MN -I'll bring it to the list

Dave Crocker - What within EPP does not meet the needs of China?

JS - EPP is a 2 entity protocol, does not support communications btwn 
other nodes (r'ant-r'ar, r'ar-r'ar, etc.). (Ask Dave.)

Eric Brunner-Williams - What kind of graph is OPP?

Rich Shockey - How will you maintain transactional intergrity btwn the nodes?

JS - Every request is signed by each node.

RS - Do you prefer any transport protocol?

JS - No we are transport agnostic.

Dave Crocker - Clarification

Jordyn Buchanan - Can't EPP meet your needs if we added the 
requirements for signatures btwn nodes?

Mark Nottingham Guy - Do you plan on using XML schema rather than new DTD

Dan Manly - How do you make sure proper security is in each node?

Rich Shockey - What application would require coordination btwn four nodes?

Jordyn Buchanan - R'ant need to authenticate with a r'y, discussed on 
the list and has been desire of some ccTLDs.

JS - Multiple tiered phone companies. Scott Hollenbeck response to 
JB, current EPP draft doesn't provide this capability, but there's o 
reason why it couldn't be updated or extension added.

EL - Should the WG accept the document?

Dave Crocker - Not good to have two protocol documents but we could 
try to address the needs met in the document by integrating it into 
EPP documents.

EL - It may be best for JS to get the document where he wants it 
before accepting it.

George Ballotsky - Process is too rushed to get a good protocol.

EL - We'll take the question to the list.

(Document has since been withdrawn from consideration.)


-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                          +1-703-227-9854
ARIN Research Engineer


From jbuchanan@register.com  Mon Jul 22 18:51:24 2002
From: jbuchanan@register.com (Jordyn Buchanan)
Date: Mon, 22 Jul 2002 13:51:24 -0400
Subject: [Ietf-not43] XML-RPC for an information service?
Message-ID: <500BCE6EFCD9E44D9D02B6483B0A759A09C3F322@cartman.register.com>

I believe the service was established prior to the existence of EPP.

-----Original Message-----
From: Andrew Newton [mailto:anewton@verisignlabs.com] 
Sent: Monday, July 22, 2002 11:31 AM
To: Stephane Bortzmeyer
Cc: ietf-not43@lists.verisignlabs.com
Subject: Re: [Ietf-not43] XML-RPC for an information service?


At first glance, this appears to be more like the work being done in the
PROVREG WG than in this one.  Plus I think we are aiming to solve a couple
more problems?

I wonder why they didn't decide to use EPP?

-andy

On Mon, 2002-07-22 at 11:04, Stephane Bortzmeyer wrote:
> Since the list is very quiet and since I wasn't able to attend the 
> Yokohama meeting, a bit of opinion.
> 
> I did not see a mention of this information service:
> 
> http://www.adamsnames.tc/api/xmlrpc.html
> 
> in the mailing list archives.
> 
> A part of it, the domquery and may be conquery procedures, are 
> directly related to the work of this WG. Any opinion, any user? I'm 
> specially interested by the fact that it relies on a standard 
> protocol, for which there are many libraries already available. With 
> this API, I can write a "whois" client in a few minutes.
> 
> 
> 
> _______________________________________________
> Ietf-not43 mailing list
> Ietf-not43@lists.verisignlabs.com 
> http://lists.verisignlabs.com/mailman/listinfo/ietf-not43


_______________________________________________
Ietf-not43 mailing list
Ietf-not43@lists.verisignlabs.com
http://lists.verisignlabs.com/mailman/listinfo/ietf-not43

From bortzmeyer@nic.fr  Tue Jul 23 13:34:36 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Tue, 23 Jul 2002 14:34:36 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <1027351858.19047.45.camel@zedonthego.admin.cto.netsol.com>
References: <20020722150448.GA16795@nic.fr> <1027351858.19047.45.camel@zedonthego.admin.cto.netsol.com>
Message-ID: <20020723123436.GA28078@nic.fr>

On Mon, Jul 22, 2002 at 11:30:57AM -0400,
 Andrew Newton <anewton@verisignlabs.com> wrote 
 a message of 31 lines which said:

> At first glance, this appears to be more like the work being done in the
> PROVREG WG than in this one.

Not at all. The XML-RPC interface of Adam's Names merges two tasks:
provisioning of objects (the conreg and domreg procedures) and
querying of objects (the domquery and conquery procedures). In this
WG, I was referring to the second one, which can be seen as a
competitor to IRIS.

> I wonder why they didn't decide to use EPP?

Besides the timing issue, there is the simple fact that one can
implement Adam's Names interface in one day, something that is far
from the huge complexity of EPP... (flames welcome but remember they
are off-topic in that WG).



From patrick@gandi.net  Tue Jul 23 14:55:04 2002
From: patrick@gandi.net (Patrick)
Date: Tue, 23 Jul 2002 15:55:04 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <3CD14E451751BD42BA48AAA50B07BAD60189BC8E@vsvapostal3.prod.netsol.com>
References: <3CD14E451751BD42BA48AAA50B07BAD60189BC8E@vsvapostal3.prod.netsol.com>
Message-ID: <20020723135504.GX740@nohope.patoche.org>

On Mon, Jul 22, 2002 at 02:39:55PM -0400, Hollenbeck, Scott took time to write:
> > On Mon, Jul 22, 2002 at 01:44:58PM -0400, Andrew Newton took 
> > time to write:
> > > And perhaps this may have been what James Seng was talking 
> > about when he
> > > gave his OPP presentation (though, he may have 
> > conceptualized a few more
> > > nodes in his network graph than is needed for this 
> > particular use case).
> > 
> > Any link/reference for this presentation ?
> 
> James gave his presentation at the London (IETF-51) IETF meeting, described
> here:
> 
> http://www.ietf.org/proceedings/01aug/51-28.htm#P3724_193588

Scott, and Edward, thanks for the information.

> I don't see a copy of his slides with the minutes, though.

I even found the expired draft on
http://www.potaroo.net/ietf/old-ids/draft-jseng-provreg-opp-00.txt

Patrick.

From anewton@verisignlabs.com  Tue Jul 23 16:21:04 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: 23 Jul 2002 11:21:04 -0400
Subject: [Ietf-not43] an IRIS over BEEP
Message-ID: <1027437664.4681.83.camel@zedonthego.admin.cto.netsol.com>

Though we are still hashing through the requirements and still
evaluating BOTH proposed approaches (and I guess others that might be
submitted), I have received private email concerning the use of HTTP
with IRIS and thought it proper to bring the issue up with the working
group.  In addition, I've had a few "senior" IETF'ers also mention the
over use of HTTP for such things.

The concern was over the following paragraph from
draft-newton-iris-http-00:

   Finally, precedents for using other transport mechanisms in layered
   applications do not seem to fit with the design goals of IRIS.
   BEEP[3], while a very complete application transport, offers many
   more features than would otherwise be used in the normal and
   expected uses of this application. Examples of such features are
   multiplexing connection behavior and peer-to-peer session
   negotiation. Conversely, the straight use of TCP such as that
   specified by [14] does not offer the client negotiation
   characteristics needed by a referral application where a single
   client, in the act of processing a query, may traverse multiple
   servers operating with different parameters.

The issue was specifically over the justification for not using BEEP. 
I'd like to know what others think about the HTTP vs. BEEP issue with
relation to IRIS and the work of this WG.  Perhaps a BEEP mapping would
be more justifiable?

Points to ponder:

1. As the private email pointed out, the multiplexing and peer-to-peer
mechanisms of BEEP can merely be turned off or refused by the
end-points.  Therefore, if they aren't desired, then they don't need to
be used.

2. As the private email also pointed out, BEEP gives you SASL, which is
worlds better than trying to shoe-horn something similar into HTTP.  Or
put more bluntly, clever attempts to rig HTTP with these features are
not viewed favorably.  This is a fairly valid point given the request
for the WG to consider draft-rescorla-auth-mech-00.txt while approaching
this problem.

3. Current port 43 operations are usually done in the very similar
stateless manner of HTTP. That is, the TCP session is established for
only a single query and response.  However, this doesn't mean it is
correct... many port 43 servers experience repeated connections that may
otherwise be conducted over a single session.  In addition, where
authorization is involved, the overhead of setup/teardown becomes more
expensive.

4. Looking at the EPP world, how many operators are using BEEP?  This
may be an indication that operators/implementers think it is too
complex.

Comments?

-andy


From shollenbeck@verisign.com  Tue Jul 23 17:08:46 2002
From: shollenbeck@verisign.com (Hollenbeck, Scott)
Date: Tue, 23 Jul 2002 12:08:46 -0400
Subject: [Ietf-not43] an IRIS over BEEP
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189BC9F@vsvapostal3.prod.netsol.com>

> 4. Looking at the EPP world, how many operators are using BEEP?  This
> may be an indication that operators/implementers think it is too
> complex.

I don't think anyone is using BEEP right now, but I may be wrong.  The early
discussions that went on in the provreg context focused mostly on two
things:

- the (perceived?) lack of mature BEEP software implementations, and

- operators have had a lot of experience with streaming over TCP, they
understand how it works, they have software that does it well, and they know
how to make it perform well.

I don't recall complexity being a significant issue.

-Scott-

From patrick@gandi.net  Tue Jul 23 17:19:51 2002
From: patrick@gandi.net (Patrick)
Date: Tue, 23 Jul 2002 18:19:51 +0200
Subject: [Ietf-not43] an IRIS over BEEP
In-Reply-To: <3CD14E451751BD42BA48AAA50B07BAD60189BC9F@vsvapostal3.prod.netsol.com>
References: <3CD14E451751BD42BA48AAA50B07BAD60189BC9F@vsvapostal3.prod.netsol.com>
Message-ID: <20020723161951.GC740@nohope.patoche.org>

On Tue, Jul 23, 2002 at 12:08:46PM -0400, Hollenbeck, Scott took time to write:
> > 4. Looking at the EPP world, how many operators are using BEEP?  This
> > may be an indication that operators/implementers think it is too
> > complex.
> 
> I don't think anyone is using BEEP right now, but I may be wrong.  The early

I have the same impression as Scott.
Basically as I understand things, Neulevel (.BIZ) tried to do so with
their XRP (which is basically EPP over BEEP over TLS), but went back
to pure EPP over TLS, at least for simplicity for now.

In November I spoke with their CTO I believe which explained to me
that internally they had a strong push forward by developers for
BEEP, and they still keep the idea for the long term. But to launch
quickly things forward they needed to start simpler.

> I don't recall complexity being a significant issue.

Not in the technical pure sense maybe, but on a broader sense
probably (for the arguments you list, not so many experiences right
now, and since EPP is also new...)

IIRC it took also a lot of time before seeing a draft about EPP over
BEEP. There was long discussions, but for a long time no draft. There
is now however.

Patrick.

From bortzmeyer@nic.fr  Wed Jul 24 11:46:15 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Wed, 24 Jul 2002 12:46:15 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020722150448.GA16795@nic.fr>
References: <20020722150448.GA16795@nic.fr>
Message-ID: <20020724104615.GA10249@nic.fr>

On Mon, Jul 22, 2002 at 05:04:48PM +0200,
 Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote 
 a message of 21 lines which said:

> http://www.adamsnames.tc/api/xmlrpc.html

And another example:

A new XML-RPC based service someone might be interested in:

DoWhois is an XML-RPC based whois client. It supports lookups for a
variety of different domain types as weel as IP addresses. It can also
handle 'thin' registries (such as com) where individual registrars
maintain their own whois servers.

One important feature is its ability to decode some whois results into
their constitunt parts, so names, addresses, nameservers, etc are easily
found and can be used by automated scripts.

The service can both be used from the main website plus can be
downloaded and installed on your own server.

Version 0.02alpha has just been released. For more info (and to try a
web based smaple client) from the website - http://www.DoWhois.com/


From anewton@verisignlabs.com  Wed Jul 24 15:40:52 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: 24 Jul 2002 10:40:52 -0400
Subject: [Ietf-not43] Domain Registrant
Message-ID: <1027521653.4716.103.camel@zedonthego.admin.cto.netsol.com>

As pointed out in Yokohama, the requirements document does not define a
domain registrant.  So are there any comments on adding the following
definition:

2.4.6 Domain Registrants
  Entities given authority over a domain via purchase, lease, or grant
from a domain registrar or domain registry are domain registrants. 
Domain registrants are considered a subset of both DNS Users (Section
2.4.5) and Intellectual Property Holders (Section 2.4.2).

-andy




From Ted.Hardie@nominum.com  Wed Jul 24 15:54:58 2002
From: Ted.Hardie@nominum.com (Ted Hardie)
Date: Wed, 24 Jul 2002 07:54:58 -0700
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020724104615.GA10249@nic.fr>; from bortzmeyer@nic.fr on Wed, Jul 24, 2002 at 12:46:15PM +0200
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr>
Message-ID: <20020724075458.B66611@shell.nominum.com>

Stephane,

Thanks for the pointer to DoWhois and to starting this conversation
on the list.  I am interested in the idea of XML-RPC, and I wonder
whether you are interested in writing a draft describing a CRISP
service using XML-RPC.  While we have not yet moved the requirements
document into the AD's queue, we are fairly far along on it and
it certainly can be used to begin parallel development of 
documents proposing specific solutions.

At the moment, we have one document proposing an LDAP-based solution
and one set of documents proposing IRIS (with a binding to HTTP).
Now is the time to put forward other proposals, and a draft specifying
how those proposals meet the requirements would be great.

			regards,
				Ted Hardie




On Wed, Jul 24, 2002 at 12:46:15PM +0200, Stephane Bortzmeyer wrote:
> On Mon, Jul 22, 2002 at 05:04:48PM +0200,
>  Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote 
>  a message of 21 lines which said:
> 
> > http://www.adamsnames.tc/api/xmlrpc.html
> 
> And another example:
> 
> A new XML-RPC based service someone might be interested in:
> 
> DoWhois is an XML-RPC based whois client. It supports lookups for a
> variety of different domain types as weel as IP addresses. It can also
> handle 'thin' registries (such as com) where individual registrars
> maintain their own whois servers.
> 
> One important feature is its ability to decode some whois results into
> their constitunt parts, so names, addresses, nameservers, etc are easily
> found and can be used by automated scripts.
> 
> The service can both be used from the main website plus can be
> downloaded and installed on your own server.
> 
> Version 0.02alpha has just been released. For more info (and to try a
> web based smaple client) from the website - http://www.DoWhois.com/
> 
> _______________________________________________
> Ietf-not43 mailing list
> Ietf-not43@lists.verisignlabs.com
> http://lists.verisignlabs.com/mailman/listinfo/ietf-not43

From anewton@verisignlabs.com  Wed Jul 24 16:47:31 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: 24 Jul 2002 11:47:31 -0400
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020724104615.GA10249@nic.fr>
References: <20020722150448.GA16795@nic.fr>  <20020724104615.GA10249@nic.fr>
Message-ID: <1027525651.4716.117.camel@zedonthego.admin.cto.netsol.com>

On Wed, 2002-07-24 at 06:46, Stephane Bortzmeyer wrote:
> And another example:
> 
> A new XML-RPC based service someone might be interested in:

What about other generic RPC mechanisms such as SOAP and/or CORBA/IIOP?

-andy


From leslie@thinkingcat.com  Wed Jul 24 17:02:54 2002
From: leslie@thinkingcat.com (Leslie Daigle)
Date: Wed, 24 Jul 2002 12:02:54 -0400
Subject: [Ietf-not43] pointers to TISDAG project
Message-ID: <3D3ECFAE.DC08E30@thinkingcat.com>

Howdy,

At the meeting last week, it was suggested that I forward some
references to the Swedish TISDAG project to the list.

By way of context -- the TISDAG project's goal was to provide
a single point of contact for searching for users' e-mail
addresses, while respecting the fact that the actual data
was stored in individual service provider/enterprise directories
(i.e., that were not going to be centralized any time soon).

Two key technical things to note about the TISDAG situation:

	1/ there wasn't the possibility (at the time) of 
	   assuming a single access protocol, so it was
	   necessary to do query and result mapping

	2/ it was about search -- that is, you couldn't
	   know in advance which server might be authoritative
	   for a given user  (if you want the e-mail address
	   for Leslie Daigle in Kista, that doesn't give you
	   a clue about what provider might have an e-mail
	   address for me).  This meant that it was critical
	   to have some kind of mechanism for intelligently
	   distributing the queries across the leaf servers
	   (in this case, an index or "hints" database that
	   provided references to likely targets)
	   
A lot of what we're discussing so far in CRISP leverages the 
structured nature of domain names (and IP allocations) so that 
the client has some ability to find authoritative servers by
location (not search through hints).  

So, the documents:  to follow up on the discussion in the WG
meeting, RFC2967 is about as far as you'll ever want to go. It
is the original tech spec for the project -- describing the 
requirements and architecture in more detail, as well as the 
actual components.   

The follow on discussion documents are only interesting if you really
get "into" the idea and want to see where we thought it might lead.
They are:
	RFC2968 -- discussion of mesh topologies
	RFC2969 -- practical experiences from implementation
	  (including surprises from various client software
	   implementations)
	RFC2970 -- an attempt to generalize the TISDAG 
	   architecture.  I would write it very differently
	   if I were writing it again today...

Leslie.

-- 

-------------------------------------------------------------------
"An essential element of a successful journey
    is recognizing when you have arrived."
   -- ThinkingCat

Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------

From bortzmeyer@nic.fr  Wed Jul 24 17:05:33 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Wed, 24 Jul 2002 18:05:33 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <1027525651.4716.117.camel@zedonthego.admin.cto.netsol.com>
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <1027525651.4716.117.camel@zedonthego.admin.cto.netsol.com>
Message-ID: <20020724160533.GA14255@nic.fr>

On Wed, Jul 24, 2002 at 11:47:31AM -0400,
 Andrew Newton <anewton@verisignlabs.com> wrote 
 a message of 8 lines which said:

> What about other generic RPC mechanisms such as SOAP and/or CORBA/IIOP?

Very good question. 

SOAP : still a moving target, quite complicated partly because of
featurism, interoperability problems.

Corba : not really in the same category. But I would say that it is
overkill when you have only two partners (a client and a server, like
in IR protocols).




From Ted.Hardie@nominum.com  Wed Jul 24 17:40:27 2002
From: Ted.Hardie@nominum.com (Ted Hardie)
Date: Wed, 24 Jul 2002 09:40:27 -0700
Subject: [Ietf-not43] draft minutes
Message-ID: <20020724094027.A68224@shell.nominum.com>

Hi,
	Below are draft minutes for the working group meeting in
Yokohama; many thanks to Ed Lewis for taking these and sending them
over so quickly.  I slowed the process a good bit, and my apologies
for that delay.  If you have revisions or additions, please send 
them to me or the list by Tuesday, July 30th.
			thanks,
				Ted Hardie





Minutes (draft) of CRISP WG meeting, July 17, 2002 in Yokohama
Chair: Ted Hardie
Minutes prepared by: Edward Lewis
Minutes edited by: Ted Hardie


Agenda:
     Review of the IESG-approved charter
     Review of the updated requirements draft
     Review of the ICANN whois Task Force draft document
     "Advertisement" for a draft on Authentication Mechanisms
         draft-rescorla-auth-mech-00.txt
     Review of two candidate proposals
         LDAP-based
         IRIS


Action Items:

1)   Andy Newton will resubmit his drafts as draft-ietf-crisp items
     so that they are tracked as working group drafts.  These will
     be updated to clarify the points raised during the working group
     meeting and on the list.  The requirements draft will be re-released
     first and the candidate proposals after.
   
2)   Leslie Daigle will send a pointer to the list on the TISDAG work.

3)   Ted Hardie will send a pointer to the Rescorla draft to the mailing
     list and start discussion of authentication mechanisms required by
     CRISP.


Meeting Review:

Charter discussion (WG chair Ted Hardie)
     (see the WG charter page for content)
     Scope has been reduced since the BoF held at Minneapolis
     Now limited to domain registries with extensibility to others a plus

     Question: "Why?"
     RIR's and IRR's are removed to allow for a narrower scope, hence
     higher probability of the WG accomplishing its goals

     Question: "Why do deliverables and milestones omit extensibility?"
     Extensibility is a facet of the proposed & to-be-worked solutions,
     degree of extensibility will be one metric used to judge goodness.

Review of requirements draft (Andy Newton)
     -01 reflect the new charter scope (not yet true for proposal docs)
     new registry types: Incident Coordination and Network Edge Resources(?)
     DNS users considered
     Functional reqts split into extensible base and specific domain items
     DNS Label Referencing (3.2.10) needs input from WG

     Question: "Why does doc exclude registrants?"
     They are just not explicitly mentioned, one reference is the DNS user.

Review of ICANN (DNSO) whois Task Force draft (Ted Hardie)
     http://www.dnso.org/ and http://www.dnso.org/dnso/notes/whoisTF/
     Questions 9-11 as input to process, requirements

     Comment: This document is open for a 4-week period for comments, as part
     of DNSO.  (See web page for details.) - Scott Hollenbeck

     Comment: European privacy laws will have an impact on CRISP (as written)
     - two folks, one whose name I missed and Jaap Akkerhius

     Comment: Requirements document should be altered to deal with privacy
     concerns. - Leslie Daigle

     Comment: TISDAG documents are helpful for understanding the problem to
     be solved here, and come from a European setting. - Also Leslie, and
     she has been asked to provide a list of relevant RFC's on TISDAG.

     Comment: Conclusions in the document did not exactly follow from the
     question presented (for question 10), from Andy

Advertisement for Auth Mech draft

     An individual submission from Eric Rescorla, "A Survey of Authentication
     Mechanisms" is recommended reading.

     http://search.ietf.org/internet-drafts/draft-rescorla-auth-mech-00.txt

     Not discussed further as there was no advanced notice given to the WG.

Candidate Proposals
     LDAP-based and IRIS
     Both doc( set)s are out of sync with new scope of charter and requirements.
     LDAP is a single, large draft
     IRIS is a set of smaller drafts (XML via HTTP)
     No further discussion as we need more background on requirements

Return to the Requriements Draft for discussion

     Question: How does authentication work in the requirements?
         Two separate issues
             Anonymous vs. identified access
             Data mining policy (3.1.1)
         Authentication query (3.1.8) - suggestion to drop section

     Question: Is this a read-write or read-only protocol?
         Read-only
         No desire to store requests on server (too complicated)
         Declare features in which a client would write (store) data on server
         as out of scope

         *** WG consensus needed on above point ***

     Question: Concerning search functions in 3.2.4 and 3.2.9, "reasonable
     subset" wording - Yoshiro Yoneya, JPNIC
         Discussion also covered ACE encoding & lookup issue, do not want to
         solve that problem in this group.
         Text about this topic solicited

     Question: Also on "reasonable" from NaoMASA Maruyama  (JPNIC)
         Resonable subset wording conflicts with data mining text (on the
         surface).
         Suggested rewording for 3.2.4 - "MUST support lookups on exact
         names and reasonable subset names, MAY/SHOULD provide limits to
         answers to alleviate performance, privacy, and/or data mining
         concerns.

     Question: Is there a requirement for hierarchical search?
         Base spec does not cover this.
         3.2.10 is closest to this topic.

     Question: Is there a requirement to allow for determination of the
         registry delegating a domain name?
         Needed feature, so folks asking for, say, ac.jp, know who to
         contact about domain name.  (DNS may have multi-label deep zones.)

Action items for Andy
     New requirements draft (with the updates discussed in meeting and a
     switch to draft-ietf-crisp-... name) is due about a week after the
     minuted are submitted.  Revised candidates assumed to appear sometime
     later.





From wessorh@ar.com  Wed Jul 24 18:09:00 2002
From: wessorh@ar.com (Rick Wesson)
Date: Wed, 24 Jul 2002 10:09:00 -0700 (PDT)
Subject: [Ietf-not43] draft minutes
In-Reply-To: <20020724094027.A68224@shell.nominum.com>
Message-ID: <Pine.LNX.4.33.0207241004230.11391-100000@flash.ar.com>


On Wed, 24 Jul 2002, Ted Hardie wrote:

> Hi,
> 	Below are draft minutes for the working group meeting in
> Yokohama; many thanks to Ed Lewis for taking these and sending them

> Charter discussion (WG chair Ted Hardie)
>      (see the WG charter page for content)
>      Scope has been reduced since the BoF held at Minneapolis
>      Now limited to domain registries with extensibility to others a plus
>
>      Question: "Why?"
>      RIR's and IRR's are removed to allow for a narrower scope, hence
>      higher probability of the WG accomplishing its goals
>


two points.. one of procedure, why are decisions being made at the meeting
and not on the list? If the RIRs and the IRRs want out of CRISP then the
name registries and registrars may want out too. To play fair the topic
needs to be discussed and consensus determined on the list.

secondly, without the RIRs and the IRRs the protocol does not improve ones
ability to navigate the heiracy of names and number delegations and as
such I believe CRISP should either solve the problem of all registries or
not exist.

I would like to understand how these decisions got made and why we all
were not consulted in the matter.

thanks,

-rick



From leslie@thinkingcat.com  Wed Jul 24 18:30:22 2002
From: leslie@thinkingcat.com (Leslie Daigle)
Date: Wed, 24 Jul 2002 13:30:22 -0400
Subject: [Ietf-not43] draft minutes
References: <Pine.LNX.4.33.0207241004230.11391-100000@flash.ar.com>
Message-ID: <3D3EE42E.BADAF54C@thinkingcat.com>

Rick,

This is so not news... 

First, it wasn't decided at the meeting in Yokohama -- as
a result of the LAST meeting (i.e., Minneapolis), it was
_proposed_ to the list (see, e.g., Ted's note to this list
on April 25):

> Subject: 
>         [Ietf-not43] Proposed charter
>    Date: 
>         Thu, 25 Apr 2002 15:24:59 -0700
>    From: 
>         Ted Hardie <Ted.Hardie@nominum.com>
>     To: 
>         ietf-not43@lists.research.netsol.com
> 
> 
> 
> 
> Howdy,
>         Based on the discussions we've had since the last IETF, I
> believe that the scope of the CRISP work has been narrowed to a focus
> on DNS-related registries, registrars, and registrants.  Though I
> believe that there is value from a user perspective for a more general
> approach, I believe that deployment of such services is unlikely among
> other infrastructure registries using similar administrative directory
> services.  Given that, I have put together the following straw
> charter, which is narrower in focus than those discussed at previous
> BoF sessions.  Comments to the list are welcome.
>                                 regards,
>                                         Ted Hardie


Leslie.


Rick Wesson wrote:
> 
> On Wed, 24 Jul 2002, Ted Hardie wrote:
> 
> > Hi,
> >       Below are draft minutes for the working group meeting in
> > Yokohama; many thanks to Ed Lewis for taking these and sending them
> 
> > Charter discussion (WG chair Ted Hardie)
> >      (see the WG charter page for content)
> >      Scope has been reduced since the BoF held at Minneapolis
> >      Now limited to domain registries with extensibility to others a plus
> >
> >      Question: "Why?"
> >      RIR's and IRR's are removed to allow for a narrower scope, hence
> >      higher probability of the WG accomplishing its goals
> >
> 
> two points.. one of procedure, why are decisions being made at the meeting
> and not on the list? If the RIRs and the IRRs want out of CRISP then the
> name registries and registrars may want out too. To play fair the topic
> needs to be discussed and consensus determined on the list.
> 
> secondly, without the RIRs and the IRRs the protocol does not improve ones
> ability to navigate the heiracy of names and number delegations and as
> such I believe CRISP should either solve the problem of all registries or
> not exist.
> 
> I would like to understand how these decisions got made and why we all
> were not consulted in the matter.
> 
> thanks,
> 
> -rick
> 
> _______________________________________________
> Ietf-not43 mailing list
> Ietf-not43@lists.verisignlabs.com
> http://lists.verisignlabs.com/mailman/listinfo/ietf-not43

-- 

-------------------------------------------------------------------
"An essential element of a successful journey
    is recognizing when you have arrived."
   -- ThinkingCat

Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------

From Ted.Hardie@nominum.com  Wed Jul 24 18:38:34 2002
From: Ted.Hardie@nominum.com (Ted Hardie)
Date: Wed, 24 Jul 2002 10:38:34 -0700
Subject: [Ietf-not43] draft minutes
In-Reply-To: <Pine.LNX.4.33.0207241004230.11391-100000@flash.ar.com>; from wessorh@ar.com on Wed, Jul 24, 2002 at 10:09:00AM -0700
References: <20020724094027.A68224@shell.nominum.com> <Pine.LNX.4.33.0207241004230.11391-100000@flash.ar.com>
Message-ID: <20020724103834.A69443@shell.nominum.com>

On Wed, Jul 24, 2002 at 10:09:00AM -0700, Rick Wesson wrote:
> two points.. one of procedure, why are decisions being made at the meeting
> and not on the list? If the RIRs and the IRRs want out of CRISP then the
> name registries and registrars may want out too. To play fair the topic
> needs to be discussed and consensus determined on the list.

This actually points to a clarification required in the minutes,
as this wasn't a decision reached in the meeting, it was a decision
by the IESG reviewed in the meeting.  The initial agenda for
the IETF listed the meeting as a BoF and the transition to working
group occured fairly close to the actual meeting.  I reviewed
the current charter and compared it to the charter proposed at
the last BoF as an aid to those who might be attending the meeting
anticipating a continuation of the previous BoF.

The charter reviewed was the same as the one posted to the list
and to the ietf-announce and new work mailing lists.  


> secondly, without the RIRs and the IRRs the protocol does not improve ones
> ability to navigate the heiracy of names and number delegations and as
> such I believe CRISP should either solve the problem of all registries or
> not exist.

While I certainly sympathize with that view, the IESG felt that a more
restricted initial charter was appropriate.  They did feel that
extensibility or applicability to other domains could be design
criteria, but that the work items of the group should be focused on
the domain name space.  The first draft of that more restricted charter
was first posted to the list back in late April (see message id
20020425152459.A67618@shell.nominum.com in the archive at
https://lists.verisignlabs.com/pipermail/ietf-not43/2002-April.txt,
and the discussion on it which followed into the May archives).

> I would like to understand how these decisions got made and why we all
> were not consulted in the matter.

I appreciate your concern for process, but I believe this discussion
did occur according to the appropriate procceses.  After the BoF,
the IESG felt a more narrowly scoped effort was appropriate; a draft
charter on that basis was posted and discussed on the working group
mailing list, and a revision of that charter based on those discussions
was posted for review on ietf-announce and new-work.  

If you continue to have concerns on the process, I would be happy to
discuss it with you as, I am sure, would the ADs.

			regards,
				Ted Hardie




From wessorh@ar.com  Wed Jul 24 18:51:53 2002
From: wessorh@ar.com (Rick Wesson)
Date: Wed, 24 Jul 2002 10:51:53 -0700 (PDT)
Subject: [Ietf-not43] draft minutes
In-Reply-To: <20020724103834.A69443@shell.nominum.com>
Message-ID: <Pine.LNX.4.33.0207241048040.11391-100000@flash.ar.com>

>
> If you continue to have concerns on the process, I would be happy to
> discuss it with you as, I am sure, would the ADs.

yes, I do and I would like to discuss it with the ADs; The parties to this
wg have not been consulted and may not want to participate w/o the IRR and
RIR registries.

If this wg's work is re-scoped to just include name registries and
registrars I have a big probelem and I'd like to discuss it with the IESG



-rick (with his CTO of the ICANN Registrars hat on)




From Ted.Hardie@nominum.com  Wed Jul 24 21:27:43 2002
From: Ted.Hardie@nominum.com (Ted Hardie)
Date: Wed, 24 Jul 2002 13:27:43 -0700
Subject: [Ietf-not43] draft minutes
In-Reply-To: <Pine.LNX.4.33.0207241048040.11391-100000@flash.ar.com>; from wessorh@ar.com on Wed, Jul 24, 2002 at 10:51:53AM -0700
References: <20020724103834.A69443@shell.nominum.com> <Pine.LNX.4.33.0207241048040.11391-100000@flash.ar.com>
Message-ID: <20020724132743.C69443@shell.nominum.com>

On Wed, Jul 24, 2002 at 10:51:53AM -0700, Rick Wesson wrote:
> yes, I do and I would like to discuss it with the ADs; The parties to this
> wg have not been consulted and may not want to participate w/o the IRR and
> RIR registries.

Patrik is the relevant AD; if you'd like me to be  involved,
please feel free to cc: me on your messages.  


> 
> If this wg's work is re-scoped to just include name registries and
> registrars I have a big probelem and I'd like to discuss it with the IESG
> 
> 
> 
> -rick (with his CTO of the ICANN Registrars hat on)

As a process point, I remind you that IETF participants speak (or
at least, are heard) as individuals.  
			regards,
				Ted Hardie



From jaap@sidn.nl  Thu Jul 25 09:31:47 2002
From: jaap@sidn.nl (Jaap Akkerhuis)
Date: Thu, 25 Jul 2002 10:31:47 +0200
Subject: [Ietf-not43] Domain Registrant
In-Reply-To: Your message of 24 Jul 2002 10:40:52 -0400.
 <1027521653.4716.103.camel@zedonthego.admin.cto.netsol.com>
Message-ID: <200207250831.g6P8Vl5d020477@bartok.sidn.nl>

    As pointed out in Yokohama, the requirements document does not define a
    domain registrant.  So are there any comments on adding the following
    definition:
    
    2.4.6 Domain Registrants
      Entities given authority over a domain via purchase, lease, or grant
    from a domain registrar or domain registry are domain registrants. 
    Domain registrants are considered a subset of both DNS Users (Section
    2.4.5) and Intellectual Property Holders (Section 2.4.2).
    
I'm not a lowyer, but from the first sentence of this definition
one might conclude conclude that when a registrar is involved, the
authority ver a domain is first passed to a regsitrar and then to
the domain name holder. As far as I know, this is not the case.

To offer some wording:

    2.4.6 Domain Registrants
    Entities given authority over a domain via purchase, lease, or grant
    from a domain registry.  

The way how the registrants gets the authority is not important, although one
might to add: This authority is given either directly or via a registrar.

The second sentence is not needed.

	jaap

From patrick@gandi.net  Thu Jul 25 13:24:21 2002
From: patrick@gandi.net (Patrick)
Date: Thu, 25 Jul 2002 14:24:21 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020724104615.GA10249@nic.fr>
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr>
Message-ID: <20020725122421.GS740@nohope.patoche.org>

On Wed, Jul 24, 2002 at 12:46:15PM +0200, Stephane Bortzmeyer took time to write:
> > http://www.adamsnames.tc/api/xmlrpc.html
> 
> And another example:
> 
> A new XML-RPC based service someone might be interested in:

[..]

> Version 0.02alpha has just been released. For more info (and to try a
> web based smaple client) from the website - http://www.DoWhois.com/

FYI, Gandi::WhoisExtract [1] does the same thing, except the parse is not
so generic (but that could be easily achieved), and it does not use
XML-RPC (whish should also be very easy to use). 
However it correctly parses around 80 (IIRC) Registrars under
.com/.net/.org (which does not seem to be the case of dowhois)
It is production quality code and really used. Available under a BSD
licence. Done in Perl OO.

However I really think that this WG has a far bigger aim than parsing
whois and stuff like that.
XML-RPC can be an idea as for the transport, but other than that...

Patrick.

[1] http://open.gandi.net/

From ehall@ehsco.com  Thu Jul 25 18:39:33 2002
From: ehall@ehsco.com (Eric A. Hall)
Date: Thu, 25 Jul 2002 12:39:33 -0500
Subject: [Ietf-not43] draft minutes
References: <Pine.LNX.4.33.0207241004230.11391-100000@flash.ar.com>
Message-ID: <3D4037D5.3010606@ehsco.com>

[sorry for the late response]

on 7/24/2002 12:09 PM Rick Wesson wrote:
>
> On Wed, 24 Jul 2002, Ted Hardie wrote: two points.. one of procedure,
> why are decisions being made at the meeting and not on the list?

The decision to limit scope to domain names was made before the WG charter
was submitted. As I understand it, this was a requirement passed down from
the IESG.

This doesn't mean that we have to ignore those parties. Towards this
point, as part of restructuring my proposal, I am going to provide
expiremental-track IDs for IPv4, IPv6, ASN and user schemas and protocols.

> secondly, without the RIRs and the IRRs the protocol does not improve
> ones ability to navigate the heiracy of names and number delegations
> and as such I believe CRISP should either solve the problem of all
> registries or not exist.

Personally, I think it is useful to limit our responsibility (and thus,
our culpability) to a single target area. If we get the core and the first
layer (domain names) right, adding more profiles should be simple. Yes, we
have to keep those other uses in mind in order to avoid designing
something that doesn't work with those other profiles (see the extra IDs
comment above), but this in fact no more of a risk than trying to define
six different standards. We could get four of them wrong in either
scenario. Focusing the standards-track effort on the core and domain names
specifications makes some sense.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/


From anewton@verisignlabs.com  Fri Jul 26 05:40:56 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: Thu, 25 Jul 2002 21:40:56 -0700
Subject: [Ietf-not43] Domain Registrant
References: <200207250831.g6P8Vl5d020477@bartok.sidn.nl>
Message-ID: <3D40D2D8.7080200@verisignlabs.com>

Jaap Akkerhuis wrote:
> 
> To offer some wording:
> 
>     2.4.6 Domain Registrants
>     Entities given authority over a domain via purchase, lease, or grant
>     from a domain registry.  

How about?

2.4.6 Domain Registrant
   Entities given authority over a domain via purchase, lease, or grant 
from a domain registry, either directly or via the services of a domain 
registrar.

-andy


From wessorh@ar.com  Fri Jul 26 06:18:36 2002
From: wessorh@ar.com (Rick Wesson)
Date: Thu, 25 Jul 2002 22:18:36 -0700 (PDT)
Subject: [Ietf-not43] Domain Registrant
In-Reply-To: <3D40D2D8.7080200@verisignlabs.com>
Message-ID: <Pine.LNX.4.33.0207252218070.11391-100000@flash.ar.com>

to me more accurate:

  Domain Registrant
    Entities given authority over a domain.

-rick


On Thu, 25 Jul 2002, Andrew Newton wrote:

> Jaap Akkerhuis wrote:
> >
> > To offer some wording:
> >
> >     2.4.6 Domain Registrants
> >     Entities given authority over a domain via purchase, lease, or grant
> >     from a domain registry.
>
> How about?
>
> 2.4.6 Domain Registrant
>    Entities given authority over a domain via purchase, lease, or grant
> from a domain registry, either directly or via the services of a domain
> registrar.
>
> -andy
>
> _______________________________________________
> Ietf-not43 mailing list
> Ietf-not43@lists.verisignlabs.com
> http://lists.verisignlabs.com/mailman/listinfo/ietf-not43
>


From jaap@sidn.nl  Fri Jul 26 10:04:41 2002
From: jaap@sidn.nl (Jaap Akkerhuis)
Date: Fri, 26 Jul 2002 11:04:41 +0200
Subject: [Ietf-not43] Domain Registrant
In-Reply-To: Your message of Thu, 25 Jul 2002 21:40:56 -0700.
 <3D40D2D8.7080200@verisignlabs.com>
Message-ID: <200207260904.g6Q94f5d025108@bartok.sidn.nl>

    Jaap Akkerhuis wrote:
    > 
    > To offer some wording:
    > 
    >     2.4.6 Domain Registrants
    >     Entities given authority over a domain via purchase, lease, or grant
    >     from a domain registry.  
    
    How about?
    
    2.4.6 Domain Registrant
       Entities given authority over a domain via purchase, lease, or grant 
    from a domain registry, either directly or via the services of a domain 
    registrar.
    
I'm not sure why you want to have the actual process of how to get
a domain in the definition, but this looks fine.

	jaap
    

From bortzmeyer@nic.fr  Fri Jul 26 10:53:10 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Fri, 26 Jul 2002 11:53:10 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020724075458.B66611@shell.nominum.com>
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <20020724075458.B66611@shell.nominum.com>
Message-ID: <20020726095310.GA30275@nic.fr>

--x+6KMIRAuhnl3hBn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Jul 24, 2002 at 07:54:58AM -0700,
 Ted Hardie <Ted.Hardie@nominum.com> wrote 
 a message of 51 lines which said:

> whether you are interested in writing a draft describing a CRISP
> service using XML-RPC. 

Ask and thou shall receive. The draft is here, I'll provide a sample
implementation soon (anyone has one for IRIS, BTW?).

Feel free to comments, flame, suggest, etc. But do remember that my
draft does not follow exactly the same ideas as IRIS: IRIS is more
open, IRPI is less flexible, in order to be ready faster.

> Now is the time to put forward other proposals, and a draft specifying
> how those proposals meet the requirements would be great.

Nice idea, but the requirments specify both things to be done at the
protocol level and things to be done only at the implementation level
(such as rate-limiting functions).







--x+6KMIRAuhnl3hBn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="draft-bortzmeyer-irpi.txt"



Network Working Group                                      S. Bortzmeyer
Internet-Draft                                                     AFNIC
Expires: January 24, 2003                                  July 26, 2002


                 Internet Registry Procedural Interface
                         draft-bortzmeyer-irpi

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at http://
   www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on January 24, 2003.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   DRAFT OF DRAFT - DO NOT USE YET

   This document describes a procedural interface to query the database
   of an Internet Registry, for instance the various contacts for a
   domain.

   It is specified as an API for the XML-RPC protocol.

   It is intended to be simple and easy to implement.  It is not a full
   solution to a complicated problem, but a way to get rid of whois more
   rapidly.




Bortzmeyer              Expires January 24, 2003                [Page 1]

Internet-Draft    Internet Registry Procedural Interface       July 2002


1. Introduction

   The specification outlined in this document is based on the
   functional requirements described in the Internet Registry Directory
   requirments [5].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC2119 [9].

1.1 General view

   IRPI is specified as an Application Programming Interface of XML-RPC
   [1].  XML-RPC is a way to call remote procedures, here we assume that
   the RPC callee will be on a Registry machine and that the caller
   wants to access information in the Registry.

   XML-RPC provides a way to marshall parameters, send them over HTTP ,
   retrieve the results and unmarshall them.  The results can be
   structured.  They can also be a fault, i.e.  an exception.  The rest
   of this document will assume familiarity with XML-RPC.

1.2 Transport

   XML-RPC specifies only one transport, HTTP.  But it should be
   straightforward to make IRPI run over other non-standard transports
   like Jabber [8].

1.3 Objects

   IRPI has a fixed set of objects, unlike, for instance, IRIS [6].
   This is to make it simpler and easier to implement fast.  A general-
   purpose Internet directory is out of scope.


















Bortzmeyer              Expires January 24, 2003                [Page 2]

Internet-Draft    Internet Registry Procedural Interface       July 2002


2. The API

2.1 General rules for the server

   The server MUST implement the introspection API [7].

   The server MUST reacts gracefully (sending a fault) to calls of
   unknown methods.

   The server MUST accepts XML-RPC structs with unknown members (in
   order to extend the protocol in the future) and SHOULD ignore them.
   It MUST accepts XML-RPC arrays with more elements than expected and
   SHOULD ignore them.

2.2 General rules for the client

   The client SHOULD use the introspection API [7] before trying
   methods.

   The client MUST accepts XML-RPC structs with unknown members (in
   order to extend the protocol in the future) and SHOULD ignore them.
   It MUST accepts XML-RPC arrays with more elements than expected and
   SHOULD ignore them.

2.3 Credentials

   Credentials are always transmitted as XML-RPC structs.  If they are
   empty (no members), it means the client has no credential to present.
   If they are non-empty, credentials always have the member "name" (a
   string) and they also have the possible members (at least one must be
   present):

      password: a plain password

      signature: TODO.  Sign what, a concatenation of the parameters,
      and how, X509 or OpenPGP?

   If non-empty credentials are presented, they MUST be checked.

   TODO: describe how the server may use the underlying authentication
   (X509 client certificate if https).  The server may also use other
   underlying information (such as the client's IP address) before
   deciding to send data or not.

   When the reply includes several named members, the server MAY choose
   to omit some for privacy reasons, depending on the client.  The
   client MUST reacts gracefully to such missing members.  TODO: a way
   for the client to discover if the information exists? Not sure it



Bortzmeyer              Expires January 24, 2003                [Page 3]

Internet-Draft    Internet Registry Procedural Interface       July 2002


   would not help the stalker.

2.4 Exceptions

   Every procedure may return faults (raise exceptions).  XML-RPC [1]
   does not define standard faults so we specify these (as faultCode and
   explanation, you may choose a different faultString):

      TODO: should we specify the fault for an nonexisting method?

      400: Badly formed request

      403: Access forbidden

      404: No such object


2.5 Mandatory procedures

   All the mandatory procedures are prefixed by 'registry.'.  Adding new
   procedures whould be done with the prefix 'registry-local.', in order
   to avoid name clashes.

      queryDomain (name <string>, credentials <struct>) returns
      <struct>.  The struct has the following members (remember that
      some may be missing, either for privacy reasons or because this
      information has no meaning for a given registry):

         name <string>

         status <string> TODO: define statuses, using the enumerated
         values of EPP domain mapping [3]?

         registered <dateTime.iso8601>

         modified <dateTime.iso8601>

         expires <dateTime.iso8601>

         holder <string> TODO: name it registrant because EPP and IRIS
         call it that way?

         technical_c <string>

         administrative_c <string>

         billing_c <string>




Bortzmeyer              Expires January 24, 2003                [Page 4]

Internet-Draft    Internet Registry Procedural Interface       July 2002


         comments <string>

         TODO: maintainer like in RIPE-NCC registry?

         nameservers <array> This array is made of two-members structs,
         each struct has two strings, "name" and "address" (the second
         may be missing if the registry does not keep that information
         for a given nameserver).

      queryContact (handle <string>, credentials <struct>) returns
      <struct>.  The returned struct has the following members (remember
      that some may be missing, either for privacy reasons or because
      this information has is not kept by a given registry):

         handle <string>

         registered <dateTime.iso8601>

         modified <dateTime.iso8601>

         status <string> TODO: define statuses, using the enumerated
         values of EPP contact mapping [4]?

         address <struct> This struct is made of:

            street <string> TODO: several strings?

            city <string>

            country <string>

            email <string>

            phone <string>

            fax <string>

            zipcode <string>

         TODO: maintainer like in RIPE-NCC registry?

      queryHost (info <struct>, credentials <struct>) returns <struct>.
      The input struct has one member, either "name" when you indicate
      the name of the host or "ipaddress" when you indicate its address.
      The returned struct has the following members:

         name <string>




Bortzmeyer              Expires January 24, 2003                [Page 5]

Internet-Draft    Internet Registry Procedural Interface       July 2002


         ipaddress <string>, may be missing if the registry does not
         keep it.  TODO: and if several addresses?


2.6 Optional procedures

   All the optional procedures are prefixed by 'registry.'.  Adding new
   procedures whould be done with the prefix 'registry-local.', in order
   to avoid name clashes.

      queryObject, query an obect without specifying the type.  TODO:
      describe the API

      queryIPaddress, query an IP address, for a RIR or an IRR, although
      it is outside of the scope of our requirments [5].

      search, fuzzy search, with regexps or things like that.  TODO:
      very dangerous for privacy.


2.7 Extending the API

   You can extend the above API in several ways:

      A registry can add new procedures, prefixed by 'registry-local.'.

      A registry can add new fields to structs passed or returned.
      These fields SHOULD be prefixed by 'x-'.

   Other extensions (such as adding parameters to procedures) are
   prohibited.




















Bortzmeyer              Expires January 24, 2003                [Page 6]

Internet-Draft    Internet Registry Procedural Interface       July 2002


3. Internationalization Considerations

   Contact information, such as names and addresses may be stored in
   Unicode and sent back in whatever encoding the caller or the callee
   chose.  The general rules of XML apply: UTF-8 and UTF-16 encoding
   MUST be supported by the parties.  Other encodings SHOULD NOT be used
   unless there is a serious reason to believe they are supported by the
   other party (XML-RPC does not allow encoding negociation).

   IDN domain names MUST be in ACE encoded form.  It is up to the client
   to translate.








































Bortzmeyer              Expires January 24, 2003                [Page 7]

Internet-Draft    Internet Registry Procedural Interface       July 2002


4. Security considerations

   There are many privacy and authentication considerations at various
   places of that document.  Apart from authentication, IRPI completely
   resides on the layers below for its security against passive
   eavesdropping or session replay.  The security model in XML-RPC
   defers all the security to the transport layer.  So you should use
   HTTPS and not HTTP is security is a concern.  See also the
   requirments [5] for a general discussion of security of an Internet
   Registry Directory.









































Bortzmeyer              Expires January 24, 2003                [Page 8]

Internet-Draft    Internet Registry Procedural Interface       July 2002


References

   [1]  UserLand Software, "The XML-RPC protocol", November 2001,
        <http://www.xml-rpc.com/>.

   [2]  AdamsNames, "AdamsNames XMLRPC API", April 2001, <http://
        www.adamsnames.tc/api/xmlrpc.html>.

   [3]  Hollenbeck, S., "Extensible Provisioning Protocol Domain
        Mapping", draft-ietf-provreg-epp-domain-04 (work in progress),
        January 2002.

   [4]  Hollenbeck, S., "Extensible Provisioning Protocol Contact
        Mapping", draft-ietf-provreg-epp-contact-04 (work in progress),
        January 2002.

   [5]  Newton, A., "Internet Registry Directory Requirements", draft-
        newton-ir-dir-requirments-00 (work in progress), June 2002.

   [6]  Newton, A., "Internet Registry Information Service", draft-
        newton-iris-00 (work in progress), February 2002.

   [7]  Dumbill, Edd., "XML-RPC introspection API", Unknown Unknown,
        <http://xmlrpc.usefulinc.com/doc/reserved.html>.

   [8]  Adams, DJ., "Jabber RPC", September 2001, <http://
        www.pipetree.com/jabber/jrpc/>.

   [9]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", RFC 2119, March 1997.


Author's Address

   Stephane Bortzmeyer
   AFNIC
   Immeuble International
   Saint-Quentin en Yvelines cedex  78181
   France

   Phone: +33 1 39 30 83 46
   EMail: bortzmeyer@nic.fr









Bortzmeyer              Expires January 24, 2003                [Page 9]

Internet-Draft    Internet Registry Procedural Interface       July 2002


Full Copyright Statement

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Bortzmeyer              Expires January 24, 2003               [Page 10]


--x+6KMIRAuhnl3hBn--

From davidb@verisignlabs.com  Fri Jul 26 16:24:29 2002
From: davidb@verisignlabs.com (David Blacka)
Date: Fri, 26 Jul 2002 11:24:29 -0400
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020726095310.GA30275@nic.fr> (Stephane Bortzmeyer's message
 of "Fri, 26 Jul 2002 11:53:10 +0200")
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr>
 <20020724075458.B66611@shell.nominum.com>
 <20020726095310.GA30275@nic.fr>
Message-ID: <ko7kji342a.fsf@pinion.admin.cto.netsol.com>

>>>>> "Stephane" == Stephane Bortzmeyer <bortzmeyer@nic.fr> writes:

 >> whether you are interested in writing a draft describing a CRISP
 >> service using XML-RPC. 

 Stephane> Ask and thou shall receive. The draft is here, I'll provide
 Stephane> a sample implementation soon (anyone has one for IRIS,
 Stephane> BTW?).

Actually, I have a sample IRIS implementation (at least for the domain
registry portion).  I'm not sure when I will be able to make it
generally available though.

-- 
David Blacka    <davidb@verisignlabs.com> 
Sr. Engineer    Verisign Applied Research

From leslie@thinkingcat.com  Fri Jul 26 18:28:12 2002
From: leslie@thinkingcat.com (Leslie Daigle)
Date: Fri, 26 Jul 2002 13:28:12 -0400
Subject: [Ietf-not43] XML-RPC for an information service?
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr>
 <20020724075458.B66611@shell.nominum.com> <20020726095310.GA30275@nic.fr>
Message-ID: <3D4186AC.BFEC8A7E@thinkingcat.com>

Howdy,

So, the draft looks like a reasonable rough draft of an xml-rpc
based approach to querying a single whois server.  (Rough because
the "todo" count is 13... :-)

But there are a number of basic requirements (for the protocol
and data structure -- not just implementation) that this does
not address.  Heck, look at the first bullet item of this
group's charter:

> The CRISP service definition will define: 
> 
> o a standard mechanism that can be used to determine the 
> authoritative server(s) for information about a given label 

What you are proposing seems based on the assumption that you know
what server you are going to connect to, and then defining some
queries you might make against it.  That's the easy part of what
CRISP is trying to do.  CRISP is tasked with defining a _service_
that will work across the individual servers managed by 
registries, such that a client starting with some label (e.g.
a dns name) can find the authoritative server and make the
relevant query.  For example, the domain name SERVICE is 
not just about the packet format for making dns queries; it's
also about having a well-known, universally-supported mechanism
for navigating the tree of servers to find authoritative information.

There may well be an xml-rpc based approach to solve the CRISP
problem, and perhaps it would be better than iris or ldap-whois.  
But until I'm a little more convinced you understand what problem
this group is solving, I, at least, am not going to spend my time
reading more of your (nice, but not relevant) proposals.

Leslie.


Stephane Bortzmeyer wrote:
> 
> On Wed, Jul 24, 2002 at 07:54:58AM -0700,
>  Ted Hardie <Ted.Hardie@nominum.com> wrote
>  a message of 51 lines which said:
> 
> > whether you are interested in writing a draft describing a CRISP
> > service using XML-RPC.
> 
> Ask and thou shall receive. The draft is here, I'll provide a sample
> implementation soon (anyone has one for IRIS, BTW?).
> 
> Feel free to comments, flame, suggest, etc. But do remember that my
> draft does not follow exactly the same ideas as IRIS: IRIS is more
> open, IRPI is less flexible, in order to be ready faster.
> 
> > Now is the time to put forward other proposals, and a draft specifying
> > how those proposals meet the requirements would be great.
> 
> Nice idea, but the requirments specify both things to be done at the
> protocol level and things to be done only at the implementation level
> (such as rate-limiting functions).
> 
>   ------------------------------------------------------------------------
> 
>    Part 1.2    Type: Plain Text (text/plain)
>            Encoding: 7bit

-- 

-------------------------------------------------------------------
"An essential element of a successful journey
    is recognizing when you have arrived."
       -- ThinkingCat

Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------

From anewton@verisignlabs.com  Fri Jul 26 18:51:34 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: Fri, 26 Jul 2002 13:51:34 -0400
Subject: [Ietf-not43] Domain Registrant
References: <200207260904.g6Q94f5d025108@bartok.sidn.nl>
Message-ID: <3D418C26.4080303@verisignlabs.com>

Jaap Akkerhuis wrote:
>     
>     2.4.6 Domain Registrant
>        Entities given authority over a domain via purchase, lease, or grant 
>     from a domain registry, either directly or via the services of a domain 
>     registrar.
>     
> I'm not sure why you want to have the actual process of how to get
> a domain in the definition, but this looks fine.

To answer your question (though we seemed to have reached agreement), 
I'm trying to make it clear what we are talking about without getting 
too involved in a narative of the process.  Simply saying "control over 
a domain" and leaving it at that (to answer Rick's question) is to also 
include domain registries, which are given control over a TLD.  And that 
isn't what we are talking about.

-andy


From anewton@verisignlabs.com  Fri Jul 26 19:27:23 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: Fri, 26 Jul 2002 14:27:23 -0400
Subject: [Ietf-not43] XML-RPC for an information service?
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <1027525651.4716.117.camel@zedonthego.admin.cto.netsol.com> <20020724160533.GA14255@nic.fr>
Message-ID: <3D41948B.1000601@verisignlabs.com>

Stephane Bortzmeyer wrote:
> 
>>What about other generic RPC mechanisms such as SOAP and/or CORBA/IIOP?
> 
> SOAP : still a moving target, quite complicated partly because of
> featurism, interoperability problems.

Actually, I disagree with this.  There are many, many pieces of software 
that can use SOAP.  Perhaps a good comparison between the XML-RPC and 
SOAP would be good.  I think I would be more supportive of a SOAP standard.

> Corba : not really in the same category. But I would say that it is
> overkill when you have only two partners (a client and a server, like
> in IR protocols).

What!? I disagree with this, but considering nobody is considering 
specifying this via CORBA, let's drop this subject.


However, I do think there is a significant difference between something 
like IRIS (and also EPP) and just using a generic RPC mechanism like 
XML-RPC, SOAP, CORBA, DCE, etc...  IRIS defines ways of talking about 
different registry types, not just different registry instances.  This 
can be modeled within SOAP or whatever, but the use of a generic RPC 
mechanism gives you enough rope to hang yourself.  It also does not 
allow the finer grain of control that is sometimes desirable.  And in 
this instance, it can easily slide into functions clearly outside the 
charter of this group, such as registryDomain( domainName ).

As for the speed it takes to implement a client that can simply query a 
server for domain information, I think the LDAP-WHOIS proposal has this 
pretty much zipped up.  It can be done in about 5 seconds using the 
'ldapsearch' command.

-andy


From wessorh@ar.com  Fri Jul 26 20:57:19 2002
From: wessorh@ar.com (Rick Wesson)
Date: Fri, 26 Jul 2002 12:57:19 -0700 (PDT)
Subject: [Ietf-not43] Domain Registrant
In-Reply-To: <3D418C26.4080303@verisignlabs.com>
Message-ID: <Pine.LNX.4.33.0207261255320.6399-100000@flash.ar.com>


On Fri, 26 Jul 2002, Andrew Newton wrote:

> Jaap Akkerhuis wrote:
> >
> >     2.4.6 Domain Registrant
> >        Entities given authority over a domain via purchase, lease, or grant
> >     from a domain registry, either directly or via the services of a domain
> >     registrar.
> >
> > I'm not sure why you want to have the actual process of how to get
> > a domain in the definition, but this looks fine.
>
> To answer your question (though we seemed to have reached agreement),
> I'm trying to make it clear what we are talking about without getting
> too involved in a narative of the process.  Simply saying "control over
> a domain" and leaving it at that (to answer Rick's question) is to also
> include domain registries, which are given control over a TLD.  And that
> isn't what we are talking about.
>

and a registry is not given authority over a domain (tld) via grant? the
issue is confusing and maybe we should ask our selves whey we are
attempting to define this entity so that it fits within the context of a
registry/registrar relationship.

-rick



From Ted.Hardie@nominum.com  Fri Jul 26 22:03:06 2002
From: Ted.Hardie@nominum.com (Ted Hardie)
Date: Fri, 26 Jul 2002 14:03:06 -0700
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020726095310.GA30275@nic.fr>; from bortzmeyer@nic.fr on Fri, Jul 26, 2002 at 11:53:10AM +0200
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <20020724075458.B66611@shell.nominum.com> <20020726095310.GA30275@nic.fr>
Message-ID: <20020726140306.C20134@shell.nominum.com>

On Fri, Jul 26, 2002 at 11:53:10AM +0200, Stephane Bortzmeyer wrote:
> Ask and thou shall receive. The draft is here, I'll provide a sample
> implementation soon (anyone has one for IRIS, BTW?).

Thanks for putting together a draft; I'll review it in detail as
soon as I can, as, I am sure, will other members of the list.


> Feel free to comments, flame, suggest, etc. But do remember that my
> draft does not follow exactly the same ideas as IRIS: IRIS is more
> open, IRPI is less flexible, in order to be ready faster.
> 
> > Now is the time to put forward other proposals, and a draft specifying
> > how those proposals meet the requirements would be great.
> 
> Nice idea, but the requirments specify both things to be done at the
> protocol level and things to be done only at the implementation level
> (such as rate-limiting functions).
> 

Hmm. If it does suggest something at the implementation level it's a
doc bug.  The draft is meant to describe how the *service* should work
and that includes both on-the-wire and off the wire details.
Implementation details (like "use this Java package" or "use XML
namepsaces" or even "avoid buffer overuns") don't belong there.
If you see things in there that reach into implementation, please
note them to the list, so we can disucss removing them.
				thanks,
					Ted Hardie


> 
> 
> 

> 
> 
> Network Working Group                                      S. Bortzmeyer
> Internet-Draft                                                     AFNIC
> Expires: January 24, 2003                                  July 26, 2002
> 
> 
>                  Internet Registry Procedural Interface
>                          draft-bortzmeyer-irpi
> 
> Status of this Memo
> 
>    This document is an Internet-Draft and is in full conformance with
>    all provisions of Section 10 of RFC2026.
> 
>    Internet-Drafts are working documents of the Internet Engineering
>    Task Force (IETF), its areas, and its working groups.  Note that
>    other groups may also distribute working documents as Internet-
>    Drafts.
> 
>    Internet-Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
> 
>    The list of current Internet-Drafts can be accessed at http://
>    www.ietf.org/ietf/1id-abstracts.txt.
> 
>    The list of Internet-Draft Shadow Directories can be accessed at
>    http://www.ietf.org/shadow.html.
> 
>    This Internet-Draft will expire on January 24, 2003.
> 
> Copyright Notice
> 
>    Copyright (C) The Internet Society (2002).  All Rights Reserved.
> 
> Abstract
> 
>    DRAFT OF DRAFT - DO NOT USE YET
> 
>    This document describes a procedural interface to query the database
>    of an Internet Registry, for instance the various contacts for a
>    domain.
> 
>    It is specified as an API for the XML-RPC protocol.
> 
>    It is intended to be simple and easy to implement.  It is not a full
>    solution to a complicated problem, but a way to get rid of whois more
>    rapidly.
> 
> 
> 
> 
> Bortzmeyer              Expires January 24, 2003                [Page 1]
> 
> Internet-Draft    Internet Registry Procedural Interface       July 2002
> 
> 
> 1. Introduction
> 
>    The specification outlined in this document is based on the
>    functional requirements described in the Internet Registry Directory
>    requirments [5].
> 
>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>    document are to be interpreted as described in RFC2119 [9].
> 
> 1.1 General view
> 
>    IRPI is specified as an Application Programming Interface of XML-RPC
>    [1].  XML-RPC is a way to call remote procedures, here we assume that
>    the RPC callee will be on a Registry machine and that the caller
>    wants to access information in the Registry.
> 
>    XML-RPC provides a way to marshall parameters, send them over HTTP ,
>    retrieve the results and unmarshall them.  The results can be
>    structured.  They can also be a fault, i.e.  an exception.  The rest
>    of this document will assume familiarity with XML-RPC.
> 
> 1.2 Transport
> 
>    XML-RPC specifies only one transport, HTTP.  But it should be
>    straightforward to make IRPI run over other non-standard transports
>    like Jabber [8].
> 
> 1.3 Objects
> 
>    IRPI has a fixed set of objects, unlike, for instance, IRIS [6].
>    This is to make it simpler and easier to implement fast.  A general-
>    purpose Internet directory is out of scope.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Bortzmeyer              Expires January 24, 2003                [Page 2]
> 
> Internet-Draft    Internet Registry Procedural Interface       July 2002
> 
> 
> 2. The API
> 
> 2.1 General rules for the server
> 
>    The server MUST implement the introspection API [7].
> 
>    The server MUST reacts gracefully (sending a fault) to calls of
>    unknown methods.
> 
>    The server MUST accepts XML-RPC structs with unknown members (in
>    order to extend the protocol in the future) and SHOULD ignore them.
>    It MUST accepts XML-RPC arrays with more elements than expected and
>    SHOULD ignore them.
> 
> 2.2 General rules for the client
> 
>    The client SHOULD use the introspection API [7] before trying
>    methods.
> 
>    The client MUST accepts XML-RPC structs with unknown members (in
>    order to extend the protocol in the future) and SHOULD ignore them.
>    It MUST accepts XML-RPC arrays with more elements than expected and
>    SHOULD ignore them.
> 
> 2.3 Credentials
> 
>    Credentials are always transmitted as XML-RPC structs.  If they are
>    empty (no members), it means the client has no credential to present.
>    If they are non-empty, credentials always have the member "name" (a
>    string) and they also have the possible members (at least one must be
>    present):
> 
>       password: a plain password
> 
>       signature: TODO.  Sign what, a concatenation of the parameters,
>       and how, X509 or OpenPGP?
> 
>    If non-empty credentials are presented, they MUST be checked.
> 
>    TODO: describe how the server may use the underlying authentication
>    (X509 client certificate if https).  The server may also use other
>    underlying information (such as the client's IP address) before
>    deciding to send data or not.
> 
>    When the reply includes several named members, the server MAY choose
>    to omit some for privacy reasons, depending on the client.  The
>    client MUST reacts gracefully to such missing members.  TODO: a way
>    for the client to discover if the information exists? Not sure it
> 
> 
> 
> Bortzmeyer              Expires January 24, 2003                [Page 3]
> 
> Internet-Draft    Internet Registry Procedural Interface       July 2002
> 
> 
>    would not help the stalker.
> 
> 2.4 Exceptions
> 
>    Every procedure may return faults (raise exceptions).  XML-RPC [1]
>    does not define standard faults so we specify these (as faultCode and
>    explanation, you may choose a different faultString):
> 
>       TODO: should we specify the fault for an nonexisting method?
> 
>       400: Badly formed request
> 
>       403: Access forbidden
> 
>       404: No such object
> 
> 
> 2.5 Mandatory procedures
> 
>    All the mandatory procedures are prefixed by 'registry.'.  Adding new
>    procedures whould be done with the prefix 'registry-local.', in order
>    to avoid name clashes.
> 
>       queryDomain (name <string>, credentials <struct>) returns
>       <struct>.  The struct has the following members (remember that
>       some may be missing, either for privacy reasons or because this
>       information has no meaning for a given registry):
> 
>          name <string>
> 
>          status <string> TODO: define statuses, using the enumerated
>          values of EPP domain mapping [3]?
> 
>          registered <dateTime.iso8601>
> 
>          modified <dateTime.iso8601>
> 
>          expires <dateTime.iso8601>
> 
>          holder <string> TODO: name it registrant because EPP and IRIS
>          call it that way?
> 
>          technical_c <string>
> 
>          administrative_c <string>
> 
>          billing_c <string>
> 
> 
> 
> 
> Bortzmeyer              Expires January 24, 2003                [Page 4]
> 
> Internet-Draft    Internet Registry Procedural Interface       July 2002
> 
> 
>          comments <string>
> 
>          TODO: maintainer like in RIPE-NCC registry?
> 
>          nameservers <array> This array is made of two-members structs,
>          each struct has two strings, "name" and "address" (the second
>          may be missing if the registry does not keep that information
>          for a given nameserver).
> 
>       queryContact (handle <string>, credentials <struct>) returns
>       <struct>.  The returned struct has the following members (remember
>       that some may be missing, either for privacy reasons or because
>       this information has is not kept by a given registry):
> 
>          handle <string>
> 
>          registered <dateTime.iso8601>
> 
>          modified <dateTime.iso8601>
> 
>          status <string> TODO: define statuses, using the enumerated
>          values of EPP contact mapping [4]?
> 
>          address <struct> This struct is made of:
> 
>             street <string> TODO: several strings?
> 
>             city <string>
> 
>             country <string>
> 
>             email <string>
> 
>             phone <string>
> 
>             fax <string>
> 
>             zipcode <string>
> 
>          TODO: maintainer like in RIPE-NCC registry?
> 
>       queryHost (info <struct>, credentials <struct>) returns <struct>.
>       The input struct has one member, either "name" when you indicate
>       the name of the host or "ipaddress" when you indicate its address.
>       The returned struct has the following members:
> 
>          name <string>
> 
> 
> 
> 
> Bortzmeyer              Expires January 24, 2003                [Page 5]
> 
> Internet-Draft    Internet Registry Procedural Interface       July 2002
> 
> 
>          ipaddress <string>, may be missing if the registry does not
>          keep it.  TODO: and if several addresses?
> 
> 
> 2.6 Optional procedures
> 
>    All the optional procedures are prefixed by 'registry.'.  Adding new
>    procedures whould be done with the prefix 'registry-local.', in order
>    to avoid name clashes.
> 
>       queryObject, query an obect without specifying the type.  TODO:
>       describe the API
> 
>       queryIPaddress, query an IP address, for a RIR or an IRR, although
>       it is outside of the scope of our requirments [5].
> 
>       search, fuzzy search, with regexps or things like that.  TODO:
>       very dangerous for privacy.
> 
> 
> 2.7 Extending the API
> 
>    You can extend the above API in several ways:
> 
>       A registry can add new procedures, prefixed by 'registry-local.'.
> 
>       A registry can add new fields to structs passed or returned.
>       These fields SHOULD be prefixed by 'x-'.
> 
>    Other extensions (such as adding parameters to procedures) are
>    prohibited.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Bortzmeyer              Expires January 24, 2003                [Page 6]
> 
> Internet-Draft    Internet Registry Procedural Interface       July 2002
> 
> 
> 3. Internationalization Considerations
> 
>    Contact information, such as names and addresses may be stored in
>    Unicode and sent back in whatever encoding the caller or the callee
>    chose.  The general rules of XML apply: UTF-8 and UTF-16 encoding
>    MUST be supported by the parties.  Other encodings SHOULD NOT be used
>    unless there is a serious reason to believe they are supported by the
>    other party (XML-RPC does not allow encoding negociation).
> 
>    IDN domain names MUST be in ACE encoded form.  It is up to the client
>    to translate.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Bortzmeyer              Expires January 24, 2003                [Page 7]
> 
> Internet-Draft    Internet Registry Procedural Interface       July 2002
> 
> 
> 4. Security considerations
> 
>    There are many privacy and authentication considerations at various
>    places of that document.  Apart from authentication, IRPI completely
>    resides on the layers below for its security against passive
>    eavesdropping or session replay.  The security model in XML-RPC
>    defers all the security to the transport layer.  So you should use
>    HTTPS and not HTTP is security is a concern.  See also the
>    requirments [5] for a general discussion of security of an Internet
>    Registry Directory.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Bortzmeyer              Expires January 24, 2003                [Page 8]
> 
> Internet-Draft    Internet Registry Procedural Interface       July 2002
> 
> 
> References
> 
>    [1]  UserLand Software, "The XML-RPC protocol", November 2001,
>         <http://www.xml-rpc.com/>.
> 
>    [2]  AdamsNames, "AdamsNames XMLRPC API", April 2001, <http://
>         www.adamsnames.tc/api/xmlrpc.html>.
> 
>    [3]  Hollenbeck, S., "Extensible Provisioning Protocol Domain
>         Mapping", draft-ietf-provreg-epp-domain-04 (work in progress),
>         January 2002.
> 
>    [4]  Hollenbeck, S., "Extensible Provisioning Protocol Contact
>         Mapping", draft-ietf-provreg-epp-contact-04 (work in progress),
>         January 2002.
> 
>    [5]  Newton, A., "Internet Registry Directory Requirements", draft-
>         newton-ir-dir-requirments-00 (work in progress), June 2002.
> 
>    [6]  Newton, A., "Internet Registry Information Service", draft-
>         newton-iris-00 (work in progress), February 2002.
> 
>    [7]  Dumbill, Edd., "XML-RPC introspection API", Unknown Unknown,
>         <http://xmlrpc.usefulinc.com/doc/reserved.html>.
> 
>    [8]  Adams, DJ., "Jabber RPC", September 2001, <http://
>         www.pipetree.com/jabber/jrpc/>.
> 
>    [9]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
>         Levels", RFC 2119, March 1997.
> 
> 
> Author's Address
> 
>    Stephane Bortzmeyer
>    AFNIC
>    Immeuble International
>    Saint-Quentin en Yvelines cedex  78181
>    France
> 
>    Phone: +33 1 39 30 83 46
>    EMail: bortzmeyer@nic.fr
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Bortzmeyer              Expires January 24, 2003                [Page 9]
> 
> Internet-Draft    Internet Registry Procedural Interface       July 2002
> 
> 
> Full Copyright Statement
> 
>    Copyright (C) The Internet Society (2002).  All Rights Reserved.
> 
>    This document and translations of it may be copied and furnished to
>    others, and derivative works that comment on or otherwise explain it
>    or assist in its implementation may be prepared, copied, published
>    and distributed, in whole or in part, without restriction of any
>    kind, provided that the above copyright notice and this paragraph are
>    included on all such copies and derivative works.  However, this
>    document itself may not be modified in any way, such as by removing
>    the copyright notice or references to the Internet Society or other
>    Internet organizations, except as needed for the purpose of
>    developing Internet standards in which case the procedures for
>    copyrights defined in the Internet Standards process must be
>    followed, or as required to translate it into languages other than
>    English.
> 
>    The limited permissions granted above are perpetual and will not be
>    revoked by the Internet Society or its successors or assigns.
> 
>    This document and the information contained herein is provided on an
>    "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
>    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
>    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
>    HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
>    MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
> 
> Acknowledgement
> 
>    Funding for the RFC Editor function is currently provided by the
>    Internet Society.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Bortzmeyer              Expires January 24, 2003               [Page 10]
> 


From Ted.Hardie@nominum.com  Fri Jul 26 22:39:50 2002
From: Ted.Hardie@nominum.com (Ted Hardie)
Date: Fri, 26 Jul 2002 14:39:50 -0700
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <3D4186AC.BFEC8A7E@thinkingcat.com>; from leslie@thinkingcat.com on Fri, Jul 26, 2002 at 01:28:12PM -0400
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <20020724075458.B66611@shell.nominum.com> <20020726095310.GA30275@nic.fr> <3D4186AC.BFEC8A7E@thinkingcat.com>
Message-ID: <20020726143950.D20134@shell.nominum.com>

On Fri, Jul 26, 2002 at 01:28:12PM -0400, Leslie Daigle wrote:
> Howdy,
> 
> So, the draft looks like a reasonable rough draft of an xml-rpc
> based approach to querying a single whois server.  (Rough because
> the "todo" count is 13... :-)
> 
> But there are a number of basic requirements (for the protocol
> and data structure -- not just implementation) that this does
> not address.  Heck, look at the first bullet item of this
> group's charter:

Note that one of the current proposals is described in multiple
documents.  One of the things I like about this is that it is easy to
bite off chunks of the problem for discussion.  Another thing I like
about it is it lets you see if a new proposal for one element can be
fit into a structure already described.  The answer may well be no,
but I see nothing wrong with proposing a solution to one chunk of the
problem, *provided we as a group can go on to look it in the context
of the whole solution*.  That may mean looking at how this fits
into other solutions already proposed, and it may mean deciding
as a group whether the advantages of a proposal for its problem
chunk are worth building the other bits around it.

In general, it is easier to finish a requirements doc and then work on
the intended solution, and it may be my fault for assuming we could do
the work in parallel at this point.  I hope we can, because we have an
aggressive schedule.  To do that, it is useful for both those
proposing a a solution and those concerned about a solution's
completeness to indicate how it fails to meet the needs of the
service by reference to the requirements document.  If that can't
be done while we wordsmith the requirements document, I believe
we can reference the scope of the problem a particular document
attempts to address.

In an example case, we might have someone put forward an abstract
schema (without reference to the language in which the schema is
expressed).  This would be a substantial chunk of the problem,
and could be discussed as such, but it would have to be seen as
only a part of the larger problem, the "schema chunk" if you will.

In this case, it looks to me like the draft takes on a "transport (or
possibly transaction) chunk".  We can certainly discuss this proposal
in relation to those requirements; we then need to fit the proposal
into the larger picture and understand if it brings specific
advantages or disadvantages when we see it in relation to the other
bits of the problem.

Stephane, is this an accurate reflection of the part of the problem
you meant to tackle?  If so, how do you see it fitting into the
other bits that have been described in the requirements documents
or other proposals (i.e. does it require new methods or can it
inherit from LDAP or IRIS for some of these other chunks?)

			regards,
				Ted Hardie




From anewton@verisignlabs.com  Tue Jul 30 19:49:08 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: 30 Jul 2002 14:49:08 -0400
Subject: [Ietf-not43] issue listed in minutes
Message-ID: <1028054952.25367.12.camel@zedonthego.admin.cto.netsol.com>

In rummaging through the last meeting minutes to update the requirements
draft, I have a question about the following:

     Question: Is this a read-write or read-only protocol?
         Read-only
         No desire to store requests on server (too complicated)
         Declare features in which a client would write (store) data on 
server
         as out of scope

         *** WG consensus needed on above point ***


To answer the question of this being a read-write vs. read-only
protocol, the requirements already contain the following text:

   The
   scope of the requirements in this document are also restricted to
   access of data from Internet registries. Requirements for
   modification, addition, or provisioning of data in Internet
   registries are out of scope.

And I believe the "too complicated" comment to be an issue for the
technical proposals when we get around to discussing them.

Comments?  Or better yet, text for the draft?

-andy





From Internet-Drafts@ietf.org  Wed Jul 31 12:35:08 2002
From: Internet-Drafts@ietf.org (Internet-Drafts@ietf.org)
Date: Wed, 31 Jul 2002 07:35:08 -0400
Subject: [Ietf-not43] I-D ACTION:draft-ietf-crisp-lw-asn-00.txt
Message-ID: <200207311135.HAA21329@ietf.org>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Cross Registry Information Service Protocol Working Group of the IETF.

	Title		: Defining and Locating Autonomous System Numbers using 
                          the Internet Resource Query Service
	Author(s)	: E. Hall
	Filename	: draft-ietf-crisp-lw-asn-00.txt
	Pages		: 11
	Date		: 30-Jul-02
	
This document defines LDAP schema and searching rules for 
autonomous system numbers, in support of the Internet Resource 
Query Service described in [ldap-whois].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-lw-asn-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-crisp-lw-asn-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-crisp-lw-asn-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020730114306.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-lw-asn-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-crisp-lw-asn-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020730114306.I-D@ietf.org>

--OtherAccess--

--NextPart--



From Internet-Drafts@ietf.org  Wed Jul 31 12:35:12 2002
From: Internet-Drafts@ietf.org (Internet-Drafts@ietf.org)
Date: Wed, 31 Jul 2002 07:35:12 -0400
Subject: [Ietf-not43] I-D ACTION:draft-ietf-crisp-lw-user-00.txt
Message-ID: <200207311135.HAA21345@ietf.org>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Cross Registry Information Service Protocol Working Group of the IETF.

	Title		: Defining and Locating Contact Persons using the 
                          Internet Resource Query Service
	Author(s)	: E. Hall
	Filename	: draft-ietf-crisp-lw-user-00.txt
	Pages		: 7
	Date		: 30-Jul-02
	
This document defines LDAP schema and searching rules for contact 
persons, in support of the Internet Resource Query Service 
described in [ldap-whois].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-lw-user-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-crisp-lw-user-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-crisp-lw-user-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020730114313.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-lw-user-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-crisp-lw-user-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020730114313.I-D@ietf.org>

--OtherAccess--

--NextPart--



From Internet-Drafts@ietf.org  Wed Jul 31 12:35:17 2002
From: Internet-Drafts@ietf.org (Internet-Drafts@ietf.org)
Date: Wed, 31 Jul 2002 07:35:17 -0400
Subject: [Ietf-not43] I-D ACTION:draft-ietf-crisp-lw-dns-00.txt
Message-ID: <200207311135.HAA21361@ietf.org>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Cross Registry Information Service Protocol Working Group of the IETF.

	Title		: Defining and Locating DNS Domains using the Internet 
                          Resource Query Service
	Author(s)	: E. Hall
	Filename	: draft-ietf-crisp-lw-dns-00.txt
	Pages		: 13
	Date		: 30-Jul-02
	
This document defines LDAP schema and searching rules for DNS 
domains, in support of the Internet Resource Query Service 
described in [ldap-whois].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-lw-dns-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-crisp-lw-dns-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-crisp-lw-dns-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020730114323.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-lw-dns-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-crisp-lw-dns-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020730114323.I-D@ietf.org>

--OtherAccess--

--NextPart--



From Internet-Drafts@ietf.org  Wed Jul 31 12:35:22 2002
From: Internet-Drafts@ietf.org (Internet-Drafts@ietf.org)
Date: Wed, 31 Jul 2002 07:35:22 -0400
Subject: [Ietf-not43] I-D ACTION:draft-ietf-crisp-lw-ipv6-00.txt
Message-ID: <200207311135.HAA21378@ietf.org>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Cross Registry Information Service Protocol Working Group of the IETF.

	Title		: Defining and Locating IPv6 Address Blocks using the 
                          Internet Resource Query Service
	Author(s)	: E. Hall
	Filename	: draft-ietf-crisp-lw-ipv6-00.txt
	Pages		: 12
	Date		: 30-Jul-02
	
This document defines LDAP schema and searching rules for IPv6 
addresses and address blocks, in support of the Internet Resource 
Query Service described in [ldap-whois].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-lw-ipv6-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-crisp-lw-ipv6-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-crisp-lw-ipv6-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020730114333.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-lw-ipv6-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-crisp-lw-ipv6-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020730114333.I-D@ietf.org>

--OtherAccess--

--NextPart--



From Internet-Drafts@ietf.org  Wed Jul 31 12:35:27 2002
From: Internet-Drafts@ietf.org (Internet-Drafts@ietf.org)
Date: Wed, 31 Jul 2002 07:35:27 -0400
Subject: [Ietf-not43] I-D ACTION:draft-ietf-crisp-lw-core-00.txt
Message-ID: <200207311135.HAA21394@ietf.org>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Cross Registry Information Service Protocol Working Group of the IETF.

	Title		: The Internet Resource Query Service and the Internet 
                          Resource Schema
	Author(s)	: E. Hall
	Filename	: draft-ietf-crisp-lw-core-00.txt
	Pages		: 61
	Date		: 30-Jul-02
	
This document describes an architectural framework for locating 
and retrieving information about network resources, using LDAPv3 
for the data-formatting and query-processing services. This 
document also defines LDAP schema and searching rules for four 
Internet resource types: DNS domains, IPv4 addresses, IPv6 
address, and AS numbers. The framework specified in this document 
also allows additional documents to define additional Internet 
resource types and their handling rules.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-lw-core-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-crisp-lw-core-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-crisp-lw-core-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020730114343.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-lw-core-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-crisp-lw-core-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020730114343.I-D@ietf.org>

--OtherAccess--

--NextPart--



From Internet-Drafts@ietf.org  Wed Jul 31 12:36:12 2002
From: Internet-Drafts@ietf.org (Internet-Drafts@ietf.org)
Date: Wed, 31 Jul 2002 07:36:12 -0400
Subject: [Ietf-not43] I-D ACTION:draft-ietf-crisp-lw-ipv4-00.txt
Message-ID: <200207311136.HAA21553@ietf.org>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Cross Registry Information Service Protocol Working Group of the IETF.

	Title		: Defining and Locating IPv4 Address Blocks using the 
                          Internet Resource Query Service
	Author(s)	: E. Hall
	Filename	: draft-ietf-crisp-lw-ipv4-00.txt
	Pages		: 12
	Date		: 30-Jul-02
	
This document defines LDAP schema and searching rules for IPv4 
addresses and address blocks, in support of the Internet Resource 
Query Service described in [ldap-whois].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-lw-ipv4-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-crisp-lw-ipv4-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-crisp-lw-ipv4-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020730114954.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-lw-ipv4-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-crisp-lw-ipv4-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020730114954.I-D@ietf.org>

--OtherAccess--

--NextPart--



From ehall@ehsco.com  Wed Jul 31 15:54:45 2002
From: ehall@ehsco.com (Eric A. Hall)
Date: Wed, 31 Jul 2002 09:54:45 -0500
Subject: [Ietf-not43] drafts
Message-ID: <3D47FA35.5070002@ehsco.com>

FYI, the spate of draft-ietf-crisp-lw-* drafts is the ldap-whois draft
broken into components as per the WG charter. draft-ietf-crisp-lw-core
describes the architecture, the inetResources parent schema, the query
processing models, and so forth, while draft-ietf-crisp-lw-dns describes
the inetDnsDomain schema and the associated matching filter. The other
drafts describe the IPv4, IPv6, ASN and user schema and matching filters,
but are listed as expiremental since they are not part of the official WG
charter.

No major changes have been made to the content. The purpose of this batch
is to align the original draft with the WG charter. I plan on making some
substantive content changes in a few weeks.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/


