Re: [bfcpbis] BFCP-UDP and DTLS

Tom Kristensen <tomkrist@cisco.com> Wed, 19 December 2012 10:45 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 E211621F894D for <bfcpbis@ietfa.amsl.com>; Wed, 19 Dec 2012 02:45:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level:
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kBitFmpSMXqQ for <bfcpbis@ietfa.amsl.com>; Wed, 19 Dec 2012 02:45:19 -0800 (PST)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 14D9721F87F2 for <bfcpbis@ietf.org>; Wed, 19 Dec 2012 02:45:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2888; q=dns/txt; s=iport; t=1355913919; x=1357123519; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=OeGF8JuSuW1WdxaclxvJAvG4owuMj4ft5mgq7zLEuks=; b=SuVZTrjT09K7TsYn7MV0lDnmcuP+tCtHWCCv5ryV/1zS3AcIlN4zro0w eTlP13B1xHCMPPKVDqeEjEV/BePoOuESiL+8tu4JHt57orVjD8avGBZmc ujsQcchNrmTRqllhZgh8ZAuQp2JjfkD5xnMM1lXhNh/sCha7Cms5qIhja U=;
X-IronPort-AV: E=Sophos;i="4.84,316,1355097600"; d="scan'208";a="10577801"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 19 Dec 2012 10:45:17 +0000
Received: from [10.47.38.141] ([10.47.38.141]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id qBJAjGTn005358; Wed, 19 Dec 2012 10:45:17 GMT
Message-ID: <50D19ABC.6040303@cisco.com>
Date: Wed, 19 Dec 2012 11:45:16 +0100
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: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B047F4F@ESESSMB209.ericsson.se> <50B62146.2050707@cisco.com> <92B7E61ADAC1BB4F941F943788C08828046CC03E@xmb-aln-x08.cisco.com>
In-Reply-To: <92B7E61ADAC1BB4F941F943788C08828046CC03E@xmb-aln-x08.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Subject: Re: [bfcpbis] BFCP-UDP and 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, 19 Dec 2012 10:45:20 -0000

Thanks, I've added reference to RFC 5764, Section 6.7 in Section 6.2.4, 
at end of this second paragraph:

<t>In order to facilitate the initial establishment of NAT bindings, and 
to maintain those bindings once established, BFCP entities using 
unreliable transport are RECOMMENDED to use STUN <xref 
target="RFC5389"/> Binding Indication for keep-alives, as described for 
ICE <xref target="RFC5245"/>. <xref target="RFC5763"/>, Section 6.7 
provides useful recommendations for middlebox interaction when DTLS is 
used.</t>

-- Tom

On 11/28/2012 10:49 PM, Charles Eckel (eckelcu) wrote:
> (as an individual)
> Adding a reference to 6.7.2 of RFC 5763 sounds like a good idea to me, and I agree that rfc4582bis is probably a more appropriate place for this than rfc4583bis.
>
> Cheers,
> Charles
>
>    
>> -----Original Message-----
>> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
>> Behalf Of Tom Kristensen (tomkrist)
>> Sent: Wednesday, November 28, 2012 6:36 AM
>> To: bfcpbis@ietf.org
>> Subject: Re: [bfcpbis] BFCP-UDP and DTLS
>>
>> Thanks Christer,
>>
>> In the upcoming version of rfc4583bis, the usage of the RFC 4145 'setup' will
>> be described (in Section 8). This attribute was just mentioned in rfc4582bis
>> until now.
>>
>> In rfc4582bis we say: "In order to facilitate the initial establishment of NAT
>> bindings, and to maintain those bindings once established, BFCP entities
>> using unreliable transport are RECOMMENDED to use STUN<xref
>> target="RFC5389"/>  Binding Indication for keep-alives, as described for ICE
>> <xref target="RFC5245"/>."
>>
>> However, we may refer to Section 6.7 (and especially 6.7.2) as well, but that
>> may belong to rfc4582bis (where usage of STUN binding indications are
>> recommended) instead of rfc4583bis?
>>
>> -- Tom
>>
>> On 11/28/2012 09:55 AM, Christer Holmberg wrote:
>>
>> 	Hi,
>>
>>
>>
>> 	I haven't really been following the BFCPbis work, so I appologize if
>> the following has been discussed.
>>
>>
>>
>> 	draft-ietf-bfcpbis-rfc4583bis-03 refers to section 5 of RFC 5763 for
>> the SDP Offer/Answer procedures, and DTLS role selection (TLS
>> client/server).
>>
>>
>>
>> 	However, I think it would also be good to refer to section 6.7 of RFC
>> 5763. Especially section 6.7.2 is important, in my view. It says that the
>> passive UA sends a STUN request, in order to open the NAT pin hole, which
>> means both UAs don't have to be active if they are behind NATs, and don't
>> support ICE. Otherwise it could cause problem, if both are active and end up
>> acting as TLS clients.
>>
>>
>>
>> 	Regards,
>>
>>
>>
>> 	Christer
>>
>>
>>
>> 	_______________________________________________
>> 	bfcpbis mailing list
>> 	bfcpbis@ietf.org
>> 	https://www.ietf.org/mailman/listinfo/bfcpbis
>>
>>
>>      
>
>