From owner-ietf-provreg@cafax.se  Mon Sep 22 09:10:25 2003
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13564
	for <provreg-archive@ietf.org>; Mon, 22 Sep 2003 09:10:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1QSQ-0006rI-00
	for provreg-archive@ietf.org; Mon, 22 Sep 2003 09:10:27 -0400
Received: from nic.cafax.se ([192.71.228.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1QSG-0006q3-00
	for provreg-archive@ietf.org; Mon, 22 Sep 2003 09:10:16 -0400
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MCnk6K016749
	for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 22 Sep 2003 14:49:46 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h8MCnkF4016748
	for ietf-provreg-outgoing; Mon, 22 Sep 2003 14:49:46 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.237.102])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MCnj6K016743
	for <ietf-provreg@cafax.se>; Mon, 22 Sep 2003 14:49:45 +0200 (MEST)
Received: from vsvapostalgw3.prod.netsol.com (vsvapostalgw3.prod.netsol.com [10.170.12.61])
	by heron.verisign.com (8.12.9/8.12.9) with ESMTP id h8MCnhcf025364
	for <ietf-provreg@cafax.se>; Mon, 22 Sep 2003 08:49:44 -0400 (EDT)
Received: by vsvapostalgw3.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <TDS5417D>; Mon, 22 Sep 2003 08:49:43 -0400
Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF82B77F@vsvapostal8.vasrv.verisign.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: [ietf-provreg] Standard EPP Port Number Assigned
Date: Mon, 22 Sep 2003 08:49:43 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

IANA has assigned standard port numbers for EPP.  Here's the relevant text
from the notice I received:

"We have assigned system port number 700 for epp and
have marked the user port number 3121 as unassigned,
returning it back to IANA.

Please see: <http://www.iana.org/assignments/port-numbers>"

IANA will eventually create a registry for XML namespaces and schemas.  Once
that's done their actions will be completed and the documents will be
further along the RFC publication path.

-Scott-


From owner-ietf-provreg@cafax.se  Mon Sep 22 11:20:08 2003
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20089
	for <provreg-archive@ietf.org>; Mon, 22 Sep 2003 11:19:50 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MF7e6K018026
	for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 22 Sep 2003 17:07:40 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h8MF7e2p018025
	for ietf-provreg-outgoing; Mon, 22 Sep 2003 17:07:40 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from nicolette.nic.cl (cisco.nic.cl [206.49.218.90])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MF7c6K018020
	for <ietf-provreg@cafax.se>; Mon, 22 Sep 2003 17:07:39 +0200 (MEST)
Received: from nic.cl (zion.intra.nic.cl [172.30.10.53])
	by nicolette.nic.cl (8.12.8/8.12.8) with ESMTP id h8MF7aCZ012745
	for <ietf-provreg@cafax.se>; Mon, 22 Sep 2003 11:07:37 -0400
Message-ID: <3F6F103D.603@nic.cl>
Date: Mon, 22 Sep 2003 11:07:41 -0400
From: "Cristian Rojas R." <crrojas@nic.cl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-provreg@cafax.se
Subject: [ietf-provreg] EPP and wildcards
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello all:

    This can be a stupid question, but I don't want to remain with the 
doubt. Can EPP use wildcards (particularly regular expressions)? I show 
you an example:
...
C:  <command>
C:    <check>
C:      <domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C:                    xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C:                    domain-1.0.xsd">
C:        <domain:name>epp*.tld</domain:name>
C:      </domain:check>
C:    </check>
C:    <clTRID>any-thing</clTRID>
C:  </command>
...
S:  <response>
S:     <result code="1000">
S:        <msg>Command completed successfully</msg>
S:     </result>
S:        <resData>
S:           <domain:chkData 
xmlns:contact="urn:ietf:params:xml:ns:domain-1.0" 
xssi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0 domain-1.0.xsd">
S:              <domain:cd>
S:                 <domain:name avail="0">eppXX.tld</domain:name>
S:                 <domain:reason avail="0">In use</domain:reason> 
S:              </domain:cd>
S:              <domain:cd>
S:                 <domain:name avail="0">eppYY.tld</domain:name>
S:                 <domain:reason avail="0">In use</domain:reason> 
S:              </domain:cd>
S:              <domain:cd>
S:                 <domain:name avail="0">eppZZ.tld</domain:name>
S:                 <domain:reason avail="0">In use</domain:reason> 
S:               </domain:cd>
...

    I'm thinking in the implementation of a whois server based in EPP 
