From leslie@research.netsol.com  Tue Feb  5 16:49:28 2002
From: leslie@research.netsol.com (Leslie Daigle)
Date: Tue, 05 Feb 2002 11:49:28 -0500
Subject: [Ietf-not43] DRAFT bof proposal
Message-ID: <3C600D18.507@research.netsol.com>

This is a multi-part message in MIME format.
--------------030803030408090106050004
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Howdy,

Following on some discussions that have been happening in various
technical forums, Andy Newton & I are putting together a proposal
for a BoF at the Minneapolis IETF.  The theory is that there is
actually a scoped problem here, and it's solvable.

I've attached the current bof proposal -- comments welcome.

Thanks,
Leslie.

-- 

------------------------------------------------------------
Leslie Daigle
leslie@verisignlabs.com

VeriSign Applied Research
------------------------------------------------------------

--------------030803030408090106050004
Content-Type: text/plain;
 name="crisp-bof.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="crisp-bof.txt"


Cross-Registry Information Service Protocol (CRISP)
===================================================

BoF Chair:  Ted Hardie

Mailing list:  ietf-not43@lists.verisignlabs.com
Archive/Subscription:
   https://lists.verisignlabs.com/mailman/listinfo/ietf-not43


Description:

The goal of this BoF is to understand the need and discuss
the creation of a working group to create or select a protocol for 
specific administrative directory services provided by registries.  
Backwards compatibility with RFC 954 (WHOIS) is a non-goal.


Motivation:

The expansion and growth of the Internet has seen the registry function
of a traditionally centralized and managed Network Information Center
become the responsibility of various autonomous, functionally disparate,
and globally distributed Internet registries. With the broadening
number of Internet registries, the uses of their administrative
directory services has expanded from the original and traditional use
of the WHOIS protocol to include: the use of whois outside the scope
its specification; formal and informal definitions of syntax;
undocumented security mechanisms; the use of non-standard protocols, 
etc.

Requirements have been gathered, straw proposals are on the table,
and the purpose of this BoF is to determine how to proceed to
specifying a new standard service (based on existing protocols
where possible), to support the universal, common needs of the
specified Internet registries and their related communities. The
requirements are of both the current use of these directory services
and the desired need of new function based on input from relevant
forums. These requirements are not specific to any protocol.

BoF Agenda:

    1. Scribe volunteer
    2. Agenda bash
    3. Discussion of requirements
        . draft-newton-ir-dir-requirements-00.txt
    4. Overview of straw proposals
        . draft-hall-ldap-whois-00.txt
        . draft-newton-xdap-01.txt
        . draft-newton-xdap-domdir-01.txt
        . draft-newton-xdap-ipdir-01.txt
    5. Charter bash




Background reading:

   Requirements:
    draft-newton-ir-dir-requirements-00.txt (coming soon)

   LDAP proposals:
    draft-newton-ldap-whois-00.txt
    draft-hall-ldap-whois-00.txt

   XML proposal:
    draft-newton-xdap-01.txt
    draft-newton-xdap-domdir-01.txt
    draft-newton-xdap-ipdir-01.txt

   The State of Whois:
    draft-campbell-whois-00.txt
    draft-brunner-rfc954-historic-00.txt



Straw Charter Proposal:


The expansion and growth of the Internet has seen the registry function
of a traditionally centralized and managed Network Information Center
become the responsibility of various autonomous, functionally disparate,
and globally distributed Internet registries. With the broadening
number of Internet registries, the uses of their administrative
directory services has expanded from the original and traditional use
of the WHOIS protocol to include: the use of whois outside the scope
its specification; formal and informal definitions of syntax;
undocumented security mechanisms; the use of non-standard protocols, 
etc.

The purpose of the CRISP Working Group is to create or select
a protocol for accessing the administrative directory services 
provided by registries.  



Specific design considerations include:

o Backwards compatibility with RFC 954 (WHOIS) is a non-goal.

