IETF Logo Mail Archive

Re: [Ntp] NTS Hackathon coordination

Daniel Franke <dfoxfranke@gmail.com> Sat, 23 March 2019 11:38 UTC

Return-Path: <dfoxfranke@gmail.com>
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 513DF130E8B for <ntp@ietfa.amsl.com>; Sat, 23 Mar 2019 04:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VGI-SV-xbvQv for <ntp@ietfa.amsl.com>; Sat, 23 Mar 2019 04:38:09 -0700 (PDT)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC35B130DE7 for <ntp@ietf.org>; Sat, 23 Mar 2019 04:38:08 -0700 (PDT)
Received: by mail-qk1-x72f.google.com with SMTP id s81so2729701qke.13 for <ntp@ietf.org>; Sat, 23 Mar 2019 04:38:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VsWslN83QX3Vj53b7FDMAMPl+DGLJPKtx0U+AEZlr/U=; b=tCOQMw9LtMsUO6VmkYiuJlIkV7k08+YuLU/2sTfheISdd1Y4UuOcbB9tiHLUzZUJuz djuqGUwi7EEi0G+BUgEyhVbN4zttNwacL8PVOIxL299IACy8hpzQsNv/UJNMt1QnG14l XEKwCyNomaZ+aDpQD8f41JwFVe93xijiFTM1TlpZk/H4PTHT68x1SNb29bgTRgnlMBRO ofiTo59HT7b+19k3M6NEteFVr+56Fq3oYEW1zxbSyG5jZLrCt2aSCQNLoDwT6fFE4LxH x6EDg5efaA9wK+zWtOiENfhVuxNugAAzHBTezRxFLe77E8/DWI8mxVXw5mydyQWflF1E jdiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VsWslN83QX3Vj53b7FDMAMPl+DGLJPKtx0U+AEZlr/U=; b=QBl5Zf228oP/ZzmudR4iPwGlVhObve8O7u0ZKY8zcKsb6JWhqhJghtVEmI3NxoG6mB Qu4vK64B1K+iFnBpmgo9fn/kKprIqACZNwIkhyXB8RLS1rPp9lbX5XEj/+RtORVjfxcL nAfL8AtqiVm3D9IYDBVVU3WNWf4MDxx4UlPmcFk+rW/oG/vkB6TzI+qJZgoH+ijYPEhO H05ct52e++vwRvKYoVvgeVRcdKBftdvdOiarVBtzAUI+jD6c+auYmNt3yccaLu+41wUn qCQH33TxbykxDrgDREWoeVOZeM2PFvMgkeqZdpEUWB0cBsXcHhnp+k6O+pQ8748UBRB+ Kj1g==
X-Gm-Message-State: APjAAAVyD7hUFGvqg8Evs3QAQX7AFObx4aM8lFw2i3qBIxAvvjpzFeQC KIwUExngv0I5qik1xuK5dgbgDlk/wD03QtenmFyXUA==
X-Google-Smtp-Source: APXvYqxZYEPJBypBevE+bC9eNMYGox9uu4ZI5AutwqIid46Zu/9AsVoahYGkn+XTeXtZRApsu0zGPw4pUMTCAV2Zw8Q=
X-Received: by 2002:a37:68cc:: with SMTP id d195mr11353740qkc.131.1553341088073; Sat, 23 Mar 2019 04:38:08 -0700 (PDT)
MIME-Version: 1.0
References: <20190322223210.1181540605C@ip-64-139-1-69.sjc.megapath.net>
In-Reply-To: <20190322223210.1181540605C@ip-64-139-1-69.sjc.megapath.net>
From: Daniel Franke <dfoxfranke@gmail.com>
Date: Sat, 23 Mar 2019 12:37:55 +0100
Message-ID: <CAJm83bCkJ+yOe_P=ZefZS8ve1sNft7n6fLK3sRnLfBdME2kwhg@mail.gmail.com>
To: Hal Murray <hmurray@megapathdsl.net>
Cc: ntp@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c50dc40584c16728"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/WKUaadUjFYiP_VdbTmWj_WGoSLQ>
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, 23 Mar 2019 11:38:11 -0000

We need to get the word out to network operators to stop filtering in this
manner (and that if they really must filter, they should limit it to mode 7
packets). As a (hopefully) temporary measure, implementers should make it
easy for users to serve NTP on an alternate port in addition to 123, and
use Port Negotiation in NTS-KE to advertise it. There should be no need for
any spec changes or IANA actions to accommodate this behavior; since we
have the negotiation mechanism, there is no need for a registered port and
administrators can pick anything not in use by another service.

On Fri, Mar 22, 2019, 23:32 Hal Murray <hmurray@megapathdsl.net> wrote:

>
> 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.
>
>
>
> --
> These are my opinions.  I hate spam.
>
>
>
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp
>

v2.23.0 | Report a Bug | By Email