Re: [MMUSIC] RFC 5245: ice-ufrags of length 256 vs stun maximum username length of 512 bytes

[Philipp Hancke <[e-mail]>]

> Apparently a simple fix would be to make offered ice-ufrag max length in
> ICE-bis 255 (instead of 256).
>
> This would even be nicely backward-compatible since the other (legacy)
> endpoint can still offer 256 chars long ufrag and we would not end up
> exceeding the max length for STUN username.

And on the other side, if an ice-bis endpoint receives a ice-ufrag of 
length 256 from a "legacy" endpoint, it can still restrict it's reply to 
255 chars.
This might be easier to describe as "accept 256 chars, but do not send 
more than 255 chars".

That seems better than trying to figure out what should happen when we 
end up with 513 bytes, thanks.

philipp