Re: [dispatch] Secure Credential Transfer Charter & BoF
John C Klensin <john-ietf@jck.com> Wed, 02 February 2022 22:14 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 48F563A1086; Wed, 2 Feb 2022 14:14:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 YvD3tBJIuZrS; Wed, 2 Feb 2022 14:14:42 -0800 (PST)
Received: from bsa2.jck.com (bsa2.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 D39533A1E0D; Wed, 2 Feb 2022 14:14:39 -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 1nFNtc-000FtM-A7; Wed, 02 Feb 2022 17:14:36 -0500
Date: Wed, 02 Feb 2022 17:14:30 -0500
From: John C Klensin <john-ietf@jck.com>
To: Matthew Byington <mbyington@apple.com>
cc: Eric Rescorla <ekr@rtfm.com>, DISPATCH <dispatch@ietf.org>, Security ADs <sec-ads@ietf.org>, Francesca Palombini <francesca.palombini@ericsson.com>
Message-ID: <BF7D90A8618BDA99A9984396@PSB>
In-Reply-To: <D11CC958-777D-4951-9364-7F46D334E71F@apple.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>
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/8fns3yFP1OCrbuCWxnQOSb-ACjc>
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: Wed, 02 Feb 2022 22:14:47 -0000
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. I think discussing this at the BOF would be fine but would strongly encourage Francesca and the Security ADs to have a conversation in advance, either to settle the issue and explain it to those of us who have questions or to make the BOF, even if informally, a joint ART-Security one to increase the odds of the right people being part of that discussion. >From experience, the thing you definitely do not want is to get a document finished and into IETF Last Call and only then have people in the Security Area complain about things you have left out or to which you have paid insufficient attention. The earlier such possibilities are identified and dealt with the better. thanks, john --On Wednesday, February 2, 2022 13:31 -0800 Matthew Byington <mbyington@apple.com> wrote: > Hi John, > > Thank you for your response. I am adding Francesca here to > this thread. > > When I first presented at Dispatch last year they helped guide > me and the other proponents to the right place. > > I don't have prior IETF experience myself - I certainly > place a lot of trust in the existing community for where this > should live. > > I should say, I'm not directly opposed to it living in the > Security Area as long as the ADs in general agree. > > Security does play a large role in our problem statement and > considerations, to your point. > > Perhaps this is something we could discuss during the BoF? > > Matt > >> On Jan 29, 2022, at 10:13 PM, John C Klensin >> <john-ietf@jck.com> wrote: >> >> Hi. >> >> I've read the thread to date but it seems more appropriate to >> respond to this message since this is not about the timing >> issue raised by others. >> >> Having read the charter and other materials, including >> skimming the slides, I would like to better understand why >> this is being proposed in ART rather than in the Security >> Area. The expertise is there (and not in ART except by happy >> accident) on most of the "primary goals" and requirements in >> the charter. It is clear why an application or application >> protocol would want to use the credential-sharing protocol >> being proposed, but it does not seem to me that qualifies it >> as ART work (or, if it does, why a significant amount of >> other work in the Security Area does not belong in ART). >> >> Just wondering... >> john >> >> >> --On Tuesday, January 25, 2022 17:00 -0800 Matthew Byington >> <mbyington=40apple.com@dmarc.ietf.org >> <mailto:mbyington=40apple.com@dmarc.ietf.org>> wrote: >> >>> Hi Eric, >>> >>> My understanding is that the BoF will be handled virtually >>> (not in-person). It has also been scheduled outside of the >>> normal IETF week. >>> >>> The BoF is working-group forming, yes. >>> >>> Matt >>> >>>> On Jan 25, 2022, at 11:38 AM, Eric Rescorla <ekr@rtfm.com> >>>> wrote: >>>> >>>> Can you clarify what the status of a "virtual BoF" is, here? >>>> I.e., is this in lieu of an actual BoF at the next IETF? Is >>>> this WG forming? >>>> >>>> -Ekr >>>> >>>> >>>> On Tue, Jan 25, 2022 at 11:36 AM Matthew Byington >>>> <mbyington=40apple.com@dmarc.ietf.org >>>> <mailto:40apple.com@dmarc.ietf.org >>>> <mailto:40apple.com@dmarc.ietf.org>>> wrote: Hi there, >>>> >>>> I wanted to send an email out communicating an upcoming >>>> virtual BoF meeting scheduled for Thursday February 10th. >>>> >>>> This is a follow-on to the initial presentation at IETF week >>>> 112 given last year. >>>> >>>> I am posting the information below to a few different IETF >>>> mailing lists, so apologies if you receive duplicate >>>> notifications on the subject. >>>> >>>> A big "thank you" to Francesca for helping us to get this >>>> scheduled and organized. >>>> >>>> Latest draft: >>>> https://www.ietf.org/archive/id/draft-secure-credential-tr >>>> an >>>> <https://www.ietf.org/archive/id/draft-secure-credential-t >>>> ran> sfer-03.html >>>> <https://www.ietf.org/archive/id/draft-secure-credential-t >>>> ra >>>> <https://www.ietf.org/archive/id/draft-secure-credential-t >>>> ra> nsfer-03.html> >>>> >>>> Charter: >>>> https://github.com/dimmyvi/secure-credential-transfer/blob >>>> /m >>>> <https://github.com/dimmyvi/secure-credential-transfer/blo >>>> b/m> ain/charter.md >>>> <https://github.com/dimmyvi/secure-credential-transfer/blo >>>> b/ >>>> <https://github.com/dimmyvi/secure-credential-transfer/blo >>>> b/> main/charter.md> >>>> >>>> BoF Request: >>>> https://datatracker.ietf.org/doc/bofreq-secure-credential- >>>> tr >>>> <https://datatracker.ietf.org/doc/bofreq-secure-credential >>>> -tr> ansfer-bof-request/ >>>> <https://datatracker.ietf.org/doc/bofreq-secure-credential >>>> -t >>>> <https://datatracker.ietf.org/doc/bofreq-secure-credential >>>> -t> ransfer-bof-request/> >>>> >>>> Virtual BoF (Francesca is finalizing this schedule still, >>>> but this is the proposed date and time): Thursday February >>>> 10th 17:00-19:00 UTC >>>> (https://www.worldtimebuddy.com/?qm=1&lid=2673730,5,8,100& >>>> h= >>>> <https://www.worldtimebuddy.com/?qm=1&lid=2673730,5,8,100& >>>> h=> 2673730&date=2022-2-10&sln=18-20&hf=1 >>>> <https://www.worldtimebuddy.com/?qm=1&lid=2673730,5,8,100& >>>> h= >>>> <https://www.worldtimebuddy.com/?qm=1&lid=2673730,5,8,100& >>>> h=> 2673730&date=2022-2-10&sln=18-20&hf=1>) >>>> >>>> Mailing list: >>>> https://www.ietf.org/mailman/listinfo/secret >>>> <https://www.ietf.org/mailman/listinfo/secret> >>>> <https://www.ietf.org/mailman/listinfo/secret >>>> <https://www.ietf.org/mailman/listinfo/secret>> >>>> >>>> Thanks, >>>> Matt >>>> _______________________________________________ >>>> dispatch mailing list >>>> dispatch@ietf.org <mailto:dispatch@ietf.org> >>>> <mailto:dispatch@ietf.org <mailto:dispatch@ietf.org>> >>>> https://www.ietf.org/mailman/listinfo/dispatch >>>> <https://www.ietf.org/mailman/listinfo/dispatch> >>>> <https://www.ietf.org/mailman/listinfo/dispatch >>>> <https://www.ietf.org/mailman/listinfo/dispatch>> >
- [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