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

[Brian E Carpenter <[e-mail]>]

Hi,

That looks good, thanks!

Regards/Ngā mihi
    Brian Carpenter

On 29-Sep-25 22:09, Chongfeng Xie wrote:
> Hi Brian,
> 
> Based on your suggestion, I plan to add the following sentences at section 1, i.e., Introduction section,
> 
>      draft-ietf-v6ops-6mops illustrates a deployment scenario called "an IPv6-Mostly network",
>      when IPv6-only and IPv4-enabled endpoints coexist on the same network (network segment,
>      VLAN, SSID etc). It allows IPv6-capable devices to remain IPv6-only while the network is
>      seamlessly supplying IPv4 access to those that require it.
> 
> Accordingly, draft-ietf-v6ops-6mops is added to the section of informational reference. If you have more comments, please feel free to raise them.
> 
> Best regards
> Chongfeng
> 
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> [e-mail]
> 
>     *From:* Brian E Carpenter <mailto:[e-mail]>
>     *Date:* 2025-09-26 11:24
>     *To:* Nick Buraglio <mailto:[e-mail]>; draft-ietf-v6ops-framework-md-ipv6only-underlay <mailto:[e-mail]>; v6ops-chairs <mailto:[e-mail]>; v6ops <mailto:[e-mail]>
>     *Subject:* [v6ops] Re: WG Last Call: draft-ietf-v6ops-framework-md-ipv6only-underlay-13 (Ends 2025-10-08)
>     I have read this draft again and I believe it is ready.
>     One tiny point: this draft doesn't mention draft-ietf-v6ops-6mops, and 6mops doesn't mention ipv6only-underlay. I think it would be useful to clarify the relationship between the two documents; since 6mops is still being developed, perhaps it belongs there.
>     Regards/Ngā mihi
>          Brian Carpenter
>     On 25-Sep-25 09:24, Nick Buraglio via Datatracker wrote:
>      >
>      > 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/
>      >
>      >
>      >
>      > _______________________________________________
>      > v6ops mailing list -- [e-mail]
>      > To unsubscribe send an email to [e-mail]
>     _______________________________________________
>     v6ops mailing list -- [e-mail]
>     To unsubscribe send an email to [e-mail]
>