Re: [dispatch] Secure Credential Transfer Charter & BoF
John C Klensin <john-ietf@jck.com> Thu, 03 February 2022 04:44 UTC
Return-Path: <john-ietf@jck.com>
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 F21AA3A196F; Wed, 2 Feb 2022 20:44:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 K8GxTOCIpNTd; Wed, 2 Feb 2022 20:44:27 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 830353A1968; Wed, 2 Feb 2022 20:44:26 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1nFTyk-000GmT-4C; Wed, 02 Feb 2022 23:44:18 -0500
Date: Wed, 02 Feb 2022 23:44:11 -0500
From: John C Klensin <john-ietf@jck.com>
To: Roman Danyliw <rdd@cert.org>, Eric Rescorla <ekr@rtfm.com>
cc: Matthew Byington <mbyington@apple.com>, DISPATCH <dispatch@ietf.org>, Security ADs <sec-ads@ietf.org>, Francesca Palombini <francesca.palombini@ericsson.com>
Message-ID: <66FFFE879E3D7B5D39B13BF4@PSB>
In-Reply-To: <BN2P110MB11078D70177B4F36B6D2CAB4DC289@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
References: <FA7592B5-D8D4-413D-97B4-1044F29FC205@apple.com> <CABcZeBNzqSnd5eGwZOui980=BfFfywLRO6asm=BtxZEgAFnWMA@mail.gmail.com> <A3547720-3AD2-409D-8FC8-605D09D4941D@apple.com> <2531793BFFD2289EC9ED5174@PSB> <D11CC958-777D-4951-9364-7F46D334E71F@apple.com> <BF7D90A8618BDA99A9984396@PSB> <CABcZeBPN_SqZhZqKG+h2dYAjJ=t=r9qFCuYj1uBmebWFfUgp_w@mail.gmail.com> <B102508D45A78A6B858E902D@PSB> <CABcZeBOvoaM5FHRsKHHRYs+L97KgNZVnD1tgTf3Thp5V1JH+yw@mail.gmail.com> <BN2P110MB11078D70177B4F36B6D2CAB4DC289@BN2P110MB1107.NAMP110.PRO D.OUTLOOK.COM>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/ZROnRYVYOxMjz2g0DXy3wI2udYM>
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: Thu, 03 Feb 2022 04:44:33 -0000
Roman, Thanks _very_ much. That completely addresses my concerns. john --On Thursday, February 3, 2022 02:25 +0000 Roman Danyliw <rdd@cert.org> wrote: > Hi! > > From: Eric Rescorla <ekr@rtfm.com> > Sent: Wednesday, February 2, 2022 8:58 PM > To: John C Klensin <john-ietf@jck.com> > Cc: Matthew Byington <mbyington@apple.com>; DISPATCH > <dispatch@ietf.org>; Security ADs <sec-ads@ietf.org>; > Francesca Palombini <francesca.palombini@ericsson.com> > Subject: Re: [dispatch] Secure Credential Transfer Charter & > BoF > > > > On Wed, Feb 2, 2022 at 3:54 PM John C Klensin > <john-ietf@jck.com<mailto:john-ietf@jck.com>> wrote: > > I still think that it would be useful to discuss this further > at the BOF so everyone who needs it gets a better > understanding of where the issues and boundaries lie and to, > at least, get agreement from the SEC ADs to help Francesca > keep an eye on developments of a WG and any document > processing. > > [Roman] We (SEC ADs) are in lock step with ART (Francesca) to > ensure that this work gets the appropriate consideration > during this formative times, and should it end up as a WG. > The BoF will help us tease out a number of things, to include > an appropriate home. If it advances, we have experimented > with different leadership models for WGs. For example, among > the recently chartered WGs, we have various AD swaps (e.g., > OHAI in SEC area but with an ART AD; SCIM in ART but with a > SEC AD). > > Regards, > Roman > > > > thanks, > john > > > --On Wednesday, February 2, 2022 14:32 -0800 Eric Rescorla > <ekr@rtfm.com<mailto:ekr@rtfm.com>> wrote: > >> On Wed, Feb 2, 2022 at 2:14 PM John C Klensin >> <john-ietf@jck.com<mailto:john-ietf@jck.com>> wrote: >> >>> Matthew, >>> >>> Thanks for the response. For me, it makes perfectly good >>> sense. And, having participated in the DISPATCH discussion, I >>> (and perhaps others) didn't adequately understand how much >>> the work would depend on issues and topics in the Security >>> area.. or we were not paying enough attention. I am actually >>> surprised the question was not raised by ekr or one of the >>> others who spends >>> >> much more time on security issues than I do. >>> >> >> Hearing my name... >> >> This actually was discussed at the meeting [0]. See the end >> where Richard Barnes says: >> "don't think it belongs in sec - the interesting questions >> are around the broader architecture. The details of the crypto >> needs to be arranged properly, but we can bring in exepertise. >> The work belongs in ART not SEC." >> >> I roughly agree with this. The crypto is fairly >> straightforward but the architecture for moving the data >> around needs serious consideration.I don't think it would be a >> disaster in SEC, but based on experience with, for instance >> ACME, it would need a lot of apps input to avoid screwing that >> side up. >> >> -Ekr >
- [dispatch] Secure Credential Transfer Charter & B… Matthew Byington
- Re: [dispatch] Secure Credential Transfer Charter… Eric Rescorla
- Re: [dispatch] Secure Credential Transfer Charter… Matthew Byington
- Re: [dispatch] Secure Credential Transfer Charter… Mark Nottingham
- Re: [dispatch] Secure Credential Transfer Charter… Eric Rescorla
- Re: [dispatch] Secure Credential Transfer Charter… Richard Barnes
- Re: [dispatch] Secure Credential Transfer Charter… Lucas Pardue
- Re: [dispatch] Secure Credential Transfer Charter… Eric Rescorla
- Re: [dispatch] Secure Credential Transfer Charter… Matthew Byington
- Re: [dispatch] Secure Credential Transfer Charter… Matthew Byington
- Re: [dispatch] Secure Credential Transfer Charter… John C Klensin
- Re: [dispatch] Secure Credential Transfer Charter… Matthew Byington
- Re: [dispatch] Secure Credential Transfer Charter… John C Klensin
- Re: [dispatch] Secure Credential Transfer Charter… Eric Rescorla
- Re: [dispatch] Secure Credential Transfer Charter… John C Klensin
- Re: [dispatch] Secure Credential Transfer Charter… Martin Thomson
- Re: [dispatch] Secure Credential Transfer Charter… Eric Rescorla
- Re: [dispatch] Secure Credential Transfer Charter… Roman Danyliw
- Re: [dispatch] Secure Credential Transfer Charter… John C Klensin
- Re: [dispatch] Secure Credential Transfer Charter… worley