[v6ops] Re: stale and abandoned WG drafts

Xipengxiao <xipengxiao@huawei.com> Mon, 12 August 2024 12:27 UTC

Return-Path: <xipengxiao@huawei.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 79834C1522B9 for <v6ops@ietfa.amsl.com>; Mon, 12 Aug 2024 05:27:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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_DBL_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
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 AqC5nkUPYSRa for <v6ops@ietfa.amsl.com>; Mon, 12 Aug 2024 05:27:41 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A85BC14F6B4 for <v6ops@ietf.org>; Mon, 12 Aug 2024 05:27:41 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4WjDHQ0fb0z6K9Q5; Mon, 12 Aug 2024 20:25:06 +0800 (CST)
Received: from frapeml100001.china.huawei.com (unknown [7.182.85.63]) by mail.maildlp.com (Postfix) with ESMTPS id 78131140C72; Mon, 12 Aug 2024 20:27:38 +0800 (CST)
Received: from frapeml500004.china.huawei.com (7.182.85.22) by frapeml100001.china.huawei.com (7.182.85.63) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Mon, 12 Aug 2024 14:27:38 +0200
Received: from frapeml500004.china.huawei.com ([7.182.85.22]) by frapeml500004.china.huawei.com ([7.182.85.22]) with mapi id 15.01.2507.039; Mon, 12 Aug 2024 14:27:38 +0200
From: Xipengxiao <xipengxiao@huawei.com>
To: "jordi.palet@consulintel.es" <jordi.palet=40consulintel.es@dmarc.ietf.org>, IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] Re: stale and abandoned WG drafts
Thread-Index: AQHa7JLBiVUHJ55GkEmNVifVA7+tO7IjhvxA
Date: Mon, 12 Aug 2024 12:27:38 +0000
Message-ID: <076cce6c12284cefa9922f7947ff5c0e@huawei.com>
References: <CACMsEX8Z4LBRQ63=P_gezMcO2p13CgX6=Tv1Ncdgfdvd39kZfw@mail.gmail.com> <CD3018BD-E7F9-4DC2-8998-453D67B9B93E@consulintel.es>
In-Reply-To: <CD3018BD-E7F9-4DC2-8998-453D67B9B93E@consulintel.es>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.217.221]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: 27BY25KX4FCOM7E2UVRZX5CZV7DBHMVK
X-Message-ID-Hash: 27BY25KX4FCOM7E2UVRZX5CZV7DBHMVK
X-MailFrom: xipengxiao@huawei.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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [v6ops] Re: stale and abandoned WG drafts
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/gDuz1U5FQnjxjggOncCX7O0wpS4>
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>

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 not 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 <jordi.palet=40consulintel.es@dmarc.ietf.org> 
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 mean 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ó:
> 
> 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