[secdir] SECDIR review of draft-ietf-spring-resiliency-use-cases

zhangdacheng <dacheng.zhang@huawei.com> Mon, 05 June 2017 01:46 UTC

Return-Path: <dacheng.zhang@huawei.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 BC1F9127869; Sun, 4 Jun 2017 18:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 PxH4llhEBcXv; Sun, 4 Jun 2017 18:46:36 -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 4044B124D6C; Sun, 4 Jun 2017 18:46:35 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DHX02190; Mon, 05 Jun 2017 01:46:33 +0000 (GMT)
Received: from SZXEMI402-HUB.china.huawei.com (10.82.75.34) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 5 Jun 2017 02:46:32 +0100
Received: from SZXEMI502-MBX.china.huawei.com ([169.254.5.112]) by SZXEMI402-HUB.china.huawei.com ([10.83.65.54]) with mapi id 14.03.0235.001; Mon, 5 Jun 2017 09:46:25 +0800
From: zhangdacheng <dacheng.zhang@huawei.com>
To: "secdir@ietf.org" <secdir@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-sipcore-name-addr-guidance.all@ietf.org" <draft-ietf-sipcore-name-addr-guidance.all@ietf.org>
CC: "draft-ietf-spring-resiliency-use-cases.all@ietf.org" <draft-ietf-spring-resiliency-use-cases.all@ietf.org>
Thread-Topic: SECDIR review of draft-ietf-spring-resiliency-use-cases
Thread-Index: AdLdnKOjtnTqkXDIRO6hg2kG+iEfdA==
Date: Mon, 05 Jun 2017 01:46:24 +0000
Message-ID: <879E76B64CF340468BF5E4DE504C2242C54869@szxemi502-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.167.227]
Content-Type: multipart/alternative; boundary="_000_879E76B64CF340468BF5E4DE504C2242C54869szxemi502mbxchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.5934B7F9.0089, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.5.112, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: eb6685a680d8b1ba91aa6d0461b5520d
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/RmIiojvZWimJFKsCgt-DwIvR0t4>
Subject: [secdir] SECDIR review of draft-ietf-spring-resiliency-use-cases
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: Mon, 05 Jun 2017 01:46:38 -0000


Hi,

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 document identifies and describes the requirements for a set of
   use cases related to network resiliency on Segment Routing (SPRING)
   networks.

This informational document introduces the candidate solutions/use cases which could be applied to enhance the network resiliency on SPRING networks when failures occurs. I think this work does not bring any additional security issue.

The document is READY for publication.

Thanks,

Dacheng