
From nobody Mon Jun  1 13:03:19 2015
Return-Path: <eckelcu@cisco.com>
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 01F891B3376; Mon,  1 Jun 2015 13:03:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 CRDerfoKlgfc; Mon,  1 Jun 2015 13:03:13 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B25641B3371; Mon,  1 Jun 2015 13:03:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4015; q=dns/txt; s=iport; t=1433188986; x=1434398586; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=FoB+eUjEQ6OgqHzvvK8QxjXujS3HqgpKw2vVekjcqkU=; b=ECr/uuWivaa1h0027+kmuXFLlfVbplHIVwVqZAkJwSTamAY7FI3CUaYl k8nbTw3zVPjkQKISDzQaXaq8VHPWRec/d+AzErjPrRbWqSBA9r5N1VBuO dFoE7l6MHXe3VRPqmK2ZI3S9uMHUtlD/kmlAITv+nKFn9LlyQc08QWjdO U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ARBQCduWxV/4cNJK1cgxBUXgbALwqFLUoCgTdMAQEBAQEBgQuEIgEBAQQBAQE3NAsMBgEIEQQBAR8JLgsUCQoEAQ0FiC0N2FoBAQEBAQEBAQEBAQEBAQEBAQEBAQETBItDhCMRAQZLDYQnBYZriWeCPoQ2hmCBK4NzkhojYYEpHBWBPW8BAYEKOoEBAQEB
X-IronPort-AV: E=Sophos;i="5.13,534,1427760000"; d="scan'208";a="424491127"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-4.cisco.com with ESMTP; 01 Jun 2015 20:03:05 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t51K33YJ017611 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 1 Jun 2015 20:03:03 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.83]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.03.0195.001; Mon, 1 Jun 2015 15:03:03 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Hutton, Andrew" <andrew.hutton@unify.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
Thread-Topic: [siprec] Stephen Farrell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS)
Thread-Index: AQHQnKX3WBrtQWZTfUyWzpoDI1UNVw==
Date: Mon, 1 Jun 2015 20:03:02 +0000
Message-ID: <D19203E9.4E739%eckelcu@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [10.154.176.27]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0BC38FED35A3CD4E839B5A8B41B9399B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/ohTejm-pshjXjgAqPS7GRlcQu3U>
Cc: "siprec@ietf.org" <siprec@ietf.org>, "draft-ietf-siprec-protocol.shepherd@ietf.org" <draft-ietf-siprec-protocol.shepherd@ietf.org>, "draft-ietf-siprec-protocol@ietf.org" <draft-ietf-siprec-protocol@ietf.org>, "siprec-chairs@ietf.org" <siprec-chairs@ietf.org>, "draft-ietf-siprec-protocol.ad@ietf.org" <draft-ietf-siprec-protocol.ad@ietf.org>
Subject: Re: [siprec] Stephen Farrell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS)
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: Mon, 01 Jun 2015 20:03:15 -0000

Please see comments inline.

On 5/27/15, 1:21 PM, "Hutton, Andrew" <andrew.hutton@unify.com> wrote:

>Some responses from me below.
>
>Regards
>Andy
>
>
>
>
>> -----Original Message-----
>> From: Stephen Farrell [mailto:stephen.farrell@cs.tcd.ie]
>> Sent: 26 May 2015 23:41
>> To: The IESG
>> Cc: draft-ietf-siprec-protocol@ietf.org; draft-ietf-siprec-
>> protocol.ad@ietf.org; siprec-chairs@ietf.org; br@brianrosen.net; draft-
>> ietf-siprec-protocol.shepherd@ietf.org; siprec@ietf.org
>> Subject: Stephen Farrell's Discuss on draft-ietf-siprec-protocol-16:
>> (with DISCUSS)
>>=20
>> Stephen Farrell has entered the following ballot position for
>> draft-ietf-siprec-protocol-16: Discuss
>>=20
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>=20
>>=20
>> Please refer to https://www.ietf.org/iesg/statement/discuss-
>> criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-siprec-protocol/
>>=20
>>=20
>>=20
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>=20
>>=20
>> (1) 5.3: How does a UA know if it's preference to not be
>> recorded has been ignored?
>
>If the UA is a recording-aware UA (i.e. supports SIPREC) and it is
>talking to a compliant recording server then it will know via the
>"a=3Drecord" SDP attribute there is some further explanation of this in
>https://tools.ietf.org/html/draft-ietf-siprec-protocol-16#section-7.1.3.
>
>
>
>>=20
>> (2) 12.2: Why is a 2011 ([I-D.ietf-avt-srtp-ekt]) expired
>> I-D ok as the method for supporting DTLS-SRTP for the CS,
>> esp when DTLS-SRTP is our currently favoured method for
>> handing WebRTC security? When is that going to be finished?
>> On what basis is that an informative and not normative
>> reference? And is that reference ever likely to be
>> standardised? (Given that it seems to be a form of TLS MitM
>> - is that fair?) Perhaps it'd be better to just admit
>> that re-encryption is needed and get over it?
>
>
>Firstly the reference appears to be wrong as I think it should point to
>https://tools.ietf.org/html/draft-ietf-avtcore-srtp-ekt-03.

I updated the reference.

>DTLS-SRTP without EKT is certainly allowed in the CS as the draft does
>not restrict the keying mechanism on the CS.  Some members of the WG
>wanted to include the EKT case to allow for the case when there is
>DTLS-SRTP on the CS and SDES on the RS without requiring re-encryption
>and I believe everybody understood that this is a corner case but maybe
>those that requested it will comment further.

The consensus forming compromise within the WG was that at a minimum the
SRC and SRS MUST support the SDP Security Descriptions (SDES) key
negotiation mechanism [RFC4568]. EKT was seen as a way to enable things to
move forward to support DTSL-SRTP on the CS side without the performance
and security penalties that come with decrypting and re-encrpting on the
SRC before sending to the SRS.

>
>
>>=20
>> (3) I'll clear once you answer: but wouldn't it be easier
>> all around to just mandate use of mutually authenticated
>> TLS between SRC and SRS in all cases?  (Even if some
>> hop-by-hop stuff is needed when there are proxies between
>> SRC and SRS.)
>>=20
>
>I think the issue here is that the SRC and SRS will often be co-located
>in an environment where mutual authentication was just not necessary and
>therefore the WG did not want to mandate this in all cases.

Yep.

Cheers,
Charles

>
>>=20
>>=20
>
>_______________________________________________
>siprec mailing list
>siprec@ietf.org
>https://www.ietf.org/mailman/listinfo/siprec


From nobody Mon Jun  1 13:13:47 2015
Return-Path: <eckelcu@cisco.com>
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 5D9701B338E; Mon,  1 Jun 2015 13:13:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 g-tqok-OXH1d; Mon,  1 Jun 2015 13:13:43 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8331E1B338B; Mon,  1 Jun 2015 13:13:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1573; q=dns/txt; s=iport; t=1433189624; x=1434399224; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=NfA3mECgny2w0lh25vLPrInQjgPQqE4kdIRKToR7ILE=; b=PaUwcszeviJQoSKj3hdNji0Z60LQOib7VIOLZ4cpilIG0fIj5HGzm2Mh d0brp/D4VgCQhNHe2nnGHZol5N6eX82gGtN1fh1TEqQAm6/kE2gqpIv4M omjGoOIv9lA64H7aO91ozIPGJ+XpucYcJg6siJNQkVQYMZTkOzrGWJxiL 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOBQDru2xV/4wNJK1cgxBUXgbAOYV3AoE3TAEBAQEBAYELhCMBAQQ6PxACAQg2ECERJQIEAQ0FiBgDEg3TPQ2FFQEBAQEBAQEBAQEBAQEBAQEBAQEBARMEi0OCTYFWEQFRAgUChCsFhmuMJYQ2hQSBXIErg3OLFYcFI2GBWoE9bwGBCzqBAQEBAQ
X-IronPort-AV: E=Sophos;i="5.13,534,1427760000"; d="scan'208";a="424383989"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-7.cisco.com with ESMTP; 01 Jun 2015 20:13:43 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t51KDgnI009185 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 1 Jun 2015 20:13:42 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.83]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.03.0195.001; Mon, 1 Jun 2015 15:13:42 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>, The IESG <iesg@ietf.org>
Thread-Topic: Kathleen Moriarty's No Objection on draft-ietf-siprec-protocol-16: (with COMMENT)
Thread-Index: AQHQmUBV2HOa5zCfA02JliyvikOo8p2X+t4A
Date: Mon, 1 Jun 2015 20:13:41 +0000
Message-ID: <D1920951.4E768%eckelcu@cisco.com>
References: <20150528121738.32088.64033.idtracker@ietfa.amsl.com>
In-Reply-To: <20150528121738.32088.64033.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [10.154.176.27]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C280FCF3892F95419EBDA253AB9A0FD5@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/rksAqhaMfpOfivvSDza3MoGp7bg>
Cc: "siprec@ietf.org" <siprec@ietf.org>, "draft-ietf-siprec-protocol.ad@ietf.org" <draft-ietf-siprec-protocol.ad@ietf.org>, "siprec-chairs@ietf.org" <siprec-chairs@ietf.org>, "draft-ietf-siprec-protocol@ietf.org" <draft-ietf-siprec-protocol@ietf.org>, "draft-ietf-siprec-protocol.shepherd@ietf.org" <draft-ietf-siprec-protocol.shepherd@ietf.org>
Subject: Re: [siprec] Kathleen Moriarty's No Objection on draft-ietf-siprec-protocol-16: (with COMMENT)
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: Mon, 01 Jun 2015 20:13:45 -0000

Hi Kathleen,

You suggestions sounds good to me. I propose updating section 12 as
follows:

OLD
The SRC and SRS MUST support SIP with TLS and MAY support SIPS with TLS as
per [RFC5630].


NEW
The SRC and SRS MUST support SIP with TLS version 1.2, SHOULD follow the
best practices when using TLS as per [RFC 7525], and MAY support SIPS with
TLS as per [RFC5630].


Cheers,
Charles

On 5/28/15, 5:17 AM, "Kathleen Moriarty"
<Kathleen.Moriarty.ietf@gmail.com> wrote:

>Kathleen Moriarty has entered the following ballot position for
>draft-ietf-siprec-protocol-16: No Objection
>
>When responding, please keep the subject line intact and reply to all
>email addresses included in the To and CC lines. (Feel free to cut this
>introductory paragraph, however.)
>
>
>Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>for more information about IESG DISCUSS and COMMENT positions.
>
>
>The document, along with other ballot positions, can be found here:
>https://datatracker.ietf.org/doc/draft-ietf-siprec-protocol/
>
>
>
>----------------------------------------------------------------------
>COMMENT:
>----------------------------------------------------------------------
>
>I support Stephen's discuss.  Also, I don't see a minimum version
>specified for TLS, right now, it's 1.2.  Is there any reason that can't
>be added.  The text on cipher suites is good, but if you'd like to have a
>pointer to the recommended ones, the TLS BCP has them listed and that can
>be referenced as well, RFC7525.
>
>


From nobody Mon Jun  1 13:18:51 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
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 EF4AA1A89F6; Mon,  1 Jun 2015 13:18:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 scQ87onVrxmR; Mon,  1 Jun 2015 13:18:46 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7A6A1A89FB; Mon,  1 Jun 2015 13:18:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id AB9A1BED1; Mon,  1 Jun 2015 21:18:44 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJJM-Wot1Fo4; Mon,  1 Jun 2015 21:18:43 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.31.250]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id CDDCDBE33; Mon,  1 Jun 2015 21:18:41 +0100 (IST)
Message-ID: <556CBE1F.7090000@cs.tcd.ie>
Date: Mon, 01 Jun 2015 21:18:39 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>,  "Hutton, Andrew" <andrew.hutton@unify.com>, The IESG <iesg@ietf.org>
References: <D19203E9.4E739%eckelcu@cisco.com>
In-Reply-To: <D19203E9.4E739%eckelcu@cisco.com>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/EB5oe5YcEHyPugHvJNVjRZbohTc>
Cc: "siprec@ietf.org" <siprec@ietf.org>, "draft-ietf-siprec-protocol.shepherd@ietf.org" <draft-ietf-siprec-protocol.shepherd@ietf.org>, "draft-ietf-siprec-protocol@ietf.org" <draft-ietf-siprec-protocol@ietf.org>, "siprec-chairs@ietf.org" <siprec-chairs@ietf.org>, "draft-ietf-siprec-protocol.ad@ietf.org" <draft-ietf-siprec-protocol.ad@ietf.org>
Subject: Re: [siprec] Stephen Farrell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS)
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: Mon, 01 Jun 2015 20:18:47 -0000

Hi Charles,

One question on just one part of this, but one that puzzles me and
may be helpful in clearing this up...

On 01/06/15 21:03, Charles Eckel (eckelcu) wrote:
> the performance
> and security penalties that come with decrypting and re-encrpting on the
> SRC before sending to the SRS.

If you don't re-encrypt isn't it possible for anyone who is part
of the CS to send bogus packets to the SRS that will then be
recorded? (Assuming the sender can get the packets to the SRS but
let's assume they can, because that's not so hard.)

Not re-encrypting seems to just be broken, if e.g. this is supposed
to be a thing one could use to hold a rogue trader accountable when
there's big piles of money at stake.

Ta,
S.


From nobody Mon Jun  1 13:46:51 2015
Return-Path: <eckelcu@cisco.com>
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 B06831A894A for <siprec@ietfa.amsl.com>; Mon,  1 Jun 2015 13:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 C7-XLi9CDZg8 for <siprec@ietfa.amsl.com>; Mon,  1 Jun 2015 13:46:48 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E00831B33E3 for <siprec@ietf.org>; Mon,  1 Jun 2015 13:46:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2981; q=dns/txt; s=iport; t=1433191608; x=1434401208; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=mmS6MjEO/QyhY/b5+dc/ySbfne21+XySais/RaPm16I=; b=VT8g5uOZguyklT3fMe3Glgi5Zix0ODB4p21MkvTPb9eMYLrRHWK8e805 KjBzajMsyTEKxTA6mGOdlG4gGYCKEyZhqH80PRbtvGzTz61m8gOnof/lF VQk0wpqMLR9QCo3E+l2/bEhtEtN1XtqtVfC3GjTWvgM/RgQ/Jj/+jBs2d E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AoBACkw2xV/5RdJa1cDoMCVF4GvlYJgVAKhS1KAoE3OBQBAQEBAQEBgQqEIwEBBAEBAWsbAgEIDgouJwslAgQBEogtDdgzAQEBAQEBAQECAQEBAQEBAQEWBItDhFM6hC0FhmuFIYcEixaXOCNhgSkcFX8+b4FGgQEBAQE
X-IronPort-AV: E=Sophos;i="5.13,535,1427760000"; d="scan'208";a="155435364"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-4.cisco.com with ESMTP; 01 Jun 2015 20:46:47 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t51Kkl6x003438 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 1 Jun 2015 20:46:47 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.83]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.03.0195.001; Mon, 1 Jun 2015 15:46:46 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQmLk88qib+VBCPkal/XHgfVcX0p2R3wyAgAYmH4A=
Date: Mon, 1 Jun 2015 20:46:46 +0000
Message-ID: <D1921296.4E781%eckelcu@cisco.com>
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu>
In-Reply-To: <556739CD.4000204@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [10.154.176.27]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <65705B5D336F1D4DA764AA355C84C029@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/VMh54l17coczEFnavDeub4X2b1o>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: Mon, 01 Jun 2015 20:46:49 -0000

I=B9m hoping the authors of the metadata draft can chime in as to what they
would like to see changed here.

Cheers,
Charles

On 5/28/15, 8:52 AM, "Paul Kyzivat" <pkyzivat@alum.mit.edu> wrote:

>On 5/27/15 4:10 PM, Barry Leiba wrote:
>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> I have to raise one of Ben's comments to DISCUSS, after giving it a lot
>> of thought.  We talked about it before Ben posted his ballot, and I said
>> that I thought the way the rs-metadata-request subtype is used is
>>abusing
>> media types: media types are meant to label containers for protocol
>> elements, but are not meant to be protocol elements themselves.  I said
>>I
>> didn't want to get too wound up with that, though, and I don't...
>>
>> ...except that it allows no room for extensibility.  And the moment you
>> need another, different request, we see why this mechanism is abusive.
>> Now, you may say that you don't see any need for extensibility, but
>>we've
>> been proven wrong in those sorts of assumptions many times.
>>
>> So, the discussion is about how you will deal with that.  Specifically,
>> an alternative would be to have an rs-request subtype, with a
>> content-type parameter such as "req=3Dmetadata" (or even use rs-metadata
>> with "req=3Dsnapshot") and a rule that req=3D values that are not recogn=
ised
>> be ignored.  If this should ever need to be extended, other "req=3D"
>>values
>> could be defined.  A registry could be created in future, if there turns
>> out to be a need.
>>
>> There are other options, as well, but the main question is why are you
>> sure that no such extensibility is needed?
>
>I agree with Barry and Ben here: I think we should have some syntax in
>the body that indicates a request for a snapshot, and that has potential
>for future extension.
>
>> Also, what you're doing with content-disposition isn't in accord with
>> what that field is for: it is for describing how the information in the
>> message part should be presented -- not what it's meant to contain or be
>> used for.  This, too, could be better handled with a content-type
>> parameter.
>
>I disagree with Barry here. He is an app guy, so I guess it makes sense
>that he would say this. But almost none of the Content-Dispositions used
>with SIP are actually rendered to a human. For instance "session" for SDP.
>
>I see the distinction between C-T and C-D being a distinction between
>how it is represented and how it is used. There could be two different
>C-Ts for SDP and SDPng, but they would both be C-D "session". The SIPREC
>metadata is used very differently, and C-D is the way to distinguish it
>from "session".
>
>	Thanks,
>	Paul
>
>_______________________________________________
>siprec mailing list
>siprec@ietf.org
>https://www.ietf.org/mailman/listinfo/siprec


From nobody Mon Jun  1 17:00:06 2015
Return-Path: <eckelcu@cisco.com>
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 326CB1A3BA4; Mon,  1 Jun 2015 17:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 RLrF44V_rURx; Mon,  1 Jun 2015 17:00:01 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EF741A3BA3; Mon,  1 Jun 2015 17:00:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1595; q=dns/txt; s=iport; t=1433203201; x=1434412801; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=TSXGNB3fJ6C+FIVHRGMv/ouYjMe0X0fGkR7iL1p5PII=; b=lboRsMvuED2BPpZeimotCGVRAe/xZj68duIX2rw+vvl9nv9V0//UaBjl Qu5P5wpOuJV/jzuv1+FNT/GNY1jPiVuMVnCRpowcg/J052KuMR77YjHKE CBjGtY5O5yUUUMhfvABLGlxpHC1zZvLNwARthe3w5f6/QX0YvKlHPU6/T g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AlBADm8GxV/5tdJa1cgxCBMga+VgmHUQKBOTgUAQEBAQEBAYEKhCMBAQQ6PxACAQgYHhAyJQIEAQ0FiC3YdwEBAQEBAQEBAQEBAQEBAQEBAQEZi0OFBgeELQEEkxCLFpc4I2GBWoE9b4FGgQEBAQE
X-IronPort-AV: E=Sophos;i="5.13,536,1427760000";  d="scan'208";a="3664758"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-3.cisco.com with ESMTP; 01 Jun 2015 23:59:58 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t51NxvSR007911 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 1 Jun 2015 23:59:57 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.83]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0195.001; Mon, 1 Jun 2015 18:59:57 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "Hutton, Andrew" <andrew.hutton@unify.com>, The IESG <iesg@ietf.org>
Thread-Topic: [siprec] Stephen Farrell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS)
Thread-Index: AQHQnKX3WBrtQWZTfUyWzpoDI1UNV52YatCA///IeoA=
Date: Mon, 1 Jun 2015 23:59:56 +0000
Message-ID: <D1923895.4E90E%eckelcu@cisco.com>
References: <D19203E9.4E739%eckelcu@cisco.com> <556CBE1F.7090000@cs.tcd.ie>
In-Reply-To: <556CBE1F.7090000@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [10.154.176.27]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B94CE5C4E38BC542B629F952AEEB8F3B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/6VeFAlZo6pQ8viILrBKQ8eWxiVQ>
Cc: "siprec@ietf.org" <siprec@ietf.org>, "draft-ietf-siprec-protocol.shepherd@ietf.org" <draft-ietf-siprec-protocol.shepherd@ietf.org>, "draft-ietf-siprec-protocol@ietf.org" <draft-ietf-siprec-protocol@ietf.org>, "siprec-chairs@ietf.org" <siprec-chairs@ietf.org>, "draft-ietf-siprec-protocol.ad@ietf.org" <draft-ietf-siprec-protocol.ad@ietf.org>
Subject: Re: [siprec] Stephen Farrell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS)
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: Tue, 02 Jun 2015 00:00:02 -0000

Hi Stephen,

My comment was meant to be interpreted within the context of an EKT
session. In this case, the SRC is still using SRTP-SDES with the SRS for
the RS, and using TLS to establish the RS and exchange the keys. But in
doing it would not need to decrypt and re-encrypt the payload with a new
key.
I may be getting in over my head here, but I believe the SRTP
authentication tag would be sufficient to determine the source of the SRTP
packets is in fact the SRC and not simply any one of the UAs participating
in the CS injecting random SRTP packets encrypted with the same key into
the stream.
I also expect that in practice there would be a firewall that allows only
appropriate SRCs to access the SRS.


Cheers,
Charles

On 6/1/15, 1:18 PM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:

>
>Hi Charles,
>
>One question on just one part of this, but one that puzzles me and
>may be helpful in clearing this up...
>
>On 01/06/15 21:03, Charles Eckel (eckelcu) wrote:
>> the performance
>> and security penalties that come with decrypting and re-encrpting on the
>> SRC before sending to the SRS.
>
>If you don't re-encrypt isn't it possible for anyone who is part
>of the CS to send bogus packets to the SRS that will then be
>recorded? (Assuming the sender can get the packets to the SRS but
>let's assume they can, because that's not so hard.)
>
>Not re-encrypting seems to just be broken, if e.g. this is supposed
>to be a thing one could use to hold a rogue trader accountable when
>there's big piles of money at stake.
>
>Ta,
>S.
>


From nobody Mon Jun  1 17:04:44 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
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 5453B1A6EFC; Mon,  1 Jun 2015 17:04:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 OW6r03xOCM7V; Mon,  1 Jun 2015 17:04:38 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D2DB1A6F0A; Mon,  1 Jun 2015 17:04:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 9634CBED3; Tue,  2 Jun 2015 01:04:36 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bKoVZspBPTdX; Tue,  2 Jun 2015 01:04:35 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.31.250]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2F8A3BE9F; Tue,  2 Jun 2015 01:04:35 +0100 (IST)
Message-ID: <556CF312.2060204@cs.tcd.ie>
Date: Tue, 02 Jun 2015 01:04:34 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>,  "Hutton, Andrew" <andrew.hutton@unify.com>, The IESG <iesg@ietf.org>
References: <D19203E9.4E739%eckelcu@cisco.com> <556CBE1F.7090000@cs.tcd.ie> <D1923895.4E90E%eckelcu@cisco.com>
In-Reply-To: <D1923895.4E90E%eckelcu@cisco.com>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/Y9lET1vDkJq8Jclw3EE20BbXb3A>
Cc: "siprec@ietf.org" <siprec@ietf.org>, "draft-ietf-siprec-protocol.ad@ietf.org" <draft-ietf-siprec-protocol.ad@ietf.org>, "draft-ietf-siprec-protocol@ietf.org" <draft-ietf-siprec-protocol@ietf.org>, "siprec-chairs@ietf.org" <siprec-chairs@ietf.org>, "draft-ietf-siprec-protocol.shepherd@ietf.org" <draft-ietf-siprec-protocol.shepherd@ietf.org>
Subject: Re: [siprec] Stephen Farrell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS)
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: Tue, 02 Jun 2015 00:04:40 -0000

Hi Charles,

On 02/06/15 00:59, Charles Eckel (eckelcu) wrote:
> Hi Stephen,
> 
> My comment was meant to be interpreted within the context of an EKT
> session. In this case, the SRC is still using SRTP-SDES with the SRS for
> the RS, and using TLS to establish the RS and exchange the keys. But in
> doing it would not need to decrypt and re-encrypt the payload with a new
> key.

I guess I need to go check the updated reference(s) on that
stuff. (It might make sense to shoot out a revision with that
fixed and other changes just to simplify the discussion, but
your AD will guide you on that.)

> I may be getting in over my head here, but I believe the SRTP
> authentication tag would be sufficient to determine the source of the SRTP
> packets is in fact the SRC and not simply any one of the UAs participating
> in the CS injecting random SRTP packets encrypted with the same key into
> the stream.

Yeah, that's one we do need to bottom out on.

> I also expect that in practice there would be a firewall that allows only
> appropriate SRCs to access the SRS.

Could well be, but even if so, that'd not be considered sufficient
really I guess.

S.


