Re: [bess] Shepherd's review of draft-ietf-bess-mvpn-expl-track

2018-02-08 Thread stephane.litkowski
Ok thanks From: Eric C Rosen [mailto:ero...@juniper.net] Sent: Wednesday, February 07, 2018 17:57 To: LITKOWSKI Stephane OBS/OINIS; draft-ietf-bess-mvpn-expl-track.auth...@ietf.org Cc: bess@ietf.org; bess-cha...@ietf.org Subject: Re: Shepherd's review of draft-ietf-bess-mvpn-expl-track On 1/16/2

Re: [bess] Shepherd's review of draft-ietf-bess-mvpn-expl-track

2018-02-08 Thread stephane.litkowski
Hi Eric, Thanks for your answers. Your proposed changes look fine to me. Regarding the RD modification, your proposal to reuse the PTA instead of tweaking the RD looks also better. Brgds, From: Eric C Rosen [mailto:ero...@juniper.net] Sent: Tuesday, February 06, 2018 21:29 To: LITKOWSKI Steph

Re: [bess] Shepherd's review of draft-ietf-bess-mvpn-expl-track

2018-02-07 Thread Eric C Rosen
On 1/16/2018 11:29 AM, Eric C Rosen wrote: “If the LIR-pF flag is set in a given PTA, the LIR flag of that PTA    SHOULD also be set.” [SLI] Why not using a MUST ? [Eric] If all the PEs support the LIR-pF flag, the procedures will work as intended even if the LIR flag is not set.  So I don't t

Re: [bess] Shepherd's review of draft-ietf-bess-mvpn-expl-track

2018-02-06 Thread Eric C Rosen
On 1/24/2018 2:25 AM, stephane.litkow...@orange.com wrote: “The procedures of [RFC6625] do not clearly state how to handle an   S-PMSI A-D route if its NLRI contains wild cards, but its PTA   specifies "no tunnel info".” [SLI] I quickly ran over RFC6625, it does not mention anything

Re: [bess] Shepherd's review of draft-ietf-bess-mvpn-expl-track

2018-01-23 Thread stephane.litkowski
Hi Eric, Andrew Thanks a lot for the updates done. Here are more comments. Overall comments: - Please add a section that contains all the abbreviations expansions: that may help non expert people to follow the acronyms without looking for the first reference in the text. [Eric] This is

Re: [bess] Shepherd's review of draft-ietf-bess-mvpn-expl-track

2018-01-18 Thread Dolganow, Andrew (Nokia - SG/Singapore)
inline with “ad>” From: Eric Rosen Date: Wednesday, January 17, 2018 at 12:31 AM To: "stephane.litkow...@orange.com" , "draft-ietf-bess-mvpn-expl-track.auth...@ietf.org" Cc: "bess@ietf.org" , "bess-cha...@ietf.org" Subject: Re: Shepherd's review of draft-ietf-bess-mvpn-expl-track Resent-From

Re: [bess] Shepherd's review of draft-ietf-bess-mvpn-expl-track

2018-01-18 Thread Eric C Rosen
I need to make a correction to my previous note. From the draft: The explicit tracking procedures do not allow an ingress node to "see" past the boundaries of the segmentation domain. This particular problem is not further addressed in this revision of this document. From

Re: [bess] Shepherd's review of draft-ietf-bess-mvpn-expl-track

2018-01-16 Thread Eric C Rosen
Thanks for your review.  I have posted revision -04 which I believe addresses your substantive comments. On 1/3/2018 8:01 AM, stephane.litkow...@orange.com wrote: Hi, As shepherd of this document, please find below some comments that I have: Overall comments: -Please add a section that cont

[bess] Shepherd's review of draft-ietf-bess-mvpn-expl-track

2018-01-03 Thread stephane.litkowski
Hi, As shepherd of this document, please find below some comments that I have: Overall comments: - Please add a section that contains all the abbreviations expansions: that may help non expert people to follow the acronyms without looking for the first reference in the text. -