[DNSOP] draft-ietf-dnsop-edns-tcp-keepalive-05

joel jaeggli <joelja@bogus.com> Thu, 07 January 2016 15:30 UTC

Return-Path: <joelja@bogus.com>
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 849211A8F41 for <dnsop@ietfa.amsl.com>; Thu, 7 Jan 2016 07:30:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 HOaRlmkBG0z0 for <dnsop@ietfa.amsl.com>; Thu, 7 Jan 2016 07:30:03 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E0811A8F3C for <dnsop@ietf.org>; Thu, 7 Jan 2016 07:30:03 -0800 (PST)
Received: from mb-2.local ([IPv6:2601:647:4204:51:74a7:106e:f363:db73]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u07FU2Td040553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 7 Jan 2016 15:30:02 GMT (envelope-from joelja@bogus.com)
To: "dnsop-chairs@tools.ietf.org" <dnsop-chairs@tools.ietf.org>, "dnsop@ietf.org" <dnsop@ietf.org>
From: joel jaeggli <joelja@bogus.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <568E8479.9090400@bogus.com>
Date: Thu, 07 Jan 2016 07:30:01 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:43.0) Gecko/20100101 Thunderbird/43.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="jOJJK50CKBgUUaS7dm7rXOMQmC6puxHwM"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/FVB_j23C51Njh1QcQZj6667i-4c>
Subject: [DNSOP] draft-ietf-dnsop-edns-tcp-keepalive-05
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 15:30:05 -0000

From Stephens discuss, this is a question we should probably answer for
ourselves. (it's no longer a consideration as a discuss.

  The question: how does this option play with DNS over
  DTLS? [1]

  The reason I ask is that there may be a need in that case
  for some similar option (or a TLS extension maybe) though
  for the DTLS session lifetime and not a TCP session
  lifetime. At present you are saying that this option is
  not it. And that's a fine answer but you could also have
  said that this could also be used for DTLS session
  lifetime handling. And that last might make sense for
  operational reasons (not sure really, but could be).

   [1] https://tools.ietf.org/html/draft-ietf-dprive-dnsodtls-03

My take personally is tcp keepalive option is not the mechanism for
dtls, but then we get multiple options specifying essentially the same
sort of value at some point in the future.

I just want to make sure we have a good reading on this.