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

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Tue, 25 April 2017 14:42 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
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 24A46131B91; Tue, 25 Apr 2017 07:42:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 wOGLpttTUTpN; Tue, 25 Apr 2017 07:42:28 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 AEC8F131499; Tue, 25 Apr 2017 07:40:05 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id v14so24339805pfd.2; Tue, 25 Apr 2017 07:40:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=64u3Z0GmSo7ldEvTp79ARpKjuJZgmwCgfDrQ2+2tvAY=; b=c0vuYzxB7Z0KPFH+EK8li+nNB0OeInIMOoiWS4cnuYrE5zH5xYTl0sGKbXX18i9qKM CxvFD7RV5Vyx7V2K510Z17lF8eIG8un/tnCmVkKRpd6FOkrANdUakYTYnzOu1SXXrhPg gzybX9i4NpDPOuwr6g1mLmDv7mPbAQFrW4DXx3Y8aU7AAVxfB2hHJJ0ijJe9nOfvwgKo uEvOuk3cli3urvAohRShuQFuxR8sbwqGS80JCKJwT0Z+pNGa2SKCYf3D8EJex925iXhV swEt/nEVLME23q+a5Lwzpnp65DX+gf8aB/6ItJDbPcwfepFC+fssfLLrhoMXQniz0hjr h2Jw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=64u3Z0GmSo7ldEvTp79ARpKjuJZgmwCgfDrQ2+2tvAY=; b=C9kXr8r4ZmdtbNHUl5Zfz6pU07SslyAzn3zmmFrGc0YGrLX+j588n5qjTT20AvMcIQ eCSoMkbjs6VfcNUE7Y3WgN7karBoHkyu6K5IpiFkWK/xEI/AkCVbCYnaBLlpe052tfMM fMovzssn1sEWAXm3EMxqanRquhoFiq1nfozbyxz3qBJEnTFTarsMymvv/UMknx8E7Fna Q5Yg8cibYmjW1pliANVMJkGeCjZfJOxcFsKIEV1sYnVu4LPLaAwdy4S8nKgoOVwZnmhg RtYfJf18mQEcG+QBfuYG0rcIlTEZKuszBMYJYnVwY5S0vDw+sR+7BBCsd0WDXJxBSZER bC/Q==
X-Gm-Message-State: AN3rC/4ez077rdu2/ENPweKCw2hupWz40bBIpG3u5F7iWR27pYv5m1JI KGLFXyXwY6VypXLZb7cpI6LJLdRUnA==
X-Received: by 10.98.29.86 with SMTP id d83mr29972031pfd.68.1493131205330; Tue, 25 Apr 2017 07:40:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.185.143 with HTTP; Tue, 25 Apr 2017 07:39:24 -0700 (PDT)
In-Reply-To: <168aa10a-a704-a2a7-aeda-bee7ec51d03b@innovationslab.net>
References: <149219238158.15851.11445565927708323216@ietfa.amsl.com> <39022825-ec29-cb90-6ed9-f52902804796@innovationslab.net> <CABcZeBOP8b-C05GLr5WkF4BcDDpq1HnwoKcuWHeVmueQZCyxAQ@mail.gmail.com> <168aa10a-a704-a2a7-aeda-bee7ec51d03b@innovationslab.net>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Tue, 25 Apr 2017 10:39:24 -0400
Message-ID: <CAHbuEH5c+k5+S_c5XXfXVEFggmgB6JJ_B-TA1_JRvj--DU3eBg@mail.gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Cc: Eric Rescorla <ekr@rtfm.com>, draft-bchv-rfc6890bis.all@ietf.org, Brian Weis <bew@cisco.com>, IESG <iesg@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/ccBUNQ2dGQcMohMsmlvMp9wfHvI>
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 14:42:31 -0000

Thank you, Brian Weis for the review.

Thanks for the update, Brian Haberman.

On Tue, Apr 25, 2017 at 9:16 AM, Brian Haberman
<brian@innovationslab.net> wrote:
> 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
>>>>
>>>
>>>
>>
>



-- 

Best regards,
Kathleen