Re: [Idr] Fw: Re: New Version Notification for draft-xie-idr-mpbgp-extention-4map6-00.txt

[Chongfeng Xie <[e-mail]>]

Hi Gyan,
Thank you for your further comments, pls see my feedback inline.


[e-mail]
 
From: Gyan Mishra
Date: 2023-01-19 13:46
To: Chongfeng Xie
CC: donggz; idr; idr-chairs; xing
Subject: Re: [Idr] Fw: Re: New Version Notification for draft-xie-idr-mpbgp-extention-4map6-00.txt

Hi Chongfeng

I see in the 4map6 path attribute it defines forwarding type on the egress PE for encapsulation or translation.  

This draft talks about the BGP aspects of the 4map6  service, however there seems to be another big piece to the puzzle which is the mapping table on the PE.

Would there be a framework document that goes over the details of the overall solution for how the mapping db on the egress PE db data structures is built  and how that would be built for both translation and encapsulation options.  
[Chongfeng]:  The subject draft is related to draft-ietf-v6ops-framework-md-ipv6only-underlay, which is the framework doument that cover the issues you mentioned.

Since this mapping is prefix based and not traditional 1-1 or 1-many NAT or PAT overload or even PT style I wonder how this would all work.
[Chongfeng]:  Yes, this is a prefix-based 1:1 adress mapping without any port mapping, so it is scalable. Furthermore, the size of routing table can be reduced in intermediate P devices, because the forwarding of IPv4 service traffic follows the IPv6 routing table.  

I am guessing that the framework draft would be in 6MAN.
[Chongfeng]: Currently, the framedoument is not in 6man, since this document does not define any new spec in it.

Thanks 

Gyan

Best regards
Chongfeng

On Thu, Jan 19, 2023 at 12:10 AM Gyan Mishra <[e-mail]> wrote:
Hi Chongfeng

 I read the draft and it’s a quite an interesting solution ipv4aas service offering.

As this relates to ipv4aas as I think it maybe a good idea to run by 6MAN and v6OPS and compare with to existing 4to6 Nat translation solutions such as 464XLAT, DSLITE etc.

Also comparatively how from a complexity and state maintenance and management overhead perspective to IPv4AAS solutions.

For the translation database on the PE nodes would that be 1-1 host entires?  I did not understand the translation or encapsulation which are different method used by the draft. 

This draft is doing a 1-1 4to6 mapping I believe which is not really translation or encapsulation.  Maybe it’s not clear to me.  

Kind Regards

Gyan

On Tue, Jan 17, 2023 at 6:37 AM Chongfeng Xie <[e-mail]> wrote:

Hello, everyone, 
We have just submitted a new draft, which is about MP-BGP extension for multi-domain IPv6-only neworking. Since this is its first submission, there must be many defects in it, we look forward to receiving more comments, suggestions and even criticism.

Best regards
Chongfeng

From: Chongfeng Xie
Date: 2023-01-17 19:33
To: internet-drafts
CC: donggz; xing; idr-chairs
Subject: Re: New Version Notification for draft-xie-idr-mpbgp-extention-4map6-00.txt

Hello, everyone, 
We have just submitted a new draft, which is about MP-BGP extension for multi-domain IPv6-only neworking. Since this is its first submission, there must be many defects in it, we look forward to receiving more comments, suggestions and even criticism.

Best regards
Chongfeng

 
From: internet-drafts
Date: 2023-01-17 19:17
To: Chongfeng Xie; Guozhen; Guozhen Dong; Xing Li
Subject: New Version Notification for draft-xie-idr-mpbgp-extention-4map6-00.txt
 
A new version of I-D, draft-xie-idr-mpbgp-extention-4map6-00.txt
has been successfully submitted by Chongfeng Xie and posted to the
IETF repository.
 
Name: draft-xie-idr-mpbgp-extention-4map6
Revision: 00
Title: MP-BGP Extension and the Procedures for IPv4/IPv6 Mapping Advertisement
Document date: 2023-01-15
Group: Individual Submission
Pages: 13
URL:            https://www.ietf.org/archive/id/draft-xie-idr-mpbgp-extention-4map6-00.txt
Status:         https://datatracker.ietf.org/doc/draft-xie-idr-mpbgp-extention-4map6/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-xie-idr-mpbgp-extention-4map6
 
 
Abstract:
   This document defines NLRI with specific AFI/SAFI combination, a new
   BGP path attribute known as the "4map6" and a set of related
   procedures, which can be used for transferring IPv4/IPv6 address
   mapping rule to support IPv4 service delivery in multi-domain
   IPv6-only underlay networks.
 
                                                                                  
 
 
The IETF Secretariat
 
 
 
_______________________________________________
Idr mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/idr
-- 

Gyan Mishra
Network Solutions Architect 
Email [e-mail]
M 301 502-1347


-- 

Gyan Mishra
Network Solutions Architect 
Email [e-mail]
M 301 502-1347