Thanks - I was trying to understand the basis of your objection. You appear to be against variable packet formats in an form (which is your choice, but I don't understand how we can develop protocols that aren't instantly ossified that way).
You also seem to think security is optional. It thought those days were over as well. Fair enough. Joe On 7/21/2016 3:13 PM, Dino Farinacci wrote: >> These are data plane functions for ingress/egress processing, which >> already does things like IPsec tunnel mode, IP in IP, IP in UDP in IP, etc. > All with fix length headers. These packet formats allow the hardware to do a > few input checks in fixed places. > > Crypto is way different and a very complex but it is a "can't ship without > it" feature. > >> I'm not sure about the others, but why is GUE so complex? It would still > Jump, test type, decide if you support it, validate the value field, do the > feature of the type (if you support it), then add length, go to next type, > rinse and repeat. > > And that doesn't even consider if there are sequencing requirements among the > TLVs. > >> allow data plane processing using existing IP forwarding, including DPI >> access to port numbers. > Not following and I think not relevant. > > Dino _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
