Re: [Secdispatch] [EXTERNAL] Re: IETF117 - Call for topics

["Salz, Rich" <[e-mail]>]

For this case, I'd recommend focusing on the problem more than having an idea of where it should go (i.e., which working group)

On 6/16/23, 9:02 AM, "Mike Ounsworth" <Mike.Ounsworth=[e-mail] <mailto:[e-mail]>> wrote:


Hey David. Welcome!


Yeah, SecDispatch is explicitly about "Where should we home this work within the Sec area?" and not about the content.


A SecDispatch presentation typically has the flow "Here's this draft. It relates to the following technologies and working groups. My proposal is that it get dispatched to WG X", and then a bunch of discussion happens, then you are given a direction for where to take your work next.


SecDispatch has the general process outlined here: https://urldefense.com/v3/__https://datatracker.ietf.org/wg/secdispatch/about/__;!!GjvTz_vk!QgJIVdklyAWilIhJDV03eJ3B96ExklE7M9s2_7k_Frp3CzxShaEpPaV8PlZT0-97vR_EmYSOuRLCht0vIHisYZf-Q_Zx$ <https://urldefense.com/v3/__https://datatracker.ietf.org/wg/secdispatch/about/__;!!GjvTz_vk!QgJIVdklyAWilIhJDV03eJ3B96ExklE7M9s2_7k_Frp3CzxShaEpPaV8PlZT0-97vR_EmYSOuRLCht0vIHisYZf-Q_Zx$> 
The goal of a SecDispatch presentation is to arrive at consensus for proceeding with one of the 7 bulleted options.


---
Mike Ounsworth


-----Original Message-----
From: Secdispatch <[e-mail] <mailto:[e-mail]>> On Behalf Of David Woodhouse
Sent: Friday, June 16, 2023 7:48 AM
To: Rifaat Shekh-Yusef <[e-mail] <mailto:[e-mail]>>
Cc: secdispatch <[e-mail] <mailto:[e-mail]>>
Subject: [EXTERNAL] Re: [Secdispatch] IETF117 - Call for topics


WARNING: This email originated outside of Entrust.
DO NOT CLICK links or attachments unless you trust the sender and know the content is safe.


______________________________________________________________________
On Fri, 2023-06-16 at 08:24 -0400, Rifaat Shekh-Yusef wrote:
> Hi David,
>
> We will add this to the list of topics to discuss. You will have 15
> minutes to present and get feedback from the WG.


Thank you. I've *absolutely* no idea what I'm doing here; apologies for the cluelessness. Is this to present the case for the mere existence of my proposal, to decide how or whether to proceed with it at all — rather than focusing on the technical minutiæ of what's in the draft itself?


If you give me a platform, I can rant for *hours* about how awful it all is, and how hard it is for users just to use the key+cert that their organisation issued to them with various applications. And how the crypto libraries seem to go out of their way to make it *hard* for applications to do the right thing, and how it takes literally
*thousands* of lines of code in the application just to make it work...
:)


I will need to present remotely if that's OK. I stand a better chance of getting to Prague in November if that makes more sense?
Any email and files/attachments transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.
_______________________________________________
Secdispatch mailing list
[e-mail] <mailto:[e-mail]>
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/secdispatch__;!!GjvTz_vk!QgJIVdklyAWilIhJDV03eJ3B96ExklE7M9s2_7k_Frp3CzxShaEpPaV8PlZT0-97vR_EmYSOuRLCht0vIHisYXnMqqhk$ <https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/secdispatch__;!!GjvTz_vk!QgJIVdklyAWilIhJDV03eJ3B96ExklE7M9s2_7k_Frp3CzxShaEpPaV8PlZT0-97vR_EmYSOuRLCht0vIHisYXnMqqhk$>