<html 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">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<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:Calibri;
panose-1:2 15 5 2 2 2 4 3 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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">>
</span>It uses a new namespaces for many of the existing elements. Thus,<o:p></o:p></p>
<p class="MsoNormal">data conforming to XAdES 101 903 (such as exisiting<o:p></o:p></p>
<p class="MsoNormal">OFF-CRYPTO XAdES) will never conform to XAdES 319 132.<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This is a good point to raise. Do we want to preclude the existing in-market XAdES from being used in OPC? I think that may not be a good idea. At this point,
the new XAdES is still a draft and will take some years to be approved by EU member states plus quite some years to possibly be adopted by industry. I can see allowing for the possibility of the new version, but I don’t think we ought to prevent the current
method from being used, even though it does have shortcomings addressed by the new version. I think any OPC-specific requirements we add can be specified in a manner that is XAdES version agnostic. For example, the ones in the draft text we looked at in
Bellevue that were based on MS-OFFCRYPTO and ODF. I think the normative references could allow both XAdES. This is a good topic for broader discussion.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">John<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> eb2mmrt@gmail.com [mailto:eb2mmrt@gmail.com]
<b>On Behalf Of </b>MURATA Makoto<br>
<b>Sent:</b> Saturday, April 4, 2015 6:30 AM<br>
<b>To:</b> SC34<br>
<b>Subject:</b> Re: OPC revision on top of XAdES 319 132-1 and -2<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt">Q3: Should we introduce a new value for<br>
ds:Reference/@Type? (My two cents: Yes)<o:p></o:p></p>
</blockquote>
<p class="MsoNormal">But this is mistaken. Both the new and legacy <br>
versions of XAdES use<br>
<a href="http://uri.etsi.org/01903#SignedProperties">http://uri.etsi.org/01903#SignedProperties</a> <br>
We have to use it.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">John left a comment on 12.6 (Generating Signatures) amd 12.7<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">(Validating Signatures) on his draft text for incorporating XAdES.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">His comment is:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> Does anything need to change here for XAdES?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Meanwhile, the new version of XAdES clearly says (in the Scope):<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> Procedures for creation and validation of XAdES <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> digital signatures are out of scope and specified in EN 319 102<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">So, the incorporation of XAdES does not require any changes to these<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">clauses.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Makoto<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">2015-04-01 9:16 GMT+09:00 MURATA Makoto <<a href="mailto:eb2m-mrt@asahi-net.or.jp" target="_blank">eb2m-mrt@asahi-net.or.jp</a>>:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal">Dear colleagues,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I reported the result of the Seattle meeting to XAdES<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">experts in Japan. They are happy to hear that SC34 and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">ETSI are likely to work together. I spoke with Kimura-san<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">and find that another committee in ETSI become a liaison of<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">another JTC1 committee recently by submitting a document to<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">JTC1. I sent that document to Juan and requested his<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">committee to submit it to JTC1.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I believe that we should use the upcoming version of XAdES<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">(319 132-1 [1] and 132-2 [2]) rather than the current<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">version (101 903) as a basis of our OPC revision. It uses<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">a new namespaces for many of the existing elements. Thus,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">data conforming to XAdES 101 903 (such as exisiting<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">OFF-CRYPTO XAdES) will never conform to XAdES 319 132.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">One of the issues in XAdES 101 903 is that the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">relationships among conformance levels is very unclear.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">XAdES 319 132 is much better than that. It now makes clear<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">which conformnace level requires which element in Annexes.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">But what should our spec look like? Here are some questions.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Q1: Shoulld we reference both 319 132-1 and 132-2? (My two cents: Yes)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Q2: Should we introduce a new value for Object/@Id? (My two cents: No)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Q3: Should we introduce a new value for ds:Reference/@Type? (My two cents: Yes)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Q4: Should we introduce some additional requirements on XAdES by <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> eliminating some options? (I have no ideas here.)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Makoto<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">[1] <a href="http://docbox.etsi.org/ESI/Open/Latest_Drafts/prEN-319132-1v009-XAdES-BuildingBlocksAndBaselineSignatures-STABLE-DRAFT.pdf" target="_blank">http://docbox.etsi.org/ESI/Open/Latest_Drafts/prEN-319132-1v009-XAdES-BuildingBlocksAndBaselineSignatures-STABLE-DRAFT.pdf</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">[2] <a href="http://docbox.etsi.org/ESI/Open/Latest_Drafts/prEN-319132-2v009-XAdES-ExtendedSignatures-STABLE-DRAFT.pdf" target="_blank">http://docbox.etsi.org/ESI/Open/Latest_Drafts/prEN-319132-2v009-XAdES-ExtendedSignatures-STABLE-DRAFT.pdf</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
Praying for the victims of the Japan Tohoku earthquake<br>
<br>
Makoto<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>