[xiph-rtp] header caching and chaining
Ralph Giles
giles at xiph.org
Sun Apr 10 19:50:22 PDT 2005
On Sun, Apr 10, 2005 at 11:18:40PM +0100, Phil Kerr wrote:
> >Also, it occured to me that while storing actual info in the SSRC would
> >be an abuse, switching on SSRC,ident pairs might be ok. I don't suggest
> >that this is a good idea, but it does leave lots of headroom.
> >
> The SSRC needs to be a random value. Having it as a derived value will
> be against RTP specs.
That's what I was saying. It can't be a derived value, but things in the
SDP could be derived from it. Or is that also contradicted?
> >I'd also suggest s/hash/md5/ just so it's possible to change the hash
> >later.
> >
> MD5 is 128 bit, a hash can be different sizes. Key could be a better
> description.
To be able to verify the hash you need to know the algorithm.
> Also Aaron's little SDP example above is 770 octets, isn't the maximum
> SDP message length 1000 octets? This chaining mechanism could be
> limited if it passes its data in SDP like this.
Hmm. removing the indirection as I suggested would help, but only so
much. Using the implicit url mapping Aaron proposed would help a lot
more. Do you have another suggestion?
-r
More information about the xiph-rtp
mailing list