From owner-ietf-provreg@cafax.se  Wed Apr  2 04:16:55 2008
Return-Path: <owner-ietf-provreg@cafax.se>
X-Original-To: ietfarch-provreg-archive@core3.amsl.com
Delivered-To: ietfarch-provreg-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 979EF3A6F2F
	for <ietfarch-provreg-archive@core3.amsl.com>; Wed,  2 Apr 2008 04:16:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CdFWuC4snMYr
	for <ietfarch-provreg-archive@core3.amsl.com>;
	Wed,  2 Apr 2008 04:16:54 -0700 (PDT)
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by core3.amsl.com (Postfix) with ESMTP id 524B63A6BDB
	for <provreg-archive@ietf.org>; Wed,  2 Apr 2008 04:15:08 -0700 (PDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m32B7KJX028222
	for <ietf-provreg-outgoing@nic.cafax.se>; Wed, 2 Apr 2008 13:07:20 +0200 (MEST)
Received: (from majordom@localhost)
	by nic.cafax.se (8.13.7/8.12.11/Submit) id m32B7Kaa011387
	for ietf-provreg-outgoing; Wed, 2 Apr 2008 13:07:20 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from app04.fccn.pt (app01.fccn.pt [193.137.198.36])
	by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m32B7JsI019252
	for <ietf-provreg@cafax.se>; Wed, 2 Apr 2008 13:07:19 +0200 (MEST)
Received: from mx.anubis.local (ste [10.1.2.2])
	by ste.anubis.internal (Postfix) with ESMTP id A39FE26EC8B;
	Wed,  2 Apr 2008 12:07:15 +0100 (WEST)
Received: from [10.0.20.1] (vpn-1.corp.fccn.pt [10.0.20.1])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx.anubis.local (Postfix) with ESMTP id 361A11BFD7A;
	Wed,  2 Apr 2008 12:07:15 +0100 (WEST)
Message-ID: <47F368E9.1040009@fccn.pt>
Date: Wed, 02 Apr 2008 12:07:21 +0100
From: Eugenio Pinto <eugenio.pinto@fccn.pt>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: ietf-provreg@cafax.se, "Hollenbeck, Scott" <shollenbeck@verisign.com>
Subject: [ietf-provreg] defining a reason code
References: <046F43A8D79C794FA4733814869CDF070231F785@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <046F43A8D79C794FA4733814869CDF070231F785@dul1wnexmb01.vcorp.ad.vrsn.com>
Content-Type: multipart/alternative;
 boundary="------------050101070201070507000409"
X-Warning-Anubis: User opted out of Anti-Virus checks
X-Warning-Anubis: User opted out of Anti-Spam checks
X-Content-Checker: AnubisNetworks MPS
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

This is a multi-part message in MIME format.
--------------050101070201070507000409
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I have another question regarding extending response codes.

I defined the following response message:

<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
  <response>
    <result code="2200">
      <msg>Authentication error</msg>
      <value>
        *<reason>5004</reason>*
      </value>
    </result>
    <trID>
      <clTRID>FCCN-12386</clTRID>
      <svTRID>TRN7063050306</svTRID>
    </trID>
  </response>
</epp>

where the reason element represents the code to a specific verified problem.

But I don't know if this is valid XML.

Can I define this this way, or I must include something with the 
namespace? like

    <result code="2200">
      <msg>Authentication error</msg>
      <value>
*        <ptdomain:panData 
xmlns:ptdomain="urn:ietf:params:xml:ns:ptdomain-1.0" 
xsi:schemaLocation="urn:ietf:params:xml:ns:ptdomain1.0 ptdomain-1.0.xsd">
      **    <ptdomain:reason>**5004**</ptdomain:reason>
**        <brdomain:panData>*
      </value>
    </result>

Thanks for your feedback.


--------------050101070201070507000409
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
I have another question regarding extending response codes.<br>
<br>
I defined the following response message:<br>
<br>
&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd"&gt;<br>
&nbsp; &lt;response&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;result code="2200"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;msg&gt;Authentication error&lt;/msg&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;value&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <b>&lt;reason&gt;5004&lt;/reason&gt;</b><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/value&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;/result&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;trID&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <br>
&nbsp;&nbsp;&nbsp; &lt;/trID&gt;<br>
&nbsp; &lt;/response&gt;<br>
&lt;/epp&gt;<br>
<br>
where the reason element represents the code to a specific verified
problem.<br>
<br>
But I don't know if this is valid XML.<br>
<br>
Can I define this this way, or I must include something with the
namespace? like<br>
<br>
&nbsp;&nbsp;&nbsp; &lt;result code="2200"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;msg&gt;Authentication error&lt;/msg&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;value&gt;<br>
<b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;ptdomain:panData
xmlns:ptdomain="urn:ietf:params:xml:ns:ptdomain-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:ptdomain1.0
ptdomain-1.0.xsd"&gt;
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</b><b>&nbsp;&nbsp;&nbsp; &lt;ptdomain:reason&gt;</b><b>5004</b><b>&lt;/ptdomain:reason&gt;<br>
</b><b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;brdomain:panData&gt;</b><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/value&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;/result&gt;<br>
<br>
Thanks for your feedback.<br>
<br>
</body>
</html>

--------------050101070201070507000409--


From owner-ietf-provreg@cafax.se  Wed Apr  2 04:21:08 2008
Return-Path: <owner-ietf-provreg@cafax.se>
X-Original-To: ietfarch-provreg-archive@core3.amsl.com
Delivered-To: ietfarch-provreg-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C59013A6A2E
	for <ietfarch-provreg-archive@core3.amsl.com>; Wed,  2 Apr 2008 04:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id s0AHvACSzGC8
	for <ietfarch-provreg-archive@core3.amsl.com>;
	Wed,  2 Apr 2008 04:21:07 -0700 (PDT)
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by core3.amsl.com (Postfix) with ESMTP id 177843A6A39
	for <provreg-archive@ietf.org>; Wed,  2 Apr 2008 04:21:06 -0700 (PDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m32BGVeL007853
	for <ietf-provreg-outgoing@nic.cafax.se>; Wed, 2 Apr 2008 13:16:31 +0200 (MEST)
Received: (from majordom@localhost)
	by nic.cafax.se (8.13.7/8.12.11/Submit) id m32BGVFA002606
	for ietf-provreg-outgoing; Wed, 2 Apr 2008 13:16:31 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from peregrine.verisign.com (peregrine.verisign.com [216.168.239.74])
	by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m32BGUeg014833
	for <ietf-provreg@cafax.se>; Wed, 2 Apr 2008 13:16:31 +0200 (MEST)
Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com [10.170.12.139])
	by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id m32B5J62007925;
	Wed, 2 Apr 2008 07:05:19 -0400
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Wed, 2 Apr 2008 07:16:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C894B2.FF0CEBFD"
Subject: [ietf-provreg] RE: defining a reason code
Date: Wed, 2 Apr 2008 07:16:35 -0400
Message-ID: <046F43A8D79C794FA4733814869CDF070231FBF5@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <47F368E9.1040009@fccn.pt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: defining a reason code
Thread-Index: AciUsbim7Mrt49xkSLKvJrCJpyk0+wAAJt9w
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Eugenio Pinto" <eugenio.pinto@fccn.pt>, <ietf-provreg@cafax.se>
X-OriginalArrivalTime: 02 Apr 2008 11:16:29.0059 (UTC) FILETIME=[FF6EA530:01C894B2]
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C894B2.FF0CEBFD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

From section 2.6 of RFC 4930:
=20
"Zero or more OPTIONAL <extValue> elements", and
=20
"A <reason> element containing a human-readable message that describes
the reason for the error.  The language of the response is identified
via an OPTIONAL "lang" attribute.  If not specified, the default
attribute value MUST be "en" (English)."
=20
No namespace needed, but you've got the <reason> element inside a
<value> element when it should be inside an <extValue> element.  You
should have some text in there, too.  Perhaps something like "5004:
Invalid password".

-Scott-=20

=20


________________________________

	From: Eugenio Pinto [mailto:eugenio.pinto@fccn.pt]=20
	Sent: Wednesday, April 02, 2008 7:07 AM
	To: ietf-provreg@cafax.se; Hollenbeck, Scott
	Subject: defining a reason code
=09
=09
	Hi,
=09
	I have another question regarding extending response codes.
=09
	I defined the following response message:
=09
	<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
<http://www.w3.org/2001/XMLSchema-instance>
xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
	  <response>
	    <result code=3D"2200">
	      <msg>Authentication error</msg>
	      <value>
	        <reason>5004</reason>
	      </value>
	    </result>
	    <trID>
	      <clTRID>FCCN-12386</clTRID>=20
	      <svTRID>TRN7063050306</svTRID>=20
	    </trID>
	  </response>
	</epp>
=09
	where the reason element represents the code to a specific
verified problem.
=09
	But I don't know if this is valid XML.
=09
	Can I define this this way, or I must include something with the
namespace? like
=09
	    <result code=3D"2200">
	      <msg>Authentication error</msg>
	      <value>
	        <ptdomain:panData
xmlns:ptdomain=3D"urn:ietf:params:xml:ns:ptdomain-1.0"
xsi:schemaLocation=3D"urn:ietf:params:xml:ns:ptdomain1.0
ptdomain-1.0.xsd">=20
	          <ptdomain:reason>5004</ptdomain:reason>
	        <brdomain:panData>
	      </value>
	    </result>
=09
	Thanks for your feedback.
=09
=09


------_=_NextPart_001_01C894B2.FF0CEBFD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>From section 2.6 of RFC =
4930:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>"Zero or more OPTIONAL &lt;extValue&gt; =
elements",=20
and</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>"A &lt;reason&gt; element containing a =
human-readable=20
message that describes the reason for the error.&nbsp; The language of =
the=20
response is identified via an OPTIONAL "lang" attribute.&nbsp; If not =
specified,=20
the default attribute value MUST be "en" (English)."</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>No namespace needed, but you've got the =
&lt;reason&gt;=20
element inside a &lt;value&gt; element when it should be inside an=20
&lt;extValue&gt; element.&nbsp; You should have some text in there, =
too.&nbsp;=20
Perhaps something like "5004: Invalid password".</FONT></SPAN></DIV><!-- =
Converted from text/plain format -->
<P><FONT size=3D2>-Scott-</FONT> </P>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Eugenio Pinto=20
  [mailto:eugenio.pinto@fccn.pt] <BR><B>Sent:</B> Wednesday, April 02, =
2008 7:07=20
  AM<BR><B>To:</B> ietf-provreg@cafax.se; Hollenbeck, =
Scott<BR><B>Subject:</B>=20
  defining a reason code<BR></FONT><BR></DIV>
  <DIV></DIV>Hi,<BR><BR>I have another question regarding extending =
response=20
  codes.<BR><BR>I defined the following response message:<BR><BR>&lt;epp =

  xmlns=3D"urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=3D<A=20
  class=3Dmoz-txt-link-rfc2396E=20
  =
href=3D"http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/200=
1/XMLSchema-instance"</A>=20
  xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0 =
epp-1.0.xsd"&gt;<BR>&nbsp;=20
  &lt;response&gt;<BR>&nbsp;&nbsp;&nbsp; &lt;result=20
  code=3D"2200"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;msg&gt;Authentication=20
  error&lt;/msg&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;value&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
<B>&lt;reason&gt;5004&lt;/reason&gt;</B><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
  &lt;/value&gt;<BR>&nbsp;&nbsp;&nbsp; =
&lt;/result&gt;<BR>&nbsp;&nbsp;&nbsp;=20
  &lt;trID&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <BR>&nbsp;&nbsp;&nbsp;=20
  &lt;/trID&gt;<BR>&nbsp; &lt;/response&gt;<BR>&lt;/epp&gt;<BR><BR>where =
the=20
  reason element represents the code to a specific verified =
problem.<BR><BR>But=20
  I don't know if this is valid XML.<BR><BR>Can I define this this way, =
or I=20
  must include something with the namespace? =
like<BR><BR>&nbsp;&nbsp;&nbsp;=20
  &lt;result code=3D"2200"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;msg&gt;Authentication =
error&lt;/msg&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;value&gt;<BR><B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;ptdomain:panData =
xmlns:ptdomain=3D"urn:ietf:params:xml:ns:ptdomain-1.0"=20
  xsi:schemaLocation=3D"urn:ietf:params:xml:ns:ptdomain1.0 =
ptdomain-1.0.xsd"&gt;=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</B><B>&nbsp;&nbsp;&nbsp;=20
  =
&lt;ptdomain:reason&gt;</B><B>5004</B><B>&lt;/ptdomain:reason&gt;<BR></B>=
<B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;brdomain:panData&gt;</B><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;/value&gt;<BR>&nbsp;&nbsp;&nbsp; &lt;/result&gt;<BR><BR>Thanks for =
your=20
  feedback.<BR><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C894B2.FF0CEBFD--


From owner-ietf-provreg@cafax.se  Wed Apr  2 20:43:50 2008
Return-Path: <owner-ietf-provreg@cafax.se>
X-Original-To: ietfarch-provreg-archive@core3.amsl.com
Delivered-To: ietfarch-provreg-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE79C3A6802
	for <ietfarch-provreg-archive@core3.amsl.com>; Wed,  2 Apr 2008 20:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vPb8VLdVYDV2
	for <ietfarch-provreg-archive@core3.amsl.com>;
	Wed,  2 Apr 2008 20:43:49 -0700 (PDT)
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by core3.amsl.com (Postfix) with ESMTP id 685393A6768
	for <provreg-archive@ietf.org>; Wed,  2 Apr 2008 20:43:48 -0700 (PDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m333YqbK012726
	for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 3 Apr 2008 05:34:52 +0200 (MEST)
Received: (from majordom@localhost)
	by nic.cafax.se (8.13.7/8.12.11/Submit) id m333YqgB021863
	for ietf-provreg-outgoing; Thu, 3 Apr 2008 05:34:52 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from app03.fccn.pt (app02.fccn.pt [193.137.198.37])
	by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m333YpDt017516
	for <ietf-provreg@cafax.se>; Thu, 3 Apr 2008 05:34:51 +0200 (MEST)
Received: from mx.anubis.local (ste [10.1.2.2])
	by ste.anubis.internal (Postfix) with ESMTP id B149A19FC6D;
	Thu,  3 Apr 2008 04:34:50 +0100 (WEST)
Received: from [10.0.20.1] (vpn-1.corp.fccn.pt [10.0.20.1])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx.anubis.local (Postfix) with ESMTP id 57E1B1B4455;
	Thu,  3 Apr 2008 04:34:49 +0100 (WEST)
Message-ID: <47F45048.3080305@fccn.pt>
Date: Thu, 03 Apr 2008 04:34:32 +0100
From: Eugenio Pinto <eugenio.pinto@fccn.pt>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
CC: ietf-provreg@cafax.se
Subject: [ietf-provreg] Re: defining a reason code
References: <046F43A8D79C794FA4733814869CDF070231FBF5@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <046F43A8D79C794FA4733814869CDF070231FBF5@dul1wnexmb01.vcorp.ad.vrsn.com>
Content-Type: multipart/alternative;
 boundary="------------080701020904090507070802"
X-Warning-Anubis: User opted out of Anti-Virus checks
X-Warning-Anubis: User opted out of Anti-Spam checks
X-Content-Checker: AnubisNetworks MPS
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

This is a multi-part message in MIME format.
--------------080701020904090507070802
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Ok.

The value and reason are required elements to the extValue type, aren't 
they?

So, I need always to have the value element even if I don't need it, right?

something like

<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
  <response>
    <result code="2200">
      <msg>Authentication error</msg>
*      <extValue>
        <value/>
        **<reason>5004: you must do the login first</reason>
      </extValue>*
    </result>
    <trID>
      <clTRID>FCCN-12386</clTRID>
      <svTRID>TRN7063050306</svTRID>
    </trID>
  </response>
</epp>

Best Regards,
Eugenio


Hollenbeck, Scott wrote:
> From section 2.6 of RFC 4930:
>  
> "Zero or more OPTIONAL <extValue> elements", and
>  
> "A <reason> element containing a human-readable message that describes 
> the reason for the error.  The language of the response is identified 
> via an OPTIONAL "lang" attribute.  If not specified, the default 
> attribute value MUST be "en" (English)."
>  
> No namespace needed, but you've got the <reason> element inside a 
> <value> element when it should be inside an <extValue> element.  You 
> should have some text in there, too.  Perhaps something like "5004: 
> Invalid password".
>
> -Scott-
>
>  
>
>     ------------------------------------------------------------------------
>     *From:* Eugenio Pinto [mailto:eugenio.pinto@fccn.pt]
>     *Sent:* Wednesday, April 02, 2008 7:07 AM
>     *To:* ietf-provreg@cafax.se; Hollenbeck, Scott
>     *Subject:* defining a reason code
>
>     Hi,
>
>     I have another question regarding extending response codes.
>
>     I defined the following response message:
>
>     <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>     xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
>       <response>
>         <result code="2200">
>           <msg>Authentication error</msg>
>           <value>
>             *<reason>5004</reason>*
>           </value>
>         </result>
>         <trID>
>           <clTRID>FCCN-12386</clTRID>
>           <svTRID>TRN7063050306</svTRID>
>         </trID>
>       </response>
>     </epp>
>
>     where the reason element represents the code to a specific
>     verified problem.
>
>     But I don't know if this is valid XML.
>
>     Can I define this this way, or I must include something with the
>     namespace? like
>
>         <result code="2200">
>           <msg>Authentication error</msg>
>           <value>
>     *        <ptdomain:panData
>     xmlns:ptdomain="urn:ietf:params:xml:ns:ptdomain-1.0"
>     xsi:schemaLocation="urn:ietf:params:xml:ns:ptdomain1.0
>     ptdomain-1.0.xsd">
>           **    <ptdomain:reason>**5004**</ptdomain:reason>
>     **        <brdomain:panData>*
>           </value>
>         </result>
>
>     Thanks for your feedback.
>

--------------080701020904090507070802
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Ok.<br>
<br>
The value and reason are required elements to the extValue type, aren't
they?<br>
<br>
So, I need always to have the value element even if I don't need it,
right?<br>
<br>
something like<br>
<br>
&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=<a
 class="moz-txt-link-rfc2396E"
 href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd"&gt;<br>
&nbsp; &lt;response&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;result code="2200"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;msg&gt;Authentication error&lt;/msg&gt;<br>
<b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;extValue&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;value/&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </b><b>&lt;reason&gt;5004: you must do the login
first&lt;/reason&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/extValue&gt;</b><br>
&nbsp;&nbsp;&nbsp; &lt;/result&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;trID&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <br>
&nbsp;&nbsp;&nbsp; &lt;/trID&gt;<br>
&nbsp; &lt;/response&gt;<br>
&lt;/epp&gt;<br>
<br>
Best Regards,<br>
Eugenio<br>
<br>
<br>
Hollenbeck, Scott wrote:
<blockquote
 cite="mid:046F43A8D79C794FA4733814869CDF070231FBF5@dul1wnexmb01.vcorp.ad.vrsn.com"
 type="cite">
  <title></title>
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta content="MSHTML 6.00.2900.3243" name="GENERATOR">
  <div dir="ltr" align="left"><span class="706411111-02042008"><font
 color="#0000ff" face="Arial" size="2">From section 2.6 of RFC 4930:</font></span></div>
  <div dir="ltr" align="left"><span class="706411111-02042008"></span>&nbsp;</div>
  <div dir="ltr" align="left"><span class="706411111-02042008"><font
 color="#0000ff" face="Arial" size="2">"Zero or more OPTIONAL
&lt;extValue&gt; elements", and</font></span></div>
  <div dir="ltr" align="left"><span class="706411111-02042008"></span>&nbsp;</div>
  <div dir="ltr" align="left"><span class="706411111-02042008"><font
 color="#0000ff" face="Arial" size="2">"A &lt;reason&gt; element
containing a human-readable message that describes the reason for the
error.&nbsp; The language of the response is identified via an OPTIONAL
"lang" attribute.&nbsp; If not specified, the default attribute value MUST
be "en" (English)."</font></span></div>
  <div dir="ltr" align="left"><span class="706411111-02042008"></span>&nbsp;</div>
  <div dir="ltr" align="left"><span class="706411111-02042008"><font
 color="#0000ff" face="Arial" size="2">No namespace needed, but you've
got the &lt;reason&gt; element inside a &lt;value&gt; element when it
should be inside an &lt;extValue&gt; element.&nbsp; You should have some
text in there, too.&nbsp; Perhaps something like "5004: Invalid password".</font></span></div>
<!-- Converted from text/plain format -->
  <p><font size="2">-Scott-</font> </p>
  <div>&nbsp;</div>
  <br>
  <blockquote
 style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
    <div class="OutlookMessageHeader" dir="ltr" align="left"
 lang="en-us">
    <hr tabindex="-1"> <font face="Tahoma" size="2"><b>From:</b>
Eugenio Pinto [<a class="moz-txt-link-freetext" href="mailto:eugenio.pinto@fccn.pt">mailto:eugenio.pinto@fccn.pt</a>] <br>
    <b>Sent:</b> Wednesday, April 02, 2008 7:07 AM<br>
    <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:ietf-provreg@cafax.se">ietf-provreg@cafax.se</a>; Hollenbeck, Scott<br>
    <b>Subject:</b> defining a reason code<br>
    </font><br>
    </div>
Hi,<br>
    <br>
I have another question regarding extending response codes.<br>
    <br>
I defined the following response message:<br>
    <br>
&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=<a
 moz-do-not-send="true" class="moz-txt-link-rfc2396E"
 href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd"&gt;<br>
&nbsp; &lt;response&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;result code="2200"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;msg&gt;Authentication error&lt;/msg&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;value&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <b>&lt;reason&gt;5004&lt;/reason&gt;</b><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/value&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;/result&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;trID&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <br>
&nbsp;&nbsp;&nbsp; &lt;/trID&gt;<br>
&nbsp; &lt;/response&gt;<br>
&lt;/epp&gt;<br>
    <br>
where the reason element represents the code to a specific verified
problem.<br>
    <br>
But I don't know if this is valid XML.<br>
    <br>
Can I define this this way, or I must include something with the
namespace? like<br>
    <br>
&nbsp;&nbsp;&nbsp; &lt;result code="2200"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;msg&gt;Authentication error&lt;/msg&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;value&gt;<br>
    <b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;ptdomain:panData
xmlns:ptdomain="urn:ietf:params:xml:ns:ptdomain-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:ptdomain1.0
ptdomain-1.0.xsd"&gt; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</b><b>&nbsp;&nbsp;&nbsp; &lt;ptdomain:reason&gt;</b><b>5004</b><b>&lt;/ptdomain:reason&gt;<br>
    </b><b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;brdomain:panData&gt;</b><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/value&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;/result&gt;<br>
    <br>
Thanks for your feedback.<br>
    <br>
  </blockquote>
</blockquote>
</body>
</html>

--------------080701020904090507070802--


From owner-ietf-provreg@cafax.se  Thu Apr  3 04:24:04 2008
Return-Path: <owner-ietf-provreg@cafax.se>
X-Original-To: ietfarch-provreg-archive@core3.amsl.com
Delivered-To: ietfarch-provreg-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D040528C620
	for <ietfarch-provreg-archive@core3.amsl.com>; Thu,  3 Apr 2008 04:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mp9Nn+Vtc5-c
	for <ietfarch-provreg-archive@core3.amsl.com>;
	Thu,  3 Apr 2008 04:24:03 -0700 (PDT)
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
	by core3.amsl.com (Postfix) with ESMTP id 3E5443A6968
	for <provreg-archive@ietf.org>; Thu,  3 Apr 2008 04:24:03 -0700 (PDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
	by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m33BGSxb006047
	for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 3 Apr 2008 13:16:28 +0200 (MEST)
Received: (from majordom@localhost)
	by nic.cafax.se (8.13.7/8.12.11/Submit) id m33BGSi6013100
	for ietf-provreg-outgoing; Thu, 3 Apr 2008 13:16:28 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from peregrine.verisign.com (peregrine.verisign.com [216.168.239.74])
	by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m33BGQX7020463
	for <ietf-provreg@cafax.se>; Thu, 3 Apr 2008 13:16:27 +0200 (MEST)
Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138])
	by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id m33B5E7Z031310;
	Thu, 3 Apr 2008 07:05:14 -0400
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Thu, 3 Apr 2008 07:16:25 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8957C.279929D6"
Subject: [ietf-provreg] RE: defining a reason code
Date: Thu, 3 Apr 2008 07:16:24 -0400
Message-ID: <046F43A8D79C794FA4733814869CDF070231FD08@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <47F45048.3080305@fccn.pt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: defining a reason code
Thread-Index: AciVO7L1DjSm2CGkQny2GEENQ3y9/AAP09hA
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Eugenio Pinto" <eugenio.pinto@fccn.pt>
Cc: <ietf-provreg@cafax.se>
X-OriginalArrivalTime: 03 Apr 2008 11:16:25.0708 (UTC) FILETIME=[27D912C0:01C8957C]
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8957C.279929D6
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Correct, if you use <extValue> you need both <value> and <reason>.  The
<value> should be the slice of XML that's causing the error.
=20
Looking at the example below, though, I don't quite see what you're
trying to do.  A 2201 error code would be more appropriate for someone
trying to execute a command before doing a <login>.  You could then use
a <value> (containing the XML command that failed, for example) after
the <msg> without using <extValue> at all.
=20

-Scott-=20

=20


________________________________

	From: Eugenio Pinto [mailto:eugenio.pinto@fccn.pt]=20
	Sent: Wednesday, April 02, 2008 11:35 PM
	To: Hollenbeck, Scott
	Cc: ietf-provreg@cafax.se
	Subject: Re: defining a reason code
=09
=09
	Ok.
=09
	The value and reason are required elements to the extValue type,
aren't they?
=09
	So, I need always to have the value element even if I don't need
it, right?
=09
	something like
=09
	<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
<http://www.w3.org/2001/XMLSchema-instance>
xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
	  <response>
	    <result code=3D"2200">
	      <msg>Authentication error</msg>
	      <extValue>
	        <value/>
	        <reason>5004: you must do the login first</reason>
	      </extValue>
	    </result>
	    <trID>
	      <clTRID>FCCN-12386</clTRID>=20
	      <svTRID>TRN7063050306</svTRID>=20
	    </trID>
	  </response>
	</epp>
=09
	Best Regards,
	Eugenio
=09
=09
	Hollenbeck, Scott wrote:=20

		From section 2.6 of RFC 4930:
		=20
		"Zero or more OPTIONAL <extValue> elements", and
		=20
		"A <reason> element containing a human-readable message
that describes the reason for the error.  The language of the response
is identified via an OPTIONAL "lang" attribute.  If not specified, the
default attribute value MUST be "en" (English)."
		=20
		No namespace needed, but you've got the <reason> element
inside a <value> element when it should be inside an <extValue> element.
You should have some text in there, too.  Perhaps something like "5004:
Invalid password".

		-Scott-=20

		=20


________________________________

			From: Eugenio Pinto
[mailto:eugenio.pinto@fccn.pt]=20
			Sent: Wednesday, April 02, 2008 7:07 AM
			To: ietf-provreg@cafax.se; Hollenbeck, Scott
			Subject: defining a reason code
		=09
		=09
			Hi,
		=09
			I have another question regarding extending
response codes.
		=09
			I defined the following response message:
		=09
			<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
<http://www.w3.org/2001/XMLSchema-instance>
xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
			  <response>
			    <result code=3D"2200">
			      <msg>Authentication error</msg>
			      <value>
			        <reason>5004</reason>
			      </value>
			    </result>
			    <trID>
			      <clTRID>FCCN-12386</clTRID>=20
			      <svTRID>TRN7063050306</svTRID>=20
			    </trID>
			  </response>
			</epp>
		=09
			where the reason element represents the code to
a specific verified problem.
		=09
			But I don't know if this is valid XML.
		=09
			Can I define this this way, or I must include
something with the namespace? like
		=09
			    <result code=3D"2200">
			      <msg>Authentication error</msg>
			      <value>
			        <ptdomain:panData
xmlns:ptdomain=3D"urn:ietf:params:xml:ns:ptdomain-1.0"
xsi:schemaLocation=3D"urn:ietf:params:xml:ns:ptdomain1.0
ptdomain-1.0.xsd">=20
=09
<ptdomain:reason>5004</ptdomain:reason>
			        <brdomain:panData>
			      </value>
			    </result>
		=09
			Thanks for your feedback.
		=09
		=09


------_=_NextPart_001_01C8957C.279929D6
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D310130811-03042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Correct, if you use &lt;extValue&gt; you need =
both=20
&lt;value&gt; and &lt;reason&gt;.&nbsp; The &lt;value&gt; should be the =
slice of=20
XML that's causing the error.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D310130811-03042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D310130811-03042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Looking at the example below, though, I don't =
quite see=20
what you're trying to do.&nbsp; A 2201 error code would be more =
appropriate for=20
someone trying to execute a command before doing a &lt;login&gt;.&nbsp; =
You=20
could then use a &lt;value&gt; (containing the XML command that failed, =
for=20
example) after the &lt;msg&gt; without using &lt;extValue&gt; at=20
all.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV><!-- =
Converted from text/plain format -->
<P><FONT size=3D2>-Scott-</FONT> </P>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Eugenio Pinto=20
  [mailto:eugenio.pinto@fccn.pt] <BR><B>Sent:</B> Wednesday, April 02, =
2008=20
  11:35 PM<BR><B>To:</B> Hollenbeck, Scott<BR><B>Cc:</B>=20
  ietf-provreg@cafax.se<BR><B>Subject:</B> Re: defining a reason=20
  code<BR></FONT><BR></DIV>
  <DIV></DIV>Ok.<BR><BR>The value and reason are required elements to =
the=20
  extValue type, aren't they?<BR><BR>So, I need always to have the value =
element=20
  even if I don't need it, right?<BR><BR>something like<BR><BR>&lt;epp=20
  xmlns=3D"urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=3D<A=20
  class=3Dmoz-txt-link-rfc2396E=20
  =
href=3D"http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/200=
1/XMLSchema-instance"</A>=20
  xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0 =
epp-1.0.xsd"&gt;<BR>&nbsp;=20
  &lt;response&gt;<BR>&nbsp;&nbsp;&nbsp; &lt;result=20
  code=3D"2200"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;msg&gt;Authentication=20
  error&lt;/msg&gt;<BR><B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;extValue&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;value/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </B><B>&lt;reason&gt;5004: you must do the login=20
  first&lt;/reason&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;/extValue&gt;</B><BR>&nbsp;&nbsp;&nbsp;=20
  &lt;/result&gt;<BR>&nbsp;&nbsp;&nbsp;=20
  &lt;trID&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <BR>&nbsp;&nbsp;&nbsp;=20
  &lt;/trID&gt;<BR>&nbsp; &lt;/response&gt;<BR>&lt;/epp&gt;<BR><BR>Best=20
  Regards,<BR>Eugenio<BR><BR><BR>Hollenbeck, Scott wrote:=20
  <BLOCKQUOTE=20
  =
cite=3Dmid:046F43A8D79C794FA4733814869CDF070231FBF5@dul1wnexmb01.vcorp.ad=
.vrsn.com=20
  type=3D"cite">
    <META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>From section 2.6 of RFC =
4930:</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D706411111-02042008></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>"Zero or more OPTIONAL &lt;extValue&gt; =
elements",=20
    and</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D706411111-02042008></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>"A &lt;reason&gt; element containing a =
human-readable=20
    message that describes the reason for the error.&nbsp; The language =
of the=20
    response is identified via an OPTIONAL "lang" attribute.&nbsp; If =
not=20
    specified, the default attribute value MUST be "en"=20
    (English)."</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D706411111-02042008></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>No namespace needed, but you've got the =
&lt;reason&gt;=20
    element inside a &lt;value&gt; element when it should be inside an=20
    &lt;extValue&gt; element.&nbsp; You should have some text in there,=20
    too.&nbsp; Perhaps something like "5004: Invalid=20
    password".</FONT></SPAN></DIV><!-- Converted from text/plain format =
-->
    <P><FONT size=3D2>-Scott-</FONT> </P>
    <DIV>&nbsp;</DIV><BR>
    <BLOCKQUOTE=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
rgb(0,0,255) 2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Eugenio Pinto [<A=20
      class=3Dmoz-txt-link-freetext=20
      =
href=3D"mailto:eugenio.pinto@fccn.pt">mailto:eugenio.pinto@fccn.pt</A>]=20
      <BR><B>Sent:</B> Wednesday, April 02, 2008 7:07 AM<BR><B>To:</B> =
<A=20
      class=3Dmoz-txt-link-abbreviated=20
      href=3D"mailto:ietf-provreg@cafax.se">ietf-provreg@cafax.se</A>; =
Hollenbeck,=20
      Scott<BR><B>Subject:</B> defining a reason=20
      code<BR></FONT><BR></DIV>Hi,<BR><BR>I have another question =
regarding=20
      extending response codes.<BR><BR>I defined the following response=20
      message:<BR><BR>&lt;epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"=20
      xmlns:xsi=3D<A class=3Dmoz-txt-link-rfc2396E=20
      href=3D"http://www.w3.org/2001/XMLSchema-instance"=20
      =
moz-do-not-send=3D"true">"http://www.w3.org/2001/XMLSchema-instance"</A> =

      xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0=20
      epp-1.0.xsd"&gt;<BR>&nbsp; &lt;response&gt;<BR>&nbsp;&nbsp;&nbsp;=20
      &lt;result code=3D"2200"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;msg&gt;Authentication=20
      error&lt;/msg&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;value&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
<B>&lt;reason&gt;5004&lt;/reason&gt;</B><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
      &lt;/value&gt;<BR>&nbsp;&nbsp;&nbsp; =
&lt;/result&gt;<BR>&nbsp;&nbsp;&nbsp;=20
      &lt;trID&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <BR>&nbsp;&nbsp;&nbsp;=20
      &lt;/trID&gt;<BR>&nbsp; =
&lt;/response&gt;<BR>&lt;/epp&gt;<BR><BR>where the=20
      reason element represents the code to a specific verified=20
      problem.<BR><BR>But I don't know if this is valid XML.<BR><BR>Can =
I define=20
      this this way, or I must include something with the namespace?=20
      like<BR><BR>&nbsp;&nbsp;&nbsp; &lt;result=20
      code=3D"2200"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;msg&gt;Authentication=20
      error&lt;/msg&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;value&gt;<BR><B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;ptdomain:panData =
xmlns:ptdomain=3D"urn:ietf:params:xml:ns:ptdomain-1.0"=20
      xsi:schemaLocation=3D"urn:ietf:params:xml:ns:ptdomain1.0=20
      ptdomain-1.0.xsd"&gt;=20
      <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</B><B>&nbsp;&nbsp;&nbsp;=20
      =
&lt;ptdomain:reason&gt;</B><B>5004</B><B>&lt;/ptdomain:reason&gt;<BR></B>=
<B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;brdomain:panData&gt;</B><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;/value&gt;<BR>&nbsp;&nbsp;&nbsp; &lt;/result&gt;<BR><BR>Thanks =
for=20
      your =
feedback.<BR><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8957C.279929D6--



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m33BGSxb006047 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 3 Apr 2008 13:16:28 +0200 (MEST)
Received: (from majordom@localhost) by nic.cafax.se (8.13.7/8.12.11/Submit) id m33BGSi6013100 for ietf-provreg-outgoing; Thu, 3 Apr 2008 13:16:28 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from peregrine.verisign.com (peregrine.verisign.com [216.168.239.74]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m33BGQX7020463 for <ietf-provreg@cafax.se>; Thu, 3 Apr 2008 13:16:27 +0200 (MEST)
Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id m33B5E7Z031310; Thu, 3 Apr 2008 07:05:14 -0400
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 3 Apr 2008 07:16:25 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8957C.279929D6"
Subject: [ietf-provreg] RE: defining a reason code
Date: Thu, 3 Apr 2008 07:16:24 -0400
Message-ID: <046F43A8D79C794FA4733814869CDF070231FD08@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <47F45048.3080305@fccn.pt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: defining a reason code
Thread-Index: AciVO7L1DjSm2CGkQny2GEENQ3y9/AAP09hA
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Eugenio Pinto" <eugenio.pinto@fccn.pt>
Cc: <ietf-provreg@cafax.se>
X-OriginalArrivalTime: 03 Apr 2008 11:16:25.0708 (UTC) FILETIME=[27D912C0:01C8957C]
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8957C.279929D6
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Correct, if you use <extValue> you need both <value> and <reason>.  The
<value> should be the slice of XML that's causing the error.
=20
Looking at the example below, though, I don't quite see what you're
trying to do.  A 2201 error code would be more appropriate for someone
trying to execute a command before doing a <login>.  You could then use
a <value> (containing the XML command that failed, for example) after
the <msg> without using <extValue> at all.
=20

-Scott-=20

=20


________________________________

	From: Eugenio Pinto [mailto:eugenio.pinto@fccn.pt]=20
	Sent: Wednesday, April 02, 2008 11:35 PM
	To: Hollenbeck, Scott
	Cc: ietf-provreg@cafax.se
	Subject: Re: defining a reason code
=09
=09
	Ok.
=09
	The value and reason are required elements to the extValue type,
aren't they?
=09
	So, I need always to have the value element even if I don't need
it, right?
=09
	something like
=09
	<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
<http://www.w3.org/2001/XMLSchema-instance>
xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
	  <response>
	    <result code=3D"2200">
	      <msg>Authentication error</msg>
	      <extValue>
	        <value/>
	        <reason>5004: you must do the login first</reason>
	      </extValue>
	    </result>
	    <trID>
	      <clTRID>FCCN-12386</clTRID>=20
	      <svTRID>TRN7063050306</svTRID>=20
	    </trID>
	  </response>
	</epp>
=09
	Best Regards,
	Eugenio
=09
=09
	Hollenbeck, Scott wrote:=20

		From section 2.6 of RFC 4930:
		=20
		"Zero or more OPTIONAL <extValue> elements", and
		=20
		"A <reason> element containing a human-readable message
that describes the reason for the error.  The language of the response
is identified via an OPTIONAL "lang" attribute.  If not specified, the
default attribute value MUST be "en" (English)."
		=20
		No namespace needed, but you've got the <reason> element
inside a <value> element when it should be inside an <extValue> element.
You should have some text in there, too.  Perhaps something like "5004:
Invalid password".

		-Scott-=20

		=20


________________________________

			From: Eugenio Pinto
[mailto:eugenio.pinto@fccn.pt]=20
			Sent: Wednesday, April 02, 2008 7:07 AM
			To: ietf-provreg@cafax.se; Hollenbeck, Scott
			Subject: defining a reason code
		=09
		=09
			Hi,
		=09
			I have another question regarding extending
response codes.
		=09
			I defined the following response message:
		=09
			<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
<http://www.w3.org/2001/XMLSchema-instance>
xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
			  <response>
			    <result code=3D"2200">
			      <msg>Authentication error</msg>
			      <value>
			        <reason>5004</reason>
			      </value>
			    </result>
			    <trID>
			      <clTRID>FCCN-12386</clTRID>=20
			      <svTRID>TRN7063050306</svTRID>=20
			    </trID>
			  </response>
			</epp>
		=09
			where the reason element represents the code to
a specific verified problem.
		=09
			But I don't know if this is valid XML.
		=09
			Can I define this this way, or I must include
something with the namespace? like
		=09
			    <result code=3D"2200">
			      <msg>Authentication error</msg>
			      <value>
			        <ptdomain:panData
xmlns:ptdomain=3D"urn:ietf:params:xml:ns:ptdomain-1.0"
xsi:schemaLocation=3D"urn:ietf:params:xml:ns:ptdomain1.0
ptdomain-1.0.xsd">=20
=09
<ptdomain:reason>5004</ptdomain:reason>
			        <brdomain:panData>
			      </value>
			    </result>
		=09
			Thanks for your feedback.
		=09
		=09


------_=_NextPart_001_01C8957C.279929D6
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D310130811-03042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Correct, if you use &lt;extValue&gt; you need =
both=20
&lt;value&gt; and &lt;reason&gt;.&nbsp; The &lt;value&gt; should be the =
slice of=20
XML that's causing the error.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D310130811-03042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D310130811-03042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Looking at the example below, though, I don't =
quite see=20
what you're trying to do.&nbsp; A 2201 error code would be more =
appropriate for=20
someone trying to execute a command before doing a &lt;login&gt;.&nbsp; =
You=20
could then use a &lt;value&gt; (containing the XML command that failed, =
for=20
example) after the &lt;msg&gt; without using &lt;extValue&gt; at=20
all.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV><!-- =
Converted from text/plain format -->
<P><FONT size=3D2>-Scott-</FONT> </P>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Eugenio Pinto=20
  [mailto:eugenio.pinto@fccn.pt] <BR><B>Sent:</B> Wednesday, April 02, =
2008=20
  11:35 PM<BR><B>To:</B> Hollenbeck, Scott<BR><B>Cc:</B>=20
  ietf-provreg@cafax.se<BR><B>Subject:</B> Re: defining a reason=20
  code<BR></FONT><BR></DIV>
  <DIV></DIV>Ok.<BR><BR>The value and reason are required elements to =
the=20
  extValue type, aren't they?<BR><BR>So, I need always to have the value =
element=20
  even if I don't need it, right?<BR><BR>something like<BR><BR>&lt;epp=20
  xmlns=3D"urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=3D<A=20
  class=3Dmoz-txt-link-rfc2396E=20
  =
href=3D"http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/200=
1/XMLSchema-instance"</A>=20
  xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0 =
epp-1.0.xsd"&gt;<BR>&nbsp;=20
  &lt;response&gt;<BR>&nbsp;&nbsp;&nbsp; &lt;result=20
  code=3D"2200"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;msg&gt;Authentication=20
  error&lt;/msg&gt;<BR><B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;extValue&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;value/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </B><B>&lt;reason&gt;5004: you must do the login=20
  first&lt;/reason&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;/extValue&gt;</B><BR>&nbsp;&nbsp;&nbsp;=20
  &lt;/result&gt;<BR>&nbsp;&nbsp;&nbsp;=20
  &lt;trID&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <BR>&nbsp;&nbsp;&nbsp;=20
  &lt;/trID&gt;<BR>&nbsp; &lt;/response&gt;<BR>&lt;/epp&gt;<BR><BR>Best=20
  Regards,<BR>Eugenio<BR><BR><BR>Hollenbeck, Scott wrote:=20
  <BLOCKQUOTE=20
  =
cite=3Dmid:046F43A8D79C794FA4733814869CDF070231FBF5@dul1wnexmb01.vcorp.ad=
.vrsn.com=20
  type=3D"cite">
    <META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>From section 2.6 of RFC =
4930:</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D706411111-02042008></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>"Zero or more OPTIONAL &lt;extValue&gt; =
elements",=20
    and</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D706411111-02042008></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>"A &lt;reason&gt; element containing a =
human-readable=20
    message that describes the reason for the error.&nbsp; The language =
of the=20
    response is identified via an OPTIONAL "lang" attribute.&nbsp; If =
not=20
    specified, the default attribute value MUST be "en"=20
    (English)."</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D706411111-02042008></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>No namespace needed, but you've got the =
&lt;reason&gt;=20
    element inside a &lt;value&gt; element when it should be inside an=20
    &lt;extValue&gt; element.&nbsp; You should have some text in there,=20
    too.&nbsp; Perhaps something like "5004: Invalid=20
    password".</FONT></SPAN></DIV><!-- Converted from text/plain format =
-->
    <P><FONT size=3D2>-Scott-</FONT> </P>
    <DIV>&nbsp;</DIV><BR>
    <BLOCKQUOTE=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
rgb(0,0,255) 2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Eugenio Pinto [<A=20
      class=3Dmoz-txt-link-freetext=20
      =
href=3D"mailto:eugenio.pinto@fccn.pt">mailto:eugenio.pinto@fccn.pt</A>]=20
      <BR><B>Sent:</B> Wednesday, April 02, 2008 7:07 AM<BR><B>To:</B> =
<A=20
      class=3Dmoz-txt-link-abbreviated=20
      href=3D"mailto:ietf-provreg@cafax.se">ietf-provreg@cafax.se</A>; =
Hollenbeck,=20
      Scott<BR><B>Subject:</B> defining a reason=20
      code<BR></FONT><BR></DIV>Hi,<BR><BR>I have another question =
regarding=20
      extending response codes.<BR><BR>I defined the following response=20
      message:<BR><BR>&lt;epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"=20
      xmlns:xsi=3D<A class=3Dmoz-txt-link-rfc2396E=20
      href=3D"http://www.w3.org/2001/XMLSchema-instance"=20
      =
moz-do-not-send=3D"true">"http://www.w3.org/2001/XMLSchema-instance"</A> =

      xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0=20
      epp-1.0.xsd"&gt;<BR>&nbsp; &lt;response&gt;<BR>&nbsp;&nbsp;&nbsp;=20
      &lt;result code=3D"2200"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;msg&gt;Authentication=20
      error&lt;/msg&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;value&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
<B>&lt;reason&gt;5004&lt;/reason&gt;</B><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
      &lt;/value&gt;<BR>&nbsp;&nbsp;&nbsp; =
&lt;/result&gt;<BR>&nbsp;&nbsp;&nbsp;=20
      &lt;trID&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <BR>&nbsp;&nbsp;&nbsp;=20
      &lt;/trID&gt;<BR>&nbsp; =
&lt;/response&gt;<BR>&lt;/epp&gt;<BR><BR>where the=20
      reason element represents the code to a specific verified=20
      problem.<BR><BR>But I don't know if this is valid XML.<BR><BR>Can =
I define=20
      this this way, or I must include something with the namespace?=20
      like<BR><BR>&nbsp;&nbsp;&nbsp; &lt;result=20
      code=3D"2200"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;msg&gt;Authentication=20
      error&lt;/msg&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;value&gt;<BR><B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;ptdomain:panData =
xmlns:ptdomain=3D"urn:ietf:params:xml:ns:ptdomain-1.0"=20
      xsi:schemaLocation=3D"urn:ietf:params:xml:ns:ptdomain1.0=20
      ptdomain-1.0.xsd"&gt;=20
      <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</B><B>&nbsp;&nbsp;&nbsp;=20
      =
&lt;ptdomain:reason&gt;</B><B>5004</B><B>&lt;/ptdomain:reason&gt;<BR></B>=
<B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;brdomain:panData&gt;</B><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;/value&gt;<BR>&nbsp;&nbsp;&nbsp; &lt;/result&gt;<BR><BR>Thanks =
for=20
      your =
feedback.<BR><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8957C.279929D6--


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m333YqbK012726 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 3 Apr 2008 05:34:52 +0200 (MEST)
Received: (from majordom@localhost) by nic.cafax.se (8.13.7/8.12.11/Submit) id m333YqgB021863 for ietf-provreg-outgoing; Thu, 3 Apr 2008 05:34:52 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from app03.fccn.pt (app02.fccn.pt [193.137.198.37]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m333YpDt017516 for <ietf-provreg@cafax.se>; Thu, 3 Apr 2008 05:34:51 +0200 (MEST)
Received: from mx.anubis.local (ste [10.1.2.2]) by ste.anubis.internal (Postfix) with ESMTP id B149A19FC6D; Thu,  3 Apr 2008 04:34:50 +0100 (WEST)
Received: from [10.0.20.1] (vpn-1.corp.fccn.pt [10.0.20.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.anubis.local (Postfix) with ESMTP id 57E1B1B4455; Thu,  3 Apr 2008 04:34:49 +0100 (WEST)
Message-ID: <47F45048.3080305@fccn.pt>
Date: Thu, 03 Apr 2008 04:34:32 +0100
From: Eugenio Pinto <eugenio.pinto@fccn.pt>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
CC: ietf-provreg@cafax.se
Subject: [ietf-provreg] Re: defining a reason code
References: <046F43A8D79C794FA4733814869CDF070231FBF5@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <046F43A8D79C794FA4733814869CDF070231FBF5@dul1wnexmb01.vcorp.ad.vrsn.com>
Content-Type: multipart/alternative; boundary="------------080701020904090507070802"
X-Warning-Anubis: User opted out of Anti-Virus checks
X-Warning-Anubis: User opted out of Anti-Spam checks
X-Content-Checker: AnubisNetworks MPS
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

This is a multi-part message in MIME format.
--------------080701020904090507070802
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Ok.

The value and reason are required elements to the extValue type, aren't 
they?

So, I need always to have the value element even if I don't need it, right?

something like

<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
  <response>
    <result code="2200">
      <msg>Authentication error</msg>
*      <extValue>
        <value/>
        **<reason>5004: you must do the login first</reason>
      </extValue>*
    </result>
    <trID>
      <clTRID>FCCN-12386</clTRID>
      <svTRID>TRN7063050306</svTRID>
    </trID>
  </response>
</epp>

Best Regards,
Eugenio


Hollenbeck, Scott wrote:
> From section 2.6 of RFC 4930:
>  
> "Zero or more OPTIONAL <extValue> elements", and
>  
> "A <reason> element containing a human-readable message that describes 
> the reason for the error.  The language of the response is identified 
> via an OPTIONAL "lang" attribute.  If not specified, the default 
> attribute value MUST be "en" (English)."
>  
> No namespace needed, but you've got the <reason> element inside a 
> <value> element when it should be inside an <extValue> element.  You 
> should have some text in there, too.  Perhaps something like "5004: 
> Invalid password".
>
> -Scott-
>
>  
>
>     ------------------------------------------------------------------------
>     *From:* Eugenio Pinto [mailto:eugenio.pinto@fccn.pt]
>     *Sent:* Wednesday, April 02, 2008 7:07 AM
>     *To:* ietf-provreg@cafax.se; Hollenbeck, Scott
>     *Subject:* defining a reason code
>
>     Hi,
>
>     I have another question regarding extending response codes.
>
>     I defined the following response message:
>
>     <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>     xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
>       <response>
>         <result code="2200">
>           <msg>Authentication error</msg>
>           <value>
>             *<reason>5004</reason>*
>           </value>
>         </result>
>         <trID>
>           <clTRID>FCCN-12386</clTRID>
>           <svTRID>TRN7063050306</svTRID>
>         </trID>
>       </response>
>     </epp>
>
>     where the reason element represents the code to a specific
>     verified problem.
>
>     But I don't know if this is valid XML.
>
>     Can I define this this way, or I must include something with the
>     namespace? like
>
>         <result code="2200">
>           <msg>Authentication error</msg>
>           <value>
>     *        <ptdomain:panData
>     xmlns:ptdomain="urn:ietf:params:xml:ns:ptdomain-1.0"
>     xsi:schemaLocation="urn:ietf:params:xml:ns:ptdomain1.0
>     ptdomain-1.0.xsd">
>           **    <ptdomain:reason>**5004**</ptdomain:reason>
>     **        <brdomain:panData>*
>           </value>
>         </result>
>
>     Thanks for your feedback.
>

--------------080701020904090507070802
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Ok.<br>
<br>
The value and reason are required elements to the extValue type, aren't
they?<br>
<br>
So, I need always to have the value element even if I don't need it,
right?<br>
<br>
something like<br>
<br>
&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=<a
 class="moz-txt-link-rfc2396E"
 href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd"&gt;<br>
&nbsp; &lt;response&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;result code="2200"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;msg&gt;Authentication error&lt;/msg&gt;<br>
<b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;extValue&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;value/&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </b><b>&lt;reason&gt;5004: you must do the login
first&lt;/reason&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/extValue&gt;</b><br>
&nbsp;&nbsp;&nbsp; &lt;/result&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;trID&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <br>
&nbsp;&nbsp;&nbsp; &lt;/trID&gt;<br>
&nbsp; &lt;/response&gt;<br>
&lt;/epp&gt;<br>
<br>
Best Regards,<br>
Eugenio<br>
<br>
<br>
Hollenbeck, Scott wrote:
<blockquote
 cite="mid:046F43A8D79C794FA4733814869CDF070231FBF5@dul1wnexmb01.vcorp.ad.vrsn.com"
 type="cite">
  <title></title>
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta content="MSHTML 6.00.2900.3243" name="GENERATOR">
  <div dir="ltr" align="left"><span class="706411111-02042008"><font
 color="#0000ff" face="Arial" size="2">From section 2.6 of RFC 4930:</font></span></div>
  <div dir="ltr" align="left"><span class="706411111-02042008"></span>&nbsp;</div>
  <div dir="ltr" align="left"><span class="706411111-02042008"><font
 color="#0000ff" face="Arial" size="2">"Zero or more OPTIONAL
&lt;extValue&gt; elements", and</font></span></div>
  <div dir="ltr" align="left"><span class="706411111-02042008"></span>&nbsp;</div>
  <div dir="ltr" align="left"><span class="706411111-02042008"><font
 color="#0000ff" face="Arial" size="2">"A &lt;reason&gt; element
containing a human-readable message that describes the reason for the
error.&nbsp; The language of the response is identified via an OPTIONAL
"lang" attribute.&nbsp; If not specified, the default attribute value MUST
be "en" (English)."</font></span></div>
  <div dir="ltr" align="left"><span class="706411111-02042008"></span>&nbsp;</div>
  <div dir="ltr" align="left"><span class="706411111-02042008"><font
 color="#0000ff" face="Arial" size="2">No namespace needed, but you've
got the &lt;reason&gt; element inside a &lt;value&gt; element when it
should be inside an &lt;extValue&gt; element.&nbsp; You should have some
text in there, too.&nbsp; Perhaps something like "5004: Invalid password".</font></span></div>
<!-- Converted from text/plain format -->
  <p><font size="2">-Scott-</font> </p>
  <div>&nbsp;</div>
  <br>
  <blockquote
 style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
    <div class="OutlookMessageHeader" dir="ltr" align="left"
 lang="en-us">
    <hr tabindex="-1"> <font face="Tahoma" size="2"><b>From:</b>
Eugenio Pinto [<a class="moz-txt-link-freetext" href="mailto:eugenio.pinto@fccn.pt">mailto:eugenio.pinto@fccn.pt</a>] <br>
    <b>Sent:</b> Wednesday, April 02, 2008 7:07 AM<br>
    <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:ietf-provreg@cafax.se">ietf-provreg@cafax.se</a>; Hollenbeck, Scott<br>
    <b>Subject:</b> defining a reason code<br>
    </font><br>
    </div>
Hi,<br>
    <br>
I have another question regarding extending response codes.<br>
    <br>
I defined the following response message:<br>
    <br>
&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=<a
 moz-do-not-send="true" class="moz-txt-link-rfc2396E"
 href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd"&gt;<br>
&nbsp; &lt;response&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;result code="2200"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;msg&gt;Authentication error&lt;/msg&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;value&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <b>&lt;reason&gt;5004&lt;/reason&gt;</b><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/value&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;/result&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;trID&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <br>
&nbsp;&nbsp;&nbsp; &lt;/trID&gt;<br>
&nbsp; &lt;/response&gt;<br>
&lt;/epp&gt;<br>
    <br>
where the reason element represents the code to a specific verified
problem.<br>
    <br>
But I don't know if this is valid XML.<br>
    <br>
Can I define this this way, or I must include something with the
namespace? like<br>
    <br>
&nbsp;&nbsp;&nbsp; &lt;result code="2200"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;msg&gt;Authentication error&lt;/msg&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;value&gt;<br>
    <b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;ptdomain:panData
xmlns:ptdomain="urn:ietf:params:xml:ns:ptdomain-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:ptdomain1.0
ptdomain-1.0.xsd"&gt; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</b><b>&nbsp;&nbsp;&nbsp; &lt;ptdomain:reason&gt;</b><b>5004</b><b>&lt;/ptdomain:reason&gt;<br>
    </b><b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;brdomain:panData&gt;</b><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/value&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;/result&gt;<br>
    <br>
Thanks for your feedback.<br>
    <br>
  </blockquote>
</blockquote>
</body>
</html>

--------------080701020904090507070802--


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m32BGVeL007853 for <ietf-provreg-outgoing@nic.cafax.se>; Wed, 2 Apr 2008 13:16:31 +0200 (MEST)
Received: (from majordom@localhost) by nic.cafax.se (8.13.7/8.12.11/Submit) id m32BGVFA002606 for ietf-provreg-outgoing; Wed, 2 Apr 2008 13:16:31 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from peregrine.verisign.com (peregrine.verisign.com [216.168.239.74]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m32BGUeg014833 for <ietf-provreg@cafax.se>; Wed, 2 Apr 2008 13:16:31 +0200 (MEST)
Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com [10.170.12.139]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id m32B5J62007925; Wed, 2 Apr 2008 07:05:19 -0400
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 2 Apr 2008 07:16:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C894B2.FF0CEBFD"
Subject: [ietf-provreg] RE: defining a reason code
Date: Wed, 2 Apr 2008 07:16:35 -0400
Message-ID: <046F43A8D79C794FA4733814869CDF070231FBF5@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <47F368E9.1040009@fccn.pt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: defining a reason code
Thread-Index: AciUsbim7Mrt49xkSLKvJrCJpyk0+wAAJt9w
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Eugenio Pinto" <eugenio.pinto@fccn.pt>, <ietf-provreg@cafax.se>
X-OriginalArrivalTime: 02 Apr 2008 11:16:29.0059 (UTC) FILETIME=[FF6EA530:01C894B2]
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C894B2.FF0CEBFD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

>From section 2.6 of RFC 4930:
=20
"Zero or more OPTIONAL <extValue> elements", and
=20
"A <reason> element containing a human-readable message that describes
the reason for the error.  The language of the response is identified
via an OPTIONAL "lang" attribute.  If not specified, the default
attribute value MUST be "en" (English)."
=20
No namespace needed, but you've got the <reason> element inside a
<value> element when it should be inside an <extValue> element.  You
should have some text in there, too.  Perhaps something like "5004:
Invalid password".

-Scott-=20

=20


________________________________

	From: Eugenio Pinto [mailto:eugenio.pinto@fccn.pt]=20
	Sent: Wednesday, April 02, 2008 7:07 AM
	To: ietf-provreg@cafax.se; Hollenbeck, Scott
	Subject: defining a reason code
=09
=09
	Hi,
=09
	I have another question regarding extending response codes.
=09
	I defined the following response message:
=09
	<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
<http://www.w3.org/2001/XMLSchema-instance>
xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
	  <response>
	    <result code=3D"2200">
	      <msg>Authentication error</msg>
	      <value>
	        <reason>5004</reason>
	      </value>
	    </result>
	    <trID>
	      <clTRID>FCCN-12386</clTRID>=20
	      <svTRID>TRN7063050306</svTRID>=20
	    </trID>
	  </response>
	</epp>
=09
	where the reason element represents the code to a specific
verified problem.
=09
	But I don't know if this is valid XML.
=09
	Can I define this this way, or I must include something with the
namespace? like
=09
	    <result code=3D"2200">
	      <msg>Authentication error</msg>
	      <value>
	        <ptdomain:panData
xmlns:ptdomain=3D"urn:ietf:params:xml:ns:ptdomain-1.0"
xsi:schemaLocation=3D"urn:ietf:params:xml:ns:ptdomain1.0
ptdomain-1.0.xsd">=20
	          <ptdomain:reason>5004</ptdomain:reason>
	        <brdomain:panData>
	      </value>
	    </result>
=09
	Thanks for your feedback.
=09
=09


------_=_NextPart_001_01C894B2.FF0CEBFD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>From section 2.6 of RFC =
4930:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>"Zero or more OPTIONAL &lt;extValue&gt; =
elements",=20
and</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>"A &lt;reason&gt; element containing a =
human-readable=20
message that describes the reason for the error.&nbsp; The language of =
the=20
response is identified via an OPTIONAL "lang" attribute.&nbsp; If not =
specified,=20
the default attribute value MUST be "en" (English)."</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D706411111-02042008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>No namespace needed, but you've got the =
&lt;reason&gt;=20
element inside a &lt;value&gt; element when it should be inside an=20
&lt;extValue&gt; element.&nbsp; You should have some text in there, =
too.&nbsp;=20
Perhaps something like "5004: Invalid password".</FONT></SPAN></DIV><!-- =
Converted from text/plain format -->
<P><FONT size=3D2>-Scott-</FONT> </P>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Eugenio Pinto=20
  [mailto:eugenio.pinto@fccn.pt] <BR><B>Sent:</B> Wednesday, April 02, =
2008 7:07=20
  AM<BR><B>To:</B> ietf-provreg@cafax.se; Hollenbeck, =
Scott<BR><B>Subject:</B>=20
  defining a reason code<BR></FONT><BR></DIV>
  <DIV></DIV>Hi,<BR><BR>I have another question regarding extending =
response=20
  codes.<BR><BR>I defined the following response message:<BR><BR>&lt;epp =

  xmlns=3D"urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi=3D<A=20
  class=3Dmoz-txt-link-rfc2396E=20
  =
href=3D"http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/200=
1/XMLSchema-instance"</A>=20
  xsi:schemaLocation=3D"urn:ietf:params:xml:ns:epp-1.0 =
epp-1.0.xsd"&gt;<BR>&nbsp;=20
  &lt;response&gt;<BR>&nbsp;&nbsp;&nbsp; &lt;result=20
  code=3D"2200"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;msg&gt;Authentication=20
  error&lt;/msg&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;value&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
<B>&lt;reason&gt;5004&lt;/reason&gt;</B><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
  &lt;/value&gt;<BR>&nbsp;&nbsp;&nbsp; =
&lt;/result&gt;<BR>&nbsp;&nbsp;&nbsp;=20
  &lt;trID&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <BR>&nbsp;&nbsp;&nbsp;=20
  &lt;/trID&gt;<BR>&nbsp; &lt;/response&gt;<BR>&lt;/epp&gt;<BR><BR>where =
the=20
  reason element represents the code to a specific verified =
problem.<BR><BR>But=20
  I don't know if this is valid XML.<BR><BR>Can I define this this way, =
or I=20
  must include something with the namespace? =
like<BR><BR>&nbsp;&nbsp;&nbsp;=20
  &lt;result code=3D"2200"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;msg&gt;Authentication =
error&lt;/msg&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;value&gt;<BR><B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;ptdomain:panData =
xmlns:ptdomain=3D"urn:ietf:params:xml:ns:ptdomain-1.0"=20
  xsi:schemaLocation=3D"urn:ietf:params:xml:ns:ptdomain1.0 =
ptdomain-1.0.xsd"&gt;=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</B><B>&nbsp;&nbsp;&nbsp;=20
  =
&lt;ptdomain:reason&gt;</B><B>5004</B><B>&lt;/ptdomain:reason&gt;<BR></B>=
<B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;brdomain:panData&gt;</B><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &lt;/value&gt;<BR>&nbsp;&nbsp;&nbsp; &lt;/result&gt;<BR><BR>Thanks for =
your=20
  feedback.<BR><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C894B2.FF0CEBFD--


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m32B7KJX028222 for <ietf-provreg-outgoing@nic.cafax.se>; Wed, 2 Apr 2008 13:07:20 +0200 (MEST)
Received: (from majordom@localhost) by nic.cafax.se (8.13.7/8.12.11/Submit) id m32B7Kaa011387 for ietf-provreg-outgoing; Wed, 2 Apr 2008 13:07:20 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from app04.fccn.pt (app01.fccn.pt [193.137.198.36]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id m32B7JsI019252 for <ietf-provreg@cafax.se>; Wed, 2 Apr 2008 13:07:19 +0200 (MEST)
Received: from mx.anubis.local (ste [10.1.2.2]) by ste.anubis.internal (Postfix) with ESMTP id A39FE26EC8B; Wed,  2 Apr 2008 12:07:15 +0100 (WEST)
Received: from [10.0.20.1] (vpn-1.corp.fccn.pt [10.0.20.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.anubis.local (Postfix) with ESMTP id 361A11BFD7A; Wed,  2 Apr 2008 12:07:15 +0100 (WEST)
Message-ID: <47F368E9.1040009@fccn.pt>
Date: Wed, 02 Apr 2008 12:07:21 +0100
From: Eugenio Pinto <eugenio.pinto@fccn.pt>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: ietf-provreg@cafax.se, "Hollenbeck, Scott" <shollenbeck@verisign.com>
Subject: [ietf-provreg] defining a reason code
References: <046F43A8D79C794FA4733814869CDF070231F785@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <046F43A8D79C794FA4733814869CDF070231F785@dul1wnexmb01.vcorp.ad.vrsn.com>
Content-Type: multipart/alternative; boundary="------------050101070201070507000409"
X-Warning-Anubis: User opted out of Anti-Virus checks
X-Warning-Anubis: User opted out of Anti-Spam checks
X-Content-Checker: AnubisNetworks MPS
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

This is a multi-part message in MIME format.
--------------050101070201070507000409
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I have another question regarding extending response codes.

I defined the following response message:

<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
  <response>
    <result code="2200">
      <msg>Authentication error</msg>
      <value>
        *<reason>5004</reason>*
      </value>
    </result>
    <trID>
      <clTRID>FCCN-12386</clTRID>
      <svTRID>TRN7063050306</svTRID>
    </trID>
  </response>
</epp>

where the reason element represents the code to a specific verified problem.

But I don't know if this is valid XML.

Can I define this this way, or I must include something with the 
namespace? like

    <result code="2200">
      <msg>Authentication error</msg>
      <value>
*        <ptdomain:panData 
xmlns:ptdomain="urn:ietf:params:xml:ns:ptdomain-1.0" 
xsi:schemaLocation="urn:ietf:params:xml:ns:ptdomain1.0 ptdomain-1.0.xsd">
      **    <ptdomain:reason>**5004**</ptdomain:reason>
**        <brdomain:panData>*
      </value>
    </result>

Thanks for your feedback.


--------------050101070201070507000409
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
I have another question regarding extending response codes.<br>
<br>
I defined the following response message:<br>
<br>
&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xmlns:xsi=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd"&gt;<br>
&nbsp; &lt;response&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;result code="2200"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;msg&gt;Authentication error&lt;/msg&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;value&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <b>&lt;reason&gt;5004&lt;/reason&gt;</b><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/value&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;/result&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;trID&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;clTRID&gt;FCCN-12386&lt;/clTRID&gt; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;svTRID&gt;TRN7063050306&lt;/svTRID&gt; <br>
&nbsp;&nbsp;&nbsp; &lt;/trID&gt;<br>
&nbsp; &lt;/response&gt;<br>
&lt;/epp&gt;<br>
<br>
where the reason element represents the code to a specific verified
problem.<br>
<br>
But I don't know if this is valid XML.<br>
<br>
Can I define this this way, or I must include something with the
namespace? like<br>
<br>
&nbsp;&nbsp;&nbsp; &lt;result code="2200"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;msg&gt;Authentication error&lt;/msg&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;value&gt;<br>
<b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;ptdomain:panData
xmlns:ptdomain="urn:ietf:params:xml:ns:ptdomain-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:ptdomain1.0
ptdomain-1.0.xsd"&gt;
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</b><b>&nbsp;&nbsp;&nbsp; &lt;ptdomain:reason&gt;</b><b>5004</b><b>&lt;/ptdomain:reason&gt;<br>
</b><b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;brdomain:panData&gt;</b><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/value&gt;<br>
&nbsp;&nbsp;&nbsp; &lt;/result&gt;<br>
<br>
Thanks for your feedback.<br>
<br>
</body>
</html>

--------------050101070201070507000409--

