<div dir="ltr">John,<br><div class="gmail_extra"><br><div class="gmail_quote">2015-06-09 8:37 GMT+09:00 John Haug <span dir="ltr"><<a href="mailto:johnhaug@exchange.microsoft.com" target="_blank">johnhaug@exchange.microsoft.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">This is what I’ve been looking at recently in preparation for next week’s meeting. Can you (or someone you’ve been talking to) what is meant by this? In 6.2.2
“Notation for requirements” there is a listing of the meanings of various cell values in the large table showing which elements / qualifying properties / services apply to which XAdES level. The last item under #5 reads:<u></u><u></u></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10pt">"*": means that the qualifying property or signature’s element (service) identified in the first column<u></u><u></u></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10pt">should not be incorporated to the signature (provided) in the corresponding level. Upper signature levels<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt">may specify other requirements.</span><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Comparing to “shall not be present” it seems the key difference is “should not” vs. “shall not”. The example at the bottom of 6.2.2 looks at CompleteCertificateRefs.
The table entry for that row shows “*” for B-B and B-T and “shall not be present” for B-LT and B-LTA. Does that mean rows using “*” and “shall not be present” are effectively deprecating those elements/properties? These rows comprise four elements used in
XAdES-C plus the RefsOnlyTimeStamp and SigAndRefsTimeStamp.</span></p></div></div></blockquote><div><br></div><div>I have also been thinking about the same thing. I will e-mail JNSA. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang="EN-US" link="#0563C1" vlink="#954F72"><div><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Ultimately, I’m trying to compare the current XAdES levels with the upcoming ones and I can only see doing so by comparing which elements are allowed in each.
(Wouldn’t it be nice if there existed a schema for each level?)</span></p></div></div></blockquote><div><br></div><div>I did create a set of RNG schemas for the current XAdES. One driver file for each </div><div>conformance level. Unfortunately, mine is based on </div><div>the "misunderstanding" that -A requires -C. My schemas are available at</div><div><a href="http://www.asahi-net.or.jp/~eb2m-mrt/XAdES.zip">http://www.asahi-net.or.jp/~eb2m-mrt/XAdES.zip</a><br></div><div><br></div><div>Regards,</div><div>Makoto</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang="EN-US" link="#0563C1" vlink="#954F72"><div><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">John<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"> <a href="mailto:eb2mmrt@gmail.com" target="_blank">eb2mmrt@gmail.com</a> [mailto:<a href="mailto:eb2mmrt@gmail.com" target="_blank">eb2mmrt@gmail.com</a>]
<b>On Behalf Of </b>MURATA Makoto<br>
<b>Sent:</b> Sunday, June 7, 2015 4:41 AM<br>
<b>To:</b> SC34<br>
<b>Subject:</b> Levels of the existing and upcoming versions of XAdES<u></u><u></u></span></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">1. Existing XAdES<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">The existing XAdES (ETSI TS 101 903 V1.4.2) has four forms and three<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">advanced forms.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Four forms<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"> Basic Electronic Signature (XAdES-BES)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> Explicit Policy based Electronic Signature (XAdES-EPES)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> Electronic Signature with Validation Data (XAdES-T and XAdES-C).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Three advanced forms<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"> Extended signatures with time forms (XAdES-X) <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> Extended long electronic signatures with time (XAdES-X-L) <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> Archival electronic signatures (XAdES-A)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Conformant generators must support either XAdES-BES or XAdES-EPES,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">while conformance verifiers must support either XAdES-BES or<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">XAdES-EPES. Conformnace requirements on XAdES-T and those on XAdES-C<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">are defined, but generators or verifiers are not required to support<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">them. Conformance requirements on XAdES-X, XAdES-X-L, or XAdES-A are<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">not defined.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">ISO 14533-2(=JIS X5093) defines different conformance requirements.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">One is the support of XAdES-T, and the other is the support of<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">XAdES-A.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">2. Upcoming XAdES<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">The upcoming XAdES (Draft EN 319 132-1 and Draft EN 319 132-2) <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">provides four XAdES baseline signature levels (132-1) and <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">some additional levels (in 132-2).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">2.1 Baseline signature levels<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">a) B-B (some signed and some unsigned qualifying properties)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">b) B-T (trusted token proving that the signature itself actually<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">existed at a certain date and time.)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">c) B-LT (all the material required for validation)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">d) B-LTA (time-stamps that allow validation long time after the generation)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">2.2 Additional levels<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">There are:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">XAdES-E-BES<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">XAdES-E-EPES<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">XAdES-E-T<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">XAdES-E-C<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">XAdES-E-X<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">XAdES-E-X-Long<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">XAdES-E-X-L<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">XAdES-E-A signatures built on XAdES-E-T<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">XAdES-E-A signatures built on XAdES-E-C, XAdES-E-X, XAdES-E-X-Long, and XAdES-E-X-L<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Regards,<u></u><u></u></p>
</div>
<p class="MsoNormal">Makoto<u></u><u></u></p>
</div>
</div>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><br>Praying for the victims of the Japan Tohoku earthquake<br><br>Makoto</div>
</div></div>