Re: [AVTCORE] Review of draft-ietf-avtcore-rfc5764-mux-fixes-02

[Paul Kyzivat <[e-mail]>]

On 9/17/15 4:10 PM, Marc Petit-Huguenin wrote:

>> K. Section 3:
>>
>> When new values or ranges are added, they MUST be tested in
>> ascending order.
>>
>
> This text should not talk about adding new values/ranges. Changed the text to:
>
> "The various range values for the first byte MUST be tested in ascending order."

I just reviewed this, and I have no idea what it means. I see nothing 
about Figure 3 that requires testing to be done in a particular order. 
The *text* suggests an if/then/else or switch statement implementation. 
But the code generated for a switch statement may well be a lookup table 
and so have no particular ordering.

The only time ordering would matter would be if the ranges overlapped. 
And IIUC the goal here that the ranges *not* overlap.

	Thanks,
	Paul