[Roll] RFC 9009 on Efficient Route Invalidation
rfc-editor@rfc-editor.org Fri, 09 April 2021 22:55 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30F5D3A1599; Fri, 9 Apr 2021 15:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 d5t8hPFpAZ3d; Fri, 9 Apr 2021 15:55:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21E0A3A15E6; Fri, 9 Apr 2021 15:55:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 050B5F4079B; Fri, 9 Apr 2021 15:55:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, roll@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210409225524.050B5F4079B@rfc-editor.org>
Date: Fri, 09 Apr 2021 15:55:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/KsfIdWCkGxA7ZpQprJTAwl4rzs8>
Subject: [Roll] RFC 9009 on Efficient Route Invalidation
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Apr 2021 22:55:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9009
Title: Efficient Route Invalidation
Author: R.A. Jadhav, Ed.,
P. Thubert,
R.N. Sahoo,
Z. Cao
Status: Standards Track
Stream: IETF
Date: April 2021
Mailbox: rahul.ietf@gmail.com,
pthubert@cisco.com,
rabinarayans0828@gmail.com,
zhencao.ietf@gmail.com
Pages: 21
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-roll-efficient-npdao-18.txt
URL: https://www.rfc-editor.org/info/rfc9009
DOI: 10.17487/RFC9009
This document explains the problems associated with the use of
No-Path Destination Advertisement Object (NPDAO) messaging in RFC
6550 and also discusses the requirements for an optimized route
invalidation messaging scheme. Further, this document specifies a new
proactive route invalidation message called the "Destination Cleanup
Object" (DCO), which fulfills requirements for optimized route
invalidation messaging.
This document is a product of the Routing Over Low power and Lossy networks Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC