From Internet-Drafts@ietf.org  Mon Aug  5 12:43:24 2002
From: Internet-Drafts@ietf.org (Internet-Drafts@ietf.org)
Date: Mon, 05 Aug 2002 07:43:24 -0400
Subject: [Ietf-not43] I-D ACTION:draft-ietf-crisp-requirements-00.txt
Message-ID: <200208051143.HAA08271@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		: Cross Registry Internet Service Protocol (CRISP) 
                          Requirements
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-requirements-00.txt
	Pages		: 25
	Date		: 02-Aug-02
	
Internet registries expose administrative and operational data via
varying directory services. This document defines functional
requirements for the directory services of domain registries and the
common base requirements for extending the use of these services for
other types of Internet registries.

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

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

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

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

--OtherAccess--

--NextPart--



From anewton@ecotroph.net  Mon Aug  5 17:17:04 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Mon, 05 Aug 2002 12:17:04 -0400
Subject: [Ietf-not43] requirements diffs
Message-ID: <3D4EA500.E06B161A@ecotroph.net>

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

I know that the first thing everyone did with their Monday morning was
to download the latest requirements draft from the repository and scan
it in detail for what changed.  After all, the only thing more fun than
talking about what your are going to do is talking about talking about
what your are going to do.

So to make the task easier, I've attached a "more-human-readable" diff
of the draft.  Also attached is an HTML version of the draft for people
wanting to use this new fangled thing called "hyper-linking" to
cross-reference sections.

-andy
--------------10D531E406820549FCF3A484
Content-Type: text/plain; charset=us-ascii;
 name="crisp-req-ann.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="crisp-req-ann.diff"

Abstract

   Internet registries expose administrative and operational data via
   varying directory services. This document defines functional
   requirements for the directory services of domain registries and the
   common base requirements for extending the use of these services for
   other types of Internet registries.

---------------------


2.4.6 Domain Registrants

   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.

---------------------

3. Functional Requirements

   Functional requirements describe an overall need or process for
   which the directory service is used by an Internet registry to
   fulfill its obligations to provide access to its respective
   customers, members, or other constituents. This section makes
   reference to terms and definitions declared in Appendix A. This
   section makes use of the term "service" to denote the set of
   functions to be provided by, and the expected behavior of, software
   built to meet these requirements in one or more protocols.

   These requirements are for the purpose of designing a technical
   specification. The words used in this section are for compliance
   with RFC2119[8], do not reference or specify policy, and speak only
   to the capabilities in the derived technology.

---------------------

3.1.8 Query of Access Levels

   If a query cannot yield a valid response due to insufficient
   permissions, the service MUST provide the client with an error
   response indicating this condition. The service SHOULD NOT provide a
   mechanism allowing a client to determine if a query will be denied
   before the query is submitted.

   It is the intent of this requirement for clients to learn of
   inadequate permission status for a query only after the query has
   been submitted. Operating modes allowing a client to predetermine
   the queries that will or will not be denied are not encouraged for
   security considerations.

---------------------

3.2.4 Domain Registrant Search

   The service MUST provide the capability of searching for registrants
   by exact name match or a reasonable name subset. The service MAY
   provide limits to the number of results from this search to
   alleviate performance or comply with Section 3.1.1. If the service
   limits the number of results from this search to alleviate
   performance, it MUST provide the client with a response indicating
   this condition. If the service limits the number of results from
   this search to comply with Section 3.1.1, it MUST NOT provide the
   client with a response indicating this condition.

   The service MUST provide a mechanism to distribute this search
   across all applicable domain registries and registrars. The service
   SHOULD have a means to narrow the scope of a search to a specific
   TLD. The service MUST be able to specify to the client an empty
   result set should the search yield no results.

---------------------

3.2.5 Domain Information Lookup

   The service MUST provide access to operational and social data
   specific to a domain given the domain's fully qualified name (FQDN).
   This information SHOULD include the following:

   o  activation status

   o  registrant name and contact data

   o  hosting nameservers

   o  technical, billing or other entity types associate with the
      domain and their relevant contact data, if any exist

   o  the name of or a reference to the registry delegating the domain

   o  the name of or a reference to the registrar for the domain, if
      one exists

---------------------

3.2.9 Domain Name Search

   The service MUST allow searching for domains by exact name match or
   a reasonable subset of a domain name. The service MAY provide limits
   to the number of results from this search to alleviate performance
   or comply with Section 3.1.1. If the service limits the number of
   results from this search to alleviate performance, it MUST provide
   the client with a response indicating this condition. If the service
   limits the number of results from this search to comply with Section
   3.1.1, it MUST NOT provide the client with a response indicating
   this condition.

   The service MUST provide a mechanism to distribute this search
   across all applicable domain registries and registrars. There should
   be a means to narrow this search based on a TLD. 

   The search mechanism SHOULD provide for differences in domain names
   between the native representation and the canonical form existing in
   the registry.

---------------------

3.2.10 DNS Label Referencing

   The service MUST use DNS[2] to determine the authoritative source of
   information about domain names. It is the intention of this
   requirement that a client be able to determine via DNS and query the
   servers or set of servers of the domain registry delegating the
   domain name, the domain registrar responsible for registering the
   domain name if one is applicable, and the domain registrant of the
   domain name. The service SHOULD provide procedures or mechanisms to
   allow this determination if it cannot be done using DNS.

---------------------

3.2.11 Distribution for Domain Registry Types

   The service MUST allow for the various registration distribution
   models of domain registry types described in Section 2.1.1 while
   complying with Section 3.1.7.

---------------------

4. Feature Requirements

   Feature requirements describe the perceived need derived from the
   functional requirements for specific technical criteria of the
   directory service. This section makes references to terms and
   definitions declared in Appendix A . This section uses the term
   "service" to denote the set of features to be provided by, and the
   expected behavior of, software built to meet these requirements in
   one or more protocols.

   These requirements are for the purpose of designing a technical
   specification. The words used in this section are for compliance
   with RFC2119[8], do not reference or specify policy, and speak only
   to the capabilities in the derived technology.


--------------10D531E406820549FCF3A484
Content-Type: text/html; charset=us-ascii;
 name="draft-ietf-crisp-requirements-00.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="draft-ietf-crisp-requirements-00.html"

