[v6ops] Re: Call for Adoption: draft-buraglio-deprecate7050

Jen Linkova <furry13@gmail.com> Thu, 12 December 2024 12:40 UTC

Return-Path: <furry13@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 47DA4C16940E; Thu, 12 Dec 2024 04:40:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.857
X-Spam-Level:
X-Spam-Status: No, score=-1.857 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 lorjbUAWHiZx; Thu, 12 Dec 2024 04:39:57 -0800 (PST)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 290F6C169439; Thu, 12 Dec 2024 04:39:57 -0800 (PST)
Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-30229d5b1caso4564391fa.2; Thu, 12 Dec 2024 04:39:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734007195; x=1734611995; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=WyxbAsyC1SbnN/I8qVoFPW9/oHUzcdbN9JIpmTgN/pk=; b=Zu/PJeCMB+JeSpLqdT7wemlwVkYNHCqIUA76qQTsgs1kE0XcVxLXGe/ge+KPux2PkW naAUGm52C5vCFpTtlDwushETDWLebGXa2DQwCj/3340TGE+S8UevbVYxqrKXT5Dj+47V whlIgpy7VTUEL5u7MM1UC1fK/+od0tPd5qI+tPCXNIIjRub+Ms8pJZ2Br0z6D4q+AetA yJC+wTp4cB6mflaszSXlAmPrsiL/HL/ECOfqRDA+p3aAy+m80ujd0f2+lghgeA1xGVJI ReuojbWQ5sD/WNOSJ90eWIYD1qrkeUoQGKxsAkKaeY3SSRXkBX24EUn6SuZr95O/2Fp8 teQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734007195; x=1734611995; h=content-transfer-encoding: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=WyxbAsyC1SbnN/I8qVoFPW9/oHUzcdbN9JIpmTgN/pk=; b=IhaQIHqs7A8zWI68Eiff9H0kH+U9NumJHadTMJWhK0rIxWC3IkFGIZMd2Q7DFUDKGW /ZZcnnqHbGPmtgBS6qVpmQNvJ54MBzSdP6mqSd7ODY1LspY4hXQm0A8KrRjwY5JY4mi9 PVkKeJWUnf6VNVowtEcLmnWA0ulGuYpLT5s9tsd9Y7/ly49nvtnlDOdIvpYipU42yLb7 yOUU/TVzRhCRsXgy95BrrUdMWdrr/e9Hmmw1QryHHOApVJO0CBuVyXUAE9NuNnlzoxTl JwPOsVRyJputGAH10HkxlNKaCYUU1gWd6T3Rb+GGCQCJ9TOBrxKz5Iam2YqlFhZXYirz Vyrg==
X-Forwarded-Encrypted: i=1; AJvYcCUfIE39+2ZoGaCrcBp+JiVd5d0BZFH/hnSPLYsaw2wZGIk+qe5pYwwy/gpNXz75LT7POoZRsg==@ietf.org
X-Gm-Message-State: AOJu0YxGZq1vR9VrJ+1n1lSC0E12WaSoqYd9mBhmB86Jpo8WIHALWBJL 5alpfY9+hKtO0VZB5Dbfcr1Tqrv0vmezpKLlNyeYDIwIB8Nx84hnh82WcvC9F61Hp5Dg7n5pThK WQubgee8LDZzJwv2omZn/d/qCoTkx3NCV
X-Gm-Gg: ASbGncttS9cK9sLOPT/MZtYDZpCYhsW1HxaxSL5ymextvdqWH1zErdN1IzSVN1h0U3A JjWxca71DLdZYByelx4Jgfblkz9EGtUtC/SUt88+rXXWkOa7l3xYNBypc+YCstR9LPOWjI1+g
X-Google-Smtp-Source: AGHT+IFYLl3VULBsN3MjqDKSHexcMJOCjg2q23Gpk/DrNp5rSNCRogn1yfDMSy0v8SnL08QmAvxnphbXlEhNovZLWMw=
X-Received: by 2002:a05:651c:b22:b0:302:360e:a153 with SMTP id 38308e7fff4ca-30251e897cfmr98391fa.36.1734007195108; Thu, 12 Dec 2024 04:39:55 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+H7tRy6APmc4USJcGOB_MdgmzPk1H48KKX8RE4DbS4Ctg@mail.gmail.com> <CADyWQ+GW-bm=31AAU8HD-d4cJoJbhW4XfG-cCdLfVCWmWO83Tw@mail.gmail.com> <CADyWQ+G8JE_ZHpmrRdqVePA1W-jRS7YNYwK1EBp4AxvubAEyaA@mail.gmail.com> <CACMsEX8VNpOOp3uZ73Zu2NSavgf9mkcW8xq_dHXKqrrOPCA8ug@mail.gmail.com> <CAKD1Yr0FxCzfYq8OP1Rv+ZMZ41PmDDJqNft3Lohcb3qhTtBubg@mail.gmail.com> <CAFU7BAQBeK_Lqf7vjK5DpM_p_WtLZNNBfevoCV5cS24uukiM_w@mail.gmail.com> <32EBF1C3-9200-48D4-B213-3EB2071EBA90@cisco.com> <CAFU7BASoz5PQgMAih53gr1V9AEbTKOm-yaFriYugJn6-c7Fr-Q@mail.gmail.com> <F146EC4F-DBB7-4AF8-8D4A-4C5013DA5D1E@cisco.com>
In-Reply-To: <F146EC4F-DBB7-4AF8-8D4A-4C5013DA5D1E@cisco.com>
From: Jen Linkova <furry13@gmail.com>
Date: Thu, 12 Dec 2024 23:39:43 +1100
Message-ID: <CAFU7BATs9XnWoYmGV+FP0e_Q-WNXMiffAGv23AL79p116Xo=5A@mail.gmail.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: PREGRTWCVIGUBDWMZ5V2E2B4LWBACHXC
X-Message-ID-Hash: PREGRTWCVIGUBDWMZ5V2E2B4LWBACHXC
X-MailFrom: furry13@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: V6Ops Chairs <v6ops-chairs@ietf.org>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, IPv6 Operations <v6ops@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [v6ops] Re: Call for Adoption: draft-buraglio-deprecate7050
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ZOpb4t0ZUnfIP-HHqLptLgpf7Uk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>

