IETF Logo Mail Archive

Re: Last Call: <draft-ietf-dnsop-serve-stale-07.txt> (Serving Stale Data to Improve DNS Resiliency) to Proposed Standard

S Moonesamy <sm+ietf@elandsys.com> Wed, 11 September 2019 18:55 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82B1212006E; Wed, 11 Sep 2019 11:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=opendkim.org header.b=NNubGEs0; dkim=pass (1024-bit key) header.d=elandsys.com header.b=hfoN+BZN
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 rsuvvilM0x-S; Wed, 11 Sep 2019 11:55:38 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 25BB0120C12; Wed, 11 Sep 2019 11:55:38 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.178.124]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x8BItOZB029248 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Sep 2019 11:55:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1568228136; x=1568314536; bh=S0IlcK6QLrM27EMSfdKUhmJwReqmgn3lmlzvwJt3PTI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NNubGEs0/fjJ+ECsLe7DFUMz+zK7X97M86mH6ubaAVFZSgrW3+E7a8IV3+0qkHlrP hsk1pZGpIeIU6Esn6DETTKPBGfEFIlKFGyJ+Q3jzYMhi9Scbj0M8C8DevcAZxHHeGT 0ET5zsjfLyEaaDsq8Q4/ZAmvz2T165fkkGfMnX24=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1568228136; x=1568314536; i=@elandsys.com; bh=S0IlcK6QLrM27EMSfdKUhmJwReqmgn3lmlzvwJt3PTI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hfoN+BZNZz+gMTRyUmoedDiqlg3V9LrL8gs2PQOXkoD0QvvzPmA4x6ihaEhNat5MG cyGZMivW3cm1+/yR6N1SpTgAmXUk8ax+H3KtfCSrSmLA47owtKm9tb6UM7T1d02rUp lug8s1u32sxYEeUZcB5TBS3hbJ21ugjvzWnk2ZlA=
Message-Id: <6.2.5.6.2.20190911114140.0ea2b0d8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 11 Sep 2019 11:55:04 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-ietf-dnsop-serve-stale-07.txt> (Serving Stale Data to Improve DNS Resiliency) to Proposed Standard
Cc: draft-ietf-dnsop-serve-stale@ietf.org
In-Reply-To: <156821841762.13409.15153693738152466982.idtracker@ietfa.am sl.com>
References: <156821841762.13409.15153693738152466982.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cGMPlXW6nlViQQL6pmAMMDTAQm4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2019 18:55:40 -0000

Hello,
At 09:13 AM 11-09-2019, The IESG wrote:
>The IESG has received a request from the Domain Name System Operations WG
>(dnsop) to consider the following document: - 'Serving Stale Data to Improve
>DNS Resiliency'
>   <draft-ietf-dnsop-serve-stale-07.txt> as Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits final
>comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2019-09-25. Exceptionally, comments may be

There is the following recommendation in Section 4: "When returning a 
response containing stale records, a recursive resolver MUST set the 
TTL of each expired record in the message to a value greater than 0, 
with 30 seconds RECOMMENDED".  Where does the "30 seconds" come from?

Regards,
S. Moonesamy

v2.23.0 | Report a Bug | By Email