<html><head><title>Cross Registry Internet Service Protocol (CRISP) Requirements</title>
<STYLE type='text/css'>
    .title { color: #990000; font-size: 22px; line-height: 22px; font-weight: bold; text-align: right;
             font-family: helvetica, arial, sans-serif }
    .filename { color: #666666; font-size: 18px; line-height: 28px; font-weight: bold; text-align: right;
                  font-family: helvetica, arial, sans-serif }
    p.copyright { color: #000000; font-size: 10px;
                  font-family: verdana, charcoal, helvetica, arial, sans-serif }
    p { margin-left: 2em; margin-right: 2em; }
    ol { margin-left: 2em; margin-right: 2em; }
    ul.text { margin-left: 2em; margin-right: 2em; }
    pre { margin-left: 3em; color: #333333 }
    ul.toc { color: #000000; line-height: 16px;
             font-family: verdana, charcoal, helvetica, arial, sans-serif }
    H3 { color: #333333; font-size: 16px; line-height: 16px; font-family: helvetica, arial, sans-serif }
    H4 { color: #000000; font-size: 14px; font-family: helvetica, arial, sans-serif }
    TD.header { color: #ffffff; font-size: 10px; font-family: arial, helvetica, san-serif; valign: top }
    TD.author-text { color: #000000; font-size: 10px;
                     font-family: verdana, charcoal, helvetica, arial, sans-serif }
    TD.author { color: #000000; font-weight: bold; margin-left: 4em; font-size: 10px; font-family: verdana, charcoal, helvetica, arial, sans-serif }
    A:link { color: #990000; font-size: 10px; text-transform: uppercase; font-weight: bold;
             font-family: MS Sans Serif, verdana, charcoal, helvetica, arial, sans-serif }
    A:visited { color: #333333; font-weight: bold; font-size: 10px; text-transform: uppercase;
                font-family: MS Sans Serif, verdana, charcoal, helvetica, arial, sans-serif }
    A:name { color: #333333; font-weight: bold; font-size: 10px; text-transform: uppercase;
             font-family: MS Sans Serif, verdana, charcoal, helvetica, arial, sans-serif }
    .link2 { color:#ffffff; font-weight: bold; text-decoration: none;
             font-family: monaco, charcoal, geneva, MS Sans Serif, helvetica, monotype, verdana, sans-serif;
             font-size: 9px }
    .RFC { color:#666666; font-weight: bold; text-decoration: none;
           font-family: monaco, charcoal, geneva, MS Sans Serif, helvetica, monotype, verdana, sans-serif;
           font-size: 9px }
    .hotText { color:#ffffff; font-weight: normal; text-decoration: none;
               font-family: charcoal, monaco, geneva, MS Sans Serif, helvetica, monotype, verdana, sans-serif;
               font-size: 9px }
</style>
</head>
<body bgcolor="#ffffff"text="#000000" alink="#000000" vlink="#666666" link="#990000">
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<table width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table width="100%" border="0" cellpadding="2" cellspacing="1">
<tr valign="top"><td width="33%" bgcolor="#666666" class="header">Network Working Group</td><td width="33%" bgcolor="#666666" class="header">A. Newton</td></tr>
<tr valign="top"><td width="33%" bgcolor="#666666" class="header">Internet-Draft</td><td width="33%" bgcolor="#666666" class="header">VeriSign, Inc.</td></tr>
<tr valign="top"><td width="33%" bgcolor="#666666" class="header">Expires: January 29, 2003</td><td width="33%" bgcolor="#666666" class="header">July 31, 2002</td></tr>
</table></td></tr></table>
<div align="right"><font face="monaco, MS Sans Serif" color="#990000" size="+3"><b><br><span class="title">Cross Registry Internet Service Protocol (CRISP) Requirements</span></b></font></div>
<div align="right"><font face="monaco, MS Sans Serif" color="#666666" size="+2"><b><span class="filename">draft-ietf-crisp-requirements-00</span></b></font></div>
<font face="verdana, helvetica, arial, sans-serif" size="2">

<h3>Status of this Memo</h3>
<p>
This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026.</p>
<p>
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.</p>
<p>
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."</p>
<p>
The list of current Internet-Drafts can be accessed at
<a href='http://www.ietf.org/ietf/1id-abstracts.txt'>http://www.ietf.org/ietf/1id-abstracts.txt</a>.</p>
<p>
The list of Internet-Draft Shadow Directories can be accessed at
<a href='http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html</a>.</p>
<p>
This Internet-Draft will expire on January 29, 2003.</p>

<h3>Copyright Notice</h3>
<p>
Copyright (C) The Internet Society (2002). All Rights Reserved.</p>

<h3>Abstract</h3>

<p>
Internet registries expose administrative and operational data via varying directory services. This document defines functional requirements for the directory services of domain registries and the common base requirements for extending the use of these services for other types of Internet registries.
</p>
<a name="toc"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Table of Contents</h3>
<ul compact class="toc">
<b><a href="#background">1.</a>&nbsp;
Background<br></b>
<b><a href="#communities">2.</a>&nbsp;
Internet Registry Communities<br></b>
<b><a href="#dom-registries">2.1</a>&nbsp;
Domain Name System Registries<br></b>
<b><a href="#domain-registries">2.1.1</a>&nbsp;
Domain Registries<br></b>
<b><a href="#domain-registrars">2.1.2</a>&nbsp;
Domain Registrars<br></b>
<b><a href="#other-registries">2.2</a>&nbsp;
Other Registries<br></b>
<b><a href="#rir">2.2.1</a>&nbsp;
Regional Internet Registries<br></b>
<b><a href="#lir">2.2.2</a>&nbsp;
Local Internet Registries<br></b>
<b><a href="#irr">2.2.3</a>&nbsp;
Internet Routing Registries<br></b>
<b><a href="#icc-reg">2.2.4</a>&nbsp;
Incident Coordination Contact Registries<br></b>
<b><a href="#nerr-reg">2.2.5</a>&nbsp;
Network Edge Resource Registries<br></b>
<b><a href="#implementers">2.3</a>&nbsp;
Implementers<br></b>
<b><a href="#end-users">2.4</a>&nbsp;
End Users<br></b>
<b><a href="#isp">2.4.1</a>&nbsp;
Service Providers and Network Operators<br></b>
<b><a href="#ipr">2.4.2</a>&nbsp;
Intellectual Property Holders<br></b>
<b><a href="#law">2.4.3</a>&nbsp;
Law Enforcement<br></b>
<b><a href="#ca">2.4.4</a>&nbsp;
Certificate Authorities<br></b>
<b><a href="#dns-users">2.4.5</a>&nbsp;
DNS Users<br></b>
<b><a href="#domain-registrants">2.4.6</a>&nbsp;
Domain Registrants<br></b>
<b><a href="#other-actors">2.5</a>&nbsp;
Other Actors<br></b>
<b><a href="#functional-requirements">3.</a>&nbsp;
Functional Requirements<br></b>
<b><a href="#common-functions">3.1</a>&nbsp;
Base Functions<br></b>
<b><a href="#mining-prev">3.1.1</a>&nbsp;
Mining Prevention<br></b>
<b><a href="#min-tech-reinvent">3.1.2</a>&nbsp;
Minimal Technical Reinvention<br></b>
<b><a href="#pred-stand-expr">3.1.3</a>&nbsp;
Standard and Extensible Schemas<br></b>
<b><a href="#level-access">3.1.4</a>&nbsp;
Level of Access<br></b>
<b><a href="#client-proc">3.1.5</a>&nbsp;
Client Processing<br></b>
<b><a href="#entity-ref">3.1.6</a>&nbsp;
Entity Referencing<br></b>
<b><a href="#decentral">3.1.7</a>&nbsp;
Decentralization<br></b>
<b><a href="#queyr-access">3.1.8</a>&nbsp;
Query of Access Levels<br></b>
<b><a href="#domain-functions">3.2</a>&nbsp;
Domain Specific Functions<br></b>
<b><a href="#contact-lookup">3.2.1</a>&nbsp;
Contact Lookup<br></b>
<b><a href="#ns-lookup">3.2.2</a>&nbsp;
Nameserver Lookup<br></b>
<b><a href="#dom-stat-lookup">3.2.3</a>&nbsp;
Domain Status Lookup<br></b>
<b><a href="#dom-registrant-search">3.2.4</a>&nbsp;
Domain Registrant Search<br></b>
<b><a href="#dom-info-lookup">3.2.5</a>&nbsp;
Domain Information Lookup<br></b>
<b><a href="#ns-search">3.2.6</a>&nbsp;
Nameserver Search<br></b>
<b><a href="#escrow">3.2.7</a>&nbsp;
Escrow Support<br></b>
<b><a href="#auth-dist">3.2.8</a>&nbsp;
Authentication Distribution<br></b>
<b><a href="#dom-name-search">3.2.9</a>&nbsp;
Domain Name Search<br></b>
<b><a href="#domain-dns-ref">3.2.10</a>&nbsp;
DNS Label Referencing<br></b>
<b><a href="#dist-for-domain-types">3.2.11</a>&nbsp;
Distribution for Domain Registry Types<br></b>
<b><a href="#feature-requirements">4.</a>&nbsp;
Feature Requirements<br></b>
<b><a href="#client-auth">4.1</a>&nbsp;
Client Authentication<br></b>
<b><a href="#referrals">4.2</a>&nbsp;
Referrals<br></b>
<b><a href="#common-ref">4.3</a>&nbsp;
Common Referral Mechanism<br></b>
<b><a href="#structure">4.4</a>&nbsp;
Structured Queries and Responses<br></b>
<b><a href="#existing-schema">4.5</a>&nbsp;
Existing Schema Language<br></b>
<b><a href="#defined-schemas">4.6</a>&nbsp;
Defined Schemas<br></b>
<b><a href="#serialization">4.7</a>&nbsp;
Serialization Definition<br></b>
<b><a href="#internationalization-con">5.</a>&nbsp;
Internationalization Considerations<br></b>
<b><a href="#iana-con">6.</a>&nbsp;
IANA Considerations<br></b>
<b><a href="#security-con">7.</a>&nbsp;
Security Considerations<br></b>
<b><a href="#rfc.references">&#167;</a>&nbsp;
References<br></b>
<b><a href="#rfc.authors">&#167;</a>&nbsp;
Author's Address<br></b>
<b><a href="#glassory">A.</a>&nbsp;
Glossary<br></b>
<b><a href="#acknowledgements">B.</a>&nbsp;
Acknowledgements<br></b>
<b><a href="#forums">B.1</a>&nbsp;
Forums<br></b>
<b><a href="#working-group">B.2</a>&nbsp;
Working Group<br></b>
<b><a href="#contributions">B.3</a>&nbsp;
Contributions<br></b>
<b><a href="#rfc.copyright">&#167;</a>&nbsp;
Full Copyright Statement<br></b>
</ul>
<br clear="all">

<a name="background"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>1.&nbsp;Background</h3>

<p>
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 have expanded from the original and traditional use of the <a href="#RFC0954">whois</a>[4] protocol to include the use of whois outside the scope of its specification, formal and informal definitions of syntax, undocumented security mechanisms, the use of other protocols, such as <a href="#RFC2167">rwhois</a>[3], to fulfill other needs, and proposals for the use of other technologies such as <a href="#RFC2251">LDAP</a>[1] and XML.
</p>

<p>
The scope of the requirements captured in this document relate to the directory services of Internet registries and their related communities (<a href="#implementers">Implementers</a>,<a href="#end-users">End Users</a>, and <a href="#other-actors">Other Actors</a>). This scoping specifically targets the requirements of <a href="#dom-registries">domain name registries</a> while acknowledging extensibility needs for possible future support of the requirements for <a href="#other-registries">other registry</a> types. The requirements are of both the current use of these directory services and the desired functionality based on input from relevant <a href="#forums">forums</a>. These requirements are not specific to any protocol. Terms used in the definition of requirements in this document may be found in the <a href="#glassory">glossary</a>.
</p>

<p>
The requirements captured in this document are for the purpose of designing technical specifications. The words used in this document for compliance with <a href="#RFC2119">RFC2119</a>[8] do not reference or specify policy and speak only to the capabilities in the derived technology. 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.
</p>

<a name="communities"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>2.&nbsp;Internet Registry Communities</h3>

<p>
The Internet registries are composed of various communities which provide scope for the requirements in this document. These communities can be generalized into the following categories: registries, registrars, implementers, end-users, and other actors.
</p>

<h4><a name="dom-registries">2.1</a>&nbsp;Domain Name System Registries</h4>

<h4><a name="domain-registries">2.1.1</a>&nbsp;Domain Registries</h4>

<p>
Domain registries are responsible for the registration of domains for use with <a href="#RFC1035">DNS</a>[2] and forward lookups (i.e. does not include the IN-ADDR.ARPA or IP6.ARPA domains). These registries have typically served two main domain functions: as the registry for a gTLD or as a registry for a ccTLD. In some instances, one entity will operate multiple TLD's, both of the gTLD and ccTLD type. A gTLD or ccTLD domain registry operator may be a governmental entity, non-governmental, non-commercial entity, or a commercial entity.
</p>

<p>
Some ccTLD's have second-level domain registrations similar in nature to gTLD's or have distinctly separate entities operating second-level domain registries similar in nature to gTLD's within the ccTLD.
</p>

<p>
Domain registries usually follow one of two models for conducting registrations of domains. The "thick" model is the more traditional model. In a "thick" domain registry, the registry contains both the operational data for the domain and the contact or <a href="#glassory">social data</a> for the domain. In this model, the registry is typically the interface to the domain registrant but may also interface with the domain registrant through domain registrars. The "thin" model domain registry contains only operational data for domains. In the "thin" model, contact or social data for the domain are maintained by a domain registrar.
</p>

<p>
Domain registries not described in this section (<a href="#domain-registries">Domain Registries</a>) are not the subject of this document and may have requirements that are out of scope for this subject matter.
</p>

<h4><a name="domain-registrars">2.1.2</a>&nbsp;Domain Registrars</h4>

<p>
Domain registrars accept domain registrations from registrants on behalf of domain registries, both "thick" and "thin". In a "thin" model registry/registrar system, a domain registrar maintains the contact and social data of a domain while the registry maintains the operational data of a domain. In a "thick" model registry/registrar system, a domain registrar passes both the operational data and contact data to the registry. Domain registrars may register a domain on behalf of a registrant in more than one domain registry.
</p>

<h4><a name="other-registries">2.2</a>&nbsp;Other Registries</h4>

<h4><a name="rir">2.2.1</a>&nbsp;Regional Internet Registries</h4>

<p>
Regional Internet Registries (RIR's) administer the allocation of IP address space and autonomous system numbers. Each RIR serves a specific geographic region, and collectively they service the entire Internet. Each RIR is a membership-based, non-profit organization that facilitates and implements global addressing policy based on the direction of their regional community. 
</p>

<h4><a name="lir">2.2.2</a>&nbsp;Local Internet Registries</h4>

<p>
Local Internet Registries (LIR's) and National Internet Registries (NIR's) are sub-registries of RIR's and coordinate the same functions of the RIR's for smaller, more specific geographic regions, sovereign nations, and localities.
</p>

<h4><a name="irr">2.2.3</a>&nbsp;Internet Routing Registries</h4>

<p>
Internet Routing Registries are routing policy databases. Their purpose is to provide information helpful in administering Internet routers. Frequently, the syntax and contents are defined by <a href="#RFC2622">RPSL</a>[5]. 
</p>

<p>
IRR's are operated by academic, commercial, governmental, and other types of organizations, including several of the RIR's. The contents of the databases vary and reflect the needs of the users directly served (e.g. an ISP may look up route entries added by their customers to decide whether to accept specific route advertisements they receive). 
</p>

<p>
Unlike RIR and domain registry data, IRR data is often duplicated between separate organizations. The IRR data has the unique characteristics of being largely available through other sources (i.e. it is advertised by the Internet routing protocols) and most often having a common data format, RPSL. 
</p>

<h4><a name="icc-reg">2.2.4</a>&nbsp;Incident Coordination Contact Registries</h4>

<p>
Incident coordination contact registries allow operators of network resources such as network infrastructure, network names, or network services to register contact information for the purpose of providing a means of incident notification. Using this type of registry, an operators of network resources are provided information for contacting the operator of another network resource from which an incident may be occurring.
</p>

<h4><a name="nerr-reg">2.2.5</a>&nbsp;Network Edge Resource Registries</h4>

<p>
Network edge resource registries provide specific information about "edge" resources. They are administered by the operators of the resources. Examples of such registries are <a href="#RFC2167">rwhois</a>[3] servers operated by networks to describe the assignment of address space allocated by RIR's or LIR's and <a href="#RFC0954">whois</a>[4] servers operated by networks to specifically announce routing policy of that network.
</p>

<h4><a name="implementers">2.3</a>&nbsp;Implementers</h4>

<p>
Implementers of client software are often either affiliated with large network operators, registry operators, or commercial entities offering value-added services, or are general citizens of the Internet. Much of the client software for use with the directory services of Internet registries is either freely available, open source, or both, or available as a service. Implementers of server software are often affiliated with operators or commercial entities specializing in the out-sourcing of development for Internet registries.
</p>

<h4><a name="end-users">2.4</a>&nbsp;End Users</h4>

<h4><a name="isp">2.4.1</a>&nbsp;Service Providers and Network Operators</h4>

<p>
Service providers and network operators provide connectivity, routing, and naming services to many other entities, some commercial and some non-commercial, both large and small. Their operational and administrative staff often interact with Internet registries on behalf of other end-users. Service providers and network operators interact with all of the Internet registry operators outlined in this document on a frequent and consistent basis. For example, network operators use the directory services of Internet registries to determine contact information for network resources that have technical problems.
</p>

<h4><a name="ipr">2.4.2</a>&nbsp;Intellectual Property Holders</h4>

<p>
Intellectual Property Holders have legal rights to the use of domain names based on copyright and trademark laws of various governments. They use the directory services of Internet registries, mostly domain registries and registrars, for purposes of maintaining and defending claims to domain names consistent with applicable laws and regulations.
</p>

<h4><a name="law">2.4.3</a>&nbsp;Law Enforcement</h4>

<p>
Law enforcement agencies use the directory services of Internet registries to find information used to carry out the enforcement of laws within their jurisdictions.
</p>

<h4><a name="ca">2.4.4</a>&nbsp;Certificate Authorities</h4>

<p>
Certificate authorities use the directory services of Internet registries as part of their verification process when issuing certificates for Internet named hosts.
</p>

<h4><a name="dns-users">2.4.5</a>&nbsp;DNS Users</h4>

<p>
Users of the Internet have client software that resolves domain names to IP addresses. Often when trouble occurs in the resolution process of DNS, these users trouble shoot system problems with the aid of information from the directory services of Internet registries.
</p>

<h4><a name="domain-registrants">2.4.6</a>&nbsp;Domain Registrants</h4>

<p>
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.
</p>

<h4><a name="other-actors">2.5</a>&nbsp;Other Actors</h4>

<p>
Requirements must also consider the positions and policies of other actors on the use of Internet registry directory services by other actors. These actors include governments, non-governmental policy-setting bodies, and other non-governmental organizations.
</p>

<a name="functional-requirements"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>3.&nbsp;Functional Requirements</h3>

<p>
Functional requirements describe an overall need or process for which the directory service is used by an Internet registry to fulfill its obligations to provide access to its respective customers, members, or other constituents. This section makes reference to terms and definitions declared in <a href="#glassory">Glossary</a>. This section makes use of the term "service" to denote the set of functions to be provided by, and the expected behavior of, software built to meet these requirements in one or more protocols.
</p>

<p>
These requirements are for the purpose of designing a technical specification. The words used in this section are for compliance with <a href="#RFC2119">RFC2119</a>[8], do not reference or specify policy, and speak only to the capabilities in the derived technology.
</p>

<h4><a name="common-functions">3.1</a>&nbsp;Base Functions</h4>

<p>
This section describes basic service requirements for an Internet registry service for any of the registries (<a href="#dom-registries">domain name registries</a> and <a href="#other-registries">other registries</a>). Additional requirements, specific to domain registries, are described in <a href="#domain-functions">Domain Specific Functions</a>.
</p>

<h4><a name="mining-prev">3.1.1</a>&nbsp;Mining Prevention</h4>

<p>
The service MUST have a mechanism to limit the amount of data that may be accessed. The service MAY have different limits for different types of data, as well as for authenticated and non-authenticated entities. The service SHOULD be capable of expressing to the client these access limitations based on queries per session per unit of time, queries per source IP address per unit of time, and total queries from all client sessions per unit of time. The service SHOULD be able to limit the amount of data based on the above types of limitations.
</p>

<h4><a name="min-tech-reinvent">3.1.2</a>&nbsp;Minimal Technical Reinvention</h4>

<p>
The service MUST NOT employ unique technology solutions for all aspects and layers above the network and transport layers of the total service solution and SHOULD make use of existing technology standards where applicable. The service MUST employ the use of network and transport layer standards as defined by the Internet Engineering Task Force. The service MUST define one or more transport mechanisms for mandatory implementation.
</p>

<h4><a name="pred-stand-expr">3.1.3</a>&nbsp;Standard and Extensible Schemas</h4>

<p>
The service MUST define standard schemas for the exchange of data needed to implement the functionality in this document. In addition, there MUST be a means to allow the use of schemas not defined by the needs of this document. Both types of schemas MUST use the same schema language.
</p>

<h4><a name="level-access">3.1.4</a>&nbsp;Level of Access</h4>

<p>
The service MUST allow the classification of data as being either privileged or non-privileged, for the purpose of restricting access to privileged data. Note that this requirement makes no assumption or prescription as to what data (social or operational) might be considered privileged, but merely provides the ability to make the classification as necessary.
</p>

<p>
The service MUST be capable of serving both privileged and non-privileged data.
</p>

<p>
The service MUST be capable of authenticating privileged entities and ensuring that only those entities have access to both privileged and non-privileged data.
</p>

<p>
The service MUST be capable of providing access to non-privileged data without requiring authentication of any type (i.e. anonymous access).
</p>

<h4><a name="client-proc">3.1.5</a>&nbsp;Client Processing</h4>

<p>
The service MUST be capable of allowing machine parsable requests and responses.
</p>

<h4><a name="entity-ref">3.1.6</a>&nbsp;Entity Referencing</h4>

<p>
There MUST be a mechanism for an entity contained within a server to be referenced uniquely by an entry in another server.
</p>

<h4><a name="decentral">3.1.7</a>&nbsp;Decentralization</h4>

<p>
The service MUST be decentralized in design and principle and MUST NOT require the aggregation of data to a central repository, server, or entity. The service MAY allow for the optional aggregation of data indexes or hints. The service MUST NOT require aggregation of data indexes or hints.
</p>

<h4><a name="queyr-access">3.1.8</a>&nbsp;Query of Access Levels</h4>

<p>
If a query cannot yield a valid response due to insufficient permissions, the service MUST provide the client with an error response indicating this condition. The service SHOULD NOT provide a mechanism allowing a client to determine if a query will be denied before the query is submitted.
</p>

<p>
It is the intent of this requirement for clients to learn of inadequate permission status for a query only after the query has been submitted. Operating modes allowing a client to predetermine the queries that will or will not be denied are not encouraged for security considerations.
</p>

<h4><a name="domain-functions">3.2</a>&nbsp;Domain Specific Functions</h4>

<p>
These functions describe requirements specifically needed by <a href="#domain-registries">domain registries</a> and <a href="#domain-registrars">domain registrars</a>. Requirements specific to <a href="#other-registries">other registries</a> MUST be specified separately. No compliant service entity is required to support the functions required by every registry type.
</p>

<h4><a name="contact-lookup">3.2.1</a>&nbsp;Contact Lookup</h4>

<p>
The service MUST allow access to social data of contact entities given a unique reference to the contact entity.
</p>

<h4><a name="ns-lookup">3.2.2</a>&nbsp;Nameserver Lookup</h4>

<p>
The service MUST allow access to operational and social data of a nameserver given the fully-qualified host name or IP address of a nameserver.
</p>

<h4><a name="dom-stat-lookup">3.2.3</a>&nbsp;Domain Status Lookup</h4>

<p>
The service MUST provide access to the status of a domain given the domain's fully qualified name. This status MUST indicate the activation status of the domain. The activation status is the same as would be available in <a href="#dom-info-lookup">Domain Information Lookup</a>.
</p>

<h4><a name="dom-registrant-search">3.2.4</a>&nbsp;Domain Registrant Search</h4>

<p>
The service MUST provide the capability of searching for registrants by exact name match or a reasonable name subset. The service MAY provide limits to the number of results from this search to alleviate performance or comply with <a href="#mining-prev">Mining Prevention</a>. If the service limits the number of results from this search to alleviate performance, it MUST provide the client with a response indicating this condition. If the service limits the number of results from this search to comply with <a href="#mining-prev">Mining Prevention</a>, it MUST NOT provide the client with a response indicating this condition.
</p>

<p>
The service MUST provide a mechanism to distribute this search across all applicable domain registries and registrars. The service SHOULD have a means to narrow the scope of a search to a specific TLD. The service MUST be able to specify to the client an empty result set should the search yield no results.
</p>

<h4><a name="dom-info-lookup">3.2.5</a>&nbsp;Domain Information Lookup</h4>

<p>
The service MUST provide access to operational and social data specific to a domain given the domain's fully qualified name (FQDN). This information SHOULD include the following:
<ul class="text">

<li>
activation status
</li>

<li>
registrant name and contact data
</li>

<li>
hosting nameservers
</li>

<li>
technical, billing or other entity types associate with the domain and their relevant contact data, if any exist
</li>

<li>
the name of or a reference to the registry delegating the domain
</li>

<li>
the name of or a reference to the registrar for the domain, if one exists
</li>

</ul>

</p>

<h4><a name="ns-search">3.2.6</a>&nbsp;Nameserver Search</h4>

<p>
The service MAY allow the ability to list all domains hosted by a specific nameserver given the fully-qualified host name or IP address, if applicable, of the nameserver. The service MAY provide a mechanism to distribute this search across all applicable domain registries and registrars.
</p>

<h4><a name="escrow">3.2.7</a>&nbsp;Escrow Support</h4>

<p>
The service MUST provide a means to escrow data of domain registrars to an escrow entity using a common schema. This escrow capability SHOULD be "off-line" and "out-of-band" from the normal operations of the service.
</p>

<h4><a name="auth-dist">3.2.8</a>&nbsp;Authentication Distribution</h4>

<p>
The service MUST be capable of allowing a centralized authority entity the means to distribute authentication information of entities accessing the service. The service MUST not require all Internet registries to participate in distributed authentication and SHOULD allow the participation by an Internet registry in distributed authentication by many centralized authority entities.
</p>

<h4><a name="dom-name-search">3.2.9</a>&nbsp;Domain Name Search</h4>

<p>
The service MUST allow searching for domains by exact name match or a reasonable subset of a domain name. The service MAY provide limits to the number of results from this search to alleviate performance or comply with <a href="#mining-prev">Mining Prevention</a>. If the service limits the number of results from this search to alleviate performance, it MUST provide the client with a response indicating this condition. If the service limits the number of results from this search to comply with <a href="#mining-prev">Mining Prevention</a>, it MUST NOT provide the client with a response indicating this condition.
</p>

<p>
The service MUST provide a mechanism to distribute this search across all applicable domain registries and registrars. There should be a means to narrow this search based on a TLD. 
</p>

<p>
The search mechanism SHOULD provide for differences in domain names between the native representation and the canonical form existing in the registry.
</p>

<h4><a name="domain-dns-ref">3.2.10</a>&nbsp;DNS Label Referencing</h4>

<p>
The service MUST use <a href="#RFC1035">DNS</a>[2] to determine the authoritative source of information about domain names. It is the intention of this requirement that a client be able to determine via DNS and query the servers or set of servers of the domain registry delegating the domain name, the domain registrar responsible for registering the domain name if one is applicable, and the domain registrant of the domain name. The service SHOULD provide procedures or mechanisms to allow this determination if it cannot be done using DNS.
</p>

<h4><a name="dist-for-domain-types">3.2.11</a>&nbsp;Distribution for Domain Registry Types</h4>

<p>
The service MUST allow for the various registration distribution models of domain registry types described in <a href="#domain-registries">Domain Registries</a> while complying with <a href="#decentral">Decentralization</a>.
</p>

<a name="feature-requirements"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>4.&nbsp;Feature Requirements</h3>

<p>
Feature requirements describe the perceived need derived from the functional requirements for specific technical criteria of the directory service. This section makes references to terms and definitions declared in <a href="#glassory">Glossary</a> . This section uses the term "service" to denote the set of features to be provided by, and the expected behavior of, software built to meet these requirements in one or more protocols.
</p>

<p>
These requirements are for the purpose of designing a technical specification. The words used in this section are for compliance with <a href="#RFC2119">RFC2119</a>[8], do not reference or specify policy, and speak only to the capabilities in the derived technology.
</p>

<h4><a name="client-auth">4.1</a>&nbsp;Client Authentication</h4>

<p>
Entities accessing the service (users) MUST be provided a mechanism for passing credentials to a server for the purpose of authentication.
</p>

<h4><a name="referrals">4.2</a>&nbsp;Referrals</h4>

<p>
To distribute queries for search continuations and to issue entity references, the service MUST provide a referral mechanism.
</p>

<h4><a name="common-ref">4.3</a>&nbsp;Common Referral Mechanism</h4>

<p>
To distribute queries for search continuation and to issue entity references, the service MUST define a common referral scheme and syntax.
</p>

<h4><a name="structure">4.4</a>&nbsp;Structured Queries and Responses</h4>

<p>
To provide for machine consumption as well as human consumption, the service MUST employ structured queries and responses.
</p>

<h4><a name="existing-schema">4.5</a>&nbsp;Existing Schema Language</h4>

<p>
To provide structured queries and responses and allow for minimal technological reinvention, the service MUST employ a pre-existing schema language.
</p>

<h4><a name="defined-schemas">4.6</a>&nbsp;Defined Schemas</h4>

<p>
To provide for machine consumption as well as human consumption, the service MUST define schemas for use by the structured queries and responses.
</p>

<h4><a name="serialization">4.7</a>&nbsp;Serialization Definition</h4>

<p>
To provide for data escrow and allow for minimal technological reinvention, the service MUST employ a pre-existing serialization specification.
</p>

<a name="internationalization-con"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>5.&nbsp;Internationalization Considerations</h3>

<p>
Requirements defined in this document MUST consider the best practices spelled out in <a href="#RFC2277">[6]</a>.
</p>

<a name="iana-con"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>6.&nbsp;IANA Considerations</h3>

<p>
IANA consideration for any service meeting these requirements will depend upon the technologies chosen and MUST be specified by any document describing such a service.
</p>

<a name="security-con"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>7.&nbsp;Security Considerations</h3>

<p>
This document contains requirements for the validation of authenticated entities and the access of authenticated entities compared with the access of non-authenticated entities. This document does not define the mechanism for validation of authenticated entities. Requirements defined in this document MUST allow for the implementation of this mechanism according best common practices.
</p>

<p>
The requirement in <a href="#level-access">Level of Access</a> must be weighed against other requirements specifying search or lookup capabilities.
</p>

<p>
In addition, this document contains requirements for referrals and entity references. Client implementations based on these requirements SHOULD take proper care in the safe-guarding of credential information when resolving referrals or entity references according to best common practices.
</p>
<a name="rfc.references"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>
References</h3>
<table width="99%" border="0">
<tr><td class="author-text" valign="top"><b><a name="RFC2251">[1]</a></b></td>
<td class="author-text"><a href="mailto:M.Wahl@critical-angle.com">Wahl, M.</a>, <a href="mailto:howes@netscape.com">Howes, T.</a> and <a href="mailto:S.Kille@isode.com">S. Kille</a>, "<a href="ftp://ftp.isi.edu/in-notes/rfc2251.txt">Lightweight Directory Access Protocol (v3)</a>", RFC 2251, December 1997.</td></tr>
<tr><td class="author-text" valign="top"><b><a name="RFC1035">[2]</a></b></td>
<td class="author-text"><a href="mailto:">Mockapetris, P.</a>, "<a href="ftp://ftp.isi.edu/in-notes/rfc1035.txt">Domain names - implementation and specification</a>", STD 13, RFC 1035, November 1987.</td></tr>
<tr><td class="author-text" valign="top"><b><a name="RFC2167">[3]</a></b></td>
<td class="author-text"><a href="mailto:scottw@rwhois.net">Williamson, S.</a>, <a href="mailto:markk@internic.net">Kosters, M.</a>, <a href="mailto:davidb@rwhois.net">Blacka, D.</a>, <a href="mailto:jasdips@rwhois.net">Singh, J.</a> and <a href="mailto:kzeil@rwhois.net">K. Zeilstra</a>, "<a href="ftp://ftp.isi.edu/in-notes/rfc2167.txt">Referral Whois (RWhois) Protocol V1.5</a>", RFC 2167, June 1997.</td></tr>
<tr><td class="author-text" valign="top"><b><a name="RFC0954">[4]</a></b></td>
<td class="author-text">Harrenstien, K., Stahl, M. and E. Feinler, "<a href="ftp://ftp.isi.edu/in-notes/rfc954.txt">NICNAME/WHOIS</a>", RFC 954, October 1985.</td></tr>
<tr><td class="author-text" valign="top"><b><a name="RFC2622">[5]</a></b></td>
<td class="author-text"><a href="mailto:cengiz@isi.edu">Alaettinoglu, C.</a>, <a href="mailto:curtis@avici.com">Villamizar, C.</a>, <a href="mailto:epg@home.net">Gerich, E.</a>, <a href="mailto:David.Kessens@qwest.net">Kessens, D.</a>, <a href="mailto:meyer@antc.uoregon.edu">Meyer, D.</a>, <a href="mailto:tbates@cisco.com">Bates, T.</a>, <a href="mailto:dfk@ripe.net">Karrenberg, D.</a> and <a href="mailto:marten@BayNetworks.com">M. Terpstra</a>, "<a href="ftp://ftp.isi.edu/in-notes/rfc2622.txt">Routing Policy Specification Language (RPSL)</a>", RFC 2622, June 1999.</td></tr>
<tr><td class="author-text" valign="top"><b><a name="RFC2277">[6]</a></b></td>
<td class="author-text"><a href="mailto:Harald.T.Alvestrand@uninett.no">Alvestrand, H.T.</a>, "<a href="ftp://ftp.isi.edu/in-notes/rfc2277.txt">IETF Policy on Character Sets and Languages</a>", BCP 18, RFC 2277, January 1998.</td></tr>
<tr><td class="author-text" valign="top"><b><a name="RFC2535">[7]</a></b></td>
<td class="author-text"><a href="mailto:dee3@us.ibm.com">Eastlake, D.</a>, "<a href="ftp://ftp.isi.edu/in-notes/rfc2535.txt">Domain Name System Security Extensions</a>", RFC 2535, March 1999.</td></tr>
<tr><td class="author-text" valign="top"><b><a name="RFC2119">[8]</a></b></td>
<td class="author-text"><a href="mailto:-">Bradner, S.</a>, "<a href="ftp://ftp.isi.edu/in-notes/rfc2119.txt">Key words for use in RFCs to Indicate Requirement Levels</a>", BCP 14, RFC 2119, March 1997.</td></tr>
</table>

<a name="rfc.authors"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Author's Address</h3>
<table width="99%" border="0" cellpadding="0" cellspacing="0">
<tr><td class="author-text">&nbsp;</td>
<td class="author-text">Andrew L. Newton</td></tr>
<tr><td class="author-text">&nbsp;</td>
<td class="author-text">VeriSign, Inc.</td></tr>
<tr><td class="author-text">&nbsp;</td>
<td class="author-text">21345 Ridgetop Circle</td></tr>
<tr><td class="author-text">&nbsp;</td>
<td class="author-text">Sterling, VA  20166</td></tr>
<tr><td class="author-text">&nbsp;</td>
<td class="author-text">USA</td></tr>
<tr><td class="author" align="right">Phone:&nbsp;</td>
<td class="author-text">+1 703 948 3382</td></tr>
<tr><td class="author" align="right">EMail:&nbsp;</td>
<td class="author-text"><a href="mailto:anewton@verisignlabs.com">anewton@verisignlabs.com</a></td></tr>
<tr><td class="author" align="right">URI:&nbsp;</td>
<td class="author-text"><a href="http://www.verisignlabs.com/">http://www.verisignlabs.com/</a></td></tr>
</table>

<a name="glassory"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Appendix A.&nbsp;Glossary</h3>

<p>

<ul class="text">

<li>
TLD: Initials for "top level domain." Referes to domains in <a href="#RFC1035">DNS</a>[2]that are hierarchically at the level just beneath the root.
</li>

<li>
ccTLD: Initials for "country code top level domain." TLD's which use one of the two character country codes defined by ISO.
</li>

<li>
gTLD: Initials for "generic top level domain." TLD's that do not use one of the two character country codes defined by ISO.
</li>

<li>
social data: Data containing names and contact information (i.e. postal addresses, phone numbers, e-mail addresses) of humans or legal entities.
</li>

<li>
operational data: Data necessary to the operation of networks and network related services and items.
</li>

<li>
RIR: Initials for "regional Internet registry."
</li>

<li>
IRR: Initials for "Internet routing registry."
</li>

<li>
authenticated entity: A person, or person acting on behalf of an organization, who has provided validatable credentials of identification via client software to the directory service of an Internet registry.
</li>

<li>
non-authenticated entity: A person, or person acting on behalf of an organization, who has not provided validatable credentials of identification via client software to the directory service of an Internet registry.
</li>

<li>
privileged entity: A person, or person acting on behalf of an organization, with authorization to access data.
</li>

<li>
non-privileged entity: A person, or person acting on behalf on an organization, with no authorization to access data.
</li>

<li>
privileged data: Data accessible by a privileged entities.
</li>

<li>
non-privileged data: Data accessible by privileged entities and non-privileged entities.
</li>

<li>
forward lookup: a DNS lookup where a domain name is resolved to an IP address.
</li>

<li>
reverse lookup: a DNS lookup where an IP address is resolved to a domain name.
</li>

<li>
mining: In the context of this document, this term is specific to data mining. This is a methodical process to obtain the contents of directory service, usually as much as possible, not relevant to any immediate need. Data mining is often not a practice welcomed by registry operators.
</li>

</ul>

</p>

<a name="acknowledgements"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Appendix B.&nbsp;Acknowledgements</h3>

<h4><a name="forums">B.1</a>&nbsp;Forums</h4>

<p>
The proceedings of the following public forums were used as input to the scope and requirements for this document: 
<ul class="text">

<li>
<a href="http://www.ietf.org/proceedings/00dec/00dec-41.htm">whois BOF of the 49th IETF</a>; December 10-15, 2000; San Diego, CA, USA
</li>

<li>
<a href="http://www.ietf.org/proceedings/01aug/51-40.htm">whoisfix BOF of the 51st IETF</a>; August 5-10, 2001; London, England
</li>

<li>
<a href="http://www.uwho.verisignlabs.com/Final-WhoIsPanel-Aug15-Resume.pdf">First UWho Consultation</a>; August 15, 2001; Washington, DC, USA
</li>

<li>
Second UWho Consultation; November 15, 2001; Marina del Rey, CA, USA
</li>

<li>
Third UWho Consultation; November 19, 2001; Washington, DC, USA
</li>

<li>
DNR WG of RIPE 40, October 1-5, 2001; Praque, Czech Republic
</li>

<li>
<a href="http://www.ripe.net/ripe/meetings/archive/ripe-40/minutes/min_database.html">Database WG of RIPE 40</a>; October 1-5, 2001; Praque, Czech Republic
</li>

<li>
<a href="http://www.nanog.org/mtg-0110/lookup.html">General Session of NANOG 23</a>; October 21-23; Oakland, CA, USA
</li>

<li>
DNR WG of RIPE 41, January 14-18, 2002; Amsterdam, The Netherlands
</li>

<li>
Database WG of RIPE 41, January 14-18, 2002; Amsterdam, The Netherlands
</li>

<li>
NANOG 24 Universal Whois BOF, February 10-12, 2002; Miami, Florida
</li>

<li>
CENTR General Assembly, February 21-22, 2002; Rambouillet, France
</li>

<li>
CRISP BOF of the 53rd IETF, March 17-22, 2002, Minneapolis, Minnesota, USA
</li>

</ul>

</p>

<h4><a name="working-group">B.2</a>&nbsp;Working Group</h4>

<p>
This document is a work item of the Cross-Registry Internet Service Protocol (CRISP) Working Group in the Applications Area of the IETF. Discussions for this working group are held on the email list ietf-not43@lists.verisignlabs.com. To subscribe to this email list, send email to ietf-not43-request@lists.verisignlabs.com with a subject line of "subscribe". Archives of this list may be found out http://lists.verisignlabs.com/pipermail/ietf-not43/.
</p>

<h4><a name="contributions">B.3</a>&nbsp;Contributions</h4>

<p>
Comments, suggestions, and feedback of significant substance have been provided by Leslie Daigle, Mark Kosters, Ted Hardie, Shane Kerr, and Cathy Murphy.
</p>
<a name="rfc.copyright"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>
<h3>Full Copyright Statement</h3>
<p class='copyright'>
Copyright (C) The Internet Society (2002). All Rights Reserved.</p>
<p class='copyright'>
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.</p>
<p class='copyright'>
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.</p>
<p class='copyright'>
This document and the information contained herein is provided on an
&quot;AS IS&quot; 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.</p>
<h3>Acknowledgement</h3>
<p class='copyright'>
Funding for the RFC editor function is currently provided by the
Internet Society.</p>
</font></body></html>

--------------10D531E406820549FCF3A484--


From leslie@thinkingcat.com  Mon Aug  5 19:00:40 2002
From: leslie@thinkingcat.com (Leslie Daigle)
Date: Mon, 05 Aug 2002 14:00:40 -0400
Subject: [Ietf-not43] requirements diffs
References: <3D4EA500.E06B161A@ecotroph.net>
Message-ID: <3D4EBD48.495EC430@thinkingcat.com>

Howdy,

Some questions & comments -- in-line:

Andrew Newton wrote:
> 3.2.4 Domain Registrant Search
> 
>    The service MUST provide the capability of searching for
> registrants
>    by exact name match or a reasonable name subset. The service MAY
>    provide limits to the number of results from this search to
>    alleviate performance or comply with Section 3.1.1. If the service
>    limits the number of results from this search to alleviate
>    performance, it MUST provide the client with a response indicating
>    this condition. If the service limits the number of results from
>    this search to comply with Section 3.1.1, it MUST NOT provide the
>    client with a response indicating this condition.

s/alleviate/improve/ or s/performance/performance bottlenecks/ 

WRT the actual requirements -- I'm not sure I understand the motivation
for when the service MUST or MUST NOT provide an indication
that it has truncated the reply.  In particular, I'm not sure I
agree that it's valuable for the service to fail silently when
something that is perceived to be data mining occurs.  It may
have been a badly-formed query, not a deliberate attempt to
mine.  Clients that submit badly-formed queries ought to be given
the indication that they didn't get the full result set & therefore
ought to reconsider the query.  Shouldn't they?


> 3.2.9 Domain Name Search
> 
>    The service MUST allow searching for domains by exact name match or
>    a reasonable subset of a domain name. The service MAY provide
> limits
>    to the number of results from this search to alleviate performance
>    or comply with Section 3.1.1. If the service limits the number of
>    results from this search to alleviate performance, it MUST provide
>    the client with a response indicating this condition. If the
> service
>    limits the number of results from this search to comply with
> Section
>    3.1.1, it MUST NOT provide the client with a response indicating
>    this condition.

Same comments as above.


>    The search mechanism SHOULD provide for differences in domain names
>    between the native representation and the canonical form existing
> in
>    the registry.

I don't think this is clear.  I believe this is speaking to the
fact that domain names will be registered using a 7-bit form (nameprep),
and the theory is to allow/require the service to store a different
representation (e.g., particular character set, encoding) of the
registered "name", as well as the name of the encoding + algorithm used
to transform it into UTF-8 before nameprep.


> 
> ---------------------
> 
> 3.2.10 DNS Label Referencing
> 
>    The service MUST use DNS[2] to determine the authoritative source
> of
>    information about domain names. It is the intention of this
>    requirement that a client be able to determine via DNS and query
> the
>    servers or set of servers of the domain registry delegating the

I think this last sentence is missing something; determine _what_
and query the servers?

>    domain name, the domain registrar responsible for registering the
>    domain name if one is applicable, and the domain registrant of the
>    domain name. The service SHOULD provide procedures or mechanisms to
>    allow this determination if it cannot be done using DNS.

I have probably missed a step, but I don't understand why the
service SHOULD do this, if it MUST provide the DNS route -- or
is the point that it should have a backup plan in case there are
transient or configuration errors with DNS at the moment a query is
made?

Leslie.

-- 

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

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

From anewton@ecotroph.net  Mon Aug  5 19:38:16 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Mon, 05 Aug 2002 14:38:16 -0400
Subject: [Ietf-not43] requirements diffs
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com>
Message-ID: <3D4EC618.68246376@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-19274-1028573289-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Leslie Daigle wrote:
> 
> Some questions & comments -- in-line:

ditto.

> > 3.2.4 Domain Registrant Search
> >
> >    The service MUST provide the capability of searching for
> > registrants
> >    by exact name match or a reasonable name subset. The service MAY
> >    provide limits to the number of results from this search to
> >    alleviate performance or comply with Section 3.1.1. If the service
> >    limits the number of results from this search to alleviate
> >    performance, it MUST provide the client with a response indicating
> >    this condition. If the service limits the number of results from
> >    this search to comply with Section 3.1.1, it MUST NOT provide the
> >    client with a response indicating this condition.
> 
> s/alleviate/improve/ or s/performance/performance bottlenecks/

Works for me.

> WRT the actual requirements -- I'm not sure I understand the motivation
> for when the service MUST or MUST NOT provide an indication
> that it has truncated the reply.  In particular, I'm not sure I
> agree that it's valuable for the service to fail silently when
> something that is perceived to be data mining occurs.  It may
> have been a badly-formed query, not a deliberate attempt to
> mine.  Clients that submit badly-formed queries ought to be given
> the indication that they didn't get the full result set & therefore
> ought to reconsider the query.  Shouldn't they?

If the service truncates the results for performance reasons, you can an
indication of this condition.

If the service truncates the results because it believes you are data
mining, you get no indication of this condition.  This makes it more
difficult, though not impossible, to determine if all the results have
been returned.

> >    The search mechanism SHOULD provide for differences in domain names
> >    between the native representation and the canonical form existing
> > in
> >    the registry.
> 
> I don't think this is clear.  I believe this is speaking to the
> fact that domain names will be registered using a 7-bit form (nameprep),
> and the theory is to allow/require the service to store a different
> representation (e.g., particular character set, encoding) of the
> registered "name", as well as the name of the encoding + algorithm used
> to transform it into UTF-8 before nameprep.

You are correct, it isn't clear.  That text seems to acknowledge this as
an issue and at the same time defer any decision on what to do for some
other time or place.

I think we as a working group need to decide what will be done with
internationalized domain names.  Unlike the IDN folks, we do have the
advantage of having a NEW protocol that can have things like fields
indicating language and so forth.  Suggestions?

> > 3.2.10 DNS Label Referencing
> >
> >    The service MUST use DNS[2] to determine the authoritative source
> > of
> >    information about domain names. It is the intention of this
> >    requirement that a client be able to determine via DNS and query
> > the
> >    servers or set of servers of the domain registry delegating the
> 
> I think this last sentence is missing something; determine _what_
> and query the servers?
> 
> >    domain name, the domain registrar responsible for registering the
> >    domain name if one is applicable, and the domain registrant of the
> >    domain name. The service SHOULD provide procedures or mechanisms to
> >    allow this determination if it cannot be done using DNS.
> 
> I have probably missed a step, but I don't understand why the
> service SHOULD do this, if it MUST provide the DNS route -- or
> is the point that it should have a backup plan in case there are
> transient or configuration errors with DNS at the moment a query is
> made?

Though transient or configuration errors are also good reasons, I was
mostly thinking that some delegation points will never have this type of
information in DNS in things like SRV records (obviously in NS records).

-andy
--=_zark-19274-1028573289-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA1MTgzODE2WjAjBgkqhkiG9w0BCQQxFgQUBwuqvocifhLOdTqvHgtxjCfSibAwUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEA1oKpnea9CJR8uq+S
t8xVTmtFCvgxfF2xgCK0Kzhlr9H0YStsRjtBap7Qjvo0Y4dmvTQItUhtFwlchhPFGHxsDIl8
UMGJGY62bf1T2n3gOX1GYe2Ucr+Pc+2Alanv8fUzlsdNdNCl/gvUUAwKds5NdC1Sl5mlPKmV
nucCBj8g50gZEmKX1By9qL8A6relozxMwKunFLjUOTIj4xvbFi8+Igil7Ej47FzDlYNGMvan
SmTdbSHR7oJ52HJi1roVLostc/v4hqusYKYjuiN3HT2dEwXynq7heEzfgw1FFiacsUB8BvtN
+/FJaRN8wLSo5s4GaR2Up7jbdkQoGr/8G66tFw==
--=_zark-19274-1028573289-0001-2--

From leslie@thinkingcat.com  Mon Aug  5 20:58:19 2002
From: leslie@thinkingcat.com (Leslie Daigle)
Date: Mon, 05 Aug 2002 15:58:19 -0400
Subject: Data mining v. poorly-framed queries [was Re: [Ietf-not43] requirements
 diffs]
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net>
Message-ID: <3D4ED8DB.8FC1A5C6@thinkingcat.com>


On the specific point of whether the service MUST NOT return
an error response indicating that the result list was truncated,
I think it would be useful to hear more from the WG as to which
is most important, or how can we reconcile:

	. mining prevention.  If no error message is given, the
	  hypothesis is that a mining client will not attempt to
	  revise the query to pick up where the results left off
	  (i.e., if a query was for "AAA*", and the results 
	  included "AAAA" through "AAAM", query for "AAAN*")

	. accurate responses to legitimate queries.  If no error
	  message is given, a legitimate queryant will not
	  know that they have in fact missed data and should re-frame
	  their query in a more precise fashion (i.e., if they
	  asked for "AAA*", and got a truncated response, they
	  should specify more, e.g., "AAARDVAR*").

Although I respect the mining prevention requirement, I'm not
personally pleased with silent failure.  I think the examples
I've given above are pretty trivial -- it's less obvious if
multiple criteria are involved (and at this instant, I don't
recall if we have requirements to support such).  

Leslie.

Andrew Newton wrote:
> > > 3.2.4 Domain Registrant Search
> > >
> > >    The service MUST provide the capability of searching for
> > > registrants
> > >    by exact name match or a reasonable name subset. The service MAY
> > >    provide limits to the number of results from this search to
> > >    alleviate performance or comply with Section 3.1.1. If the service
> > >    limits the number of results from this search to alleviate
> > >    performance, it MUST provide the client with a response indicating
> > >    this condition. If the service limits the number of results from
> > >    this search to comply with Section 3.1.1, it MUST NOT provide the
> > >    client with a response indicating this condition.
> >
> > s/alleviate/improve/ or s/performance/performance bottlenecks/
> 
> Works for me.
> 
> > WRT the actual requirements -- I'm not sure I understand the motivation
> > for when the service MUST or MUST NOT provide an indication
> > that it has truncated the reply.  In particular, I'm not sure I
> > agree that it's valuable for the service to fail silently when
> > something that is perceived to be data mining occurs.  It may
> > have been a badly-formed query, not a deliberate attempt to
> > mine.  Clients that submit badly-formed queries ought to be given
> > the indication that they didn't get the full result set & therefore
> > ought to reconsider the query.  Shouldn't they?
> 
> If the service truncates the results for performance reasons, you can an
> indication of this condition.
> 
> If the service truncates the results because it believes you are data
> mining, you get no indication of this condition.  This makes it more
> difficult, though not impossible, to determine if all the results have
> been returned.

-- 

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

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

From ehall@ehsco.com  Mon Aug  5 21:50:39 2002
From: ehall@ehsco.com (Eric A. Hall)
Date: Mon, 05 Aug 2002 15:50:39 -0500
Subject: [Ietf-not43] requirements diffs
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net>
Message-ID: <3D4EE51F.7080203@ehsco.com>

on 8/5/2002 1:38 PM Andrew Newton wrote:
> Leslie Daigle wrote:

>>I don't think this is clear.  I believe this is speaking to the
>>fact that domain names will be registered using a 7-bit form (nameprep),
>>and the theory is to allow/require the service to store a different
>>representation (e.g., particular character set, encoding) of the
>>registered "name", as well as the name of the encoding + algorithm used
>>to transform it into UTF-8 before nameprep.
> 
> You are correct, it isn't clear.  That text seems to acknowledge this as
> an issue and at the same time defer any decision on what to do for some
> other time or place.
> 
> I think we as a working group need to decide what will be done with
> internationalized domain names.  Unlike the IDN folks, we do have the
> advantage of having a NEW protocol that can have things like fields
> indicating language and so forth.  Suggestions?

There are several different issues here. Are we talking about the resource
being queried for, the servers being queried, or both? With LDAP-WHOIS in
particular, there is the DIT domain (dc=label) plus the query string
(cn=domain). UTF-8 can be used wherever we want but if we use it for the
DIT parts then that affects the LDAP domainComponent matching syntax,
which is arguably out of scope. At the same time, having part of the
string be ASCII-compatible encoding (ACE) and another part be UTF-8 is
somewhat clumsy and dare-I-say error-prone.

Another related issue, are we talking about the UI or the protocol? Saying
that the input sequence should be converted before the query string is
built would make some sense as a minimalist approach.

On the other hand, do we want to mandate that all DITs *MUST* use the ACE
form in their directory trees? Who wants to look at ACE gobbledygoop in
their DIT, or worse be required to do it?

And so forth. Ugly stuff.

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


From anewton@ecotroph.net  Mon Aug  5 22:07:02 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Mon, 05 Aug 2002 17:07:02 -0400
Subject: [Ietf-not43] requirements diffs
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net> <3D4EE51F.7080203@ehsco.com>
Message-ID: <3D4EE8F6.3EEDC940@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-20634-1028582218-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Eric A. Hall" wrote:
> 
> There are several different issues here. Are we talking about the resource
> being queried for, the servers being queried, or both? 

I was assuming the resource which is being queried.  If we have to make
special arrangements for the servers being queried, then perhaps the IDN
WG has missed the mark.

> With LDAP-WHOIS in
> particular, there is the DIT domain (dc=label) plus the query string
> (cn=domain). UTF-8 can be used wherever we want but if we use it for the
> DIT parts then that affects the LDAP domainComponent matching syntax,
> which is arguably out of scope. At the same time, having part of the
> string be ASCII-compatible encoding (ACE) and another part be UTF-8 is
> somewhat clumsy and dare-I-say error-prone.

I agree.

> Another related issue, are we talking about the UI or the protocol? Saying
> that the input sequence should be converted before the query string is
> built would make some sense as a minimalist approach.
> 
> On the other hand, do we want to mandate that all DITs *MUST* use the ACE
> form in their directory trees? Who wants to look at ACE gobbledygoop in
> their DIT, or worse be required to do it?

I'm not sure which, as I'm not an expert in this internationalization
stuff.  My gut tells me that it could be done in the UI as you
suggested.  However, how does that work with partial-name searches?

> And so forth. Ugly stuff.

Again, agreed!

-andy
--=_zark-20634-1028582218-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA1MjEwNzAyWjAjBgkqhkiG9w0BCQQxFgQUffllu+3Lvt4cB3T891DpbR57nAUwUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAnfljWFOACxPwUWCr
Lz3l03umL+lTKnzwYZnLSviFjPA+JdXvFXjZkp74emVnyY/RPNxmF5tUtthy2S8EcWksTTjR
aoyPtBAjrh73FL53RXVZeO+JirLh8MOFyuo8ZfO7LxlnwFWMZgFZxFCEgkaQ72nf0/9fB3tU
Tubn+0EGepEmg1g2gMwj//ORoq7S35gmvR+qKGtVYmCsztAw1V6QcbtVuaSwREafpO+84Czr
2ZYD5uwZiNN2BpCItc26CknnEipSyEk36YGClJfbjoDuYxt1V4yu3AwqRh+vUWMlMLM6n4lM
cBFBtXQ2afxxnoAKV1lTLTpa4mjU9Jijtw4e9Q==
--=_zark-20634-1028582218-0001-2--

From anewton@ecotroph.net  Mon Aug  5 22:12:56 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Mon, 05 Aug 2002 17:12:56 -0400
Subject: [Ietf-not43] Re: Data mining v. poorly-framed queries [was Re: [Ietf-not43]
 requirements diffs]
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net> <3D4ED8DB.8FC1A5C6@thinkingcat.com>
Message-ID: <3D4EEA58.677B9AD7@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-20709-1028582569-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

After thinking about this some more, it has occured to me that perhaps
the wording for this section has actually crossed the line from "what
can be done" to "what must be done", despite our best intentions to
avoid stating policy.  Therefore, it must be reworked.

I think the right thing to do would be to stipulate that the protocols
have such a feature to notify the user of the truncation condition.  The
use of these notifications are, and in reality will be, site specific.

-andy

Leslie Daigle wrote:
> 
> On the specific point of whether the service MUST NOT return
> an error response indicating that the result list was truncated,
> I think it would be useful to hear more from the WG as to which
> is most important, or how can we reconcile:
> 
>         . mining prevention.  If no error message is given, the
>           hypothesis is that a mining client will not attempt to
>           revise the query to pick up where the results left off
>           (i.e., if a query was for "AAA*", and the results
>           included "AAAA" through "AAAM", query for "AAAN*")
> 
>         . accurate responses to legitimate queries.  If no error
>           message is given, a legitimate queryant will not
>           know that they have in fact missed data and should re-frame
>           their query in a more precise fashion (i.e., if they
>           asked for "AAA*", and got a truncated response, they
>           should specify more, e.g., "AAARDVAR*").
> 
> Although I respect the mining prevention requirement, I'm not
> personally pleased with silent failure.  I think the examples
> I've given above are pretty trivial -- it's less obvious if
> multiple criteria are involved (and at this instant, I don't
> recall if we have requirements to support such).
> 
> Leslie.
--=_zark-20709-1028582569-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA1MjExMjU2WjAjBgkqhkiG9w0BCQQxFgQUbL7k6ps3rUQZ9uqbrJgRR6GiHtgwUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAS5jQlsH7J6zgdlQ6
2q3aq16hSz7w6e0aySeSS5oBOiBvq1i/VhQuE8mCc3jFPg3ff8HPEf/4s47oZ7/h/FRAeSKR
zW0ivNEj/bK8NcNSVJdxjgvYhThzf/I8tOUA7TpkeJ3QrSIW+bwWnxciF/OzMRTCLSbLkN0H
zJVB367dxADoVN3APBpMhLAklSxsWoS5xs9JW+8aQHDNPa1lDglLL4zCkZOZ9plEO5d4eCEn
WtPUpP1zbUg9zU/K5aqcNu3XV7XJ2hf2HBVLn9NDJI8vja/tVyNO/Vs1p/iZP5+PDfUDB6Ol
xkiDXbN7NFRqugvzvvhnsp20/MMwuf3IYz/spg==
--=_zark-20709-1028582569-0001-2--

From ehall@ehsco.com  Tue Aug  6 00:45:22 2002
From: ehall@ehsco.com (Eric A. Hall)
Date: Mon, 05 Aug 2002 18:45:22 -0500
Subject: [Ietf-not43] requirements diffs
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net> <3D4EE51F.7080203@ehsco.com> <3D4EE8F6.3EEDC940@ecotroph.net>
Message-ID: <3D4F0E12.9050809@ehsco.com>

on 8/5/2002 4:07 PM Andrew Newton wrote:
> "Eric A. Hall" wrote:
>
>> There are several different issues here. Are we talking about the
>> resource being queried for, the servers being queried, or both?
>
> I was assuming the resource which is being queried.  If we have to make
>  special arrangements for the servers being queried, then perhaps the
> IDN WG has missed the mark.

I was speaking in the logical. In the case of LDAP-WHOIS, the DIT is used
to determine the servers. Unless there are rules which state how DITs are
to be mapped, there is significant potential for error. I think that these
rules are out of scope for us, unfortunately.

I'll look at the LDAP URL in depth at some point and figure out what our
options are. At the moment, I am pretty certain that all referenced domain
names will have to be ACE. This is unfortunate, since it means that the
DITs and the entries will also have to be ACE.

As to whether or not the IDN WG succeeded or not, keep in mind that the
only extra-IETF pressures were on the resell side. Thus, the IDN only
really had to devise a consistent encoding format so that everybody was
selling the same domain names, not so that users could actually use them.
Unfortunate but there you have it.

> I'm not sure which, as I'm not an expert in this internationalization
> stuff.  My gut tells me that it could be done in the UI as you
> suggested.  However, how does that work with partial-name searches?

No

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


From bortzmeyer@nic.fr  Tue Aug  6 07:49:57 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Tue, 6 Aug 2002 08:49:57 +0200
Subject: [Ietf-not43] Internationalization issues in the registry (Was: requirements diffs
In-Reply-To: <3D4EE8F6.3EEDC940@ecotroph.net>
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net> <3D4EE51F.7080203@ehsco.com> <3D4EE8F6.3EEDC940@ecotroph.net>
Message-ID: <20020806064957.GA9312@nic.fr>

On Mon, Aug 05, 2002 at 05:07:02PM -0400,
 Andrew Newton <anewton@ecotroph.net> wrote 
 a message of 97 lines which said:

> > which is arguably out of scope. At the same time, having part of the
> > string be ASCII-compatible encoding (ACE) and another part be UTF-8 is
> > somewhat clumsy and dare-I-say error-prone.
> 
> I agree.

I'm not sure we will have the choice. For the domain names, we have to
stick with IDNA and ACE. For the social information (names and addresses
of the contacts, for instance), unless we want to force them to go
through nameprep + ACE, we will use Unicode. So, even in the
registry's database, we will have the problem.

The only other solutions I see are:

1) storing the original (Unicode) form of the domain name as well as
the ACE. It requires a change in the registrar-registry protocol
(draft-ietf-provreg-epp-domain-04.txt contains nothing about
transmitting the original form).

2) As I said before, using nameprep + ACE with contact information. I
would disagree. ACE was choosen for specific reasons (the ability to
use existing nameserver sofwtare), we should not push that hack too
far.

> I'm not sure which, as I'm not an expert in this internationalization
> stuff.  My gut tells me that it could be done in the UI as you
> suggested.

For the domain names, it seems the only reasonable choice, and
consistent with IDNA.

>  However, how does that work with partial-name searches?

As soon as you move from US-ASCII, "fuzzy" searches (including
partial-name but also accent-insensitive searches, etc) become very
difficult to specify because each language has its own rules.

If we want to stay away from registry policy, I suggest to accept
solution 1 ("the registry MAY store the original form of the IDN and
MAY accept queries based on the original form") but not to mandate it.


From patrick@gandi.net  Tue Aug  6 11:39:20 2002
From: patrick@gandi.net (Patrick)
Date: Tue, 6 Aug 2002 12:39:20 +0200
Subject: [Ietf-not43] Internationalization issues in the registry (Was: requirements diffs
In-Reply-To: <20020806064957.GA9312@nic.fr>
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net> <3D4EE51F.7080203@ehsco.com> <3D4EE8F6.3EEDC940@ecotroph.net> <20020806064957.GA9312@nic.fr>
Message-ID: <20020806103920.GR21513@nohope.patoche.org>

On Tue, Aug 06, 2002 at 08:49:57AM +0200, Stephane Bortzmeyer took time to write:
> On Mon, Aug 05, 2002 at 05:07:02PM -0400,
>  Andrew Newton <anewton@ecotroph.net> wrote 
>  a message of 97 lines which said:
> 
> > > which is arguably out of scope. At the same time, having part of the
> > > string be ASCII-compatible encoding (ACE) and another part be UTF-8 is
> > > somewhat clumsy and dare-I-say error-prone.
> > 
> > I agree.
> 
> I'm not sure we will have the choice. For the domain names, we have to
> stick with IDNA and ACE. For the social information (names and addresses

I disagree. IDNA & ACE are used instead of UTF-8 to be able to have
iDNS right now, that is without changing all software (name servers,
resolvers library, etc...)
For a new protocol, I see no reason to use ACE.

> 1) storing the original (Unicode) form of the domain name as well as
> the ACE. It requires a change in the registrar-registry protocol
> (draft-ietf-provreg-epp-domain-04.txt contains nothing about
> transmitting the original form).

Based on XML, EPP is already using UTF-8.
It includes specific details about internationalized strings in
contact details (they do not need to use ACE at all, hopefully).

I do not think this requires any change.
I quote:
2.1 Domain and Host Names   
  The syntax for domain and host names described in this document
  MUST  conform to [RFC952] as updated by [RFC1123].  These
  conformance requirements might change as a result of progressing
  work in developing standards for internationalized domain names.

I suppose that registries could accept through EPP domain names in
UTF-8 and do the ACE thing themselves... until the time ACE is not
needed anymore.

> 2) As I said before, using nameprep + ACE with contact information. I
> would disagree. ACE was choosen for specific reasons (the ability to
> use existing nameserver sofwtare), we should not push that hack too
> far.

So, we agree on that and we should extend that idea to domain names.

Patrick.

From bortzmeyer@nic.fr  Tue Aug  6 12:57:04 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Tue, 6 Aug 2002 13:57:04 +0200
Subject: [Ietf-not43] Internationalization issues in the registry (Was: requirements diffs
In-Reply-To: <20020806103920.GR21513@nohope.patoche.org>
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net> <3D4EE51F.7080203@ehsco.com> <3D4EE8F6.3EEDC940@ecotroph.net> <20020806064957.GA9312@nic.fr> <20020806103920.GR21513@nohope.patoche.org>
Message-ID: <20020806115704.GA12960@nic.fr>

On Tue, Aug 06, 2002 at 12:39:20PM +0200,
 Patrick <patrick@gandi.net> wrote 
 a message of 52 lines which said:

> I suppose that registries could accept through EPP domain names in
> UTF-8 and do the ACE thing themselves... until the time ACE is not
> needed anymore.
> 
> > 2) As I said before, using nameprep + ACE with contact information. I
> > would disagree. ACE was choosen for specific reasons (the ability to
> > use existing nameserver sofwtare), we should not push that hack too
> > far.
> 
> So, we agree on that and we should extend that idea to domain names.

So, to summary:

The Registry should accept Unicode in domain names (and contact
information), using plain EPP (It can reduce the set of acceptable
characters in its policy, for instance, .eu could restrict itself to
Latin-1 and Greek.)

The Registry translates to ACE just to check the unicity and to
generate the zone files.

Since the Registry's database stores Unicode, information protocols
like IRIS can use it natively (thus solving the partial-name matching
problem but of course not all the funny other matching problems of
Unicode).

Implementation note: I'm not sure that all EPP servers authors are
aware of that and react gracefully to IDN. A note in the future RFC
could be useful.


From patrick@gandi.net  Tue Aug  6 16:36:52 2002
From: patrick@gandi.net (Patrick)
Date: Tue, 6 Aug 2002 17:36:52 +0200
Subject: [Ietf-not43] Internationalization issues in the registry (Was: requirements diffs
In-Reply-To: <20020806115704.GA12960@nic.fr>
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net> <3D4EE51F.7080203@ehsco.com> <3D4EE8F6.3EEDC940@ecotroph.net> <20020806064957.GA9312@nic.fr> <20020806103920.GR21513@nohope.patoche.org> <20020806115704.GA12960@nic.fr>
Message-ID: <20020806153652.GZ21513@nohope.patoche.org>

On Tue, Aug 06, 2002 at 01:57:04PM +0200, Stephane Bortzmeyer took time to write:
> The Registry should accept Unicode in domain names (and contact
> information), using plain EPP (It can reduce the set of acceptable
> characters in its policy, for instance, .eu could restrict itself to
> Latin-1 and Greek.)
> 
> The Registry translates to ACE just to check the unicity and to
> generate the zone files.
> 
> Since the Registry's database stores Unicode, information protocols
> like IRIS can use it natively (thus solving the partial-name matching
> problem but of course not all the funny other matching problems of
> Unicode).

Sounds good to me ;-)
And when all software will be updated, the ACE part will vanish.
Hopefully ;-)

> Implementation note: I'm not sure that all EPP servers authors are
> aware of that and react gracefully to IDN. A note in the future RFC
> could be useful.

See the paragraph quoted previously : EPP is built on current RFC
regarding what you put in domain names (for now A-Z 0-9 and -), but
clearly specifies future directions to be in accordance with new RFCs
(that is after IDN WG produces them), and is built with XML which is
already happy with UTF-8.
Current implementations may not support it, but it is just a matter
of upgrading them when the time arrives ;-)
(FYI our toolkit soon to be released implementing EPP does not
support characters outside what described above for domain names, and
we will update it when IDN registrations become something really
existing)

Patrick.

From anewton@ecotroph.net  Tue Aug  6 16:59:48 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Tue, 06 Aug 2002 11:59:48 -0400
Subject: [Ietf-not43] Internationalization issues in the registry (Was:
 requirements diffs
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net> <3D4EE51F.7080203@ehsco.com> <3D4EE8F6.3EEDC940@ecotroph.net> <20020806064957.GA9312@nic.fr> <20020806103920.GR21513@nohope.patoche.org> <20020806115704.GA12960@nic.fr>
Message-ID: <3D4FF274.195DB1FE@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-25379-1028650186-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Stephane Bortzmeyer wrote:
> 
> So, to summary:
> 
> The Registry should accept Unicode in domain names (and contact
> information), using plain EPP (It can reduce the set of acceptable
> characters in its policy, for instance, .eu could restrict itself to
> Latin-1 and Greek.)
> 
> The Registry translates to ACE just to check the unicity and to
> generate the zone files.
> 
> Since the Registry's database stores Unicode, information protocols
> like IRIS can use it natively (thus solving the partial-name matching
> problem but of course not all the funny other matching problems of
> Unicode).

After reading this and the discussion Stephane brought up on the PROVREG
list, this seems reasonable to me.

However, this still leaves open the issues Eric mentioned... what
encoding to you use for the DNS label when finding the authoritative
server, and what do you do with URL's?

-andy
--=_zark-25379-1028650186-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA2MTU1OTQ4WjAjBgkqhkiG9w0BCQQxFgQUAuyDYo+Yy9VPbtPDVkwVVunScx8wUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAx57JbFQESCT0Wtmy
6pu/AJR31NQF5o98nhzqezGojPNvAu9DQHyxnRrl3h7smgUhZpIOqexWhsCx9YBiG6t9e6QI
CCrlW99c62L6fl8fjPvh0jUNIU5q9eCUceY2tqKiDaSfre5MK4iiiRDt48u7gn6ooimDnfU5
5CM6YiSUyteTNkpCELjnBZ5PQWudMdh8P9pUi2IhyoBRy2CHSFNvpBZASkGH8pA6sCV1nkek
ZXHWdn8lD2ihbqX65ObeLAC7FfRuUSWKkfAz50BqS8QCvCwXoLysJ6ATkSD/STMDjRmbPqZ7
fZ6Tr/6vfxj8N957cy0XGCGgcNgKRuXnPswJqw==
--=_zark-25379-1028650186-0001-2--

From Ted.Hardie@nominum.com  Tue Aug  6 18:04:06 2002
From: Ted.Hardie@nominum.com (Ted Hardie)
Date: Tue, 6 Aug 2002 10:04:06 -0700 (PDT)
Subject: [Ietf-not43] Re: Data mining v. poorly-framed queries [was Re: [Ietf-not43]
In-Reply-To: <3D4EEA58.677B9AD7@ecotroph.net> from "Andrew Newton" at Aug 05, 2002 05:12:56 PM
Message-ID: <200208061704.KAA11599@geode.he.net>

Andy writes:
> I think the right thing to do would be to stipulate that the protocols
> have such a feature to notify the user of the truncation condition.  The
> use of these notifications are, and in reality will be, site specific.
> 

This gets to be hard to debug; if I might or might not get a specific
error based on which service provider I'm talking to, we can end up
back in the soup pretty quickly.  I'd rather see the requirement say
something like:

"The service MUST indicate if a response has been truncated using
a standard error mechanism, but MAY omit details from that response
in order to hinder the 'chaining' of requests by data miners".

This does err on the side of supporting standard errors over 
avoiding data mining, but I'd really, really hate for us to be
back in the situation where diagnostics have to be cased for individual
services.
			regards,
				Ted Hardie


From leslie@thinkingcat.com  Tue Aug  6 18:26:35 2002
From: leslie@thinkingcat.com (Leslie Daigle)
Date: Tue, 06 Aug 2002 13:26:35 -0400
Subject: [Ietf-not43] Re: Data mining v. poorly-framed queries [was
 Re:[Ietf-not43]
References: <200208061704.KAA11599@geode.he.net>
Message-ID: <3D5006CB.C1A956C4@thinkingcat.com>

I'd prefer this -- I always like deterministic behaviour :-) 
But I think I agree with Andy in that it's not what will get 
implemented, irrespective of what our requirements state.

So, two possibilities:

	. as proposed below:  will servers in fact implement
	  sufficiently random deletions from the result set,
	  or will miners simply try to chain, anyway.

	. as currently written in the requirements doc:  the service 
	  MUST fail silently when it has a query that generates too 
	  many hits.  Both legitimate clients and miners will have
	  to retry queries to confirm they got everything they
	  wanted...

At this point, it seems like we're trying to do behaviour modification
on end-users via requirements for a service that will be implemented
in some as-yet-to-be-decided protocol... that seems like too many
layers of indirection for sanity.

Leslie.

Ted Hardie wrote:
> 
> Andy writes:
> > I think the right thing to do would be to stipulate that the protocols
> > have such a feature to notify the user of the truncation condition.  The
> > use of these notifications are, and in reality will be, site specific.
> >
> 
> This gets to be hard to debug; if I might or might not get a specific
> error based on which service provider I'm talking to, we can end up
> back in the soup pretty quickly.  I'd rather see the requirement say
> something like:
> 
> "The service MUST indicate if a response has been truncated using
> a standard error mechanism, but MAY omit details from that response
> in order to hinder the 'chaining' of requests by data miners".
> 
> This does err on the side of supporting standard errors over
> avoiding data mining, but I'd really, really hate for us to be
> back in the situation where diagnostics have to be cased for individual
> services.
>                         regards,
>                                 Ted Hardie

-- 

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

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

From Ted.Hardie@nominum.com  Tue Aug  6 18:58:35 2002
From: Ted.Hardie@nominum.com (Ted Hardie)
Date: Tue, 6 Aug 2002 10:58:35 -0700 (PDT)
Subject: [Ietf-not43] Re: Data mining v. poorly-framed queries [was
In-Reply-To: <3D5006CB.C1A956C4@thinkingcat.com> from "Leslie Daigle" at Aug 06, 2002 01:26:35 PM
Message-ID: <200208061758.KAA23524@geode.he.net>

> 
> 
> I'd prefer this -- I always like deterministic behaviour :-) 
> But I think I agree with Andy in that it's not what will get 
> implemented, irrespective of what our requirements state.
> 
> So, two possibilities:
> 
> 	. as proposed below:  will servers in fact implement
> 	  sufficiently random deletions from the result set,
> 	  or will miners simply try to chain, anyway.
> 
> 	. as currently written in the requirements doc:  the service 
> 	  MUST fail silently when it has a query that generates too 
> 	  many hits.  Both legitimate clients and miners will have
> 	  to retry queries to confirm they got everything they
> 	  wanted...
> 
> At this point, it seems like we're trying to do behaviour modification
> on end-users via requirements for a service that will be implemented
> in some as-yet-to-be-decided protocol... that seems like too many
> layers of indirection for sanity.
> 
> Leslie.

Leslie,
	I'm not sure that we are trying to do behavior mod on the end
user; I think we're trying to do protocol design based on the abusive
cases rather than normal use.  Given the strong message we've received
that data mining is a problem, I think we do have to take it into
account, but not to the point where we seriously perturb the behavior
of the protocol.
	I advocate changing the current "silent failure" requirement.
I believe it hinders normal use, and does not stop abusive behavior.
I'd like to change it to something that supports normal use in an
interoperable and deterministic way.  I'm totally open to suggestions
as to what that might be, if the error message with omitted details
is not appropriate.
			regards,
					Ted Hardie







From anewton@ecotroph.net  Tue Aug  6 19:39:20 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Tue, 06 Aug 2002 14:39:20 -0400
Subject: [Ietf-not43] Re: Data mining v. poorly-framed queries [was
References: <200208061758.KAA23524@geode.he.net>
Message-ID: <3D5017D8.F444AA6E@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-26325-1028659759-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ted Hardie wrote:
> 
> Leslie,
>         I'm not sure that we are trying to do behavior mod on the end
> user; I think we're trying to do protocol design based on the abusive
> cases rather than normal use.  Given the strong message we've received
> that data mining is a problem, I think we do have to take it into
> account, but not to the point where we seriously perturb the behavior
> of the protocol.
>         I advocate changing the current "silent failure" requirement.
> I believe it hinders normal use, and does not stop abusive behavior.
> I'd like to change it to something that supports normal use in an
> interoperable and deterministic way.  I'm totally open to suggestions
> as to what that might be, if the error message with omitted details
> is not appropriate.
>                         regards,
>                                         Ted Hardie

Ted,

I still think my point is valid.  We can stipulate that the protocol
provide such an indicator, but its use will really be up to the
individual operators.  There really is no way to mandate it other than
to go to every registry operator and demand to see their list of
domains.

-andy
--=_zark-26325-1028659759-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA2MTgzOTIwWjAjBgkqhkiG9w0BCQQxFgQUq1Grn8p64vcz4IuDpKmlmgvNB1owUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAgTXsuldWWzy76/gB
vvAMxE47vXAOIRzo0yIT/kb9NwoYPsH6aqAphoPGmxsiso8kOvd579aNoIuHwu3OnAnNga5H
gAP1wpIe7SAIChU43lqblkqldfYrazSUc8dtInc5caHXeRXc9X4GS3Ecn7aeclgUOTOa6BpN
Ygzkz2hFIdy473PjIKILS83XFKe3ez2ipNSvmGMlPtqBOFe0VdC7WUu+byrt0lpnN8D3665A
q16OU8ri9MdK34/7+rnBT8puzRoD2UpF34T7IwXYAoTvj/kBk4FQO0FqldgHzAVPXnnC6fMh
dM/8G3+IReHoUqAdQ4myvKCL408qrTL7ir20UQ==
--=_zark-26325-1028659759-0001-2--

From bortzmeyer@nic.fr  Wed Aug  7 13:34:23 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Wed, 7 Aug 2002 14:34:23 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <3D4186AC.BFEC8A7E@thinkingcat.com>
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <20020724075458.B66611@shell.nominum.com> <20020726095310.GA30275@nic.fr> <3D4186AC.BFEC8A7E@thinkingcat.com>
Message-ID: <20020807123423.GE24159@nic.fr>

On Fri, Jul 26, 2002 at 01:28:12PM -0400,
 Leslie Daigle <leslie@thinkingcat.com> wrote 
 a message of 75 lines which said:

> What you are proposing seems based on the assumption that you know
> what server you are going to connect to, 

Right. Referrals are another TODO.

> 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,

Your explanation is very clear and precise but does not reflect the
work I've seen on this WG. The IRIS draft, for instance, is not very
detailed on this point and, like my proposal, focus on interaction
with a given server.

> such that a client starting with some label (e.g.
> a dns name) can find the authoritative server and make the
> relevant query. 

This could be done on the client-side, too, like many whois clients do
at the present time.

"\.(com|net|org)" -> whois.networksolutions.com
"\.(info)"        -> whois.affilias.info
"\.(.*)           -> whois.nic.$1

> 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.

Glad you mention it. I could add just one line saying that the
authoritative server is found with RFC 2782.
  
> But until I'm a little more convinced you understand what problem
> this group is solving, 

I understand much better the issues, thanks to your explanations. But
I agree with the Ted Hardie's point of view: Crisp has several
problems to solve and my proposal more-or-less fits one (querying a
given server). Unlike you, I do not think it is the less important
question.

From bortzmeyer@nic.fr  Wed Aug  7 13:36:22 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Wed, 7 Aug 2002 14:36:22 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020726143950.D20134@shell.nominum.com>
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <20020724075458.B66611@shell.nominum.com> <20020726095310.GA30275@nic.fr> <3D4186AC.BFEC8A7E@thinkingcat.com> <20020726143950.D20134@shell.nominum.com>
Message-ID: <20020807123622.GF24159@nic.fr>

On Fri, Jul 26, 2002 at 02:39:50PM -0700,
 Ted Hardie <Ted.Hardie@nominum.com> wrote 
 a message of 58 lines which said:

> 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? 

Not completely because my proposal also addresses the schema chunk
(unlike IRIS which postpones the actual schema discussion, since it is
not clear we can all agree on a common schema).

From bortzmeyer@nic.fr  Wed Aug  7 13:38:59 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Wed, 7 Aug 2002 14:38:59 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020726140306.C20134@shell.nominum.com>
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <20020724075458.B66611@shell.nominum.com> <20020726095310.GA30275@nic.fr> <20020726140306.C20134@shell.nominum.com>
Message-ID: <20020807123859.GG24159@nic.fr>

On Fri, Jul 26, 2002 at 02:03:06PM -0700,
 Ted Hardie <Ted.Hardie@nominum.com> wrote 
 a message of 595 lines which said:

> > 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.

OK, I rephrase it in another way. The current requirments specify
things that have to be done when designing the protocol (i.e. the
drafts on IRIS or IRPI has to specify something that will fit the
requirments) and it also specify things that will have to be done when
actually implementing a service (like rate-limiting functions).

Hence, no protocol proposal (LDAP, IRIS, etc) can actually fulfill 100
% of the requirments.

From bortzmeyer@nic.fr  Wed Aug  7 13:44:08 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Wed, 7 Aug 2002 14:44:08 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <3D41948B.1000601@verisignlabs.com>
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <1027525651.4716.117.camel@zedonthego.admin.cto.netsol.com> <20020724160533.GA14255@nic.fr> <3D41948B.1000601@verisignlabs.com>
Message-ID: <20020807124408.GH24159@nic.fr>

On Fri, Jul 26, 2002 at 02:27:23PM -0400,
 Andrew Newton <anewton@verisignlabs.com> wrote 
 a message of 35 lines which said:

> I think I would be more supportive of a SOAP standard.

Could you explain why? A good explanation would be a proposal using
SOAP, with features that cannot be done in XML-RPC (for those who
never tried SOAP or XML-RPC, <summary level="rough">SOAP is a superset
of XML-RPC</summary>).
 
> this instance, it can easily slide into functions clearly outside the 
> charter of this group, such as registryDomain( domainName ).

You are absolutely  right. I am reading
<URL:http://www.cafax.se/ietf-provreg/maillist/2001-01/msg00189.html>
to study this issue :-)




From bortzmeyer@nic.fr  Wed Aug  7 14:46:07 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Wed, 7 Aug 2002 15:46:07 +0200
Subject: [Ietf-not43] Internationalization issues in the registry (Was: requirements diffs
In-Reply-To: <20020806153652.GZ21513@nohope.patoche.org>
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net> <3D4EE51F.7080203@ehsco.com> <3D4EE8F6.3EEDC940@ecotroph.net> <20020806064957.GA9312@nic.fr> <20020806103920.GR21513@nohope.patoche.org> <20020806115704.GA12960@nic.fr> <20020806153652.GZ21513@nohope.patoche.org>
Message-ID: <20020807134607.GA25858@nic.fr>

On Tue, Aug 06, 2002 at 05:36:52PM +0200,
 Patrick <patrick@gandi.net> wrote 
 a message of 39 lines which said:

> clearly specifies future directions to be in accordance with new RFCs
> (that is after IDN WG produces them), and is built with XML which is
> already happy with UTF-8.

It is not only an issue with IDN. The LibertyRMS test bed does not
allow contact information in Unicode either ("syntax error"). And I
assume most (all?)  EPP servers will do the same.

> Current implementations may not support it, but it is just a matter
> of upgrading them when the time arrives ;-)

Let's cross our fingers. I'm not really optimistic.







From patrick@gandi.net  Wed Aug  7 15:04:06 2002
From: patrick@gandi.net (Patrick)
Date: Wed, 7 Aug 2002 16:04:06 +0200
Subject: [Ietf-not43] Internationalization issues in the registry (Was: requirements diffs
In-Reply-To: <20020807134607.GA25858@nic.fr>
References: <3D4EA500.E06B161A@ecotroph.net> <3D4EBD48.495EC430@thinkingcat.com> <3D4EC618.68246376@ecotroph.net> <3D4EE51F.7080203@ehsco.com> <3D4EE8F6.3EEDC940@ecotroph.net> <20020806064957.GA9312@nic.fr> <20020806103920.GR21513@nohope.patoche.org> <20020806115704.GA12960@nic.fr> <20020806153652.GZ21513@nohope.patoche.org> <20020807134607.GA25858@nic.fr>
Message-ID: <20020807140406.GJ21513@nohope.patoche.org>

On Wed, Aug 07, 2002 at 03:46:07PM +0200, Stephane Bortzmeyer took time to write:
> On Tue, Aug 06, 2002 at 05:36:52PM +0200,
>  Patrick <patrick@gandi.net> wrote 
>  a message of 39 lines which said:
> 
> > clearly specifies future directions to be in accordance with new RFCs
> > (that is after IDN WG produces them), and is built with XML which is
> > already happy with UTF-8.
> 
> It is not only an issue with IDN. The LibertyRMS test bed does not
> allow contact information in Unicode either ("syntax error"). And I
> assume most (all?)  EPP servers will do the same.

Again, maybe I was not clear :
the libertyRMS test best (or any other) is not authoritative at all.
The fact that it today does not do something that may or should be
done in the future is no indication at all there is a problem...
except the fact that the software will need to be updated in the
future.

BTW some EPP Registries works without problems with Unicode caracters
in contact. Our own toolkit handles that without problems.

> > Current implementations may not support it, but it is just a matter
> > of upgrading them when the time arrives ;-)
> 
> Let's cross our fingers. I'm not really optimistic.

I do not understand. When Registries will need to do true Unicode
domain names they will update their software, that is all.

And besides, I will dare to say that it would be a small update.

Patrick.

From patrick@gandi.net  Wed Aug  7 15:41:03 2002
From: patrick@gandi.net (Patrick)
Date: Wed, 7 Aug 2002 16:41:03 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020807123423.GE24159@nic.fr>
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <20020724075458.B66611@shell.nominum.com> <20020726095310.GA30275@nic.fr> <3D4186AC.BFEC8A7E@thinkingcat.com> <20020807123423.GE24159@nic.fr>
Message-ID: <20020807144103.GN21513@nohope.patoche.org>

On Wed, Aug 07, 2002 at 02:34:23PM +0200, Stephane Bortzmeyer took time to write:
> > such that a client starting with some label (e.g.
> > a dns name) can find the authoritative server and make the
> > relevant query. 
> 
> This could be done on the client-side, too, like many whois clients do
> at the present time.
> 
> "\.(com|net|org)" -> whois.networksolutions.com
> "\.(info)"        -> whois.affilias.info
> "\.(.*)           -> whois.nic.$1

A system that would not need to update *all* client software to
change something is something interesting... Like DNS for example:
you do not need to change your resolver when ICANN adds a new TLD.

It could be done, but it should not to. That is my point of view.
The mechanism in place should handle this sort of things
transparently.
Also I am not sure a system like the one you propose could be used
for all purposes in CRISP. Ok, easy for domain names (at least now),
but how for IPv4 adresses ? You plan to have each client software
having a mapping between netmasks and IP Registries ?

Personnally I would imagine that something like DNS SRV records may
be useful.

> > But until I'm a little more convinced you understand what problem
> > this group is solving, 
> 
> I understand much better the issues, thanks to your explanations. But
> I agree with the Ted Hardie's point of view: Crisp has several
> problems to solve and my proposal more-or-less fits one (querying a
> given server). Unlike you, I do not think it is the less important
> question.

I would dare to say that it is the easier part. This is also a part where
many ideas already exists (SOAP, RPC-XML, Corba, whatever), and it
``just'' needs to be adapted to the current setup. It is not to say
that your work is less important, just that there are other parts.
(the charter have 6 points, querying is one among the 6)

Ok, I have done nothing, so who I am to criticize anyway...

Patrick.

From patrick@gandi.net  Wed Aug  7 15:48:26 2002
From: patrick@gandi.net (Patrick)
Date: Wed, 7 Aug 2002 16:48:26 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <20020807124408.GH24159@nic.fr>
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <1027525651.4716.117.camel@zedonthego.admin.cto.netsol.com> <20020724160533.GA14255@nic.fr> <3D41948B.1000601@verisignlabs.com> <20020807124408.GH24159@nic.fr>
Message-ID: <20020807144826.GO21513@nohope.patoche.org>

On Wed, Aug 07, 2002 at 02:44:08PM +0200, Stephane Bortzmeyer took time to =
write:
> On Fri, Jul 26, 2002 at 02:27:23PM -0400,
>  Andrew Newton <anewton@verisignlabs.com> wrote=20
>  a message of 35 lines which said:
>=20
> > I think I would be more supportive of a SOAP standard.
>=20
> Could you explain why? A good explanation would be a proposal using
> SOAP, with features that cannot be done in XML-RPC (for those who
> never tried SOAP or XML-RPC, <summary level=3D"rough">SOAP is a superset
> of XML-RPC</summary>).

Probably a good start for a comparison:
http://weblog.masukomi.org/writings/xml-rpc_vs_soap.htm
(particularly the last =A7)

Based on that, and what I know, I would also favor SOAP over XML-RPC.
Mainly because the thing_to_be_designed is not just about passing
domain names between a client and a server. It is about passing
``something'' between a client and many servers (with the task of
choosing the right one).

Patrick.

From anewton@ecotroph.net  Wed Aug  7 15:39:20 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Wed, 07 Aug 2002 10:39:20 -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> <3D4186AC.BFEC8A7E@thinkingcat.com> <20020807123423.GE24159@nic.fr>
Message-ID: <3D513118.420DFD3B@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-31653-1028731762-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Stephane Bortzmeyer wrote:
> 
> Your explanation is very clear and precise but does not reflect the
> work I've seen on this WG. The IRIS draft, for instance, is not very
> detailed on this point and, like my proposal, focus on interaction
> with a given server.
> 
> > such that a client starting with some label (e.g.
> > a dns name) can find the authoritative server and make the
> > relevant query.

It is in the back of the IRIS drafts on the TODO list.  Anyway, the
forthcoming IRIS drafts will have it in there.

Anyway, I think we can all thank Eric Hall for providing the clue that
got us all to this point.  His LDAP-WHOIS drafts quite clearly spell-out
how this works.

-andy
--=_zark-31653-1028731762-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA3MTQzOTIwWjAjBgkqhkiG9w0BCQQxFgQUD5GTAHbnGiSxYJFfG5+Orp5L43QwUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEASWQYcRoYUXsKCYdo
tdrCTaZj7047Uyh3k8QUNvq0uCFkQrbHOlO6nTsMsFdlQfXIWI8/k5NntKL81BGv3bOQ0sqs
1PcxZ5twGn8SRymFfc23k/7HxmNhrMBFWKQJ2jtpaUo99TIWZRMs0+AjopgK04PJ1/7758g2
yySSjrRmZR5rIrP5Cl2jtjp+IJpTwkXYRlLlIhD4PaR1JBfaBj8kVFS+6v19SpzDeYcU5FVm
2Q7WBkCf5v40tmr8Mu/y5ffdP5ojNmIaxAtwoB2XENASTOxeM0kHqpIiSO2+33DvZLhR3NT5
dwd7xI/bRfqvSH5HVCa+9FzmSP4SlVTqP41P4Q==
--=_zark-31653-1028731762-0001-2--

From anewton@ecotroph.net  Wed Aug  7 15:40:24 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Wed, 07 Aug 2002 10:40:24 -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> <3D4186AC.BFEC8A7E@thinkingcat.com> <20020726143950.D20134@shell.nominum.com> <20020807123622.GF24159@nic.fr>
Message-ID: <3D513158.41684C77@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-31721-1028731826-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Stephane Bortzmeyer wrote:
> 
> Not completely because my proposal also addresses the schema chunk
> (unlike IRIS which postpones the actual schema discussion, since it is
> not clear we can all agree on a common schema).

Yes it does.  Read the DREG draft.

-andy
--=_zark-31721-1028731826-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA3MTQ0MDI0WjAjBgkqhkiG9w0BCQQxFgQUEN5ig6uNZwEicA3p/xTxdmORyOcwUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAoBG8hMje8d2OOcMY
8HtJaBqrkO2/fkLQ94PwS16olSq4xFSX7Uk21lI8B5cDo1EzivG2PXfANhnP4RSO3F51AFxg
IVRLbhl35CA3H4CKW5PIWy+cM4At2G8odJ9m5J5MczmEZLNHbE83VdDI+Y1ExL87gwL+Oxwe
aqVZ9jF4UAmZci7CdO4ls3K1hWSAVeW4PQbORrtiGbLrZdds75ExRJ8gd2/KAiBovBfZBckq
ZpNoo8qXgZJFOdiH2Q6vrOcVFPGorxv3QNwE58LCbElO7Dv53rWY2AWzXBMwPiFMZgxnnLlZ
GuKKzluBg74l78sORIiE3szA9y1srwk66ZsBPg==
--=_zark-31721-1028731826-0001-2--

From anewton@ecotroph.net  Wed Aug  7 16:08:57 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Wed, 07 Aug 2002 11:08:57 -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> <3D41948B.1000601@verisignlabs.com> <20020807124408.GH24159@nic.fr>
Message-ID: <3D513809.5D285A92@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-32294-1028733538-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Stephane Bortzmeyer wrote:
> 
> > I think I would be more supportive of a SOAP standard.
> 
> Could you explain why? A good explanation would be a proposal using
> SOAP, with features that cannot be done in XML-RPC (for those who
> never tried SOAP or XML-RPC, <summary level="rough">SOAP is a superset
> of XML-RPC</summary>).

Why SOAP over XML-RPC?
1) Dave Winer has even moved on.  He co-authored the first SOAP spec.
2) XML-RPC is tied to HTTP (as is SOAP 1.0).  To understand why the
firewall-bypass protocol is a bad idea, read RFC 3205.
3) XML-RPC is copyright Dave Winer, with a fairly liberal copyright. 
SOAP 1.2 will be a W3C spec.  That makes some people a little more
comfortable (and, I hate to say it, even me).
4) SOAP implementations are available from open source good guys and the
likes of enterprise solutions providers such as IBM, MicroSoft, BEA,
etc.

However, I don't think it is right of us to dismiss your idea at least
without a proper explanation.  I had to think about it some more to
actually get an answer I felt comfortable with.

Both XML-RPC and SOAP are abstraction layers intended to divorce the
"business logic" programmer of the murky details of the layers
underneath.  However, what we are proposing also involves the use of DNS
SRV or NAPTR records to a greater extent than can be found in most
library implementations.  This means the implementer will need a fair
bit of knowledge about the total solution anyway.

In addition, both XML-RPC and SOAP 1.0 seem to violate RFC 3205.  This
isn't good.  While there is a SOAP to BEEP spec that could get around
this, I would bet you'd be hard pressed to find an implementation of it
that suits your needs.  This also eliminates your ability to plug-in the
underlying stuff and just go.

-andy
--=_zark-32294-1028733538-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA3MTUwODU3WjAjBgkqhkiG9w0BCQQxFgQUaa3XQhR7Ttqmdb3we8U1Ku2Sk5AwUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAILeuR/nqzl70HUsk
eZLlnVMHse7FUoAY6tiAMSP+4hYCwoluqedFaSWIve1GnYVYqxzA3QeAdImjIEHFgB/qulRb
QSSRUaZYKV+ATD1uWVoi3ATVxVOgF4NiKZv3tG0S47NUXWpByqjpPg1K8Wqmz0rxUNBaJJd/
7cdXBArNR2L2Sq9laDt47S3xjxPbTKSUR/GMLZnIYFX0fWsdmDPF5buTXg4L/iuwhCyttoXA
acErY0kvozhG7cX5AN46xk8Z9/54nUnW+IE6Re8lJN7QoTsLrIZmaRCoffiw58qweMO3o5oq
Aen49xslZ75dxHLcue1Tf+/BTdGLbxE4v5yLxw==
--=_zark-32294-1028733538-0001-2--

From bortzmeyer@nic.fr  Wed Aug  7 16:41:27 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Wed, 7 Aug 2002 17:41:27 +0200
Subject: [Ietf-not43] XML-RPC for an information service?
In-Reply-To: <3D513809.5D285A92@ecotroph.net>
References: <20020722150448.GA16795@nic.fr> <20020724104615.GA10249@nic.fr> <1027525651.4716.117.camel@zedonthego.admin.cto.netsol.com> <20020724160533.GA14255@nic.fr> <3D41948B.1000601@verisignlabs.com> <20020807124408.GH24159@nic.fr> <3D513809.5D285A92@ecotroph.net>
Message-ID: <20020807154127.GA27902@nic.fr>

On Wed, Aug 07, 2002 at 11:08:57AM -0400,
 Andrew Newton <anewton@ecotroph.net> wrote 
 a message of 95 lines which said:

> 2) XML-RPC is tied to HTTP (as is SOAP 1.0).

There are implementations of XML-RPC over Jabber and BEEP (under
construction). However, I agree they are extensions of the original
spec (like many good things in XML-RPC, like the introspection API or
the Unicode support).

>  To understand why the firewall-bypass protocol is a bad idea, read
> RFC 3205.

I've read it and, like many people, I disagree with it. If I have a
XML-RPC server which uses HTTP and listens on port 8080, explain how
it violates firewall rules. And what is the difference between a
XML-RPC server using port 80 and a CGI?

> 3) XML-RPC is copyright Dave Winer, with a fairly liberal copyright. 
> SOAP 1.2 will be a W3C spec.  That makes some people a little more
> comfortable (and, I hate to say it, even me).

Me too. It is clearly a problem with XML-RPC. Should I start an IETF
WG to standardize XML-RPC? :-) (I'm joking but it is how the IETF made
SSL into the IETF-compliant TLS.)

> 4) SOAP implementations are available from open source good guys and the
> likes of enterprise solutions providers such as IBM, MicroSoft, BEA,
> etc.

Same thing for XML-RPC.

> In addition, both XML-RPC and SOAP 1.0 seem to violate RFC 3205.  This
> isn't good.

It does not bother me. SOAP 1.0 violates it less (thanks to the
SOAPAction header but SOAP 1.2 will deprecate it).



From anewton@ecotroph.net  Wed Aug  7 22:35:19 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Wed, 07 Aug 2002 17:35:19 -0400
Subject: [Ietf-not43] rewording of section 3.2.8
Message-ID: <3D519297.836ED979@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-2354-1028756722-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

If nobody objects, I'd like to reword section 3.2.8 of the requirements.

It currently says:

3.2.8 Authentication Distribution

The service MUST be capable of allowing a centralized authority
entity the means to distribute authentication information of
entities accessing the service. The service MUST not require all
Internet registries to participate in distributed authentication and
SHOULD allow the participation by an Internet registry in
distributed authentication by many centralized authority entities.

The first sentence seems to be out-of-scope for the group (too much on
the provisioning side) and the rest isn't tight enough.

Perhaps:

3.2.8 Authentication Distribution

The service MUST not require any Internet registries to participate
in any particular distributed authentication system.  The service SHOULD
allow the participation by an Internet registry in distributed
authentication by many centralized authority entities.

And perhaps moving it to section 3.1 instead of 3.2.

