Re: [DNSOP] Call for Adoption: draft-belyavskiy-rfc5933-bis

S Moonesamy <sm+ietf@elandsys.com> Thu, 18 June 2020 07:51 UTC

Return-Path: <sm@elandsys.com>
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 DA52C3A0F0A; Thu, 18 Jun 2020 00:51:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=elandsys.com
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 XBWsxHbdfJnO; Thu, 18 Jun 2020 00:51:33 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id EEA8E3A0F80; Thu, 18 Jun 2020 00:51:20 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.18.20]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 05I7p76g029833 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Jun 2020 00:51:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1592466679; x=1592553079; i=@elandsys.com; bh=QnxzjqJZRJUtu22SL6RWxZPl2YXqSwBknzsIhnZsgN0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=N0dwNBwm8A70PGW48C/H4T21Uv85ST7h8qSLD10nTA/kcmRFFAWNxMmmqFkUe2UwV 6aSPm285y7ObLyN0OltrcXrIPApG/Qnvqqhl4eI0XagPZrzzil0AFXpTUbuG0ca2uD +z6JyHAnYUJ3QhnZPHNZwgb3/bXGkRZ53S2ly/7k=
Message-Id: <6.2.5.6.2.20200618002452.0c0c90c0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 18 Jun 2020 00:47:20 -0700
To: dnsop@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: dnsop-chairs@ietf.org
In-Reply-To: <CADyWQ+H4713BnZDntTuVW0FrO59zZ9NFJ=J=n9JFFq2zmfy2pQ@mail.g mail.com>
References: <CADyWQ+H4713BnZDntTuVW0FrO59zZ9NFJ=J=n9JFFq2zmfy2pQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4GhDJhmExud-5UvLcbBbOtLYuCY>
Subject: Re: [DNSOP] Call for Adoption: draft-belyavskiy-rfc5933-bis
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: Thu, 18 Jun 2020 07:51:40 -0000

Hello,
At 02:07 PM 03-06-2020, Tim Wicinski wrote:
>As we stated in the meeting and in our chairs actions, we're going to run
>regular call for adoptions over next few months.
>We are looking for *explicit* support for adoption.
>
>
>This starts a Call for Adoption for draft-belyavskiy-rfc5933-bis

There is the following in Section 1: "Familiarity with DNSSEC and 
with GOST signature and hash algorithms is assumed in this 
document."  I am not familiar with the cryptographic aspects [1] of 
the GOST R 34.11-2012 to perform an adequate review of that standard.

The current draft is well-written.  It probably needs some work 
before it is ready for a Last Call.  I suggest consideration what to 
do about RFC 5933 given that the intended status of the document.

Regards,
S. Moonesamy

1. The Security Area Directors will likely ask whether the document 
was reviewed by the relevant research group.