IETF Logo Mail Archive

Re: [Sidrops] New Version Notification for draft-sriram-sidrops-drop-invalid-policy-00.txt

Stephen Kent <stkent@verizon.net> Fri, 09 March 2018 16:17 UTC

Return-Path: <stkent@verizon.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 24A10127978 for <sidrops@ietfa.amsl.com>; Fri, 9 Mar 2018 08:17:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 aAQA5z9n_6H6 for <sidrops@ietfa.amsl.com>; Fri, 9 Mar 2018 08:17:16 -0800 (PST)
Received: from omr-m008e.mx.aol.com (omr-m008e.mx.aol.com [204.29.186.7]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3320012D7F2 for <sidrops@ietf.org>; Fri, 9 Mar 2018 08:17:16 -0800 (PST)
Received: from mtaout-mba02.mx.aol.com (mtaout-mba02.mx.aol.com [172.26.133.110]) by omr-m008e.mx.aol.com (Outbound Mail Relay) with ESMTP id 3D09C3800063; Fri, 9 Mar 2018 11:17:15 -0500 (EST)
Received: from iMac-Study.fios-router.home (pool-108-49-30-217.bstnma.fios.verizon.net [108.49.30.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mtaout-mba02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id D111338000082; Fri, 9 Mar 2018 11:17:14 -0500 (EST)
To: "Montgomery, Douglas (Fed)" <dougm@nist.gov>, "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>, Tim Bruijnzeels <tim@ripe.net>
Cc: "sidrops-chairs@ietf.org" <sidrops-chairs@ietf.org>, "sidrops@ietf.org" <sidrops@ietf.org>
References: <152029076512.12908.14537578849320525718.idtracker@ietfa.amsl.com> <BYAPR09MB2773819AB3961189CDA9B4D784D90@BYAPR09MB2773.namprd09.prod.outlook.com> <074D75CB-7D34-4838-BEAA-88AE5E044F6C@ripe.net> <BYAPR09MB27738385E28497E1EC5B32AD84DE0@BYAPR09MB2773.namprd09.prod.outlook.com> <70613650-C8D6-43D9-8643-5694B77BADA9@nist.gov>
From: Stephen Kent <stkent@verizon.net>
Message-ID: <5d2afc8e-7f9a-e2bc-fa84-88b943639bd6@verizon.net>
Date: Fri, 09 Mar 2018 11:17:14 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <70613650-C8D6-43D9-8643-5694B77BADA9@nist.gov>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
x-aol-global-disposition: G
x-aol-sid: 3039ac1a856e5aa2b38a4ce4
X-AOL-IP: 108.49.30.217
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/c79vktl5Yg7mQEQeAuhtEKYLGh8>
Subject: Re: [Sidrops] New Version Notification for draft-sriram-sidrops-drop-invalid-policy-00.txt
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: Fri, 09 Mar 2018 16:17:17 -0000

Doug,

> Maybe another way to phrase this is, as far as we can tell (sec 4, RFC6483) the documented use of AS0 is a usage convention at best, i.e. does not have any specific normative requirements, beyond normal ROA / validation procedures.
Since 6483 is informational,  nothing it says is normative. However, 
RFCs 6491, 7606, and 7607 are standards track and the more relevant 
documents. Why did you not cite those RFCs and their (normative) 
statements for how AS 0 is to be treated in the RPKI context?

Steve

v2.23.0 | Report a Bug | By Email