> 
> 
> Cheers,
> Charles
> 
> On 6/1/15, 1:18 PM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:
> 
>>
>> Hi Charles,
>>
>> One question on just one part of this, but one that puzzles me and
>> may be helpful in clearing this up...
>>
>> On 01/06/15 21:03, Charles Eckel (eckelcu) wrote:
>>> the performance
>>> and security penalties that come with decrypting and re-encrpting on the
>>> SRC before sending to the SRS.
>>
>> If you don't re-encrypt isn't it possible for anyone who is part
>> of the CS to send bogus packets to the SRS that will then be
>> recorded? (Assuming the sender can get the packets to the SRS but
>> let's assume they can, because that's not so hard.)
>>
>> Not re-encrypting seems to just be broken, if e.g. this is supposed
>> to be a thing one could use to hold a rogue trader accountable when
>> there's big piles of money at stake.
>>
>> Ta,
>> S.
>>
> 


From nobody Tue Jun  2 04:05:42 2015
Return-Path: <kathleen.moriarty.ietf@gmail.com>
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 482921B33DB; Mon,  1 Jun 2015 13:35:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 htwve1Zc77iy; Mon,  1 Jun 2015 13:35:23 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F186C1B33DA; Mon,  1 Jun 2015 13:35:22 -0700 (PDT)
Received: by wizo1 with SMTP id o1so119646870wiz.1; Mon, 01 Jun 2015 13:35:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=s/XpmdEkpmyZ+35JybEykQVxXrTQLyvd76zPPIGKRnY=; b=xf/XFWdAKCB9WLjJme+OwmQI4Gso766BmMpyYKF6VjqNtv05zrBxRVeKL06DVCguSG 13ur74ulHMKbmuR3PCUMNy3+pyfi3xFFRa9alZ860vHw3NNym9bYpMOU8YTSsa+Qryxx q9HnsgeUMD3QWlBJEr5v3SmuZED9RFDPWPL5qF58uxjHC5wXYuXixdy/7Vv4plxE03Ox lF+WZzOX0GTPSuIV1UTCNqiuXH9xkV4xPDWqCUwQAKlcTqon+6QHZArFWgHx3mLcGElD V99VHbHfI36LvyzH9XLzOHuNOkBagMxZL1CPTNTNx4h6W3/kVu9CJ0noss69Oq/aU7IJ SIRQ==
MIME-Version: 1.0
X-Received: by 10.194.222.230 with SMTP id qp6mr44833045wjc.70.1433190921751;  Mon, 01 Jun 2015 13:35:21 -0700 (PDT)
Received: by 10.28.148.148 with HTTP; Mon, 1 Jun 2015 13:35:21 -0700 (PDT)
In-Reply-To: <D1920951.4E768%eckelcu@cisco.com>
References: <20150528121738.32088.64033.idtracker@ietfa.amsl.com> <D1920951.4E768%eckelcu@cisco.com>
Date: Mon, 1 Jun 2015 16:35:21 -0400
Message-ID: <CAHbuEH5YFWVFh+WrpUDT7OCmnT-+kM6auwM2XqWOHo1C6ow_-Q@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Content-Type: multipart/alternative; boundary=001a11c3bad8c952de05177ac344
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/R_DC3BXVZBJvIUjryhlj2NTo9bo>
X-Mailman-Approved-At: Tue, 02 Jun 2015 04:05:40 -0700
Cc: "siprec@ietf.org" <siprec@ietf.org>, "draft-ietf-siprec-protocol.ad@ietf.org" <draft-ietf-siprec-protocol.ad@ietf.org>, "siprec-chairs@ietf.org" <siprec-chairs@ietf.org>, "draft-ietf-siprec-protocol@ietf.org" <draft-ietf-siprec-protocol@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-siprec-protocol.shepherd@ietf.org" <draft-ietf-siprec-protocol.shepherd@ietf.org>
Subject: Re: [siprec] Kathleen Moriarty's No Objection on draft-ietf-siprec-protocol-16: (with COMMENT)
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: Mon, 01 Jun 2015 20:35:25 -0000

--001a11c3bad8c952de05177ac344
Content-Type: text/plain; charset=UTF-8

On Mon, Jun 1, 2015 at 4:13 PM, Charles Eckel (eckelcu) <eckelcu@cisco.com>
wrote:

> Hi Kathleen,
>
> You suggestions sounds good to me. I propose updating section 12 as
> follows:
>
> OLD
> The SRC and SRS MUST support SIP with TLS and MAY support SIPS with TLS as
> per [RFC5630].
>
>
> NEW
> The SRC and SRS MUST support SIP with TLS version 1.2, SHOULD follow the
> best practices when using TLS as per [RFC 7525], and MAY support SIPS with
> TLS as per [RFC5630].
>

Thanks, Charles!

Best regards,
Kathleen

>
>
> Cheers,
> Charles
>
> On 5/28/15, 5:17 AM, "Kathleen Moriarty"
> <Kathleen.Moriarty.ietf@gmail.com> wrote:
>
> >Kathleen Moriarty has entered the following ballot position for
> >draft-ietf-siprec-protocol-16: No Objection
> >
> >When responding, please keep the subject line intact and reply to all
> >email addresses included in the To and CC lines. (Feel free to cut this
> >introductory paragraph, however.)
> >
> >
> >Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> >for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> >The document, along with other ballot positions, can be found here:
> >https://datatracker.ietf.org/doc/draft-ietf-siprec-protocol/
> >
> >
> >
> >----------------------------------------------------------------------
> >COMMENT:
> >----------------------------------------------------------------------
> >
> >I support Stephen's discuss.  Also, I don't see a minimum version
> >specified for TLS, right now, it's 1.2.  Is there any reason that can't
> >be added.  The text on cipher suites is good, but if you'd like to have a
> >pointer to the recommended ones, the TLS BCP has them listed and that can
> >be referenced as well, RFC7525.
> >
> >
>
>


-- 

Best regards,
Kathleen

--001a11c3bad8c952de05177ac344
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Jun 1, 2015 at 4:13 PM, Charles Eckel (eckelcu) <span dir=3D"lt=
r">&lt;<a href=3D"mailto:eckelcu@cisco.com" target=3D"_blank">eckelcu@cisco=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Kathleen,<b=
r>
<br>
You suggestions sounds good to me. I propose updating section 12 as<br>
follows:<br>
<br>
OLD<br>
The SRC and SRS MUST support SIP with TLS and MAY support SIPS with TLS as<=
br>
per [RFC5630].<br>
<br>
<br>
NEW<br>
The SRC and SRS MUST support SIP with TLS version 1.2, SHOULD follow the<br=
>
best practices when using TLS as per [RFC 7525], and MAY support SIPS with<=
br>
TLS as per [RFC5630].<br></blockquote><div><br></div><div>Thanks, Charles!<=
/div><div><br></div><div>Best regards,</div><div>Kathleen=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
<br>
<br>
Cheers,<br>
Charles<br>
<br>
On 5/28/15, 5:17 AM, &quot;Kathleen Moriarty&quot;<br>
<div class=3D"HOEnZb"><div class=3D"h5">&lt;<a href=3D"mailto:Kathleen.Mori=
arty.ietf@gmail.com">Kathleen.Moriarty.ietf@gmail.com</a>&gt; wrote:<br>
<br>
&gt;Kathleen Moriarty has entered the following ballot position for<br>
&gt;draft-ietf-siprec-protocol-16: No Objection<br>
&gt;<br>
&gt;When responding, please keep the subject line intact and reply to all<b=
r>
&gt;email addresses included in the To and CC lines. (Feel free to cut this=
<br>
&gt;introductory paragraph, however.)<br>
&gt;<br>
&gt;<br>
&gt;Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss-=
criteria.html" target=3D"_blank">https://www.ietf.org/iesg/statement/discus=
s-criteria.html</a><br>
&gt;for more information about IESG DISCUSS and COMMENT positions.<br>
&gt;<br>
&gt;<br>
&gt;The document, along with other ballot positions, can be found here:<br>
&gt;<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-siprec-protocol/=
" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-siprec-prot=
ocol/</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;----------------------------------------------------------------------<=
br>
&gt;COMMENT:<br>
&gt;----------------------------------------------------------------------<=
br>
&gt;<br>
&gt;I support Stephen&#39;s discuss.=C2=A0 Also, I don&#39;t see a minimum =
version<br>
&gt;specified for TLS, right now, it&#39;s 1.2.=C2=A0 Is there any reason t=
hat can&#39;t<br>
&gt;be added.=C2=A0 The text on cipher suites is good, but if you&#39;d lik=
e to have a<br>
&gt;pointer to the recommended ones, the TLS BCP has them listed and that c=
an<br>
&gt;be referenced as well, RFC7525.<br>
&gt;<br>
&gt;<br>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature"><div dir=3D"ltr"><br><div>Best regards,</div=
><div>Kathleen</div></div></div>
</div></div>

--001a11c3bad8c952de05177ac344--


From nobody Fri Jun 12 13:06:15 2015
Return-Path: <alissa@cooperw.in>
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 0AF9E1B29F3 for <siprec@ietfa.amsl.com>; Fri, 12 Jun 2015 13:06:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.801
X-Spam-Level: 
X-Spam-Status: No, score=-0.801 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 V21YTY8dQlcb for <siprec@ietfa.amsl.com>; Fri, 12 Jun 2015 13:06:10 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E62CD1B29FA for <siprec@ietf.org>; Fri, 12 Jun 2015 13:06:08 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 30C8020E15 for <siprec@ietf.org>; Fri, 12 Jun 2015 16:06:08 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 12 Jun 2015 16:06:08 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=mbjYpxk2JD8gFD3iY/mafcRU4DU=; b=Bhbcxt AzPaEW5/3xspebepAVkfdi2cZ0Xx3ZBhzvIyISsEmSa/8M7NiHS54CGc2ORm/Nei 2qGHUYPfhVuWfMe+7DJnjyhhZ6OA/VBUxxiTaclfInTgWgU/iKEHkbyvD3xXf+nX Tt8ewQhEUVBI5lBIKSaHSXIPdR2l2Dh4/pyoo=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=mbjYpxk2JD8gFD3 iY/mafcRU4DU=; b=TcVfZAmmHu/eKQ6OKFURAigWWimLKuIqnvmBAbk45SwwP/1 REHDNupXBVZcNqfFb2AROXIsk8D2PBPLk/EY0DhkCa3jxHlNJOcOna9neyFsn2S3 D7ylvFda17U7YX2WaY1DboH1fnTv/fxnVU5gNviitp4x4FPxju7P7Q+dPYpk=
X-Sasl-enc: SZOpyc2YE1rNnZxUHHeFUrpXxHxEaCOsqegcWQQs6zwm 1434139567
Received: from dhcp-171-68-21-86.cisco.com (unknown [171.68.21.86]) by mail.messagingengine.com (Postfix) with ESMTPA id 4AF246800F2; Fri, 12 Jun 2015 16:06:07 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <D1921296.4E781%eckelcu@cisco.com>
Date: Fri, 12 Jun 2015 13:06:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in>
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu> <D1921296.4E781%eckelcu@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/D2H05Fg9wSnxdJfgZEfff4pkaeU>
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: Fri, 12 Jun 2015 20:06:13 -0000

Still looking for folks to respond on this =97 have only seen a response =
from Paul.

Alissa

On Jun 1, 2015, at 1:46 PM, Charles Eckel (eckelcu) <eckelcu@cisco.com> =
wrote:

> I=B9m hoping the authors of the metadata draft can chime in as to what =
they
> would like to see changed here.
>=20
> Cheers,
> Charles
>=20
> On 5/28/15, 8:52 AM, "Paul Kyzivat" <pkyzivat@alum.mit.edu> wrote:
>=20
>> On 5/27/15 4:10 PM, Barry Leiba wrote:
>>=20
>>> =
----------------------------------------------------------------------
>>> DISCUSS:
>>> =
----------------------------------------------------------------------
>>>=20
>>> I have to raise one of Ben's comments to DISCUSS, after giving it a =
lot
>>> of thought.  We talked about it before Ben posted his ballot, and I =
said
>>> that I thought the way the rs-metadata-request subtype is used is
>>> abusing
>>> media types: media types are meant to label containers for protocol
>>> elements, but are not meant to be protocol elements themselves.  I =
said
>>> I
>>> didn't want to get too wound up with that, though, and I don't...
>>>=20
>>> ...except that it allows no room for extensibility.  And the moment =
you
>>> need another, different request, we see why this mechanism is =
abusive.
>>> Now, you may say that you don't see any need for extensibility, but
>>> we've
>>> been proven wrong in those sorts of assumptions many times.
>>>=20
>>> So, the discussion is about how you will deal with that.  =
Specifically,
>>> an alternative would be to have an rs-request subtype, with a
>>> content-type parameter such as "req=3Dmetadata" (or even use =
rs-metadata
>>> with "req=3Dsnapshot") and a rule that req=3D values that are not =
recognised
>>> be ignored.  If this should ever need to be extended, other "req=3D"
>>> values
>>> could be defined.  A registry could be created in future, if there =
turns
>>> out to be a need.
>>>=20
>>> There are other options, as well, but the main question is why are =
you
>>> sure that no such extensibility is needed?
>>=20
>> I agree with Barry and Ben here: I think we should have some syntax =
in
>> the body that indicates a request for a snapshot, and that has =
potential
>> for future extension.
>>=20
>>> Also, what you're doing with content-disposition isn't in accord =
with
>>> what that field is for: it is for describing how the information in =
the
>>> message part should be presented -- not what it's meant to contain =
or be
>>> used for.  This, too, could be better handled with a content-type
>>> parameter.
>>=20
>> I disagree with Barry here. He is an app guy, so I guess it makes =
sense
>> that he would say this. But almost none of the Content-Dispositions =
used
>> with SIP are actually rendered to a human. For instance "session" for =
SDP.
>>=20
>> I see the distinction between C-T and C-D being a distinction between
>> how it is represented and how it is used. There could be two =
different
>> C-Ts for SDP and SDPng, but they would both be C-D "session". The =
SIPREC
>> metadata is used very differently, and C-D is the way to distinguish =
it
>> from "session".
>>=20
>> 	Thanks,
>> 	Paul
>>=20
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


From nobody Sun Jun 14 22:19:51 2015
Return-Path: <rmohanr@cisco.com>
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 539161B3262 for <siprec@ietfa.amsl.com>; Sun, 14 Jun 2015 22:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.51
X-Spam-Level: 
X-Spam-Status: No, score=-12.51 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_38=0.6, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 iNDeAJg_eQJT for <siprec@ietfa.amsl.com>; Sun, 14 Jun 2015 22:19:48 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 505A61B3261 for <siprec@ietf.org>; Sun, 14 Jun 2015 22:19:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6466; q=dns/txt; s=iport; t=1434345588; x=1435555188; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=LND+JZaG3aMlo382Pbs6zzWO0ijo4Mt6N6/DZ7IMTCU=; b=HQkPjlJYopZuuWweUxq4gvC9aMEDSTJI8yeCWSNYiyyQdg0B7B8XbKoX MXWKhrrjDVP5kywQneHGIBFqxxoL2xbRb4zfcoXVZuTsOA9zJz8nq2/rU 5mF/Rb//RNYoBsIzxWT23/engEbTNNtWsTlRfNdxnz3I3w5t/fXs/2LSX 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A3BQBOYH5V/4QNJK1cgxBUXwaDGLpIgVcKhTBKAhyBCzoSAQEBAQEBAYEKhCIBAQEEAQEBMToXBAIBCBEDAQIBBCgCAiULHQgCBAESiC8NlV2dEQaVdAEBAQEBAQEBAQEBAQEBAQEBAQEVBIEbiimEUzoGglyBSwWGeoxhAYtBgTOEBJJZJmOBKBwVgT1vgUaBAQEBAQ
X-IronPort-AV: E=Sophos;i="5.13,616,1427760000"; d="scan'208";a="159433763"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-5.cisco.com with ESMTP; 15 Jun 2015 05:19:47 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t5F5Jk5b013219 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Jun 2015 05:19:46 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.34]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0195.001; Mon, 15 Jun 2015 00:19:46 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Alissa Cooper <alissa@cooperw.in>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQpyrkJJoq6w2sCEyGUxziYAl77Q==
Date: Mon, 15 Jun 2015 05:19:45 +0000
Message-ID: <D1A44B8B.343CD%rmohanr@cisco.com>
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu> <D1921296.4E781%eckelcu@cisco.com> <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in>
In-Reply-To: <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [173.39.64.231]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <5A0C83A03281A049B15079851B4D171D@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/zs2DMruSLqKckmZ6okN_oPPKh7M>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: Mon, 15 Jun 2015 05:19:50 -0000

UGxlYXNlIHNlZSBpbmxpbmUgZm9yIGNvbW1lbnRzDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQpGcm9tOiBBbGlzc2EgQ29vcGVyIDxhbGlzc2FAY29vcGVydy5pbj4NCkRhdGU6IFNhdHVy
ZGF5LCAxMyBKdW5lIDIwMTUgMTozNiBhbQ0KVG86ICJDaGFybGVzIEVja2VsIChlY2tlbGN1KSIg
PGVja2VsY3VAY2lzY28uY29tPg0KQ2M6ICJzaXByZWNAaWV0Zi5vcmciIDxzaXByZWNAaWV0Zi5v
cmc+DQpTdWJqZWN0OiBSZTogW3NpcHJlY10gQmFycnkgTGVpYmEncyBEaXNjdXNzIG9uDQpkcmFm
dC1pZXRmLXNpcHJlYy1wcm90b2NvbC0xNjogKHdpdGggRElTQ1VTUyBhbmQgQ09NTUVOVCkNCg0K
PlN0aWxsIGxvb2tpbmcgZm9yIGZvbGtzIHRvIHJlc3BvbmQgb24gdGhpcyChqiBoYXZlIG9ubHkg
c2VlbiBhIHJlc3BvbnNlDQo+ZnJvbSBQYXVsLg0KPg0KPkFsaXNzYQ0KPg0KPk9uIEp1biAxLCAy
MDE1LCBhdCAxOjQ2IFBNLCBDaGFybGVzIEVja2VsIChlY2tlbGN1KSA8ZWNrZWxjdUBjaXNjby5j
b20+DQo+d3JvdGU6DQo+DQo+PiBJqfZtIGhvcGluZyB0aGUgYXV0aG9ycyBvZiB0aGUgbWV0YWRh
dGEgZHJhZnQgY2FuIGNoaW1lIGluIGFzIHRvIHdoYXQNCj4+dGhleQ0KPj4gd291bGQgbGlrZSB0
byBzZWUgY2hhbmdlZCBoZXJlLg0KPj4gDQo+PiBDaGVlcnMsDQo+PiBDaGFybGVzDQo+PiANCj4+
IE9uIDUvMjgvMTUsIDg6NTIgQU0sICJQYXVsIEt5eml2YXQiIDxwa3l6aXZhdEBhbHVtLm1pdC5l
ZHU+IHdyb3RlOg0KPj4gDQo+Pj4gT24gNS8yNy8xNSA0OjEwIFBNLCBCYXJyeSBMZWliYSB3cm90
ZToNCj4+PiANCj4+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPj4+PiBESVNDVVNTOg0KPj4+PiAtLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQo+Pj4+IA0KPj4+PiBJIGhhdmUgdG8gcmFpc2Ugb25lIG9mIEJlbidzIGNvbW1lbnRz
IHRvIERJU0NVU1MsIGFmdGVyIGdpdmluZyBpdCBhDQo+Pj4+bG90DQo+Pj4+IG9mIHRob3VnaHQu
ICBXZSB0YWxrZWQgYWJvdXQgaXQgYmVmb3JlIEJlbiBwb3N0ZWQgaGlzIGJhbGxvdCwgYW5kIEkN
Cj4+Pj5zYWlkDQo+Pj4+IHRoYXQgSSB0aG91Z2h0IHRoZSB3YXkgdGhlIHJzLW1ldGFkYXRhLXJl
cXVlc3Qgc3VidHlwZSBpcyB1c2VkIGlzDQo+Pj4+IGFidXNpbmcNCj4+Pj4gbWVkaWEgdHlwZXM6
IG1lZGlhIHR5cGVzIGFyZSBtZWFudCB0byBsYWJlbCBjb250YWluZXJzIGZvciBwcm90b2NvbA0K
Pj4+PiBlbGVtZW50cywgYnV0IGFyZSBub3QgbWVhbnQgdG8gYmUgcHJvdG9jb2wgZWxlbWVudHMg
dGhlbXNlbHZlcy4gIEkNCj4+Pj5zYWlkDQo+Pj4+IEkNCj4+Pj4gZGlkbid0IHdhbnQgdG8gZ2V0
IHRvbyB3b3VuZCB1cCB3aXRoIHRoYXQsIHRob3VnaCwgYW5kIEkgZG9uJ3QuLi4NCj4+Pj4gDQo+
Pj4+IC4uLmV4Y2VwdCB0aGF0IGl0IGFsbG93cyBubyByb29tIGZvciBleHRlbnNpYmlsaXR5LiAg
QW5kIHRoZSBtb21lbnQNCj4+Pj55b3UNCj4+Pj4gbmVlZCBhbm90aGVyLCBkaWZmZXJlbnQgcmVx
dWVzdCwgd2Ugc2VlIHdoeSB0aGlzIG1lY2hhbmlzbSBpcyBhYnVzaXZlLg0KPj4+PiBOb3csIHlv
dSBtYXkgc2F5IHRoYXQgeW91IGRvbid0IHNlZSBhbnkgbmVlZCBmb3IgZXh0ZW5zaWJpbGl0eSwg
YnV0DQo+Pj4+IHdlJ3ZlDQo+Pj4+IGJlZW4gcHJvdmVuIHdyb25nIGluIHRob3NlIHNvcnRzIG9m
IGFzc3VtcHRpb25zIG1hbnkgdGltZXMuDQo+Pj4+IA0KPj4+PiBTbywgdGhlIGRpc2N1c3Npb24g
aXMgYWJvdXQgaG93IHlvdSB3aWxsIGRlYWwgd2l0aCB0aGF0Lg0KPj4+PlNwZWNpZmljYWxseSwN
Cj4+Pj4gYW4gYWx0ZXJuYXRpdmUgd291bGQgYmUgdG8gaGF2ZSBhbiBycy1yZXF1ZXN0IHN1YnR5
cGUsIHdpdGggYQ0KPj4+PiBjb250ZW50LXR5cGUgcGFyYW1ldGVyIHN1Y2ggYXMgInJlcT1tZXRh
ZGF0YSIgKG9yIGV2ZW4gdXNlIHJzLW1ldGFkYXRhDQo+Pj4+IHdpdGggInJlcT1zbmFwc2hvdCIp
IGFuZCBhIHJ1bGUgdGhhdCByZXE9IHZhbHVlcyB0aGF0IGFyZSBub3QNCj4+Pj5yZWNvZ25pc2Vk
DQo+Pj4+IGJlIGlnbm9yZWQuICBJZiB0aGlzIHNob3VsZCBldmVyIG5lZWQgdG8gYmUgZXh0ZW5k
ZWQsIG90aGVyICJyZXE9Ig0KPj4+PiB2YWx1ZXMNCj4+Pj4gY291bGQgYmUgZGVmaW5lZC4gIEEg
cmVnaXN0cnkgY291bGQgYmUgY3JlYXRlZCBpbiBmdXR1cmUsIGlmIHRoZXJlDQo+Pj4+dHVybnMN
Cj4+Pj4gb3V0IHRvIGJlIGEgbmVlZC4NCj4+Pj4gDQo+Pj4+IFRoZXJlIGFyZSBvdGhlciBvcHRp
b25zLCBhcyB3ZWxsLCBidXQgdGhlIG1haW4gcXVlc3Rpb24gaXMgd2h5IGFyZSB5b3UNCj4+Pj4g
c3VyZSB0aGF0IG5vIHN1Y2ggZXh0ZW5zaWJpbGl0eSBpcyBuZWVkZWQ/DQo+Pj4gDQo+Pj4gSSBh
Z3JlZSB3aXRoIEJhcnJ5IGFuZCBCZW4gaGVyZTogSSB0aGluayB3ZSBzaG91bGQgaGF2ZSBzb21l
IHN5bnRheCBpbg0KPj4+IHRoZSBib2R5IHRoYXQgaW5kaWNhdGVzIGEgcmVxdWVzdCBmb3IgYSBz
bmFwc2hvdCwgYW5kIHRoYXQgaGFzDQo+Pj5wb3RlbnRpYWwNCj4+PiBmb3IgZnV0dXJlIGV4dGVu
c2lvbi4NCg0KSSBhbSBmaW5lIHdpdGggaGF2aW5nIHN1Y2ggYSBleHRlbnNpb24gdG8gdXNlIHJz
LW1ldGFkYXRhIHdpdGggcmVxPSBzbw0KdGhhdCBpdCBhbGxvd3MgZm9yIGFueSBleHRlbnNpb25z
IHRoYXQgd291bGQgY29tZSBpbiBmdXR1cmUuIEZvciB0aGUNCmN1cnJlbnQgdmVyc2lvbiBvZiBT
SVBSRUMgd2UgY291bGQgdXNlIHJlcT1zbmFwc2hvdC4NCiANCj4+PiANCj4+Pj4gQWxzbywgd2hh
dCB5b3UncmUgZG9pbmcgd2l0aCBjb250ZW50LWRpc3Bvc2l0aW9uIGlzbid0IGluIGFjY29yZCB3
aXRoDQo+Pj4+IHdoYXQgdGhhdCBmaWVsZCBpcyBmb3I6IGl0IGlzIGZvciBkZXNjcmliaW5nIGhv
dyB0aGUgaW5mb3JtYXRpb24gaW4NCj4+Pj50aGUNCj4+Pj4gbWVzc2FnZSBwYXJ0IHNob3VsZCBi
ZSBwcmVzZW50ZWQgLS0gbm90IHdoYXQgaXQncyBtZWFudCB0byBjb250YWluIG9yDQo+Pj4+YmUN
Cj4+Pj4gdXNlZCBmb3IuICBUaGlzLCB0b28sIGNvdWxkIGJlIGJldHRlciBoYW5kbGVkIHdpdGgg
YSBjb250ZW50LXR5cGUNCj4+Pj4gcGFyYW1ldGVyLg0KDQpDb250ZW50LURpc3Bvc2l0aW9uIGhl
YWRlciBmaWVsZCBkZXNjcmliZXMgaG93IHRoZSBtZXNzYWdlIGJvZHkgcGFydCBpcyB0bw0KYmUg
aW50ZXJwcmV0ZWQNCiAgIGJ5IHRoZSBVQUMgb3IgVUFTLiBBcyBTSVBSRUMgbWV0YWRhdGEgaXMg
dXNlZCBkaWZmZXJlbnRseSBieSByZWNvcmRlcnMNCnRoYW4gdGhlIGJvZHkgdHlwZXMgbGlrZSBT
RFAgdGhlIENvbnRlbnQtRGlzcG9zaXRpb24gobBzZXNzaW9uobEgZGVmaW5lZCBpbg0KUkZDIDMy
NjEgY2Fubm90IGJlIHVzZWQgaGVyZS4NCkkgdGhpbmsgaXRzIGZpbmUgdG8gaGF2ZSBuZXcgQy1E
LiBBbHNvIEkgc2VlIHNldmVyYWwgb2Ygb3RoZXIgU0lQIFJGQ3MNCihsaWtlIFJGQyA1NjIxLCBS
RkMgMzIwNCkgdGhhdCBkZWZpbmVzIG5ldyBib2R5IGRlZmluZXMgaXRzIG93biBDLUQuDQoNClNv
IHdlIGNvdWxkIHN0aWNrIHdpdGggY3VycmVudCBDLUQgaW4gdGhlIGRyYWZ0IC4NCg0KUmVnYXJk
cywNClJhbQ0KDQo+Pj4gDQo+Pj4gSSBkaXNhZ3JlZSB3aXRoIEJhcnJ5IGhlcmUuIEhlIGlzIGFu
IGFwcCBndXksIHNvIEkgZ3Vlc3MgaXQgbWFrZXMgc2Vuc2UNCj4+PiB0aGF0IGhlIHdvdWxkIHNh
eSB0aGlzLiBCdXQgYWxtb3N0IG5vbmUgb2YgdGhlIENvbnRlbnQtRGlzcG9zaXRpb25zDQo+Pj51
c2VkDQo+Pj4gd2l0aCBTSVAgYXJlIGFjdHVhbGx5IHJlbmRlcmVkIHRvIGEgaHVtYW4uIEZvciBp
bnN0YW5jZSAic2Vzc2lvbiIgZm9yDQo+Pj5TRFAuDQo+Pj4gDQo+Pj4gSSBzZWUgdGhlIGRpc3Rp
bmN0aW9uIGJldHdlZW4gQy1UIGFuZCBDLUQgYmVpbmcgYSBkaXN0aW5jdGlvbiBiZXR3ZWVuDQo+
Pj4gaG93IGl0IGlzIHJlcHJlc2VudGVkIGFuZCBob3cgaXQgaXMgdXNlZC4gVGhlcmUgY291bGQg
YmUgdHdvIGRpZmZlcmVudA0KPj4+IEMtVHMgZm9yIFNEUCBhbmQgU0RQbmcsIGJ1dCB0aGV5IHdv
dWxkIGJvdGggYmUgQy1EICJzZXNzaW9uIi4gVGhlDQo+Pj5TSVBSRUMNCj4+PiBtZXRhZGF0YSBp
cyB1c2VkIHZlcnkgZGlmZmVyZW50bHksIGFuZCBDLUQgaXMgdGhlIHdheSB0byBkaXN0aW5ndWlz
aCBpdA0KPj4+IGZyb20gInNlc3Npb24iLg0KPj4+IA0KPj4+IAlUaGFua3MsDQo+Pj4gCVBhdWwN
Cj4+PiANCj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPj4+IHNpcHJlYyBtYWlsaW5nIGxpc3QNCj4+PiBzaXByZWNAaWV0Zi5vcmcNCj4+PiBodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcHJlYw0KPj4gDQo+PiBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gc2lwcmVjIG1haWxp
bmcgbGlzdA0KPj4gc2lwcmVjQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL3NpcHJlYw0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fDQo+c2lwcmVjIG1haWxpbmcgbGlzdA0KPnNpcHJlY0BpZXRmLm9yZw0K
Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lwcmVjDQoNCg==