o Information must be managed in a distributed fashion (e.g., at
  different registries), while it is desirable to be able to
  locate (or find) the source of authoritative data no matter
  where it is stored (i.e., distributed storage, global navigation).

o The service must support the concept of priviledged and non-
  priviledged data (although the definition of what is priviledged
  is not within scope for this work)


The service definition will define: 

o specific data types and queries to be supported in the global service

o standard process for naming or locating authoritative servers 

o expression of input query 

o expression of result sets 

o standard expression of error conditions 


Deliverables: 

o Finalized requirements document for the CRISP service

o Document specifying (the use of) a protocol for providing CRISP
  standard service.


Input documents:
    draft-newton-ir-dir-requirements-00.txt (coming soon)


Goals and Milestones:

 Jun 02    Submit requirements document as an Informational RFC 
           
 Sep 02    Submit first draft of protocol (use) specification

 Jan 03    Submit revised protocol (use) specification document
           as Proposed Standard.
           
 Feb 03    Close working group.

--------------030803030408090106050004--


From brunner@world.std.com  Wed Feb  6 21:33:27 2002
From: brunner@world.std.com (Eric Brunner)
Date: Wed, 06 Feb 2002 16:33:27 -0500
Subject: [Ietf-not43] DRAFT bof proposal
In-Reply-To: Your message of "Tue, 05 Feb 2002 11:49:28 EST."
 <3C600D18.507@research.netsol.com>
Message-ID: <200202062133.QAA13633@world.std.com>

Leslie,

I intend to rev. draft-brunner-rfc954-historic-00.txt this week.

I'll quibble with the dualism of "privileged and non-priviledged" data,
as that doesn't quite capture the requirements to get in under the data
protection radar(s).

Eric

From ehall@ehsco.com  Thu Feb  7 03:13:50 2002
From: ehall@ehsco.com (Eric A. Hall)
Date: Wed, 06 Feb 2002 21:13:50 -0600
Subject: [Ietf-not43] DNS servers in WHOIS output
Message-ID: <3C61F0EE.219C57FC@ehsco.com>

I'm updating the LDAP-WHOIS specification, and have an open issue that
needs addressing. See the following text, and the question at bottom.


10.3.	Nameserver Attributes

WHOIS servers for DNS domains have historically provided information about
the DNS servers associated with a domain, such as providing the hostnames
and IP addresses of the DNS servers which have been delegated authority
over a particular domain.

However, this information has typically been provided as a reflection of
the registration process, and has not been provided as a beneficial part
of the WHOIS service in particular. Users who have needed to find and
review DNS information have typically known to use DNS for this function,
and have had no motivation to use WHOIS for this purpose.

Furthermore, providing this information in the LDAP-WHOIS model is
somewhat problematic, since it is difficult to integrate the DNS data into
LDAP cleanly. The best design for such a service would entail an auxiliary
object class for the inetDnsDomain object class which provided resource
record attributes, and which stored NS and the associated A resource
records as directory objects. While such a structure would provide
multiple benefits to multiple problems, it seems imprudent to pursue this
approach for the single short-term objective of caching delegation name
servers.

For this reason, attributes for this information are not provided in the
LDAP-WHOIS service. Instead, users and application developers are
encouraged to develop practices for querying the DNS zones for information
related to DNS. However, if this information is absolutely required,
server operators MAY provide it as unstructured data in the
inetGeneralComments free-text attribute (possibly using a name:address
pair for each server).


There are a couple of questions to ask here. First of all, how accurate is
that assesment? My own experience is that DNS is the best place to debug
DNS problems. If a domain isn't delegated in the parent, who cares what
WHOIS says? Conversely, any servers which may be listed in WHOIS are
likely to answer, but who cares if they answer if the DNS delegation is
broken? In that regard, any DNS data which may be provided in WHOIS is
useless, for all practical purposes. By the same token, we don't expect
that the zone delegation will give us WHOIS date, so why do we need to
expect that the WHOIS data should give us the DNS delegation? Show me how
it could be otherwise, if you believe as much.

