[SIPForum-discussion] INFO method

Jonathan Rosenberg jdrosen at cisco.com
Mon Sep 19 13:21:05 UTC 2005


There are specifications that define mechanisms for key exchange for 
media sessions:

http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions-12.txt

-Jonathan R.

darmil at neobee.net wrote:

> Yes, something like that. But I want to set secure communication with my mechanism between them on the MSRP level. To do that, before start of media (MSRP) I need to exchange setting information (key agreement, authentication, etc.). I believe that signalization domain is right place for such thing.
> 
> Regards,
> Darko    
> 
> Eric Burger <eburger at brooktrout.com> wrote :
> 
> 
>>No. You probably want to connect the
>>endpoints directly (like through TCP) for your private communication. &nbsp;See the
>>mechanism of MSRP or MRCPv2.
>>
>>&nbsp;
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>From: discussion-bounces at sipforum.org
>>[mailto:discussion-bounces at sipforum.org] On
>>Behalf Of Darko Milic
>>Sent: Sunday, September 18, 2005
>>3:53 PM
>>To: An open list for discussion of
>>SIP-related topics
>>Subject: Re: [SIPForum-discussion]
>>INFO method
>>
>>
>>
>>&nbsp;
>>
>>Thanks to all,
>>I've get some idea of INFO usage. As I said my intention was to send some
>>additional information after SIP dialog had been opened. This information
>>includes some cryptographic parameters, in several rounds, before media
>>communication, meaningful only for upper application (Call Control) on both
>>side, but not for human user. I believe now that INFO is appropriate
>>solution&nbsp; and that the MESSAGE request should be left for human user data.
>>Isn&#8217;t it?
>>
>>&nbsp;
>>
>>Regards, 
>>
>>Darko 
>>
>>
>>
>>&nbsp; 
>>
>>Beith, Gordon wrote: 
>>
>>INFO method is used for various mid-call communication and
>>also for SIP-T (i.e. ISUP transparency).
>>
>>It has been used for, but is not
>>recommended, DTMF communication. RFC 2833 is the recommendation for that.
>>
>>Further to this, and proprietary messages,
>>services, etc. use INFO method as well. This sounds like what you want to do
>>here. 
>>
>>&nbsp;
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>From:
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> discussion mailing list
> discussion at sipforum.org
> http://sipforum.org/mailman/listinfo/discussion
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen at cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com



More information about the discussion mailing list