From nobody Tue Jun 16 15:00:38 2015
Return-Path: <eckelcu@cisco.com>
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 4406A1AC3B6 for <siprec@ietfa.amsl.com>; Tue, 16 Jun 2015 15:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.111
X-Spam-Level: 
X-Spam-Status: No, score=-12.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6, J_CHICKENPOX_38=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 TogiORX434Kr for <siprec@ietfa.amsl.com>; Tue, 16 Jun 2015 15:00:33 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B476B1AC3B5 for <siprec@ietf.org>; Tue, 16 Jun 2015 15:00:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9058; q=dns/txt; s=iport; t=1434492033; x=1435701633; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=XPOHPXgF2ZOWDUMVckbsxsyjkJr7ijeCf0CWvfzN31c=; b=Gzco/7HaSG90S9IDY14Cqx6r1ckv4e8HMfc8DaCd8DE5szub2/9Dpslj D3rd10WbW4LbqFj0/ckjOB1u40YKTcrZnzYzVzWPggwqf7N6TNxMJC/hC Un86IJaVnw77YcKIeF5gAVLtI3Ddx3jXBisA41cYelmiI+St4I8SjFbZK c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CwBACHm4BV/40NJK1bgxBUXwaDGLsGCYFbCoUuSgIcgSo4FAEBAQEBAQGBCoQiAQEBBAEBATE6FwQCAQgRAwECAQQoAgIlCx0IAgQBEogvDZlznREGllgBAQEBAQEBAQEBAQEBAQEBAQEBAQETBIEbiimEayIGglyBSwWGeoxlAYtEgTOECYpghCGDWyZjgSgcFYE9b4FGgQEBAQE
X-IronPort-AV: E=Sophos;i="5.13,628,1427760000";  d="scan'208";a="2183792"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-9.cisco.com with ESMTP; 16 Jun 2015 22:00:32 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t5GM0WxH028750 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 16 Jun 2015 22:00:32 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.83]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0195.001; Tue, 16 Jun 2015 17:00:32 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, Alissa Cooper <alissa@cooperw.in>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQmLk88qib+VBCPkal/XHgfVcX0p2R3wyAgAYmH4CAEbOjgIADv1mAgAI0lwA=
Date: Tue, 16 Jun 2015 22:00:31 +0000
Message-ID: <D1A5E31A.4FA7C%eckelcu@cisco.com>
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu> <D1921296.4E781%eckelcu@cisco.com> <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in> <D1A44B8B.343CD%rmohanr@cisco.com>
In-Reply-To: <D1A44B8B.343CD%rmohanr@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [10.154.176.41]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <67093DD5ED4408409778C7A9FD7D19E7@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/0Jom8ABRPl-JQKwAE-KIJ4C7ECw>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: Tue, 16 Jun 2015 22:00:36 -0000

SGkgUmFtLA0KDQpUaGFua3MgZm9yIHlvdXIgY29tbWVudHMuIFlvdXIgc3VnZ2VzdGlvbnMgYWxp
Z24gd2l0aCBQYXVsoa9zIGFuZCBtb3N0bHkNCmFkZHJlc3MgdGhlIGNvbmNlcm5zIHJhaXNlZCBi
eSBCZW4gYW5kIEJhcnJ5LiBUaGV5IHNvdW5kIGZpbmUgdG8gbWUgYXMNCndlbGwuDQoNCkkgaGFk
IGEgbG9vayBhdCB0aGUgZHJhZnQgYW5kIHRyaWVkIHRvIGRldGVybWluZSB3aGF0IGluIHRoZSBk
cmFmdCBzaG91bGQNCmNoYW5nZS4gRWl0aGVyIEkgZW5jb3VudGVyZWQgb3RoZXIgcHJldmlvdXNs
eSB1bmRpc2NvdmVyZWQgaXNzdWVzLCBvciBJoa9tDQpqdXN0IGNvbmZ1c2VkIHJlZ2FyZGluZyBD
b250ZW50LVR5cGUgYW5kIE1JTUUgdHlwZXMuDQoNClNlY3Rpb24gOSByZWFkcywNCg0KICBTb21l
IG1ldGFkYXRhIGF0dHJpYnV0ZXMgYXJlIGNvbnRhaW5lZCBpbiBTRFAsIGFuZCBvdGhlcnMgYXJl
DQogIGNvbnRhaW5lZCBpbiBhIG5ldyBjb250ZW50IHR5cGUgImFwcGxpY2F0aW9uL3JzLW1ldGFk
YXRhobEuDQoNClRoaXMgaXMgZmluZS4gQnV0IHRoZW4gdGhlIGV4YW1wbGUgaW4gc2VjdGlvbiA5
LjEgaGFzIHRoZSBmb2xsb3dpbmc6DQoNCiAgQWNjZXB0OiBhcHBsaWNhdGlvbi9zZHAsIGFwcGxp
Y2F0aW9uL3JzLW1ldGFkYXRhLXJlcXVlc3QNCiAgQ29udGFjdDogPHNpcDoyMDAwQHNyYy5leGFt
cGxlLmNvbT47K3NpcC5zcmMNCiAgQ29udGVudC1UeXBlOiBtdWx0aXBhcnQvbWl4ZWQ7Ym91bmRh
cnk9Zm9vYmFyDQogIENvbnRlbnQtTGVuZ3RoOiBbbGVuZ3RoXQ0KDQogIC0tZm9vYmFyDQogIENv
bnRlbnQtVHlwZTogYXBwbGljYXRpb24vc2RwDQoNCiAgdj0wDQogIG89U1JTIDI4OTA4NDQ1MjYg
Mjg5MDg0NDUyNiBJTiBJUDQgMTk4LjUxLjEwMC4xDQogIHM9LQ0KICBjPUlOIElQNCAxOTguNTEu
MTAwLjENCiAgdD0wIDANCiAgbT1hdWRpbyAxMjI0MCBSVFAvQVZQIDAgNCA4DQogIGE9c2VuZG9u
bHkNCiAgYT1sYWJlbDoxDQoNCiAgLS1mb29iYXINCiAgQ29udGVudC1UeXBlOiBhcHBsaWNhdGlv
bi9ycy1tZXRhZGF0YQ0KICBDb250ZW50LURpc3Bvc2l0aW9uOiByZWNvcmRpbmctc2Vzc2lvbg0K
DQogIFttZXRhZGF0YSBjb250ZW50XQ0KDQpBbmQgU2VjdGlvbiA5LjIgaGFzIHRoZSBmb2xsb3dp
bmc6DQoNCiAgVGhlIFNSUyBNVVNUIE5PVCByZXF1ZXN0IGEgZnVsbCBtZXRhZGF0YSBzbmFwc2hv
dCBpbiBhbiBVUERBVEUNCiAgcmVzcG9uc2Ugb3IgaW4gYW55IG90aGVyIFNJUCB0cmFuc2FjdGlv
bi4gVGhlIGZvcm1hdCBvZiB0aGUgY29udGVudA0KICBpcyAiYXBwbGljYXRpb24vcnMtbWV0YWRh
dGEtcmVxdWVzdCIsIGFuZCB0aGUgYm9keSBmb3JtYXQgaXMgYSBzaW1wbGUNCiAgdGV4dC1iYXNl
ZCBmb3JtYXQuIFRoZSBmb2xsb3dpbmcgc2hvd3MgYW4gZXhhbXBsZToNCg0KSXMgImFwcGxpY2F0
aW9uL3JzLW1ldGFkYXRhLXJlcXVlc3ShsSBtZWFudCB0byBiZSB1c2VkIGZvciByZXF1ZXN0cyBm
cm9tDQp0aGUgU1JTLCBhbmQgYm90aCBhcHBsaWNhdGlvbi9ycy1tZXRhZGF0YSBhbmQNCmFwcGxp
Y2F0aW9uL3JzLW1ldGFkYXRhLXJlcXVlc3QgbmVlZCB0byBiZSBkZWZpbmVkIGFuZCByZWdpc3Rl
cmVkIGluIHRoaXMNCmRyYWZ0Pw0KDQoNCkNoZWVycywNCkNoYXJsZXMNCg0KDQoNCk9uIDYvMTQv
MTUsIDEwOjE5IFBNLCAiUmFtIE1vaGFuIFIgKHJtb2hhbnIpIiA8cm1vaGFuckBjaXNjby5jb20+
IHdyb3RlOg0KDQo+UGxlYXNlIHNlZSBpbmxpbmUgZm9yIGNvbW1lbnRzDQo+DQo+LS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj5Gcm9tOiBBbGlzc2EgQ29vcGVyIDxhbGlzc2FAY29vcGVydy5p
bj4NCj5EYXRlOiBTYXR1cmRheSwgMTMgSnVuZSAyMDE1IDE6MzYgYW0NCj5UbzogIkNoYXJsZXMg
RWNrZWwgKGVja2VsY3UpIiA8ZWNrZWxjdUBjaXNjby5jb20+DQo+Q2M6ICJzaXByZWNAaWV0Zi5v
cmciIDxzaXByZWNAaWV0Zi5vcmc+DQo+U3ViamVjdDogUmU6IFtzaXByZWNdIEJhcnJ5IExlaWJh
J3MgRGlzY3VzcyBvbg0KPmRyYWZ0LWlldGYtc2lwcmVjLXByb3RvY29sLTE2OiAod2l0aCBESVND
VVNTIGFuZCBDT01NRU5UKQ0KPg0KPj5TdGlsbCBsb29raW5nIGZvciBmb2xrcyB0byByZXNwb25k
IG9uIHRoaXMgoaogaGF2ZSBvbmx5IHNlZW4gYSByZXNwb25zZQ0KPj5mcm9tIFBhdWwuDQo+Pg0K
Pj5BbGlzc2ENCj4+DQo+Pk9uIEp1biAxLCAyMDE1LCBhdCAxOjQ2IFBNLCBDaGFybGVzIEVja2Vs
IChlY2tlbGN1KSA8ZWNrZWxjdUBjaXNjby5jb20+DQo+Pndyb3RlOg0KPj4NCj4+PiBJqfZtIGhv
cGluZyB0aGUgYXV0aG9ycyBvZiB0aGUgbWV0YWRhdGEgZHJhZnQgY2FuIGNoaW1lIGluIGFzIHRv
IHdoYXQNCj4+PnRoZXkNCj4+PiB3b3VsZCBsaWtlIHRvIHNlZSBjaGFuZ2VkIGhlcmUuDQo+Pj4g
DQo+Pj4gQ2hlZXJzLA0KPj4+IENoYXJsZXMNCj4+PiANCj4+PiBPbiA1LzI4LzE1LCA4OjUyIEFN
LCAiUGF1bCBLeXppdmF0IiA8cGt5eml2YXRAYWx1bS5taXQuZWR1PiB3cm90ZToNCj4+PiANCj4+
Pj4gT24gNS8yNy8xNSA0OjEwIFBNLCBCYXJyeSBMZWliYSB3cm90ZToNCj4+Pj4gDQo+Pj4+PiAN
Cj4+Pj4+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQ0KPj4+Pj4gRElTQ1VTUzoNCj4+Pj4+IA0KPj4+Pj4tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQo+Pj4+PiANCj4+Pj4+IEkgaGF2ZSB0byByYWlzZSBvbmUgb2YgQmVuJ3MgY29tbWVu
dHMgdG8gRElTQ1VTUywgYWZ0ZXIgZ2l2aW5nIGl0IGENCj4+Pj4+bG90DQo+Pj4+PiBvZiB0aG91
Z2h0LiAgV2UgdGFsa2VkIGFib3V0IGl0IGJlZm9yZSBCZW4gcG9zdGVkIGhpcyBiYWxsb3QsIGFu
ZCBJDQo+Pj4+PnNhaWQNCj4+Pj4+IHRoYXQgSSB0aG91Z2h0IHRoZSB3YXkgdGhlIHJzLW1ldGFk
YXRhLXJlcXVlc3Qgc3VidHlwZSBpcyB1c2VkIGlzDQo+Pj4+PiBhYnVzaW5nDQo+Pj4+PiBtZWRp
YSB0eXBlczogbWVkaWEgdHlwZXMgYXJlIG1lYW50IHRvIGxhYmVsIGNvbnRhaW5lcnMgZm9yIHBy
b3RvY29sDQo+Pj4+PiBlbGVtZW50cywgYnV0IGFyZSBub3QgbWVhbnQgdG8gYmUgcHJvdG9jb2wg
ZWxlbWVudHMgdGhlbXNlbHZlcy4gIEkNCj4+Pj4+c2FpZA0KPj4+Pj4gSQ0KPj4+Pj4gZGlkbid0
IHdhbnQgdG8gZ2V0IHRvbyB3b3VuZCB1cCB3aXRoIHRoYXQsIHRob3VnaCwgYW5kIEkgZG9uJ3Qu
Li4NCj4+Pj4+IA0KPj4+Pj4gLi4uZXhjZXB0IHRoYXQgaXQgYWxsb3dzIG5vIHJvb20gZm9yIGV4
dGVuc2liaWxpdHkuICBBbmQgdGhlIG1vbWVudA0KPj4+Pj55b3UNCj4+Pj4+IG5lZWQgYW5vdGhl
ciwgZGlmZmVyZW50IHJlcXVlc3QsIHdlIHNlZSB3aHkgdGhpcyBtZWNoYW5pc20gaXMNCj4+Pj4+
YWJ1c2l2ZS4NCj4+Pj4+IE5vdywgeW91IG1heSBzYXkgdGhhdCB5b3UgZG9uJ3Qgc2VlIGFueSBu
ZWVkIGZvciBleHRlbnNpYmlsaXR5LCBidXQNCj4+Pj4+IHdlJ3ZlDQo+Pj4+PiBiZWVuIHByb3Zl
biB3cm9uZyBpbiB0aG9zZSBzb3J0cyBvZiBhc3N1bXB0aW9ucyBtYW55IHRpbWVzLg0KPj4+Pj4g
DQo+Pj4+PiBTbywgdGhlIGRpc2N1c3Npb24gaXMgYWJvdXQgaG93IHlvdSB3aWxsIGRlYWwgd2l0
aCB0aGF0Lg0KPj4+Pj5TcGVjaWZpY2FsbHksDQo+Pj4+PiBhbiBhbHRlcm5hdGl2ZSB3b3VsZCBi
ZSB0byBoYXZlIGFuIHJzLXJlcXVlc3Qgc3VidHlwZSwgd2l0aCBhDQo+Pj4+PiBjb250ZW50LXR5
cGUgcGFyYW1ldGVyIHN1Y2ggYXMgInJlcT1tZXRhZGF0YSIgKG9yIGV2ZW4gdXNlDQo+Pj4+PnJz
LW1ldGFkYXRhDQo+Pj4+PiB3aXRoICJyZXE9c25hcHNob3QiKSBhbmQgYSBydWxlIHRoYXQgcmVx
PSB2YWx1ZXMgdGhhdCBhcmUgbm90DQo+Pj4+PnJlY29nbmlzZWQNCj4+Pj4+IGJlIGlnbm9yZWQu
ICBJZiB0aGlzIHNob3VsZCBldmVyIG5lZWQgdG8gYmUgZXh0ZW5kZWQsIG90aGVyICJyZXE9Ig0K
Pj4+Pj4gdmFsdWVzDQo+Pj4+PiBjb3VsZCBiZSBkZWZpbmVkLiAgQSByZWdpc3RyeSBjb3VsZCBi
ZSBjcmVhdGVkIGluIGZ1dHVyZSwgaWYgdGhlcmUNCj4+Pj4+dHVybnMNCj4+Pj4+IG91dCB0byBi
ZSBhIG5lZWQuDQo+Pj4+PiANCj4+Pj4+IFRoZXJlIGFyZSBvdGhlciBvcHRpb25zLCBhcyB3ZWxs
LCBidXQgdGhlIG1haW4gcXVlc3Rpb24gaXMgd2h5IGFyZQ0KPj4+Pj55b3UNCj4+Pj4+IHN1cmUg
dGhhdCBubyBzdWNoIGV4dGVuc2liaWxpdHkgaXMgbmVlZGVkPw0KPj4+PiANCj4+Pj4gSSBhZ3Jl
ZSB3aXRoIEJhcnJ5IGFuZCBCZW4gaGVyZTogSSB0aGluayB3ZSBzaG91bGQgaGF2ZSBzb21lIHN5
bnRheCBpbg0KPj4+PiB0aGUgYm9keSB0aGF0IGluZGljYXRlcyBhIHJlcXVlc3QgZm9yIGEgc25h
cHNob3QsIGFuZCB0aGF0IGhhcw0KPj4+PnBvdGVudGlhbA0KPj4+PiBmb3IgZnV0dXJlIGV4dGVu
c2lvbi4NCj4NCj5JIGFtIGZpbmUgd2l0aCBoYXZpbmcgc3VjaCBhIGV4dGVuc2lvbiB0byB1c2Ug
cnMtbWV0YWRhdGEgd2l0aCByZXE9IHNvDQo+dGhhdCBpdCBhbGxvd3MgZm9yIGFueSBleHRlbnNp
b25zIHRoYXQgd291bGQgY29tZSBpbiBmdXR1cmUuIEZvciB0aGUNCj5jdXJyZW50IHZlcnNpb24g
b2YgU0lQUkVDIHdlIGNvdWxkIHVzZSByZXE9c25hcHNob3QuDQo+IA0KPj4+PiANCj4+Pj4+IEFs
c28sIHdoYXQgeW91J3JlIGRvaW5nIHdpdGggY29udGVudC1kaXNwb3NpdGlvbiBpc24ndCBpbiBh
Y2NvcmQgd2l0aA0KPj4+Pj4gd2hhdCB0aGF0IGZpZWxkIGlzIGZvcjogaXQgaXMgZm9yIGRlc2Ny
aWJpbmcgaG93IHRoZSBpbmZvcm1hdGlvbiBpbg0KPj4+Pj50aGUNCj4+Pj4+IG1lc3NhZ2UgcGFy
dCBzaG91bGQgYmUgcHJlc2VudGVkIC0tIG5vdCB3aGF0IGl0J3MgbWVhbnQgdG8gY29udGFpbiBv
cg0KPj4+Pj5iZQ0KPj4+Pj4gdXNlZCBmb3IuICBUaGlzLCB0b28sIGNvdWxkIGJlIGJldHRlciBo
YW5kbGVkIHdpdGggYSBjb250ZW50LXR5cGUNCj4+Pj4+IHBhcmFtZXRlci4NCj4NCj5Db250ZW50
LURpc3Bvc2l0aW9uIGhlYWRlciBmaWVsZCBkZXNjcmliZXMgaG93IHRoZSBtZXNzYWdlIGJvZHkg
cGFydCBpcyB0bw0KPmJlIGludGVycHJldGVkDQo+ICAgYnkgdGhlIFVBQyBvciBVQVMuIEFzIFNJ
UFJFQyBtZXRhZGF0YSBpcyB1c2VkIGRpZmZlcmVudGx5IGJ5IHJlY29yZGVycw0KPnRoYW4gdGhl
IGJvZHkgdHlwZXMgbGlrZSBTRFAgdGhlIENvbnRlbnQtRGlzcG9zaXRpb24gobBzZXNzaW9uobEg
ZGVmaW5lZCBpbg0KPlJGQyAzMjYxIGNhbm5vdCBiZSB1c2VkIGhlcmUuDQo+SSB0aGluayBpdHMg
ZmluZSB0byBoYXZlIG5ldyBDLUQuIEFsc28gSSBzZWUgc2V2ZXJhbCBvZiBvdGhlciBTSVAgUkZD
cw0KPihsaWtlIFJGQyA1NjIxLCBSRkMgMzIwNCkgdGhhdCBkZWZpbmVzIG5ldyBib2R5IGRlZmlu
ZXMgaXRzIG93biBDLUQuDQo+DQo+U28gd2UgY291bGQgc3RpY2sgd2l0aCBjdXJyZW50IEMtRCBp
biB0aGUgZHJhZnQgLg0KPg0KPlJlZ2FyZHMsDQo+UmFtDQo+DQo+Pj4+IA0KPj4+PiBJIGRpc2Fn
cmVlIHdpdGggQmFycnkgaGVyZS4gSGUgaXMgYW4gYXBwIGd1eSwgc28gSSBndWVzcyBpdCBtYWtl
cw0KPj4+PnNlbnNlDQo+Pj4+IHRoYXQgaGUgd291bGQgc2F5IHRoaXMuIEJ1dCBhbG1vc3Qgbm9u
ZSBvZiB0aGUgQ29udGVudC1EaXNwb3NpdGlvbnMNCj4+Pj51c2VkDQo+Pj4+IHdpdGggU0lQIGFy
ZSBhY3R1YWxseSByZW5kZXJlZCB0byBhIGh1bWFuLiBGb3IgaW5zdGFuY2UgInNlc3Npb24iIGZv
cg0KPj4+PlNEUC4NCj4+Pj4gDQo+Pj4+IEkgc2VlIHRoZSBkaXN0aW5jdGlvbiBiZXR3ZWVuIEMt
VCBhbmQgQy1EIGJlaW5nIGEgZGlzdGluY3Rpb24gYmV0d2Vlbg0KPj4+PiBob3cgaXQgaXMgcmVw
cmVzZW50ZWQgYW5kIGhvdyBpdCBpcyB1c2VkLiBUaGVyZSBjb3VsZCBiZSB0d28gZGlmZmVyZW50
DQo+Pj4+IEMtVHMgZm9yIFNEUCBhbmQgU0RQbmcsIGJ1dCB0aGV5IHdvdWxkIGJvdGggYmUgQy1E
ICJzZXNzaW9uIi4gVGhlDQo+Pj4+U0lQUkVDDQo+Pj4+IG1ldGFkYXRhIGlzIHVzZWQgdmVyeSBk
aWZmZXJlbnRseSwgYW5kIEMtRCBpcyB0aGUgd2F5IHRvIGRpc3Rpbmd1aXNoDQo+Pj4+aXQNCj4+
Pj4gZnJvbSAic2Vzc2lvbiIuDQo+Pj4+IA0KPj4+PiAJVGhhbmtzLA0KPj4+PiAJUGF1bA0KPj4+
PiANCj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cj4+Pj4gc2lwcmVjIG1haWxpbmcgbGlzdA0KPj4+PiBzaXByZWNAaWV0Zi5vcmcNCj4+Pj4gaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXByZWMNCj4+PiANCj4+PiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+IHNpcHJlYyBt
YWlsaW5nIGxpc3QNCj4+PiBzaXByZWNAaWV0Zi5vcmcNCj4+PiBodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3NpcHJlYw0KPj4NCj4+X19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj4+c2lwcmVjIG1haWxpbmcgbGlzdA0KPj5zaXByZWNA
aWV0Zi5vcmcNCj4+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXByZWMN
Cj4NCg0K


