Re: [v6ops] Fw: New Version Notification for draft-xie-v6ops-framework-multi-domain-ipv6only-00.txt

[Chongfeng XIE <[e-mail]>]

Hi, Bob,
Thank you for your comments.   I agree with you, in general, edge routers that are close to users process local routes and a default route into the big internet.   NSP in section 8.3 does not require every edge router handling IPv4 conversion to have a full IPv4 table for the whole internet, for every edge router, it can have its own mapping prefix, it can also obtain mapping prefix of other PEs ,including default mapping prefix from default egress PE, by exchaning mapping rules.  Maybe the illustration on this in the current draft is not clear, we will revise it later. 

Best regards

Chongfeng



[e-mail]
 
From: Bob Harold
Date: 2022-06-22 01:15
To: Chongfeng XIE
CC: list
Subject: Re: [v6ops] Fw: New Version Notification for draft-xie-v6ops-framework-multi-domain-ipv6only-00.txt

On Tue, Jun 21, 2022 at 2:27 AM Chongfeng XIE <[e-mail]> wrote:

Hi, folks,
We have submitted a new draft of  "draft-xie-v6ops-framework-multi-domain-ipv6only-00"  as below,  this work is based on the comments to the presentation of "draft-xie-v6ops-reqirements-multi-domain-ipv6only" in IETF 113.
 
Name: draft-xie-v6ops-framework-multi-domain-ipv6only
Revision: 00
Title: Framework of Multi-domain IPv6-only Network
Document date: 2022-06-21
Group: Individual Submission
Pages: 20
URL:            https://www.ietf.org/archive/id/draft-xie-v6ops-framework-multi-domain-ipv6only-00.txt
Status:         https://datatracker.ietf.org/doc/draft-xie-v6ops-framework-multi-domain-ipv6only/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-xie-v6ops-framework-multi-domain-ipv6only
 
Abstract:
   For the IPv6 transition, dual-stack deployments require both IPv4 and
   IPv6 transfer capabilities are deployed in parallel.  IPv6-only is
   considered as the ultimate stage where only IPv6 transfer
   capabilities are used while ensuring global reachability for both
   IPv6 and IPv4(IPv4aaS).  This document specifies requirements and
   propose a general framework when deploying IPv6-only in multi-domain
   network.


Any comments and suggestions are welcome.                                                                                 
 
Best regards
Chongfeng


I like the idea, but I have a concern.  As I understand it, routers near the edge in the current internet only need a small portion of the IPv4 routing table - just the local routes, and a default route into the big internet.  But section 8.3 Mapping, option 2) NSP would require every router at the edge handling IPv4 conversion to have a full IPv4 table for the whole internet, so it can use the right IPv6 prefix.  Is that correct?

-- 
Bob Harold