(for the comunication between whois server an registry's EPP server). 
This whois must accept regular expressions (just like Afilias whois). I 
think that is not possible use EPP with RE, but I prefer to ask.
   

-- 
Cristian A. Rojas R. <crrojas@nic.cl>   NIC Chile
Agustinas 1357 4to Piso, Codigo Postal 6500587, Santiago Chile
Phone: (562) 940 77 00   Fax: (562) 940 77 01




From owner-ietf-provreg@cafax.se  Mon Sep 22 15:31:40 2003
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04324
	for <provreg-archive@ietf.org>; Mon, 22 Sep 2003 15:31:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1WPI-0001LS-00
	for provreg-archive@ietf.org; Mon, 22 Sep 2003 15:31:36 -0400
Received: from nic.cafax.se ([192.71.228.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1WP7-00016O-00
	for provreg-archive@ietf.org; Mon, 22 Sep 2003 15:31:25 -0400
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MJGA6K020153
	for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 22 Sep 2003 21:16:10 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h8MJGAiZ020152
	for ietf-provreg-outgoing; Mon, 22 Sep 2003 21:16:10 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.237.102])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MJG86K020147
	for <ietf-provreg@cafax.se>; Mon, 22 Sep 2003 21:16:08 +0200 (MEST)
Received: from vsvapostalgw3.prod.netsol.com (vsvapostalgw3.prod.netsol.com [10.170.12.61])
	by heron.verisign.com (8.12.9/8.12.9) with ESMTP id h8MJG6cf008957;
	Mon, 22 Sep 2003 15:16:07 -0400 (EDT)
Received: by vsvapostalgw3.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <TDS543QT>; Mon, 22 Sep 2003 15:16:06 -0400
Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF014A8EA7@vsvapostal8.vasrv.verisign.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Cristian Rojas R.'" <crrojas@nic.cl>,
        "'ietf-provreg@cafax.se'"
	 <ietf-provreg@cafax.se>
Subject: RE: [ietf-provreg] EPP and wildcards
Date: Mon, 22 Sep 2003 15:16:07 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

The data type used to define domain names is defined in section 4.2 of the
EPP core protocol draft.  Look for the "<simpleType name="labelType">"
definition; it uses the XML schema "token" data type.  This XML Schema data
type allows use of the "*" character.

However, section 2.1 of the domain draft requires conformance with RFCs 952
and 1123.  These don't allow the "*" character in domain names.  You could
use the EPP core data type to define a schema of your own for domain
searching, but searching as you described isn't supported in the domain
draft.

-Scott-

> -----Original Message-----
> From: Cristian Rojas R. [mailto:crrojas@nic.cl] 
> Sent: Monday, September 22, 2003 11:08 AM
> To: ietf-provreg@cafax.se
> Subject: [ietf-provreg] EPP and wildcards
> 
> 
> Hello all:
> 
>     This can be a stupid question, but I don't want to remain 
> with the 
> doubt. Can EPP use wildcards (particularly regular 
> expressions)? I show 
> you an example:
> ...
> C:  <command>
> C:    <check>
> C:      <domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
> C:                    
> xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
> C:                    domain-1.0.xsd">
> C:        <domain:name>epp*.tld</domain:name>
> C:      </domain:check>
> C:    </check>
> C:    <clTRID>any-thing</clTRID>
> C:  </command>
> ...
> S:  <response>
> S:     <result code="1000">
> S:        <msg>Command completed successfully</msg>
> S:     </result>
> S:        <resData>
> S:           <domain:chkData 
> xmlns:contact="urn:ietf:params:xml:ns:domain-1.0" 
> xssi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0 
> domain-1.0.xsd">
> S:              <domain:cd>
> S:                 <domain:name avail="0">eppXX.tld</domain:name>
> S:                 <domain:reason avail="0">In use</domain:reason> 
> S:              </domain:cd>
> S:              <domain:cd>
> S:                 <domain:name avail="0">eppYY.tld</domain:name>
> S:                 <domain:reason avail="0">In use</domain:reason> 
> S:              </domain:cd>
> S:              <domain:cd>
> S:                 <domain:name avail="0">eppZZ.tld</domain:name>
> S:                 <domain:reason avail="0">In use</domain:reason> 
> S:               </domain:cd>
> ...
> 
>     I'm thinking in the implementation of a whois server based in EPP 
> (for the comunication between whois server an registry's EPP server). 
> This whois must accept regular expressions (just like Afilias 
> whois). I 
> think that is not possible use EPP with RE, but I prefer to ask.
>    
> 
> -- 
> Cristian A. Rojas R. <crrojas@nic.cl>   NIC Chile
> Agustinas 1357 4to Piso, Codigo Postal 6500587, Santiago Chile
> Phone: (562) 940 77 00   Fax: (562) 940 77 01
> 


From owner-ietf-provreg@cafax.se  Tue Sep 30 16:48:36 2003
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15239
	for <provreg-archive@ietf.org>; Tue, 30 Sep 2003 16:48:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4RQJ-00057e-00
	for provreg-archive@ietf.org; Tue, 30 Sep 2003 16:48:43 -0400
Received: from nic.cafax.se ([192.71.228.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4RQI-00057V-00
	for provreg-archive@ietf.org; Tue, 30 Sep 2003 16:48:42 -0400
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8UKX16K026851
	for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 30 Sep 2003 22:33:01 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h8UKX1sq026850
	for ietf-provreg-outgoing; Tue, 30 Sep 2003 22:33:01 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from smtp2.arin.net (smtp2.arin.net [192.149.252.32])
	by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8UKWx6K026845
	for <ietf-provreg@cafax.se>; Tue, 30 Sep 2003 22:33:00 +0200 (MEST)
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id 89DBC508; Tue, 30 Sep 2003 16:32:56 -0400 (EDT)
Received: from arin.net (mta [192.136.136.126])
	by smtp2.arin.net (Postfix) with ESMTP id 4D5AF52D
	for <ietf-provreg@cafax.se>; Tue, 30 Sep 2003 16:32:55 -0400 (EDT)
Received: from [127.0.0.1] (HELO [192.149.252.108])
  by arin.net (CommuniGate Pro SMTP 4.1)
  with ESMTP id 824374; Tue, 30 Sep 2003 16:27:49 -0400
Mime-Version: 1.0
X-Sender: edlewis@127.0.0.1
Message-Id: <a05111b0fbb9f956642ee@[192.149.252.108]>
Date: Tue, 30 Sep 2003 16:32:50 -0400
To: ietf-provreg@cafax.se
From: Edward Lewis <edlewis@arin.net>
Subject: [ietf-provreg] where we are
Cc: edlewis@arin.net
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Status: No, hits=-1.6 required=5.0
	tests=SIGNATURE_SHORT_SPARSE,SPAM_PHRASE_01_02
	version=2.43-arin1
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

(Off the top of my head as September draws to a close...)

It's been nearly 5 months since the IESG has approved our documents 
at the Proposed Standards level.  The documents have moved into the 
RFC Editor's Queue where they have been held up because we reference 
another document.  (The other document was trailing ours, but that 
document has been approved.)

We do have a port number reserved, mail of that was sent out a few weeks ago.

What's next?

Well, the design of the WG is to close down after the documents are 
in the RFC series.  We are hanging around, in form, only to make sure 
there are no hiccups with the publication of the documents.  We have 
no milestones left, we do not plan to meet in Minneapolis.

The mailing list will be available after the WG folds.  And reaching 
Proposed Standard isn't the ultimate goal - the next level is Draft 
Standard.

Draft standard is achieved by meeting criteria in RFC 2026.  There 
are two I want to highlight.

1) A report of interoperability of implementations.  At least two 
completely independent implementations are needed, that's client and 
server, and there has to be a test and report that reports on how 
clear the specifications are.  (That's Client X with Server Y, Client 
Y with Server X.)

This is not a product comparison, it's not important if Client Z is 
broken, it's whether two folks could read the same words and wrote 
code that follows the protocol as intended.  This is a measure of how 
clear the specifications are.  Not a measure of the implementors.

2) There's a 6 month delay between PS and DS - at a minimum.  The 
delay isn't the big hurdle in anyway.  In fact, next week will mark 5 
months since the IESG approved our documents.  I've asked a few folks 
if these 5 months count towards the 6, some answered yes and some 
said it should start with the port number assignment.

Either way, I'm sure the interoperability hurdle is the greater feat.

Those wishing to push this effort towards Draft (and maybe eventually 
Full) Standard ought to keep this points in mind.  What is needed are 
implementations, then testing, and then maybe a proposed BOF/Charter 
to constitute a WG for the next level of review.  There's no reason 
to "wait" because of the RFC 2026 calendar delays.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                            +1-703-227-9854
ARIN Research Engineer

Sponge Bob Square Pants?  I'm still trying to figure out the Macarena.



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8UKX16K026851 for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 30 Sep 2003 22:33:01 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h8UKX1sq026850 for ietf-provreg-outgoing; Tue, 30 Sep 2003 22:33:01 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from smtp2.arin.net (smtp2.arin.net [192.149.252.32]) by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8UKWx6K026845 for <ietf-provreg@cafax.se>; Tue, 30 Sep 2003 22:33:00 +0200 (MEST)
Received: by smtp2.arin.net (Postfix, from userid 5003) id 89DBC508; Tue, 30 Sep 2003 16:32:56 -0400 (EDT)
Received: from arin.net (mta [192.136.136.126]) by smtp2.arin.net (Postfix) with ESMTP id 4D5AF52D for <ietf-provreg@cafax.se>; Tue, 30 Sep 2003 16:32:55 -0400 (EDT)
Received: from [127.0.0.1] (HELO [192.149.252.108]) by arin.net (CommuniGate Pro SMTP 4.1) with ESMTP id 824374; Tue, 30 Sep 2003 16:27:49 -0400
Mime-Version: 1.0
X-Sender: edlewis@127.0.0.1
Message-Id: <a05111b0fbb9f956642ee@[192.149.252.108]>
Date: Tue, 30 Sep 2003 16:32:50 -0400
To: ietf-provreg@cafax.se
From: Edward Lewis <edlewis@arin.net>
Subject: [ietf-provreg] where we are
Cc: edlewis@arin.net
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Status: No, hits=-1.6 required=5.0 tests=SIGNATURE_SHORT_SPARSE,SPAM_PHRASE_01_02 version=2.43-arin1
X-Spam-Level: 
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

(Off the top of my head as September draws to a close...)

It's been nearly 5 months since the IESG has approved our documents 
at the Proposed Standards level.  The documents have moved into the 
RFC Editor's Queue where they have been held up because we reference 
another document.  (The other document was trailing ours, but that 
document has been approved.)

We do have a port number reserved, mail of that was sent out a few weeks ago.

What's next?

Well, the design of the WG is to close down after the documents are 
in the RFC series.  We are hanging around, in form, only to make sure 
there are no hiccups with the publication of the documents.  We have 
no milestones left, we do not plan to meet in Minneapolis.

The mailing list will be available after the WG folds.  And reaching 
Proposed Standard isn't the ultimate goal - the next level is Draft 
Standard.

Draft standard is achieved by meeting criteria in RFC 2026.  There 
are two I want to highlight.

1) A report of interoperability of implementations.  At least two 
completely independent implementations are needed, that's client and 
server, and there has to be a test and report that reports on how 
clear the specifications are.  (That's Client X with Server Y, Client 
Y with Server X.)

This is not a product comparison, it's not important if Client Z is 
broken, it's whether two folks could read the same words and wrote 
code that follows the protocol as intended.  This is a measure of how 
clear the specifications are.  Not a measure of the implementors.

2) There's a 6 month delay between PS and DS - at a minimum.  The 
delay isn't the big hurdle in anyway.  In fact, next week will mark 5 
months since the IESG approved our documents.  I've asked a few folks 
if these 5 months count towards the 6, some answered yes and some 
said it should start with the port number assignment.

