IETF Logo Mail Archive

Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples

Roman Shpount <roman@telurix.com> Fri, 13 March 2015 20:56 UTC

Return-Path: <roman@telurix.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35BC91A879E for <rtcweb@ietfa.amsl.com>; Fri, 13 Mar 2015 13:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 cZbjyTYhSBd7 for <rtcweb@ietfa.amsl.com>; Fri, 13 Mar 2015 13:56:49 -0700 (PDT)
Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) (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 B077A1A037D for <rtcweb@ietf.org>; Fri, 13 Mar 2015 13:56:49 -0700 (PDT)
Received: by iecvj10 with SMTP id vj10so122042634iec.0 for <rtcweb@ietf.org>; Fri, 13 Mar 2015 13:56:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=kzO4nYOcVkNgN+nK4R7sjxvQ6IO4LxRCBqEuumhkadw=; b=bquFpi5ZuM3yiM6n8hYfoch/+lOsKSHdKvcC8hUwY7N9PPmIJvmtKes0Sjrybhl5M/ saXgdTHlPXydsEvZsWLd5xkjJduvgtMtLKIRs05vtEMj3k+5B5GvdHf/VNBJyRoB8zDH Fp08zNZlNjr1GWJ7U0lEXAZjlrW2uwJzVeMvBgaTHwyVjRWo3JqjQ0+IuFf5aL43uAoj eJCMOY3541cZmVUu8Oitgm6C3KPdxIwxUn0gmbwHl6dowE4qt+Gah7QdDCoAJsDvv9K+ eNyoaKrQAFRiufUtJhXB4h5/2ysWCKsTF1aqX6vQ4vnnCKlJCaPDDonAKY8x1iuo5iki Ph9w==
X-Gm-Message-State: ALoCoQkvtFEVhai09a7WOVoMv/+KInBASXuKmupyfIegu97FlG3LQRdHJUPVbIlImlyRHOb83+QM
X-Received: by 10.107.9.213 with SMTP id 82mr71277254ioj.57.1426280205891; Fri, 13 Mar 2015 13:56:45 -0700 (PDT)
Received: from mail-ie0-f177.google.com (mail-ie0-f177.google.com. [209.85.223.177]) by mx.google.com with ESMTPSA id j87sm1959034iod.21.2015.03.13.13.56.44 for <rtcweb@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Mar 2015 13:56:44 -0700 (PDT)
Received: by iegc3 with SMTP id c3so129464514ieg.3 for <rtcweb@ietf.org>; Fri, 13 Mar 2015 13:56:43 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.89.72 with SMTP id f8mr37721845icm.24.1426280201685; Fri, 13 Mar 2015 13:56:41 -0700 (PDT)
Received: by 10.36.20.10 with HTTP; Fri, 13 Mar 2015 13:56:41 -0700 (PDT)
In-Reply-To: <55034C0C.6070100@jive.com>
References: <54F74B02.1070902@jive.com> <7594FB04B1934943A5C02806D1A2204B1D7367A0@ESESSMB209.ericsson.se> <CALiegfmyp=v6thk4eLz7nL1BHh2Qj7jmC84tdG7ufg8HPXsVKA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D7369C9@ESESSMB209.ericsson.se> <CAD5OKxtCswToNzoZnnqJ5M66mjNjKJoA++WYNqN5155n+CWXsA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D736AC0@ESESSMB209.ericsson.se> <CAD5OKxs1grSqAG32mf__wtsjpo68jZmKonbd+EsJmYNsDHUbFQ@mail.gmail.com> <CAOJ7v-3YypG1s9KXOCA+Fo58SuVuUk5-thcSc0k3N2j=4ZmJoA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D737A76@ESESSMB209.ericsson.se> <CAD5OKxs+OEDp9pYrZHw237PfsNunao=PSC89dRhWiFcMwEQUXg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D739611@ESESSMB209.ericsson.se> <CAOJ7v-3bCxVP9fNuRFp_sVBXh4msnF1=fVZrefE0jejMzY8VQQ@mail.gmail.com> <5503147C.3060506@alvestrand.no> <CAOJ7v-23_H2jjgG6GrOd1MPv9M-iDbzsdF=L9e5xJsEbH=21PA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D73A2E9@ESESSMB209.ericsson.se> <55034C0C.6070100@jive.com>
Date: Fri, 13 Mar 2015 16:56:41 -0400
Message-ID: <CAD5OKxvHyYLw0guakUDfKCMzGfJSauv4axYi85-xwWR2nTsHLg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Simon Perreault <sperreault@jive.com>
Content-Type: multipart/alternative; boundary="90e6ba6147e2c5b5be051131bc13"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/gZeI5UbxyXmaJ5QbxN8lMEyPSv0>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] DTLS, DTLS-SRTP, and 5-tuples
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2015 20:56:51 -0000

On Fri, Mar 13, 2015 at 4:43 PM, Simon Perreault <sperreault@jive.com>
wrote:

> What we need is to explain why text in DTLS-SRTP that specifically talks
> about binding to a specific 5-tuple applies differently with ICE.
>
>
We need text that explains that RTP/RTCP, SRTP/SRTCP, DTLS and DTLS-SRTP
should not bind to a specific 5-tuple when running on top of ICE. We would
also need to explain the concept of the virtual transport channel created
by ICE. We will need to specify how specific 5-tuples get associated with
the same virtual transport. Anything else is of no immediate value. I
believe, the most appropriate place for this would be ICE-bis. One way of
doing this is to introduce the concept of "ICE compatible transports", list
the requirements, and specify transports currently supported as examples.
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email