IETF Logo Mail Archive

Re: [Ntp] Changing port 123

Watson Ladd <watson@cloudflare.com> Mon, 24 February 2020 20:20 UTC

Return-Path: <watson@cloudflare.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 A9C923A126B for <ntp@ietfa.amsl.com>; Mon, 24 Feb 2020 12:20:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 7FavnaDOOmh7 for <ntp@ietfa.amsl.com>; Mon, 24 Feb 2020 12:20:35 -0800 (PST)
Received: from mail-qv1-xf36.google.com (mail-qv1-xf36.google.com [IPv6:2607:f8b0:4864:20::f36]) (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 4DE533A126A for <ntp@ietf.org>; Mon, 24 Feb 2020 12:20:35 -0800 (PST)
Received: by mail-qv1-xf36.google.com with SMTP id p2so4700713qvo.10 for <ntp@ietf.org>; Mon, 24 Feb 2020 12:20:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xdy6/fQoJeMRKWf0Huzl2GggHHTyHeALYzHjDHTlE2Y=; b=WRMgVMPqg83/JoRgSJxIpEKbOMCGNwui+uQnXTwCLbe4/pTh8uRU22tQH9bOBMN2iw IT4uacDuvlIaBlqTZA8lmU8opVtbCbrB8n19UuxuH49upEfWrlgHJaJoOb3G9ppApIeU VrCNl/C6KQ5EfQbMi1mpHOm6g1MNPrctBolBo=
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=xdy6/fQoJeMRKWf0Huzl2GggHHTyHeALYzHjDHTlE2Y=; b=uPV7uSdxP1/GY3j5hc56SJ/Tv8Moq6E8OSXhx+2HOOUN9B7TYn8kFHHGayuvL0oeJh PtwDoibs2U+3uWLk4SxCq0AU0/+LlX9/FhSZRi7ofAxyB0Se43GQVXG2SdAGsZDcuDSv d3gCnqqCW7nPhvDjyYx8jHjebXtCzo/YGUIDJueiGREFnJ0TvbfZYyq8HJQcznDfAh+k 0v/nXLlmiuJDxm5W+V0g1qUHUsZbjxOyiCrieq3ewmRd7BOL656OwFNO+7RMVupwg+30 tdQ76rRG1QsGNtoVTwDFSvjz2947Ip42304bpm/sjJIrwK1v+5eKFRpaWgqClnC66A9d RXCA==
X-Gm-Message-State: APjAAAX+XlkKyq66U0AciNmiwteRcp+hoyQesXYQOu097AIZA86Cx2tz QqKv8say2jXQkvKcMuhsQv7jr1/uswiPsMcNg/jIlg==
X-Google-Smtp-Source: APXvYqz3FSO0PeAZYOp833pCqeMugxC98x6StPwr2raW8I1cPjwZUQlV1Ly7JRHLQB0fELTLwQO0Ta3oRl6L2IfAHXA=
X-Received: by 2002:ad4:446b:: with SMTP id s11mr45584443qvt.148.1582575634378; Mon, 24 Feb 2020 12:20:34 -0800 (PST)
MIME-Version: 1.0
References: <CAN2QdAEo-70coXwWtxbS=mdsH0WmFPDkTaUkAeJA=5oARQGjOA@mail.gmail.com> <CAMGpriUpH2ySh8n4EkpbZvgJ4vtcDV0bMxR1LdmYiBYys_JVKQ@mail.gmail.com> <545ddaec-b720-caa6-c7db-f6e41b2b961e@nwtime.org>
In-Reply-To: <545ddaec-b720-caa6-c7db-f6e41b2b961e@nwtime.org>
From: Watson Ladd <watson@cloudflare.com>
Date: Mon, 24 Feb 2020 12:20:23 -0800
Message-ID: <CAN2QdAGrGJ7VRk+cuugtpzTbcb5Gw_99EkT9-04f9E9ZUo1cMw@mail.gmail.com>
To: Harlan Stenn <stenn@nwtime.org>
Cc: Erik Kline <ek.ietf@gmail.com>, Watson Ladd <watson=40cloudflare.com@dmarc.ietf.org>, NTP WG <ntp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/Moc4kcyDJBj2wZVmhP2Zn2L3sZ4>
Subject: Re: [Ntp] Changing port 123
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: Mon, 24 Feb 2020 20:20:37 -0000

On Mon, Feb 24, 2020 at 12:19 PM Harlan Stenn <stenn@nwtime.org> wrote:
>
> The NTP Project remains completely opposed to using TCP 123 for NTS-KE.

Sorry for miswriting in my original email: this is an alternate UDP
port to pass NTS protected NTP packets over, not TCP.

What is the use of TCP 123 going to be?
>
> On 2/24/2020 11:18 AM, Erik Kline wrote:
> > On Mon, Feb 24, 2020 at 9:09 AM Watson Ladd
> > <watson=40cloudflare.com@dmarc.ietf.org
> > <mailto:40cloudflare.com@dmarc.ietf.org>> wrote:
> >
> >     Unfortunately it seems that port 123 cannot be extended in any way,
> >     shape, or form.
> >
> >     I'd like to recommend that operators advertise an alternate port for
> >     NTS via the NTS-KE port advertisement. Given the extent of the
> >     problems reported I don't think port 123 will ever work, unless we get
> >     network operators to not do length based blocking (very unlikely).
> >
> >
> > A new port will probably require firewalls to be explicitly opened for it.
> >
> > _______________________________________________
> > ntp mailing list
> > ntp@ietf.org
> > https://www.ietf.org/mailman/listinfo/ntp
> >
>
> --
> Harlan Stenn <stenn@nwtime.org>
> http://networktimefoundation.org - be a member!
>
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp

v2.23.0 | Report a Bug | By Email