-andy
--=_zark-2354-1028756722-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA3MjEzNTE5WjAjBgkqhkiG9w0BCQQxFgQUvt6oRlHj+I2eOETN4+2Q47TbLF4wUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAw94954UM5I5HPtbn
G8Yo9Ui5nI/EU6K0Iol7FevwjDVbX08A/ppz1k7/Jap75Rkt3s+D3q1McjvFBCB27EymAVio
tY97RwHvJY5m27f8gjd7oev37Mlqk6TFpDk9HJNP/xCqCPa5PvwxvFafgE0Eq2WCDmmdH13l
uiSdVq471RqN/EsSFqxoLYZSbS63Cf/596Suh9BT3OF/xSvepBNGeialKOwO5+74ThkLRurA
DuwfpDn31JmezXCOHE1ZjGDzpoc28ha/aTrilcTbEAz1y0idgRmatYNORcJrLwAVOyK4yDTB
TByJ4jngMQ/qPJ3je7aSQXh0My3crcstI76xzA==
--=_zark-2354-1028756722-0001-2--

From anewton@ecotroph.net  Wed Aug  7 23:35:16 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Wed, 07 Aug 2002 18:35:16 -0400
Subject: [Ietf-not43] 3.2.3 & 3.2.5 requirements
Message-ID: <3D51A0A4.5A7FE2B@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-2696-1028760318-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Also, if nobody objects... I'd like to delete 3.2.3 because it is
covered under 3.2.5.  I'd also like to change the SHOULD in 3.2.5 to a
MUST.

