Hi Guozhen,
I have a few questions on the draft.
a) The introduction section says that this document defines "a new type of
segment", is it a new type of segment or a new type of SID behavior?
b) I don't quite understand how encapsulation or translation processing of IPv4
packets E/T is distinguished by the identity of ARG field, could you explain it?
c) What's the relationship between the new End.4map6 and the existing VPN
service SIDs defined in RFC9252, can they be used together?
Regards
Yao
Original
From: guozhen.dong <guozhen.d...@foxmail.com>
To: spring <spring@ietf.org>;
Date: 2025年07月10日 18:49
Subject: [spring] Request for more discussion/feedback on
draft-dong-spring-sr-4map6-segments
_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-le...@ietf.org
Hi, all,
We posted the -04 revision of the
https://datatracker.ietf.org/doc/draft-dong-spring-sr-4map6-segments/ a few
weeks ago.
This draft defines a new type of segment for Segment Routing, 4map6 segment,
which is an IPv4/IPv6 conversion function based on stateless mapping rules
running in PE nodes for the delivery of IPv4 services over IPv6-only network.
The new SID mainly deals with how to generate new IPv6 headers based on the
information of IPv4 packets.
We would like to request more feedback/suggestions/discussions on this draft,
so that we can further improve it and progress the document.
Best regards,
Guozhen
_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-le...@ietf.org
