Hello everyone,
We have just submitted a new draft, which is about 4map6 Segment for IPv4
Service delivery over IPv6-only underlay networks. Since this is the first
submission, there must be many defects in it, we look forward to receiving more
comments, suggestions and even criticism.
——
Hi Guozhen and authors,
Thanks for introducing your I-D.
I have read this I-D roughly, and noticed the following description in section
3:
When a new IPv6 packet arrives at PE2, PE2 parses its Locator part.
If it matches the IPv6 mapping prefix instantiated by itself, it
decapsulates th
Hi Working group,
As previously mentioned in the mail list
https://mailarchive.ietf.org/arch/msg/spring/5iLxCBmOrSNqOafiCRYy3BZGvkg/,
we've finished the work "to write a draft [DRAFT] to explain in detail about
the impacts of SRv6-multicast approaches to SRv6 architecture in general for
the WG
Hi Huaimo,
Thanks for drawing the attention on this document.
Here are some review comments for your consideration.
1. In section 3.1:
A Repair List RL is obtained based on the path. It is one of the followings:
o RL = if the path does not go through PE A; Or
o RL = if the
Hi Weiqiang,
Thanks for addressing my comments made on IETF 115 meeting, it is good to see
this version refers to draft-ietf-spring-resource-aware-segments.
This document focuses on introducing resource guarantee to SR policies, which
is one of the use cases of resource-aware segments. It may b
