Re: [secdir] Review of draft-ietf-pwe3-iccp-stp-04

Mingui Zhang <zhangmingui@huawei.com> Wed, 23 September 2015 08:30 UTC

Return-Path: <zhangmingui@huawei.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6414B1A9097 for <secdir@ietfa.amsl.com>; Wed, 23 Sep 2015 01:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 nCn9Fj_pVszK for <secdir@ietfa.amsl.com>; Wed, 23 Sep 2015 01:30:33 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 854361A9094 for <secdir@ietf.org>; Wed, 23 Sep 2015 01:30:32 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BXY22949; Wed, 23 Sep 2015 08:30:29 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 23 Sep 2015 09:30:28 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.203]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0235.001; Wed, 23 Sep 2015 16:30:21 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: Shawn M Emery <shawn.emery@oracle.com>, "secdir@ietf.org" <secdir@ietf.org>
Thread-Topic: Review of draft-ietf-pwe3-iccp-stp-04
Thread-Index: AQHQ9deIDMAYKNPE50evs3I3IKG70J5Jx9Sw
Date: Wed, 23 Sep 2015 08:30:20 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E787206621@nkgeml512-mbx.china.huawei.com>
References: <559A155B.6080505@oracle.com> <56025EEB.5060602@oracle.com>
In-Reply-To: <56025EEB.5060602@oracle.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.146.93]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/secdir/S_Pwr18WkOlwDUZg6MMM1y5Rg0g>
Cc: "draft-ietf-pwe3-iccp-stp.all@tools.ietf.org" <draft-ietf-pwe3-iccp-stp.all@tools.ietf.org>
Subject: Re: [secdir] Review of draft-ietf-pwe3-iccp-stp-04
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 23 Sep 2015 08:30:36 -0000

Hi Shawn,

Thanks for the review! The comments will be incorporated in the new version.

Thanks,
Mingui 

> -----Original Message-----
> From: Shawn M Emery [mailto:shawn.emery@oracle.com]
> Sent: Wednesday, September 23, 2015 4:12 PM
> To: secdir@ietf.org
> Cc: draft-ietf-pwe3-iccp-stp.all@tools.ietf.org
> Subject: Review of draft-ietf-pwe3-iccp-stp-04
> 
> 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 draft specifies a Spanning Tree Protocol (STP) application for the
> Inter-Chassis Communication Protocol (ICCP).
> 
> The security considerations section does exist and refers to the base ICCP
> specification, RFC 7275, for applicability.  7275 lists the security constraints
> and limitations sufficiently when considering the reviewed draft.
> The section goes on to describe potential DoS attacks as described in 7275 and
> provides a single example to mitigate such an attack.  Even though this
> coverage is fairly sparse, 7275 outlines a more comprehensive list of thwarting
> potential threats.
> 
> General comments:
> 
> None.
> 
> Editorial comments:
> 
> PE, PW, AC, CE, and LDP are never expanded.
> 
> s/need be active/need to be active/
> 
> s/such system/such systems/
> 
> s/that support ICCP/that supports ICCP/
> 
> s/on CE or PE/on the CE or PE/
> 
> s/attack on channel/attack on a channel/
> 
> s/careful attack on channel/a careful attack on a channel/
> 
> Shawn.
> --