DRAGE, Keith (Keith) wrote:
I believe that ISUP interworking as defined in ITU-T Q.1912.5 can put an
ISUP body in INVITE requests as well as INFO requests. If we now came to
define a package for that usage, what is the relationship between the
package negotiation and any bodies transmitted in requests other than
INFO?
Is it none, i.e. they just happen to share the same MIME type, and this
is allowed?
The current usage is grandfathered.
If there is new work to update the specs for ISUP interworking to use
this new info package mechanism, then it will have to conform to the
info package spec for the parts of the usage that utilize INFO. The same
revision will have to deal with any revisions that it deems necessary to
the conveyance of ISUP info in INVITE requests and responses. I don't
think we can concern ourselves with that here.
But at least the ISUP work was careful to define a Content-Disposition
("signal") for use with their ISUP bodies, so further work may not be
needed.
Thanks,
Paul
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP
