DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gondrom.org;
 b=SZPPsNGVqzRU2Kfr/EQZEviBGFRt6m9QBBYk0vl2rOqmHY/FB7OySI9MWCb44mu7z1jNpzTPJg9Xr+CS0eU5IzLwCTp7rkAjzq1cX364freFkDS/PNFjjvQ9Le9CJN+p;
 h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:X-Enigmail-Version:Content-Type;
Message-ID: <5147CDBE.5010809@gondrom.org>
Date: Tue, 19 Mar 2013 10:30:22 +0800
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: apps-discuss@ietf.org,  draft-schaad-pkix-rfc2875-bis​.all@tools.ietf.org
Content-Type: multipart/alternative;
 boundary="------------050603000603070804000509"
Cc: iesg@ietf.org
Subject: [apps-discuss] AppsDir review of draft-schaad-pkix-rfc2875-bis-07
Precedence: list

This is a multi-part message in MIME format.
--------------050603000603070804000509
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

I have been selected as the Applications Area Directorate reviewer for
this draft (for background on appsdir, please see ​
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).

Please resolve these comments along with any other Last Call comments
you may receive. Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-schaad-pkix-rfc2875-bis-07
Title: Constrained Application Protocol (CoAP)
Reviewer: Tobias Gondrom
Review Date: 18.03.2013

Summary: This draft is good work and almost ready for publication as
Standards Track RFC

Please clean up a number of spelling errors, mostly in section 1, a few
downward refs in the idnits and one minor question.

Comments/Questions:
- section 4.1.  ASN.1 Encoding
This question may be outdated, but would it be worth to mention in the
section to which ASN.1 version the spec is conform?

- Nits:
section 1:
s/Among the responsibilities of a Certificate Authority in issuing a
certificates/Among the responsibilities of a Certificate Authority in
issuing certificates
s/ and that it verify that/ and that it verifies that
s/requester of the certificate is call/requester of the certificate is
called
s/Two methods use the the key agreement process/Two methods use the key
agreement process
(there might be more...)


Reference Errors:
  ** Downref: Normative reference to an Informational RFC: RFC 2104

  ** Downref: Normative reference to an Informational RFC: RFC 2986

  ** Downref: Normative reference to an Informational RFC: RFC 6234


Best regards, Tobias



--------------050603000603070804000509
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="Arial">I have been selected as the Applications Area
      Directorate reviewer for <br>
      this draft (for background on appsdir, please see ​ <br>
      <a class="moz-txt-link-freetext" href="http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate">http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate</a>
      ).<br>
      <br>
      Please resolve these comments along with any other Last Call
      comments <br>
      you may receive. Please wait for direction from your document
      shepherd <br>
      or AD before posting a new version of the draft.<br>
      <br>
      Document: draft-schaad-pkix-rfc2875-bis-07<br>
      Title: Constrained Application Protocol (CoAP)<br>
      Reviewer: Tobias Gondrom<br>
      Review Date: 18.03.2013<br>
      <br>
      Summary: This draft is good work and almost ready for publication
      as Standards Track RFC<br>
      <br>
      Please clean up a number of spelling errors, mostly in section 1,
      a few downward refs in the idnits and one minor question. <br>
      <br>
      Comments/Questions:<br>
      - section 4.1.  ASN.1 Encoding<br>
      This question may be outdated, but would it be worth to mention in
      the section to which ASN.1 version the spec is conform? <br>
      <br>
      - Nits:<br>
      section 1: <br>
      s/Among the responsibilities of a Certificate Authority in issuing
      a certificates/</font><font face="Arial"><font face="Arial">Among
        the responsibilities of a Certificate Authority in issuing
        certificates<br>
        s/ and that it verify that/ and that it verifies that<br>
        s/requester of the certificate is call/requester of the
        certificate is called<br>
        s/Two methods use the the key agreement process/Two methods use
        the key agreement process<br>
      </font>(there might be more...)<br>
      <br>
      <br>
      Reference Errors: <br>
        ** Downref: Normative reference to an Informational RFC: RFC
      2104<br>
      <br>
        ** Downref: Normative reference to an Informational RFC: RFC
      2986<br>
      <br>
        ** Downref: Normative reference to an Informational RFC: RFC
      6234<br>
      <br>
      <br>
      Best regards, Tobias<br>
      <br>
      <br>
    </font>
  </body>
</html>

--------------050603000603070804000509--