Secondarily, the principle reason that ANY such data has ever been
included with the WHOIS information is because WHOIS+DNS is required for
registration INPUT. However, as argued above, WHOIS+DNS is NOT required
for output.

In light of that argument, it is worth noting that the LDAP-WHOIS service
is neither designed nor intended to function as a registry interface. As
such, there is no compelling reason I can think of for including DNS data
in the WHOIS output, other than ~"we have always done it that way."

Now then, having said all of that, it is possible to include DNS data in
the WHOIS output, and to do so in a format which is programmatically
parsable, which is to spend a fair number of cycles on a schema for
resource records in general. This will be required sooner or later anyway,
so its not a huge issue to do it sooner. However, I would rather not
inflate the initial deployment requirements too much. Furthermore,
providing this information also carries a certain responsibilty to discuss
where the data comes from, the security risks from failing to secure the
data, and so forth. It really raises the first-step bar dramatically, and
this is something I would rather avoid.

So, is DNS information such as NS RRs and the glue A RRs something that
people really need, or is it just something that people expect because its
always been there, but it isn't absolutely required.

Comments please

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

From Stig.Venaas@uninett.no  Thu Feb  7 07:06:08 2002
From: Stig.Venaas@uninett.no (Stig Venaas)
Date: Thu, 7 Feb 2002 08:06:08 +0100
Subject: [Ietf-not43] DNS servers in WHOIS output
In-Reply-To: <3C61F0EE.219C57FC@ehsco.com>; from ehall@ehsco.com on Wed, Feb 06, 2002 at 09:13:50PM -0600
References: <3C61F0EE.219C57FC@ehsco.com>
Message-ID: <20020207080608.C21603@sverresborg.uninett.no>

On Wed, Feb 06, 2002 at 09:13:50PM -0600, Eric A. Hall wrote:
> Furthermore, providing this information in the LDAP-WHOIS model is
> somewhat problematic, since it is difficult to integrate the DNS data into
> LDAP cleanly. The best design for such a service would entail an auxiliary
> object class for the inetDnsDomain object class which provided resource
> record attributes, and which stored NS and the associated A resource
> records as directory objects. While such a structure would provide

I have a simple schema that might be of use (used for storing zones
in LDAP), but I guess the hardest part isn't the schema it self, but
all the related issues you listed.

> Secondarily, the principle reason that ANY such data has ever been
> included with the WHOIS information is because WHOIS+DNS is required for
> registration INPUT. However, as argued above, WHOIS+DNS is NOT required
> for output.

Agree with this and the text I deleted above.

> So, is DNS information such as NS RRs and the glue A RRs something that
> people really need, or is it just something that people expect because its
> always been there, but it isn't absolutely required.

I think the latter.

>From our standpoint, the idea is (was?) that the output from
traditional WHOIS should look like the registration forms. This
might help in some cases, but I'm not sure how important that is.
I think it's just as well to leave it out.

Stig

From anewton@verisignlabs.com  Thu Feb  7 16:16:27 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: Thu, 7 Feb 2002 11:16:27 -0500
Subject: [Ietf-not43] DNS servers in WHOIS output
In-Reply-To: <3C61F0EE.219C57FC@ehsco.com>; from ehall@ehsco.com on Wed, Feb 06, 2002 at 09:13:50PM -0600
References: <3C61F0EE.219C57FC@ehsco.com>
Message-ID: <20020207111627.E6339@zed.admin.cto.netsol.com>

On Wed, Feb 06, 2002 at 09:13:50PM -0600, Eric A. Hall wrote:
> 
> In light of that argument, it is worth noting that the LDAP-WHOIS service
> is neither designed nor intended to function as a registry interface. As
> such, there is no compelling reason I can think of for including DNS data
> in the WHOIS output, other than ~"we have always done it that way."
> 
[..snip..]
>
> So, is DNS information such as NS RRs and the glue A RRs something that
> people really need, or is it just something that people expect because its
> always been there, but it isn't absolutely required.

