<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>We had no issues with validation of SMDs containing whitespace. Leaving whitespace in would marginally reduce our support costs, however it appears that more people would rather it is removed.</div>
<div><br>
</div>
<div>I disagree with the assertion that removal of whitespace is more correct. Validation failures due to whitespace is an indication of a defective implementation. Transformation the SMD XML document prior to signature validation, such as into an object then
back into an XML document, is likely subject to further defects.</div>
<div><br>
</div>
<div>We support only base64 encoded marks.</div>
<div><br>
</div>
<div>Regards,</div>
<div>James Mitchell / Product Owner</div>
</div>
<div>ARI Registry Services</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><Wodjenski>, Sharon <<a href="mailto:Sharon.Wodjenski@neustar.biz">Sharon.Wodjenski@neustar.biz</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, 6 August 2013 5:05 AM<br>
<span style="font-weight:bold">To: </span>"'Gould, James'" <<a href="mailto:JGould@verisign.com">JGould@verisign.com</a>>, Gustavo Lozano <<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:tmch-tech@icann.org">tmch-tech@icann.org</a>" <<a href="mailto:tmch-tech@icann.org">tmch-tech@icann.org</a>>, "<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>" <<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [gtld-tech] [tmch-tech] Test SMDs files now available<br>
</div>
<div><br>
</div>
<div xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">Gustavo,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">My comments also inline tagged with [SEW].<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><br>
Sharon<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">
<a href="mailto:tmch-tech-bounces@icann.org">tmch-tech-bounces@icann.org</a> [<a href="mailto:tmch-tech-bounces@icann.org">mailto:tmch-tech-bounces@icann.org</a>]
<b>On Behalf Of </b>Gould, James<br>
<b>Sent:</b> Monday, August 05, 2013 1:57 PM<br>
<b>To:</b> Gustavo Lozano<br>
<b>Cc:</b> <a href="mailto:tmch-tech@icann.org">tmch-tech@icann.org</a>; <a href="mailto:gtld-tech@icann.org">
gtld-tech@icann.org</a><br>
<b>Subject:</b> Re: [tmch-tech] Test SMDs files now available<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Gustavo,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">My feedback is below.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color: black; font-family: Calibri, sans-serif; ">-- </span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: black; font-family: Calibri, sans-serif; "> </span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: black; font-family: Calibri, sans-serif; ">JG</span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: black; font-family: Calibri, sans-serif; "> </span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: black; font-family: Calibri, sans-serif; "><img width="75" height="66" id="_x0000_i1025" src="cid:image001.png@01CE91EB.D8A5F520"></span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: black; font-family: Calibri, sans-serif; "> </span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(13, 44, 118); font-family: Calibri, sans-serif; ">James Gould</span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(54, 56, 59); font-family: Calibri, sans-serif; ">Principal Software Engineer</span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(5, 0, 226); font-family: Calibri, sans-serif; "><a href="mailto:jgould@verisign.com">jgould@verisign.com</a></span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(54, 56, 59); font-family: Calibri, sans-serif; "> </span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(54, 56, 59); font-family: Calibri, sans-serif; ">703-948-3271 (Office)</span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(52, 54, 57); font-family: Calibri, sans-serif; ">12061 Bluemont Way</span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(52, 54, 57); font-family: Calibri, sans-serif; ">Reston, VA 20190</span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(13, 44, 118); font-family: Calibri, sans-serif; ">VerisignInc.com</span><span style="color: black; font-family: Cambria, serif; "><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 11pt; color: black; font-family: Calibri, sans-serif; ">From:
</span></b><span style="font-size: 11pt; color: black; font-family: Calibri, sans-serif; ">Gustavo Lozano <<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>><br>
<b>Date: </b>Monday, August 5, 2013 1:28 PM<br>
<b>To: </b>James Gould <<a href="mailto:jgould@verisign.com">jgould@verisign.com</a>><br>
<b>Cc: </b>"<a href="mailto:tmch-tech@icann.org">tmch-tech@icann.org</a>" <<a href="mailto:tmch-tech@icann.org">tmch-tech@icann.org</a>>, "<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>" <<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>><br>
<b>Subject: </b>Re: [tmch-tech] Test SMDs files now available<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">James,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Let me discuss this with the development team, but before, I want to have feedback from the community about the following:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">I suppose that also the carriage returns should be eliminated and not only white spaces. This will create big lines (between 8K and 16K bytes). Does anyone
foresee implementation problems with big lines of text? <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">That is correct that no extra white space or carriage returns should be included (pretty printing), since including it introduces validation risk when unmarshaling
and marshaling the data. I do not believe the size of the lines should be an issue. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Has anyone have had success in using the test SMD XML (with the white spaces and carriage returns) in their EPP implementations including client libraries?<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">I have in the Launch EPP SDK although after changes. The existing Launch EPP SDK holds the attributes of the signed mark and encoded signed mark in attributes
of a class, where the marshaling (encoding) and unmarshaling (decoding) is done without keeping a full copy of the source DOM tree. Re-marshaling of the data will remove the extra white space and carriage returns, whether it's a signed mark or encoded signed
mark, thus resulting in invalidating it. I have updated the Launch EPP SDK to include an immutable signed mark that will hold the full copy of the source DOM tree to keep the extra white space and carriage returns. The changes allow for the creating of signed
marks from scratch and the parsing of signed marks with and without extra white space and carriage returns. Other client side and server side implementations might have to make similar adjustments to deal with the extra white space and carriage returns. </span><span style="font-size: 10.5pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">[SEW] We, too, had to make changes to the RTK to accommodate the white spaces/carriage returns and agree with Jim that the correct thing to
do is remove white spaces and carriage returns from the SMD.<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Even without whitespaces and carriage returns there is still risk that implementations may break the signature if precautions are not taken. One possibility
for mitigating this problem is requiring Registrars to send the base64-encoded blob from the SMD file (decoding base64 sounds cheaper than customer support).<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">I believe the best answer is to simply not add the extra white space and carriage returns in the signed mark XML within the SMD's. Since the SMD's base64
encode the signed mark, there is absolutely no benefit in pretty printing the signed mark XML. We all know that white space is significant with XML signatures, so pretty printing the XML prior to base64 encoding it introduces additional validation risk with
no perceived value. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">I have received questions about the use of <smd:signedMark> vs <smd:encodedSignedMark> in EPP.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">My question to all of you is:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">How many of you will require <smd:signedMark>-only by policy?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">How many of you will require <smd:encodedSignedMark>-only by policy?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">How many of you will support both?<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">We will support both. I believe the problem of pretty printing the signed mark XML prior to base64 encoding it is independent of what the servers will require
by policy since anyone can decode the base64 encoded signed mark. If adding the pretty printing of the signed mark XML is not needed and including the pretty printing increases the risk of validation errors, then the pretty printing the signed mark XML should
be removed. <o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">[SEW] We will support both.</span></i></b><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Thank you,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Gustavo<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 11pt; color: black; font-family: Calibri, sans-serif; ">From:
</span></b><span style="font-size: 11pt; color: black; font-family: Calibri, sans-serif; "><Gould>, James <<a href="mailto:JGould@verisign.com">JGould@verisign.com</a>><br>
<b>Date: </b>Saturday, August 3, 2013 7:33 AM<br>
<b>To: </b>Gustavo Lozano <<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>><br>
<b>Cc: </b>"<a href="mailto:tmch-tech@icann.org">tmch-tech@icann.org</a>" <<a href="mailto:tmch-tech@icann.org">tmch-tech@icann.org</a>>, "<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>" <<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>><br>
<b>Subject: </b>Re: [tmch-tech] Test SMDs files now available<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Gustavo,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">In reviewing the sample SMD's I notice that the decoded signed marks are pretty printed with spaces. I recommend that no spaces be used with the signed marks
since it introduces additional risk of validation errors. The spaces do not add any value since they are base64 encoded and software could pretty print the XML if needed outside of the validation flow.<br>
<br>
JG <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">James F. Gould<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Principal Engineer<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Verisign<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><a href="mailto:jgould@verisign.com">jgould@verisign.com</a><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><br>
On Jul 16, 2013, at 1:41 AM, "Gustavo Lozano" <<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Colleagues,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Information about the recently published test SMDs files can be found in the following link:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><a href="http://newgtlds.icann.org/en/about/trademark-clearinghouse/smd-test-repository-15jul13-en.pdf">http://newgtlds.icann.org/en/about/trademark-clearinghouse/smd-test-repository-15jul13-en.pdf</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">The different parties involved in the TMCH project have developed test SMDs files in order to obtain feedback from the community and assist implementers of
the SMD technology in testing their own implementations. These test SMDs files have been generated using the same models of HSMs (ICANN-TMCH-CA and TMV) that are going to be used in production. The code used to generate them is the latest version of the TMCH
code developed by the different parties involved in the TMCH project. These test SMDs files should cover the different test cases and comply with <a href="http://tools.ietf.org/html/draft-lozano-tmch-smd-02">http://tools.ietf.org/html/draft-lozano-tmch-smd-02</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">We appreciate your feedback no later than July 23, please test them and send your feedback to the mailing list or to me privately. We understand that this
is a short period of time and any bug found after this date will be corrected, but it is extremely helpful if you could send your feedback before this date.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Note: These test SMDs files include the TMV and CA certificate embedded in the XML, new test SMDs files are going to be generated soon in order to remove
the CA certificate. The inclusion of the CA certificate in the SMD file should not have an impact on the tests performed with these SMDs files.<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Thank you,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; color: black; font-family: Calibri, sans-serif; ">Gustavo<o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</span>
</body>
</html>