From nobody Tue Jun 16 15:33:52 2015
Return-Path: <eckelcu@cisco.com>
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 1B7A31ACD42; Tue, 16 Jun 2015 15:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 QwGKmK6cwFKb; Tue, 16 Jun 2015 15:33:49 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EBE11ACD09; Tue, 16 Jun 2015 15:33:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3331; q=dns/txt; s=iport; t=1434494018; x=1435703618; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=eFRb3DM0ltcH7Wa4Nz2PhANqle1q9E4qs6PCKDDBzJo=; b=XRjB9N3JBIljH3QLIrPbBJWtdaYoqs2/FhIFbE8wFQCGYQ2U0JOAbTNJ h7r7FhWNTgnEqFOgcLXnlJyUseeLgluUfy15IkWhOSUgqzj3mhhSsGgLR 9rziTSOioHIXhNjv9jDSwLY7YBFdMZBjAgP7n0jxhUsVJeyxCGeG8DqtV 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CJBQC9o4BV/4gNJK1bgxCBMwa5c4Q0h10CgUY5EwEBAQEBAQGBCoQjAQEEOi4REAIBCBgeEDIlAgQBDQWIL81zAQEBAQEBAQEBAQEBAQEBAQEBARmLRIUGB4QtAQSTXwGLRIEzkwqDWyZjgVmBPW+BRoEBAQEB
X-IronPort-AV: E=Sophos;i="5.13,629,1427760000"; d="scan'208";a="159905239"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-2.cisco.com with ESMTP; 16 Jun 2015 22:33:37 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t5GMXbar025241 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 16 Jun 2015 22:33:37 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.83]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Tue, 16 Jun 2015 17:33:37 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "Hutton, Andrew" <andrew.hutton@unify.com>, The IESG <iesg@ietf.org>
Thread-Topic: [siprec] Stephen Farrell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS)
Thread-Index: AQHQnKX3WBrtQWZTfUyWzpoDI1UNV52YatCA///IeoCAAHalAIAXBDSA
Date: Tue, 16 Jun 2015 22:33:36 +0000
Message-ID: <D1A5EEDD.4FAC6%eckelcu@cisco.com>
References: <D19203E9.4E739%eckelcu@cisco.com> <556CBE1F.7090000@cs.tcd.ie> <D1923895.4E90E%eckelcu@cisco.com> <556CF312.2060204@cs.tcd.ie>
In-Reply-To: <556CF312.2060204@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [10.154.176.41]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <94EFC7499137CE4E95A5FF2B881E0E60@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/8V0vS3K1qb_8Ay4iy9n_6-Q-98w>
Cc: "siprec@ietf.org" <siprec@ietf.org>, "draft-ietf-siprec-protocol.ad@ietf.org" <draft-ietf-siprec-protocol.ad@ietf.org>, "draft-ietf-siprec-protocol@ietf.org" <draft-ietf-siprec-protocol@ietf.org>, "siprec-chairs@ietf.org" <siprec-chairs@ietf.org>, "draft-ietf-siprec-protocol.shepherd@ietf.org" <draft-ietf-siprec-protocol.shepherd@ietf.org>
Subject: Re: [siprec] Stephen Farrell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS)
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: Tue, 16 Jun 2015 22:33:51 -0000

On 6/1/15, 5:04 PM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:

>
>Hi Charles,
>
>On 02/06/15 00:59, Charles Eckel (eckelcu) wrote:
>> Hi Stephen,
>>=20
>> My comment was meant to be interpreted within the context of an EKT
>> session. In this case, the SRC is still using SRTP-SDES with the SRS for
>> the RS, and using TLS to establish the RS and exchange the keys. But in
>> doing it would not need to decrypt and re-encrypt the payload with a new
>> key.
>
>I guess I need to go check the updated reference(s) on that
>stuff. (It might make sense to shoot out a revision with that
>fixed and other changes just to simplify the discussion, but
>your AD will guide you on that.)
>
>> I may be getting in over my head here, but I believe the SRTP
>> authentication tag would be sufficient to determine the source of the
>>SRTP
>> packets is in fact the SRC and not simply any one of the UAs
>>participating
>> in the CS injecting random SRTP packets encrypted with the same key into
>> the stream.
>
>Yeah, that's one we do need to bottom out on.
>
>> I also expect that in practice there would be a firewall that allows
>>only
>> appropriate SRCs to access the SRS.
>
>Could well be, but even if so, that'd not be considered sufficient
>really I guess.

I checked with Dan Wing on this. Your concerns about spoofing are correct.
Let me paraphrase here:

With a design in which EKT is used within a conference and the SRC
forwards media streams for recording purposes to an SRS using SRTP/SDES
with the same keys, each conference participant could send traffic,
pretending to be any other participant, and the crypto wouldn't protect
against that. But if all the keys are flying around with SDES, the only
way to design a system that protects Alice from spoofing Bob (in a two
party call) is to add a mixer which -- yes -- has to suffer the
decrypt/re-encrypt, so that Alice only talks to/from the mixer, and Bob
only talks to/from the mixer, and Alice and Bob don't know each other's
keys.

Personally I still expect this is a model that will be used due to the
performance characteristics; however, some deployment scenarios will
obviously require tighter security. Would adding something to this effect
in the security considerations section be sufficient?

Cheers,
Charles

>
>S.
>
>
>>=20
>>=20
>> Cheers,
>> Charles
>>=20
>> On 6/1/15, 1:18 PM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:
>>=20
>>>
>>> Hi Charles,
>>>
>>> One question on just one part of this, but one that puzzles me and
>>> may be helpful in clearing this up...
>>>
>>> On 01/06/15 21:03, Charles Eckel (eckelcu) wrote:
>>>> the performance
>>>> and security penalties that come with decrypting and re-encrpting on
>>>>the
>>>> SRC before sending to the SRS.
>>>
>>> If you don't re-encrypt isn't it possible for anyone who is part
>>> of the CS to send bogus packets to the SRS that will then be
>>> recorded? (Assuming the sender can get the packets to the SRS but
>>> let's assume they can, because that's not so hard.)
>>>
>>> Not re-encrypting seems to just be broken, if e.g. this is supposed
>>> to be a thing one could use to hold a rogue trader accountable when
>>> there's big piles of money at stake.
>>>
>>> Ta,
>>> S.
>>>
>>=20


From nobody Wed Jun 17 02:02:07 2015
Return-Path: <rmohanr@cisco.com>
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 A61E21A8728 for <siprec@ietfa.amsl.com>; Wed, 17 Jun 2015 02:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.111
X-Spam-Level: 
X-Spam-Status: No, score=-12.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6, J_CHICKENPOX_38=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 taRa83XLJ2AB for <siprec@ietfa.amsl.com>; Wed, 17 Jun 2015 02:02:03 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 543ED1A8726 for <siprec@ietf.org>; Wed, 17 Jun 2015 02:02:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10310; q=dns/txt; s=iport; t=1434531723; x=1435741323; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=23RqR5L2wbieuwLunnXd5lj9imElgjWhQ8dUOYouJ5M=; b=kSzp9LAd+NFXgFHLphmkdcO/4veREXxEM8OfchRYkrAO/2jCWi4F7g2D tn71oC4ViYH7mga0gqMZ9dZNDmBkpxbF0uiwkqVTVy1OSDDwNQ6qLfcuz InXlxI1yMXbzAxqsfcbV8omHNxyboU+HGArl1/PbEuCptkVeg7TCe/80x U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CNBABuNoFV/49dJa1cgxBUXwaDGLpzCYFdCoUuSgIcgSQ4FAEBAQEBAQGBCoQiAQEBBAEBATE6FwQCAQgRAwECAQQoAgIlCx0IAgQBEogvDZgenREGlkoBAQEBAQEBAQEBAQEBAQEBAQEBARQEgRuKKYRTGCIGglyBSQWGfYxrAYtGgTSECopkhCODWyZjgSgcFYE9b4FGgQIBAQE
X-IronPort-AV: E=Sophos;i="5.13,632,1427760000"; d="scan'208";a="160257458"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Jun 2015 09:02:01 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t5H921hd006440 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 17 Jun 2015 09:02:01 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.106]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Wed, 17 Jun 2015 04:02:01 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, Alissa Cooper <alissa@cooperw.in>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQqNxFwWz4djJr8EWZ26GQ/cDozw==
Date: Wed, 17 Jun 2015 09:01:59 +0000
Message-ID: <D1A73596.34B10%rmohanr@cisco.com>
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu> <D1921296.4E781%eckelcu@cisco.com> <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in> <D1A44B8B.343CD%rmohanr@cisco.com> <D1A5E31A.4FA7C%eckelcu@cisco.com>
In-Reply-To: <D1A5E31A.4FA7C%eckelcu@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [173.39.64.231]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <988C2A7EB614F14197D696911B6D8D2C@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/m_9iEHbAuE7ZzWLRqDaHNIpCm0k>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: Wed, 17 Jun 2015 09:02:05 -0000

SGkgQ2hhcmxlcywNCg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiAiQ2hh
cmxlcyBFY2tlbCAgIChlY2tlbGN1KSIgPGVja2VsY3VAY2lzY28uY29tPg0KRGF0ZTogV2VkbmVz
ZGF5LCAxNyBKdW5lIDIwMTUgMzozMCBhbQ0KVG86IENpc2NvIEVtcGxveWVlIDxybW9oYW5yQGNp
c2NvLmNvbT4sIEFsaXNzYSBDb29wZXIgPGFsaXNzYUBjb29wZXJ3LmluPiwNCiJzaXByZWNAaWV0
Zi5vcmciIDxzaXByZWNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW3NpcHJlY10gQmFycnkgTGVp
YmEncyBEaXNjdXNzIG9uDQpkcmFmdC1pZXRmLXNpcHJlYy1wcm90b2NvbC0xNjogKHdpdGggRElT
Q1VTUyBhbmQgQ09NTUVOVCkNCg0KPkhpIFJhbSwNCj4NCj5UaGFua3MgZm9yIHlvdXIgY29tbWVu
dHMuIFlvdXIgc3VnZ2VzdGlvbnMgYWxpZ24gd2l0aCBQYXVsoa9zIGFuZCBtb3N0bHkNCj5hZGRy
ZXNzIHRoZSBjb25jZXJucyByYWlzZWQgYnkgQmVuIGFuZCBCYXJyeS4gVGhleSBzb3VuZCBmaW5l
IHRvIG1lIGFzDQo+d2VsbC4NCj4NCj5JIGhhZCBhIGxvb2sgYXQgdGhlIGRyYWZ0IGFuZCB0cmll
ZCB0byBkZXRlcm1pbmUgd2hhdCBpbiB0aGUgZHJhZnQgc2hvdWxkDQo+Y2hhbmdlLiBFaXRoZXIg
SSBlbmNvdW50ZXJlZCBvdGhlciBwcmV2aW91c2x5IHVuZGlzY292ZXJlZCBpc3N1ZXMsIG9yIEmh
r20NCj5qdXN0IGNvbmZ1c2VkIHJlZ2FyZGluZyBDb250ZW50LVR5cGUgYW5kIE1JTUUgdHlwZXMu
DQo+DQo+U2VjdGlvbiA5IHJlYWRzLA0KPg0KPiAgU29tZSBtZXRhZGF0YSBhdHRyaWJ1dGVzIGFy
ZSBjb250YWluZWQgaW4gU0RQLCBhbmQgb3RoZXJzIGFyZQ0KPiAgY29udGFpbmVkIGluIGEgbmV3
IGNvbnRlbnQgdHlwZSAiYXBwbGljYXRpb24vcnMtbWV0YWRhdGGhsS4NCj4NCj5UaGlzIGlzIGZp
bmUuIEJ1dCB0aGVuIHRoZSBleGFtcGxlIGluIHNlY3Rpb24gOS4xIGhhcyB0aGUgZm9sbG93aW5n
Og0KPg0KPiAgQWNjZXB0OiBhcHBsaWNhdGlvbi9zZHAsIGFwcGxpY2F0aW9uL3JzLW1ldGFkYXRh
LXJlcXVlc3QNCj4gIENvbnRhY3Q6IDxzaXA6MjAwMEBzcmMuZXhhbXBsZS5jb20+OytzaXAuc3Jj
DQo+ICBDb250ZW50LVR5cGU6IG11bHRpcGFydC9taXhlZDtib3VuZGFyeT1mb29iYXINCj4gIENv
bnRlbnQtTGVuZ3RoOiBbbGVuZ3RoXQ0KPg0KPiAgLS1mb29iYXINCj4gIENvbnRlbnQtVHlwZTog
YXBwbGljYXRpb24vc2RwDQo+DQo+ICB2PTANCj4gIG89U1JTIDI4OTA4NDQ1MjYgMjg5MDg0NDUy
NiBJTiBJUDQgMTk4LjUxLjEwMC4xDQo+ICBzPS0NCj4gIGM9SU4gSVA0IDE5OC41MS4xMDAuMQ0K
PiAgdD0wIDANCj4gIG09YXVkaW8gMTIyNDAgUlRQL0FWUCAwIDQgOA0KPiAgYT1zZW5kb25seQ0K
PiAgYT1sYWJlbDoxDQo+DQo+ICAtLWZvb2Jhcg0KPiAgQ29udGVudC1UeXBlOiBhcHBsaWNhdGlv
bi9ycy1tZXRhZGF0YQ0KPiAgQ29udGVudC1EaXNwb3NpdGlvbjogcmVjb3JkaW5nLXNlc3Npb24N
Cj4NCj4gIFttZXRhZGF0YSBjb250ZW50XQ0KPg0KPkFuZCBTZWN0aW9uIDkuMiBoYXMgdGhlIGZv
bGxvd2luZzoNCj4NCj4gIFRoZSBTUlMgTVVTVCBOT1QgcmVxdWVzdCBhIGZ1bGwgbWV0YWRhdGEg
c25hcHNob3QgaW4gYW4gVVBEQVRFDQo+ICByZXNwb25zZSBvciBpbiBhbnkgb3RoZXIgU0lQIHRy
YW5zYWN0aW9uLiBUaGUgZm9ybWF0IG9mIHRoZSBjb250ZW50DQo+ICBpcyAiYXBwbGljYXRpb24v
cnMtbWV0YWRhdGEtcmVxdWVzdCIsIGFuZCB0aGUgYm9keSBmb3JtYXQgaXMgYSBzaW1wbGUNCj4g
IHRleHQtYmFzZWQgZm9ybWF0LiBUaGUgZm9sbG93aW5nIHNob3dzIGFuIGV4YW1wbGU6DQo+DQo+
SXMgImFwcGxpY2F0aW9uL3JzLW1ldGFkYXRhLXJlcXVlc3ShsSBtZWFudCB0byBiZSB1c2VkIGZv
ciByZXF1ZXN0cyBmcm9tDQo+dGhlIFNSUywgYW5kIGJvdGggYXBwbGljYXRpb24vcnMtbWV0YWRh
dGEgYW5kDQo+YXBwbGljYXRpb24vcnMtbWV0YWRhdGEtcmVxdWVzdCBuZWVkIHRvIGJlIGRlZmlu
ZWQgYW5kIHJlZ2lzdGVyZWQgaW4gdGhpcw0KPmRyYWZ0Pw0KDQpJIGJlbGlldmUgc28uIEkgdGhp
bmsgYXBwbGljYXRpb24vcnMtbWV0YWRhdGEtcmVxdWVzdCB3YXMgYWRkZWQgZm9yIFNSQyB0bw0K
cmVxdWVzdCBhIHNuYXBzaG90LiBGb3IgU1JDIHdoZW5ldmVyIGl0IGluZGljYXRlcyBtZXRhZGF0
YShlaXRoZXIgaW4gYQ0KSU5WSVRFL1VQREFURS9SRS1JTlZJVEUpIG9yIGluIGEgcmVzcG9uc2Ug
dG8gYSByZXF1ZXN0IG1lc3NhZ2UgZnJvbSBTUlMsDQppdCBzaG91bGQgYWx3YXlzIGhhdmUgY29u
dGVudCB0eXBlIGFzIGFwcGxpY2F0aW9uL3JzLW1ldGFkYXRhLg0KDQpSZWdhcmRzLA0KUmFtDQo+
DQo+DQo+Q2hlZXJzLA0KPkNoYXJsZXMNCj4NCj4NCj4NCj5PbiA2LzE0LzE1LCAxMDoxOSBQTSwg
IlJhbSBNb2hhbiBSIChybW9oYW5yKSIgPHJtb2hhbnJAY2lzY28uY29tPiB3cm90ZToNCj4NCj4+
UGxlYXNlIHNlZSBpbmxpbmUgZm9yIGNvbW1lbnRzDQo+Pg0KPj4tLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPj5Gcm9tOiBBbGlzc2EgQ29vcGVyIDxhbGlzc2FAY29vcGVydy5pbj4NCj4+RGF0
ZTogU2F0dXJkYXksIDEzIEp1bmUgMjAxNSAxOjM2IGFtDQo+PlRvOiAiQ2hhcmxlcyBFY2tlbCAo
ZWNrZWxjdSkiIDxlY2tlbGN1QGNpc2NvLmNvbT4NCj4+Q2M6ICJzaXByZWNAaWV0Zi5vcmciIDxz
aXByZWNAaWV0Zi5vcmc+DQo+PlN1YmplY3Q6IFJlOiBbc2lwcmVjXSBCYXJyeSBMZWliYSdzIERp
c2N1c3Mgb24NCj4+ZHJhZnQtaWV0Zi1zaXByZWMtcHJvdG9jb2wtMTY6ICh3aXRoIERJU0NVU1Mg
YW5kIENPTU1FTlQpDQo+Pg0KPj4+U3RpbGwgbG9va2luZyBmb3IgZm9sa3MgdG8gcmVzcG9uZCBv
biB0aGlzIKGqIGhhdmUgb25seSBzZWVuIGEgcmVzcG9uc2UNCj4+PmZyb20gUGF1bC4NCj4+Pg0K
Pj4+QWxpc3NhDQo+Pj4NCj4+Pk9uIEp1biAxLCAyMDE1LCBhdCAxOjQ2IFBNLCBDaGFybGVzIEVj
a2VsIChlY2tlbGN1KSA8ZWNrZWxjdUBjaXNjby5jb20+DQo+Pj53cm90ZToNCj4+Pg0KPj4+PiBJ
qfZtIGhvcGluZyB0aGUgYXV0aG9ycyBvZiB0aGUgbWV0YWRhdGEgZHJhZnQgY2FuIGNoaW1lIGlu
IGFzIHRvIHdoYXQNCj4+Pj50aGV5DQo+Pj4+IHdvdWxkIGxpa2UgdG8gc2VlIGNoYW5nZWQgaGVy
ZS4NCj4+Pj4gDQo+Pj4+IENoZWVycywNCj4+Pj4gQ2hhcmxlcw0KPj4+PiANCj4+Pj4gT24gNS8y
OC8xNSwgODo1MiBBTSwgIlBhdWwgS3l6aXZhdCIgPHBreXppdmF0QGFsdW0ubWl0LmVkdT4gd3Jv
dGU6DQo+Pj4+IA0KPj4+Pj4gT24gNS8yNy8xNSA0OjEwIFBNLCBCYXJyeSBMZWliYSB3cm90ZToN
Cj4+Pj4+IA0KPj4+Pj4+IA0KPj4+Pj4+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+Pj4+Pj4tDQo+Pj4+Pj4gRElT
Q1VTUzoNCj4+Pj4+PiANCj4+Pj4+Pi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPj4+Pj4+LQ0KPj4+Pj4+IA0KPj4+
Pj4+IEkgaGF2ZSB0byByYWlzZSBvbmUgb2YgQmVuJ3MgY29tbWVudHMgdG8gRElTQ1VTUywgYWZ0
ZXIgZ2l2aW5nIGl0IGENCj4+Pj4+PmxvdA0KPj4+Pj4+IG9mIHRob3VnaHQuICBXZSB0YWxrZWQg
YWJvdXQgaXQgYmVmb3JlIEJlbiBwb3N0ZWQgaGlzIGJhbGxvdCwgYW5kIEkNCj4+Pj4+PnNhaWQN
Cj4+Pj4+PiB0aGF0IEkgdGhvdWdodCB0aGUgd2F5IHRoZSBycy1tZXRhZGF0YS1yZXF1ZXN0IHN1
YnR5cGUgaXMgdXNlZCBpcw0KPj4+Pj4+IGFidXNpbmcNCj4+Pj4+PiBtZWRpYSB0eXBlczogbWVk
aWEgdHlwZXMgYXJlIG1lYW50IHRvIGxhYmVsIGNvbnRhaW5lcnMgZm9yIHByb3RvY29sDQo+Pj4+
Pj4gZWxlbWVudHMsIGJ1dCBhcmUgbm90IG1lYW50IHRvIGJlIHByb3RvY29sIGVsZW1lbnRzIHRo
ZW1zZWx2ZXMuICBJDQo+Pj4+Pj5zYWlkDQo+Pj4+Pj4gSQ0KPj4+Pj4+IGRpZG4ndCB3YW50IHRv
IGdldCB0b28gd291bmQgdXAgd2l0aCB0aGF0LCB0aG91Z2gsIGFuZCBJIGRvbid0Li4uDQo+Pj4+
Pj4gDQo+Pj4+Pj4gLi4uZXhjZXB0IHRoYXQgaXQgYWxsb3dzIG5vIHJvb20gZm9yIGV4dGVuc2li
aWxpdHkuICBBbmQgdGhlIG1vbWVudA0KPj4+Pj4+eW91DQo+Pj4+Pj4gbmVlZCBhbm90aGVyLCBk
aWZmZXJlbnQgcmVxdWVzdCwgd2Ugc2VlIHdoeSB0aGlzIG1lY2hhbmlzbSBpcw0KPj4+Pj4+YWJ1
c2l2ZS4NCj4+Pj4+PiBOb3csIHlvdSBtYXkgc2F5IHRoYXQgeW91IGRvbid0IHNlZSBhbnkgbmVl
ZCBmb3IgZXh0ZW5zaWJpbGl0eSwgYnV0DQo+Pj4+Pj4gd2UndmUNCj4+Pj4+PiBiZWVuIHByb3Zl
biB3cm9uZyBpbiB0aG9zZSBzb3J0cyBvZiBhc3N1bXB0aW9ucyBtYW55IHRpbWVzLg0KPj4+Pj4+
IA0KPj4+Pj4+IFNvLCB0aGUgZGlzY3Vzc2lvbiBpcyBhYm91dCBob3cgeW91IHdpbGwgZGVhbCB3
aXRoIHRoYXQuDQo+Pj4+Pj5TcGVjaWZpY2FsbHksDQo+Pj4+Pj4gYW4gYWx0ZXJuYXRpdmUgd291
bGQgYmUgdG8gaGF2ZSBhbiBycy1yZXF1ZXN0IHN1YnR5cGUsIHdpdGggYQ0KPj4+Pj4+IGNvbnRl
bnQtdHlwZSBwYXJhbWV0ZXIgc3VjaCBhcyAicmVxPW1ldGFkYXRhIiAob3IgZXZlbiB1c2UNCj4+
Pj4+PnJzLW1ldGFkYXRhDQo+Pj4+Pj4gd2l0aCAicmVxPXNuYXBzaG90IikgYW5kIGEgcnVsZSB0
aGF0IHJlcT0gdmFsdWVzIHRoYXQgYXJlIG5vdA0KPj4+Pj4+cmVjb2duaXNlZA0KPj4+Pj4+IGJl
IGlnbm9yZWQuICBJZiB0aGlzIHNob3VsZCBldmVyIG5lZWQgdG8gYmUgZXh0ZW5kZWQsIG90aGVy
ICJyZXE9Ig0KPj4+Pj4+IHZhbHVlcw0KPj4+Pj4+IGNvdWxkIGJlIGRlZmluZWQuICBBIHJlZ2lz
dHJ5IGNvdWxkIGJlIGNyZWF0ZWQgaW4gZnV0dXJlLCBpZiB0aGVyZQ0KPj4+Pj4+dHVybnMNCj4+
Pj4+PiBvdXQgdG8gYmUgYSBuZWVkLg0KPj4+Pj4+IA0KPj4+Pj4+IFRoZXJlIGFyZSBvdGhlciBv
cHRpb25zLCBhcyB3ZWxsLCBidXQgdGhlIG1haW4gcXVlc3Rpb24gaXMgd2h5IGFyZQ0KPj4+Pj4+
eW91DQo+Pj4+Pj4gc3VyZSB0aGF0IG5vIHN1Y2ggZXh0ZW5zaWJpbGl0eSBpcyBuZWVkZWQ/DQo+
Pj4+PiANCj4+Pj4+IEkgYWdyZWUgd2l0aCBCYXJyeSBhbmQgQmVuIGhlcmU6IEkgdGhpbmsgd2Ug
c2hvdWxkIGhhdmUgc29tZSBzeW50YXgNCj4+Pj4+aW4NCj4+Pj4+IHRoZSBib2R5IHRoYXQgaW5k
aWNhdGVzIGEgcmVxdWVzdCBmb3IgYSBzbmFwc2hvdCwgYW5kIHRoYXQgaGFzDQo+Pj4+PnBvdGVu
dGlhbA0KPj4+Pj4gZm9yIGZ1dHVyZSBleHRlbnNpb24uDQo+Pg0KPj5JIGFtIGZpbmUgd2l0aCBo
YXZpbmcgc3VjaCBhIGV4dGVuc2lvbiB0byB1c2UgcnMtbWV0YWRhdGEgd2l0aCByZXE9IHNvDQo+
PnRoYXQgaXQgYWxsb3dzIGZvciBhbnkgZXh0ZW5zaW9ucyB0aGF0IHdvdWxkIGNvbWUgaW4gZnV0
dXJlLiBGb3IgdGhlDQo+PmN1cnJlbnQgdmVyc2lvbiBvZiBTSVBSRUMgd2UgY291bGQgdXNlIHJl
cT1zbmFwc2hvdC4NCj4+IA0KPj4+Pj4gDQo+Pj4+Pj4gQWxzbywgd2hhdCB5b3UncmUgZG9pbmcg
d2l0aCBjb250ZW50LWRpc3Bvc2l0aW9uIGlzbid0IGluIGFjY29yZA0KPj4+Pj4+d2l0aA0KPj4+
Pj4+IHdoYXQgdGhhdCBmaWVsZCBpcyBmb3I6IGl0IGlzIGZvciBkZXNjcmliaW5nIGhvdyB0aGUg
aW5mb3JtYXRpb24gaW4NCj4+Pj4+PnRoZQ0KPj4+Pj4+IG1lc3NhZ2UgcGFydCBzaG91bGQgYmUg
cHJlc2VudGVkIC0tIG5vdCB3aGF0IGl0J3MgbWVhbnQgdG8gY29udGFpbg0KPj4+Pj4+b3INCj4+
Pj4+PmJlDQo+Pj4+Pj4gdXNlZCBmb3IuICBUaGlzLCB0b28sIGNvdWxkIGJlIGJldHRlciBoYW5k
bGVkIHdpdGggYSBjb250ZW50LXR5cGUNCj4+Pj4+PiBwYXJhbWV0ZXIuDQo+Pg0KPj5Db250ZW50
LURpc3Bvc2l0aW9uIGhlYWRlciBmaWVsZCBkZXNjcmliZXMgaG93IHRoZSBtZXNzYWdlIGJvZHkg
cGFydCBpcw0KPj50bw0KPj5iZSBpbnRlcnByZXRlZA0KPj4gICBieSB0aGUgVUFDIG9yIFVBUy4g
QXMgU0lQUkVDIG1ldGFkYXRhIGlzIHVzZWQgZGlmZmVyZW50bHkgYnkgcmVjb3JkZXJzDQo+PnRo
YW4gdGhlIGJvZHkgdHlwZXMgbGlrZSBTRFAgdGhlIENvbnRlbnQtRGlzcG9zaXRpb24gobBzZXNz
aW9uobEgZGVmaW5lZCBpbg0KPj5SRkMgMzI2MSBjYW5ub3QgYmUgdXNlZCBoZXJlLg0KPj5JIHRo
aW5rIGl0cyBmaW5lIHRvIGhhdmUgbmV3IEMtRC4gQWxzbyBJIHNlZSBzZXZlcmFsIG9mIG90aGVy
IFNJUCBSRkNzDQo+PihsaWtlIFJGQyA1NjIxLCBSRkMgMzIwNCkgdGhhdCBkZWZpbmVzIG5ldyBi
b2R5IGRlZmluZXMgaXRzIG93biBDLUQuDQo+Pg0KPj5TbyB3ZSBjb3VsZCBzdGljayB3aXRoIGN1
cnJlbnQgQy1EIGluIHRoZSBkcmFmdCAuDQo+Pg0KPj5SZWdhcmRzLA0KPj5SYW0NCj4+DQo+Pj4+
PiANCj4+Pj4+IEkgZGlzYWdyZWUgd2l0aCBCYXJyeSBoZXJlLiBIZSBpcyBhbiBhcHAgZ3V5LCBz
byBJIGd1ZXNzIGl0IG1ha2VzDQo+Pj4+PnNlbnNlDQo+Pj4+PiB0aGF0IGhlIHdvdWxkIHNheSB0
aGlzLiBCdXQgYWxtb3N0IG5vbmUgb2YgdGhlIENvbnRlbnQtRGlzcG9zaXRpb25zDQo+Pj4+PnVz
ZWQNCj4+Pj4+IHdpdGggU0lQIGFyZSBhY3R1YWxseSByZW5kZXJlZCB0byBhIGh1bWFuLiBGb3Ig
aW5zdGFuY2UgInNlc3Npb24iIGZvcg0KPj4+Pj5TRFAuDQo+Pj4+PiANCj4+Pj4+IEkgc2VlIHRo
ZSBkaXN0aW5jdGlvbiBiZXR3ZWVuIEMtVCBhbmQgQy1EIGJlaW5nIGEgZGlzdGluY3Rpb24gYmV0
d2Vlbg0KPj4+Pj4gaG93IGl0IGlzIHJlcHJlc2VudGVkIGFuZCBob3cgaXQgaXMgdXNlZC4gVGhl
cmUgY291bGQgYmUgdHdvDQo+Pj4+PmRpZmZlcmVudA0KPj4+Pj4gQy1UcyBmb3IgU0RQIGFuZCBT
RFBuZywgYnV0IHRoZXkgd291bGQgYm90aCBiZSBDLUQgInNlc3Npb24iLiBUaGUNCj4+Pj4+U0lQ
UkVDDQo+Pj4+PiBtZXRhZGF0YSBpcyB1c2VkIHZlcnkgZGlmZmVyZW50bHksIGFuZCBDLUQgaXMg
dGhlIHdheSB0byBkaXN0aW5ndWlzaA0KPj4+Pj5pdA0KPj4+Pj4gZnJvbSAic2Vzc2lvbiIuDQo+
Pj4+PiANCj4+Pj4+IAlUaGFua3MsDQo+Pj4+PiAJUGF1bA0KPj4+Pj4gDQo+Pj4+PiBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+Pj4gc2lwcmVjIG1h
aWxpbmcgbGlzdA0KPj4+Pj4gc2lwcmVjQGlldGYub3JnDQo+Pj4+PiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcHJlYw0KPj4+PiANCj4+Pj4gX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+Pj4gc2lwcmVjIG1haWxpbmcgbGlz
dA0KPj4+PiBzaXByZWNAaWV0Zi5vcmcNCj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9zaXByZWMNCj4+Pg0KPj4+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4+PnNpcHJlYyBtYWlsaW5nIGxpc3QNCj4+PnNpcHJlY0BpZXRm
Lm9yZw0KPj4+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXByZWMNCj4+
DQo+DQoNCg==


