<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Consolas" size="2"><span style="font-size:10.5pt;">
<div>Thanks. I was wondering if we should add an additional constraint regarding the number of octets. For example, what do we think about this text:</div>
<div> </div>
<div>The password supplied to the algorithm is to be a UTF-16LE encoded string; strings longer than 510 octets are truncated to 510 octets. <font color="red"><b>Further, the number of octets </b></font><font color="red"><b>should be evenly divisible by the
size of the octets of the character in the target octet set</b></font><font color="red"><b>. </b></font>If there is a leading BOM character (U+FEFF) in the encoded password it is removed before hash calculation.</div>
<div> </div>
<div>Does this add any value?</div>
<div> </div>
<div>Thanks,</div>
<div> </div>
<div>shawn</div>
<div>-----Original Message-----<br>
From: MURATA Makoto (FAMILY Given) [<a href="mailto:eb2m-mrt@asahi-net.or..jp">mailto:eb2m-mrt@asahi-net.or.jp</a>]
<br>
Sent: Tuesday, February 17, 2009 2:44 AM<br>
To: e-SC34-WG4@ecma-international.org<br>
Subject: Re: DR-09-0070: PML, Presentation: modifyVerifer password length</div>
<div> </div>
<div>Oops, we are a part of ISO. We should use "octet" rather than "byte",</div>
<div>since a byte is not always 8 bits. ISO/IEC 10646 uses "octet".</div>
<div> </div>
<div>--</div>
<div>MURATA Makoto (FAMILY Given) <EB2M-MRT@asahi-net.or.jp></div>
<div> </div>
<div> </div>
<div> </div>
</span></font>
</body>
</html>