IETF Logo Mail Archive

Re: [Rats] Use case -> architecture document

Thomas Hardjono <hardjono@mit.edu> Tue, 15 October 2019 17:53 UTC

Return-Path: <hardjono@mit.edu>
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 C478B120856 for <rats@ietfa.amsl.com>; Tue, 15 Oct 2019 10:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 8d10V98r4mid for <rats@ietfa.amsl.com>; Tue, 15 Oct 2019 10:53:11 -0700 (PDT)
Received: from outgoing-exchange-7.mit.edu (outgoing-exchange-7.mit.edu [18.9.28.58]) (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 8EA931208BD for <rats@ietf.org>; Tue, 15 Oct 2019 10:53:11 -0700 (PDT)
Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id x9FHqINC011903; Tue, 15 Oct 2019 13:52:24 -0400
Received: from oc11expo23.exchange.mit.edu (18.9.4.88) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 15 Oct 2019 13:52:17 -0400
Received: from oc11expo23.exchange.mit.edu (18.9.4.88) by oc11expo23.exchange.mit.edu (18.9.4.88) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 15 Oct 2019 13:52:31 -0400
Received: from oc11expo23.exchange.mit.edu ([18.9.4.88]) by oc11expo23.exchange.mit.edu ([18.9.4.88]) with mapi id 15.00.1365.000; Tue, 15 Oct 2019 13:52:30 -0400
From: Thomas Hardjono <hardjono@mit.edu>
To: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "Schönwälder, Jürgen" <J.Schoenwaelder@jacobs-university.de>, Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org>
CC: "rats@ietf.org" <rats@ietf.org>
Thread-Topic: [Rats] Use case -> architecture document
Thread-Index: AQHVfpUqjJtzD6RpnkWle2afJHWHDqdSdumAgAAwqYCAABSIAIAACXkAgAAPg4CACDdQAIABGICAgAANtAD//88sCA==
Date: Tue, 15 Oct 2019 17:52:30 +0000
Message-ID: <1571161950747.36630@mit.edu>
References: <CAHbuEH7f0jjquR=iZDgof4DkgpZKgxEP86NcQ0A1NQ=SP+_FHA@mail.gmail.com> <C02846B1344F344EB4FAA6FA7AF481F13E9560C0@dggemm511-mbx.china.huawei.com> <CAHbuEH7WkqeyUW3sL5bdw5N25B6O7ZEF0Qkx03fE5c42Sd4M5w@mail.gmail.com> <b91baad2-2fc3-a5e4-6898-e2cddcda300d@sit.fraunhofer.de> <20191009145006.r2pjsoo6jxirah64@anna.jacobs.jacobs-university.de> <CAHbuEH6u-6GsJjK8s0eFQPLeSuGjPMgonhyQkmaeA6Q+rp42kA@mail.gmail.com> <9379d880-2b7e-6657-c547-b37bb7a9e466@sit.fraunhofer.de> <CAHbuEH7XfWgPT+=T-Za9Cw-5GRQj0_+WT3L+Kd4aPp6VvU9jAQ@mail.gmail.com> <MWHPR21MB078499E5D4A2A5E697924EC7A3900@MWHPR21MB0784.namprd21.prod.outlook.com> <20191015154500.ruv2ie36hsxfb3qq@anna.jacobs.jacobs-university.de>, <a9b6c097-c8c4-1c88-374d-7d07ea34e626@sit.fraunhofer.de>
In-Reply-To: <a9b6c097-c8c4-1c88-374d-7d07ea34e626@sit.fraunhofer.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [199.243.96.171]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/mFtMcGwG85zfaLbvc1ghiwKVwuw>
Subject: Re: [Rats] Use case -> architecture document
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: Tue, 15 Oct 2019 17:53:21 -0000

I would prefer for RATS WG to continue with the current architecture draft (draft-birkholz-rats-architecture-02) and develop it further for many reasons (including that so much work and time has been put into this architecture draft).

Dave's new draft (draft-thaler-rats-architecture-00) well written, and identifies a very good problem scenario being solved.

One way to solve this dilemma of drafts is to use the term "profiles" for more specific/narrower problems being solved.

So if draft-birkholz could be the top level architecture document, then draft-thaler could be a profile that addresses a given problem scenario (e.g. network endpoint assessment).

This profiling approach is also used with great success in other WGs (e.g. OAuth WG with OAuth and UMA profile), and also in other standard organizations (e.g. SAML-WebSSO is a profile of SAML-core).

This would also allow other profile drafts in RATS to be developed beyond network endpoint assessment.


-- thomas --

v2.23.0 | Report a Bug | By Email