Either way, I'm sure the interoperability hurdle is the greater feat.

Those wishing to push this effort towards Draft (and maybe eventually 
Full) Standard ought to keep this points in mind.  What is needed are 
implementations, then testing, and then maybe a proposed BOF/Charter 
to constitute a WG for the next level of review.  There's no reason 
to "wait" because of the RFC 2026 calendar delays.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                            +1-703-227-9854
ARIN Research Engineer

Sponge Bob Square Pants?  I'm still trying to figure out the Macarena.


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MJGA6K020153 for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 22 Sep 2003 21:16:10 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h8MJGAiZ020152 for ietf-provreg-outgoing; Mon, 22 Sep 2003 21:16:10 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.237.102]) by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MJG86K020147 for <ietf-provreg@cafax.se>; Mon, 22 Sep 2003 21:16:08 +0200 (MEST)
Received: from vsvapostalgw3.prod.netsol.com (vsvapostalgw3.prod.netsol.com [10.170.12.61]) by heron.verisign.com (8.12.9/8.12.9) with ESMTP id h8MJG6cf008957; Mon, 22 Sep 2003 15:16:07 -0400 (EDT)
Received: by vsvapostalgw3.prod.netsol.com with Internet Mail Service (5.5.2653.19) id <TDS543QT>; Mon, 22 Sep 2003 15:16:06 -0400
Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF014A8EA7@vsvapostal8.vasrv.verisign.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Cristian Rojas R.'" <crrojas@nic.cl>, "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: RE: [ietf-provreg] EPP and wildcards
Date: Mon, 22 Sep 2003 15:16:07 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

