Re: [v6ops] draft-xie-v6ops-reqirements-multi-domain-ipv6only

[Xipengxiao <[e-mail]>]

Hi Chongfeng,

I read your draft twice, but I may still have some misunderstanding.  With this disclaimer, I provide my comments below:


1.    Section 4: I think the draft identifies a problem that may be worth solving, that is, there is a need for multi-domain IPv6-only solutions to eliminate unnecessary v4-v6 conversions in the middle.

2.    Section 5: after reading the problem statement in Section 4, I expect some solution ideas here.  But Section 5 is about scenarios.   The scenarios seem unnecessarily comprehensive too.  I feel that the logic is distracted.

3.    Section 6: some requirements are related to the problem statement, others are not so related.  I suggest deleting those not so related to keep the logic clearer, e.g. R1, R5, R8

4.    Section 7:

a.    This seems like a solution section to me.  So, should this draft be submitted to 6man?

b.    It’s not clear to me, how your framework/solution reduces v4-v6 conversions compared to existing softwire solutions.

5.    Section 8:

a.    It may be worth comparing, how an IPv4 packet will be handled with and without your solution.  Is there a difference in the number of v4-v6 conversions?


There are also some minor editorial comments:



For the IPv6 transition, dual-stack deployments require both IPv4 and

   IPv6 transfer capabilities are deployed in parallel.

XiPeng: the word “transfer” is a little strange.  Maybe “transport”?

   o  Multi-domain IPv6-only network: An IPv6-only network which
      consists of multiple ASes belonging to and operated by the same
      operator.

   o  Inter-domain IPv6-only network: An IPv6-only network which
      consists of multiple ASes belonging to and operated by different
      operators.

XiPeng: the meaning of domain is different in these two terms.  In the former, it means an AS.  In the latter, it means an administrative domain.  To avoid inconsistency, you may consider changing Multi-domain IPv6-only network to Multi-AS IPv6-only network
The global industry has not given a unified definition of IPv6-only network so far.



XiPeng: I think the ipv6-deployment-status draft now gives good definition of IPv6-only.  You may take a look.



Scenario 4: DC-to-DC, i.e., IPv6-only provide communications between

   VMs hosted in cloud data centers, despite they are IPv4, IPv6 or

   IPv4/IPv6 dual-stack.


==>

Scenario 4: DC-to-DC, i.e., IPv6-only provides communications between

   VMs hosted in cloud data centers, no matter they are IPv4, IPv6 or

   IPv4/IPv6 dual-stack.

7.2.  ADPT

XiPeng: ADPT is not previously defined, and not defined here until in the middle of paragraph.  Suggest either defining it in the terminology section, and defining it in the 1st sentence of this paragraph
AFBR is not defined either.





From: v6ops <[e-mail]> On Behalf Of Fred Baker
Sent: Sunday, July 3, 2022 8:00 PM
To: v6ops list <[e-mail]>
Subject: [v6ops] draft-xie-v6ops-reqirements-multi-domain-ipv6only

With this email, let me invite commentary on draft-xie-v6ops-reqirements-multi-domain-ipv6only. Please read the draft and raise any issues you might have with it.