Re: [v6ops] WG Call For Adoption: draft-xie-v6ops-framework-md-ipv6only-underlay-05

[Qin Wu <[e-mail]>]

Hi, Xie and authors:
Thanks for writing this document, it is very useful guideline document which helps operators and developers understand how to migrate toward IPv6 only network while still not disrupt IPv4 service.
Here are few comments and suggestions:
Title
How about change it into Framework for IPv4 service over IPv6 only underlay network in multi-domain setting?
Abstract:
I think transfer lack accuracy, what you propose to support IPv6 bearer or IPv6 transport in the underlay
And support IPv6 as a service and IPv4 as a service simultaneously in the overlay network.
How about change it into IPv6 bearer?
Add service behind “both IPv6 and IPv4 (usually known as IPv4aaS).”

I don’t think we should emphasize security consideration sine security consideration is MUST for every IETF documents.

Section 2, definition of IPv6 only network
s/multi-domain IPv6-only network: An IPv6-only network which consists / multi-domain IPv6-only network: An IPv6-only underlay network which consists

Section 2
The short names of ASBR, AFBR, ADPT need to be expanded? E.g., AFBR is short name of Address Family Border Router

Section 4:
For multi-domain network, should we add reference to RFC8299, RFC8466? I think these two RFCs are most relevant one which have already considered both IPv4 and IPv6 support.

s/transporation/transport

Section 5:
I am wondering whether requirements should be separated from this framework document as independent I-D? or maybe change requirements into principles?

Section 7
I believe Ipv4 delivery from ingress PE to egress PE is related to PE based VPN while IPv4 delivery from UE/CPE to egress PE is more related to CE based VPN or SD-WAN
For IPv6 data path from Ingress PE to Egress PE, Can this IPv6 Data Path IPSEC tunnel or there are multiple random paths between Ingress PE to Egress PE and each Path traverses across multiple domains and has multiple hops?
If it can be the IPSEC tunnel, I am wondering whether this tunnel will be shared by all UE/CPE who send the traffic over this data path? Would it be great to add some IPSEC example in this draft to explain this?

-Qin
发件人: v6ops [mailto:[e-mail]] 代表 Ron Bonica
发送时间: 2022年11月19日 5:54
收件人: [e-mail]
主题: [v6ops] WG Call For Adoption: draft-xie-v6ops-framework-md-ipv6only-underlay-05

Folks,

This message initiates a WG call for adoption for draft-xie-v6ops-framework-md-ipv6only-underlay-05. To accommodate the American holiday, the call for adoption will end on December 9, 2022.

                                                       Ron



Juniper Business Use Only