Subject: Re: [siprec] #39: Add text to describe limitations of using SIP Proxy as SRC

From: "siprec issue tracker" <[email-masked]>
Date: Mon, 27 Sep 2010 15:59:32 -0000

#39: Add text to describe limitations of using SIP Proxy as SRC
--------------------------------------------------+-------------------------
 Reporter:  andrew.hutton@…                       |       Owner:  andrew.hutton@…                     
     Type:  enhancement                           |      Status:  new                                 
 Priority:  minor                                 |   Milestone:                                      
Component:  Architecture                          |     Version:                                      
 Severity:  -                                     |    Keywords:                                      
--------------------------------------------------+-------------------------

Comment(by andrew.hutton@…):

 I propose to add a section 4.1.5 with the title "SIP Proxy cannot be an
 SRC" or something similar.

 I propose the following text for this section.

 "A SIP Proxy is unable to act as an SRC because it does not have access to
 the media and therefore has no way of enabling the delivery of the
 replicated media to the SRS. If a SIP Proxy attempted to use SIP 3PCC
 mechanisms to deliver the media stream to the SRS it would not be able to
 and maintain compliance with the requirements as specified in [draft-ietf-
 siprec-req]. For example it would not be possible to meet REQ-32 which
 states:

 If the Communication Session is encrypted, the Recording Session MUST use
 different keys"

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/siprec/trac/ticket/39#comment:1>
siprec <http://tools.ietf.org/siprec/>