Subject: Re: [Sipping] draft-johnston-sipping-cc-uui-05

From: Alan Johnston <[email-masked]>
Date: Mon, 01 Dec 2008 15:51:34 -0600

Cullen,

That is the standard way S/MIME is used with SIP.  Of course, extensions 
to the way SIP and S/MIME are used together could be developed, but this 
draft would not be the place to do this.

The better way to do this for this particular application would probably 
be to encrypt the UUI before passing it to the SIP stack, but this also 
would be out of scope for this draft.

Thanks,
Alan

Cullen Jennings wrote:
>
> So you want the new header to be tunneled in a body part of the SIP 
> message?
>
> On Nov 27, 2008, at 12:00 PM, Alan Johnston wrote:
>
>> Cullen Jennings wrote:
>> > <snip>
>> > Uh, I can understand how S/MIME protects a body but seems like a bit
>> > more might be needed to explain how it protects a header.
>> >>
>>
>> Is the text in RFC 3261 not clear?
>>
>>     23.4 SIP Header Privacy and Integrity using S/MIME: Tunneling SIP
>>
>> If not, I doubt this draft is the right place to clarify it, but perhaps
>> in another draft.
>>
>> Thanks,
>> Alan
>>
>>
>> >>
>> >>
>> >> Thanks,
>> >> Alan
>> >>
>> >>
>> >> >>
>> >> >
>> >> > Cullen in my individual contributor role
>> >> >
>> >> >
>> >> >
>> >>
>> >> _______________________________________________
>> >> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
>> >> This list is for NEW development of the application of SIP
>> >> Use [email-masked] for questions on current sip
>> >> Use [email-masked] 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 [email-masked] for questions on current sip
>> Use [email-masked] 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 [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP