<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">FYI, the URL is here: <br>
      <br>
      <a
href="http://nat.sakimura.org/2013/08/27/refactoring-openid-connect-drafts/">http://nat.sakimura.org/2013/08/27/refactoring-openid-connect-drafts/</a><br>
      <br>
      <br>
      <br>
      (2013/09/06 13:28), Nat Sakimura wrote:<br>
    </div>
    <blockquote
      cite="mid:42C38498-31C5-478C-9B50-61F653811CCD@gmail.com"
      type="cite">
      <meta http-equiv="Context-Type" content="text/html; charset=utf-8">
      <div>Combined spec is up in the same blog page as partitioned ones
        now. </div>
      <div><br>
      </div>
      <div>Please review. </div>
      <div><br>
        Nat</div>
      <div><br>
        Sep 6, 2013 0:01、Mike Jones <<a moz-do-not-send="true"
          href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>>
        のメッセージ:<br>
        <br>
      </div>
      <blockquote type="cite">
        <div>
          <meta name="Generator" content="Microsoft Word 14 (filtered
            medium)">
          <div class="WordSection1">
            <p class="MsoNormal">Spec call notes 5-Sep-13</p>
            <p class="MsoNormal"> </p>
            <p class="MsoNormal">Nat Sakimura</p>
            <p class="MsoNormal">Mike Jones</p>
            <p class="MsoNormal">George Fletcher</p>
            <p class="MsoNormal">John Bradley</p>
            <p class="MsoNormal">Tony Nadalin</p>
            <p class="MsoNormal">Justin Richer</p>
            <p class="MsoNormal">Edmund Jay</p>
            <p class="MsoNormal"> </p>
            <p class="MsoNormal">Agenda:</p>
            <p class="MsoNormal">               Pre-IIW Meeting</p>
            <p class="MsoNormal">               Possible Pre-IETF 88
              Meeting</p>
            <p class="MsoNormal">               Document Structuring</p>
            <p class="MsoNormal">               Open Issues</p>
            <p class="MsoNormal"> </p>
            <p class="MsoNormal">Pre-IIW Meeting:</p>
            <p class="MsoNormal">               We will have several
              topics</p>
            <p class="MsoNormal"> </p>
            <p class="MsoNormal">Possible Pre-IETF 88 Meeting:</p>
            <p class="MsoNormal">               We will ask on the list
            </p>
            <p class="MsoNormal"> </p>
            <p class="MsoNormal">Document Structuring:</p>
            <p class="MsoNormal">               We reviewed Nat's first
              stab at <a moz-do-not-send="true"
href="http://nat.sakimura.org/2013/08/27/refactoring-openid-connect-drafts/">http://nat.sakimura.org/2013/08/27/refactoring-openid-connect-drafts/</a></p>
            <p class="MsoNormal">               Justin suggested
              combining Authentication Core and Authentication Implicit</p>
            <p class="MsoNormal">               Security and Privacy
              Considerations are still missing from this</p>
            <p class="MsoNormal">               Nat didn't yet have time
              to do the exercise of combining Messages and Standard</p>
            <p class="MsoNormal">               George suggested that we
              could keep the organization that Nat has done but produce
              a single concatenated version</p>
            <p class="MsoNormal">               George suggested that we
              could write a guide</p>
            <p class="MsoNormal">               Justin suggested that we
              could write the guide as a set of wiki pages that refer to
              spec sections</p>
            <p class="MsoNormal">               Nat said that we could
              name documents as Chapter 1, Chapter 2, etc.</p>
            <p class="MsoNormal">               John suggested having a
              single document with modular chapters that could be
              considered standalone documents</p>
            <p class="MsoNormal">               Mike said that the
              criticism he's heard most is that there are too many
              documents</p>
            <p class="MsoNormal">               Mike said that he'd like
              to see the combined document</p>
            <p class="MsoNormal">               Tony said that there is
              no place to start</p>
            <p class="MsoNormal">               Nat also proposes to
              delete the Basic and Implicit specs</p>
            <p class="MsoNormal">               Mike suggested that we
              have a "Getting Started" doc - Tony said that it could be
              called "Read Me First"</p>
            <p class="MsoNormal">               Mike asked if Nat could
              produce a stab at the combined document</p>
            <p class="MsoNormal">                              He agreed
              that he would</p>
            <p class="MsoNormal">                              Then we
              could ask people on the list what they think of the
              different choices</p>
            <p class="MsoNormal">               Tony said that SAML
              reorganized to combine about 20 documents into about 4</p>
            <p class="MsoNormal">               Tony said that there
              isn't a simple way to understand conformance</p>
            <p class="MsoNormal">                              Nat said
              that he hasn't included the Implementation Considerations
              section yet</p>
            <p class="MsoNormal">                             
              Implementation Considerations could be renamed Conformance</p>
            <p class="MsoNormal">               We will devote the next
              call after Nat produces the combined spec to continuing
              the discussion</p>
            <p class="MsoNormal">               Tony said that SAML has
              a separate conformance doc</p>
            <p class="MsoNormal">                              It
              describes different implementations, such as SSO profile</p>
            <p class="MsoNormal">                              John said
              that that's where the conformance profiles are defined</p>
            <p class="MsoNormal">                              Nat said
              that he'd prefer that we have a separate conformance
              document</p>
            <p class="MsoNormal"> </p>
            <p class="MsoNormal">Open Issues:</p>
            <p class="MsoNormal">               There are no new open
              issues</p>
          </div>
        </div>
      </blockquote>
      <blockquote type="cite">
        <div><span>_______________________________________________</span><br>
          <span>Openid-specs-ab mailing list</span><br>
          <span><a moz-do-not-send="true"
              href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a></span><br>
          <span><a moz-do-not-send="true"
              href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></span><br>
        </div>
      </blockquote>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Openid-specs-ab mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Nat Sakimura (<a class="moz-txt-link-abbreviated" href="mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>)
Nomura Research Institute, Ltd. 
Tel:+81-3-6274-1412 Fax:+81-3-6274-1547

本メールに含まれる情報は機密情報であり、宛先に記載されている方のみに送信することを意図しております。意図された受取人以外の方によるこれらの情報の開示、複製、再配布や転送など一切の利用が禁止されています。誤って本メールを受信された場合は、申し訳ござ&#1235
 6;&#124
14;せんが、送信者までお知らせいただき、受信されたメールを削除していただきますようお願い致します。
PLEASE READ:
The information contained in this e-mail is confidential and intended for the named recipient(s) only.
If you are not an intended recipient of this e-mail, you are hereby notified that any review, dissemination, distribution or duplication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete your copy from your system.
</pre>
  </body>
</html>