Return-Path: 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 A9DD5C1519A2 for ; Mon, 12 Aug 2024 10:18:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.105 X-Spam-Level: X-Spam-Status: No, score=-2.105 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, 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 (1024-bit key) header.d=qacafe.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 SxABZmOoojLN for ; Mon, 12 Aug 2024 10:18:37 -0700 (PDT) Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 64A0AC151070 for ; Mon, 12 Aug 2024 10:18:37 -0700 (PDT) Received: by mail-pj1-x102e.google.com with SMTP id 98e67ed59e1d1-2cb4b7fef4aso3603065a91.0 for ; Mon, 12 Aug 2024 10:18:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qacafe.com; s=google; t=1723483117; x=1724087917; 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=DGdfvWi1hpw0SoW1HQ0qY5j6Ebv3eeMS3Ory5ke/45E=; b=FUxFA86dB5pniekRYF5hCkZFIn+dx5780eur9osak79dxitSg8zrpQ0XDB4LRQN4K1 CY9gnfGmwX8bK5N2bvmFLlHIkRzfd4rk4GGeazzyb9gf3GUMT9JMXaMcf6oM8FGcKgpt U0TPsfa92HmRTvMrruDvVhmBMIleMLkzVafhk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723483117; x=1724087917; 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=DGdfvWi1hpw0SoW1HQ0qY5j6Ebv3eeMS3Ory5ke/45E=; b=FgzMkz+rHtbz62iK1akOVvi2j/sdaGwbpiYNQGwDc1f/bJ/CzS/4xbygxjE21yU3Dw 7NUWjTkZUrvHCiwkV4OO02njgvVJrC63hRWtbY4ANGC9S7OTarbE142kO5C7TQWMXFNb JcXT3ozZywvhGWyOww8Y0JOm8vs9J3FFnMZp1EpkRVXDq+djeFKux+rVPqGQMf5Llz10 coKR3nuG9C9N1yhhhKpT8ULsOxT7PQ4Zx484s/BOxRsNnLhxtDlvyk6W92WWwceN59fE 0yTr1y0aDGqirqlucf7Sn4VnTcbJ1fyLCcdczqPxmdbk2nYKjyfh4HAoiKrq0al5Iym0 fcRA== X-Forwarded-Encrypted: i=1; AJvYcCVU2zLqzIJO7BCVnaTJCX03lrkVv99LFKnwndaJQWT7k9zX7o3ybjWx8KWcWbt22nB+gl7ueP3bIdt4WOqA/w== X-Gm-Message-State: AOJu0YwZFtzrBK0leydqSwv0taVSwdMMhWo15I8yihbKhZxS4TM4xjFx 8nJSD99JlKS9btiiM14EYRruCfTE6Xe/B5ZTXyQ2u8y1rrYsaKXkj2vIM2gBeuluJApkhZAGP3H pPWv0az7pguCSyjoHyqqrVtL7toNOCpsukyNZJWhmpr6IJq+GoRo= X-Google-Smtp-Source: AGHT+IF0QP/C9pYMSwS1wTQx+Xo6+GnIZeYiEHB/EJDpYAJPZON/dRf+iRgP/1viG4s0Jt3B50vsJmOYmJxu9FewtjM= X-Received: by 2002:a17:90a:2d83:b0:2cd:7d6f:31b0 with SMTP id 98e67ed59e1d1-2d3926a9b7fmr880439a91.43.1723483116606; Mon, 12 Aug 2024 10:18:36 -0700 (PDT) MIME-Version: 1.0 References: <076cce6c12284cefa9922f7947ff5c0e@huawei.com> In-Reply-To: From: Timothy Winters Date: Mon, 12 Aug 2024 13:18:24 -0400 Message-ID: To: Nick Buraglio Content-Type: multipart/alternative; boundary="000000000000f142c6061f7fae1a" Message-ID-Hash: KCM2OCZY2EWMKSTSWM64BT4KJLAG6HAM X-Message-ID-Hash: KCM2OCZY2EWMKSTSWM64BT4KJLAG6HAM X-MailFrom: tim@qacafe.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: "jordi.palet@consulintel.es" , IPv6 Operations X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5Bv6ops=5D_Re=3A_stale_and_abandoned_WG_drafts?= List-Id: v6ops discussion list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000f142c6061f7fae1a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I asked for adoption at the end of the presentation in Vancouver for ( https://datatracker.ietf.org/doc/draft-winters-v6ops-rfc7084bis/). I did neglect to send the request on the mailing list which has led to some of this confusion. The authors will put out a new version based on feedback and I'll ask on the mailing list to help avoid confusion. As Jordi mentioned, the older 7084bis (draft-ietf-v6ops-rfc7084-bis-04) ended up becoming 8585. The new 7084 references 8585 for transition mechanisms. ~Tim On Mon, Aug 12, 2024 at 9:56=E2=80=AFAM Nick Buraglio wrote: > There is indeed another draft ( > https://datatracker.ietf.org/doc/draft-winters-v6ops-rfc7084bis/ ) which > has not been called for adoption. There were some discussions back in lat= e > 2023 about splitting documents out with a -bis to 7084 (seen here > https://mailarchive.ietf.org/arch/msg/v6ops/5Af8W_vlQp74B3Hl9jAEaPdDtuE/ > ). I will reach out to Tim for further clarification and to refresh > my memory. > > nb > > > > On Mon, Aug 12, 2024 at 8:00=E2=80=AFAM jordi.palet@consulintel.es 40consulintel.es@dmarc.ietf.org> wrote: > >> Hi XiPeng, >> >> Yes, I=E2=80=99m aware of that =E2=80=A6 in fact I=E2=80=99m co-author o= f that document as well =E2=80=A6 >> we are just waiting for the WG adoption, not sure if the call has been d= one >> already? >> >> Regards, >> Jordi >> >> @jordipalet >> >> >> > El 12 ago 2024, a las 14:27, Xipengxiao > 40huawei.com@dmarc.ietf.org> escribi=C3=B3: >> > >> > Hi Jordi, >> > >> > Sometime ago there was a discussion in the ML to update CPE >> requirements. Tim Winters and a few other people have some proposals. = If >> there are important things in draft-ietf-v6ops-rfc7084-bis-04 that are n= ot >> covered in RFC8585, you can work with Tim et al to submit a draft. This= is >> one of the WG milestones. Thanks. >> > >> > XiPeng >> > >> > -----Original Message----- >> > From: jordi.palet@consulintel.es > 40consulintel.es@dmarc.ietf.org> >> > Sent: Monday, August 12, 2024 10:35 AM >> > To: IPv6 Operations >> > Subject: [v6ops] Re: stale and abandoned WG drafts >> > >> > Hi Nick, >> > >> >> draft-ietf-v6ops-rfc7084-bis-04 >> > >> > Initially the WG accepted a new version of the RFC7084. However, right >> before the LC, the WG changed their mind and then the work was done by m= ean >> of an alternative path, with resulted in RFC8585. >> > >> > Regards, >> > Jordi >> > >> > @jordipalet >> > >> > >> >> El 26 jul 2024, a las 21:09, Nick Buraglio < >> buraglio@forwardingplane.net> escribi=C3=B3: >> >> >> >> As mentioned in the 120 v6ops session, we are doing some housekeeping >> >> and changing status on old documents. Document details are below, we >> >> plan to move these to DEAD status. If folks would like to revive them >> >> they can be updated and state changed. >> >> >> >> draft-ietf-v6ops-ipv6rtr-reqs-04 >> >> Requirements for IPv6 Routers >> >> 2018-05-26 Expired >> >> WG Document >> >> >> >> draft-ietf-v6ops-rfc7084-bis-04 >> >> Basic Requirements for IPv6 Customer Edge Routers >> >> 2017-06-12 Expired >> >> WG Document >> >> >> >> draft-ietf-v6ops-design-choices-12 >> >> Routing-Related Design Choices for IPv6 Networks >> >> 2016-11-13 Expired >> >> WG Document : Informational >> >> Fred Baker >> >> >> >> draft-ietf-v6ops-dhcpv6-slaac-problem-07 >> >> DHCPv6/SLAAC Interaction Problems on Address and DNS Configuration >> >> 2016-08-17 Expired >> >> WG Document : Informational >> >> Fred Baker >> >> >> >> draft-ietf-v6ops-dc-ipv6-01 >> >> IPv6 Operational Guidelines for Datacenters >> >> 2014-02-04 Expired >> >> In WG Last Call >> >> Fred Baker >> >> >> >> draft-ietf-v6ops-balanced-ipv6-security-01 >> >> Balanced Security for IPv6 Residential CPE >> >> 2013-12-06 Expired >> >> WG Document >> >> Review: secdir Early >> >> >> >> draft-ietf-v6ops-monitor-ds-ipv6-00 >> >> Monitoring Dual Stack/IPv6-only Networks and Services >> >> 2013-08-14 Expired >> >> WG Document >> >> >> >> draft-ietf-v6ops-v4v6tran-framework-02 >> >> Framework for IP Version Transition Scenarios >> >> 2011-07-26 Expired >> >> WG Document : Informational Ron Bonica >> >> >> >> draft-ietf-v6ops-nat64-pb-statement-req-00 >> >> IPv4/IPv6 Coexistence and Transition: Requirements for solutions >> >> 2008-05-13 Expired >> >> WG Document >> >> >> >> draft-ietf-v6ops-campus-transition-01 >> >> IPv6 Campus Transition Scenario Description and Analysis >> >> 2007-03-28 Expired >> >> WG Document >> >> >> >> draft-ietf-v6ops-routing-guidelines-01 >> >> IPv6 Routing Policies Guidelines >> >> 2007-02-27 Expired >> >> WG Document >> >> >> >> draft-ietf-v6ops-ipv4survey-00 >> >> Survey of IPv4 Addresses in Currently Deployed IETF Standards >> >> 2003-01-13 Expired >> >> WG Document >> >> >> >> _______________________________________________ >> >> v6ops mailing list -- v6ops@ietf.org >> >> To unsubscribe send an email to v6ops-leave@ietf.org >> > >> > >> > ********************************************** >> > 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 o= r >> 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 o= r >> 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 >> > 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 >> >> >> ********************************************** >> 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 o= r >> 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 >> 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 > --000000000000f142c6061f7fae1a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I asked for adoption at the end of the presentation in Van= couver for (https://datatracker.ietf.org/doc/draft-wint= ers-v6ops-rfc7084bis/). I did neglect to send the request on the mailin= g list which has led to some of this confusion.=C2=A0 =C2=A0The authors wil= l put out a new version based on feedback and I'll ask on the mailing l= ist to help avoid confusion.=C2=A0

As Jordi mentioned, t= he older 7084bis=C2=A0(draft-ietf-v6ops-rfc7084-bis-04) ended up becoming 8= 585.=C2=A0 =C2=A0 The new 7084 references 8585 for transition mechanisms.

~Tim

=
On Mon, Aug 12, 2024 at 9:56=E2=80=AF= AM Nick Buraglio <buraglio@forwardingplane.net> wrote:
There is indeed an= other draft ( https://datatracker.ietf.org/doc/draft-wi= nters-v6ops-rfc7084bis/ ) which has not been called for adoption. There= were some discussions back in late 2023 about splitting documents=C2=A0out= with a -bis to 7084 (seen here=C2=A0https://ma= ilarchive.ietf.org/arch/msg/v6ops/5Af8W_vlQp74B3Hl9jAEaPdDtuE/ ). I wil= l reach out to Tim for further clarification and to refresh my=C2=A0memory.= =C2=A0=C2=A0

nb


<= /div>
O= n Mon, Aug 12, 2024 at 8:00=E2=80=AFAM jordi.palet@consulintel.es <jordi.palet= =3D40c= onsulintel.es@dmarc.ietf.org> wrote:
Hi XiPeng,

Yes, I=E2=80=99m aware of that =E2=80=A6 in fact I=E2=80=99m co-author of t= hat document as well =E2=80=A6 we are just waiting for the WG adoption, not= sure if the call has been done already?

Regards,
Jordi

@jordipalet


> El 12 ago 2024, a las 14:27, Xipengxiao <xipengxiao=3D40huawei.com@dmarc.ietf= .org> escribi=C3=B3:
>
> Hi Jordi,
>
> Sometime ago there was a discussion in the ML to update CPE requiremen= ts.=C2=A0 Tim Winters and a few other people have some proposals.=C2=A0 If = there are important things in draft-ietf-v6ops-rfc7084-bis-04 that are not = covered in RFC8585, you can work with Tim et al to submit a draft.=C2=A0 Th= is is one of the WG milestones.=C2=A0 Thanks.
>
> XiPeng
>
> -----Original Message-----
> From: = jordi.palet@consulintel.es <jordi.palet=3D40consulintel.es@dmarc.ietf.org<= /a>>
> Sent: Monday, August 12, 2024 10:35 AM
> To: IPv6 Operations <v6ops@ietf.org>
> Subject: [v6ops] Re: stale and abandoned WG drafts
>
> Hi Nick,
>
>> draft-ietf-v6ops-rfc7084-bis-04
>
> Initially the WG accepted a new version of the RFC7084. However, right= before the LC, the WG changed their mind and then the work was done by mea= n of an alternative path, with resulted in RFC8585.
>
> Regards,
> Jordi
>
> @jordipalet
>
>
>> El 26 jul 2024, a las 21:09, Nick Buraglio <buraglio@forwardingplane.net= > escribi=C3=B3:
>>
>> As mentioned in the 120 v6ops session, we are doing some housekeep= ing
>> and changing status on old documents. Document details are below, = we
>> plan to move these to DEAD status. If folks would like to revive t= hem
>> they can be updated and state changed.
>>
>> draft-ietf-v6ops-ipv6rtr-reqs-04
>> Requirements for IPv6 Routers
>> 2018-05-26 Expired
>> WG Document
>>
>> draft-ietf-v6ops-rfc7084-bis-04
>> Basic Requirements for IPv6 Customer Edge Routers
>> 2017-06-12 Expired
>> WG Document
>>
>> draft-ietf-v6ops-design-choices-12
>> Routing-Related Design Choices for IPv6 Networks
>> 2016-11-13 Expired
>> WG Document : Informational
>> Fred Baker
>>
>> draft-ietf-v6ops-dhcpv6-slaac-problem-07
>> DHCPv6/SLAAC Interaction Problems on Address and DNS Configuration=
>> 2016-08-17 Expired
>> WG Document : Informational
>> Fred Baker
>>
>> draft-ietf-v6ops-dc-ipv6-01
>> IPv6 Operational Guidelines for Datacenters
>> 2014-02-04 Expired
>> In WG Last Call
>> Fred Baker
>>
>> draft-ietf-v6ops-balanced-ipv6-security-01
>> Balanced Security for IPv6 Residential CPE
>> 2013-12-06 Expired
>> WG Document
>> Review: secdir Early
>>
>> draft-ietf-v6ops-monitor-ds-ipv6-00
>> Monitoring Dual Stack/IPv6-only Networks and Services
>> 2013-08-14 Expired
>> WG Document
>>
>> draft-ietf-v6ops-v4v6tran-framework-02
>> Framework for IP Version Transition Scenarios
>> 2011-07-26 Expired
>> WG Document : Informational Ron Bonica
>>
>> draft-ietf-v6ops-nat64-pb-statement-req-00
>> IPv4/IPv6 Coexistence and Transition: Requirements for solutions >> 2008-05-13 Expired
>> WG Document
>>
>> draft-ietf-v6ops-campus-transition-01
>> IPv6 Campus Transition Scenario Description and Analysis
>> 2007-03-28 Expired
>> WG Document
>>
>> draft-ietf-v6ops-routing-guidelines-01
>> IPv6 Routing Policies Guidelines
>> 2007-02-27 Expired
>> WG Document
>>
>> draft-ietf-v6ops-ipv4survey-00
>> Survey of IPv4 Addresses in Currently Deployed IETF Standards
>> 2003-01-13 Expired
>> WG Document
>>
>> _______________________________________________
>> v6ops mailing list -- v6ops@ietf.org
>> To unsubscribe send an email to v6ops-leave@ietf.org
>
>
> **********************************************
> 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 o= r confidential. The information is intended to be for the exclusive use of = the individual(s) named above and further non-explicilty authorized disclos= ure, 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 aw= are that any disclosure, copying, distribution or use of the contents of th= is information, even if partially, including attached files, is strictly pr= ohibited, will be considered a criminal offense, so you must reply to the o= riginal sender to inform about this communication and delete it.
>
>
>
>
> _______________________________________________
> 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


**********************************************
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 con= fidential. The information is intended to be for the exclusive use of the i= ndividual(s) named above and further non-explicilty authorized disclosure, = copying, distribution or use of the contents of this information, even if p= artially, including attached files, is strictly prohibited and will be cons= idered a criminal offense. If you are not the intended recipient be aware t= hat any disclosure, copying, distribution or use of the contents of this in= formation, even if partially, including attached files, is strictly prohibi= ted, will be considered a criminal offense, so you must reply to the origin= al sender to inform about this communication and delete it.




_______________________________________________
v6ops mailing list -- v= 6ops@ietf.org
To unsubscribe send an email to v6ops-leave@ietf.org
_______________________________________________
v6ops mailing list -- v= 6ops@ietf.org
To unsubscribe send an email to v6ops-leave@ietf.org
--000000000000f142c6061f7fae1a--