Re: [secdir] Secdir telechat review of draft-bchv-rfc6890bis-06

Brian Haberman <brian@innovationslab.net> Tue, 25 April 2017 13:16 UTC

Return-Path: <brian@innovationslab.net>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 561ED129AE8; Tue, 25 Apr 2017 06:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 BarfvB1WEHlq; Tue, 25 Apr 2017 06:16:10 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67C9F12EC9B; Tue, 25 Apr 2017 06:16:10 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 41D4788108; Tue, 25 Apr 2017 06:16:10 -0700 (PDT)
Received: from clemson.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id BE6CB3280AE4; Tue, 25 Apr 2017 06:16:09 -0700 (PDT)
To: Eric Rescorla <ekr@rtfm.com>
References: <149219238158.15851.11445565927708323216@ietfa.amsl.com> <39022825-ec29-cb90-6ed9-f52902804796@innovationslab.net> <CABcZeBOP8b-C05GLr5WkF4BcDDpq1HnwoKcuWHeVmueQZCyxAQ@mail.gmail.com>
Cc: Brian Weis <bew@cisco.com>, secdir@ietf.org, draft-bchv-rfc6890bis.all@ietf.org, IESG <iesg@ietf.org>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <168aa10a-a704-a2a7-aeda-bee7ec51d03b@innovationslab.net>
Date: Tue, 25 Apr 2017 09:16:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBOP8b-C05GLr5WkF4BcDDpq1HnwoKcuWHeVmueQZCyxAQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="dfqKhN8ame53hD0jUoPXOxl9sUxCPRQbI"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/OMdCXimkprzoJU2A5UcWSuvG2DY>
Subject: Re: [secdir] Secdir telechat review of draft-bchv-rfc6890bis-06
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 13:16:18 -0000

Done!


On 4/25/17 9:12 AM, Eric Rescorla wrote:
> You probably should, to be honest, just for convention. But I'm willing to
> defer to others on this topic.
> 
> -Ekr
> 
> 
> On Tue, Apr 25, 2017 at 5:22 AM, Brian Haberman <brian@innovationslab.net>
> wrote:
> 
>> Hi Brian,
>>      Thanks for the review. I will wait for the Security ADs to
>> determine if they want a "blank" Security Considerations section added.
>>
>> Regards,
>> Brian
>>
>>
>> On 4/14/17 1:53 PM, Brian Weis wrote:
>>> Reviewer: Brian Weis
>>> Review result: Ready
>>>
>>> I have reviewed this document as part of the security directorate's
>>> ongoing effort to review all IETF documents being processed by the
>>> IESG.  These comments were written primarily for the benefit of the
>>> security area directors.  Document editors and WG chairs should treat
>>> these comments just like any other last call comments.
>>>
>>> This five page document clarifies that the intent of the term "global"
>>> in RFC 6809 is for a special-purpose address to be "globally
>>> reachable". It also corrects some errors in the IANA Special-Purpose
>>> Address Registries.
>>>
>>> Since the scope of "global" is clarified rather than changed, there
>>> does not seem to be any additional security considerations.  None of
>>> the error corrections introduce additional security considerations
>>> either.  The authors obviously came to the same conclusion since they
>>> did not include a Security Considerations section. This does not
>>> concern me personally, and I'll leave it for the Security ADs to
>>> determine if they prefer one added that states "there are no security
>>> considerations".
>>>
>>> I consider the document Ready.
>>>
>>> Brian Weis
>>>
>>
>>
>