From nobody Wed Jun 17 06:48:20 2015
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 CEC0E1ACCE7 for <siprec@ietfa.amsl.com>; Wed, 17 Jun 2015 06:48:19 -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 cJPhWHR8249v for <siprec@ietfa.amsl.com>; Wed, 17 Jun 2015 06:48:18 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC07F1ACCE3 for <siprec@ietf.org>; Wed, 17 Jun 2015 06:48:17 -0700 (PDT)
Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-09v.sys.comcast.net with comcast id hRmA1q0032XD5SV01RoG2v; Wed, 17 Jun 2015 13:48:16 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-20v.sys.comcast.net with comcast id hRoG1q00L3Ge9ey01RoGs2; Wed, 17 Jun 2015 13:48:16 +0000
Message-ID: <55817A9F.8040901@alum.mit.edu>
Date: Wed, 17 Jun 2015 09:48:15 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: siprec@ietf.org
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu> <D1921296.4E781%eckelcu@cisco.com> <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in> <D1A44B8B.343CD%rmohanr@cisco.com> <D1A5E31A.4FA7C%eckelcu@cisco.com> <D1A73596.34B10%rmohanr@cisco.com>
In-Reply-To: <D1A73596.34B10%rmohanr@cisco.com>
Content-Type: text/plain; charset=euc-kr
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1434548896; bh=00PyJMXjC6t9c1GpkEtZ5JmiPg2y0FQO7nGVG7yx+ck=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Jp0WsmlnTIedOOahDilUniuZ+HycYgdHAdmncg+4DckYjjvWtqmAPqo503oKMl/ef GtnZsIl6E86+VAoFwXBNTo5uL18hxToiiid+tHJ7fW4rFfWnqKxpqqA1ipegNuLeUn /ErXhsU/1f9h83alrjJMrOLbPaJultJkg8jSLy3VrZvthp6HCLtqABWE8Zja/XWbVB R2cgz2MSbyP50JdzkeVnQLQuFrjLkBdsnJZo1QdiM1YvCZYCASzL6V/ZYVLYxhLSmt WgFxRfah0OBh1KW8UMVBS2S2mYCRgO1518YYxjvGQFiZPsKH3c2PtNCqEpcbo+6JzB zBlfyVfKrOR8A==
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/smcB4eKQL6vS-Xr8zm_5abthWW8>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: Wed, 17 Jun 2015 13:48:20 -0000

On 6/17/15 5:01 AM, Ram Mohan R (rmohanr) wrote:

>> Is "application/rs-metadata-request¡± meant to be used for requests from
>> the SRS, and both application/rs-metadata and
>> application/rs-metadata-request need to be defined and registered in this
>> draft?
> 
> I believe so. I think application/rs-metadata-request was added for SRC to
> request a snapshot. For SRC whenever it indicates metadata(either in a
> INVITE/UPDATE/RE-INVITE) or in a response to a request message from SRS,
> it should always have content type as application/rs-metadata.

The intent was that rs-metadata be used from SRC to SRS, and
rs-metadata-request be used from SRS to SRC. The reason for different
C-Ts is that the syntax is different - one has an XML syntax, and the
other is just text with the semantics defined entirely by the C-T.

If we are going to define some fancier syntax for the latter, it might
be cleaner to simply define a new xml entity in our schema for that
purpose. Then we would only need one C-T value. There would then be a
semantic restriction about which entities are sent by SRC and SRS.

	Thanks,
	Paul


From nobody Thu Jun 18 02:21:29 2015
Return-Path: <rmohanr@cisco.com>
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 223501B30BA for <siprec@ietfa.amsl.com>; Thu, 18 Jun 2015 02:21:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 5ycXPC2LB7P0 for <siprec@ietfa.amsl.com>; Thu, 18 Jun 2015 02:21:26 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7D9D1B30B9 for <siprec@ietf.org>; Thu, 18 Jun 2015 02:21:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2030; q=dns/txt; s=iport; t=1434619286; x=1435828886; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=aOgaJMqAuw9TyqjyXpdhMYUzDhb4fKPeQVGdnAUs2wQ=; b=KUSP1o/6/Xv88oGHP9yxVAgpDqBXbFUuHAmDFyDJDTvZE3/wYHjld8yI XXU6Xp8BBeCS7IXGglrzqKCB7/HrY3psva5U8YpKWPHG76kOeDdndz1wB Pq2wpWmt22B0GigW3+zb75okYVv/yfUm02LG55EWbWyw4ktNmhgs3/Fu4 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A/BADpjIJV/4ENJK1cDoMCVF8GvW4JgVsKhS5KAoE3OBQBAQEBAQEBgQqEIgEBAQMBAQEBaxAHBAIBCA4DAwECAS4nCx0IAgQBEognCA3FIgEBAQEBAQEBAQEBAQEBAQEBFwSLRYRTOgaEJQWMPIc0AYtIgTWOcIgAJmOBWX8+b4FGgQIBAQE
X-IronPort-AV: E=Sophos;i="5.13,638,1427760000"; d="scan'208";a="160514967"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-8.cisco.com with ESMTP; 18 Jun 2015 09:21:25 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t5I9LPBu021483 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Jun 2015 09:21:25 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.106]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Thu, 18 Jun 2015 04:21:25 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQqagllIO38B/6Vk+k/xA0IJedtg==
Date: Thu, 18 Jun 2015 09:21:25 +0000
Message-ID: <D1A88AA1.34CC8%rmohanr@cisco.com>
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu> <D1921296.4E781%eckelcu@cisco.com> <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in> <D1A44B8B.343CD%rmohanr@cisco.com> <D1A5E31A.4FA7C%eckelcu@cisco.com> <D1A73596.34B10%rmohanr@cisco.com> <55817A9F.8040901@alum.mit.edu>
In-Reply-To: <55817A9F.8040901@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [173.39.64.231]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5C70D2830EDA144D9DC3B8F4CF5849F6@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/qD5wHD1MoycQw2iom9y4flX9DWs>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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, 18 Jun 2015 09:21:28 -0000

-----Original Message-----
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Date: Wednesday, 17 June 2015 7:18 pm
To: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Barry Leiba's Discuss on
draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)

>On 6/17/15 5:01 AM, Ram Mohan R (rmohanr) wrote:
>
>>> Is "application/rs-metadata-request=B2 meant to be used for requests fr=
om
>>> the SRS, and both application/rs-metadata and
>>> application/rs-metadata-request need to be defined and registered in
>>>this
>>> draft?
>>=20
>> I believe so. I think application/rs-metadata-request was added for SRC
>>to
>> request a snapshot. For SRC whenever it indicates metadata(either in a
>> INVITE/UPDATE/RE-INVITE) or in a response to a request message from SRS,
>> it should always have content type as application/rs-metadata.
>
>The intent was that rs-metadata be used from SRC to SRS, and
>rs-metadata-request be used from SRS to SRC. The reason for different
>C-Ts is that the syntax is different - one has an XML syntax, and the
>other is just text with the semantics defined entirely by the C-T.

That=B9s right.=20

 "application/rs-metadata-request=B2 from SRS to SRC and
"application/rs-metadata" whenever SRC sends metadata to SRS (either in
request messages or in response to a request from SRS)
looks good to me.


>
>If we are going to define some fancier syntax for the latter,

I don=B9t see a need as the latter does not have any XML syntax as of today=
.
SRS is free to put in any text it likes or leave it empty as well and just
request for metadata from SRC.

Regards,
Ram

> it might
>be cleaner to simply define a new xml entity in our schema for that
>purpose. Then we would only need one C-T value. There would then be a
>semantic restriction about which entities are sent by SRC and SRS.
>
>	Thanks,
>	Paul
>
>_______________________________________________
>siprec mailing list
>siprec@ietf.org
>https://www.ietf.org/mailman/listinfo/siprec


From nobody Thu Jun 18 10:08:39 2015
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 CC62B1B2A1C for <siprec@ietfa.amsl.com>; Thu, 18 Jun 2015 10:08:38 -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 J3ccQ6bDteWk for <siprec@ietfa.amsl.com>; Thu, 18 Jun 2015 10:08:37 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CB991B2A10 for <siprec@ietf.org>; Thu, 18 Jun 2015 10:08:37 -0700 (PDT)
Received: from resomta-ch2-07v.sys.comcast.net ([69.252.207.103]) by resqmta-ch2-10v.sys.comcast.net with comcast id ht7o1q0032EPM3101t8cyr; Thu, 18 Jun 2015 17:08:36 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-07v.sys.comcast.net with comcast id ht8c1q0093Ge9ey01t8cVR; Thu, 18 Jun 2015 17:08:36 +0000
Message-ID: <5582FB13.5060204@alum.mit.edu>
Date: Thu, 18 Jun 2015 13:08:35 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>,  "siprec@ietf.org" <siprec@ietf.org>
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu> <D1921296.4E781%eckelcu@cisco.com> <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in> <D1A44B8B.343CD%rmohanr@cisco.com> <D1A5E31A.4FA7C%eckelcu@cisco.com> <D1A73596.34B10%rmohanr@cisco.com> <55817A9F.8040901@alum.mit.edu> <D1A88AA1.34CC8%rmohanr@cisco.com>
In-Reply-To: <D1A88AA1.34CC8%rmohanr@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1434647316; bh=as+cokVT+xS61PJ1FKkS/eechJ3lym3Tm6qXBgbd+C8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=oXolz1xaddAum6u7nv3denrAkfjg8TkUy+Tj3mVHnCasJkhDWAb81wLooO5vE3Mfp z86EgiDc0b45/cnFs9Ivc7h2jGmSbOcrsFU2UM4TGlUCEwXHNpogVcqgHp8KxmNPFG c4xs+zs8TbAshoqO6yNhULW5OtrmykcwZJlXbmChAGeksu+UsSXByrZnSrHRvrT3nl I9nAS3S1l6BSfP6lG0ik6Lbq6H+zhDgetTgade3pwOSegtZC/QhlvRhTpkC2ZsKWsY 3FaPm0m8jfh22QWOwOI35nZ3tllVpIpoZX8X0i3nBD4/INvQryXVOb+HyCUU6+rcOu ugXiXeskiLsdQ==
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/Qfp3Olp75wmShmajBoPLmhHA-f0>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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, 18 Jun 2015 17:08:39 -0000

On 6/18/15 5:21 AM, Ram Mohan R (rmohanr) wrote:
>
>
> -----Original Message-----
> From: Paul Kyzivat <pkyzivat@alum.mit.edu>
> Date: Wednesday, 17 June 2015 7:18 pm
> To: "siprec@ietf.org" <siprec@ietf.org>
> Subject: Re: [siprec] Barry Leiba's Discuss on
> draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
>
>> On 6/17/15 5:01 AM, Ram Mohan R (rmohanr) wrote:
>>
>>>> Is "application/rs-metadata-request² meant to be used for requests from
>>>> the SRS, and both application/rs-metadata and
>>>> application/rs-metadata-request need to be defined and registered in
>>>> this
>>>> draft?
>>>
>>> I believe so. I think application/rs-metadata-request was added for SRC
>>> to
>>> request a snapshot. For SRC whenever it indicates metadata(either in a
>>> INVITE/UPDATE/RE-INVITE) or in a response to a request message from SRS,
>>> it should always have content type as application/rs-metadata.
>>
>> The intent was that rs-metadata be used from SRC to SRS, and
>> rs-metadata-request be used from SRS to SRC. The reason for different
>> C-Ts is that the syntax is different - one has an XML syntax, and the
>> other is just text with the semantics defined entirely by the C-T.
>
> That¹s right.
>
>   "application/rs-metadata-request² from SRS to SRC and
> "application/rs-metadata" whenever SRC sends metadata to SRS (either in
> request messages or in response to a request from SRS)
> looks good to me.
>
>
>>
>> If we are going to define some fancier syntax for the latter,
>
> I don¹t see a need as the latter does not have any XML syntax as of today.
> SRS is free to put in any text it likes or leave it empty as well and just
> request for metadata from SRC.

Well, the issue was raised that we haven't provided any extensibility 
for what the SRS can say to the SRC. So we need to address that. Doing 
so probably means introducing *some* syntax into the content sent.

So, what I am suggesting is:
- make the message be XML
- use the same schema used for SRC to SRS messages
- use the same C-T and C-D for both directions
- add a new entity definition to that schema for the purpose
- specify that for SRS to SRC, only the one new entity is valid
- specify the behavior when something else is received by the SRC,
   in a way that allows for future extensibility.

	Thanks,
	Paul

> Regards,
> Ram
>
>> it might
>> be cleaner to simply define a new xml entity in our schema for that
>> purpose. Then we would only need one C-T value. There would then be a
>> semantic restriction about which entities are sent by SRC and SRS.
>>
>> 	Thanks,
>> 	Paul
>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>
>


From nobody Thu Jun 18 16:49:48 2015
Return-Path: <eckelcu@cisco.com>
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 D9AB31B2D95; Thu, 18 Jun 2015 16:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level: 
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 6Ih3yge9mlQV; Thu, 18 Jun 2015 16:49:44 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D24D51B2D97; Thu, 18 Jun 2015 16:49:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9937; q=dns/txt; s=iport; t=1434671384; x=1435880984; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=N+0yKlyannG+xUlQ4fTBnGJJgq1/qqlGxpP4os35tSI=; b=lPGlcCP8YFuc+LrlsEYdNb0X7/Fr5TB8tTV/j2BksyuZTmkXEBU3V2Li qzFmNaGe/jmCYiKTOUep0d4zse9YRaIApdmY11jqqSJwZSKjETrVVMge6 OjYFrcJVnckyaI4iZ4PJNlbU/GeDF+bJE+gpry4j4/TbPzYqW1zlNYka2 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AbBQDUV4NV/4wNJK1TCYMQVF8GuUeENIFlhXgCgTg6EgEBAQEBAQGBCoQjAQEEcAIHEAIBCBI0MhcOAgQBDQWILw3GRgEBAQEBAQEBAQEBAQEBAQEBAQEBGIpDgQKEIwcKAQYYMwIFhCsFhn2FP4RbglkBhFKGeIE1QYNKgwuHW4Qlg1smY4EoHBWBPW8BAYEKOoECAQEB
X-IronPort-AV: E=Sophos;i="5.13,641,1427760000";  d="scan'208";a="8495849"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-3.cisco.com with ESMTP; 18 Jun 2015 23:49:42 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t5INngPi006346 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Jun 2015 23:49:42 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.83]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0195.001; Thu, 18 Jun 2015 18:49:42 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Ben Campbell <ben@nostrum.com>, The IESG <iesg@ietf.org>
Thread-Topic: Ben Campbell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQmAlIvedyK9Qkc0aW9RIqsCAGEJ2y8UgA
Date: Thu, 18 Jun 2015 23:49:41 +0000
Message-ID: <D1A88627.5019B%eckelcu@cisco.com>
References: <20150526231115.15164.11308.idtracker@ietfa.amsl.com>
In-Reply-To: <20150526231115.15164.11308.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.2.150604
x-originating-ip: [10.154.176.41]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <D69EC950977C594CA6321C9431E946FA@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/x5cZqz4Uss3qwSrulvqA_yJPeCY>
Cc: "siprec@ietf.org" <siprec@ietf.org>, "draft-ietf-siprec-protocol.ad@ietf.org" <draft-ietf-siprec-protocol.ad@ietf.org>, "siprec-chairs@ietf.org" <siprec-chairs@ietf.org>, "draft-ietf-siprec-protocol@ietf.org" <draft-ietf-siprec-protocol@ietf.org>, "draft-ietf-siprec-protocol.shepherd@ietf.org" <draft-ietf-siprec-protocol.shepherd@ietf.org>
Subject: Re: [siprec] Ben Campbell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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, 18 Jun 2015 23:49:47 -0000

