Re: [spring] Results of SR compression analysis?

2021-03-10 Thread Darren Dukes (ddukes)
(hit send too soon) We should now work toward the targets Weiqiang mentioned during the meeting for an April/May submission of the analysis text. Thanks! Darren On 2021-03-10, 2:40 PM, "Darren Dukes (ddukes)" wrote: Hi Fan, I fixed the link in the minutes. https://mailarchive.ietf.org/arch/m

Re: [spring] Results of SR compression analysis?

2021-03-10 Thread Darren Dukes (ddukes)
Hi Fan, I fixed the link in the minutes. https://mailarchive.ietf.org/arch/msg/srcomp/ryOuYQbquExcmdi8a9KSNy4FAV4/ Thanks for drawing that to our attention. That analysis was done on Feb 11 but the design team decided not to review and submit any of its content (except for the structure) before

[spring] I-D Action: draft-ietf-spring-sr-service-programming-04.txt

2021-03-10 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Packet Routing in Networking WG of the IETF. Title : Service Programming with Segment Routing Authors : Francois Clad

Re: [spring] FW: New Version Notification for draft-bonica-6man-comp-rtg-hdr-09.txt

2021-03-10 Thread Stefano Salsano
Il 2020-04-30 16:31, Ron Bonica ha scritto: Stefano, We have a LINUX implementation that we can share with you. Also, some students from Harvey Mudd University have put together a benchmarking methodology. I will contact you off-list. Hi Ron, this topic has come back to my mind when going

[spring] Results of SR compression analysis?

2021-03-10 Thread Yangfan (IP Standard)
Hi SPRING, First of all, I really appreciate the SR compression design team for their hard work. But I found out the analysis results are empty in the analysis draft[1] as Xuesong pointed out at the meeting. I tried to get the answer of why this is empty from the meeting minutes(https://codimd

Re: [spring] RTG-DIR review of draft-ietf-bess-srv6-services-05

2021-03-10 Thread Ketan Talaulikar (ketant)
Hi Sasha, Indeed your version is better and we’ll put that in on the next draft update. Thanks, Ketan From: Alexander Vainshtein Sent: 10 March 2021 19:40 To: Ketan Talaulikar (ketant) Cc: draft-ietf-bess-srv6-services@ietf.org; b...@ietf.org; spring@ietf.org; Swadesh Agrawal (swaagraw) ;

Re: [spring] RTG-DIR review of draft-ietf-bess-srv6-services-05

2021-03-10 Thread Alexander Vainshtein
Ketan, From my POV an even better version would be “Usage of multicast trees as P-tunnels is outside the scope of this document”. But your proposed text is also OK with me. Regards, Sasha Office: +972-39266302 Cell: +972-549266302 Email: alexander.vainsht...@rbbn.com From: Ketan Talaulik

Re: [spring] RTG-DIR review of draft-ietf-bess-srv6-services-05

2021-03-10 Thread Ketan Talaulikar (ketant)
Hi Sasha, My apologies and I think I understand your point. Would the following text change convey the right meaning? s/ The setup of multicast trees for use as P-tunnels is outside the scope of this document / The setup and usage of multicast trees as P-tunnels is outside the scope of this do

Re: [spring] RTG-DIR review of draft-ietf-bess-srv6-services-05

2021-03-10 Thread Rabadan, Jorge (Nokia - US/Mountain View)
Hi Biswas, “now say variable part starts at 112 (transposition offset), transposition length is 8 and locator length is 96 (FUNC+ARG length is 20). According to section 4 we should transpose 8 bits from offset 112 to label field in mp_reach_nlri. But section 5.1 says that we should transpose FU

Re: [spring] RTG-DIR review of draft-ietf-bess-srv6-services-05

2021-03-10 Thread Manomugdha Biswas
Hi Ketan, According to section “4. Encoding SRv6 SID information" for efficient encoding, variable part of SRv6 SID is transposed to label field. This draft has given an example of variable part as FUNC+ARG. Section “5.1. IPv4 VPN Over SRv6 Core" says that Label field of IPv4-VPN NLRI

Re: [spring] RTG-DIR review of draft-ietf-bess-srv6-services-05

2021-03-10 Thread Alexander Vainshtein
Ketan, Lots of thanks for posting an updated version of the draft. I have looked it up, and it seems that the majority of my review comments have been addressed. I defer to the Routing ADs regarding my metadata comments. One point that, IMHO, requires additional clarification, is restriction of