IETF Logo Mail Archive

Re: [DNSOP] DNSSEC as a Best Current Practice

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 21 March 2022 14:36 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 3F0C03A12B7 for <dnsop@ietfa.amsl.com>; Mon, 21 Mar 2022 07:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham 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 nXl79QqEDCKZ for <dnsop@ietfa.amsl.com>; Mon, 21 Mar 2022 07:36:36 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id A5FAC3A0AC0 for <DNSOP@ietf.org>; Mon, 21 Mar 2022 07:36:34 -0700 (PDT)
Received: (qmail 50232 invoked from network); 21 Mar 2022 14:32:46 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 21 Mar 2022 14:32:46 -0000
Message-ID: <c9493050-5602-8b06-f3f5-9d018840640a@necom830.hpcl.titech.ac.jp>
Date: Mon, 21 Mar 2022 23:36:32 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: DNSOP@ietf.org
References: <3035599f-bcb9-b753-54bc-32f61683a0e5@necom830.hpcl.titech.ac.jp> <2F644929-3B97-4375-9458-7A64B2E17B04@nohats.ca> <e8781ae3-8cfa-1de7-abab-85fe4962b3db@necom830.hpcl.titech.ac.jp> <416D39CB-DDD6-45D9-9D59-F2B777EAED5F@rfc1035.com>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <416D39CB-DDD6-45D9-9D59-F2B777EAED5F@rfc1035.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6cCXa8K4q3LxwDMj-jS5K_GH2HM>
Subject: Re: [DNSOP] DNSSEC as a Best Current Practice
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 21 Mar 2022 14:36:38 -0000

Jim Reid wrote:

> That might or might not be true. But where's your draft and code for an alternative?

How can you say I must provide some draft for some protocol by
myself even though an alternative of DNS cookie already is an rfc?

						Masataka Ohta

v2.23.0 | Report a Bug | By Email