Re: [siprec] New Version Notification for draft-yan-siprec-msrp-recording-01.txt

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 03 July 2014 16:08 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B84B1A0356 for <siprec@ietfa.amsl.com>; Thu, 3 Jul 2014 09:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sf41qnapuNTI for <siprec@ietfa.amsl.com>; Thu, 3 Jul 2014 09:08:41 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id 081561A0330 for <siprec@ietf.org>; Thu, 3 Jul 2014 09:08:40 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta07.westchester.pa.mail.comcast.net with comcast id MrjW1o0041c6gX857s8gYe; Thu, 03 Jul 2014 16:08:40 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta23.westchester.pa.mail.comcast.net with comcast id Ms8g1o00G3ZTu2S3js8gLY; Thu, 03 Jul 2014 16:08:40 +0000
Message-ID: <53B58008.9070507@alum.mit.edu>
Date: Thu, 03 Jul 2014 12:08:40 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Simon Farrow <simon.farrow@stancilcorp.com>, siprec@ietf.org
References: <20140528220324.16934.76369.idtracker@ietfa.amsl.com> <53865EEC.7000605@alum.mit.edu> <538E1806.9040908@alum.mit.edu> <53AC4B1A.9050707@alum.mit.edu> <000601cf963e$e742b0c0$b5c81240$@stancilcorp.com>
In-Reply-To: <000601cf963e$e742b0c0$b5c81240$@stancilcorp.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1404403720; bh=y6V3ZdovvRyvwTIr0XdG0fzy0bJ7O8FAsnjNgGcoBzc=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Q6DNc55cDftUtXulJodmOkEjwGfgRwfCMvwwkpzjAdTJxevz9BSSqch5BQmLnFADt dUeCtxvKqNtZ/4mzyDcDGn9CLJMugAZOyXL16BVswHQbMA8w3jMfYgdkZLqhS4dckR VnnHC5EoXnzsswtKaa1TWtau1R/7xuzGhPbJjg5MPDAthofpHgUfRkP3uWb2UI27O0 xesBEGpbWX4bBwi7bD0PbIwI85bknGRAmv5NlYwJDN3aBquLfpdvIdONWYR6colEeQ 9o6AadVYX3HWi5/ETE3uU/D6tQh2PeG5Leqb2Q/Tu5kk34BadqP+p+4O2g56GvcTJk f4QL/yl+Vp0Ig==
Archived-At: http://mailarchive.ietf.org/arch/msg/siprec/ZU4V55O86sDIMK9yN-Q7_fU9GH4
Subject: Re: [siprec] New Version Notification for draft-yan-siprec-msrp-recording-01.txt
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec/>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jul 2014 16:08:42 -0000

On 7/2/14 5:45 PM, Simon Farrow wrote:
> Paul
>
> Sorry for the delay in getting to the document.
>
> Is encryption out scope for this document (as it is mentioned in the Siprec
> Protocol document).

It isn't out of scope. See the Security Considerations of the protocol 
document.

> If so I think that should be stated but we might need to
> take into consideration RFC 5547 (File Transfer) mentions secured MIME
> (S/MIME) RFC 3851 while the protocol document only mentions RFC 3711, 5124
> and 4568.

File transfer may be a special case, but maybe not.

If the file content is secured with S/MIME, then it is my expectation 
that this protection would be retained in the recording. That may well 
mean that the SRS can't understand the content of the recorded file.

Do you think that we need additional language about this case?

	Thanks,
	Paul

> Once again thanks to you and Michael on preparing this document.
>
> Simon Farrow
> Director of Engineering
>
> Stancil Corporation
> 2644 South Croddy Way
> Santa Ana
> CA 92704
>
> Tel: 1-714-546-2002 ext 4311
> http://www.stancilcorp.com
> simon.farrow@stancilcorp.com
>
> -----Original Message-----
> From: siprec [mailto:siprec-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: Thursday, June 26, 2014 9:32 AM
> To: siprec@ietf.org
> Subject: Re: [siprec] New Version Notification for
> draft-yan-siprec-msrp-recording-01.txt
>
> Trying one more time. Please!!!
>
> On 6/3/14 2:46 PM, Paul Kyzivat wrote:
>> Can I get some people in the wg to review and comment on this version?
>>
>>       Thanks,
>>       Paul
>>
>> On 5/28/14 6:10 PM, Paul Kyzivat wrote:
>>> I've submitted a revised version of the msrp recording draft.
>>> This one is substantially fleshed out. It certainly needs more
>>> tweaking, but is complete enough that you should be able to make
>>> meaningful comments on the approach.
>>>
>>>       Thanks,
>>>       Paul
>>>
>>>
>>> -------- Original Message --------
>>> Subject: New Version Notification for
>>> draft-yan-siprec-msrp-recording-01.txt
>>> Date: Wed, 28 May 2014 15:03:24 -0700
>>> From: internet-drafts@ietf.org
>>> To: Michael Yan <michael.yan@huawei.com>,        "Paul H. Kyzivat"
>>> <pkyzivat@alum.mit.edu>,        "Michael Yan" <michael.yan@huawei.com>,
>>>          "Paul Kyzivat" <pkyzivat@alum.mit.edu>
>>>
>>>
>>> A new version of I-D, draft-yan-siprec-msrp-recording-01.txt
>>> has been successfully submitted by Paul H. Kyzivat and posted to the
>>> IETF repository.
>>>
>>> Name:        draft-yan-siprec-msrp-recording
>>> Revision:    01
>>> Title:        Overview for MSRP Recording based on SIPREC
>>> Document date:    2014-05-28
>>> Group:        Individual Submission
>>> Pages:        9
>>> URL:
>>> http://www.ietf.org/internet-drafts/draft-yan-siprec-msrp-recording-0
>>> 1.txt
>>>
>>> Status:
>>> https://datatracker.ietf.org/doc/draft-yan-siprec-msrp-recording/
>>> Htmlized:
>>> http://tools.ietf.org/html/draft-yan-siprec-msrp-recording-01
>>> Diff:
>>> http://www.ietf.org/rfcdiff?url2=draft-yan-siprec-msrp-recording-01
>>>
>>> Abstract:
>>>      SIPREC is capable of recording interactive text media that is
>>>      transmitted via RTP.  However that format is not commonly used for
>>>      message or chat scenarios.  There is also a need for recording text
>>>      media carried via MSRP.  One case of note is exchange of text between
>>>      hearing-impaired users and emergence service bureaus.  Also,
>>>      recording support is needed for MSRP used in chat conferences and
>>>      multimedia conferences.
>>>
>>>      This document describes how to achieve MSRP channel recording within
>>>      the mechanism of SIP Recording (SIPREC).
>>>
>>>
>>>
>>>
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>> submission until the htmlized version and diff are available at
>>> tools.ietf.org.
>>>
>>> The IETF Secretariat
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> siprec mailing list
>>> siprec@ietf.org
>>> https://www.ietf.org/mailman/listinfo/siprec
>>>
>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>>
>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>
>