As they stand:

3.2.3 Domain Status Lookup

   The service MUST provide access to the status of a domain given the
   domain's fully qualified name. This status MUST indicate the
   activation status of the domain. The activation status is the same
   as would be available in Section 3.2.5.


3.2.5 Domain Information Lookup

   The service MUST provide access to operational and social data
   specific to a domain given the domain's fully qualified name (FQDN).
   This information SHOULD include the following:

   o  activation status

   o  registrant name and contact data

   o  hosting nameservers

   o  technical, billing or other entity types associate with the
      domain and their relevant contact data, if any exist

   o  the name of or a reference to the registry delegating the domain

   o  the name of or a reference to the registrar for the domain, if
      one exists

-andy
--=_zark-2696-1028760318-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA3MjIzNTE2WjAjBgkqhkiG9w0BCQQxFgQUjg/qOSfkJ650efU/X9rmy2AjY/IwUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAuwHYRuFxID7UiHL1
LyLpYkb6NwSZomVl4F5jQWkGVBbQIUG4QgVlZHr2SJGpx1MGeyxJPOHvq0TmKY6l1japTxVL
YeMDB6ThDWTOEWodGCY9VPFEuc5/W0CerEaoR9reR/7HvhdH2BgFPlE2jQXDu1FjXHJ8e6qu
fFx9ra3XurZWM4JphbHIJ5XfTPh5ZxIqD0qWikdKoBjsyj3u3hQ02lcPE+p7HJcPUOfn3+KW
NepEvp9LWr1jD50qsvsf7hAm5IipFye9pXpYBKc2YtbTQb059Z/TDzaAeSzERlyMepYsyXGt
wv/iaqKJmloRurC2A403ROfaDW7k5T0i77/ooQ==
--=_zark-2696-1028760318-0001-2--

