[bfcpbis] (no subject)
Woo Johnman <wuym2000cn@gmail.com> Wed, 30 May 2012 09:31 UTC
Return-Path: <wuym2000cn@gmail.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 F2BC711E8083 for <bfcpbis@ietfa.amsl.com>; Wed, 30 May 2012 02:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.237
X-Spam-Level:
X-Spam-Status: No, score=-1.237 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_72=0.6, MISSING_SUBJECT=1.762, RCVD_IN_DNSWL_LOW=-1]
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 f70UAZam1xwZ for <bfcpbis@ietfa.amsl.com>; Wed, 30 May 2012 02:31:54 -0700 (PDT)
Received: from mail-qa0-f49.google.com (mail-qa0-f49.google.com [209.85.216.49]) by ietfa.amsl.com (Postfix) with ESMTP id 63A8E11E8079 for <bfcpbis@ietf.org>; Wed, 30 May 2012 02:31:54 -0700 (PDT)
Received: by qabj40 with SMTP id j40so2332653qab.15 for <bfcpbis@ietf.org>; Wed, 30 May 2012 02:31:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=X6BdrcaPrr3Og30so0IOvq02LDltZ4J/3FY/QcJI4Bs=; b=WcVkk2HWjSl6tR0SdVid22R9fnFCTqszdx6vuS7gme0ebt4oSEEtrrc9TZF0QdhW9o 1uYIkA11QtDZFTsEG5ljF3fbQD3s2OsWhrP5c6uMUzyr4mtl0pT0t60aLVnQ5bB/+pXw P1nLGxsB1KswXS3pzxtQT9szOAL+RohGuoPvVQAxgqLx+o/ISV67+5LaZ74R+7BtB16v 7JXSOGCQ4WGK325NOAFm5wome07aCys0/rWAfr+0ZC4B/H4qJvCG+HNohdTZpY4kkb5O iPB63vc+OxGMddUUuT9zAtSy2jSIquIpTFXtIfFAViX6L2DJBkmxb89qcPTQWO8Exvgo pggg==
MIME-Version: 1.0
Received: by 10.229.137.146 with SMTP id w18mr4371390qct.38.1338370313742; Wed, 30 May 2012 02:31:53 -0700 (PDT)
Received: by 10.229.239.19 with HTTP; Wed, 30 May 2012 02:31:53 -0700 (PDT)
Date: Wed, 30 May 2012 17:31:53 +0800
Message-ID: <CAMxBvpArA8HA5xMnGX-P=rdoUOGOEwCfAZTRcdaP-djcSac=Ug@mail.gmail.com>
From: Woo Johnman <wuym2000cn@gmail.com>
To: bfcpbis@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [bfcpbis] (no subject)
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 09:31:55 -0000
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] (no subject) Woo Johnman