Re: [bfcpbis] BFCP over DTLS
Alan Ford <alanford@cisco.com> Wed, 30 May 2012 11:53 UTC
Return-Path: <alanford@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B952B21F86AD for <bfcpbis@ietfa.amsl.com>; Wed, 30 May 2012 04:53:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.157
X-Spam-Level:
X-Spam-Status: No, score=-8.157 tagged_above=-999 required=5 tests=[AWL=1.842, BAYES_00=-2.599, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_HI=-8]
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 xlT7KPGmL+xu for <bfcpbis@ietfa.amsl.com>; Wed, 30 May 2012 04:53:51 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id BD08421F86A3 for <bfcpbis@ietf.org>; Wed, 30 May 2012 04:53:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=alanford@cisco.com; l=1502; q=dns/txt; s=iport; t=1338378830; x=1339588430; h=date:subject:from:to:message-id:in-reply-to:mime-version: content-transfer-encoding; bh=ImuIpuVrENqZ7sqJDtK3+O+yT7wKvNrAz7Otj4SOXbQ=; b=JaDjaLgnyId+CmyEkKbTFjUi8dONrGw8QoKyVh3UyB+VwGwBd9u4Kb5d SA5xl4X1MBcR3yrYiQfX0B3YnXaAzycwtqBfdQA7W7fHcKYX3V4PxGEz6 wxZtK3E3uqdH7Ynmx707CPG1WoZdJ65epfoRXaNUSrOzkhpKk5AeJmSZb o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAJsJxk+Q/khR/2dsb2JhbABEtA2BB4IXAQEBAwEBAQEPAScCATEQDQEIDlkGMAEBBAESIodbAwYFC5kUlkANiUoEiiRhhUIDlRiKeIMVgWaCYQ
X-IronPort-AV: E=Sophos;i="4.75,683,1330905600"; d="scan'208";a="5146108"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 30 May 2012 11:53:49 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q4UBrnrs004310; Wed, 30 May 2012 11:53:49 GMT
Received: from xmb-ams-203.cisco.com ([144.254.75.14]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 30 May 2012 13:53:49 +0200
Received: from 10.55.89.253 ([10.55.89.253]) by XMB-AMS-203.cisco.com ([144.254.75.14]) with Microsoft Exchange Server HTTP-DAV ; Wed, 30 May 2012 11:53:48 +0000
User-Agent: Microsoft-Entourage/12.33.0.120411
Date: Wed, 30 May 2012 12:53:48 +0100
From: Alan Ford <alanford@cisco.com>
To: Woo Johnman <wuym2000cn@gmail.com>, bfcpbis@ietf.org
Message-ID: <CBEBC8DC.A448%alanford@cisco.com>
Thread-Topic: [bfcpbis] BFCP over DTLS
Thread-Index: Ac0+Wt9sGmIB8V5ajkO1FRnf/5rJCg==
In-Reply-To: <CAMxBvpB0pnr4Rr31m=mrypiXBJxZjk2bCvroguWAvXxzPRKjiQ@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 30 May 2012 11:53:49.0438 (UTC) FILETIME=[E04799E0:01CD3E5A]
Subject: Re: [bfcpbis] BFCP over DTLS
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2012 11:53:51 -0000
Hi, Yes, there should indeed be a reference to RFC6347 for DTLS in Section 7. The line referencing [7] says: For a UDP/ DTLS connection established using the same exchange, either party can be the DTLS server depending on the setup attributes exchanged, as defined in [7]. This is referring to the use of the DTLS setup attributes (a=setup) in the SDP, which is discussed in [7] (Section 7.1). It definitely does not suggest the use of SRTP. I guess it could be a bit clearer in the text; the updates in 4572bis also touch on this. Regards, Alan On 30/05/2012 10:35, "Woo Johnman" <wuym2000cn@gmail.com> wrote: > Hi, > I feel BFCP over DTLS is not well documented in rfc4582bis. > At section 7 "Lower-Layer Security". > It says "BFCP floor control servers > and clients MUST support TLS for transport over TCP and MUST support DTLS > for > transport over UDP [4]." But reference [4] is only about BFCP over TLS. > Reference for BFCP over DTLS seems missing. > At the end of the same section,it seems say DTLS connection setup > procedure shall > follow [7]. If it is true, does it mean BFCP message is packeted as > SRTP? If not, would it be better to > give more details about DTLS connection setup and packetization. > > Please give more explain. > > Thanks in advance, > > Youngmin > _______________________________________________ > bfcpbis mailing list > bfcpbis@ietf.org > https://www.ietf.org/mailman/listinfo/bfcpbis
- [bfcpbis] BFCP over DTLS Woo Johnman
- Re: [bfcpbis] BFCP over DTLS Alan Ford
- Re: [bfcpbis] BFCP over DTLS Tom Kristensen