I think you are making a bigger deal out of this than necessary.
The intention of WHOIS as it relates to why NS records are duplicated
there is to be a place to go when DNS isn't functioning properly.
Such things as cache poisoning, incorrect master/slave relationships,
etc... can cause this.  And yes, I have used it for troubleshooting.

But since this is for troubleshooting and nobody is saying to do
backup resolution out of WHOIS or LDAP (atleast I hope not!), it
isn't necessary to reproduce the DNS infomation verbatim.  So breaking
this out into separate NS and A records seems to be overdoing it
a bit.

-andy

-- 
Andrew Newton
VeriSign Applied Research
anewton@research.netsol.com

From anewton@verisignlabs.com  Thu Feb  7 16:46:30 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: Thu, 7 Feb 2002 11:46:30 -0500
Subject: [Ietf-not43] DNS servers in WHOIS output
In-Reply-To: <3C62AD9E.544A8D5B@ehsco.com>; from ehall@ehsco.com on Thu, Feb 07, 2002 at 10:38:54AM -0600
References: <3C61F0EE.219C57FC@ehsco.com> <20020207111627.E6339@zed.admin.cto.netsol.com> <3C62AD9E.544A8D5B@ehsco.com>
Message-ID: <20020207114630.B6500@zed.admin.cto.netsol.com>

On Thu, Feb 07, 2002 at 10:38:54AM -0600, Eric A. Hall wrote:
> 
> So read-only replication is okay. Alright, replication from what then?
> Does it replicate from DNS where it is the most valuable for diagnostic
> purposes, or does it replicate from the registration database? Although
> these should be the same thing they won't always be. Updates which go into
> DNS the next day, for example, will have different values in the two
> systems. Which one to use?

Well, if it is being used for troubleshooting, I would only use the
values out of WHOIS when DNS isn't working (and let's be clear,
for finding the problem, not as an automated back-up resolution
process).  It also depends on the
registry as to the accuracy of WHOIS vs. DNS and the latency between
updates.

-andy

-- 
Andrew Newton
VeriSign Applied Research
anewton@research.netsol.com

From ehall@ehsco.com  Thu Feb  7 16:38:54 2002
From: ehall@ehsco.com (Eric A. Hall)
Date: Thu, 07 Feb 2002 10:38:54 -0600
Subject: [Ietf-not43] DNS servers in WHOIS output
References: <3C61F0EE.219C57FC@ehsco.com> <20020207111627.E6339@zed.admin.cto.netsol.com>
Message-ID: <3C62AD9E.544A8D5B@ehsco.com>

Andrew Newton wrote:

> But since this is for troubleshooting and nobody is saying to do
> backup resolution out of WHOIS or LDAP (atleast I hope not!), it
> isn't necessary to reproduce the DNS infomation verbatim.  So breaking
> this out into separate NS and A records seems to be overdoing it
> a bit.

So read-only replication is okay. Alright, replication from what then?
Does it replicate from DNS where it is the most valuable for diagnostic
purposes, or does it replicate from the registration database? Although
these should be the same thing they won't always be. Updates which go into
DNS the next day, for example, will have different values in the two
systems. Which one to use?

If we do this, how does the data need to be defined? Clearly we want
information to be programmatically parsable for maximum leverage (not as
an out-of-band way to do DNS, but to allow clients to perform routine
tasks on the data, such as querying the servers for the SOA of the zone,
to see if it actually exists). This requires a schema for DNS RRs, if we
want to do it right.

Also, if we're going to do that, shouldn't we also look at providing
routing information with the IP networks?

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

From ehall@ehsco.com  Thu Feb  7 17:09:46 2002
From: ehall@ehsco.com (Eric A. Hall)
Date: Thu, 07 Feb 2002 11:09:46 -0600
Subject: [Ietf-not43] DNS servers in WHOIS output
References: <3C61F0EE.219C57FC@ehsco.com> <20020207111627.E6339@zed.admin.cto.netsol.com> <3C62AD9E.544A8D5B@ehsco.com> <20020207114630.B6500@zed.admin.cto.netsol.com>
Message-ID: <3C62B4DA.92D3655B@ehsco.com>

Andrew Newton wrote:
> 
> On Thu, Feb 07, 2002 at 10:38:54AM -0600, Eric A. Hall wrote:
> >
> > So read-only replication is okay. Alright, replication from what then?

> Well, if it is being used for troubleshooting, I would only use the
> values out of WHOIS when DNS isn't working (and let's be clear,

Okay. We can also make use of the various Modifed* operational attributes
to show when/who the changes were made, which will let people know if
there is some lag between the registration view and the DNS view.

I'll start looking at the attributes needed for this.

ps--I'm of the opinion that this information is absolutely necessary to
deployment. People will scream if a useless feature is no longer
available, which will hinder deployment, so I will give them the useless
feature. I just wanted to confirm that it is in fact useless.

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

From bruce_campbell@ripe.net  Thu Feb  7 20:35:30 2002
From: bruce_campbell@ripe.net (Bruce Campbell)
Date: Thu, 7 Feb 2002 21:35:30 +0100 (CET)
Subject: [Ietf-not43] DNS servers in WHOIS output
In-Reply-To: <3C62AD9E.544A8D5B@ehsco.com>
Message-ID: <Pine.LNX.4.44.0202072127490.17272-100000@x22.ripe.net>

On Thu, 7 Feb 2002, Eric A. Hall wrote:

> Andrew Newton wrote:
>
> > But since this is for troubleshooting and nobody is saying to do
> > backup resolution out of WHOIS or LDAP (atleast I hope not!), it
> > isn't necessary to reproduce the DNS infomation verbatim.  So breaking
> > this out into separate NS and A records seems to be overdoing it
> > a bit.

tab or 'known character' seperated for preference please.

> So read-only replication is okay. Alright, replication from what then?
> Does it replicate from DNS where it is the most valuable for diagnostic
> purposes, or does it replicate from the registration database? Although

'Most valuable' for diagnostic purposes would be to use the same,
authoritative source that the zone files are generated from.  In most
cases, this is the Registration database.

Regards,

-- 
                             Bruce Campbell                            RIPE
                   Systems/Network Engineer                             NCC
                 www.ripe.net - PGP562C8B1B                      Operations


From sanz@denic.de  Fri Feb  8 09:45:27 2002
From: sanz@denic.de (Marcos Sanz/Denic)
Date: Fri, 8 Feb 2002 10:45:27 +0100
Subject: [Ietf-not43] DNS servers in WHOIS output
Message-ID: <OF92F210A9.1A307561-ONC1256B5A.0034E88A@denic.de>

On 07.02.2002 17:46 Andrew Newton <anewton@verisignlabs.com> wrote:
>
> Well, if it is being used for troubleshooting, I would only use the
> values out of WHOIS when DNS isn't working (and let's be clear,

And what about domains, which are registered, but are not connected at =
the
moment (latency between registry-DB and DNS, domain is in a blocked sta=
tus,
...). You cannot "dig" them, though it would be useful to be able to ac=
cess
the registration information.

Regards,
Marcos Sanz
DENIC eG=



From anewton@verisignlabs.com  Fri Feb  8 14:38:18 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: Fri, 8 Feb 2002 09:38:18 -0500
Subject: [Ietf-not43] I-D ACTION:draft-newton-ir-dir-requirements-00.txt
Message-ID: <20020208093818.C7011@zed.admin.cto.netsol.com>

--1yeeQ81UyVL57Vl7
Content-Type: text/plain; charset=us-ascii

As was discussed on this list some time ago, and mentioned in the
BoF request, this is a draft on requirements for Internet registry
directories.

-andy

