Re: [sidr] AD Review of draft-ietf-sidr-slurm-04

Di Ma <madi@zdns.cn> Wed, 31 January 2018 08:39 UTC

Return-Path: <madi@zdns.cn>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E64813169D; Wed, 31 Jan 2018 00:39:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level:
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] 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 akMAwZ5iMtx0; Wed, 31 Jan 2018 00:39:42 -0800 (PST)
Received: from smtpbg132.qq.com (SMTPBG132.QQ.COM [113.108.23.42]) (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 3361D1316A0; Wed, 31 Jan 2018 00:39:38 -0800 (PST)
X-QQ-mid: bizesmtp5t1517387951tl3iam7be
Received: from [192.168.216.94] (unknown [202.173.9.211]) by esmtp4.qq.com (ESMTP) with id ; Wed, 31 Jan 2018 16:39:10 +0800 (CST)
X-QQ-SSF: 00400000004000F0FF30000B0000000
X-QQ-FEAT: pQslgWCixdZFaCkWDG7aZvCm+bE9j7NTpEHG1F/YtT24BdFiYOZ7+pNMRd74P 9PCPzLoRVP61+8lDVm30aC/5dTP6ioubhFk5Ne7S7kZgx6+GokJdfHg1wTeyqfubwqP2M9V fHw8UzbXH+0IhjuWLZzs+CveKFEz02H0U3HVudTR3crkuW1sokmVs+6HFejxm1x0k4KNCA+ zHrvSUUF5YxTI/X6LHbOAm0cnB+Mhk/5sxLOYnuNiCAK5DYCtgHMy0UDjaJVlcHFZAM4yuM UEbhLOzAtwJiOIQBoZxWUkQJcgyYTtZ7blMgLVEucl6xuH
X-QQ-GoodBg: 2
Content-Type: text/plain; charset="gb2312"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Di Ma <madi@zdns.cn>
In-Reply-To: <DM2PR09MB055943E50F1E08DC82BED08484E50@DM2PR09MB0559.namprd09.prod.outlook.com>
Date: Wed, 31 Jan 2018 16:39:09 +0800
Cc: Alvaro Retana <aretana.ietf@gmail.com>, "draft-ietf-sidr-slurm@ietf.org" <draft-ietf-sidr-slurm@ietf.org>, Chris Morrow <morrowc@ops-netman.net>, "sidr-chairs@ietf.org" <sidr-chairs@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <15A3BEEB-4A6A-49FB-AF29-3CD53D4EF484@zdns.cn>
References: <CAMMESsw1i_Am0UOS0Tx6yfz7kb_jsaxhMZtu5rcsoM4cDeVfkw@mail.gmail.com> <DM2PR09MB055943E50F1E08DC82BED08484E50@DM2PR09MB0559.namprd09.prod.outlook.com>
To: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>
X-Mailer: Apple Mail (2.3445.5.20)
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:zdns.cn:qybgweb:qybgweb17
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/88k01MPbpSz43dpBG5NH5X-9sPU>
Subject: Re: [sidr] AD Review of draft-ietf-sidr-slurm-04
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jan 2018 08:39:48 -0000

Sriram,

Thanks for your comments.

We authors will update the draft, in response to your suggestions and comments from the AD.

Di


> 在 2018年1月30日,04:36,Sriram, Kotikalapudi (Fed) <kotikalapudi.sriram@nist.gov> 写道:
> 
> David, Di, Tim:
>  
> These are minor comments in alignment with Alvaro’s.
>  
> Alvaro wrote:
>  
> >M4. References:
>  
> >M4.1. s/I-D.ietf-sidr-bgpsec-overview/rfc8205  ...and should be Normative.
>  
> >M4.3. [minor] Please update the references according to the Nits [1].
>  
> >[1] https://tools.ietf.org/idnits?url=https://tools.ietf.org/id/draft-ietf-sidr-slurm-04.txt 
>  
> With regard to updating the references, I noticed that the draft references
> [I-D.ietf-sidr-bgpsec-overview] in two places where it should reference
> BGPsec Protocol Specification [RFC 8205].  For example, on page 3:
>  
> (Validation of the origin of a route is
>    described in [RFC6483], and validation of the path of a route is
>    described in [I-D.ietf-sidr-bgpsec-overview].)
>  
> For “validation of the path of a route” the pointer should be Section 5 of RFC 8205.
>  
> AFAIK, [I-D.ietf-sidr-bgpsec-overview] is expired and there are no plans to publish it.
>  
> I would also suggest that both RFCs 6483 and 6811 can be referenced when
> talking about “Validation of the origin of a route.”  RFC 6811 is Standards Track
> while 6483 is Informational.
>  
> Thanks.
>  
> Sriram
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr