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

Di Ma <madi@zdns.cn> Wed, 31 January 2018 15:29 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 33E5913181E; Wed, 31 Jan 2018 07:29:20 -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 WkITx1uL-2qJ; Wed, 31 Jan 2018 07:29:10 -0800 (PST)
Received: from smtpbg339.qq.com (smtpbg339.qq.com [14.17.44.34]) (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 2EB6F12EB73; Wed, 31 Jan 2018 07:26:21 -0800 (PST)
X-QQ-mid: bizesmtp14t1517412374tpelieeq
Received: from [192.168.3.3] (unknown [118.247.18.232]) by esmtp4.qq.com (ESMTP) with id ; Wed, 31 Jan 2018 23:26:13 +0800 (CST)
X-QQ-SSF: 00400000004000F0FG30000B0000000
X-QQ-FEAT: 5gms5Di3ODjQt/A+ZLWtNltG6OiEjZkezD2IncgPRkVF5pnNXKzYWOK3mJGUo 4PXcSQWG30Gd7H7WzY8Lz+zAyyP6B/dcrms++yQaCca+ZmAcC4OpkmPaTi0oZmY1J3RlPrc b281OnMMge6P+hdftiW1TwMpC8xrsIjpQYB0907HWXWUWDcPitvqs3HcjbgWGqCBZ03QDGc 10Hyu0/thO9fnr0mw6jfsN+pEADblOWxZMms2HEb4KmotqlFUhtc5MGCltdjYD+Otd2V3vQ Ro076B3kg5vzeHy20Ni+fihtrDMakztE8K3GMnxV0B+CXb
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 23:26:12 +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: <441F300D-4D67-4EA4-A5F6-1305ABFB872A@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:qybgweb3
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/PrUQhvaQni4t4R_EM9rbo4di_xE>
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 15:29:20 -0000

Sriram,

Thanks again for your comments.


> 在 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.


Yes.  We should make the change.


> 
> 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.

Agreed.

RFC 6811 is more competent to talk about Validation of the origin of a route. 

Di


> 
> Thanks.
> 
> Sriram
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr