Re: [OPSAWG] Secdir telechat review of draft-ietf-opsawg-service-assurance-architecture-12

Benoit Claise <benoit.claise@huawei.com> Tue, 03 January 2023 18:27 UTC

Return-Path: <benoit.claise@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96773C1524B2; Tue, 3 Jan 2023 10:27:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UbRfZor8ehPz; Tue, 3 Jan 2023 10:27:20 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 714D3C1524AC; Tue, 3 Jan 2023 10:27:20 -0800 (PST)
Received: from frapeml500001.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4NmggP2qf8z6HJLh; Wed, 4 Jan 2023 02:07:29 +0800 (CST)
Received: from [10.48.133.176] (10.48.133.176) by frapeml500001.china.huawei.com (7.182.85.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.34; Tue, 3 Jan 2023 19:12:06 +0100
Message-ID: <05df5bef-fb6f-f890-369d-905fbc757015@huawei.com>
Date: Tue, 03 Jan 2023 19:12:01 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1
Content-Language: en-GB
To: Christian Huitema <huitema@huitema.net>, secdir@ietf.org
CC: draft-ietf-opsawg-service-assurance-architecture.all@ietf.org, last-call@ietf.org, opsawg@ietf.org
References: <167156291971.30422.1052696363553168878@ietfa.amsl.com>
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <167156291971.30422.1052696363553168878@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.48.133.176]
X-ClientProxiedBy: dggems705-chm.china.huawei.com (10.3.19.182) To frapeml500001.china.huawei.com (7.182.85.94)
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/4BgRaLYYeDNV-TgBf9UzXLEIh0I>
Subject: Re: [OPSAWG] Secdir telechat review of draft-ietf-opsawg-service-assurance-architecture-12
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2023 18:27:21 -0000

Thanks Christian.

Regards, Benoit

On 12/20/2022 8:01 PM, Christian Huitema via Datatracker wrote:
> Reviewer: Christian Huitema
> Review result: Ready
>
> My review of version 11 of this draft was making a number of suggestions. These
> suggestions have largely been addressed in the version 12 of the draft:
>
> * The risk caused by compromised agents are addressed by setting permissions
> according to [I-D.ietf-opsawg-service-assurance-yang].
>
> * The security section now includes a more precise description of the
> permissions that should be granted to SAIN agents
>
> * The authors added recommendation that service administrators only obtain the
> information needed for building the assurance graph and no more, which somewhat
> mitigates the risk of attackers using configuration data.
>
> * The authors added a suggestion to compare reporting by multiple agents and
> detect potential anomalies such as compromised agent mishbehaving, and
> reasonably flag that as a point for further study.
>
> * The risks caused by loss of access to NTP service are documented.
>
> In addition to flagging the NTP risk, the authors could have suggested
> mitigation for temporary loss of access to the NTP service. There might be ways
> such as indicating the state of the clocks in the agents report, or estimating
> potential clock drift based on quality of local clocks and delay since the last
> NTP synchronization. However, this is  speculative and it would be sufficient
> to flag it for further study.
>
>
>
>