On 2/9/2017 12:05 PM, Tom Herbert wrote:
>> Otherwise, the only way to know where the Nth TLV field starts is to
>> parse through the N-1th, which - recursively - reduces to requiring
>> iterative processing.
>>
> Yes, and iterative processing of an open ended list of TLVs is still
> hard to do in hardware _and_ software and in fact is an obvious DOS
> vector. Last I checked OpenFlow, P4, and eBPF don't fully implement
> loops that are needed to process an arbitrary list of TLVs (they
> resolved this through some hackery and artificial constraints). The
> unlimited flexibility of TLVs does not come without a cost...
Wouldn't the obvious solution be to let the entire encapsulation
protocol be negotiated by the endpoints anyway?
I.e., take the specification of that protocol out of purview of NVO3?
The only thing NVO3 needs to do is:
- develop a negotiation protocol
- indicate how to use some subset of encapsulations
If the key issue here is the debate between bitfield and TLV, that
should be taken off the table as an issue.
Joe
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
