Re: [dispatch] Secure Credential Transfer Charter & BoF

worley@ariadne.com Sun, 30 January 2022 21:36 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C55533A083B for <dispatch@ietfa.amsl.com>; Sun, 30 Jan 2022 13:36:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.983
X-Spam-Level:
X-Spam-Status: No, score=-0.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 rlWoO-z7EjoR for <dispatch@ietfa.amsl.com>; Sun, 30 Jan 2022 13:36:37 -0800 (PST)
Received: from resqmta-h1p-028596.sys.comcast.net (resqmta-h1p-028596.sys.comcast.net [IPv6:2001:558:fd02:2446::4]) (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 8E58B3A0839 for <dispatch@ietf.org>; Sun, 30 Jan 2022 13:36:37 -0800 (PST)
Received: from resomta-h1p-027913.sys.comcast.net ([96.102.179.200]) by resqmta-h1p-028596.sys.comcast.net with ESMTP id EExqnEtvQYLxoEHsBnTFDT; Sun, 30 Jan 2022 21:36:35 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1643578595; bh=OL/krJqwrrHWUOdEdsqTKWVFTYB0yYoOO1z0HOT3YvE=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=ZPmmf9PqJAEYD4PYV70I5xZc0NyRuwhTjKwtT5E5Cx0BOmsm/2A327VXZvoSL8ZMg TPWf4NJT4Gn2hPIk7E0DkJDcSeNfZ/9qNoqgpybQX7y3JDnjl8UpEipqATMbo42fhF k5jJ0ZRFlS1V+JAP+jHmT+iFtXILCDwnfgAEirWMtc8puQ+tiAZh30D/XRssbHUCrD p6fVcXrJRvxqXON8z54hvzwEq0LLfIfyZ/7JlpFLoBEAGwwqURH2VukJbtxqsOG5tU qDYRTtH92Gwm1liPULtEGIViCyO0S777M8DnW45/FBp39HGKxMsiPWNhV1mqS5j4oG YQL8QmVQXRAfg==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::7430]) by resomta-h1p-027913.sys.comcast.net with ESMTPA id EHs8ne3qZvdSFEHsAnIomq; Sun, 30 Jan 2022 21:36:35 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 20ULaWkD1075944 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for <dispatch@ietf.org>; Sun, 30 Jan 2022 16:36:32 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 20ULaWUu1075941; Sun, 30 Jan 2022 16:36:32 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: dispatch@ietf.org
In-Reply-To: <FA7592B5-D8D4-413D-97B4-1044F29FC205@apple.com> (mbyington=40apple.com@dmarc.ietf.org)
Sender: worley@ariadne.com
Date: Sun, 30 Jan 2022 16:36:31 -0500
Message-ID: <877dagaotc.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/0QhnasCuJF0HNUC3dpTlNqxd4Mc>
Subject: Re: [dispatch] Secure Credential Transfer Charter & BoF
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jan 2022 21:36:42 -0000

And so that we can possibly lure in people who we haven't motivated to
think about this, I copy this from the BoF request so y'all can skim it
with minimal effort:

    The goal is to allow users with secure credentials on their mobile
    devices to be able to shares entitlements that these credentials
    grant to other users.

    This would be achieved by defining and standardizing a protocol that
    will facilitate such credential transfers from individual to
    individual. The protocol will leverage a "relay server" to transfer
    data from sender to recipient. The scope of the transfer is limited
    to a single origin device and a single destination device. This
    system does not exist today in a standards-based, cross-platform and
    cross-channel capacity.

    The goal of this BoF is to answer some of the questions that came up
    during the Dispatch meeting (such as, why can't these credentials
    simply be lifted and cloned and then sent to the recipient?). We
    also want to provide additional detail into the applicable use
    cases, and some of the security and privacy requirements for the
    solution. The ultimate goal is to form a WG to discuss the
    initiative in an ongoing capacity.

Dale