Hi Rajiv,
Thanks for these kind words.
Generally speaking, we should design for efficiency. Furthermore, we should
engineer for future requirements. For example, in the future, service providers
may require longer SID lists (5 or more!). We should plan for that today.
Likewise, in the future, people may deploy new applications that emit short
packets. We should also plan for that today.
If we don't plan for future requirements, obsolescence will be much closer than
we expect.
Ron
Juniper Internal
> -----Original Message-----
> From: spring <[email protected]> On Behalf Of Rajiv Asati (rajiva)
> Sent: Thursday, March 28, 2019 11:37 AM
> To: [email protected]
> Cc: [email protected]
> Subject: [spring] IPv6-compressed-routing-header-crh
>
> Hi Ron,
>
> Very Interesting idea that you presented during SPRING session today. Seems
> useful.
>
> Two comments/clarification -
>
> 1. One of the slides indicated that small packet size on the Internet was
> ~500B
> and calculated ~10% due to Routing EH overhead accordingly. Of course, if we
> look at mid packet size (800-1000B) or large packet size (1000~1400B), then
> the overhead would be a lot less.
>
> We should also look at the % mix of small packets vs mid vs large size to
> calculate the impact. If mid to large packets were dominant (say, as much as
> >70% given >80% of traffic is video (ABR etc) per the latest VNI studies ),
> >then
> the overhead impact due to non-compressed SID usage on the traffic would
> be even less over all.
>
> 2. Also, what % of savings do we get by using compressed RH vs non-
> compressed RH ? 24B vs 64B per packet !!
>
>
> Cheers,
> Rajiv
>
> _______________________________________________
> spring mailing list
> [email protected]
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_spring&d=DwICAg&c=HAkYuh63rsuhr6
> Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=Fch9FQ82sir-BoLx84hKuKwl-
> AWF2EfpHcAwrDThKP8&m=jmZxWm2Aql61pHCtvKteTsWzTqqt883W1s5m4
> Hg4Fxg&s=Jd6XyAybfJQVqups1svIV2qgpN8t39yQZOjL0HT5UZw&e=
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
