Return-Path: X-Original-To: rtcweb@ietfa.amsl.com Delivered-To: rtcweb@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3768B21F8793 for ; Wed, 2 Oct 2013 13:32:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id paekQY-Vq--3 for ; Wed, 2 Oct 2013 13:32:12 -0700 (PDT) Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id B53AC21F8E21 for ; Wed, 2 Oct 2013 13:31:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1380745917; x=1412281917; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=6kLlxF4r10V7WbsEbM0jSI5Gv5EyDSchVDdwrg9Rpa0=; b=ZxRjs8QvErwnRLv+PgUZi4ZR4GItNEZMpcH8BCOCcDOkM3dK9o170BIP lgJ0rS+XUXLPIWqQJmriQscRsdkjZSHFp++Lv85alAykirNXaK3jDZ7tZ MrnKiqpGg4mic2wobhy3PY64OA1WKTVUGK8zFqLCJiMV1TBrlZE0cIhJZ k=; X-IronPort-AV: E=McAfee;i="5400,1158,7215"; a="77814380" Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine01.qualcomm.com with ESMTP; 02 Oct 2013 13:31:57 -0700 X-IronPort-AV: E=McAfee;i="5400,1158,7215"; a="521035518" Received: from nasanexhc10.na.qualcomm.com ([172.30.48.3]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 02 Oct 2013 13:31:57 -0700 Received: from NASANEXD01H.na.qualcomm.com ([169.254.8.8]) by nasanexhc10.na.qualcomm.com ([172.30.48.3]) with mapi id 14.03.0158.001; Wed, 2 Oct 2013 13:31:56 -0700 From: "Mandyam, Giridhar" To: Harald Alvestrand , Parthasarathi R Thread-Topic: [rtcweb] SRTP/AVPF/TCP in draft-ietf-rtcweb-transports-01 Thread-Index: Ac6/lnkAhKE72RhfQdaR3bEfZ6NwEgAUOoEAAA5cARA= Date: Wed, 2 Oct 2013 20:31:57 +0000 Message-ID: References: <006401cebf96$7db7a4f0$7926eed0$@co.in> <524C7FD8.1050801@alvestrand.no> In-Reply-To: <524C7FD8.1050801@alvestrand.no> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.45.230.6] Content-Type: multipart/alternative; boundary="_000_CAC8DBE4E9704C41BCB290C2F3CC921A165B77DAnasanexd01hnaqu_" MIME-Version: 1.0 Cc: "rtcweb@ietf.org" Subject: Re: [rtcweb] SRTP/AVPF/TCP in draft-ietf-rtcweb-transports-01 X-BeenThere: rtcweb@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Real-Time Communication in WEB-browsers working group list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2013 20:32:22 -0000 --_000_CAC8DBE4E9704C41BCB290C2F3CC921A165B77DAnasanexd01hnaqu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Does RFC 6544 work (http://tools.ietf.org/html/rfc6544) for a normative ref= erence on SRTP/AVP over TCP? -Giri From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of= Harald Alvestrand Sent: Wednesday, October 02, 2013 1:20 PM To: Parthasarathi R Cc: rtcweb@ietf.org Subject: Re: [rtcweb] SRTP/AVPF/TCP in draft-ietf-rtcweb-transports-01 On 10/02/2013 07:40 PM, Parthasarathi R wrote: Hi Harald, Could you please let me know the specification which indicates SRTP/AVPF/TC= P profile in Sec 2.2 of draft-ietf-rtcweb-transports-01. Thanks Partha That's a good question! http://tools.ietf.org/html/rfc4571 defines TCP/RTP/AVP, but there doesn't s= eem to be a corresponding defintion for SRTP/AVPF over TCP. Neither is the RFC 4571 profile registered at IANA - I think both that and = the DTLS forms should have been at http://www.iana.org/assignments/rtp-para= meters/rtp-parameters.xhtml#rtp-parameters-7 - but this registry seems so s= hort, I wonder if I'm missing something. -- Surveillance is pervasive. Go Dark. --_000_CAC8DBE4E9704C41BCB290C2F3CC921A165B77DAnasanexd01hnaqu_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Does RFC 6544 work (http://tools.ietf.org/html/rfc654= 4) for a normative reference on SRTP/AVP over TCP?

-Giri

 <= /p>

From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ie= tf.org] On Behalf Of Harald Alvestrand
Sent: Wednesday, October 02, 2013 1:20 PM
To: Parthasarathi R
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] SRTP/AVPF/TCP in draft-ietf-rtcweb-transports-= 01

 

On 10/02/2013 07:40 PM, Parthasarathi R wrote:<= /o:p>

Hi Harald,
 
Could you please let me know the specification which indicates SRTP/AV=
PF/TCP
profile in Sec 2.2 of draft-ietf-rtcweb-transports-01. 

 


Thanks


Partha


 

That's a good question!

http://tools.ietf.org/html/r= fc4571 defines TCP/RTP/AVP, but there doesn't seem to be a correspondin= g defintion for SRTP/AVPF over TCP.

Neither is the RFC 4571 profile registered at IANA - I think both that and = the DTLS forms should have been at http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-par= ameters-7 - but this registry seems so short, I wonder if I'm missing s= omething.


-- 
Surveillance is pervasive. Go Dark.
--_000_CAC8DBE4E9704C41BCB290C2F3CC921A165B77DAnasanexd01hnaqu_--