-- 
Andrew Newton
VeriSign Applied Research
anewton@research.netsol.com

--1yeeQ81UyVL57Vl7
Content-Type: message/rfc822

Received: from localhost (localhost [127.0.0.1])
	by zed.admin.cto.netsol.com (8.9.3+Sun/8.9.1) with ESMTP id IAA07726
	for <anewton@localhost>; Fri, 8 Feb 2002 08:25:13 -0500 (EST)
Received: from vsvapostal1.prod.netsol.com
	by localhost with POP3 (fetchmail-5.1.0)
	for anewton@localhost (single-drop); Fri, 08 Feb 2002 08:25:14 -0500 (EST)
Received: from netsol.com (mx1netsol.mgt.netsol.com [192.168.222.92]) by VSVAPOSTALGW1.prod.netsol.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id DD9BF5YA; Fri, 8 Feb 2002 08:30:49 -0500
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by netsol.com (8.9.3/8.9.3) with ESMTP id IAA28967;
	Fri, 8 Feb 2002 08:30:27 -0500 (EST)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id IAA12988
	for ietf-123-outbound.04@ietf.org; Fri, 8 Feb 2002 08:25:00 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA12661
	for <all-ietf@loki.ietf.org>; Fri, 8 Feb 2002 07:35:27 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04494
	for <all-ietf@ietf.org>; Fri, 8 Feb 2002 07:35:26 -0500 (EST)
Message-Id: <200202081235.HAA04494@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-newton-ir-dir-requirements-00.txt
Date: Fri, 08 Feb 2002 07:35:26 -0500
Sender: nsyracus@cnri.reston.va.us

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Internet Registry Directory Requirements
	Author(s)	: A. Newton, S. Kerr
	Filename	: draft-newton-ir-dir-requirements-00.txt
	Pages		: 20
	Date		: 07-Feb-02
	
Internet registries expose administrative and operational data via
varying directory services. This document defines the common
requirements for the directory services of these Internet registries.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-newton-ir-dir-requirements-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-newton-ir-dir-requirements-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-newton-ir-dir-requirements-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:	<20020207165832.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-newton-ir-dir-requirements-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-newton-ir-dir-requirements-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"


--OtherAccess--

--NextPart--

--1yeeQ81UyVL57Vl7--

From ehall@ehsco.com  Wed Feb 13 17:16:02 2002
From: ehall@ehsco.com (Eric A. Hall)
Date: Wed, 13 Feb 2002 11:16:02 -0600
Subject: [Ietf-not43] [Fwd: I-D ACTION:draft-hall-ldap-whois-01.txt]
Message-ID: <3C6A9F52.35B9D736@ehsco.com>

This is a multi-part message in MIME format.
--------------3F74449C6CAC336B5DCEF9A0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


FYI, a new version of draft-hall-ldap-whois is available.

