[v6ops] Re: WG Last Call: draft-ietf-v6ops-framework-md-ipv6only-underlay-13 (Ends 2025-10-08)

[Xipengxiao <[e-mail]>]

Hi folks,

Ron Bonica has kindly agreed to be the shepherd for draft-ietf-v6ops-framework-md-ipv6only-underlay.  Now we are waiting for the writeup before we send the document to the responsible AD, Mahesh Jethanandani, in this case.

Regards,

XiPeng 

-----Original Message-----
From: Xipengxiao <xipengxiao=[e-mail]> 
Sent: Wednesday, February 11, 2026 2:21 PM
To: [e-mail]
Cc: [e-mail]; [e-mail]
Subject: RE: WG Last Call: draft-ietf-v6ops-framework-md-ipv6only-underlay-13 (Ends 2025-10-08)

Hi folks,

Draft-ietf-v6ops-framework-md-ipv6only-underlay has been in WGLC since Sept.  During the process, the following people expressed support for its publication:

Brian Carpenter, Xing Li, Fan Zhang, Tianran Zhou, Xiao Min, Yao Liu, Tim Wicinski (with nits), Pang Ran, Weiqiang Cheng

Meanwhile, Jen Linkova, Daryll Swer and XiPeng Xiao raised substantive comments leading to six revisions of the draft.  After reading the latest -19 version, I believe all the issues raised by Jen, Daryll and Xipeng have been addressed, and the draft is ready to be sent to the IESG.  I do notice a few remaining editorial issues, e.g.,  s/nor/or in "nor any risk of traffic black-holing", but I think these issues can be fixed during the IETF last call process.

As such, the chairs would like to the give the WG another week to review and comment, before we send it to Med/IESG on Monday Feb. 23. 

Thank you very much, and happy Chinese New Year (next week) to the Chinese colleagues!

XiPeng  

 

-----Original Message-----
From: Nick Buraglio via Datatracker <[e-mail]> 
Sent: Wednesday, September 24, 2025 11:25 PM
To: [e-mail]; [e-mail]; [e-mail]
Subject: WG Last Call: draft-ietf-v6ops-framework-md-ipv6only-underlay-13 (Ends 2025-10-08)


Subject: WG Last Call: draft-ietf-v6ops-framework-md-ipv6only-underlay-13
(Ends 2025-10-08)

This message starts a 2-week WG Last Call for this document.

Abstract:
   For the IPv6 transition, IPv6-only is considered as the final stage,
   where only IPv6 protocol is used for transport while maintaining
   global reachability for both IPv6 and IPv4 services.  This document
   illustrates a framework of multi-domain IPv6-only underlay network
   from an operator's perspective.  In particular, it proposes stateless
   address mapping as the base for enabling IPv4 service data
   transmission in an multi-domain IPv6-only environment(i.e.,IPv4-as-
   a-Service).  It describes the methodology of stateless IPv4/IPv6
   mapping, illustrates the behaviors of network devices, analyzes the
   options of IPv6 mapping prefix allocation, examines the utilization
   of SRv6, and discusses the security considerations.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-framework-md-ipv6only-underlay/

Please review and indicate your support or objection to proceed with the publication of this document by replying to this email keeping [e-mail] in copy. Objections should be motivated and suggestions to resolve them are highly appreciated.

Authors, and WG participants in general, are reminded again of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [1]. Appropriate IPR disclosures required for full conformance with the provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. Sanctions available for application to violators of IETF IPR Policy can be found at [3].

Thank you.

[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/