The data type used to define domain names is defined in section 4.2 of the
EPP core protocol draft.  Look for the "<simpleType name="labelType">"
definition; it uses the XML schema "token" data type.  This XML Schema data
type allows use of the "*" character.

However, section 2.1 of the domain draft requires conformance with RFCs 952
and 1123.  These don't allow the "*" character in domain names.  You could
use the EPP core data type to define a schema of your own for domain
searching, but searching as you described isn't supported in the domain
draft.

-Scott-

> -----Original Message-----
> From: Cristian Rojas R. [mailto:crrojas@nic.cl] 
> Sent: Monday, September 22, 2003 11:08 AM
> To: ietf-provreg@cafax.se
> Subject: [ietf-provreg] EPP and wildcards
> 
> 
> Hello all:
> 
>     This can be a stupid question, but I don't want to remain 
> with the 
> doubt. Can EPP use wildcards (particularly regular 
> expressions)? I show 
> you an example:
> ...
> C:  <command>
> C:    <check>
> C:      <domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
> C:                    
> xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
> C:                    domain-1.0.xsd">
> C:        <domain:name>epp*.tld</domain:name>
> C:      </domain:check>
> C:    </check>
> C:    <clTRID>any-thing</clTRID>
> C:  </command>
> ...
> S:  <response>
> S:     <result code="1000">
> S:        <msg>Command completed successfully</msg>
> S:     </result>
> S:        <resData>
> S:           <domain:chkData 
> xmlns:contact="urn:ietf:params:xml:ns:domain-1.0" 
> xssi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0 
> domain-1.0.xsd">
> S:              <domain:cd>
> S:                 <domain:name avail="0">eppXX.tld</domain:name>
> S:                 <domain:reason avail="0">In use</domain:reason> 
> S:              </domain:cd>
> S:              <domain:cd>
> S:                 <domain:name avail="0">eppYY.tld</domain:name>
> S:                 <domain:reason avail="0">In use</domain:reason> 
> S:              </domain:cd>
> S:              <domain:cd>
> S:                 <domain:name avail="0">eppZZ.tld</domain:name>
> S:                 <domain:reason avail="0">In use</domain:reason> 
> S:               </domain:cd>
> ...
> 
>     I'm thinking in the implementation of a whois server based in EPP 
> (for the comunication between whois server an registry's EPP server). 
> This whois must accept regular expressions (just like Afilias 
> whois). I 
> think that is not possible use EPP with RE, but I prefer to ask.
>    
> 
> -- 
> Cristian A. Rojas R. <crrojas@nic.cl>   NIC Chile
> Agustinas 1357 4to Piso, Codigo Postal 6500587, Santiago Chile
> Phone: (562) 940 77 00   Fax: (562) 940 77 01
> 


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MF7e6K018026 for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 22 Sep 2003 17:07:40 +0200 (MEST)
Received: by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h8MF7e2p018025 for ietf-provreg-outgoing; Mon, 22 Sep 2003 17:07:40 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from nicolette.nic.cl (cisco.nic.cl [206.49.218.90]) by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MF7c6K018020 for <ietf-provreg@cafax.se>; Mon, 22 Sep 2003 17:07:39 +0200 (MEST)
Received: from nic.cl (zion.intra.nic.cl [172.30.10.53]) by nicolette.nic.cl (8.12.8/8.12.8) with ESMTP id h8MF7aCZ012745 for <ietf-provreg@cafax.se>; Mon, 22 Sep 2003 11:07:37 -0400
Message-ID: <3F6F103D.603@nic.cl>
Date: Mon, 22 Sep 2003 11:07:41 -0400
From: "Cristian Rojas R." <crrojas@nic.cl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-provreg@cafax.se
Subject: [ietf-provreg] EPP and wildcards
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Hello all:

    This can be a stupid question, but I don't want to remain with the 
doubt. Can EPP use wildcards (particularly regular expressions)? I show 
you an example:
...
C:  <command>
C:    <check>
C:      <domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C:                    xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C:                    domain-1.0.xsd">
C:        <domain:name>epp*.tld</domain:name>
C:      </domain:check>
C:    </check>
C:    <clTRID>any-thing</clTRID>
C:  </command>
...
S:  <response>
S:     <result code="1000">
S:        <msg>Command completed successfully</msg>
S:     </result>
S:        <resData>
S:           <domain:chkData 
xmlns:contact="urn:ietf:params:xml:ns:domain-1.0" 
xssi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0 domain-1.0.xsd">
S:              <domain:cd>
S:                 <domain:name avail="0">eppXX.tld</domain:name>
S:                 <domain:reason avail="0">In use</domain:reason> 
S:              </domain:cd>
S:              <domain:cd>
S:                 <domain:name avail="0">eppYY.tld</domain:name>
S:                 <domain:reason avail="0">In use</domain:reason> 
S:              </domain:cd>
S:              <domain:cd>
S:                 <domain:name avail="0">eppZZ.tld</domain:name>
S:                 <domain:reason avail="0">In use</domain:reason> 
S:               </domain:cd>
...

    I'm thinking in the implementation of a whois server based in EPP 
(for the comunication between whois server an registry's EPP server). 
This whois must accept regular expressions (just like Afilias whois). I 
think that is not possible use EPP with RE, but I prefer to ask.
   

-- 
Cristian A. Rojas R. <crrojas@nic.cl>   NIC Chile
Agustinas 1357 4to Piso, Codigo Postal 6500587, Santiago Chile
Phone: (562) 940 77 00   Fax: (562) 940 77 01




Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MCnk6K016749 for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 22 Sep 2003 14:49:46 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0/Submit) id h8MCnkF4016748 for ietf-provreg-outgoing; Mon, 22 Sep 2003 14:49:46 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.237.102]) by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h8MCnj6K016743 for <ietf-provreg@cafax.se>; Mon, 22 Sep 2003 14:49:45 +0200 (MEST)
Received: from vsvapostalgw3.prod.netsol.com (vsvapostalgw3.prod.netsol.com [10.170.12.61]) by heron.verisign.com (8.12.9/8.12.9) with ESMTP id h8MCnhcf025364 for <ietf-provreg@cafax.se>; Mon, 22 Sep 2003 08:49:44 -0400 (EDT)
Received: by vsvapostalgw3.prod.netsol.com with Internet Mail Service (5.5.2653.19) id <TDS5417D>; Mon, 22 Sep 2003 08:49:43 -0400
Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF82B77F@vsvapostal8.vasrv.verisign.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: [ietf-provreg] Standard EPP Port Number Assigned
Date: Mon, 22 Sep 2003 08:49:43 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