Hi Ben,

Thanks for all these valuable comments. Some of your points have been
discussed in other threads, but I do not see any direct response. Sorry
for the long delay. Let me try to summarize by commenting inline.


On 5/26/15, 4:11 PM, "Ben Campbell" <ben@nostrum.com> wrote:

>Ben Campbell has entered the following ballot position for
>draft-ietf-siprec-protocol-16: Discuss
>
>When responding, please keep the subject line intact and reply to all
>email addresses included in the To and CC lines. (Feel free to cut this
>introductory paragraph, however.)
>
>
>Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>for more information about IESG DISCUSS and COMMENT positions.
>
>
>The document, along with other ballot positions, can be found here:
>https://datatracker.ietf.org/doc/draft-ietf-siprec-protocol/
>
>
>
>----------------------------------------------------------------------
>DISCUSS:
>----------------------------------------------------------------------
>
>I am concerned that this draft allows the recording session to downgrade
>security from the communication session. It says "SHOULD NOT", but then
>explicitly allows for the downgrade when the SRC and SRS are in the same
>administrative domain. This seems to create a whole new "last hop
>exception" for media, similar to the one for SIPS that we took so many
>years to deprecate. (Except it's worse because the potentially insecure
>hop goes to an endpoint not necessarily expected to be a party to the
>media.)

Andy explained as follows:

"I think the issue here is that the SRC and SRS will often be co-located
in an environment where mutual authentication was just not necessary and
therefore the WG did not want to mandate this in all cases.=B2

>
>Section 6.1.2 includes a "contract in place" as a form of recording
>indication. The other mechanisms seem to say that a given call is being
>recorded. A contract cannot do that, except in the degenerate case of
>"all calls are recorded." This doesn't seem to fit the spirit of the
>"MUST provide recording indication" language.

I expanded section 6.3 in an attempt to address similar concerns:

A recording-aware UA MUST provide a recording indication to the end user
 through an appropriate user interface, indicating whether recording is
on, off, or paused for each medium. Appropriate user interfaces may
include real-time notification or previously established agreements that
 use of the device is subject to recording.  Some user agents that are
automatons (e.g., IVR, media server, PSTN gateway) may not have a user
interface to render recording indication.  When such a user agent
indicates recording awareness, the UA SHOULD render recording indication
 through other means, such as passing an in-band tone on the PSTN
gateway, putting the recording indication in a log file, or raising an
application event in a VoiceXML dialog.  These user agents MAY also
choose not to indicate recording awareness, thereby relying on whatever
mechanism an SRC chooses to indicate recording, such as playing a tone
in-band.



>
>Section 12, 2nd paragraph says the SRC and SRS "MUST support SIP with TLS
>and MAY support SIPS with
>   TLS as per [RFC5630]". That actually downgrades the requirement for
>SIPS support from that in 3261/5630. (3261 says you MUST support SIPS if
>you support TLS.)

As noted in RFC 5630, SIPS was underspecified in RFC 3261 and this was a
source of confusion. RFC 5360 aimed to fix this, and states:

Because a SIPS URI implies that requests sent to the resource
   identified by it be sent over each SIP hop over TLS, SIPS URIs are
   not suitable for "best-effort TLS": they are only suitable for "TLS-
   only" requests.  This is recognized in Section 26.2.2 of [RFC3261]
<http://tools.ietf.org/html/rfc3261#section-26.2.2>.
Users that distribute a SIPS URI as an address-of-record may elect
      to operate devices that refuse requests over insecure transports.
   If one wants to use "best-effort TLS" for SIP, one just needs to use
   a SIP URI, and send the request over TLS.


>
>
>----------------------------------------------------------------------
>COMMENT:
>----------------------------------------------------------------------
>
>The reference to 7245 is informational. Do you expect that a
>reader/implementor could understand/implement this draft without
>understanding the architecture and terminology from that RFC? The same
>applies for 3550--I'm skeptical that one could implement this draft
>without understanding RTP.

I will change these references to normative.

>
>-- Figure 1: The text says the flow is basically the same whether the SRC
>is in an endpoint or separate. This may be logically true, but the flow
>really would change--none of of the flow between UA(A) and SRC would
>exist.

I broke into two call flows, one illustrating each case.

>
>-- 5.2: UPDATE needs a citation to 3311. Also, 3311 "RECOMMENDS"
>reINVITEs over UPDATEs for confirmed dialogs. It would be helpful to add
>some motivation as to why this draft seems to prefer UPDATE.

Added a citation. UPDATE is preferred, actually required, for the SRS to
request to snapshot, but re-INVITE or UPDATE can be used by the SRC to
send metadata. I don=B9t believe any preference was meant to be implied.
UPDATE was chosen for the SRS to request metadata because it could be sent
regardless of the state of the dialog. This was seen as better than
requiring support for both UPDATE and re-INVITE for this operation.

>
>-- 5.3: It seems odd to me that the SRC can ignore an explicit preference
>not to record. Wouldn't it be better just to refuse to complete/accept
>the call, if some policy overrides the end-user's preference?

We decided to leave this choice to the user, who can drop the call if the
recording state of the call is not acceptable to the user.

>
>-- Figure 3: If the UA prefers not to be recorded, shouldn't it express
>that at setup time, rather than wait for the SRC to indicate recording is
>happening? As shown, this almost guarantees a bit of media will be
>recorded. (Seems like there should be some guidance about this in the
>text.) The last paragraph of 6.1.2 seems to reinforce the problem by
>suggesting the participant might base the decision to express a
>preference on a tag that is optional for the SRC to send in the first
>place.

Yes, but in this case the example read, "After the call is established and
recording is in progress, UA (B) later decides to change the recording
preference to no recording=B2. This real time interaction seemed useful as =
a
example. More examples can be added if necessary.
Note that the use of the a=3Drecord attribute is REQUIRED when recording. I=
t
is not optional.

>
>-- 6.3, last paragraph: It seems odd that the requirement to render a
>recording indicator be lower for a media server than for other UAs. This
>seems to circumvent user notification in one of the most common uses of
>recording these days.

This section was reworded, as quoted in my previous comment.

>
>-- 9.1 : The last bullet seems to be a motivation to not send metadata at
>all, which is expressly forbidden in the first paragraph.

This was meant to illustrate that the SRC may not record everything to
which it has access, with privacy concerns being one example. I suppose
such filtering could be performed later on the recorded content, but that
assumes a specific relationship the administrative domain of the SRC and
that of the SRS.

>
>-- 9.2: The use of  the content-type value as the sole indicator that the
>an UPDATE request should be interpreted as an request for a metadata
>snapshot update is rather odd.  If you end up with new kinds of metadata
>requests in the future, does each one get it's own media-type?

This is being sorted out in another thread. I agree, something needs to
change here.

>
>-- 12: If this doc is to depend on the security considerations in 6341,
>that needs to be a normative reference--which is a bit of a pain because
>I think it's an informational RFC.

We tried to avoid this with the language "The use cases and requirements
document [RFC6341] outlines the general security considerations, and this
document describes specific security recommendations.=B2

>
>-- 12.1:=20
>"recording session uses TLS" -- I assume that's for SIP? Also It's worth
>discussing how mutual authentication applies if the SRC is in an end-user
>device. Is it expected to have a client cert? No option to use  SIP
>identity?
>
>Also, I'm a bit uncomfortable assuming devices in the same administrative
>domain automatically trust each other. It might be better to say "If they
>trust each other..."

Using the word =B3trust" is a slippery slope as well. For a UA acting as a
SRC, the implied requirement is that it has a cert.
=20
>
>-- 12.2:
>
>I get quite a bit of heartburn out of making Security Descriptions MTI
>and dtls-srtp optional. I guess I may have to hold my nose on this one.

It is what it is.

>
>Editorial:
>
>-- 4: 2nd paragraph: " ... does not represent the protocol"
> and first bullet: "Delivering recorded media in real-time as the CS
>media"
>
>I don't understand what either of those mean.

Neither do I :(
Perhaps it means the SRS is not defined to act as a playback device to be
brought into a CS by the SRC?

>
>-- 5.1, 2nd paragraph: "B2BUA to bridge
>the media between UA(A) and UA(B)"
>
>Is there a reason not to use the terminology from RFC 7092? (e.g. =B3relay=
=B2
>or =B3terminate=B2 media)?

Relay sound good. I=B9ll switch to that.

>
>-- 7.3.1: The normative language in the first paragraph is redundant to
>similar language in 6.3.

Will remove the redundant normative language in 7.3.1.

Cheers,
Charles


From nobody Thu Jun 18 21:46:28 2015
Return-Path: <rmohanr@cisco.com>
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 039881A1A30 for <siprec@ietfa.amsl.com>; Thu, 18 Jun 2015 21:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 BPL42EmLrfgS for <siprec@ietfa.amsl.com>; Thu, 18 Jun 2015 21:46:25 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CC2A1A1A36 for <siprec@ietf.org>; Thu, 18 Jun 2015 21:46:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6294; q=dns/txt; s=iport; t=1434689185; x=1435898785; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=L21UmhoTphEcTGKfw6w9jWC2fXt+rYk73CMHuPSR3mU=; b=OLa2fnYSLNkLFx/1PRo1jzWWHZ/KKLlXT9pB8oIcaH3JfDeCDYTSstXC mzUDGSr/Hb8J9z8+66cKe8nOBl91+3UaWqXIhRzJobRujjcFKzisLOvUt qjaESC6lH/6Wgh37MxniBmHzdyDbW+WOoQQA04fmLmFzu77jBKM6TNFMn M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ByBQAnnoNV/4oNJK1cDoMCVF8Ggxi6ZYFcCoUuSgIcgSQ6EgEBAQEBAQGBCoQiAQEBBAEBATE6FwQCAQgOAwMBAgEEKAICJQsdCAIEARKILw2QLJ0RBpZcAQEBAQEBAQEBAQEBAQEBAQEBFgSBG4oqhFM6BoJcgUkFk3QBi0uBNY5ziAAmY4FZfz5vgUaBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.13,643,1427760000"; d="scan'208";a="160946878"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Jun 2015 04:46:24 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t5J4kO7b009682 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 19 Jun 2015 04:46:24 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.106]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Thu, 18 Jun 2015 23:46:23 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQqkrkbkLFNQjY5kCETRqJyDLuSw==
Date: Fri, 19 Jun 2015 04:46:23 +0000
Message-ID: <D1A9977E.34E64%rmohanr@cisco.com>
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu> <D1921296.4E781%eckelcu@cisco.com> <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in> <D1A44B8B.343CD%rmohanr@cisco.com> <D1A5E31A.4FA7C%eckelcu@cisco.com> <D1A73596.34B10%rmohanr@cisco.com> <55817A9F.8040901@alum.mit.edu> <D1A88AA1.34CC8%rmohanr@cisco.com> <5582FB13.5060204@alum.mit.edu>
In-Reply-To: <5582FB13.5060204@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [173.39.64.231]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <BFE1F42F1547DC458B5D8F26CB3B447E@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/ajquZR2jQTpHPNc5RWMigfV-4QQ>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: Fri, 19 Jun 2015 04:46:27 -0000

SGkgUGF1bCwNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogUGF1bCBLeXpp
dmF0IDxwa3l6aXZhdEBhbHVtLm1pdC5lZHU+DQpEYXRlOiBUaHVyc2RheSwgMTggSnVuZSAyMDE1
IDEwOjM4IHBtDQpUbzogQ2lzY28gRW1wbG95ZWUgPHJtb2hhbnJAY2lzY28uY29tPiwgInNpcHJl
Y0BpZXRmLm9yZyIgPHNpcHJlY0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBbc2lwcmVjXSBCYXJy
eSBMZWliYSdzIERpc2N1c3Mgb24NCmRyYWZ0LWlldGYtc2lwcmVjLXByb3RvY29sLTE2OiAod2l0
aCBESVNDVVNTIGFuZCBDT01NRU5UKQ0KDQo+T24gNi8xOC8xNSA1OjIxIEFNLCBSYW0gTW9oYW4g
UiAocm1vaGFucikgd3JvdGU6DQo+Pg0KPj4NCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQo+PiBGcm9tOiBQYXVsIEt5eml2YXQgPHBreXppdmF0QGFsdW0ubWl0LmVkdT4NCj4+IERhdGU6
IFdlZG5lc2RheSwgMTcgSnVuZSAyMDE1IDc6MTggcG0NCj4+IFRvOiAic2lwcmVjQGlldGYub3Jn
IiA8c2lwcmVjQGlldGYub3JnPg0KPj4gU3ViamVjdDogUmU6IFtzaXByZWNdIEJhcnJ5IExlaWJh
J3MgRGlzY3VzcyBvbg0KPj4gZHJhZnQtaWV0Zi1zaXByZWMtcHJvdG9jb2wtMTY6ICh3aXRoIERJ
U0NVU1MgYW5kIENPTU1FTlQpDQo+Pg0KPj4+IE9uIDYvMTcvMTUgNTowMSBBTSwgUmFtIE1vaGFu
IFIgKHJtb2hhbnIpIHdyb3RlOg0KPj4+DQo+Pj4+PiBJcyAiYXBwbGljYXRpb24vcnMtbWV0YWRh
dGEtcmVxdWVzdKn3IG1lYW50IHRvIGJlIHVzZWQgZm9yIHJlcXVlc3RzDQo+Pj4+PmZyb20NCj4+
Pj4+IHRoZSBTUlMsIGFuZCBib3RoIGFwcGxpY2F0aW9uL3JzLW1ldGFkYXRhIGFuZA0KPj4+Pj4g
YXBwbGljYXRpb24vcnMtbWV0YWRhdGEtcmVxdWVzdCBuZWVkIHRvIGJlIGRlZmluZWQgYW5kIHJl
Z2lzdGVyZWQgaW4NCj4+Pj4+IHRoaXMNCj4+Pj4+IGRyYWZ0Pw0KPj4+Pg0KPj4+PiBJIGJlbGll
dmUgc28uIEkgdGhpbmsgYXBwbGljYXRpb24vcnMtbWV0YWRhdGEtcmVxdWVzdCB3YXMgYWRkZWQg
Zm9yDQo+Pj4+U1JDDQo+Pj4+IHRvDQo+Pj4+IHJlcXVlc3QgYSBzbmFwc2hvdC4gRm9yIFNSQyB3
aGVuZXZlciBpdCBpbmRpY2F0ZXMgbWV0YWRhdGEoZWl0aGVyIGluIGENCj4+Pj4gSU5WSVRFL1VQ
REFURS9SRS1JTlZJVEUpIG9yIGluIGEgcmVzcG9uc2UgdG8gYSByZXF1ZXN0IG1lc3NhZ2UgZnJv
bQ0KPj4+PlNSUywNCj4+Pj4gaXQgc2hvdWxkIGFsd2F5cyBoYXZlIGNvbnRlbnQgdHlwZSBhcyBh
cHBsaWNhdGlvbi9ycy1tZXRhZGF0YS4NCj4+Pg0KPj4+IFRoZSBpbnRlbnQgd2FzIHRoYXQgcnMt
bWV0YWRhdGEgYmUgdXNlZCBmcm9tIFNSQyB0byBTUlMsIGFuZA0KPj4+IHJzLW1ldGFkYXRhLXJl
cXVlc3QgYmUgdXNlZCBmcm9tIFNSUyB0byBTUkMuIFRoZSByZWFzb24gZm9yIGRpZmZlcmVudA0K
Pj4+IEMtVHMgaXMgdGhhdCB0aGUgc3ludGF4IGlzIGRpZmZlcmVudCAtIG9uZSBoYXMgYW4gWE1M
IHN5bnRheCwgYW5kIHRoZQ0KPj4+IG90aGVyIGlzIGp1c3QgdGV4dCB3aXRoIHRoZSBzZW1hbnRp
Y3MgZGVmaW5lZCBlbnRpcmVseSBieSB0aGUgQy1ULg0KPj4NCj4+IFRoYXSp9nMgcmlnaHQuDQo+
Pg0KPj4gICAiYXBwbGljYXRpb24vcnMtbWV0YWRhdGEtcmVxdWVzdKn3IGZyb20gU1JTIHRvIFNS
QyBhbmQNCj4+ICJhcHBsaWNhdGlvbi9ycy1tZXRhZGF0YSIgd2hlbmV2ZXIgU1JDIHNlbmRzIG1l
dGFkYXRhIHRvIFNSUyAoZWl0aGVyIGluDQo+PiByZXF1ZXN0IG1lc3NhZ2VzIG9yIGluIHJlc3Bv
bnNlIHRvIGEgcmVxdWVzdCBmcm9tIFNSUykNCj4+IGxvb2tzIGdvb2QgdG8gbWUuDQo+Pg0KPj4N
Cj4+Pg0KPj4+IElmIHdlIGFyZSBnb2luZyB0byBkZWZpbmUgc29tZSBmYW5jaWVyIHN5bnRheCBm
b3IgdGhlIGxhdHRlciwNCj4+DQo+PiBJIGRvbqn2dCBzZWUgYSBuZWVkIGFzIHRoZSBsYXR0ZXIg
ZG9lcyBub3QgaGF2ZSBhbnkgWE1MIHN5bnRheCBhcyBvZg0KPj50b2RheS4NCj4+IFNSUyBpcyBm
cmVlIHRvIHB1dCBpbiBhbnkgdGV4dCBpdCBsaWtlcyBvciBsZWF2ZSBpdCBlbXB0eSBhcyB3ZWxs
IGFuZA0KPj5qdXN0DQo+PiByZXF1ZXN0IGZvciBtZXRhZGF0YSBmcm9tIFNSQy4NCj4NCj5XZWxs
LCB0aGUgaXNzdWUgd2FzIHJhaXNlZCB0aGF0IHdlIGhhdmVuJ3QgcHJvdmlkZWQgYW55IGV4dGVu
c2liaWxpdHkNCj5mb3Igd2hhdCB0aGUgU1JTIGNhbiBzYXkgdG8gdGhlIFNSQy4gU28gd2UgbmVl
ZCB0byBhZGRyZXNzIHRoYXQuIERvaW5nDQo+c28gcHJvYmFibHkgbWVhbnMgaW50cm9kdWNpbmcg
KnNvbWUqIHN5bnRheCBpbnRvIHRoZSBjb250ZW50IHNlbnQuDQoNCkkgZG9uoa90IHNlZSBhbnkg
aXNzdWUgaW4gaGF2aW5nIGEgc3ludGF4IChYTUwgaW4gd2hpY2ggY2FzZSB3ZSBjYW4gcmUtdXNl
DQp0aGUgbWV0YWRhdGEgWE1MIG5hbWVzcGFjZSBhbmQganVzdCBhZGQgb25lIG1vcmUgWE1MIGVs
ZW1lbnQpIHRvIHJlcXVlc3QNCmZvciBzbmFwc2hvdC4gSG93ZXZlciBkb26hr3Qgc2VlIGl0IGJy
aW5nIG11Y2ggdmFsdWUgZm9yIHRoZSBjdXJyZW50DQp2ZXJzaW9uIG9mIFNJUFJFQyBwcm90b2Nv
bC4gSW4gdGhlIGN1cnJlbnQgdmVyc2lvbiwgYWxsIHdlIG5lZWQgaXMgZm9yIFNSUw0KdG8gdGVs
bCBTUkMgdGhhdCBpdCBuZWVkcyBhIHNuYXBzaG90IG9mIG1ldGFkYXRhLiBGb3IgdGhhdCwgaXQg
Y2FuIGp1c3QNCnNlbmQgobBhcHBsaWNhdGlvbi9ycy1tZXRhZGF0YS1yZXF1ZXN0obEgd2l0aA0K
Y29udGVudC1sZW5ndGggMCBmb3Igbm93IGFuZCBzYXkgaW4gZnV0dXJlIGhhdmUgYSBib2R5IFsg
d2hpY2ggY2FuIG1hcCB0bw0Kc2FtZSBYTUwgc2NoZW1hXS4NCg0KV2hlbiB3ZSBuZWVkIHRvIGV4
dGVuZChzYXkgaGF2ZSBtb3JlIHNwZWNpZmljIGRldGFpbHMgbGlrZSByZXF1ZXN0aW5nDQpzbmFw
c2hvdCBmb3IgYSBwYXJ0aWN1bGFyIHBvcnRpb24pIHRoZW4gd2Ugd291bGQgaGF2ZSB0byBkZWZp
bmUgYSBmb3JtYWwNClhNTCBzeW50YXggd2hpY2ggaXMgd2hhdCBpcyB0aGUgY29uY2VybiBmb3Jt
IEJhcnJ5IGhlcmUgYXMgSSB1bmRlcnN0YW5kLg0KDQpJIGhhdmUgYSBxdWVzdGlvbiAtIGlzIGl0
IGFsbG93ZWQgdG8gaGF2ZSBhIHR3byBkaWZmZXJlbnQgQy1UIChzYXkNCqGwYXBwbGljYXRpb24v
cnMtbWV0YWRhdGEtcmVxdWVzdKGxIGFuZCChsGFwcGxpY2F0aW9uL3JzLW1ldGFkYXRhIikgYW5k
IHN0aWxsDQpoYXZlIGNvbnRlbnQgcG9pbnQgdG8gc2FtZSBYTUwgZG9jdW1lbnQgPw0KVGhlIHJl
YXNvbiBmb3IgYXNraW5nIGlzIEkgc3RpbGwgZmVlbCB0aGV5IGhhdmUgdG8gYmUgZGlmZmVyZW50
IEMtVCBhcw0KdGhleSBhcmUgbm90IHJlbGF0ZWQuIE9uZSBDLVQgaXMgZm9yIHJlcHJlc2VudGlu
ZyB0aGUgc25hcHNob3Qgb2YgbWV0YWRhdGENCmFuZCBvdGhlciBpcyBmb3IgcmVxdWVzdGluZyB0
aGUgc2FtZS4gU28gbG9naWNhbGx5IGl0IG1ha2Ugc2Vuc2UgdG8gc3RpbGwNCmNvbnNpZGVyIHRo
ZW0gYXMgdHdvIGRpZmZlcmVudCBjb250ZW50LXR5cGVzLiBUaGUgQy1EIGNhbiBiZSBzYW1lIGFz
IGJvdGgNCmFyZSBmb3IgcmVjb3JkaW5nIHNlc3Npb24uDQoNCkluIGFueSBjYXNlIEkgd291bGQg
bGlrZSB0byBoZWFyIGZlZWRiYWNrIGZyb20gc29tZSBtb3JlIGZvbGtzIGluIFdHIG9uDQp0aGlz
IGNoYW5nZSBiZWZvcmUgd2UgZ28gaW4gdG8gZGV0YWlscyBvZiBob3cgdG8gcmVwcmVzZW50IHRo
ZSByZXF1ZXN0Lg0KDQpSZWdhcmRzLA0KUmFtDQoNCj4tIG1ha2UgdGhlIG1lc3NhZ2UgYmUgWE1M
DQo+LSB1c2UgdGhlIHNhbWUgc2NoZW1hIHVzZWQgZm9yIFNSQyB0byBTUlMgbWVzc2FnZXMNCj4t
IHVzZSB0aGUgc2FtZSBDLVQgYW5kIEMtRCBmb3IgYm90aCBkaXJlY3Rpb25zDQo+LSBhZGQgYSBu
ZXcgZW50aXR5IGRlZmluaXRpb24gdG8gdGhhdCBzY2hlbWEgZm9yIHRoZSBwdXJwb3NlDQo+LSBz
cGVjaWZ5IHRoYXQgZm9yIFNSUyB0byBTUkMsIG9ubHkgdGhlIG9uZSBuZXcgZW50aXR5IGlzIHZh
bGlkDQo+LSBzcGVjaWZ5IHRoZSBiZWhhdmlvciB3aGVuIHNvbWV0aGluZyBlbHNlIGlzIHJlY2Vp
dmVkIGJ5IHRoZSBTUkMsDQo+ICAgaW4gYSB3YXkgdGhhdCBhbGxvd3MgZm9yIGZ1dHVyZSBleHRl
bnNpYmlsaXR5Lg0KPg0KPglUaGFua3MsDQo+CVBhdWwNCj4NCj4+IFJlZ2FyZHMsDQo+PiBSYW0N
Cj4+DQo+Pj4gaXQgbWlnaHQNCj4+PiBiZSBjbGVhbmVyIHRvIHNpbXBseSBkZWZpbmUgYSBuZXcg
eG1sIGVudGl0eSBpbiBvdXIgc2NoZW1hIGZvciB0aGF0DQo+Pj4gcHVycG9zZS4gVGhlbiB3ZSB3
b3VsZCBvbmx5IG5lZWQgb25lIEMtVCB2YWx1ZS4gVGhlcmUgd291bGQgdGhlbiBiZSBhDQo+Pj4g
c2VtYW50aWMgcmVzdHJpY3Rpb24gYWJvdXQgd2hpY2ggZW50aXRpZXMgYXJlIHNlbnQgYnkgU1JD
IGFuZCBTUlMuDQo+Pj4NCj4+PiAJVGhhbmtzLA0KPj4+IAlQYXVsDQo+Pj4NCj4+PiBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+IHNpcHJlYyBtYWls
aW5nIGxpc3QNCj4+PiBzaXByZWNAaWV0Zi5vcmcNCj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3NpcHJlYw0KPj4NCj4+DQo+DQoNCg==


From nobody Mon Jun 22 08:13:19 2015
Return-Path: <andrew.hutton@unify.com>
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 D20041ACE64 for <siprec@ietfa.amsl.com>; Mon, 22 Jun 2015 08:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.09
X-Spam-Level: 
X-Spam-Status: No, score=0.09 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 CQGhoHVixsfW for <siprec@ietfa.amsl.com>; Mon, 22 Jun 2015 08:13:17 -0700 (PDT)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id E62E41ACE51 for <siprec@ietf.org>; Mon, 22 Jun 2015 08:13:16 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx11.unify.com (Server) with ESMTP id D272F1EB8487; Mon, 22 Jun 2015 17:13:15 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.9]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0224.002; Mon, 22 Jun 2015 17:13:15 +0200
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQmLk7GVjaOmlorUqQBpj3aMW38p24x1dQ
Date: Mon, 22 Jun 2015 15:13:14 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF1E7CD3A9@MCHP04MSX.global-ad.net>
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu> <D1921296.4E781%eckelcu@cisco.com> <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in> <D1A44B8B.343CD%rmohanr@cisco.com> <D1A5E31A.4FA7C%eckelcu@cisco.com> <D1A73596.34B10%rmohanr@cisco.com> <55817A9F.8040901@alum.mit.edu> <D1A88AA1.34CC8%rmohanr@cisco.com> <5582FB13.5060204@alum.mit.edu> <D1A9977E.34E64%rmohanr@cisco.com>
In-Reply-To: <D1A9977E.34E64%rmohanr@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/DJLjLA0j_Yl5f3MrTo9Ag_auFHE>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 22 Jun 2015 15:13:18 -0000

