[Rats] 答复: Call for adoption (after draft rename) for Yang module draft

"Xialiang (Frank, Network Standard & Patent Dept)" <frank.xialiang@huawei.com> Mon, 18 November 2019 10:39 UTC

Return-Path: <frank.xialiang@huawei.com>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC1B2120851 for <rats@ietfa.amsl.com>; Mon, 18 Nov 2019 02:39:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 cewGIxdgIX2S for <rats@ietfa.amsl.com>; Mon, 18 Nov 2019 02:39:29 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22BF41200DF for <rats@ietf.org>; Mon, 18 Nov 2019 02:39:29 -0800 (PST)
Received: from lhreml705-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 22008EB4B3CB2C6B7EB6; Mon, 18 Nov 2019 10:39:27 +0000 (GMT)
Received: from lhreml711-chm.china.huawei.com (10.201.108.62) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 18 Nov 2019 10:39:26 +0000
Received: from lhreml711-chm.china.huawei.com (10.201.108.62) by lhreml711-chm.china.huawei.com (10.201.108.62) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Mon, 18 Nov 2019 10:39:26 +0000
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by lhreml711-chm.china.huawei.com (10.201.108.62) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Mon, 18 Nov 2019 10:39:26 +0000
Received: from DGGEMM511-MBX.china.huawei.com ([169.254.1.140]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0439.000; Mon, 18 Nov 2019 18:39:22 +0800
From: "Xialiang (Frank, Network Standard & Patent Dept)" <frank.xialiang@huawei.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "rats@ietf.org" <rats@ietf.org>
Thread-Topic: [Rats] Call for adoption (after draft rename) for Yang module draft
Thread-Index: AQHVlCwI8/lytau3hU+AhCwtIdg/0ad+BqGAgAAHhQCAAAO1AIAGacyAgAAGuYCAAJAygIAAtdsAgAB+MgCAAqU4AIACdRAAgAOa1oCAATDOAIAAAeiAgAAadwCAAIeEoA==
Date: Mon, 18 Nov 2019 10:39:21 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F13EA50B8E@dggemm511-mbx.china.huawei.com>
References: <147F9159-6055-4E55-ABDC-43DFE3498BF1@island-resort.com> <ce5f8206-74dc-36bb-0093-a93045d5c67f@sit.fraunhofer.de> <0A7E3A4F-8534-4E98-BCB7-1454E07699F4@island-resort.com> <C3AE2645-49C8-4313-BCED-02FEB576B614@cisco.com> <1C8A1884-A37D-45E3-8C11-2FC5A083B245@island-resort.com> <HE1PR0702MB375366C5F7FE5C497C35D73B8F740@HE1PR0702MB3753.eurprd07.prod.outlook.com> <7106C9D3-8ED1-419E-81F8-4CDA799BEDAE@intel.com> <MWHPR21MB07844F61BEFAE03F9E7DD290A3770@MWHPR21MB0784.namprd21.prod.outlook.com> <6E7D64B4-2049-4D0A-ADC5-CA3F0647779B@island-resort.com> <MWHPR21MB07840B6CF7BEE0A11ABE54BFA3700@MWHPR21MB0784.namprd21.prod.outlook.com> <20191117144129.llvg7fsrqgaqtgkn@anna.jacobs.jacobs-university.de> <MWHPR21MB0784B0111EADA4A9A6C766D0A34D0@MWHPR21MB0784.namprd21.prod.outlook.com> <FADBA46B-5B70-4B21-A159-B22593310B53@island-resort.com> <5993.1574073238@dooku.sandelman.ca>
In-Reply-To: <5993.1574073238@dooku.sandelman.ca>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.41.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/4363LeGtPUcyXHUor7WgO0wCvQc>
Subject: [Rats] =?utf-8?b?562U5aSNOiAgQ2FsbCBmb3IgYWRvcHRpb24gKGFmdGVy?= =?utf-8?q?_draft_rename=29_for_Yang_module_draft?=
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Remote Attestation Procedures <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2019 10:39:31 -0000

Policy Enforcement Point or Policy Decision Point?

-----邮件原件-----
发件人: RATS [mailto:rats-bounces@ietf.org] 代表 Michael Richardson
发送时间: 2019年11月18日 18:34
收件人: rats@ietf.org
主题: Re: [Rats] Call for adoption (after draft rename) for Yang module draft


    >> Case 1) The network notices anomalous traffic coming from a device
    >> already on the network, which triggers a verifier to ask the device to
    >> attest to its health (which may have changed since it was last
    >> attested).  Here there might even be no Relying Party involved per se.

    >> Case 2) The network has not noticed anything odd, but wants to
    >> proactively query a device anyway, e.g., because the network's
    >> appraisal policy of what is considered trustworthy has just changed.
    >> Again there might even be no Relying Party involved.

Laurence Lundblade <lgl@island-resort.com>; wrote:
    > I would call the network the relying party. Attestation always has a
    > relying party because there would be no point if no one cared (if a
    > tree falls in a forest…)

I would be even more specific to say that the network's Policy Enforcement Point is the relying party. 


--
Michael Richardson <mcr+IETF@sandelman.ca>;, Sandelman Software Works  -= IPv6 IoT consulting =-