IETF Logo Mail Archive

[Rats] Virtual Interim call for agenda

"Smith, Ned" <ned.smith@intel.com> Sat, 28 September 2019 19:35 UTC

Return-Path: <ned.smith@intel.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 77269120096 for <rats@ietfa.amsl.com>; Sat, 28 Sep 2019 12:35:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=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 Re1RQ3Np4Xcc for <rats@ietfa.amsl.com>; Sat, 28 Sep 2019 12:35:58 -0700 (PDT)
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) (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 3B0D1120019 for <rats@ietf.org>; Sat, 28 Sep 2019 12:35:58 -0700 (PDT)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Sep 2019 12:35:57 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.64,560,1559545200"; d="scan'208,217";a="194858094"
Received: from orsmsx103.amr.corp.intel.com ([10.22.225.130]) by orsmga006.jf.intel.com with ESMTP; 28 Sep 2019 12:35:57 -0700
Received: from orsmsx114.amr.corp.intel.com (10.22.240.10) by ORSMSX103.amr.corp.intel.com (10.22.225.130) with Microsoft SMTP Server (TLS) id 14.3.439.0; Sat, 28 Sep 2019 12:35:57 -0700
Received: from orsmsx109.amr.corp.intel.com ([169.254.11.122]) by ORSMSX114.amr.corp.intel.com ([169.254.8.55]) with mapi id 14.03.0439.000; Sat, 28 Sep 2019 12:35:57 -0700
From: "Smith, Ned" <ned.smith@intel.com>
To: "rats@ietf.org" <rats@ietf.org>
Thread-Topic: Virtual Interim call for agenda
Thread-Index: AQHVdjPyp7ZPvcTHz0qhMo5IJmMKQw==
Date: Sat, 28 Sep 2019 19:35:56 +0000
Message-ID: <3B8F8332-9BF0-4090-B42E-AB936D54013B@intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
x-originating-ip: [10.251.130.72]
Content-Type: multipart/alternative; boundary="_000_3B8F83329BF04090B42EAB936D54013Bintelcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/O896uzHegW4cgEERR62qpe08h-g>
Subject: [Rats] Virtual Interim call for agenda
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: Sat, 28 Sep 2019 19:36:00 -0000

Hello all!
I’m putting together the agenda for the RATS virtual interim scheduled for Tuesday, Oct 8th 2019 @ 14:30 UTC (7:30 PDT).
Draft agenda so far:

-          Milestones update (RATS chairs)

-       Architecture draft - https://datatracker.ietf.org/doc/draft-birkholz-rats-architecture/ - (Henk Birkholtz)

-          Interaction model draft - https://datatracker.ietf.org/doc/draft-birkholz-rats-reference-interaction-model/ - (Henk Birkholtz)

-       Yang module draft - https://datatracker.ietf.org/doc/draft-birkholz-rats-basic-yang-module/ - (Henk Birkholtz)

Also, should there be more discussion around which claims RATS WG is going to define?

  *   Are there missing claims?
  *   Is there growing consensus that the claims we currently define are sufficiently understood and relevant?
  *   How will RATS support vendor defined claims?

v2.23.0 | Report a Bug | By Email