ON: 19 June 2015 00:46 Ram Mohan R Wrote:
>=20
> I have a question - is it allowed to have a two different C-T (say
> "application/rs-metadata-request" and "application/rs-metadata") and
> still
> have content point to same XML document ?
> The reason for asking is I still feel they have to be different C-T as
> they are not related. One C-T is for representing the snapshot of
> metadata
> and other is for requesting the same. So logically it make sense to
> still
> consider them as two different content-types. The C-D can be same as
> both
> are for recording session.
>=20


I don't think they have to be different C-T's that surely depends on how th=
e XML content is defined.

Andy


From nobody Mon Jun 22 08:15:25 2015
Return-Path: <andrew.hutton@unify.com>
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 043191ACD3D for <siprec@ietfa.amsl.com>; Mon, 22 Jun 2015 08:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 cQYB2Iv5Q7Wj for <siprec@ietfa.amsl.com>; Mon, 22 Jun 2015 08:15:23 -0700 (PDT)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 0C15A1A1B87 for <siprec@ietf.org>; Mon, 22 Jun 2015 08:15:23 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx12.unify.com (Server) with ESMTP id 539E823F0468; Mon, 22 Jun 2015 17:15:22 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.9]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0224.002; Mon, 22 Jun 2015 17:15:21 +0200
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQmLk7GVjaOmlorUqQBpj3aMW38p2yoWlJgAYpLxA=
Date: Mon, 22 Jun 2015 15:15:20 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF1E7CD3DF@MCHP04MSX.global-ad.net>
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu> <D1921296.4E781%eckelcu@cisco.com> <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in> <D1A44B8B.343CD%rmohanr@cisco.com> <D1A5E31A.4FA7C%eckelcu@cisco.com> <D1A73596.34B10%rmohanr@cisco.com> <55817A9F.8040901@alum.mit.edu> <D1A88AA1.34CC8%rmohanr@cisco.com> <5582FB13.5060204@alum.mit.edu>
In-Reply-To: <5582FB13.5060204@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/9j1uvdGp48k_EzLNefKOl3WgGIM>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 22 Jun 2015 15:15:24 -0000

On: 18 June 2015 13:09 Paul Kyzivat Wrote:


>=20
> So, what I am suggesting is:
> - make the message be XML
> - use the same schema used for SRC to SRS messages
> - use the same C-T and C-D for both directions
> - add a new entity definition to that schema for the purpose
> - specify that for SRS to SRC, only the one new entity is valid
> - specify the behavior when something else is received by the SRC,
>    in a way that allows for future extensibility.
>=20
> 	Thanks,
> 	Paul

Although it is a fairly significant and rather late change I can see the be=
nefit of this approach Paul's suggestion seems to make sense to me.

Andy


From nobody Mon Jun 22 08:42:33 2015
Return-Path: <rmohanr@cisco.com>
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 AA6AA1B2B20 for <siprec@ietfa.amsl.com>; Mon, 22 Jun 2015 08:42:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 p5BJXR6LChfo for <siprec@ietfa.amsl.com>; Mon, 22 Jun 2015 08:42:30 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B5051B2F78 for <siprec@ietf.org>; Mon, 22 Jun 2015 08:42:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1685; q=dns/txt; s=iport; t=1434987750; x=1436197350; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=ygbQLgqxjJ3CDIj1dqgwWpDmHoBfy8ZiR9WT1jXwnYc=; b=lBlE+duc3gC++iGa/fyLncGpz67ONm5EWghzC0iA99fJyq3wGI/BLwuW 2h009XdwT5jFliQZZHy2GYf+af5wjUFU7TMjCCJxAUucAnqnzH8QVxbOy L5gCbSkwlK24nEe6xNNGsz0sxBBL42QujKqHSSHk8fVeP4kFGxLJR+xTb s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AwBAAnLIhV/5BdJa1cDoMCgTMGuVqEKwmHXgKBODgUAQEBAQEBAYEKhCIBAQEEgQUEAgEIEQMBAgEuMh0IAgQBEogvyjgBAQEBAQEBAQIBAQEBAQEBARqLRYRbMgaEJQEEjESEXoJbAYtNgTqOdogBJmOBWX8+b4FGgQIBAQE
X-IronPort-AV: E=Sophos;i="5.13,660,1427760000";  d="scan'208";a="9298871"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-1.cisco.com with ESMTP; 22 Jun 2015 15:42:29 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t5MFgTmb010187 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 22 Jun 2015 15:42:29 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.106]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0195.001; Mon, 22 Jun 2015 10:42:29 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Hutton, Andrew" <andrew.hutton@unify.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQrQILbkLFNQjY5kCETRqJyDLuSw==
Date: Mon, 22 Jun 2015 15:42:28 +0000
Message-ID: <D1AE278B.351F3%rmohanr@cisco.com>
References: <20150527201048.14199.57234.idtracker@ietfa.amsl.com> <556739CD.4000204@alum.mit.edu> <D1921296.4E781%eckelcu@cisco.com> <3153DE64-FC84-4903-9974-40B0A7433327@cooperw.in> <D1A44B8B.343CD%rmohanr@cisco.com> <D1A5E31A.4FA7C%eckelcu@cisco.com> <D1A73596.34B10%rmohanr@cisco.com> <55817A9F.8040901@alum.mit.edu> <D1A88AA1.34CC8%rmohanr@cisco.com> <5582FB13.5060204@alum.mit.edu> <D1A9977E.34E64%rmohanr@cisco.com> <9F33F40F6F2CD847824537F3C4E37DDF1E7CD3A9@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF1E7CD3A9@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [10.65.44.53]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8AC7402E3AD64440866F09108F5E6572@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/jrmGkT48cuSBq-QGZZJMvDx2jaM>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 22 Jun 2015 15:42:31 -0000

-----Original Message-----
From: <Hutton>, Andrew <andrew.hutton@unify.com>
Date: Monday, 22 June 2015 8:43 pm
To: Cisco Employee <rmohanr@cisco.com>, Paul Kyzivat
<pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Subject: RE: [siprec] Barry Leiba's Discuss on
draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)

>ON: 19 June 2015 00:46 Ram Mohan R Wrote:
>>=20
>> I have a question - is it allowed to have a two different C-T (say
>> "application/rs-metadata-request" and "application/rs-metadata") and
>> still
>> have content point to same XML document ?
>> The reason for asking is I still feel they have to be different C-T as
>> they are not related. One C-T is for representing the snapshot of
>> metadata
>> and other is for requesting the same. So logically it make sense to
>> still
>> consider them as two different content-types. The C-D can be same as
>> both
>> are for recording session.
>>=20
>
>
>I don't think they have to be different C-T's that surely depends on how
>the XML content is defined.

Sure.

As I mentioned I don=B9t see any real advantage in having same C-T vs
different one.  OTOH by having same C-T for metadata req and metadata, an
SRC now has to parse the entire XML to understand what the SRS wants
before replying to the RE-INVITE/UPDATE it got from SRS. By having a
different C-T by an SRC can act by looking at the C-T header value itself
and optionally choose to parse XML.  If that is some thing the WG is ok
with I am fine as well.

I will come up with the XML syntax for the request on the suggestion from
Paul and send the updated schema to the list.

Regards,
Ram

>Andy


From nobody Mon Jun 22 11:29:49 2015
Return-Path: <Yaron.Pdut@nice.com>
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 43C931A1A58 for <siprec@ietfa.amsl.com>; Mon, 22 Jun 2015 11:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level: 
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 XF_1-O1H-f8e for <siprec@ietfa.amsl.com>; Mon, 22 Jun 2015 11:29:44 -0700 (PDT)
Received: from mailil.nice.com (mailil.nice.com [192.114.148.4]) by ietfa.amsl.com (Postfix) with ESMTP id 610B01A1A4A for <siprec@ietf.org>; Mon, 22 Jun 2015 11:29:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.13,660,1427749200"; d="scan'208";a="39597863"
Received: from TLVMBX02.nice.com ([fe80::4cde:216b:6cff:cf37]) by tlvcas02.nice.com ([192.168.253.18]) with mapi; Mon, 22 Jun 2015 21:29:32 +0300
From: Yaron Pdut <Yaron.Pdut@nice.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, Andrew Hutton <andrew.hutton@unify.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Date: Mon, 22 Jun 2015 21:29:31 +0300
Thread-Topic: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQrQILbkLFNQjY5kCETRqJyDLuS5242L/z
Message-ID: <nw7mrb9sd2g08dii72ye8xu6.1434997940378@email.android.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/ujtfAkSDfMFsmcbi3he8FeICEl8>
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 22 Jun 2015 18:29:46 -0000

Trying to be pragmatic, today there are dozens of SIPREC implementations in=
 the market that support the current specification for few years now, I do =
not see them modifing code at this stage.

This means that the RFC will be a dead word for most vendors on one hand an=
d will force SRS vendors to support yet another version (we already support=
 at least 3 flavors of it today) on the other hand.

Already today there are many voices in industry thinking SIPREC intrudoce t=
oo much overhead. It is too open, too complex protocol, and they are consid=
ering lightweight REST based API as an alternative.

Approving this, IMHO, will put SIPREC future in a question.

BR,
Yaron

-------- Original Message --------
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
Date: Mon, June 22, 2015 6:42 PM +0300
To: "Hutton, Andrew" <andrew.hutton@unify.com>, Paul Kyzivat <pkyzivat@alum=
.mit.edu>, siprec@ietf.org
Subject: Re: [siprec] Barry Leiba's Discuss on draft-ietf-siprec-protocol-1=
6: (with DISCUSS and COMMENT)


-----Original Message-----
From: <Hutton>, Andrew <andrew.hutton@unify.com>
Date: Monday, 22 June 2015 8:43 pm
To: Cisco Employee <rmohanr@cisco.com>, Paul Kyzivat
<pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Subject: RE: [siprec] Barry Leiba's Discuss on
draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)

>ON: 19 June 2015 00:46 Ram Mohan R Wrote:
>>
>> I have a question - is it allowed to have a two different C-T (say
>> "application/rs-metadata-request" and "application/rs-metadata") and
>> still
>> have content point to same XML document ?
>> The reason for asking is I still feel they have to be different C-T as
>> they are not related. One C-T is for representing the snapshot of
>> metadata
>> and other is for requesting the same. So logically it make sense to
>> still
>> consider them as two different content-types. The C-D can be same as
>> both
>> are for recording session.
>>
>
>
>I don't think they have to be different C-T's that surely depends on how
>the XML content is defined.

Sure.

As I mentioned I don=B9t see any real advantage in having same C-T vs
different one.  OTOH by having same C-T for metadata req and metadata, an
SRC now has to parse the entire XML to understand what the SRS wants
before replying to the RE-INVITE/UPDATE it got from SRS. By having a
different C-T by an SRC can act by looking at the C-T header value itself
and optionally choose to parse XML.  If that is some thing the WG is ok
with I am fine as well.

I will come up with the XML syntax for the request on the suggestion from
Paul and send the updated schema to the list.

Regards,
Ram

>Andy

_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec


From nobody Mon Jun 22 16:36:22 2015
Return-Path: <ben@nostrum.com>
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 6E6501A90DB; Mon, 22 Jun 2015 16:36:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.39
X-Spam-Level: *
X-Spam-Status: No, score=1.39 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, T_RP_MATCHES_RCVD=-0.01] 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 7V7SuZ9wxqbc; Mon, 22 Jun 2015 16:36:18 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 399131B2A71; Mon, 22 Jun 2015 16:36:18 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t5MNa3Sj011586 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 22 Jun 2015 18:36:14 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: "Ben Campbell" <ben@nostrum.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Date: Mon, 22 Jun 2015 18:36:03 -0500
Message-ID: <BEA4A46B-E69E-405A-A215-858B6FD21987@nostrum.com>
In-Reply-To: <D1A88627.5019B%eckelcu@cisco.com>
References: <20150526231115.15164.11308.idtracker@ietfa.amsl.com> <D1A88627.5019B%eckelcu@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.1r5084)
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/8rwdxQYLidVibNfya81PCIhetak>
Cc: "draft-ietf-siprec-protocol@ietf.org" <draft-ietf-siprec-protocol@ietf.org>, "draft-ietf-siprec-protocol.ad@ietf.org" <draft-ietf-siprec-protocol.ad@ietf.org>, "siprec-chairs@ietf.org" <siprec-chairs@ietf.org>, "siprec@ietf.org" <siprec@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-siprec-protocol.shepherd@ietf.org" <draft-ietf-siprec-protocol.shepherd@ietf.org>
Subject: Re: [siprec] Ben Campbell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 22 Jun 2015 23:36:20 -0000

Hi, thanks for the response. Comments inline. (I removed things that 
don't seem to need discussion)

Ben.

On 18 Jun 2015, at 18:49, Charles Eckel (eckelcu) wrote:

> Hi Ben,
>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> I am concerned that this draft allows the recording session to 
>> downgrade
>> security from the communication session. It says "SHOULD NOT", but 
>> then
>> explicitly allows for the downgrade when the SRC and SRS are in the 
>> same
>> administrative domain. This seems to create a whole new "last hop
>> exception" for media, similar to the one for SIPS that we took so 
>> many
>> years to deprecate. (Except it's worse because the potentially 
>> insecure
>> hop goes to an endpoint not necessarily expected to be a party to the
>> media.)
>
> Andy explained as follows:
>
> "I think the issue here is that the SRC and SRS will often be 
> co-located
> in an environment where mutual authentication was just not necessary 
> and
> therefore the WG did not want to mandate this in all cases.Â²
>

I think Andy's comments were to Stephen's discuss about mutual 
authentication in general. This is a somewhat different issue. I'm 
talking about when the participants of a call chosen to use certain 
security protections on the CS, and the SRC and SRS downgrade that for 
the RS.

(and by the way, I wrote that it says "SHOULD NOT" in my discussion, but 
the text in 12 actually says "should not". That should probably be 
capitalized unless it's stated elsewhere in caps.)

>>
>> Section 6.1.2 includes a "contract in place" as a form of recording
>> indication. The other mechanisms seem to say that a given call is 
>> being
>> recorded. A contract cannot do that, except in the degenerate case of
>> "all calls are recorded." This doesn't seem to fit the spirit of the
>> "MUST provide recording indication" language.
>
> I expanded section 6.3 in an attempt to address similar concerns:
>
> A recording-aware UA MUST provide a recording indication to the end 
> user
> through an appropriate user interface, indicating whether recording is
> on, off, or paused for each medium. Appropriate user interfaces may
> include real-time notification or previously established agreements 
> that
> use of the device is subject to recording.  Some user agents that are
> automatons (e.g., IVR, media server, PSTN gateway) may not have a user
> interface to render recording indication.  When such a user agent
> indicates recording awareness, the UA SHOULD render recording 
> indication
> through other means, such as passing an in-band tone on the PSTN
> gateway, putting the recording indication in a log file, or raising an
> application event in a VoiceXML dialog.  These user agents MAY also
> choose not to indicate recording awareness, thereby relying on 
> whatever
> mechanism an SRC chooses to indicate recording, such as playing a tone
> in-band.

I don't think that addresses my concern. There's a fundamental 
difference between an indication that this call is being recorded, and 
an agreement that all calls might be recorded. (Unless that agreement 
says all calls _will_ be recorded). The language here seems to conflate 
the two.

I realize that the following is mostly in the domain of lawyers and not 
engineers--but what happens when my mobile operator puts a "may record" 
clause in my user agreement. That seems to qualify under the language 
used here.

>
>
>
>>
>> Section 12, 2nd paragraph says the SRC and SRS "MUST support SIP with 
>> TLS
>> and MAY support SIPS with
>> TLS as per [RFC5630]". That actually downgrades the requirement for
>> SIPS support from that in 3261/5630. (3261 says you MUST support SIPS 
>> if
>> you support TLS.)
>
> As noted in RFC 5630, SIPS was underspecified in RFC 3261 and this was 
> a
> source of confusion. RFC 5360 aimed to fix this, and states:
>
> Because a SIPS URI implies that requests sent to the resource
> identified by it be sent over each SIP hop over TLS, SIPS URIs are
> not suitable for "best-effort TLS": they are only suitable for "TLS-
> only" requests.  This is recognized in Section 26.2.2 of [RFC3261]
> <http://tools.ietf.org/html/rfc3261#section-26.2.2>.
> Users that distribute a SIPS URI as an address-of-record may elect
>    to operate devices that refuse requests over insecure transports.
> If one wants to use "best-effort TLS" for SIP, one just needs to use
> a SIP URI, and send the request over TLS.

The quoted language is about when it might not be appropriate to _use_ 
SIPS. It doesn't talk at all about _support_ requirements. In 
particular, it does not relax the 3261 requirement that says "Any 
implementation that supports TLS MUST support the SIPS URI scheme."

>
>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------

[...]

>
>>
>> -- 5.2: UPDATE needs a citation to 3311. Also, 3311 "RECOMMENDS"
>> reINVITEs over UPDATEs for confirmed dialogs. It would be helpful to 
>> add
>> some motivation as to why this draft seems to prefer UPDATE.
>
> Added a citation. UPDATE is preferred, actually required, for the SRS 
> to
> request to snapshot, but re-INVITE or UPDATE can be used by the SRC to
> send metadata. I donÂ¹t believe any preference was meant to be 
> implied.
> UPDATE was chosen for the SRS to request metadata because it could be 
> sent
> regardless of the state of the dialog. This was seen as better than
> requiring support for both UPDATE and re-INVITE for this operation.

It would be worth adding a sentence or two to that effect.

>
>>
>> -- 5.3: It seems odd to me that the SRC can ignore an explicit 
>> preference
>> not to record. Wouldn't it be better just to refuse to 
>> complete/accept
>> the call, if some policy overrides the end-user's preference?
>
> We decided to leave this choice to the user, who can drop the call if 
> the
> recording state of the call is not acceptable to the user.

That choice makes it considerably more likely for a user to accidentally 
allow themselves to be recorded when they intended not to.

>
>>
>> -- Figure 3: If the UA prefers not to be recorded, shouldn't it 
>> express
>> that at setup time, rather than wait for the SRC to indicate 
>> recording is
>> happening? As shown, this almost guarantees a bit of media will be
>> recorded. (Seems like there should be some guidance about this in the
>> text.) The last paragraph of 6.1.2 seems to reinforce the problem by
>> suggesting the participant might base the decision to express a
>> preference on a tag that is optional for the SRC to send in the first
>> place.
>
> Yes, but in this case the example read, "After the call is established 
> and
> recording is in progress, UA (B) later decides to change the recording
> preference to no recordingÂ². This real time interaction seemed useful 
> as a
> example. More examples can be added if necessary.
> Note that the use of the a=record attribute is REQUIRED when 
> recording. It
> is not optional.

Whether there are more examples or not, it would be useful to have a 
discussion of the implications of expressing a recording preference 
proactively vs reactively.


>
>>
>> -- 6.3, last paragraph: It seems odd that the requirement to render a
>> recording indicator be lower for a media server than for other UAs. 
>> This
>> seems to circumvent user notification in one of the most common uses 
>> of
>> recording these days.
>
> This section was reworded, as quoted in my previous comment.

The rewording still has the issue. a recording aware UA MUST provide a 
recording indication. UAs without appropriate user interfaces (like 
IVRs, media servers, etc) SHOULD indicate this some other way. SHOULD is 
a lower requirement than MUST.

>
>>
>> -- 9.1 : The last bullet seems to be a motivation to not send 
>> metadata at
>> all, which is expressly forbidden in the first paragraph.
>
> This was meant to illustrate that the SRC may not record everything to
> which it has access, with privacy concerns being one example. I 
> suppose
> such filtering could be performed later on the recorded content, but 
> that
> assumes a specific relationship the administrative domain of the SRC 
> and
> that of the SRS.

So does "not record everything" include the ability to send no metadata? 
Perhaps the first sentence in 9.1 that says "The SRC MUST send metadata" 
is overstated?

>
>>
>> -- 9.2: The use of  the content-type value as the sole indicator that 
>> the
>> an UPDATE request should be interpreted as an request for a metadata
>> snapshot update is rather odd.  If you end up with new kinds of 
>> metadata
>> requests in the future, does each one get it's own media-type?
>
> This is being sorted out in another thread. I agree, something needs 
> to
> change here.

Understood, I will watch that thread.

>
>>
>> -- 12: If this doc is to depend on the security considerations in 
>> 6341,
>> that needs to be a normative reference--which is a bit of a pain 
>> because
>> I think it's an informational RFC.
>
> We tried to avoid this with the language "The use cases and 
> requirements
> document [RFC6341] outlines the general security considerations, and 
> this
> document describes specific security recommendations.Â²

Could the reader fully understand the security considerations without 
reading 6341? If so, then informational is okay.

>
>>
>> -- 12.1:
>> "recording session uses TLS" -- I assume that's for SIP? Also It's 
>> worth
>> discussing how mutual authentication applies if the SRC is in an 
>> end-user
>> device. Is it expected to have a client cert? No option to use  SIP
>> identity?
>>
>> Also, I'm a bit uncomfortable assuming devices in the same 
>> administrative
>> domain automatically trust each other. It might be better to say "If 
>> they
>> trust each other..."
>
> Using the word Â³trust" is a slippery slope as well.

The text already uses that word. It says that if the SRS and SRC are in 
the same domain, they have an inherent trust relationship. That's not 
always the case.

> For a UA acting as a
> SRC, the implied requirement is that it has a cert.

Better to be explicit.

[...]


From nobody Tue Jun 23 11:00:54 2015
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 B071B1B2EB2 for <siprec@ietfa.amsl.com>; Tue, 23 Jun 2015 11:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.664
X-Spam-Level: 
X-Spam-Status: No, score=0.664 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 fATi9j3Ym22J for <siprec@ietfa.amsl.com>; Tue, 23 Jun 2015 11:00:51 -0700 (PDT)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9123C1B2EAD for <siprec@ietf.org>; Tue, 23 Jun 2015 11:00:51 -0700 (PDT)
Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-11v.sys.comcast.net with comcast id ju0c1q0032N9P4d01u0qyr; Tue, 23 Jun 2015 18:00:50 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-13v.sys.comcast.net with comcast id ju0q1q00Q3Ge9ey01u0q8Z; Tue, 23 Jun 2015 18:00:50 +0000
Message-ID: <55899ED1.5040700@alum.mit.edu>
Date: Tue, 23 Jun 2015 14:00:49 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: siprec@ietf.org
References: <20150526231115.15164.11308.idtracker@ietfa.amsl.com> <D1A88627.5019B%eckelcu@cisco.com> <BEA4A46B-E69E-405A-A215-858B6FD21987@nostrum.com>
In-Reply-To: <BEA4A46B-E69E-405A-A215-858B6FD21987@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1435082450; bh=W0l1g47qiq6w6z4nZBRx61vORvfVO3boceQSpe38wd4=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ZmC4zsJB51p6+Ni68iKBRUwBeNc5ya0PcE7lk6LAO8zWr9PIrNARPM+eOtUWzNqu2 3aESqQCEif5EVix7WDuZvbLZo5Qd5UqiBzCO+j5wGdap29NrMKttZUgRI4vPAHWzex D9/2Tnm3g77p4zOAf+JCiaVZQ/4XVD4YhaZQ8T56yb46piY5RXLW4vz00uc4zM02lE fGh9uXtn0x4IW5UlJvP8JkHE2DGGSZPyU6Lwtzqu153hVpRxIZqA0KayWLlsl4ZBvb cIclgAAUPUlp8Zs9aB6t5OMnbWxHGqdmBgV4auTS4cMN8wW4+7ezG8GbpQ1Q61s1zM MdyWEgBgyF64w==
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/Qiux9Uid1y0rOETTGb1tjfDEi-4>
Subject: Re: [siprec] Ben Campbell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 23 Jun 2015 18:00:52 -0000

On 6/22/15 7:36 PM, Ben Campbell wrote:

>> A recording-aware UA MUST provide a recording indication to the end user
>> through an appropriate user interface, indicating whether recording is
>> on, off, or paused for each medium. Appropriate user interfaces may
>> include real-time notification or previously established agreements that
>> use of the device is subject to recording.  Some user agents that are
>> automatons (e.g., IVR, media server, PSTN gateway) may not have a user
>> interface to render recording indication.  When such a user agent
>> indicates recording awareness, the UA SHOULD render recording indication
>> through other means, such as passing an in-band tone on the PSTN
>> gateway, putting the recording indication in a log file, or raising an
>> application event in a VoiceXML dialog.  These user agents MAY also
>> choose not to indicate recording awareness, thereby relying on whatever
>> mechanism an SRC chooses to indicate recording, such as playing a tone
>> in-band.
>
> I don't think that addresses my concern. There's a fundamental
> difference between an indication that this call is being recorded, and
> an agreement that all calls might be recorded. (Unless that agreement
> says all calls _will_ be recorded). The language here seems to conflate
> the two.
>
> I realize that the following is mostly in the domain of lawyers and not
> engineers--but what happens when my mobile operator puts a "may record"
> clause in my user agreement. That seems to qualify under the language
> used here.

I appreciate your concern. I would be *very* unhappy if a carrier put 
such language in my contract. I can imagine that this could be presented 
as a non-negotiable condition of service, though I consider that to be 
entirely unreasonable. (However, whether the language is there or not, 
in practice that is what the current situation is in the US with CALEA.)

OTOH, there are situations where this is entirely appropriate - the call 
center case, or for stock brokers - there there are requirements to 
record. Certainly in the call center case it would be a problem to 
include an indication of recording in the audio stream to the agent. 
Potentially a call center agent work station could have other means to 
indicate recording. But that would exclude some common existing 
equipment. Also, in the call center case, if there is an indication, 
then there would probably be a preference by management to always 
indicate that calls are being recorded, even if they might not be, so 
that the agent wouldn't know when he was being recorded. Also, this 
overlaps with active listening (by conferencing in a supervisor) that is 
technically (and legally?) distinct from recording and yet has similar 
concerns.

It is unclear here how to balance the concerns. I'm certainly open to 
suggestions about how best to do this.

	Thanks,
	Paul


From nobody Tue Jun 23 21:12:10 2015
Return-Path: <rmohanr@cisco.com>
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 D1B991B3466 for <siprec@ietfa.amsl.com>; Tue, 23 Jun 2015 21:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Atfmyzrq6dEh for <siprec@ietfa.amsl.com>; Tue, 23 Jun 2015 21:12:07 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84D371B3464 for <siprec@ietf.org>; Tue, 23 Jun 2015 21:12:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1530; q=dns/txt; s=iport; t=1435119127; x=1436328727; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=SiHycUj/WKuBw/G5vrajx7W4sTwEWLOrUsGr2RkXNNY=; b=cmQv9b0sIoPevksnsX3UEHHOa4V3X5OAGiMD3Q5igCgci8bloRQxlByg rwXvMup0BI8TAzWfB+gH6kncoapVH6k7yufzYjORBIDGgJbfWpWxC4Jr8 TpceYhefMOmUv8KIPk4VTU2Ms0Yr0pdeGG5VjI4CAD/gU+ThL7Z9+CZ1R U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AzBQB3LYpV/4MNJK1bDoMCgTMGuUGENIdeAoFEOhIBAQEBAQEBgQqEIgEBAQQ6SwQCAQgOAwMBAh8QMh0IAgQBEogvzR0BAQEBAQEBAQIBAQEBAQEBG4tKhQ0GhCUFk38Bi1CYNSZjgVp/Pm+BRoECAQEB
X-IronPort-AV: E=Sophos;i="5.13,669,1427760000"; d="scan'208";a="162176349"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-3.cisco.com with ESMTP; 24 Jun 2015 04:12:06 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t5O4C63o010240 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 24 Jun 2015 04:12:06 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.76]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0195.001; Tue, 23 Jun 2015 23:12:06 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: [siprec] Ben Campbell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQrjPu4KdcCtvdHUeIsL1rmo21NA==
Date: Wed, 24 Jun 2015 04:12:06 +0000
Message-ID: <D1B02A47.35615%rmohanr@cisco.com>
References: <20150526231115.15164.11308.idtracker@ietfa.amsl.com> <D1A88627.5019B%eckelcu@cisco.com> <BEA4A46B-E69E-405A-A215-858B6FD21987@nostrum.com> <55899ED1.5040700@alum.mit.edu>
In-Reply-To: <55899ED1.5040700@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.1.150515
x-originating-ip: [173.39.66.165]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7AC329DB0335B141A19F3655863BEBA5@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/hz5xp_NRGeCrD5mRZ9aKfZtopM8>
Subject: Re: [siprec] Ben Campbell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 24 Jun 2015 04:12:09 -0000

-----Original Message-----
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Date: Tuesday, 23 June 2015 11:30 pm
To: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] Ben Campbell's Discuss on
draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)

