Re: [Ntp] NTS Hackathon coordination

Christer Weinigel <christer@weinigel.se> Sat, 20 July 2019 13:55 UTC

Return-Path: <christer@weinigel.se>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B174E12008B for <ntp@ietfa.amsl.com>; Sat, 20 Jul 2019 06:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.916
X-Spam-Level:
X-Spam-Status: No, score=-0.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_TRY_3LD=0.001] autolearn=no 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 oq3LiQYkgAYy for <ntp@ietfa.amsl.com>; Sat, 20 Jul 2019 06:55:41 -0700 (PDT)
Received: from mail.weinigel.se (37-46-169-123.customers.ownit.se [37.46.169.123]) by ietfa.amsl.com (Postfix) with ESMTP id 0DBCB120052 for <ntp@ietf.org>; Sat, 20 Jul 2019 06:55:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by zoo.weinigel.se (Postfix) with ESMTP id 0E3ED1E0276; Sat, 20 Jul 2019 15:55:39 +0200 (CEST)
Received: from mail.weinigel.se ([127.0.0.1]) by localhost (mail.weinigel.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id acDF9PRMg0Fj; Sat, 20 Jul 2019 15:55:36 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by zoo.weinigel.se (Postfix) with ESMTP id 021E51E01AB; Sat, 20 Jul 2019 15:55:35 +0200 (CEST)
From: Christer Weinigel <christer@weinigel.se>
To: Martin Langer <mart.langer@ostfalia.de>, ntp@ietf.org
References: <20190322223210.1181540605C@ip-64-139-1-69.sjc.megapath.net> <746c447d-7d99-9bc5-0167-a3560d6bef03@ostfalia.de> <d580d78a-1058-3848-6024-8daa02e9e8f2@weinigel.se>
Message-ID: <545df323-65a5-a170-ae08-0f6e5fe941d7@weinigel.se>
Date: Sat, 20 Jul 2019 15:55:35 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1
MIME-Version: 1.0
In-Reply-To: <d580d78a-1058-3848-6024-8daa02e9e8f2@weinigel.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/A0PB9LGtbZfVxQQh6bfX1WKvFGY>
Subject: Re: [Ntp] NTS Hackathon coordination
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jul 2019 13:55:43 -0000

Hi everyone,

I've created a Slack channel for IETF-105 hackathon time-related stuff.

You ought to be able to join the channel using this link:

https://join.slack.com/t/ietf-105-time/shared_invite/enQtNjg5NDAyNDE0MTE1LTVhZDE3YzEzMTk1ZWYyNDAxZGFjZmM1OTE1ZTFiYmY4MGJlZGYyZDYyMThjNmQzOTk0MGE4N2FkZmU5MmFjNDM

   /Christer

On 2019-07-20 13:51, Christer Weinigel wrote:
> Hi all,
> 
> I just got back from vacation, but I will participate too.
> 
> I've set up my Python server on the same machine as before:
> 
> ntske: zoo.weinigel.se 4446
> 
> There's nothing really new though, I've fixed a crash bug in my server 
> (an exception that would stop the server if the client closed the TLS 
> socket before I could read from it).
> 
> When I was at the AIS hackathon in Uganda a few weeks ago we used slack 
> to communicate within the group and I think that worked out rather well. 
>   I'd suggest that we set up a slack channel for the NTP/NTS/time group 
> for this hackathon too.  Does anybody know how to do that?  Otherwise I 
> could give it a try.
> 
>    /Christer
> 
> On 2019-07-04 10:17, Martin Langer wrote:
>> Hello everybody.
>>
>> I just wanted to say that I will participate the next hackathon (remote).
>> We should note somewhere which IPs, port numbers, NTP-EF IDs and 
>> features (like IPv6 support, separated NTS-KE server, ...) each 
>> implementation expect.
>>
>> I can provide 3 time servers with different settings.
>>
>>
>> best regards,
>> Martin
>>
>>
>> Am 22.03.2019 um 23:32 schrieb Hal Murray:
>>> odonoghue@isoc.org said:
>>>>     For those participating, I’ll see you physically or virtually 
>>>> tomorrow.
>>>>     The room will open at 9:00 am CET. It will take us a little 
>>>> while to get
>>>>     started and get through the opening portions, so for the remote 
>>>> folks,
>>>>     please be patient with us.
>>> I assume somebody will find bugs/quirks in our code.  I'll be 
>>> available via
>>> email.  I'm in California.  I think that means you are starting at my
>>> midnight.  I'm a night owl, so we'll get some overlap.
>>>
>>> 2 more servers:
>>>    ntp1.glypnod.com - San Francisco
>>>    ntp2.glypnod.com - London
>>>
>>> The NTS-LE server is listening on port 123, both IPv4 and IPv6.
>>>
>>> I've seen cases where some NTP packets don't make it to London.  I 
>>> assume it's
>>> filtering leftover from the DDoS mess of a few years ago.  Normal NTP
>>> request/responses get through.  Longer requests with NTS extensions 
>>> don't get
>>> in to London if the source port is 123.
>>>
>>>
>>>
>>