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

I’ve reviewed this document.  I think it is a very good start, and think we can get it ready to ship quite quickly.

I have the following comments:

We need to specify a way to send and save REPORTS that are sent/received on the CS to the SRS.  If, for example, a message sent by a party to another is not received completely, and a REPORT js generated on the RS, we need to somehow record than in the CS.  You have a note about reports, but it isn’t clear if you mean reports in the CS or the RS.  Both have to be recorded, but at least in the RS, the SRS has all the info needed.

I think there is a problem with the text about adding a CPIM wrapper if there isn’t one.  I think the recording has to know if the original message was sent by some entity other than the one in the CPIM From (that is, we have to preserve the MSRP From).  The SRS has to know whether the original message had a CPIM header, and its contents.   If the SRC changes the message (by adding the wrapper) I think the SRS has to be able to figure that out, and record that fact in some way.

When we echo a message from the RS to the CS, we’re going to lose the MESSAGE-ID from the RS.  That’s a problem.  We have to save that info in the recording.  A hack would be to use the same message ID in both the CS and the RS, possibly with some prefix.

I worry a bit about chunking in the RS differently from chunking in the CS. I may be mistaken, but if the chunking is different, will that affect the byte-range response in a failure report?

The URIs in the original to/from need to be captured, but they will be different in the RS.  Need to fix that.

Do we need to say something about max-size issues between CS and RS?

You can’t possibly not change -metadata.  As an example. you have to allow an msrp AoR for a participant

Yes, I think we have to extend Participant to handle nicks.  Probably also to handle the SIP session URI vs the MSRP URIs

Brian

On Jun 26, 2014, at 12:32 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> 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-01.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