>OTOH, there are situations where this is entirely appropriate - the call
>center case, or for stock brokers - there there are requirements to
>record. Certainly in the call center case it would be a problem to
>include an indication of recording in the audio stream to the agent.
>Potentially a call center agent work station could have other means to
>indicate recording. But that would exclude some common existing
>equipment. Also, in the call center case, if there is an indication,
>then there would probably be a preference by management to always
>indicate that calls are being recorded, even if they might not be, so
>that the agent wouldn't know when he was being recorded. Also, this
>overlaps with active listening (by conferencing in a supervisor) that is
>technically (and legally?) distinct from recording and yet has similar
>concerns.

My understanding w.r.t Call Centre is the agent is informed that some of
his calls may be recorded for quality monitoring, supervising e.t.c
This could just be a contact clause/via some other means. Now exactly
which calls are being recorded/monitored is something I guess Agents may
not really know.
It is ok in a environment like CallCentre but definitely NOT acceptable
elsewhere.

Ram


From nobody Wed Jun 24 00:34:27 2015
Return-Path: <DAVE.HIGTON@nice.com>
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 60BBD1B3118 for <siprec@ietfa.amsl.com>; Wed, 24 Jun 2015 00:34:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.012
X-Spam-Level: 
X-Spam-Status: No, score=-5.012 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 0iKKL5YR1N6b for <siprec@ietfa.amsl.com>; Wed, 24 Jun 2015 00:34:24 -0700 (PDT)
Received: from SOUMD02.eu.nice.com (ukemail.nice.com [195.99.0.242]) by ietfa.amsl.com (Postfix) with ESMTP id EF2581B3116 for <siprec@ietf.org>; Wed, 24 Jun 2015 00:34:23 -0700 (PDT)
Received: from mail pickup service by SOUMD02.eu.nice.com with Microsoft SMTPSVC; Wed, 24 Jun 2015 08:34:22 +0100
Received: from SOUCAS10a.eu.nice.com ([10.1.1.36]) by SOUMD02.eu.nice.com with Microsoft SMTPSVC(8.5.9600.16384); Wed, 24 Jun 2015 08:34:22 +0100
Received: from SOUMBX10A.eu.nice.com ([10.1.1.34]) by SOUCAS10a.eu.nice.com ([10.1.1.36]) with mapi id 14.03.0224.002; Wed, 24 Jun 2015 08:34:22 +0100
From: "Dave Higton" <DAVE.HIGTON@nice.com>
To: <siprec@ietf.org>
Thread-Topic: [siprec] Ben Campbell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
Thread-Index: AQHQqiGfYk2RVRzGU06yLYfCMg0/PJ25I2CAgAE0q4CAAPE2IA==
Date: Wed, 24 Jun 2015 07:34:21 +0000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.3.9600.17728
Message-ID: <A0F1EB49F328CB479867909C77D380E3CEC2@SOUMBX10a.eu.nice.com>
References: <20150526231115.15164.11308.idtracker@ietfa.amsl.com> <D1A88627.5019B%eckelcu@cisco.com> <BEA4A46B-E69E-405A-A215-858B6FD21987@nostrum.com> <55899ED1.5040700@alum.mit.edu>
In-Reply-To: <55899ED1.5040700@alum.mit.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.44.60.68]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 24 Jun 2015 07:34:22.0539 (UTC) FILETIME=[305751B0:01D0AE50]
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/cdt0wzKnNzMHLsbRODND3DaaXPU>
Subject: Re: [siprec] Ben Campbell's Discuss on draft-ietf-siprec-protocol-16: (with DISCUSS and COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 24 Jun 2015 07:34:26 -0000

On 23 June 2015 19:01 Paul Kyzivat wrote:

On 6/22/15 7:36 PM, Ben Campbell wrote:

>> A recording-aware UA MUST provide a recording indication to the end =
user
>> through an appropriate user interface, indicating whether recording =
is
>>> on, off, or paused for each medium. Appropriate user interfaces may
>>> include real-time notification or previously established agreements =
that
>>> use of the device is subject to recording.  Some user agents that =
are
>>> automatons (e.g., IVR, media server, PSTN gateway) may not have a =
user
>>> interface to render recording indication.  When such a user agent
>>> indicates recording awareness, the UA SHOULD render recording =
indication
>>> through other means, such as passing an in-band tone on the PSTN
>>> gateway, putting the recording indication in a log file, or raising =
an
>>> application event in a VoiceXML dialog.  These user agents MAY also
>>> choose not to indicate recording awareness, thereby relying on =
whatever
>>> mechanism an SRC chooses to indicate recording, such as playing a =
tone
>>> in-band.
>>
>> I don't think that addresses my concern. There's a fundamental
>> difference between an indication that this call is being recorded, =
and
>> an agreement that all calls might be recorded. (Unless that agreement
>> says all calls _will_ be recorded). The language here seems to =
conflate
>> the two.
>>
>> I realize that the following is mostly in the domain of lawyers and =
not
>> engineers--but what happens when my mobile operator puts a "may =
record"
>> clause in my user agreement. That seems to qualify under the language
>> used here.
>
>I appreciate your concern. I would be *very* unhappy if a carrier put=20
>such language in my contract. I can imagine that this could be =
presented=20
>as a non-negotiable condition of service, though I consider that to be=20
>entirely unreasonable. (However, whether the language is there or not,=20
>in practice that is what the current situation is in the US with =
CALEA.)
>
>OTOH, there are situations where this is entirely appropriate - the =
call=20
>center case, or for stock brokers - there there are requirements to=20
>record. Certainly in the call center case it would be a problem to=20
>include an indication of recording in the audio stream to the agent.=20
>Potentially a call center agent work station could have other means to=20
>indicate recording. But that would exclude some common existing=20
>equipment. Also, in the call center case, if there is an indication,=20
>then there would probably be a preference by management to always=20
>indicate that calls are being recorded, even if they might not be, so=20
>that the agent wouldn't know when he was being recorded. Also, this=20
>overlaps with active listening (by conferencing in a supervisor) that =
is=20
>technically (and legally?) distinct from recording and yet has similar=20
>concerns.
>
>It is unclear here how to balance the concerns. I'm certainly open to=20
>suggestions about how best to do this.

Indication to users that they are being recorded is surely a system =
level
consideration.  For example, it's perfectly reasonable for a company to
formally inform all its staff of the policy on call recording, and it's =
usual
for a telephone system to answer all incoming calls with a recorded
message informing the caller that the call will or may be recorded.

I don't think it is reasonable to mandate that a UA must provide the
indication.

It's worth a mention somewhere that informing users is a common
legal requirement and that due consideration must be given to how
that is to be achieved.  But IMHO that's all that SIPREC can say.

Dave

PS My apologies if I've not got the quoting right.  The only tool I
can use here is Outlook.



NICE Systems UK Limited ("NICE") is registered in England under company =
number, 3403044. The registered office of NICE is at Tollbar Way, Hedge =
End, Southampton, Hampshire SO30 2ZP.

Confidentiality: This communication and any attachments are intended for =
the above-named persons only and may be confidential and/or legally =
privileged. Any opinions expressed in this communication are not =
necessarily those of NICE. If this communication has come to you in =
error you must take no action based on it, nor must you copy or show it =
to anyone; please delete/destroy and inform the sender by e-mail =
immediately.

Monitoring: NICE may monitor incoming and outgoing e-mails.

Viruses: Although we have taken steps toward ensuring that this e-mail =
and attachments are free from any virus, we advise that in keeping with =
good computing practice the recipient should ensure they are actually =
virus free.


From nobody Wed Jun 24 13:46:19 2015
Return-Path: <iana-shared@icann.org>
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 CFB461B29E0; Wed, 24 Jun 2015 09:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.41
X-Spam-Level: 
X-Spam-Status: No, score=-2.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 RUwoOGhD6vXs; Wed, 24 Jun 2015 09:02:01 -0700 (PDT)
Received: from smtp1.lax.icann.org (smtp01.icann.org [192.0.33.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E88C1B2A41; Wed, 24 Jun 2015 09:01:29 -0700 (PDT)
Received: from request3.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp1.lax.icann.org (8.13.8/8.13.8) with ESMTP id t5OG1Rnf012647;  Wed, 24 Jun 2015 16:01:27 GMT
Received: by request3.lax.icann.org (Postfix, from userid 48) id F03C9C207A1; Wed, 24 Jun 2015 16:01:27 +0000 (UTC)
RT-Owner: pearl.liang
From: "Pearl Liang via RT" <iana-issues@iana.org>
In-Reply-To: <rt-4.2.9-2438-1432030135-51.824299-7-0@icann.org>
References: <RT-Ticket-824299@icann.org> <RT-Ticket-821860@icann.org> <20150501233938.13902.67660.idtracker@ietfa.amsl.com> <rt-4.2.9-25910-1431621812-625.821860-7-0@icann.org> <D17FA1B7.49878%eckelcu@cisco.com> <rt-4.2.9-32567-1431972582-1818.824299-7-0@icann.org> <D180CA12.49F2B%eckelcu@cisco.com> <rt-4.2.9-2438-1432030135-51.824299-7-0@icann.org>
Message-ID: <rt-4.2.9-574-1435161687-949.824299-7-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #824299
X-Managed-BY: RT 4.2.9 (http://www.bestpractical.com/rt/)
X-RT-Originator: pearl.liang@icann.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Wed, 24 Jun 2015 16:01:27 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/siprec/rWb5-LrX9AzlR2JNP5n14Rjx2WI>
X-Mailman-Approved-At: Wed, 24 Jun 2015 13:46:17 -0700
Cc: siprec@ietf.org, siprec-chairs@ietf.org, draft-ietf-siprec-protocol@ietf.org
Subject: [siprec] [IANA #824299] Re: Last Call: <draft-ietf-siprec-protocol-16.txt> (Session Recording Protocol) to Proposed Standard
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: iana-issues@iana.org
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 24 Jun 2015 16:02:04 -0000

Hello,

Upon review, Flemming Andreasen, DE, has approved this request:

This draft requests to register two new SDP Parameters in the sub-registry
att-field (both session and media level) of the SDP Parameters registry
located at:

http://www.iana.org/assignments/sdp-parameters/

Two proposed new SDP attributes are:

Type: att-field (both session and media level)
SDP Name: record
Reference: [ RFC-to-be ]

Type: att-field (both session and media level)
SDP Name: recordpref
Reference: [ RFC-to-be ]

Thanks,
~pl

Pearl Liang
ICANN



On Tue May 19 10:08:55 2015, eckelcu@cisco.com wrote:
> Correct. Thanks.
> 
> Charles
> 
> On 5/18/15, 7:09 PM, "Pearl Liang via RT" <drafts-lastcall@iana.org> wrote:
> 
> >On Mon May 18 13:56:50 2015, eckelcu@cisco.com wrote:
> >> Hi Pearl,
> >> 
> >> Thank you for reviewing and providing your comments and questions. I
> >>have
> >> indicated my proposed solutions inline and ccÂ¹d the siprec working group
> >> so others can validate and raise any concerns.
> >> 
> >> On 5/14/15, 5:43 PM, "Pearl Liang via RT" <drafts-lastcall@iana.org>
> >>wrote:
> >> 
> >> >(BEGIN IANA LAST CALL COMMENTS)
> >> >
> >> >IESG/Authors/WG Chairs:
> >> >
> >> >IANA has reviewed draft-ietf-siprec-protocol-16.  Authors should review
> >> >the comments and/or questions below.  Please report any inaccuracies
> >>and
> >> >respond to any questions as soon as possible.
> >> >
> >> >We received the following comments/questions from the IANA's reviewer:
> >> >
> >> >IANA has a couple questions about some of the actions requested in the
> >> >IANA Considerations section of this document.
> >> >
> >> >IANA understands that upon approval of this document, there are five
> >> >actions which IANA must complete.
> >> >
> >> >First, in the Option Tags subregistry of the Session Initiation
> >>Protocol
> >> >(SIP) Parameters registry located at:
> >> >
> >> >http://www.iana.org/assignments/sip-parameters/
> >> >
> >> >two new option tags will be added as follows:
> >> >
> >> >Name: siprec
> >> >Description: This option tag is for identifying the SIP session is for
> >> >the purpose of a recording session. This is typically not used in a
> >> >Supported header. When present in a Require header in a request, it
> >> >indicates that the UAS is either an SRC or SRS capable of handling a
> >> >recording session.
> >> >Reference: [ RFC-to-be ]
> >> >
> >> >Name: record-aware
> >> >Description: This option tag is to indicate the ability for the user
> >> >agent to receive recording indicators in media level or session level
> >> >SDP. When present in a Supported header, it indicates that the UA can
> >> >receive recording indicators in media level or session level SDP.
> >> >Reference: [ RFC-to-be ]
> >> >
> >> >Second, in the iso.org.dod.internet.features.sip-tree (1.3.6.1.8.4)
> >> >subregistry in the Media Feature Tags - iso.org.dod.internet.features
> >> >(1.3.6.1.8) registry located at:
> >> >
> >> >http://www.iana.org/assignments/media-feature-tags/
> >> >
> >> >two new Media Feature Tags are to be registered as follows:
> >> >
> >> >Decimal: [ TBD-at-Registration ]
> >> >Name: sip.src
> >> >Description: This feature tag indicates that the user agent is a
> >>Session
> >> >Recording Client for the purpose for Recording Session.
> >> >Reference: [ RFC-to-be ]
> >> >
> >> >Decimal: [ TBD-at-Registration ]
> >> >Name: sip.srs
> >> >Description: This feature tag indicates that the user agent is a
> >>Session
> >> >Recording Server for the purpose for Recording Session.
> >> >Reference: [ RFC-to-be ]
> >> >
> >> >IANA notes that the authors suggest 25 and 26 for the Decimal values
> >>for
> >> >these registrations.
> >> >
> >> >QUESTION: Both 25 and 26 have been assigned.  The authors should remove
> >> >the values from section 11.2.  IANA suggested to use TBD place holder
> >>to
> >> >avoid 
> >> >this sort of conflicts.
> >> 
> >> 
> >> I will replace with 25 and 26 each with Â³[ TBD-at-Registration ]Â².
> >> 
> >> 
> >> >
> >> >Third, in the Content Disposition Parameters subregistry of the Content
> >> >Disposition Values and Parameters registry located at:
> >> >
> >> >http://www.iana.org/assignments/cont-disp/
> >> >
> >> >a new content-disposition parameter is to be registered as followed:
> >> >
> >> >Name: recording-session
> >> >Description: metadata about the recording session or reason for
> >>metadata
> >> >snapshot request
> >> >Reference: [ RFC-to-be ]
> >> >
> >> >Fourth, in the application subregistry of the Media Types registry
> >> >located at:
> >> >
> >> >http://www.iana.org/assignments/media-types/
> >> >
> >> >a new media type will be registered as follows:
> >> >
> >> >Name: rs-metadata-request
> >> >Template: [ TBD-at-registration ]
> >> >Reference: [ RfC-to-be ]
> >> >
> >> >Fifth:
> >> >
> >> >IANA Question --> the next request to IANA requests that two new SDP
> >> >attributes be registered but for the type says (for both) that the type
> >> >should be "session or media level." Do the authors mean session AND
> >>media
> >> >level, or do they mean something else?   As this document requests
> >> >registrations in a Specification Required registry, the authors need to
> >> >clarify the request before we can initiate the required Expert Review.
> >> >Expert review will need to be completed before your document can be
> >> >approved for publication as an RFC.
> >> 
> >> 
> >> Please register these two new SDP attributes as both session level
> >> attributes and as media level attributes.
> >> 
> >
> >So, both new attributes are used as both session AND media level.
> >We will submit this to Expert Review.
> >
> >Thanks,
> >~pl
> >
> >
> >> >
> >> >In a registry to be identified later (see IANA Question above), located
> >> >at:
> >> >
> >> >http://www.iana.org/assignments/sdp-parameters/
> >> >
> >> >two new SDP Parameters are to be registered as follows:
> >> >
> >> >Type: record
> >> >SDP Name: Recording Indication
> >> >Reference: [ RFC-to-be ]
> >> >
> >> >Type: recordpref
> >> >SDP Name: Recording Preference
> >> >Reference: [ RFC-to-be ]
> >> >
> >> >IANA understands that these five actions are the only ones required to
> >>be
> >> >completed upon approval of this document.
> >> >
> >> >Note:  The actions requested in this document will not be completed
> >>until
> >> >the document has been approved for publication as an RFC. This message
> >>is
> >> >only to confirm what actions will be performed.
> >> >
> >> >Please note that IANA cannot reserve specific values. However, early
> >> >allocation is available for some types of registrations. For more
> >> >information, please see RFC 7120.
> >> >
> >> >Thanks,
> >> >
> >> >Pearl Liang
> >> >ICANN
> >> >
> >> >(END IANA LAST CALL COMMENTS)
> >> 
> >> Cheers,
> >> Charles
> >> 
> >> >
> >> >
> >> >On Fri May 01 23:40:02 2015, iesg-secretary@ietf.org wrote:
> >> >> 
> >> >> The IESG has received a request from the SIP Recording WG (siprec) to
> >> >> consider the following document:
> >> >> - 'Session Recording Protocol'
> >> >>   <draft-ietf-siprec-protocol-16.txt> as Proposed Standard
> >> >> 
> >> >> The IESG plans to make a decision in the next few weeks, and solicits
> >> >> final comments on this action. Please send substantive comments to
> >>the
> >> >> ietf@ietf.org mailing lists by 2015-05-15. Exceptionally, comments
> >>may
> >> >>be
> >> >> sent to iesg@ietf.org instead. In either case, please retain the
> >> >> beginning of the Subject line to allow automated sorting.
> >> >> 
> >> >> Abstract
> >> >> 
> >> >> 
> >> >>    This document specifies the use of the Session Initiation Protocol
> >> >>    (SIP), the Session Description Protocol (SDP), and the Real Time
> >> >>    Protocol (RTP) for delivering real-time media and metadata from a
> >> >>    Communication Session (CS) to a recording device.  The Session
> >> >>    Recording Protocol specifies the use of SIP, SDP, and RTP to
> >> >>    establish a Recording Session (RS) between the Session Recording
> >> >>    Client (SRC), which is on the path of the CS, and a Session
> >>Recording
> >> >>    Server (SRS) at the recording device.  This document considers
> >>only
> >> >>    active recording, where the SRC purposefully streams media to an
> >>SRS
> >> >>    and all participating user agents are notified of the recording.
> >> >>    Passive recording, where a recording device detects media directly
> >> >>    from the network (e.g., using port-mirroring techniques), is
> >>outside
> >> >>    the scope of this document.  In addition, lawful intercept is
> >>outside
> >> >>    the scope of this document.
> >> >> 
> >> >> 
> >> >> 
> >> >> 
> >> >> The file can be obtained via
> >> >> https://datatracker.ietf.org/doc/draft-ietf-siprec-protocol/
> >> >> 
> >> >> IESG discussion can be tracked via
> >> >> https://datatracker.ietf.org/doc/draft-ietf-siprec-protocol/ballot/
> >> >> 
> >> >> 
> >> >> The following IPR Declarations may be related to this I-D:
> >> >> 
> >> >>    https://datatracker.ietf.org/ipr/1912/
> >> >> 
> >> >> 
> >> >> 
> >> >
> >> >
> >> 
> >
> >
> 


