Re: [AVT] 2833bis

[Henning Schulzrinne <hgs@cs.columbia.edu>]

>     "Some events are actually states, i.e., the appearence of a   |
>      different named event implies the end of the previous        |
>      state. Thus, for named RTP events labeled "state" in Tables  |
>      1 through 5, sending of a packet with the "E" bit set is     |
>      OPTIONAL. State events are sent with zero duration."
>
> Does this mean that once I send an RFC 2833 "state" event, then any 
> other RFC
> 2833 event will obsolete that state, or is it only another "state" 
> event that
> will negate it ? It would seem that only "state" events should be able to
> obsolete another "state" event. Furthermore, it's also not clear to me 
> whether
> such "state" events need to be divided in groups, so that e.g. state 
> events A,
> and B can change each other, and C and D can change each other, but 
> neither A or
> B can affect C or D.

Interesting question. So far, the only states are the ABCD states and 
on/off hook. In general, I would agree that state groups make the most 
sense. I'll just use the lowest event number as the state group 
identifier in the table, to avoid yet another namespace.

> Also, I noticed that off-hook and on-hook in table 4 are not marked as 
> states. I
> assume that's an error.

Yes.

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt