[Teep] Secure Channel definition for TEEP Use Case for Confidential Computing
Ira McDonald <blueroofmusic@gmail.com> Wed, 09 November 2022 16:34 UTC
Return-Path: <blueroofmusic@gmail.com>
X-Original-To: teep@ietfa.amsl.com
Delivered-To: teep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49148C14CE47 for <teep@ietfa.amsl.com>; Wed, 9 Nov 2022 08:34:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 WgvP7ZihmGvc for <teep@ietfa.amsl.com>; Wed, 9 Nov 2022 08:34:42 -0800 (PST)
Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37389C14CE27 for <teep@ietf.org>; Wed, 9 Nov 2022 08:34:42 -0800 (PST)
Received: by mail-ua1-x92c.google.com with SMTP id p1so5595611uak.11 for <teep@ietf.org>; Wed, 09 Nov 2022 08:34:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Kw7iTyMFGkUeMicoAHry7IDSn12PBMS+teOAkDufYig=; b=lW5lLLnPksKbUJH5B/CYyr6gUQPIRrNj+kCDPo/+1lDdDB4U22bbj0imoLndedr9GN b1ZheQ8WzONKe3velizQGHWNnJPVDbL3tFpR3nXp18SrmMTrhqj1nXl9DEpybxyTB8DC hYBw+SNecib0eCfpl9GaVQ6xqj8E+zwgcOAGAssxOlidJRKqI1r1D1pgnxyLZhZFyCT8 vcW6jUhN7Qz0ISUVIMsP0HsAGE3lzweXG0qBjgLdZj4U+4V5GKw3iDOgPiD1wxWdHnc0 ih0wE4uRS01aEE18XCjrGDI1BRrmm/y5um4hMFhATrFu7myK8QhqvuN7CBhvJCpOHBqN p54g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Kw7iTyMFGkUeMicoAHry7IDSn12PBMS+teOAkDufYig=; b=rHVnWD9xueluFw9u9cFHG+ZhyH8B/f1e9gh4aHwmasZe9Qp4o/x7EJFJutxMnGKH4F 0ytgHu29iAaY36q2rASWtcIRatqQrwX+rluSzMJQU+tONtuGqtVJfApThyiChw+oJ42d rI+5C7NPx09yo1fdBQL6W6w/2D0q/tG59RXIXUey/6xGIfQyfsQq2LUdtPCcGqo7SuTn zglHhDpRDsl33I8JEmeUrhi2OuuqEWbzdonIfVkB2PkPipESxlbnkxDH913I42x9fog0 frPTM0MgTYw6ih4HVBh0QDY1whbB3WW8iOJ8/yxy+0S1BUq6aedeRdvQDrC3FLCCn+TN 6EjQ==
X-Gm-Message-State: ACrzQf2V28vY75EH90Ad49gTelGfYxmGbsx5Z8ODpIp7kOKIXWc3Nkle YhVn0c7iZVht2WfEt7796KW6LwOQVtImBaFU3X7xb8pu0L4=
X-Google-Smtp-Source: AMsMyM4KqKcjbV/HzGt00k1olxuPFjo865yByImbPX3iTuxLQi/5OC1LtwOa4OiA9vOknYp9MyRKS+YghNqGp71RkHQ=
X-Received: by 2002:ab0:5659:0:b0:40f:f3d5:a241 with SMTP id z25-20020ab05659000000b0040ff3d5a241mr19359028uaa.70.1668011680833; Wed, 09 Nov 2022 08:34:40 -0800 (PST)
MIME-Version: 1.0
From: Ira McDonald <blueroofmusic@gmail.com>
Date: Wed, 09 Nov 2022 11:34:29 -0500
Message-ID: <CAN40gSs6m0RF2TrvUX+yrb91DMr5fWpD93XxnzfJz933+68tKQ@mail.gmail.com>
To: teep <teep@ietf.org>, Ira McDonald <blueroofmusic@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000b7a40605ed0c3bda"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/iEPUKUGP14feSqtCmPNwnk6tNrc>
Subject: [Teep] Secure Channel definition for TEEP Use Case for Confidential Computing
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A Protocol for Dynamic Trusted Execution Environment Enablement <teep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teep>, <mailto:teep-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teep/>
List-Post: <mailto:teep@ietf.org>
List-Help: <mailto:teep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teep>, <mailto:teep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2022 16:34:46 -0000
Hi, >From NIST Glossary https://csrc.nist.gov/glossary/term/secure_channel: "A path for transferring data between two entities or components that ensures confidentiality, integrity and replay protection, as well as mutual authentication between the entities or components. The secure channel may be provided using approved cryptographic, physical or procedural methods, or a combination thereof. Sometimes called a trusted channel." from SP800-90A-Rev1 https://doi.org/10.6028/NIST.SP.800-90Ar1 I suggest using this definition. Cheers, - Ira *Ira McDonald (Musician / Software Architect)* *Chair - SAE Trust Anchors and Authentication TF* *Co-Chair - TCG Trusted Mobility Solutions WG* *Co-Chair - TCG Metadata Access Protocol SG* *Chair - Linux Foundation Open Printing WGSecretary - IEEE-ISTO Printer Working GroupCo-Chair - IEEE-ISTO PWG Internet Printing Protocol WGIETF Designated Expert - IPP & Printer MIBBlue Roof Music / High North Inchttp://sites.google.com/site/blueroofmusic <http://sites.google.com/site/blueroofmusic>http://sites.google.com/site/highnorthinc <http://sites.google.com/site/highnorthinc>mailto: blueroofmusic@gmail.com <blueroofmusic@gmail.com>(permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434*
- [Teep] Secure Channel definition for TEEP Use Cas… Ira McDonald
- Re: [Teep] Secure Channel definition for TEEP Use… yangpenglin