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

Hi Ron,

I support adoption! Some comments for authors to work on -

## Minor

- Section 6.2, Figure 3 needs better description in text and consider
adding a legend for RM, MD, RP, DF. The interface Ix also gets a bit
confusing. If some of them are internal interfaces, do they need to be
listed in a standard? I am worried about this section overall. Perhaps
better to describe this as an example in the appendix?

## Nits

- Choose a smaller abbreviation for the header - "Multi-domain IPv6-only
Underlay Framewor"

- Avoid using the term "IPv6 transfer capabilities", stick to "forwarding".
It is used once in abstract!

- Consider breaking this sentence up
````
   This document specifies
   requirements and proposes a framework for deploying IPv6-only as the
   underlay in multi-domain networks, discusses the requirements of
   service traffic, major components and interfaces, IPv6 mapping prefix
   allocation, typical procedures for service delivery.
````

- s/considerations with security/security considerations/
- s/As per 2022/As of 2022/
- s/when IPv6 usage is being the dominant/when IPv6 usage is dominant/
- s/should not succeed two/should not exceed two/
- s/addtess/address/
- Expand on first use
    - eBGP
    - XLAT
    - CLAT
    - PLAT

Thanks!
Dhruv

On Sat, Nov 19, 2022 at 3:24 AM Ron Bonica <rbonica=
40juniper.net@dmarc.ietf.org> wrote:

> 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
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>