[Ntp] Re: [dispatch] Re: New Individual Draft: draft-helmprotocol-tttps-00

["Heime.Jorgen" <[e-mail]>]

Tim,

Currently ttttps:// draft is updated to 02.

https://datatracker.ietf.org/doc/draft-helmprotocol-tttps/02/

Now ttttps:// is integrated into the Roughtime chain to protect against timestamp manipulation.

As per your advice, I’ve cc’d the NTP and sec-dispatch mailing lists to kick off the discussion.

Also, I’m looking for more contributors and experts to join this effort. If you know anyone who might be interested in co-authoring or reviewing this, I’d greatly appreciate your recommendations.

-Heime

-------- Original Message --------
On Friday, 04/03/26 at 14:35 Tim Bray <[e-mail]> wrote:

> I would add that in my experience most of the really thorough and high quality IETF discussions happen by email. So, I would encourage you, once you have the rest of the documentation in order, to revise your Internet Draft with the appropriate references and see if you can get a discussion going on one of the mailing lists. Unlike Dispatch, mailing-list discussions have no time limits.
>
> Such a discussion might get the attention of whatever subset of IETF people are interested in the problem area. This would probably also improve the quality of the discussion at a subsequent Dispatch session. Dispatch discussions tend not to be “is this good” but rather “what’s the next step in dealing with this” and (very important) “who would commit to work on this”. The chances of having people willing to work on your draft would obviously be improved by prior discussion. -Tim
>
> On Thu, Apr 2, 2026, 10:14 p.m. Jim Fenton <[e-mail]> wrote:
>
>> On 2 Apr 2026, at 5:00, Heime.Jorgen wrote:
>>
>>> I look forward to seeing the "correct process" facilitate a rigorous technical session in July.
>>
>> In order to set expectations for the Dispatch session at IETF 126, I’d like to point out that the purpose of the session is to very briefly summarize the proposal (internet draft) being dispatched and solicit input on whether this is appropriate for IETF, and if so how best to approach it, e.g., have a BOF session, create a mailing list for further discussion, or direct it to a relevant existing working group.
>>
>> Each topic at Dispatch is normally allocated 10 minutes: 5 minutes for presentation and 5 minutes for questions and comments from participants. Accordingly, you should not expect a rigorous technical discussion in the Dispatch session.
>>
>> -Jim
>>
>> _______________________________________________
>> dispatch mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]