IANA has assigned standard port numbers for EPP.  Here's the relevant text
from the notice I received:

"We have assigned system port number 700 for epp and
have marked the user port number 3121 as unassigned,
returning it back to IANA.

Please see: <http://www.iana.org/assignments/port-numbers>"

IANA will eventually create a registry for XML namespaces and schemas.  Once
that's done their actions will be completed and the documents will be
further along the RFC publication path.

-Scott-


Return-Path: <johnnvcl@EconomicGrowthNetwork.com>
Received: from EconomicGrowthNetwork.com (host34.200-45-218.telecom.net.ar [200.45.218.34]) by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with SMTP id h875rg6K021397; Sun, 7 Sep 2003 07:53:59 +0200 (MEST)
Message-ID: <1a9f01c37502$4acf9b90$ab685ba2@llkblosw>
Reply-To: johnnvcl@EconomicGrowthNetwork.com
From: johnnvcl@EconomicGrowthNetwork.com
To: "Manager" <liman@cafax.se>
Cc: <ietf-provreg-logger@cafax.se>
Subject: GlobalTradeIndex Link - No Charge!       Owe
Date: Sun, 07 Sep 2003 17:38:40 +1200
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_2DB_3965_25339844.F594C273"
X-Priority: 3
User-Agent: MIME-tools 5.503 (Entity 5.501)

------=_NextPart_2DB_3965_25339844.F594C273
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


------=_NextPart_2DB_3965_25339844.F594C273
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64


