Re: [Rats] Requesting timeslot at IETF 119

"Liuchunchi(Peter)" <liuchunchi@huawei.com> Sun, 10 March 2024 07:47 UTC

Return-Path: <liuchunchi@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 90ACCC14F61E; Sat, 9 Mar 2024 23:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 yuJHx3SMol7B; Sat, 9 Mar 2024 23:47:25 -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 8E9D7C14E515; Sat, 9 Mar 2024 23:47:25 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4TssLl26k9z6K5pj; Sun, 10 Mar 2024 15:42:23 +0800 (CST)
Received: from lhrpeml100006.china.huawei.com (unknown [7.191.160.224]) by mail.maildlp.com (Postfix) with ESMTPS id 433B7140C72; Sun, 10 Mar 2024 15:47:22 +0800 (CST)
Received: from canpemm100005.china.huawei.com (7.192.105.21) by lhrpeml100006.china.huawei.com (7.191.160.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Sun, 10 Mar 2024 07:47:20 +0000
Received: from dggpeml500018.china.huawei.com (7.185.36.186) by canpemm100005.china.huawei.com (7.192.105.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Sun, 10 Mar 2024 15:47:18 +0800
Received: from dggpeml500018.china.huawei.com ([7.185.36.186]) by dggpeml500018.china.huawei.com ([7.185.36.186]) with mapi id 15.01.2507.035; Sun, 10 Mar 2024 15:47:18 +0800
From: "Liuchunchi(Peter)" <liuchunchi@huawei.com>
To: "Smith, Ned" <ned.smith@intel.com>, "rats@ietf.org" <rats@ietf.org>, "rats-chairs@ietf.org" <rats-chairs@ietf.org>
CC: "Eric Voit (evoit)" <evoit@cisco.com>
Thread-Topic: Requesting timeslot at IETF 119
Thread-Index: AdpxChGrro//Co26RuiAru0hIyNUoQASRN0AAFqTCpA=
Date: Sun, 10 Mar 2024 07:47:17 +0000
Message-ID: <5779c8c553644c2b9d4d8804d31a9226@huawei.com>
References: <145b9c98d53b472daff5ac8f52ea9bda@huawei.com> <D819E9AD-4F29-4AC2-BD9A-02DAC2AAD9B3@intel.com>
In-Reply-To: <D819E9AD-4F29-4AC2-BD9A-02DAC2AAD9B3@intel.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.39.60]
Content-Type: multipart/alternative; boundary="_000_5779c8c553644c2b9d4d8804d31a9226huaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/VdF8tw1MUSrTRkN1x1VhhDHUklI>
Subject: Re: [Rats] Requesting timeslot at IETF 119
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 10 Mar 2024 07:47:29 -0000

Hello Ned,

Thank you for the reply. I am familiar with this draft. In fact it is actively discussed in NASR mailing list.

I can summarize existing mailing list discussions about this draft in my talk, if approved.

Best,
Peter

From: Smith, Ned <ned.smith@intel.com>
Sent: Saturday, March 9, 2024 4:21 AM
To: Liuchunchi(Peter) <liuchunchi@huawei.com>; rats@ietf.org; rats-chairs@ietf.org
Cc: Eric Voit (evoit) <evoit@cisco.com>
Subject: Re: Requesting timeslot at IETF 119

Peter,
Thanks for the request.
BTW: Are you familiar with draft-voit-rats-trustworthy-path-routing-09 (ietf.org)<https://datatracker.ietf.org/doc/draft-voit-rats-trustworthy-path-routing/>
Thx,
Ned

From: "Liuchunchi(Peter)" <liuchunchi=40huawei.com@dmarc.ietf.org<mailto:liuchunchi=40huawei.com@dmarc.ietf.org>>
Date: Thursday, March 7, 2024 at 7:41 PM
To: "rats@ietf.org<mailto:rats@ietf.org>" <rats@ietf.org<mailto:rats@ietf.org>>, "rats-chairs@ietf.org<mailto:rats-chairs@ietf.org>" <rats-chairs@ietf.org<mailto:rats-chairs@ietf.org>>
Subject: Requesting timeslot at IETF 119
Resent-From: <alias-bounces@ietf.org<mailto:alias-bounces@ietf.org>>
Resent-To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com<mailto:Kathleen.Moriarty.ietf@gmail.com>>, Nancy Cam-Winget <ncamwing@cisco.com<mailto:ncamwing@cisco.com>>, <ned.smith@intel.com<mailto:ned.smith@intel.com>>
Resent-Date: Thursday, March 7, 2024 at 7:41 PM

Dear RATS and chairs,

Recently we are preparing a BoF and potential creation of a new working group that is highly relevant to RATS. The name is Network Attestation for Secure Routing (NASR<https://www.ietf.org/mailman/listinfo/nasr>).

Taking the name literally, NASR extends the attestation process to a routing path by consuming and connecting RATS’ attestation results of every device on this path. The final goal is to route sensitive data packets only on top of trusted devices, trusted operating environments or trusted services.

Since this initiative uses RATS outputs and share a similar concept with RATS, we need guidance and advice (or better, help) from RATS. I would like to request 10 minutes of agenda time to present, if possible..

Draft: draft-liu-nasr-requirements-01<https://datatracker.ietf.org/doc/draft-liu-nasr-requirements/>
Side Meeting: https://github.com/liuchunchi/nasr_side_meeting

Best regards,
Peter (Chunchi) Liu