On Thu, Dec 12, 2024 at 7:10 PM Charles Eckel (eckelcu)
<eckelcu@cisco.com> wrote:
> >> One option is to send an LS from v6ops to relevant 3GPP groups informing them of this draft and recommending they update their specs accordingly. Another option is to bring contributions to the relevant 3GPPs groups that update the relevant specs.
> >
> > Which option would you recommend? ;)
>
> I was leaning toward doing both; however, digging into this a bit more, I did not find any 3GPP specifications that reference RFC 7050 or RFC 8781. That is not to say that 3GPP deployments do not implement these mechanisms, but it is not clear to me what needs to be updated in terms of 3GPP requirements/specifications.

I'd say that 3GPP has nothing to do with RFC7050 - it's between the
endpoint and DNS64 servers: the endpoints discover the NAT64 prefix by
resolving "ipv4only.arpa.".
It would be nice if the network provides the endpoints with the NAT64
prefix by using RFC8781, but mobile networks are not doing it now. So
it's expected that 3GPP specifications do not mention RFC8781 *yet* -
and that's exactly what we'd like to change.

> >> I can help with the first,
> >
> > Thank you!
> >
> >> although I recommend waiting until an adopted working group draft exists.
> >
> > Strictly speaking RFC8781 (published by 6MAN) already says that PREF64
> > shall be preferred over RFC7050, and section 4.3.3 of
> > https://datatracker.ietf.org/doc/draft-ietf-v6ops-6mops/ states smth
> > very similar to this draft, but I guess 2 weeks are not going to
> > change anything ;)
> >
> > A question to v6ops chairs: is it going to be another call for
> > adoption, or was it enough interest expressed on the dnssop thread by
> > v6ops? It's not really clear from Tim's email..
> >
> >>
> >>> On Dec 11, 2024, at 8:27 AM, Jen Linkova <furry13@gmail.com> wrote:
> >>>
> >>> Adding Charles, who is the IETF 3GPP liaison.
> >>>
> >>> Charles, do you think it's feasible to add RFC8781 to the 3GPP
> >>> requirements? If yes, what do we need to do?
> >>>
> >>> Thanks!
> >>>
> >>> On Wed, Dec 11, 2024 at 1:06 PM Lorenzo Colitti
> >>> <lorenzo=40google.com@dmarc.ietf.org> wrote:
> >>>>
> >>>> I support adoption. It's high time for RFC7050 to be deprecated.
> >>>>
> >>>> We should try to get RFC 8781 into the next revision of the 3GPP requirements, so that mobile networks vendors implement it and mobile network operators can use it. Not sure who can help with that. Do we have a 3GPP liaison function/person, and is that what it/they are supposed to help with?
> >>>>
> >>>> On Mon, Dec 9, 2024 at 12:15 PM Nick Buraglio <buraglio@forwardingplane.net> wrote:
> >>>>>
> >>>>> FYI, this document had significantly more support within v6ops. As such, we've moved the adoption call here, so please think about it as a v6ops document, and voice any support, concern, advice, or general thoughts on the adoption call here.
> >>>>>
> >>>>> nb
> >>>>>
> >>>>> ---------- Forwarded message ---------
> >>>>> From: Tim Wicinski <tjw.ietf@gmail.com>
> >>>>> Date: Fri, Dec 6, 2024 at 1:32 PM
> >>>>> Subject: Re: Call for Adoption: draft-buraglio-deprecate7050
> >>>>> To: dnsop <dnsop@ietf.org>
> >>>>> Cc: dnsop-chairs <dnsop-chairs@ietf.org>, list <v6ops@ietf.org>, <v6ops-chairs@ietf.org>
> >>>>>
> >>>>>
> >>>>> All
> >>>>>
> >>>>> The DNSOP chairs have closed the Call for Adoption on this document.  The interest in adopting this is much higher in v6ops, so we talked with the v6ops chairs and Warren, and DNSOP will  NOT adopt this work. However, since there is interest to work on this, v6ops does seem poised to adopt this.  They will make sure dnsop are kept informed.
> >>>>>
> >>>>> Thanks all.
> >>>>>
> >>>>> tim
> >>>>>
> >>>>>
> >>>>> On Wed, Dec 4, 2024 at 11:23 AM Tim Wicinski <tjw.ietf@gmail.com> wrote:
> >>>>>>
> >>>>>> All
> >>>>>>
> >>>>>> A followup on the Call For Adoption.  We realized we did not include v6ops in this call for adoption, but we are also have not heard from folks in the working group after the talk at the last IETF meeting.
> >>>>>>
> >>>>>> Once again, this is a call for adoption for  "Deprecation of DNS64 for Discovery of IPv6 Prefix Used for IPv6 Address Synthesis"
> >>>>>>
> >>>>>> The draft is available here: https://datatracker.ietf.org/doc/draft-buraglio-deprecate7050/
> >>>>>>
> >>>>>> The chairs will take the silence as the group is not interested in working on this
> >>>>>>
> >>>>>> thanks
> >>>>>> tim
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Nov 20, 2024 at 11:22 AM Tim Wicinski <tjw.ietf@gmail.com> wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>> All
> >>>>>>>
> >>>>>>> During IETF121, there seemed to be some consensus to adopt this work in DNSOP.
> >>>>>>> Here are the relevant minutes and link to the presentation from the session:
> >>>>>>>
> >>>>>>>   Deprecation of DNS64 for Discovery of IPv6 Prefix Used for IPv6 Address Synthesis
> >>>>>>>       https://datatracker.ietf.org/meeting/121/materials/slides-121-dnsop-sessa-deprecation-of-dns64-for-discovery-of-ipv6-prefix-used-for-ipv6-address-synthesis-00
> >>>>>>>
> >>>>>>>       Jen Linkova: 7050 won't work in multihoming
> >>>>>>>           Would like to see this adopted
> >>>>>>>       Lorenzo Colitti: Would like to do this
> >>>>>>>           Have you asked the mobile operators why they do this?
> >>>>>>>           Maybe not realistic
> >>>>>>>           Nick: Maybe say "non-mobile environments"
> >>>>>>>       Tommy: Will not update his earlier draft, this is a better draft
> >>>>>>>       Èric: Likes this
> >>>>>>>           Nick: Not saying remove the old ones
> >>>>>>>       Lorenzo: Talk to mobile operators, maybe drop the old stuff
> >>>>>>>
> >>>>>>>
> >>>>>>> This starts a Call for Adoption for draft-buraglio-deprecate7050
> >>>>>>> "Deprecation of DNS64 for Discovery of IPv6 Prefix Used for IPv6 Address Synthesis"
> >>>>>>>
> >>>>>>> The draft is available here: https://datatracker.ietf.org/doc/draft-buraglio-deprecate7050/
> >>>>>>>
> >>>>>>> Please review this draft to see if you think it is suitable for adoption
> >>>>>>> by DNSOP, and send any comments to the list, clearly stating your view.
> >>>>>>>
> >>>>>>> Please also indicate if you are willing to contribute text, review, etc.
> >>>>>>>
> >>>>>>> Because of the American holiday next week, we are going to run this adoption call a little bit longer.
> >>>>>>>
> >>>>>>> This call for adoption ends: December 11, 2024
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> For DNSOP co-chairs
> >>>>>>> tim
> >>>>>
> >>>>> _______________________________________________
> >>>>> v6ops mailing list -- v6ops@ietf.org
> >>>>> To unsubscribe send an email to v6ops-leave@ietf.org
> >>>>
> >>>> _______________________________________________
> >>>> v6ops mailing list -- v6ops@ietf.org
> >>>> To unsubscribe send an email to v6ops-leave@ietf.org
> >>>
> >>>
> >>>
> >>> --
> >>> Cheers, Jen Linkova
> >>
> >
> >
> > --
> > Cheers, Jen Linkova
>


-- 
Cheers, Jen Linkova