From bortzmeyer@nic.fr  Thu Aug  8 11:00:07 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Thu, 8 Aug 2002 12:00:07 +0200
Subject: [Ietf-not43] Using EPP for Crisp?
Message-ID: <20020808100007.GA4466@nic.fr>

Since the recent DNSO report from the whois task force mentions using
EPP to replace whois (!), I wonder what is the current feeling about
this issue. The only thing I've found in the archives of provreg is:

http://www.cafax.se/ietf-provreg/maillist/2001-01/msg00189.html

Any change since? Other things I should read before claiming that we
should merge provreg and crisp ? :-)




From patrick@gandi.net  Thu Aug  8 12:47:21 2002
From: patrick@gandi.net (Patrick)
Date: Thu, 8 Aug 2002 13:47:21 +0200
Subject: [Ietf-not43] Using EPP for Crisp?
In-Reply-To: <20020808100007.GA4466@nic.fr>
References: <20020808100007.GA4466@nic.fr>
Message-ID: <20020808114721.GD21513@nohope.patoche.org>

On Thu, Aug 08, 2002 at 12:00:07PM +0200, Stephane Bortzmeyer took time to write:
> Since the recent DNSO report from the whois task force mentions using
> EPP to replace whois (!), I wonder what is the current feeling about

(a probable error)
Issues related to EPP & whois are, I think, around the fact that at
least for now EPP-based Registries are thick instead of thin, in
which case REgistries are able to provide full whois support without
Registrars. This enables some topics discussed in the TF, as output
uniformization, etc...

