Use cases for local-end set session id?

What's the use case for local ends requesting a session id? As far as I
can tell from the spec at the moment, the local end and all
intermediaries have to deal with the possibility that the remote sets
its own session id that's different from the requested one. Therefore
this feels like a feature that adds a lot of implementation complexity
and high possibility for bugs (e.g. because code assumes that it will
always get the session id it requested, but doesn't), but has little
value since it can't actually be relied on. Therefore my a-priori stance
is that it should be removed.

If there are compelling use cases for it it should at least be
simplified to "present with a string value" or missing, and not allow
null or anything else.

Received on Wednesday, 4 February 2015 18:32:37 UTC