Re: [dispatch] New Version Notification for draft-bakker-dispatch-3gpp-ims-xml-body-handling-00.txt

[Gonzalo Camarillo <[e-mail]>]

Hi John Luc,

> Today, indeed, "3gpp-ims+xml" bodies with disposition type "3gpp-alternative-service" are carried in SIP responses while "3gpp-ims+xml" bodies with disposition type "3gpp-service-info" are carried in SIP requests.
> I don't know if that "will always" be the case.

right, everybody I have asked about this also tells me what you say
above. You can distinguish between those two cases by just checking
whether it is a request or a response. The 3GPP specs seem to confirm
that is the case as well. Therefore, what you are saying is that based
on the *current* requirements and use cases that have been discussed so
far, this draft is not needed.

With respect to potential future cases where you would carry one of the
disposition types in both requests and responses, nobody has given any
example of those, at least yet.

In any case, one of the main objections we have seen from the dispatch
community is that this has been presented as an already-made solution
that is already implemented and, thus, could not really be changed much
even if the IETF decided to work on it. But given your answer above, it
seems we do not need this solution for the *current* requirements and
use cases. So, the backward compatibility problem goes away because if
there were *new* requirements or use cases at some point , we could work
on a solution from scratch.

Am I missing something here?

Cheers,

Gonzalo