> this issue. The only thing I've found in the archives of provreg is:
> 
> http://www.cafax.se/ietf-provreg/maillist/2001-01/msg00189.html
> 
> Any change since? 

I believe that the Provreg WG is clear about the fact that it is
designing a provisioning protocol and only that.
Feel free to bring the issue again on ietf-provreg right now.

> Other things I should read before claiming that we
> should merge provreg and crisp ? :-)

There was a thread on ietf-whois about merging RRP & whois
(http://www.imc.org/ietf-whois/mail-archive/threads.html)
I believe most arguments would be the same for (or against in fact)
merging EPP & CRISP

If you claim this merging then please explain how you will handle the
following points for CRISP with EPP:
* a standard mechanism that can be used to determine the
authoritative server(s) for information about a given label 
* authentication and verification of data integrity 
as well as the following points from the requirements:
3.1.1 3.1.4 3.1.6 3.1.7 3.1.8
3.2.4 3.2.8 3.2.9 
4.2 4.3

Those are just some pointers of problems I think that EPP can not handle
because it was not designed to do so.

Patrick.

From anewton@ecotroph.net  Thu Aug  8 15:24:07 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Thu, 08 Aug 2002 10:24:07 -0400
Subject: [Ietf-not43] 3.2.3 & 3.2.5 requirements
References: <200208080302.UAA21540@geode.he.net>
Message-ID: <3D527F07.37D86B28@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-6513-1028817254-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ted Hardie wrote:
> 
> > 3.2.5 Domain Information Lookup
> >
> >    The service MUST provide access to operational and social data
> >    specific to a domain given the domain's fully qualified name (FQDN).
> >    This information SHOULD include the following:
> >
> >    o  activation status
> >
> >    o  registrant name and contact data
> >
> >    o  hosting nameservers
> >
> >    o  technical, billing or other entity types associate with the
> >       domain and their relevant contact data, if any exist
> >
> >    o  the name of or a reference to the registry delegating the domain
> >
> >    o  the name of or a reference to the registrar for the domain, if
> >       one exists
> 
> I think SHOULD makes sense here, in its guise as "ought to, unless you
> have a very good reason not to".  A good reason not to having hosting
> nameservers, for example, is that activation status is "Deleted", "pending"
> or some similar non-operational state.  Billing info for deleted entries
> might also be inappropriate, even if a service continued to provide
> an entry like "deleted".  As an example, NASA asked a service using
> its name outside of the bound of the space act of 1952 to desist doing
> so; I can see maintaining a listing of that domain as "deleted"
> so that someone debugging knows that it is deliberately gone.

I don't disagree with what you are saying.  However the MUST really
should be in terms of what the protocols (that make up the service)
should support.  Which elements are or are not included will most likely
depend on site policy.

So, it probably should read, "The service MUST be capable of supplying
the following information for this lookup:".  

And perhaps something about what to do if an operator chooses to omit
something so that implementers know what to expect.  Perhaps, "The
service MUST be capable of expressing these information components in a
predictable and standard structure while allowing operator policy
determine which elements are or are not appropriate for any particular
query instance." Ok, did I screw that up?  Maybe I'll try this again
after another cup of coffee.

Thoughts?

-andy
--=_zark-6513-1028817254-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA4MTQyNDA3WjAjBgkqhkiG9w0BCQQxFgQUY5F0mBniqGguEaRwojRI47gnsKMwUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAhTtamrPl8WnX6eyG
iYVfngpjBfsaktBkJpmjR6AuFEQ0gMiWGPETQgOJ0i4yaRaSUkWFwlCqeVCHBVRUsUc0/Hbt
18LoxS1puIOPCtHaP1guh39jbI0vz0bQfzjBOi+UqK0RmRhv/ZSeFxOt5lzROEdZbJokxzmL
1I5FdEIF19F+SFLt84Lqr0eik2SUseIcLFqCoe4kPG+Lwq2vysHrfGPAW5cIAFr13ejnXh+X
ji/Qmr3tAeY91RlF81q1w2vMe6ebE/5GvKn+oHfM2iZgIg4iltxGUmSMWE+/9g4sigJi/TNw
OWxKNR9lajzpjqrpkrMBXsTAxuQ4Ag2ai0N+eg==
--=_zark-6513-1028817254-0001-2--

From anewton@ecotroph.net  Thu Aug  8 15:37:26 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Thu, 08 Aug 2002 10:37:26 -0400
Subject: [Ietf-not43] Using EPP for Crisp?
References: <20020808100007.GA4466@nic.fr> <20020808114721.GD21513@nohope.patoche.org>
Message-ID: <3D528226.6FD8E5A1@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-6675-1028818052-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I agree with Patrick.  Just a few comments in-line:

Patrick wrote:
> 
> On Thu, Aug 08, 2002 at 12:00:07PM +0200, Stephane Bortzmeyer took time to write:
> > Since the recent DNSO report from the whois task force mentions using
> > EPP to replace whois (!), I wonder what is the current feeling about

Is this in a new version of the report?  The last one I saw didn't say
this.

> I believe that the Provreg WG is clear about the fact that it is
> designing a provisioning protocol and only that.
> Feel free to bring the issue again on ietf-provreg right now.

Actually, please DO NOT!  They have hashed through it and reached a
conclusion.  There is no reason to disturb their progress with this
issue.

> Those are just some pointers of problems I think that EPP can not handle
> because it was not designed to do so.

Not that there is anything wrong with EPP.  They had a very specific
scope and have done a great job.  However, misunderstanding what they
have done and misusing their work will only lead to problems.

-andy
--=_zark-6675-1028818052-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA4MTQzNzI2WjAjBgkqhkiG9w0BCQQxFgQUy0MeZHvo0gs+tR5YdMS94JxgnkcwUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAXpPYGdVodnLTkk3t
IuV7MWg6kiGddyb0hCKkeuu1xg3+yT0hdopBcGpZptB/4sX6ER8EsRgnZSst4HpAx7bvmzYM
QbHamt6CQViRgoiTGMu6RX3htGH2A86hE+Pl/mbauiVoSLCreEV5a5pKpEr9TFHTszsF+TlQ
FmPoOQ84KkQHBfaKmsbR23Ju3vPSA2Qtdnx7LHePoeDe7SNLmtRIBi4TVSQQHwEmYk08rkfT
JVXD8m5F1sKiryNWBgbmZ/RETN8nDbm1pfztwJ6g3ZX3vR6/a1YH2mAZgDX/zPDjuZkzkpye
5nVuhH3ur4X66/bzt2N64atgcSOabY7H522Ukg==
--=_zark-6675-1028818052-0001-2--

From patrick@gandi.net  Thu Aug  8 15:53:25 2002
From: patrick@gandi.net (Patrick)
Date: Thu, 8 Aug 2002 16:53:25 +0200
Subject: [Ietf-not43] Using EPP for Crisp?
In-Reply-To: <3D528226.6FD8E5A1@ecotroph.net>
References: <20020808100007.GA4466@nic.fr> <20020808114721.GD21513@nohope.patoche.org> <3D528226.6FD8E5A1@ecotroph.net>
Message-ID: <20020808145325.GL21513@nohope.patoche.org>

On Thu, Aug 08, 2002 at 10:37:26AM -0400, Andrew Newton took time to write:
> > On Thu, Aug 08, 2002 at 12:00:07PM +0200, Stephane Bortzmeyer took time to write:
> > > Since the recent DNSO report from the whois task force mentions using
> > > EPP to replace whois (!), I wonder what is the current feeling about
> 
> Is this in a new version of the report?  The last one I saw didn't say
> this.

In http://www.dnso.org/dnso/notes/whoisTF/20020625.TFwhois-report.htm
(an awfully bloated MS HTML file)
it is written:
...  and the results therefore do not take into account new
marketplace realities brought by the introduction of these TLDs
which, in general, provide centralized WHOIS data, in a standardized
(EPP) format.

This is the only sentence where you find the word EPP

This is why I said it is just an error I think . Like I said earlier,
I think that for non technical people, right now, EPP = thick
Registries = centralized whois.

> > Those are just some pointers of problems I think that EPP can not handle
> > because it was not designed to do so.
> 
> Not that there is anything wrong with EPP.  They had a very specific
> scope and have done a great job.  However, misunderstanding what they
> have done and misusing their work will only lead to problems.

I totally agree (I also participate in Provreg ;-)).

Patrick.

From Ted.Hardie@nominum.com  Thu Aug  8 17:14:06 2002
From: Ted.Hardie@nominum.com (Ted Hardie)
Date: Thu, 8 Aug 2002 09:14:06 -0700 (PDT)
Subject: [Ietf-not43] 3.2.3 & 3.2.5 requirements
In-Reply-To: <3D527F07.37D86B28@ecotroph.net> from "Andrew Newton" at Aug 08, 2002 10:24:07 AM
Message-ID: <200208081614.JAA10551@geode.he.net>

Andy quoted, then went on to write:
> > I think SHOULD makes sense here, in its guise as "ought to, unless you
> > have a very good reason not to".  A good reason not to having hosting
> > nameservers, for example, is that activation status is "Deleted", "pending"
> > or some similar non-operational state.  Billing info for deleted entries
> > might also be inappropriate, even if a service continued to provide
> > an entry like "deleted".  As an example, NASA asked a service using
> > its name outside of the bound of the space act of 1952 to desist doing
> > so; I can see maintaining a listing of that domain as "deleted"
> > so that someone debugging knows that it is deliberately gone.
> 
> I don't disagree with what you are saying.  However the MUST really
> should be in terms of what the protocols (that make up the service)
> should support.  Which elements are or are not included will most likely
> depend on site policy.

I agree that the service MUST be able to provide the pieces listed.
I think we both agree that there are times when some elements won't
make sense.  It may be the correct thing to do isn't to omit
the elements, but to emit them with null values; this strategy
can be used when an authorization threshold isn't met, the state
doesn't usefully carry the resulting data, and so on.

