Re: INFO usage: relationship of package bodies to those of other requests

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I was using that as an example, and I think you have missed my question.

Let me rephrase in more general terms.

If a define MIME type that is appropriate for use in an info package,
and negotiate the use of that package in a particular dialog:

-	can I use bodies of that MIME type in other messages in the same
dialog?
-	is that usage entirely and absolutely independent of the info
package use?

Regards

Keith

> -----Original Message-----
> From: sipping-bounces@xxxxxxxx 
> [mailto:sipping-bounces@xxxxxxxx] On Behalf Of Paul Kyzivat
> Sent: Friday, October 24, 2008 2:56 PM
> To: DRAGE, Keith (Keith)
> Cc: sipping@xxxxxxxx
> Subject: Re:  INFO usage: relationship of package 
> bodies to those of other requests
> 
> 
> 
> 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
> 
_______________________________________________
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

[Index of Archives]     [IETF Announce]     [IETF Discussion]     [Linux SCSI]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Big List of Linux Books]

  Powered by Linux