Fanghong,
Please see zzh4> below.
Juniper Business Use Only
From: duanfanghong
Sent: Saturday, June 18, 2022 5:06 AM
To: Jeffrey (Zhaohui) Zhang ; bess@ietf.org
Subject: RE: [bess] A new draft for MVPN in IPv6-only network.
[External Email. Be cautious of content]
Hi Jeffrey,
Please see
Hi Jeffrey,
Please see Dfh4> below.
Thanks.
Fanghong
From: Jeffrey (Zhaohui) Zhang [mailto:zzhang=40juniper@dmarc.ietf.org]
Sent: Saturday, June 18, 2022 6:36 AM
To: duanfanghong ; bess@ietf.org
Subject: RE: [bess] A new draft for MVPN in IPv6-only network.
HI Fanghong,
Let me pull up
HI Fanghong,
Let me pull up the points up here at the top.
Dfh3> I think you were making a mistake, RT-constrain is an extra procedure
and cannot run without obsoleting the propagating-along-reverse-path-of-I-PMSI
procedure. So, I think the solution you considered is with too many
Hi Jeffrey,
Please see Dfh3> below.
Thanks.
Fanghong
From: Jeffrey (Zhaohui) Zhang [mailto:zzhang=40juniper@dmarc.ietf.org]
Sent: Thursday, June 16, 2022 10:17 AM
To: duanfanghong ; bess@ietf.org
Cc: Xiejingrong (Jingrong) ; Gengxuesong (Geng Xuesong)
; Wangheng (MCAST, P)
Subject: RE:
Hi Fanghong,
Please see zzh3> below.
Juniper Business Use Only
From: duanfanghong
Sent: Wednesday, June 15, 2022 3:36 AM
To: Jeffrey (Zhaohui) Zhang ; bess@ietf.org
Cc: Xiejingrong (Jingrong) ; Gengxuesong (Geng Xuesong)
; Wangheng (MCAST, P)
Subject: RE: [bess] A new draft for MVPN in
Hi Jeffrey,
Please see Dfh2> below.
Thanks.
Fanghong
From: Jeffrey (Zhaohui) Zhang [mailto:zzhang=40juniper@dmarc.ietf.org]
Sent: Wednesday, June 15, 2022 11:41 AM
To: duanfanghong ; bess@ietf.org
Cc: Xiejingrong (Jingrong) ; Gengxuesong (Geng Xuesong)
; Wangheng (MCAST, P)
Subject: RE:
Hi Fanghong,
Please see zzh2> below.
Juniper Business Use Only
From: duanfanghong
Sent: Sunday, June 5, 2022 10:55 PM
To: Jeffrey (Zhaohui) Zhang ; bess@ietf.org
Cc: Xiejingrong (Jingrong) ; Gengxuesong (Geng Xuesong)
; Wangheng (MCAST, P)
Subject: RE: [bess] A new draft for MVPN in
Hi Jeffrey,
Please see Dfh> below.
Thanks.
Fanghong
From: Jeffrey (Zhaohui) Zhang [mailto:zzhang=40juniper@dmarc.ietf.org]
Sent: Friday, June 3, 2022 4:06 AM
To: duanfanghong ; bess@ietf.org
Cc: Xiejingrong (Jingrong) ; Gengxuesong (Geng Xuesong)
; Wangheng (MCAST, P)
Subject: RE: [bess]
Hi Fanghong,
Please see zzh> below.
Juniper Business Use Only
From: duanfanghong
Sent: Thursday, June 2, 2022 6:50 AM
To: Jeffrey (Zhaohui) Zhang ; bess@ietf.org
Cc: Xiejingrong (Jingrong) ; Gengxuesong (Geng Xuesong)
; Wangheng (MCAST, P)
Subject: RE: [bess] A new draft for MVPN in
Hi Jeffrey,
In the draft I published, we focus on the problems and solutions of MVPN in
IPv6-only infrastructure and dual-stack infrastructure. Although the
"source-as" field length problem overlaps with the one mentioned in your draft,
I think it does not prevent moving our draft forward.
1．
Hi Fanghong,
My understanding of the main problem that is pointed out in your draft is that
the "source-as" field cannot hold an IPv6 address that is required for
non-segmented tunnels in case of IPv6 infrastructure.
The draft I referred to also pointed out that problem, and gave a solution
Hi Jeffrey,
I have read your draft carefully, as you mentioned in this draft, it is a less
optimal solution for PE to PE C-Multicast signaling.
In the draft I just published, we describe IPv6-only infrastructure and
dual-stack infrastructure issues and solutions for regular option B scenario
Hi Fanghong,
It seems that
https://datatracker.ietf.org/doc/html/draft-zzhang-bess-mvpn-evpn-cmcast-enhancements-01#section-1.3
talked about the problems and a more general solution.
That draft also has other enhancements considerations. It has stalled but looks
like we should get it going.
Hi All,
MVPN(RFC 6513/RFC 6514/RFC 6515) faces some problems in IPv6-only networks,
especially in the non-segmented inter-AS scenario and IPv4 to IPv6 migration
scenario.
We have published a new draft
https://datatracker.ietf.org/doc/draft-duan-bess-mvpn-ipv6-infras/, aiming to
solve
14 matches
Mail list logo
