Re: [rtcweb] No Interim on SDES at this juncture

Hadriel Kaplan <> Wed, 12 June 2013 16:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6234321F93C4 for <>; Wed, 12 Jun 2013 09:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.578
X-Spam-Status: No, score=-6.578 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 50j6eGdItWmH for <>; Wed, 12 Jun 2013 09:29:15 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 1B3DC21F91B7 for <>; Wed, 12 Jun 2013 09:29:12 -0700 (PDT)
Received: from ( []) by (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r5CGTAZ0007537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 12 Jun 2013 16:29:11 GMT
Received: from ( []) by (8.14.4+Sun/8.14.4) with ESMTP id r5CGT9BQ026845 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jun 2013 16:29:10 GMT
Received: from ( []) by (8.14.4+Sun/8.14.4) with ESMTP id r5CGT9Mh024632; Wed, 12 Jun 2013 16:29:09 GMT
Received: from [] (/ by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 12 Jun 2013 09:29:09 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_56605741-7CC2-46C1-9DC2-82E913F319CA"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Hadriel Kaplan <>
In-Reply-To: <>
Date: Wed, 12 Jun 2013 12:29:08 -0400
Message-Id: <>
References: <> <> <>
To: Ted Hardie <>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: []
Subject: Re: [rtcweb] No Interim on SDES at this juncture
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, 12 Jun 2013 16:29:22 -0000

On Jun 12, 2013, at 11:38 AM, Ted Hardie <> wrote:

> On Tue, Jun 11, 2013 at 7:25 PM, Hadriel Kaplan <> wrote:
> Oh excellent, then it's a "No Plan" for SRTP as well.  Cool.
> Hi Hadriel,
> Actually this isn't correct.  The plan of record for this is DTLS/SRTP:
> If you think that plan isn't clear enough in the security architecture and security documents, 
> suggested text would be welcome.  The point of an SDES discussion wasn't to create an 
> initial plan, in other words, or event to discuss changing the existing plan, but to consider 
> whether other options were to be included.

What we had talked about back in IETF 83 (or some previous meeting) was whether DTLS-SRTP would be the only MTI key exchange, or whether SDES would also be MTI.
We did not come to consensus in IETF 83, and tabled it for more discussion.  Since then it has been put at the end of the agendas, resulting in us running out of time for it.  At the last IETF 86 or Boston interim, one of the WG Chairs (I don't remember who) said we'd have a virtual interim dedicated to cover it.  Now we don't.  Ergo, we don't have a plan.

> We haven't set an agenda for Berlin, but the obvious thing to do here is not to wait, but to kick of the discussion on the list with a draft proposing what you want to see; or, as I said below "Working group discussion on the point, and documents addressing it, are welcome at this point, if folks do want to re-open the topic in this venue. "

We've had a lot of discussions on the list about this over the past couple years.  I thought the general feeling was at this point we needed to discuss it live - either in person or on a con call - because it was hard to follow all the arguments in email.  Maybe that was just my feeling, but I could swear some other people said the same thing at the last IETF 86 meeting or Boston interim.