Re: [bess] Question regarding RFC6625 and this draft-->//RE: I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt

2019-01-24 Thread Xiejingrong
@ietf.org Subject: RE: [bess] Question regarding RFC6625 and this draft-->//RE: I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt Robert, You may want to leave the previous tunnel (if it is no longer needed for other traffic). E.g., sending an mldp label withdrawal or withdrawing a Leaf

Re: [bess] Question regarding RFC6625 and this draft-->//RE: I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt

2019-01-24 Thread Jeffrey (Zhaohui) Zhang
Cc: Xiejingrong ; draft-ietf-bess-mvpn-expl-tr...@ietf.org; bess@ietf.org Subject: Re: [bess] Question regarding RFC6625 and this draft-->//RE: I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt Hi Jeffrey, Isn't this just a matter of how you would be implementing "tunneling"

Re: [bess] Question regarding RFC6625 and this draft-->//RE: I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt

2019-01-24 Thread Robert Raszuk
gt; > To: Jeffrey (Zhaohui) Zhang ; > draft-ietf-bess-mvpn-expl- > > tr...@ietf.org > > Cc: bess@ietf.org > > Subject: RE: Question regarding RFC6625 and this draft-->//RE: [bess] I-D > > Action: draft-ietf-bess-mvpn-expl-track-13.txt > > > > Hi Jeffrey, >

Re: [bess] Question regarding RFC6625 and this draft-->//RE: I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt

2019-01-23 Thread Jeffrey (Zhaohui) Zhang
hang ; draft-ietf-bess-mvpn-expl- > tr...@ietf.org > Cc: bess@ietf.org > Subject: RE: Question regarding RFC6625 and this draft-->//RE: [bess] I-D > Action: draft-ietf-bess-mvpn-expl-track-13.txt > > Hi Jeffrey, > > Thanks for the explaination. > I have the same un

Re: [bess] Question regarding RFC6625 and this draft-->//RE: I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt

2019-01-23 Thread Xiejingrong
draft-ietf-bess-mvpn-expl-tr...@ietf.org Cc: bess@ietf.org Subject: RE: Question regarding RFC6625 and this draft-->//RE: [bess] I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt Hi Jingrong, You're right that to avoid disruption and duplication a switchover delay is needed on th

Re: [bess] Question regarding RFC6625 and this draft-->//RE: I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt

2019-01-23 Thread Jeffrey (Zhaohui) Zhang
9 8:47 PM > To: Jeffrey (Zhaohui) Zhang ; draft-ietf-bess-mvpn-expl- > tr...@ietf.org > Cc: bess@ietf.org > Subject: RE: Question regarding RFC6625 and this draft-->//RE: [bess] I-D > Action: draft-ietf-bess-mvpn-expl-track-13.txt > > Hi Jeffrey, > > The sender PE need to work o

Re: [bess] Question regarding RFC6625 and this draft-->//RE: I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt

2019-01-22 Thread Xiejingrong
Message- From: Jeffrey (Zhaohui) Zhang [mailto:zzh...@juniper.net] Sent: Saturday, January 12, 2019 3:29 AM To: Xiejingrong ; draft-ietf-bess-mvpn-expl-tr...@ietf.org Cc: bess@ietf.org Subject: RE: Question regarding RFC6625 and this draft-->//RE: [bess] I-D Action: draft-ietf-bess-mvpn-e

Re: [bess] Question regarding RFC6625 and this draft-->//RE: I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt

2019-01-11 Thread Jeffrey (Zhaohui) Zhang
Jeffrey > -Original Message- > From: Xiejingrong [mailto:xiejingr...@huawei.com] > Sent: Thursday, January 10, 2019 11:10 PM > To: draft-ietf-bess-mvpn-expl-tr...@ietf.org > Cc: bess@ietf.org > Subject: Question regarding RFC6625 and this draft-->//RE: [bess] I-D Action: > d

[bess] Question regarding RFC6625 and this draft-->//RE: I-D Action: draft-ietf-bess-mvpn-expl-track-13.txt

2019-01-10 Thread Xiejingrong
Hi, I have a question regarding RFC6625 and this draft, since this draft is based on the RFC6625. In RFC6625 section "3.2.1 Finding the match for (C-S,C-G) for Data Reception": It defined the rules for Finding the matched S-PMSI A-D route for a (C-S,C-G) state on a receiver site PE. It seems