I'm also not entirely sure that "site policy" is the right way to
describe the test for when something should and shouldn't be present.
The way I see it, the eventual service description should say
something like "when authorization is below the trusted level, the
service should do X".  Sites determine when authorization is below
the trusted level, but don't determine X when the condition is met.
If there are choices, those need to be spelled out or bounded (so
"return an error or re-present credential challenge" or
"notify service management" both work, even though how notifying
service management works isn't described).

Does this make sense?
			regards,
					Ted Hardie 




From shollenbeck@verisign.com  Thu Aug  8 18:15:06 2002
From: shollenbeck@verisign.com (Hollenbeck, Scott)
Date: Thu, 8 Aug 2002 13:15:06 -0400
Subject: [Ietf-not43] Using EPP for Crisp?
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60336FD2F@vsvapostal3.prod.netsol.com>

> > Those are just some pointers of problems I think that EPP 
> can not handle
> > because it was not designed to do so.
> 
> Not that there is anything wrong with EPP.  They had a very specific
> scope and have done a great job.  However, misunderstanding what they
> have done and misusing their work will only lead to problems.

All very true.  At our San Diego proto-provreg BoF I initially floated the
idea of having one WG tackle both provisioning and whois-like issues, but we
eventually decided to narrow our scope to just the provisioning end of
things to help make the problem manageable.  I'd like to think that there
might be some provreg data structures that might be useful within the CRISP
effort, but the protocol itself wasn't designed for a CRISP-like purpose at
all.

-Scott-

From anewton@ecotroph.net  Thu Aug  8 18:31:19 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Thu, 08 Aug 2002 13:31:19 -0400
Subject: [Ietf-not43] 3.2.3 & 3.2.5 requirements
References: <200208081614.JAA10551@geode.he.net>
Message-ID: <3D52AAE7.C270395@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-8153-1028828486-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ted Hardie wrote:
> 
> I agree that the service MUST be able to provide the pieces listed.
> I think we both agree that there are times when some elements won't
> make sense.  It may be the correct thing to do isn't to omit
> the elements, but to emit them with null values; this strategy
> can be used when an authorization threshold isn't met, the state
> doesn't usefully carry the resulting data, and so on.

Well, that is what I meant.  The schema language used needs to be able
to specify that there is a place for the value of a piece of
information, it is just not provided.  Both the LDAP and XML Schema
approaches can do this.

-andy
--=_zark-8153-1028828486-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODA4MTczMTE5WjAjBgkqhkiG9w0BCQQxFgQUHHLpB+U7Ua93IF4KzVALvZIRMHYwUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAyxUP6c15DHmzFRMe
5uIZz9nvwgdig99ESuNklGQ/MSJAei73Azd9FWmB1TqQ2qCS0yKL9qxTMX7lPLcVNmF6U0p5
MlNIl1eM+E9tO5zfknd+WQXuaDISKO+V5BYMf0qieKkY4WnT/gDD5sGLMPwej3s207CJNqVN
+NYjQU6p44lIpgCCd3dT3ImfEbipC/0rnt47U7Tca9iws6T+lEaEZ6ulnzY9//IXR4WbERH+
ssPX2YSsN7Y+BLvlNNfm5yJYG2X/O4IChgNKpgzKoFvxZJXHJ+L9hxEoag0oGLbgnOG2eCII
4nopOc4X8uv/lB8GiLfHkWR9wZGV4LCOxnX9kg==
--=_zark-8153-1028828486-0001-2--

From bortzmeyer@nic.fr  Mon Aug 12 15:02:02 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Mon, 12 Aug 2002 16:02:02 +0200
Subject: [Ietf-not43] Using EPP for Crisp?
In-Reply-To: <3CD14E451751BD42BA48AAA50B07BAD60336FD2F@vsvapostal3.prod.netsol.com>
References: <3CD14E451751BD42BA48AAA50B07BAD60336FD2F@vsvapostal3.prod.netsol.com>
Message-ID: <20020812140202.GA8844@nic.fr>

On Thu, Aug 08, 2002 at 01:15:06PM -0400,
 Hollenbeck, Scott <shollenbeck@verisign.com> wrote 
 a message of 21 lines which said:

> I'd like to think that there might be some provreg data structures
> that might be useful within the CRISP effort,

I believe so, too. We are struggling with defining things like the
status of a domain, the exact meaning of "registrant", etc and it
would be a pity to have two different dictionaries for the two
protocols.


From bortzmeyer@nic.fr  Tue Aug 13 07:38:45 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Tue, 13 Aug 2002 08:38:45 +0200
Subject: [Ietf-not43] Mail address mandatory?
Message-ID: <20020813063845.GA16761@nic.fr>

I read in draft-ietf-crisp-lw-user-00.txt:

     The target inetOrgPerson entries MAY have any number of attributes 
     defined, with any number of access restrictions, as required by 
     local security policies, government regulations or personal 
     privacy concerns. However, the mail attribute MUST be defined, 
     MUST be valid, and MUST have anonymous read permissions. 

Why is it so (MUST have anonymous read permissions)? The email address
is often precisely the attribute some people want to hide (because of
spammers).

Anyway, it should be a matter of policy, I don't think it is
appropriate to put it in the protocol.



From ehall@ehsco.com  Tue Aug 13 14:44:04 2002
From: ehall@ehsco.com (Eric A. Hall)
Date: Tue, 13 Aug 2002 08:44:04 -0500
Subject: [Ietf-not43] Mail address mandatory?
References: <20020813063845.GA16761@nic.fr>
Message-ID: <3D590D24.2000809@ehsco.com>

on 8/13/2002 1:38 AM Stephane Bortzmeyer wrote:
> I read in draft-ietf-crisp-lw-user-00.txt:
> 
>      The target inetOrgPerson entries MAY have any number of attributes 
>      defined, with any number of access restrictions, as required by 
>      local security policies, government regulations or personal 
>      privacy concerns. However, the mail attribute MUST be defined, 
>      MUST be valid, and MUST have anonymous read permissions. 
> 
> Why is it so (MUST have anonymous read permissions)? The email address
> is often precisely the attribute some people want to hide (because of
> spammers).

The email address doesn't have to a primary account.

The reason I made it mandatory is that there is no other form of contact
information which is viable. Postal mail doesn't help when you are
suffering aa DoS attack from a specific network, for example.

There is another reason for using email addresses, which is that I plan to
define a lookup mechanism for contacts using the email addr as the lookup
key (EG, provide a way to find out which domains and netblocks are
associated with <bortzmeyer@nic.fr>). DITs aren't all that functional or
friendly outside the protocol.

> Anyway, it should be a matter of policy, I don't think it is
> appropriate to put it in the protocol.

Andy has made that argument in the past, too. In the end, it seems to me
that if there isn't any contact information available, there isn't any
benefit to the service.

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


From bortzmeyer@nic.fr  Fri Aug 16 08:39:36 2002
From: bortzmeyer@nic.fr (Stephane Bortzmeyer)
Date: Fri, 16 Aug 2002 09:39:36 +0200
Subject: [Ietf-not43] Mail address mandatory?
In-Reply-To: <3D590D24.2000809@ehsco.com>
References: <20020813063845.GA16761@nic.fr> <3D590D24.2000809@ehsco.com>
Message-ID: <20020816073936.GC22641@nic.fr>

On Tue, Aug 13, 2002 at 08:44:04AM -0500,
 Eric A. Hall <ehall@ehsco.com> wrote 
 a message of 36 lines which said:

> The email address doesn't have to a primary account.

[Sorry, I do not understand that one.]

> The reason I made it mandatory is that there is no other form of contact
> information which is viable. Postal mail doesn't help when you are
> suffering aa DoS attack from a specific network, for example.

But phone contact helps in that case and I could say that "email does
not help when there is completely broken network configuration which
prevents email". No contact channel is 100 % reliable in every case,
that's why we must have several.
 
> There is another reason for using email addresses, which is that I plan to
> define a lookup mechanism for contacts using the email addr as the lookup
> key (EG, provide a way to find out which domains and netblocks are
> associated with <bortzmeyer@nic.fr>).

IPR people would love to have it but ordinary people (not big
corporations lawyers) may disagree. I see that as a registry policy
issue, which should not be forced by a technical protocol.

> > Anyway, it should be a matter of policy, I don't think it is
> > appropriate to put it in the protocol.
> 
> Andy has made that argument in the past, too. 

People who agree with me must be really smart :-)

> In the end, it seems to me that if there isn't any contact
> information available, there isn't any benefit to the service.

For .eu, one of the ideas was to allow people to opt-out of all but
one contact information (they have to accept that at least one among
phone, fax or email, is public).


From Internet-Drafts@ietf.org  Fri Aug 16 12:45:33 2002
From: Internet-Drafts@ietf.org (Internet-Drafts@ietf.org)
Date: Fri, 16 Aug 2002 07:45:33 -0400
Subject: [Ietf-not43] I-D ACTION:draft-ietf-crisp-iris-areg-00.txt
Message-ID: <200208161145.HAA11913@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		: IRIS Address Registry Schema
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-areg-00.txt
	Pages		: 18
	Date		: 15-Aug-02
	
This document describes an IRIS registry id and schema for
registered Internet address information. The schema extends the
necessary query and result operations of IRIS
(draft-ietf-crisp-iris-core-00.txt) to provide the functional
information service needs for syntaxes and results used by Internet
address registries.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-areg-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-iris-areg-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-iris-areg-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:	<20020815150703.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-iris-areg-00.txt

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

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

--OtherAccess--

--NextPart--



From Internet-Drafts@ietf.org  Fri Aug 16 12:45:43 2002
From: Internet-Drafts@ietf.org (Internet-Drafts@ietf.org)
Date: Fri, 16 Aug 2002 07:45:43 -0400
Subject: [Ietf-not43] I-D ACTION:draft-ietf-crisp-iris-core-00.txt
Message-ID: <200208161145.HAA11945@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		: Internet Registry Information Service (IRIS)
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-core-00.txt
	Pages		: 31
	Date		: 15-Aug-02
	
This document describes an application layer client-server protocol
for a framework of representing the query and result operations of
the information services of Internet registries. Specified in XML,
the protocol defines generic query and result operations and a
mechanism for extending these operations for specific registry
service needs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-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-iris-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-iris-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:	<20020815150735.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--



From Internet-Drafts@ietf.org  Fri Aug 16 12:45:38 2002
From: Internet-Drafts@ietf.org (Internet-Drafts@ietf.org)
Date: Fri, 16 Aug 2002 07:45:38 -0400
Subject: [Ietf-not43] I-D ACTION:draft-ietf-crisp-iris-dreg-00.txt
Message-ID: <200208161145.HAA11929@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		: IRIS Domain Registry Schema
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-dreg-00.txt
	Pages		: 28
	Date		: 15-Aug-02
	
This document describes an IRIS (draft-ietf-crisp-iris-core-00.txt )
registry schema for registered DNS information. The schema extends
the necessary query and result operations of IRIS to provide the
functional information service needs for syntaxes and results used
by domain registries and registrars.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-dreg-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-iris-dreg-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-iris-dreg-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:	<20020815150724.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-iris-dreg-00.txt

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

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

--OtherAccess--

--NextPart--



From Internet-Drafts@ietf.org  Fri Aug 16 12:45:48 2002
From: Internet-Drafts@ietf.org (Internet-Drafts@ietf.org)
Date: Fri, 16 Aug 2002 07:45:48 -0400
Subject: [Ietf-not43] I-D ACTION:draft-ietf-crisp-iris-beep-00.txt
Message-ID: <200208161145.HAA11961@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		: Using the Internet Registry Information Service (IRIS)
                          over the Blocks Extensible Exchange Protocol (BEEP)
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-beep-00.txt
	Pages		: 17
	Date		: 15-Aug-02
	
This document specifies how to use the Blocks Extensible Exchange
Protocol (BEEP) as the application transport substrate for the
Internet Registry Information Service (IRIS) as described
draft-ietf-crisp-iris-core-00.txt.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-beep-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-iris-beep-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-iris-beep-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:	<20020815150746.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-iris-beep-00.txt

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

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

--OtherAccess--

--NextPart--



From ehall@ehsco.com  Fri Aug 16 15:04:00 2002
From: ehall@ehsco.com (Eric A. Hall)
Date: Fri, 16 Aug 2002 09:04:00 -0500
Subject: [Ietf-not43] Mail address mandatory?
References: <20020813063845.GA16761@nic.fr> <3D590D24.2000809@ehsco.com> <20020816073936.GC22641@nic.fr>
Message-ID: <3D5D0650.3090609@ehsco.com>

on 8/16/2002 2:39 AM Stephane Bortzmeyer wrote:
> On Tue, Aug 13, 2002 at 08:44:04AM -0500, Eric A. Hall
> <ehall@ehsco.com> wrote

>> The email address doesn't have to a primary account.
>
> [Sorry, I do not understand that one.]

You are not required to use <bortzmeyer@nic.fr>, but can instead use
<junk@hotmail.com> if you don't want to expose your real address.

>> The reason I made it mandatory is that there is no other form of
>> contact information which is viable. Postal mail doesn't help when
>> you are suffering aa DoS attack from a specific network, for example.
>>
>
> But phone contact helps in that case and I could say that "email does
> not help when there is completely broken network configuration which
> prevents email". No contact channel is 100 % reliable in every case,
> that's why we must have several.

This sounds like a good reason to mandate TWO contact forms. There's no
way I'd get away with that so I picked one that had to be provided. People
can provide as much or as little as they want but they have to provide
this one at a minimum.

>> In the end, it seems to me that if there isn't any contact
>> information available, there isn't any benefit to the service.
>
> For .eu, one of the ideas was to allow people to opt-out of all but one
> contact information (they have to accept that at least one among phone,
> fax or email, is public).

Can you please provide a pointer to the definitive policy statement? This
issue is not resolved in my mind either, and I'd like to see other texts
which may help.

>> There is another reason for using email addresses, which is that I
>> plan to define a lookup mechanism for contacts using the email addr
>> as the lookup key (EG, provide a way to find out which domains and
>> netblocks are associated with <bortzmeyer@nic.fr>).
>
> IPR people would love to have it but ordinary people (not big
> corporations lawyers) may disagree. I see that as a registry policy
> issue, which should not be forced by a technical protocol.

The profile will have to be voluntary. Since a favored email address will
reside in a single DIT -- but the associated resources will each reside in
their own independent DITs -- linking the different DITs will have to be
voluntary. EG, if I update my ntrg.com entry to point to ehall@ehsco.com,
there is no way that the owner of the ntrg.com entry will be able to
update the ehall@ehsco.com entry. As such, I will have to make that update
myself, meaning that it would be voluntary.

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


From anewton@ecotroph.net  Fri Aug 16 15:51:57 2002
From: anewton@ecotroph.net (Andrew Newton)
Date: Fri, 16 Aug 2002 10:51:57 -0400
Subject: [Ietf-not43] new IRIS drafts
Message-ID: <3D5D118D.E45C6E6D@ecotroph.net>

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zark-8978-1029510161-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Unofficial HTML versions may be fetched from here:
http://www.ecotroph.net/~anewton/

While the concepts have not changed, much of the terminology in the core
draft has changed to be clearer.  Admittedly, the old versions were a
bit confusing.

The other significant change is in the application-transport layer.

-andy
--=_zark-8978-1029510161-0001-2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIII9AYJKoZIhvcNAQcCoIII5TCCCOECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BkYwggMGMIICb6ADAgECAgMHMt4wDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh
d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg
RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA0MTAxODU4MjBaFw0wMzA0MTAxODU4MjBa
MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFGFu
ZXd0b25AZWNvdHJvcGgubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5Kc4
10hpxiGBE08UE3H/qKMXC/cx3lQeVKk7/dKSUNZkspeOXZiH/oFyl9tQtcIxQ216EvXo53T1
2QBB044fo+CkitDYvt1zZSHLQY9cBDR3s8FqA7HVHOAyC7BMqUPaSBaliaXDOlPbXBxOkuGY
sBdRAzRv51UdW3HoWAhkGBWCzMCVMru7e1ZGrwtrYqaWXJN37spr7QgHdVmXhjOSu7rMmiDC
UW5IneJomR+nHNiFmjqFqMxFpJw/5MmdjPCjS8iVwbSU0QpFepenIc/Fr0pBH/qDlEX1Tawr
sLlRJA+npwO97b2VViAdajF35k+6c7ZMl4C5NAF0fvN6qzEWfQIDAQABozEwLzAfBgNVHREE
GDAWgRRhbmV3dG9uQGVjb3Ryb3BoLm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAHF4Ljf5CziCiMSNwm++3gO/XyAXz0aPUNoQNtPj+C3CndMZIgKsxIUnYbLM0EYcZFDZ
O2QTpLB53zq2hT1sdPs3YpgXkJY31s+JsT6zOR6zDYYtdqNuE0cb/BzIZIzhRJlcl3M7zHoy
h/0PnY54cc7m6StJtmfbc2n/sCu1YCoyMIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6R
ATANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp
bEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNV
BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0G
A1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMf
UGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
gYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRx
oKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGH
gzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQD
AgEGMA0GCSqGSIb3DQEBBAUAA4GBADGxS0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3
J3sEObr85vIk65H6vewNKjj3UFWobPcNrUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBd
avl50OouJd2K5PzbDR+dAvNa28o89kTqJmmHf0iezqWf54TYyWJirQXGMYICdjCCAnICAQEw
gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl
czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBzLeMAkGBSsO
AwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDIw
ODE2MTQ1MTU3WjAjBgkqhkiG9w0BCQQxFgQUTGWrRzY/94+BG/DnVc2HkB7EgpowUgYJKoZI
hvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZI
hvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAezgb7GoZEGzzU1p2
OGt5OybSpU6XsdICynoI55dOIN8IjQBlztiYN75Dx4CsLZJy2LPKMee3j6/MoBQeLkINozfK
6ex05IHhznGBFORMTHOuuoL5WjQcl21U7dFBZ0PBVogaV9qi/oRgwVPmBwwnsHDpvKfVfMHQ
myi915BWxToGi9gUd1CzEL/gy6EnkglH2X5QbQwSv3tMpcjToWBZKrJ8Rh+GNLIXN6F8ToXl
R+cSmS+J0N34xucjbFODaVh8eAKDdtUdYV3QTRq2SMkaOQCqE9RSqk0OACkUfPx6CsOpvWp1
fkwqHxPugeTSi2Fwa8JzTsEicpvGFWPYF43C8g==
--=_zark-8978-1029510161-0001-2--

From PRoberts@MEGISTO.com  Tue Aug 27 19:44:44 2002
From: PRoberts@MEGISTO.com (Phil Roberts)
Date: Tue, 27 Aug 2002 14:44:44 -0400
Subject: [Ietf-not43] Nomcom call for volunteers
Message-ID: <200208271844.OAA06546@ietf.org>

The members of the IESG and IAB and the IETF chair are selected
by a nominations committee made up of volunteers from the
IETF community.  The nominations committee is now in the process
of being formed and volunteers are being accepted until Sep 6.
Please see (http://www.ietf.org/nomcom/msg19765.html)
for information if you are interested in volunteering 
to be on the nominations committee.

