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

"Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov> Mon, 22 October 2018 21:19 UTC

From: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>
To: "sidrops@ietf.org" <sidrops@ietf.org>
CC: Tim Bruijnzeels <tim@nlnetlabs.nl>, Keyur Patel <keyur@arrcus.com>, Jeff Haas <jhaas@juniper.net>
Thread-Topic: New Version Notification for draft-sriram-sidrops-drop-invalid-policy-02.txt
Thread-Index: AQHUahQbBPyM/huMxU2PSFHTRw+HjqUrwT+Q
Date: Mon, 22 Oct 2018 21:19:32 +0000
Message-ID: <SN6PR0901MB2366CBB5EBA7918C8A01EADC84F40@SN6PR0901MB2366.namprd09.prod.outlook.com>
References: <154021875771.5752.5681218895770750570.idtracker@ietfa.amsl.com>
In-Reply-To: <154021875771.5752.5681218895770750570.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9804491b-d325-434a-a7ef-08d638640f80
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2018 21:19:32.6438 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR0901MB2367
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/uxjJWV4Nq1YvzrmQtJzhoXRdDFk>
Subject: [Sidrops] FW: New Version Notification for draft-sriram-sidrops-drop-invalid-policy-02.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 22 Oct 2018 21:19:40 -0000

The following changes made in this updated version:
- AS0 ROA consideration  (Tim)
- 0.0.0.0/0 (IPv4) or ::/0 (IPv6) consideration  (Keyur)
- Jeff Haas' suggestions about implementation included

URL:            https://tools.ietf.org/html/draft-sriram-sidrops-drop-invalid-policy-02   

Please let authors know about your reflections on the following wordings in the draft:

   The existence of an AS0 ROA for a prefix means that the prefix or any
   more specific prefix subsumed in it are forbidden from routing except
   when there exists a different ROA with a normal ASN for the prefix or
   the more specific prefix.  DISR policy MUST apply the following
   exception: If a route is Invalid due to an AS0 ROA, then always drop
   the route.

   Any routes for 0.0.0.0/0 (IPv4) or ::/0 (IPv6) in the routing table
   must be excluded from consideration in the DISR policy.  (Author's
   note: Think this through with help from the WG.)

Thanks.
Sriram


-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: Monday, October 22, 2018 10:33 AM
To: Sriram, Kotikalapudi (Fed) <kotikalapudi.sriram@nist.gov>; Montgomery, Douglas (Fed) <dougm@nist.gov>; Borchert, Oliver (Fed) <oliver.borchert@nist.gov>; Job Snijders <job@ntt.net>
Subject: New Version Notification for draft-sriram-sidrops-drop-invalid-policy-02.txt

A new version of I-D, draft-sriram-sidrops-drop-invalid-policy-02.txt
has been successfully submitted by Kotikalapudi Sriram and posted to the
IETF repository.

Name:		draft-sriram-sidrops-drop-invalid-policy
Revision:	02
Title:		Origin Validation Policy Considerations for Dropping Invalid Routes
Document date:	2018-10-22
Group:		Individual Submission
Pages:		7

URL:            https://tools.ietf.org/html/draft-sriram-sidrops-drop-invalid-policy-02  
Diff:  https://tools.ietf.org/rfcdiff?url2=draft-sriram-sidrops-drop-invalid-policy-02.txt 

Abstract:
   Deployment of Resource Public Key Infrastructure (RPKI) and Route
   Origin Authorizations (ROAs) is expected to occur gradually over
   several or many years.  During the incremental deployment period,
   network operators would wish to have a meaningful policy for dropping
   Invalid routes.  Their goal is to balance (A) dropping Invalid routes
   so hijacked routes can be eliminated, versus (B) tolerance for
   missing or erroneously created ROAs for customer prefixes.  This
   document considers a Drop Invalid if Still Routable (DISR) policy
   that is based on these considerations.  The key principle of DISR
   policy is that an Invalid route can be dropped if a Valid or NotFound
   route exists for a subsuming less specific prefix.

[Sidrops] FW: New Version Notification for draft-… Sriram, Kotikalapudi (Fed)