Re: [stir] WG Last Call for STIR Certificates Document

J Braunberger <jbraunberger@gmail.com> Wed, 13 July 2016 21:09 UTC

Return-Path: <jbraunberger@gmail.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 695D512D8F2 for <stir@ietfa.amsl.com>; Wed, 13 Jul 2016 14:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y82XMyYzCLft for <stir@ietfa.amsl.com>; Wed, 13 Jul 2016 14:09:02 -0700 (PDT)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 564AF12D8EE for <stir@ietf.org>; Wed, 13 Jul 2016 14:09:02 -0700 (PDT)
Received: by mail-vk0-x22c.google.com with SMTP id j126so29192505vkg.3 for <stir@ietf.org>; Wed, 13 Jul 2016 14:09:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=3r2sANEoQShAU0ufYGYjAmlsyFWfSHKIUBlmB44c4x0=; b=Nn/laXufYfNJJkkVI2FW7dtPbnAGQeSWfZM5GhZhEJaKkXenokRGGf9HfH4mnm2hHY txqlPHaOTt4ioMLYDgpBOzkv/l7a2K8IkPQPP/t8pPVuFOkUrMHzJvi9bhMT5eXn30j5 ATWX/jKj/kp9J4h8Pq42Vb0xccS/5EKwPVS+iCrGAAI+NeTMNrSYRA6eaRiI9f4T1V1q IIgGG2wzBMvlCdM6WUZy+8mscqR5qPK11UHk3BW+0WF8B0jqLT2s0skff4jS2I8OhktV Ic8r7ZLDK4gv5SaDHem0GtSwaovFkK7ppc8SUVGEaC+qcoX78hvwxh3Ua7toZIruO+t+ cdhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=3r2sANEoQShAU0ufYGYjAmlsyFWfSHKIUBlmB44c4x0=; b=SdTFwkhELVe8hQ/5nHa7JD0EBINi9Fw32SDDQqur+/TrZwlsLhlSAq6X7J97WfbnkA no93ueTHFQhBQef4N6NDN7RYbflQykeO++RG+Y+g1iSSmef+VbUSKKC1y7NALfTcAzd5 YfUZ1QT+29yGmmCqKL21UlblPtUi1Wcyo+LuCqLAvKewmxmF3PNKhEHycXrjOlpRIhms JFAxbRrMY/YsgxLhCg2kPWxnEmK+7FhDvt37z/5OdUuw/ZlX9hTByBCc6EwtlNPgQHKN UDX0pTLJCY7ro9AWu1qPUw/XMXyGiJGlgia+NZcGlCYc7kEsSArXCwe2/LqqazRLfaIF ljTA==
X-Gm-Message-State: ALyK8tI1HZnGwJj+0jaT1YI/hXfrsblF0CqyDj+IPD5IU7gvRGXAb0Z1vFdJpiH6lwg6ZCS7a1uELf1if7An2A==
X-Received: by 10.31.107.146 with SMTP id k18mr4171448vki.35.1468444141338; Wed, 13 Jul 2016 14:09:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.33.150 with HTTP; Wed, 13 Jul 2016 14:09:00 -0700 (PDT)
In-Reply-To: <C9FA2A19-9D3E-411B-BB89-B211787594D3@vigilsec.com>
References: <C9FA2A19-9D3E-411B-BB89-B211787594D3@vigilsec.com>
From: J Braunberger <jbraunberger@gmail.com>
Date: Wed, 13 Jul 2016 14:09:00 -0700
Message-ID: <CAF8+_LAdab7GOs7RROn5ew64BTfD3M8_1R+7to2fD-Xww0F-tQ@mail.gmail.com>
To: IETF STIR Mail List <stir@ietf.org>
Content-Type: multipart/alternative; boundary="001a114783cc6ac7c405378acb2b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/Fi6pKLMCE2PB27lyaDyv_YicXt4>
Subject: Re: [stir] WG Last Call for STIR Certificates Document
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2016 21:09:04 -0000

Just found a few proofreading things for cleanup...

     - page 3, 2nd last paragraph, 2nd last line:  s/taht/that/

     - page 8, section 7, near end of 1st paragraph, the phrase before the
"," seems incomplete
                   "[I-D.ietf-stir-rfc4474bis] provides an "info" parameter
of the
                    Identity header which contains a URI where the
credential used to
                    generate the Identity header, and requires documents
which define
                   credential systems to list the URI schemes that may be
present in the
                   "info" parameter."
     - page 9, section 8, near end of 1st paragraph:  "TN Authorization
List extension particular is to allow a verifier to" - should it be "in
particular"?
     - page 10, section 3, last sentence:  should be "a future version" or
"future versions"
     - page 10, section 9, last sentence on page:  s/that/than/
     - page 11, section 9.1, last paragraph:  s/relying/relied/
     - page 13, section 9.2.1, 2nd paragraph, 2nd sentence:
 s/signlerequestExtensions/singleRequestExtensions/
     - page 13, first bullet:  s/Sectin/Section/
                                      also, "of as per in" - a little
awkward?
     - page 14, section 9.3, last sentence:  "A verifier would then follow
the URI to ascertain whether the list of TNs authorized for use by the
caller." -
                                                             incomplete
sentence?
     - page 15, 2nd line:   s/number/numbers/

John Braunberger

On Wed, Jul 13, 2016 at 12:43 PM, Russ Housley <housley@vigilsec.com> wrote:

> The authors of the STIR Certificates document
> (https://www.ietf.org/id/draft-ietf-stir-certificates-07.txt)
> have stated that the document is mature and ready for WG Last Call.
>
> This message starts a two week WG Last Call for the STIR Certificates
> document, which will end on 27 July 2016.  Ideally major concerns
> will be raised quickly so that they can be tackled during IETF 96.
>
> Please review the document and send comments on it to the STIR WG
> mail list.  Please clearly state your opinion as to whether the
> document is ready for publication as a standards-track RFC.
> Remember that support for publication is needed.
>
> Thanks,
> Russ & Robert
>
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir
>