Hi Yao，
Apologies for my late reply. Please see my feedback inline[Guozhen].
在 2025年7月11日 10:50，[email protected] 写道：
Hi Guozhen,
I have a fewquestions 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?
[Guozhen] We have defined a new 4map6 segment type, with the purpose of
providing mapping rule-based conversion and transmission for IPv4 packets over
IPv6-only underlay networks. Simultaneously, we have defined the corresponding
SID behavior, End.4map6, which specifies the stateless mapping,
encapsulation/decapsulation, and other operations to be executed by network
nodes when processing this segment.
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?
[Guozhen] The ARG field contains a behavior identifier used to indicate whether
the node should perform Encapsulation or Translation. The structure of the
4map6 SID is:
IPv6 Prefix + E/T +IPv4 Address
E/T is an identifier bit within the ARG field used to specify the processing
method:
If it is encapsulation, the IPv4 data packet is encapsulated within an IPv6
packet.
If it is translation, the IPv4 address is translated into anIPv6 address.
When a PE node processes a data packet, it performs thecorresponding operation
based on the E/T identifier in the ARG field.
c) What's the relationship between thenew End.4map6 and the existing VPN
service SIDs defined in RFC9252, can they be used together?
[Guozhen] In this draft, End.4map6 is primarily used to implement IPv4-IPv6
address mapping and forwarding over an IPv6-only underlay network. Whereas the
SIDs in RFC9252 are mainly used to provide BGP overlayservices, such as L3VPN
and EVPN in SRv6 networks. They can coexist in the same network and even on the
same node. They belong to different endpoint behaviors and they can be
advertised separately via the BGP Prefix-SID attribute and carried within the
SRv6 Service TLV. If needed, we can subsequently provide furtherclarification
on how 4map6 SID and VPN SIDs can cooperate in practice.
Regards
Yao
Original
From:guozhen.dong [email protected]
To:spring [email protected];
Date:2025年07月10日 18:49
Subject:[spring] Request for more discussion/feedback on
draft-dong-spring-sr-4map6-segments
_______________________________________________
[email protected]
[email protected]
Hi, all,
We posted the -04 revision of
thehttps://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 -- [email protected]
To unsubscribe send an email to [email protected]
