Re: [Sidrops] WG Adoption call for draft-madi-sidrops-rp-adoption

Di Ma <madi@rpstir.net> Wed, 11 October 2017 05:37 UTC

Return-Path: <madi@rpstir.net>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F9BE13239C for <sidrops@ietfa.amsl.com>; Tue, 10 Oct 2017 22:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 kujYXiycSeHl for <sidrops@ietfa.amsl.com>; Tue, 10 Oct 2017 22:37:46 -0700 (PDT)
Received: from out20-3.mail.aliyun.com (out20-3.mail.aliyun.com [115.124.20.3]) (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 BE9C3132026 for <sidrops@ietf.org>; Tue, 10 Oct 2017 22:37:45 -0700 (PDT)
X-Alimail-AntiSpam: AC=CONTINUE; BC=0.2111687|-1; FP=0|0|0|0|0|-1|-1|-1; HT=e02c03292; MF=madi@rpstir.net; NM=1; PH=DS; RN=3; RT=3; SR=0; TI=SMTPD_---.964DYCr_1507700229;
Received: from 192.168.218.249(mailfrom:madi@rpstir.net ip:124.17.24.252) by smtp.aliyun-inc.com(10.147.40.200); Wed, 11 Oct 2017 13:37:39 +0800
Content-Type: text/plain; charset="gb2312"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Di Ma <madi@rpstir.net>
In-Reply-To: <m2a80ycxid.wl-randy@psg.com>
Date: Wed, 11 Oct 2017 13:36:39 +0800
Cc: Keyur Patel <keyur@arrcus.com>, SIDR Operations WG <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1F8309A-232E-420F-9EF0-62317ECC929F@rpstir.net>
References: <CB3C3CD7-AE5E-4267-9E56-C55229D8BADA@arrcus.com> <m2d15ud00u.wl-randy@psg.com> <C0F6FF01-014B-4616-93F8-9370EEFF370F@arrcus.com> <m2a80ycxid.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/xCdEYOCEMN7vMmp8Mz13u-cVp0s>
Subject: Re: [Sidrops] WG Adoption call for draft-madi-sidrops-rp-adoption
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Oct 2017 05:37:47 -0000

Randy,

> 
> the document is mis-titled.  it is not a requirements document at all;
> note the lack of normative 2119 (or whatever it is numbered this week).


Good catch.

But I don’t think the document is mis-titled. 

I thought we don’t need normative 2119 in this draft as an Informational requirements document. 

Noting Informational RFC 4892 (Requirements for a Mechanism Identifying a Name Server Instance) and Informational RFC 6168 (Requirements for Management of Name Servers for the DNS) both have normative 2119, I am fine with adding normative 2119 in next version. 


Di