Return-Path: <rifaat.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 0C0B61296F9;
 Sat, 15 Oct 2016 03:14:35 -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 sPmqAyZBXaXD; Sat, 15 Oct 2016 03:14:33 -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 9D9DF1296F6;
 Sat, 15 Oct 2016 03:14:33 -0700 (PDT)
Received: by mail-vk0-x22c.google.com with SMTP id 83so112787807vkd.0;
 Sat, 15 Oct 2016 03:14:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; 
 h=mime-version:from:date:message-id:subject:to;
 bh=jFZsA7YAof+oWKCbYgnR9iBWZ/C0r/5HNcySQmI7OVw=;
 b=MiHqlgovQ9sFxKyLwS2hfDmnpjD86ZsP5YIBRNRalnT79UkNp/HOBpHmDeixdaJVaA
 uCBNr4bf23uivsURB1bpvJHewzLNhqE3IuXzAA8qSo0YMKuookrjINmo1fiUKPI0G2kH
 LpcIL8fzXcqI0Kx4O7DZAwoxHCBUFRm33mkIymyE/QaCqCjpfWClLtIfO3cr6AImGyQa
 UPoUQMIAMJOdaLGa9bmS5OpWmLiBU7XkO2Ld6Y/KudDoqF7FTRGGhmNuO3f66HrZJrNT
 wYLLwJqE7BPbdZwjXFqkLjU6bjUhzRdCSaqitqaWgC2K5y1vT42PSogbTXFKbFzsKL81
 9w4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=jFZsA7YAof+oWKCbYgnR9iBWZ/C0r/5HNcySQmI7OVw=;
 b=OwjuGNYaJ1ABbZQF6mu85FcfA/VBuESUHWqBNUpBbqaO7nifa9x7mtJp5Z55yzljyd
 CAG/qoSHPKjbz7UzSPkKPI2M5BmsM+yW/vU8hKUnP2U+5k+8xUnbw2jPearGW0IYZjwr
 UD11I6z8ozMIIxXzkHvz/5o4ANSDy3Jg0kLcL76WIYvfmdh241/YqZyLbDQI+kN926Cm
 MuxkWsFhuLKOFTqvYZDSzeXOC4+c+lf0i2fY4Yk6eqKK0EfiFyKwO9AA+tu2pWFyvNWL
 3JOu/0tvgek59Poj7N9WAXE3Fg0nm5HOLTvelfipdVBXX5EhqXFnznKBFnFMYsralJ9Y
 mwhQ==
X-Gm-Message-State: AA6/9RnOsq1dLa/GH05kitNyn2dRZkRTG5ksmmR4Wi5h33Sl8WzizDvn2MOZZNnMEDFQ1UGya3OYLYUWjNoJig==
X-Received: by 10.31.92.22 with SMTP id q22mr12317658vkb.88.1476526472677;
 Sat, 15 Oct 2016 03:14:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.3.116 with HTTP; Sat, 15 Oct 2016 03:14:32 -0700 (PDT)
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Sat, 15 Oct 2016 06:14:32 -0400
Message-ID: <CAGL6epLG+fW5Qx3iha0GDXEgsavw_f1HfzKhCSnNq2DAsbvwew@mail.gmail.com>
To: The IESG <iesg@ietf.org>, secdir@ietf.org, 
 draft-ietf-ccamp-ospf-availability-extension.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=001a114e61a2e7cead053ee49b2b
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/-6MMzHGweJB_x-7CIZBfcASrIkc>
Subject: [secdir] SecDir review of
 draft-ietf-ccamp-ospf-availability-extension-07
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 15 Oct 2016 10:14:35 -0000

--001a114e61a2e7cead053ee49b2b
Content-Type: text/plain; charset=UTF-8

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.

Summary: *Ready*

This is a Standard Track document that extend the GMPLS OSPF routing
protocol by introducing an optional ISCD Availability sub-TLV, which could
be used for route computation in a network that contains links with
variable discrete bandwidth. This document defines the distribution
mechanism for this new extension.

The Security Consideration section clearly describes the security and
privacy issues with this new extension, and since this is only an extension
to an existing mechanism, it points to other documents that cover the
mechanism and the security implications and potential solutions.

Regards,
 Rifaat

--001a114e61a2e7cead053ee49b2b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style=3D"font-size:12.8px">I have reviewed this docum=
ent as part of the security directorate&#39;s=C2=A0<span style=3D"font-size=
:12.8px">ongoing effort to review all IETF documents being processed by the=
=C2=A0</span><span style=3D"font-size:12.8px">IESG.=C2=A0 These comments we=
re written primarily for the benefit of the=C2=A0</span><span style=3D"font=
-size:12.8px">security area directors.=C2=A0 Document editors and WG chairs=
 should treat=C2=A0</span><span style=3D"font-size:12.8px">these comments j=
ust like any other last call comments.</span></div><div style=3D"font-size:=
12.8px"><br></div><div style=3D"font-size:12.8px">Summary:=C2=A0<b>Ready</b=
></div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12=
.8px">This is a Standard Track document that extend the GMPLS OSPF routing =
protocol by introducing <span style=3D"font-size:12.8px">an optional ISCD A=
vailability sub-TLV, which could be used for route computation in a network=
 that contains links with variable discrete bandwidth. This document define=
s the distribution mechanism for this new extension.</span></div><div style=
=3D"font-size:12.8px"><span style=3D"font-size:12.8px"><br></span></div><di=
v style=3D"font-size:12.8px"><span style=3D"font-size:12.8px">The Security =
Consideration section clearly describes the security and privacy issues wit=
h this new extension, and since this is only an extension to an existing me=
chanism, it points to other documents that cover the mechanism and the secu=
rity implications and potential solutions.</span></div><div style=3D"font-s=
ize:12.8px"><br></div><div style=3D"font-size:12.8px">Regards,</div><div st=
yle=3D"font-size:12.8px">=C2=A0Rifaat</div></div>

--001a114e61a2e7cead053ee49b2b--

