Re: [TLS] I-D Action:draft-ietf-tls-dtls-heartbeat-01.txt

Sean Turner <turners@ieca.com> Tue, 01 February 2011 14:27 UTC

Return-Path: <turners@ieca.com>
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64C2B3A6CDE for <tls@core3.amsl.com>; Tue, 1 Feb 2011 06:27:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.092
X-Spam-Level:
X-Spam-Status: No, score=-102.092 tagged_above=-999 required=5 tests=[AWL=-0.394, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HO2DlsisPlMF for <tls@core3.amsl.com>; Tue, 1 Feb 2011 06:27:49 -0800 (PST)
Received: from nm6.bullet.mail.ac4.yahoo.com (nm6.bullet.mail.ac4.yahoo.com [98.139.52.203]) by core3.amsl.com (Postfix) with SMTP id 2075F3A6BA3 for <tls@ietf.org>; Tue, 1 Feb 2011 06:27:49 -0800 (PST)
Received: from [98.139.52.194] by nm6.bullet.mail.ac4.yahoo.com with NNFMP; 01 Feb 2011 14:31:03 -0000
Received: from [98.139.52.176] by tm7.bullet.mail.ac4.yahoo.com with NNFMP; 01 Feb 2011 14:31:03 -0000
Received: from [127.0.0.1] by omp1059.mail.ac4.yahoo.com with NNFMP; 01 Feb 2011 14:31:03 -0000
X-Yahoo-Newman-Id: 634141.79106.bm@omp1059.mail.ac4.yahoo.com
Received: (qmail 52329 invoked from network); 1 Feb 2011 14:31:03 -0000
Received: from thunderfish.local (turners@96.241.4.28 with plain) by smtp112.biz.mail.re2.yahoo.com with SMTP; 01 Feb 2011 06:31:03 -0800 PST
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
X-YMail-OSG: io4DEQcVM1mtP4J.AJHG1QzTTodFLHeljwMof7HrWVeFkkR 5Lz_n4bOl7RT35xz7Jw5jXbQh38QO33SDjffWE9Xe224UBsMfDGI1P27MnAI hFmDIQms7Qvc4zIkwLtD6zn1mE58mfd_uxx5pnoVyWWT8zU9cRN5ktqNCQ.B Bpr5_TNJnWp7ygn35xanNuMoMeXv6emESRmFBLxOANVoI86b9BxhC_.CNmZS BJG3P6BELDTCdtJKUZcuyhBl5HXXe6dLcJ_lwZ73JesUUBaPIlT59Ps8MI9h JC_jhc7PtX_adf4XK0R7b7S2E1mdCdN1Nna7L
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4D481926.6090409@ieca.com>
Date: Tue, 01 Feb 2011 09:31:02 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
References: <20110127114502.24680.73782.idtracker@localhost><8239oeqz6c.fsf@mid.bfk.de> <4848B682-273F-4B52-B9E2-ACBFDFDAAB7F@lurchi.franken.de> <00cf01cbc1f4$dc962700$4001a8c0@gateway.2wire.net>
In-Reply-To: <00cf01cbc1f4$dc962700$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: tls@ietf.org
Subject: Re: [TLS] I-D Action:draft-ietf-tls-dtls-heartbeat-01.txt
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 14:27:50 -0000

On 2/1/11 4:23 AM, t.petch wrote:
> ----- Original Message -----
> From: "Michael Tüxen"<Michael.Tuexen@lurchi.franken.de>
> To: "Florian Weimer"<fweimer@bfk.de>
> Cc:<tls@ietf.org>
> Sent: Thursday, January 27, 2011 2:49 PM
>
> On Jan 27, 2011, at 2:00 PM, Florian Weimer wrote:
>
>>> This document describes the Heartbeat Extension for the Transport
>>> Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
>>> protocol.
>>
>> I think this paragraph
>>
>> | There MUST NOT be more than one HeartbeatRequest message in flight
>> | at a time.
>>
>> should be changed to:
>>
>> | Retransmissions MUST use the same payload as the original
>> | HeartbeatRequest message.
> The intention of the sentence in the ID is that you can not send
> multiple HeartbeatRequest out. This could overload the network since
> DTLS uses transport layers which do not necessary provide a congestion
> control. That is why you can only have one request in flight.
> Please note that it is not in flight anymore if the corresponding
> HeartbeatReply has been received or the retransmission timer fires.
>
> Michael
>
> My experience of the IESG is that they will insist on a paragraph about
> Congestion Control (lack of) and mitigation thereof.  At the same time,
> I find it very hard to know what words will satisfy them; my most recent
> experience was with RFC6012, albeit a more complex scenario.
>
> Tom Petch

I suspect that the transport ADs' interest will be piqued the minute 
they read the words: mtu ;)  The best thing to do is to ask for an early 
review from tsv-dir@ietf.org.  I'm willing to send it over if you'd like?

This is my bad, because I haven't yet figured out what magic incantation 
needs to go in drafts to appease the transport (and probably internet 
area) ADs.

spt

>>
>> The original requirement seems to be pretty much unimplementable
>> because of transport layer characteristics.
> Not sure what problem you are thinking about.
> An implementation of the ID for OpenSSL is available at
> http://sctp.fh-muenster.de/dtls-patches.html
>
> Best regards
> Michael
>>
>> --
>> Florian Weimer<fweimer@bfk.de>
>> BFK edv-consulting GmbH       http://www.bfk.de/
>> Kriegsstraße 100              tel: +49-721-96201-1
>> D-76133 Karlsruhe             fax: +49-721-96201-99
>> _______________________________________________
>> TLS mailing list
>> TLS@ietf.org
>> https://www.ietf.org/mailman/listinfo/tls
>>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>