Re: [DNSOP] Fwd: New Version Notification for draft-wkumari-dnsop-ttl-stretching-00.txt

Mukund Sivaraman <muks@isc.org> Fri, 06 January 2017 19:42 UTC

Return-Path: <muks@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AFC4129E09 for <dnsop@ietfa.amsl.com>; Fri, 6 Jan 2017 11:42:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 b3OXorPkEzNk for <dnsop@ietfa.amsl.com>; Fri, 6 Jan 2017 11:42:05 -0800 (PST)
Received: from mail.banu.com (mail.banu.com [46.4.129.225]) by ietfa.amsl.com (Postfix) with ESMTP id 07DB7129610 for <dnsop@ietf.org>; Fri, 6 Jan 2017 11:42:04 -0800 (PST)
Received: from jurassic (unknown [115.118.213.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id BC6BA2FA0225; Fri, 6 Jan 2017 19:42:02 +0000 (GMT)
Date: Sat, 07 Jan 2017 01:11:59 +0530
From: Mukund Sivaraman <muks@isc.org>
To: tjw ietf <tjw.ietf@gmail.com>
Message-ID: <20170106194159.GA14578@jurassic>
References: <147909930902.10318.12934239778853597228.idtracker@ietfa.amsl.com> <CAHw9_iK2mrzjpew2-jH9HTxoxGQT2DESzFt2G_iPQDOjq2KAEw@mail.gmail.com> <20161127111037.GA10721@jurassic> <CAHw9_iJXOEFoXLM-8XspFQBiHKZtpP6djFr6YR-Zd+A7NG5P0A@mail.gmail.com> <20170106172545.GA2684@jurassic> <ad86d5d0-40d4-0470-a369-37ab7af2937b@bogus.com> <20170106182542.GA10310@jurassic> <CADyWQ+H3O0V5i6K_K-VQA=dp6=C9APPVuaEpst-dY90PFeG-Bg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM"
Content-Disposition: inline
In-Reply-To: <CADyWQ+H3O0V5i6K_K-VQA=dp6=C9APPVuaEpst-dY90PFeG-Bg@mail.gmail.com>
User-Agent: Mutt/1.7.1 (2016-10-04)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/E3DXk0m-IeNm6i2nzlujgH5nSAo>
Cc: joel jaeggli <joelja@bogus.com>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-wkumari-dnsop-ttl-stretching-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 06 Jan 2017 19:42:06 -0000

Hi Tim

On Fri, Jan 06, 2017 at 02:00:39PM -0500, tjw ietf wrote:
> Mukund,
> 
> While I agree with you, Joel has the right guidance on this; but also
> knowing the authors fairly well,
> I feel they would not send us down a road that will box the work into a
> corner.

Yes, it was not in any way a statement about these particular authors.
I know the two authors are trying to work together to document something
which will be beneficial for DNS. Having spoken to DCL about this in
Seoul (I told DCL that Warren wanted to make a draft for this and they
should get in touch), I don't think he has any specific interest to
incorporate a patented idea.  Their interest is in having the details of
TTL stretching worked out.

However, when there is any person X introducing a specificiation which
incorporates a patent he/she owns, it could appear self-serving. In this
case, isn't it due process to question if any other approaches are
possible? (I say this in general terms - not specifically about this
author or his company.)

TTL stretching is a simple problem (it isn't a complicated area such as
a media codec). Exploring whether the method can be implemented without
being encumbered by the known patent wouldn't take a lot of time or
discussion.

This isn't even a published draft yet, so we don't know what the authors
may come up with.

There have been some noises from the nethers that the patent could be
avoided with minor modifications. I'm encouraging the authors again to
do some exploring. :P

		Mukund