The current text says we do not allow multiple Info-Packages per INFO
message. Although not stated (and I will state explicitly if we
continue to go in this direction), this nominally makes parsers easier
and makes failure handling straightforward.
I would offer the former issue is not real. Namely the way of
transporting multiple Info-Packages in an INFO message would be to
encapsulate in a multipart MIME body. However, all SIP endpoints must
support multipart MIME, so this is a non-issue.
The latter issue is quite true in theory. If I send two Info Package
bodies, and for some reason the UAS barfs on one of those bodies, the
UAS does not have a clean way of indicating which body barfed, and
both effectively get treated at the UAC as failed. The reason I
caveated this issue "in theory" is I cannot think of a situation where
this would matter. Most of these usages are all-or-nothing, which
means simply failing is OK.
Moreover, I would offer the first thing people will ask for is
transporting multiple INFO messages in a single message....
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