People who don't want to read the whole thing should focus on section 7,
since that is where all of the elements come together for the core
query-formation and referral-processing services.


 15.     Changes from Previous Versions 
      
    The following changes were made to the -00 version: 
     
       *   The "Objectives" section has been removed. [ir-dir-req] is 
           now being used as the guiding document for this service. 
      
       *   Several typographical errors have been fixed. 
     
       *   Some unnecessary text has been removed. 
     
       *   Figures changed to show complete sets of object classes, to 
           improve inheritance visibility. 
     
       *   Clarified the handling of reverse-lookup domains (zones 
           within the in-addr.arpa portion of the DNS hierarchy) in 
           the inetDnsDomain object class reference text. 
     
       *   Referrals now use regular LDAP URLs (multiple responses 
           with explicit hostnames and port numbers). Prior editions 
           of this specification used LDAP SRV resource records for 
           all referrals. 
     
       *   The delegation status codes used by the 
           inetDnsDelegationStatus, inetIpv4DelegationStatus, 
           inetIpv6DelegationStatus and inetAsnDelegationStatus 
           attributes have been condensed to a more logical set. 
     
       *   Added an inetDnsAuthServers attribute for publishing the 
           authoritative DNS servers associated with a domain. NOTE 
           THAT THIS IS A TEMPORARY ATTRIBUTE THAT WILL EVENTUALLY BE 
           REPLACED BY GENERALIZED RESOURCE-RECORD ENTRIES AND 
           ATTRIBUTES. 
     
       *   Added an inetGeneralDisclaimer attribute for publishing 
           generalized disclaimers. 
     
       *   Added the inetAssociatedResources auxiliary object class 
           for defining associated resources, and moved some of the IP 
           addressing and ASN attributes to the new object class. 
     
       *   Several attributes had their OIDs changed. NOTE THAT THIS 
           IS AN INTERNET DRAFT, AND THAT THE OIDS ARE SUBJECT TO 
           ADDITIONAL CHANGES AS THIS DOCUMENT IS EDITED. 

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/
--------------3F74449C6CAC336B5DCEF9A0
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Return-Path: <ietf-123-owner@loki.ietf.org>
Received: from loki.ietf.org ([132.151.1.177] verified)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.5.2)
  with ESMTP id 55746 for lists@EHSCO.COM; Wed, 13 Feb 2002 08:03:37 -0600
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id IAA03411
	for ietf-123-outbound.02@ietf.org; Wed, 13 Feb 2002 08:45:00 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA02829
	for <all-ietf@loki.ietf.org>; Wed, 13 Feb 2002 07:09:38 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28738
	for <all-ietf@ietf.org>; Wed, 13 Feb 2002 07:09:37 -0500 (EST)
Message-Id: <200202131209.HAA28738@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-hall-ldap-whois-01.txt
Date: Wed, 13 Feb 2002 07:09:37 -0500
Sender: nsyracus@cnri.reston.va.us

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: The Internet Resource Query Service and the WHOIS 
                          Resource Schema
	Author(s)	: E. Hall, A. Newton
	Filename	: draft-hall-ldap-whois-01.txt
	Pages		: 88
	Date		: 12-Feb-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 processing rules for four 
Internet resource types: DNS domains, IPv4 addresses, IPv6 
address, and AS numbers. The framework specified in this document 
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-hall-ldap-whois-01.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-hall-ldap-whois-01.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-hall-ldap-whois-01.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:	<20020212144135.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-hall-ldap-whois-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-hall-ldap-whois-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--



--------------3F74449C6CAC336B5DCEF9A0--


From anewton@verisignlabs.com  Tue Feb 26 17:07:28 2002
From: anewton@verisignlabs.com (Andrew Newton)
Date: Tue, 26 Feb 2002 12:07:28 -0500
Subject: [Ietf-not43] CRISP BOF Scheduled
Message-ID: <20020226120728.C2615@zed.admin.cto.netsol.com>

For all who may not have seen, the CRISP BOF appears to be
scheduled for Monday evening.

> Cross-Registry Information Service Protocol BOF (crisp)
> 
> Monday, March 18 at 1930-2200

More here:

http://www.ietf.org/ietf/02mar/crisp.txt

-andy


-- 
Andrew Newton
VeriSign Applied Research
anewton@research.netsol.com

From ehall@ehsco.com  Tue Feb 26 18:36:55 2002
From: ehall@ehsco.com (Eric A. Hall)
Date: Tue, 26 Feb 2002 12:36:55 -0600
Subject: [Ietf-not43] CRISP BOF Scheduled
References: <20020226120728.C2615@zed.admin.cto.netsol.com>
Message-ID: <3C7BD5C7.95DB21D8@ehsco.com>

Andrew Newton wrote:

> > Cross-Registry Information Service Protocol BOF (crisp)

> http://www.ietf.org/ietf/02mar/crisp.txt

Slight clarification:

 | Background reading:

 |   LDAP proposals:

 |     draft-hall-ldap-whois-00.txt

draft-hall-ldap-whois-01.txt is the latest version

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