PGh0bWw+DQoNCjxib2R5IHRleHQ9IiMwMEZGRkYiIGJnY29sb3I9IiMxNzE4
MDEiIGxpbms9IiNGRkZGMDAiIHZsaW5rPSIjMDBGRjAwIiBhbGluaz0iIzAw
MDBGRiI+DQoNCjxkaXYgYWxpZ249ImNlbnRlciI+DQogIDxjZW50ZXI+DQog
IDx0YWJsZSBib3JkZXI9IjMiIGNlbGxwYWRkaW5nPSIzIiBjZWxsc3BhY2lu
Zz0iMyIgd2lkdGg9IjQ1MCIgYm9yZGVyY29sb3I9IiNDMEMwQzAiIGJvcmRl
cmNvbG9ybGlnaHQ9IiM4MDAwMDAiIGJvcmRlcmNvbG9yZGFyaz0iI0ZGQ0Mw
MCI+DQogICAgPHRyPg0KICAgICAgPHRkPjxhIGhyZWY9Imh0dHA6Ly93d3cu
RWNvbm9taWNHcm93dGhOZXR3b3JrLmNvbSI+PGltZyBzcmM9Imh0dHA6Ly9l
Y29ub21pY2dyb3d0aG5ldHdvcmsuY29tL2VkZ2Vsb2dvLmpwZyIgYWxpZ249
ImxlZnQiIHZhbGlnbj0idG9wIiB3aWR0aD0iNDc0IiBoZWlnaHQ9IjEwMiI+
PC9hPjwvdGQ+DQogICAgPC90cj4NCiAgICA8dHI+DQogICAgICA8dGQ+DQog
ICAgICAgIDxwIGFsaWduPSJjZW50ZXIiPjxicj4NCiAgICAgICAgPHU+PGI+
PGZvbnQgY29sb3I9IiNGRkNDMDAiIHNpemU9IjQiPlRoZSBFY29ub21pYyBH
cm93dGggTmV0d29yazwvZm9udD48L2I+PC91PjwvcD4NCiAgICAgICAgPHAg
YWxpZ249ImNlbnRlciI+PGI+PGZvbnQgY29sb3I9IiNGRkZGRkYiPldlIHdv
dWxkIGxpa2UgdG8gaW52aXRlIHlvdXINCiAgICAgICAgY29tcGFueSBvciBv
cmdhbml6YXRpb24gdG8gbGlzdCB5b3VyIGJ1c2luZXNzIG9uIEdsb2JhbFRy
YWRlSW5kZXguY29tDQogICAgICAgIGFuZCBiZWNvbWUgYSBtZW1iZXIgb2Yg
dGhlIEVjb25vbWljIEdyb3d0aCBOZXR3b3JrLCZuYnNwOyBhIG5ldw0KICAg
ICAgICBtYXJrZXRpbmcmbmJzcDs8YnI+DQogICAgICAgIHN0cmF0ZWd5IGZv
ciBidXNpbmVzcywgV29ybGR3aWRlITxicj4NCiAgICAgICAgPGJyPg0KICAg
ICAgICBMaXN0aW5ncyBhcmUgYXQgbm8gY2hhcmdlIChsaW1pdGVkIHRpbWUg
b2ZmZXIpLCB0aGV5IGluY2x1ZGUgeW91cg0KICAgICAgICBjb21wbGV0ZSBi
dXNpbmVzcyBpbmZvcm1hdGlvbiB3aXRoIGtleSB3b3JkIGNvbWJpbmF0aW9u
cyB0byBhY2NvbW1vZGF0ZQ0KICAgICAgICB0YXJnZXRlZCBidXNpbmVzcyBx
dWVyaWVzLiBFYWNoIGJ1c2luZXNzIGhhcyB0aGVpciBvd24gYWRtaW5pc3Ry
YXRpb24NCiAgICAgICAgcGFnZSB0byBjb250cm9sIHRoZWlyIG93biBwcmVz
ZW5jZSBvbiB0aGUgSW5kZXguPC9mb250PjwvYj48L3A+DQogICAgICAgIDxw
IGFsaWduPSJjZW50ZXIiPjxiPjxmb250IGNvbG9yPSIjRkZGRkZGIj5UaGlz
IGlzIGFuIEludGVybmF0aW9uYWwNCiAgICAgICAgQnVzaW5lc3MgSW5kZXgg
YW5kIGhhcyBiZWVuIGRldmVsb3BlZCB0byB3b3JrIGxpa2UgYSBtYWduZXQg
YnJpbmdpbmcNCiAgICAgICAgYnV5ZXJzICZhbXA7IHN1cHBsaWVycyB0b2dl
dGhlci4gQWRkaXRpb25hbCBhcmVhcyB3aWxsIHByb3ZpZGUgdml0YWwNCiAg
ICAgICAgaW5mb3JtYXRpb24gcmVnYXJkaW5nIG9yZGluYW5jZXMsIGxlZ2Fs
aXRpZXMsIHF1b3RhcywgdGF4YXRpb24sIHNoaXBwaW5nDQogICAgICAgIGlu
Zm8sIGVkdWNhdGlvbiBhbmQgb3RoZXIgYnVzaW5lc3MgaXNzdWVzLiBXZSB3
aWxsIGluY2x1ZGUgdHJhdmVsLA0KICAgICAgICB0b3VyaXNtIGFuZCBzcGVj
aWFsdHkgbG9kZ2luZyBhbmQgdG91ciBwYWNrYWdlcy48L2ZvbnQ+PC9iPjwv
cD4NCiAgICAgICAgPHAgYWxpZ249ImNlbnRlciI+PGZvbnQgY29sb3I9IiNG
RkNDMDAiPjx1PjxiPk91ciB0YXJnZXQgaXMgdGhlPC9iPjwvdT48L2ZvbnQ+
PGI+PGZvbnQgY29sb3I9IiNGRkNDMDAiPjx1Pg0KICAgICAgICBJbnRlcm5h
dGlvbmFsIEJ1c2luZXNzIENvbW11bml0eSE8L3U+PC9mb250Pjxmb250IGNv
bG9yPSIjRkZGRkZGIj48YnI+DQogICAgICAgIDxicj4NCiAgICAgICAgPGEg
aHJlZj0iaHR0cDovL3d3dy5lY29ub21pY2dyb3d0aG5ldHdvcmsuY29tL2Fk
dmVydGlzaW5nLmNmbSI+U3VibWl0IGENCiAgICAgICAgU2l0ZSE8L2E+PC9m
b250PjwvYj48L3A+DQogICAgICA8L3RkPg0KICAgIDwvdHI+DQogICAgPHRy
Pg0KICAgICAgPHRkPg0KICAgICAgICA8cCBhbGlnbj0iY2VudGVyIj48YnI+
DQogICAgICAgIDxmb250IGNvbG9yPSIjRkZGRkZGIj5QbGVhc2UgZ28gdG8g
PGEgaHJlZj0iaHR0cDovL3d3dy5HbG9iYWxUcmFkZUluZGV4LmNvbSI+d3d3
Lkdsb2JhbFRyYWRlSW5kZXguY29tPC9hPg0KICAgICAgICBvciA8YSBocmVm
PSJodHRwOi8vd3d3LkVjb25vbWljR3Jvd3RoTmV0d29yay5jb20iPnd3dy5F
Y29ub21pY0dyb3d0aE5ldHdvcmsuY29tPC9hPg0KICAgICAgICBhdCB5b3Vy
IGVhcmxpZXN0IGNvbnZlbmllbmNlIHRvIGxpc3QgeW91ciBidXNpbmVzcyBv
biB0aGlzIG5ldyBhbmQNCiAgICAgICAgZXhjaXRpbmcgbmV0d29yay4gPGI+
PHU+WW91IHdpbGwgYmUgZ2xhZCB5b3UgZGlkITwvdT48L2I+PC9mb250Pjxi
cj4NCiAgICAgICAgPC9wPg0KICAgICAgPC90ZD4NCiAgICA8L3RyPg0KICAg
IDx0cj4NCiAgICAgIDx0ZD4NCiAgICAgICAgPHAgYWxpZ249ImNlbnRlciI+
PGZvbnQgZmFjZT0iQXJpYWwiIHNpemU9IjEiIGNvbG9yPSIjRkZGRkZGIj48
YnI+DQogICAgICAgIFdlIGFyZSBzb3JyeSBpZiB3ZSBoYXZlIG9mZmVuZGVk
IHlvdSBieSBzZW5kaW5nIHRoaXMgaW52aXRhdGlvbiB0byB5b3UuJm5ic3A7
PGJyPg0KICAgICAgICBXZSBmb3VuZCB5b3VyIGVtYWlsIGFkZHJlc3Mgb24g
R29vZ2xlLCBBbHRhVmlzdGEsIGFsbHRoZXdlYiBvcg0KICAgICAgICBnb29n
bGUuY28udWsuPGJyPg0KICAgICAgICAmbmJzcDtJZiB5b3Ugd291bGQgbGlr
ZSB0byBiZSB0YWtlbiBvZmYgb3VyIG1haWxpbmcgbGlzdCwgUGxlYXNlPGJy
Pg0KICAgICAgICBzZW5kIHRvIDxhIGhyZWY9Im1haWx0bzpyZW1vdmVzQGds
b2JhbGFpZC5jb20/c3ViamVjdD1SZW1vdmUiPnJlbW92ZXNAZWNvbm9taWNn
cm93dGhuZXR3b3JrLmNvbT9zdWJqZWN0PVJlbW92ZTwvYT4uPGJyPg0KICAg
ICAgICA8YnI+DQogICAgICAgIFlvdSBtYXkgYWxzbyBjYWxsIHVzIGF0IDE4
NjYgNTE2DQogICAgICAgIDg0MTImbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgVVNBPC9mb250Pjxmb250IGZhY2U9IkFyaWFsIiBzaXpl
PSIxIiBjb2xvcj0iI0ZGMDBGRiI+PGJyPg0KICAgICAgICA8L2ZvbnQ+PC9w
Pg0KICAgICAgPC90ZD4NCiAgICA8L3RyPg0KICA8L3RhYmxlPg0KICA8L2Nl
bnRlcj4NCjwvZGl2Pg0KDQo8L2JvZHk+DQoNCjwvaHRtbD4NCg0KSW9mDQpS
cmlwdmhsbg==

