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 6DB98C15109C for ; Mon, 12 Aug 2024 06:56:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.107 X-Spam-Level: X-Spam-Status: No, score=-2.107 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, 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=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=forwardingplane.net 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 tC7obl6tcUP0 for ; Mon, 12 Aug 2024 06:56:40 -0700 (PDT) Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 C4D4BC14F5EF for ; Mon, 12 Aug 2024 06:56:40 -0700 (PDT) Received: by mail-qt1-x834.google.com with SMTP id d75a77b69052e-44fdde0c8dcso25076541cf.0 for ; Mon, 12 Aug 2024 06:56:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forwardingplane.net; s=google; t=1723470999; x=1724075799; 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=uTugQqwryVcn81LfNVECL2JMraIzDYCxPaui33o5Sm4=; b=Ev5H35u4Bh7O92z7GiiWJRJUB8/1zXqSZVPmTx44QdHEctAYlGwAa9mri4YiQfNHCY PYzYj/c5wYWn6puzI3lizolnB8eDSxEAv2/WJ6iBPbmZLBxvBE2yURK01zgGoBIccA1W 4of4cfstlka6+qV+dLW/PQwqjhQKimF/VIGk0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723470999; x=1724075799; 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=uTugQqwryVcn81LfNVECL2JMraIzDYCxPaui33o5Sm4=; b=OOUPj4SCZzHAh2yhbh9Wx3QkGD1vALfgFijFem93upCAsqCLweZzfVtnF3JzY5wqJi 0ueR3Ynd+N5ZXOFoCtp9MyrRd6ijcrtS1bhEjJRFrYuBggHkjLzjpBoI7oyUziAZISG1 ekHePS7gaQ4z79T2WxOuROzRLfEsvaq9gGbqJKQSjvEodKwAOGTjrcDrgHYnwwT6YqW9 PBywh06BayoxmanpyDnCGhgLe8yGuxx624dT2BaegaeHQ3SGtD+RlMlOZhf3r6WY2BdS 7JfGOa1uYUaZyVMbCvuEsID4F/9XJQnt8S+4aHqmsDtQrZoq6ZiHMHZBQ5UoLbP5etSG nLOQ== X-Gm-Message-State: AOJu0YwDI7qTmQl1FS32mGWXvR5ki/cMHzJt3HkIYTLHNJWlU17VnR1r FBtPG8fCcAvZHtInE8yc/MePvDzRvjW8TdaYDjlWn6/y5liPu/9NKlxgHY8WvCKcxeYbmE+VkP4 mBo7PAk56seeELZzuBK3UKCp2yvZCMuPT5ck5z1lcSeUlg5aZ6w== X-Google-Smtp-Source: AGHT+IGYU9uYFfxT4urxV5EcsBrLFEWKzypfTJ4W1PzGrPMh0wuL1AQz+iXr/pS2Qt3QJWbCdoinNcAdFm1bJHKsrmg= X-Received: by 2002:a05:622a:8cc:b0:447:e0e6:7787 with SMTP id d75a77b69052e-45349b94daemr4445221cf.60.1723470999487; Mon, 12 Aug 2024 06:56:39 -0700 (PDT) MIME-Version: 1.0 References: <076cce6c12284cefa9922f7947ff5c0e@huawei.com> In-Reply-To: From: Nick Buraglio Date: Mon, 12 Aug 2024 08:56:28 -0500 Message-ID: To: "jordi.palet@consulintel.es" Content-Type: multipart/alternative; boundary="000000000000b4a246061f7cdc6f" Message-ID-Hash: SO36I6OZJA44CPDIUOVN3RH7HKT5V3YG X-Message-ID-Hash: SO36I6OZJA44CPDIUOVN3RH7HKT5V3YG X-MailFrom: buraglio@forwardingplane.net 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: 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: --000000000000b4a246061f7cdc6f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 late 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 wrote: > Hi XiPeng, > > Yes, I=E2=80=99m aware of that =E2=80=A6 in fact I=E2=80=99m co-author of= that document as well =E2=80=A6 > we are just waiting for the WG adoption, not sure if the call has been do= ne > 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. I= f > there are important things in draft-ietf-v6ops-rfc7084-bis-04 that are no= t > 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 me= an > 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 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 > > 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 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 > To unsubscribe send an email to v6ops-leave@ietf.org > --000000000000b4a246061f7cdc6f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
There is indeed another draft ( https://datatracker.ietf= .org/doc/draft-winters-v6ops-rfc7084bis/ ) which has not been called fo= r adoption. There were some discussions back in late 2023 about splitting d= ocuments=C2=A0out with a -bis to 7084 (seen here=C2=A0https://mai= larchive.ietf.org/arch/msg/v6ops/5Af8W_vlQp74B3Hl9jAEaPdDtuE/ ). I will= 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
--000000000000b4a246061f7cdc6f--