Re: [DNSOP] Stephen Farrell's Discuss on draft-ietf-dnsop-edns-tcp-keepalive-05: (with DISCUSS and COMMENT)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 07 January 2016 14:52 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1C1B1A8AED; Thu, 7 Jan 2016 06:52:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MANGLED_WANT=2.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1KSb2YHeq99c; Thu, 7 Jan 2016 06:52:56 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B1CB1A8AEF; Thu, 7 Jan 2016 06:52:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 37BFBBE59; Thu, 7 Jan 2016 14:52:53 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BEi7rij3hqt3; Thu, 7 Jan 2016 14:52:53 +0000 (GMT)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 85C72BE58; Thu, 7 Jan 2016 14:52:52 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1452178373; bh=F9LZYiEZo9EMhupu/evbExMt2VQZ0UJkOP2yUuRce1U=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=UtTqUOekPAAgkpw0ejaMG9UVymKJZSVaLnQ++KibFa7htZk9uOm86JPuoXEHRY03v A2+j0q3bWPpFdl7T/20alrE/AoNWerc8CAOiewK4yji5Glvfs8oAWQ9M5FmA49nGA2 TghyhOuWVft83n3mnIlXMKPnRCCf4AfEI7YeznWs=
To: sara <sara@sinodun.com>
References: <20160106205756.6256.31213.idtracker@ietfa.amsl.com> <FD698BD5-BD49-4968-A9FE-E5F58E1984D1@sinodun.com> <568D8E0F.8020609@cs.tcd.ie> <6BE9A610-E007-48DD-AE1D-E7C86877AD8A@sinodun.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <568E7BC4.5040905@cs.tcd.ie>
Date: Thu, 07 Jan 2016 14:52:52 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <6BE9A610-E007-48DD-AE1D-E7C86877AD8A@sinodun.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/6zIGOO27FgxtUNY5_-uG1eyRMmk>
Cc: tjw.ietf@gmail.com, draft-ietf-dnsop-edns-tcp-keepalive@ietf.org, dnsop@ietf.org, dnsop-chairs@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [DNSOP] Stephen Farrell's Discuss on draft-ietf-dnsop-edns-tcp-keepalive-05: (with DISCUSS and COMMENT)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2016 14:52:57 -0000

Hi Sara,

On 07/01/16 10:54, sara wrote:
> 
>> On 6 Jan 2016, at 21:58, Stephen Farrell
>> <stephen.farrell@cs.tcd.ie> wrote:
>> 
>> 
>> Hiya,
>>> 
>>> Speaking for myself I don’t see this as the solution to managing
>>> DTLS sessions, I think that would be better handled with a TLS
>>> extension.
>> 
>> Yes, that's the obvious answer, and a not bad answer. Did the dnsop
>> WG (or dprive) consider the issue already?
> 
> It is a good question, but it wan't explicitly discussed AFAIK.

Okey-dokey, I'll ask Joel how he prefers to handle this on the
call today and go with whatever he recommends.

> 
>>>> - 3.3.2:
>> 
>> Oops:-) Typo there sorry, the one that puzzled me is at the end of
>> 3.2.2 where it says " This holds true even if a previous 
>> edns-keepalive-option exchange occurred on the existing TCP 
>> connection."
> 
> Ah, this is to do with the semantics of EDNS0 exchanges. It just
> clarifies that if the server chooses not to send the option in this
> scenario it is effectively equivalent to the server sending a 0
> timeout (indicating it does not want to continue with keepalive) even
> it if previously indicated it supported it.

Ah grand, I get it now. I think the way you've explained it above
is clearer for me anyway, so maybe consider saying it that way if
you do any more changes.

Cheers,
S.

> 
> Sara.
>