------=_NextPart_2DB_3965_25339844.F594C273--



Return-Path: <johndrwn@GlobalTradeIndex.com>
Received: from GlobalTradeIndex.com (MG013223.user.veloxzone.com.br [200.165.13.223]) by nic.cafax.se (8.12.10.Beta0/8.12.10.Beta0) with SMTP id h865St6K010600; Sat, 6 Sep 2003 07:29:00 +0200 (MEST)
Message-ID: <070c01c3743e$0aeb8f30$f6457234@ksadg>
Reply-To: johndrwn@GlobalTradeIndex.com
From: johndrwn@GlobalTradeIndex.com
To: "Manager" <liman@cafax.se>
Cc: <ietf-provreg-logger@cafax.se>
Subject: Economic Development Network - Link        Kbersvowp
Date: Sat, 06 Sep 2003 12:13:51 +0600
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_892_7897_1B84F93D.C4D7BF66"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

This is a multi-part message in MIME format.

------=_NextPart_892_7897_1B84F93D.C4D7BF66
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


------=_NextPart_892_7897_1B84F93D.C4D7BF66
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64


PGh0bWw+DQoNCjxib2R5IHRleHQ9IiMwMEZGRkYiIGJnY29sb3I9IiMxNzE4
MDEiIGxpbms9IiNGRkZGMDAiIHZsaW5rPSIjMDBGRjAwIiBhbGluaz0iIzAw
MDBGRiI+DQoNCjxkaXYgYWxpZ249ImNlbnRlciI+DQogIDxjZW50ZXI+DQog
IDx0YWJsZSBib3JkZXI9IjMiIGNlbGxwYWRkaW5nPSIzIiBjZWxsc3BhY2lu
Zz0iMyIgd2lkdGg9IjQ1MCIgYm9yZGVyY29sb3I9IiNDMEMwQzAiIGJvcmRl
cmNvbG9ybGlnaHQ9IiM4MDAwMDAiIGJvcmRlcmNvbG9yZGFyaz0iI0ZGQ0Mw
MCI+DQogICAgPHRyPg0KICAgICAgPHRkPjxhIGhyZWY9Imh0dHA6Ly93d3cu
RWNvbm9taWNHcm93dGhOZXR3b3JrLmNvbSI+PGltZyBzcmM9Imh0dHA6Ly9l
Y29ub21pY2dyb3d0aG5ldHdvcmsuY29tL2VkZ2Vsb2dvLmpwZyIgYWxpZ249
ImxlZnQiIHZhbGlnbj0idG9wIiB3aWR0aD0iNDc0IiBoZWlnaHQ9IjEwMiI+
PC9hPjwvdGQ+DQogICAgPC90cj4NCiAgICA8dHI+DQogICAgICA8dGQ+DQog
ICAgICAgIDxwIGFsaWduPSJjZW50ZXIiPjxicj4NCiAgICAgICAgPHU+PGI+
PGZvbnQgY29sb3I9IiNGRkNDMDAiIHNpemU9IjQiPlRoZSBFY29ub21pYyBH
cm93dGggTmV0d29yazwvZm9udD48L2I+PC91PjwvcD4NCiAgICAgICAgPHAg
YWxpZ249ImNlbnRlciI+PGI+PGZvbnQgY29sb3I9IiNGRkZGRkYiPldlIHdv
dWxkIGxpa2UgdG8gaW52aXRlIHlvdXINCiAgICAgICAgY29tcGFueSBvciBv
cmdhbml6YXRpb24gdG8gbGlzdCB5b3VyIGJ1c2luZXNzIG9uIEdsb2JhbFRy
YWRlSW5kZXguY29tDQogICAgICAgIGFuZCBiZWNvbWUgYSBtZW1iZXIgb2Yg
dGhlIEVjb25vbWljIEdyb3d0aCBOZXR3b3JrLCZuYnNwOyBhIG5ldw0KICAg
ICAgICBtYXJrZXRpbmcmbmJzcDs8YnI+DQogICAgICAgIHN0cmF0ZWd5IGZv
ciBidXNpbmVzcywgV29ybGR3aWRlITxicj4NCiAgICAgICAgPGJyPg0KICAg
ICAgICBMaXN0aW5ncyBhcmUgYXQgbm8gY2hhcmdlIChsaW1pdGVkIHRpbWUg
b2ZmZXIpLCB0aGV5IGluY2x1ZGUgeW91cg0KICAgICAgICBjb21wbGV0ZSBi
dXNpbmVzcyBpbmZvcm1hdGlvbiB3aXRoIGtleSB3b3JkIGNvbWJpbmF0aW9u
cyB0byBhY2NvbW1vZGF0ZQ0KICAgICAgICB0YXJnZXRlZCBidXNpbmVzcyBx
dWVyaWVzLiBFYWNoIGJ1c2luZXNzIGhhcyB0aGVpciBvd24gYWRtaW5pc3Ry
YXRpb24NCiAgICAgICAgcGFnZSB0byBjb250cm9sIHRoZWlyIG93biBwcmVz
ZW5jZSBvbiB0aGUgSW5kZXguPC9mb250PjwvYj48L3A+DQogICAgICAgIDxw
IGFsaWduPSJjZW50ZXIiPjxiPjxmb250IGNvbG9yPSIjRkZGRkZGIj5UaGlz
IGlzIGFuIEludGVybmF0aW9uYWwNCiAgICAgICAgQnVzaW5lc3MgSW5kZXgg
YW5kIGhhcyBiZWVuIGRldmVsb3BlZCB0byB3b3JrIGxpa2UgYSBtYWduZXQg
YnJpbmdpbmcNCiAgICAgICAgYnV5ZXJzICZhbXA7IHN1cHBsaWVycyB0b2dl
dGhlci4gQWRkaXRpb25hbCBhcmVhcyB3aWxsIHByb3ZpZGUgdml0YWwNCiAg
ICAgICAgaW5mb3JtYXRpb24gcmVnYXJkaW5nIG9yZGluYW5jZXMsIGxlZ2Fs
aXRpZXMsIHF1b3RhcywgdGF4YXRpb24sIHNoaXBwaW5nDQogICAgICAgIGlu
Zm8sIGVkdWNhdGlvbiBhbmQgb3RoZXIgYnVzaW5lc3MgaXNzdWVzLiBXZSB3
aWxsIGluY2x1ZGUgdHJhdmVsLA0KICAgICAgICB0b3VyaXNtIGFuZCBzcGVj
aWFsdHkgbG9kZ2luZyBhbmQgdG91ciBwYWNrYWdlcy48L2ZvbnQ+PC9iPjwv
cD4NCiAgICAgICAgPHAgYWxpZ249ImNlbnRlciI+PGZvbnQgY29sb3I9IiNG
RkNDMDAiPjx1PjxiPk91ciB0YXJnZXQgaXMgdGhlPC9iPjwvdT48L2ZvbnQ+
PGI+PGZvbnQgY29sb3I9IiNGRkNDMDAiPjx1Pg0KICAgICAgICBJbnRlcm5h
dGlvbmFsIEJ1c2luZXNzIENvbW11bml0eSE8L3U+PC9mb250Pjxmb250IGNv
bG9yPSIjRkZGRkZGIj48YnI+DQogICAgICAgIDxicj4NCiAgICAgICAgPGEg
aHJlZj0iaHR0cDovL3d3dy5lY29ub21pY2dyb3d0aG5ldHdvcmsuY29tL2Fk
dmVydGlzaW5nLmNmbSI+U3VibWl0IGENCiAgICAgICAgU2l0ZSE8L2E+PC9m
b250PjwvYj48L3A+DQogICAgICA8L3RkPg0KICAgIDwvdHI+DQogICAgPHRy
Pg0KICAgICAgPHRkPg0KICAgICAgICA8cCBhbGlnbj0iY2VudGVyIj48YnI+
DQogICAgICAgIDxmb250IGNvbG9yPSIjRkZGRkZGIj5QbGVhc2UgZ28gdG8g
PGEgaHJlZj0iaHR0cDovL3d3dy5HbG9iYWxUcmFkZUluZGV4LmNvbSI+d3d3
Lkdsb2JhbFRyYWRlSW5kZXguY29tPC9hPg0KICAgICAgICBvciA8YSBocmVm
PSJodHRwOi8vd3d3LkVjb25vbWljR3Jvd3RoTmV0d29yay5jb20iPnd3dy5F
Y29ub21pY0dyb3d0aE5ldHdvcmsuY29tPC9hPg0KICAgICAgICBhdCB5b3Vy
IGVhcmxpZXN0IGNvbnZlbmllbmNlIHRvIGxpc3QgeW91ciBidXNpbmVzcyBv
biB0aGlzIG5ldyBhbmQNCiAgICAgICAgZXhjaXRpbmcgbmV0d29yay4gPGI+
PHU+WW91IHdpbGwgYmUgZ2xhZCB5b3UgZGlkITwvdT48L2I+PC9mb250Pjxi
cj4NCiAgICAgICAgPC9wPg0KICAgICAgPC90ZD4NCiAgICA8L3RyPg0KICAg
IDx0cj4NCiAgICAgIDx0ZD4NCiAgICAgICAgPHAgYWxpZ249ImNlbnRlciI+
PGZvbnQgZmFjZT0iQXJpYWwiIHNpemU9IjEiIGNvbG9yPSIjRkZGRkZGIj48
YnI+DQogICAgICAgIFdlIGFyZSBzb3JyeSBpZiB3ZSBoYXZlIG9mZmVuZGVk
IHlvdSBieSBzZW5kaW5nIHRoaXMgaW52aXRhdGlvbiB0byB5b3UuJm5ic3A7
PGJyPg0KICAgICAgICBXZSBmb3VuZCB5b3VyIGVtYWlsIGFkZHJlc3Mgb24g
R29vZ2xlLCBBbHRhVmlzdGEsIGFsbHRoZXdlYiBvcg0KICAgICAgICBnb29n
bGUuY28udWsuPGJyPg0KICAgICAgICAmbmJzcDtJZiB5b3Ugd291bGQgbGlr
ZSB0byBiZSB0YWtlbiBvZmYgb3VyIG1haWxpbmcgbGlzdCwgUGxlYXNlPGJy
Pg0KICAgICAgICBzZW5kIHRvIDxhIGhyZWY9Im1haWx0bzpyZW1vdmVzQGds
b2JhbGFpZC5jb20/c3ViamVjdD1SZW1vdmUiPnJlbW92ZXNAZWNvbm9taWNn
cm93dGhuZXR3b3JrLmNvbT9zdWJqZWN0PVJlbW92ZTwvYT4uPGJyPg0KICAg
ICAgICA8YnI+DQogICAgICAgIFlvdSBtYXkgYWxzbyBjYWxsIHVzIGF0IDE4
NjYgNTE2DQogICAgICAgIDg0MTImbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgVVNBPC9mb250Pjxmb250IGZhY2U9IkFyaWFsIiBzaXpl
PSIxIiBjb2xvcj0iI0ZGMDBGRiI+PGJyPg0KICAgICAgICA8L2ZvbnQ+PC9w
Pg0KICAgICAgPC90ZD4NCiAgICA8L3RyPg0KICA8L3RhYmxlPg0KICA8L2Nl
bnRlcj4NCjwvZGl2Pg0KDQo8L2JvZHk+DQoNCjwvaHRtbD4NCg0KVXhrDQpT
aGpwbnI=

------=_NextPart_892_7897_1B84F93D.C4D7BF66--


