Re: [bfcpbis] rfc4583bis TLS SDP example - Re: More comments on RFC 4582

Tom Kristensen <tomkrist@cisco.com> Wed, 06 June 2012 08:32 UTC

Return-Path: <tomkrist@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 6F3DD21F8853 for <bfcpbis@ietfa.amsl.com>; Wed, 6 Jun 2012 01:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.459
X-Spam-Level:
X-Spam-Status: No, score=-9.459 tagged_above=-999 required=5 tests=[AWL=-0.660, BAYES_00=-2.599, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_57=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 5hVbMUtOr2id for <bfcpbis@ietfa.amsl.com>; Wed, 6 Jun 2012 01:32:52 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 7A24E21F8852 for <bfcpbis@ietf.org>; Wed, 6 Jun 2012 01:32:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=tomkrist@cisco.com; l=2836; q=dns/txt; s=iport; t=1338971572; x=1340181172; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=5/WcxpA3H0Jg5xsUdJw38EbGJBcdx1NQrJxlYaqr8Q8=; b=W5e3tMCbMUkUGylKK9saFauPOHoHqo8EszD1KYQDy1yV7aBh0VUZ9aj8 2/GZ1RbtCapfwR4N2Iz/fWNPcPyJx7DSuWGPqbx9tGsOCMiBbX8G7t+D+ rgZRRZ3Wj0HA0xdeBfTs+YN6UIAhihO5aDfsRZx2t8odHnieO69KuVRN1 g=;
X-IronPort-AV: E=Sophos;i="4.75,723,1330905600"; d="scan'208";a="5433138"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 06 Jun 2012 08:32:51 +0000
Received: from [10.55.82.232] (dhcp-10-55-82-232.cisco.com [10.55.82.232]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q568WpBT003331; Wed, 6 Jun 2012 08:32:51 GMT
Message-ID: <4FCF15B2.1010008@cisco.com>
Date: Wed, 06 Jun 2012 10:32:50 +0200
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: Tom Kristensen <tomkrist@cisco.com>
References: <20120604131529.133a66fa@lminiero-acer><4FCCB52E.5010109@cisco.com><A997DBD5DD3E0B46A6D0353CF3E32CCB0FE3D87D@xmb-sjc-233.amer.cisco.com> <4FCD9EF5.80106@cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C073873E7@xmb-sjc-234.amer.cisco.com> <4FCEEF8F.1090903@cisco.com>
In-Reply-To: <4FCEEF8F.1090903@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: bfcpbis@ietf.org, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Chelliah Sivachelvan (chelliah)" <chelliah@cisco.com>
Subject: Re: [bfcpbis] rfc4583bis TLS SDP example - Re: More comments on RFC 4582
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, 06 Jun 2012 08:32:53 -0000

Just for the record:
Will change Charles' UDP/DTLS/BFCP in the example below ==> UDP/TLS/BFCP.

-- Tom

On 06/06/2012 07:50 AM, Tom Kristensen wrote:
> Sure, a good idea to add an accompanying DTLS example. If no 
> objections are received, this will be part of the next version of the 
> draft.
>
> -- Tom
>
> On 06/05/2012 07:19 PM, Charles Eckel (eckelcu) wrote:
>> I agree, however, perhaps it would be useful to add a second example in
>> which an endpoint initiates the offer and uses DTLS; e.g.:
>>
>> Offer from client:
>>
>>     m=application 50000 UDP/DTLS/BFCP *
>>     a=setup:actpass
>>     a=fingerprint:SHA-1 \
>>          4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
>>     a=floorctrl:c-only, s-only
>>     a=confid:4321
>>     a=userid:1234
>>     a=floorid:1 mstrm:10
>>     a=floorid:2 mstrm:11
>>     m=audio 50002 RTP/AVP 0
>>     a=label:10
>>     m=video 50004 RTP/AVP 31
>>     a=label:11
>>
>> The following is the answer returned by the server.
>>
>>     m=application 9 UDP/DTLS/BFCP *
>>     a=setup:active
>>     a=fingerprint:SHA-1 \
>>          3D:B4:7B:E3:CC:FC:0D:1B:5D:31:33:9E:48:9B:67:FE:68:40:E8:21
>>     a=floorctrl:s-only
>>     a=confid:4321
>>     a=userid:1234
>>     a=floorid:1 mstrm:10
>>     a=floorid:2 mstrm:11
>>     m=audio 55000 RTP/AVP 0
>>     m=video 55002 RTP/AVP 31
>>
>> Cheers,
>> Charles
>>
>>> -----Original Message-----
>>> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
>>> Behalf Of Tom Kristensen (tomkrist)
>>> Sent: Monday, June 04, 2012 10:54 PM
>>> To: Chelliah Sivachelvan (chelliah)
>>> Cc: Lorenzo Miniero; bfcpbis@ietf.org; Tom Kristensen; Gonzalo
>>> Camarillo
>>> Subject: [bfcpbis] rfc4583bis TLS SDP example - Re: More comments on
>>> RFC 4582
>>>
>>> On 06/04/2012 04:22 PM, Chelliah Sivachelvan (chelliah) wrote:
>>>> Tom,
>>>>
>>>> A minor comment on the SDP example in section 9. In the context of
>>> DTLS,
>>>> the setup a line must be "actpass" in the offer. See excerpts from
>>> RFC
>>>> 5763:
>>>>
>>>>        [ The endpoint that is the offerer MUST use the setup
>> attribute
>>>>         value of setup:actpass and be prepared to receive a
>>> client_hello
>>>>         before it receives the answer.]
>>>>
>>> Yes, this is true for DTLS usage (UDP/TLS/BFCP). However, the example
>>> is
>>> the original example from RFC 4582 related to TLS (TCP/TLS/BFCP). So I
>>> believe the example in rfc4583bis is correct!
>>>
>>> -- Tom
>>> _______________________________________________
>>> bfcpbis mailing list
>>> bfcpbis@ietf.org
>>> https://www.ietf.org/mailman/listinfo/bfcpbis
>
> _______________________________________________
> bfcpbis mailing list
> bfcpbis@ietf.org
> https://www.ietf.org/mailman/listinfo/bfcpbis
>