Re: [v6ops] LAN-side NTP in rfc7084bis?

Mark Smith <markzzzsmith@gmail.com> Wed, 20 March 2024 13:21 UTC

Return-Path: <markzzzsmith@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB00FC151090 for <v6ops@ietfa.amsl.com>; Wed, 20 Mar 2024 06:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level:
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jyEfHDWmy1Kx for <v6ops@ietfa.amsl.com>; Wed, 20 Mar 2024 06:21:06 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08851C14F711 for <v6ops@ietf.org>; Wed, 20 Mar 2024 06:21:05 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id 2adb3069b0e04-513e89d0816so4300272e87.0 for <v6ops@ietf.org>; Wed, 20 Mar 2024 06:21:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710940864; x=1711545664; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dKJXgf+F4x+fU0Asx2PWOmpUu1HSB7TygcKWk9W779s=; b=P1cVm56OgYJ4ml595fJhu5WaHrM+R5df84nRVvCl7agmkENnY2pLfGTRgQH45C0cpf HAggy68TYYgNNcGrAcmnQSKSTDByv4gQY3zM/y4QtH6YcgcLiNXnom3jliGjW9PaxtZy IMcjIV9l3GPGZh+OCx04syVVB/yb/j3TNzJcUxGQQpNyqAtQgQVkRi/KrKO+9a3U7ZsS eq40ChzVkUwLedD7XTqWLZaqxV6aBmjq43M07ilxGvuqBZPsLJDDTo7kJizqKQJ0CmkO BzN12dGNry/EXI6R/rZn9RnZxdmrG1s7XEwnaxs0/b5FwxDEM95ZsdwVTvHrJpfvZ/D+ QYNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710940864; x=1711545664; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dKJXgf+F4x+fU0Asx2PWOmpUu1HSB7TygcKWk9W779s=; b=JziyDtxGXdNhkFhOMW5knFnq6I1B/rOBk7NmCOQf5GX0WxujtJO9IYKTSg+oxMD4q1 q5mfTzO5Jd4HAYe0upB4G1njRE1qjcmJTjkGlXGeym0gF9oQe7xMwoLMqWvUJ5w8KqBF /L0cetSyS9jsaVpXsz+JAX2IxeNgcpOHJUWDVbG43RqmHtSlX/yV0vuc8yNkfYJQ1mJR Umn/WIVoEM155mHZPTLImyq9Hz9um37llK+fX7FmIOfsgCvJ/36OF3ih8A4AOB9d2O71 YJW+MW8KKY6yfaAy/0hFc/HCG/yqd31qcFReMSpGYX8NFPO2EBoYZl9POBGgKE9B6IsD /Aug==
X-Forwarded-Encrypted: i=1; AJvYcCUr2p7Nh6H5HzS9hb3HPuGrfWHNQtVG2AkuJj4zzGjHN2hoAaNyx+5gG8uBCozPGxEHt8Lr7P/donhvMIqulg==
X-Gm-Message-State: AOJu0YwswZqrkt70WOSXtOmXKnlQEzE/f/EvaC7Rr5Y6GkM/W5ZJsiGv F5h8YBJD7tX/iMDeJMy99kJZzIF+W726QNW/mCBnoFpkGMAzgKuyGd7BYXOYOjAE8MySoB07way SaIsFVY7DB/2Jjk31z47sOoo/aBw=
X-Google-Smtp-Source: AGHT+IF9w8yQtsNjh6WNF9oVx8qKOjaWrEnEx0LpuRWZMSkynTbLlNuOKaSlJ6ekUd8CDvG4skXBrUWAayapEFfuevs=
X-Received: by 2002:a05:6512:4025:b0:515:8d1c:bf09 with SMTP id br37-20020a056512402500b005158d1cbf09mr714315lfb.16.1710940863435; Wed, 20 Mar 2024 06:21:03 -0700 (PDT)
MIME-Version: 1.0
References: <7199173b-a473-4117-63b3-917687cb5766@gmail.com> <CAJgLMKu7hsRvgAaU_im8PJVOLqFcC89YZGVFRU8gxTtNFnwc8w@mail.gmail.com> <Zfqz_ZAIeqU-0iX3@Space.Net> <21B591DB-91EB-475B-9E63-415B703ED4B9@consulintel.es>
In-Reply-To: <21B591DB-91EB-475B-9E63-415B703ED4B9@consulintel.es>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 20 Mar 2024 23:20:53 +1000
Message-ID: <CAO42Z2zKyRV2bLZP2-8RNuq=JtvQQ-Yy9fOmZ34Dw-j2DQthSQ@mail.gmail.com>
To: "jordi.palet@consulintel.es" <jordi.palet=40consulintel.es@dmarc.ietf.org>
Cc: Gert Doering <gert@space.net>, IPv6 Operations <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000065a0000614177688"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/4gbEqXe-liHCwDmTSsRNKGu8ntw>
Subject: Re: [v6ops] LAN-side NTP in rfc7084bis?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2024 13:21:10 -0000

On Wed, 20 Mar 2024, 21:06 jordi.palet@consulintel.es, <jordi.palet=
40consulintel.es@dmarc.ietf.org> wrote:

> Yes, we should do that, not just for NTP.
>
> “Any protocol or service supported by the CE for IPv4 MUST be also
> supported for IPv6. The CE MAY support additional protocols or services
> even if not supported in IPv4"
>


Even more generally, I think a CE really should be a DHCPv6 relay for
options the upstream SP can provide, rather than being limited to what
DHCPv6 options the CE itself can support. LAN side stateful DHCPv6
addressing can be supported by handling IA_NA and IA_TA options locally.


IPv6 CE Device DHCPv6 Option Transparency
https://datatracker.ietf.org/doc/html/draft-smith-v6ops-ce-dhcpv6-transparency-00


Regards,
Mark.


>
>
> > El 20 mar 2024, a las 11:01, Gert Doering <gert@space.net> escribió:
> >
> > Hi,
> >
> > On Wed, Mar 20, 2024 at 11:07:17AM +1000, Timothy Winters wrote:
> >>> It occurred to me a bit late that a reasonable statement might be that
> >>> *if* a CE router supports NTP over IPv4 on the LAN side, then it MUST
> also
> >>> support it over IPv6; otherwise it can be a MAY.
> >>>
> >> That is a very good "late" thought.   The next revision, we'll take a
> stab
> >> at documenting that.
> >
> > I'd argue that this should be true for all 'non core' services offered
> > - like, "if the router offers file sharing services over IPv4, it MUST
> > also offer them over IPv6".  Or USB->LAN printer sharing, or...
> >
> > Not sure how to word that in a sufficiently generic way.
> >
> > Gert Doering
> >        -- NetMaster
> > --
> > have you enabled IPv6 on something today...?
> >
> > SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael
> Emmer,
> >                                           Ingo Lalla, Karin Schuler
> > Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
> > D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> > Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
>
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the exclusive use of
> the individual(s) named above and further non-explicilty authorized
> disclosure, copying, distribution or use of the contents of this
> information, even if partially, including attached files, is strictly
> prohibited and will be considered a criminal offense. If you are not the
> intended recipient be aware that any disclosure, copying, distribution or
> use of the contents of this information, even if partially, including
> attached files, is strictly prohibited, will be considered a criminal
> offense, so you must reply to the original sender to inform about this
> communication and delete it.
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>