Subject: [Roll] FW: New Version Notification for draft-ietf-roll-efficient-npdao-15.txt

From: Rahul Arvind Jadhav <[email-masked]>
Date: Mon, 8 Jul 2019 13:04:56 +0000

Hello all, 

The draft is updated for following:
1. Considerations for DCO retry. This was discussed as part of Mirja's DISCUSS point. (Section 4.6.3)
2. I previously missed an update based on Eric Gray's comment. This is incorporated now. (Section 4.6.2)

We believe that there are no pending updates (based on IESG comments) to the document.

Thanks,
Rahul

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: 08 July 2019 20:58
To: Rabi Narayan Sahoo <[email-masked]>; Pascal Thubert <[email-masked]>; Rahul Jadhav <[email-masked]>; Rabi Narayan Sahoo <[email-masked]>; Zhen Cao <[email-masked]>; Rahul Arvind Jadhav <[email-masked]>
Subject: New Version Notification for draft-ietf-roll-efficient-npdao-15.txt

A new version of I-D, draft-ietf-roll-efficient-npdao-15.txt
has been successfully submitted by Rahul Arvind Jadhav and posted to the IETF repository.

Name:		draft-ietf-roll-efficient-npdao
Revision:	15
Title:		Efficient Route Invalidation
Document date:	2019-07-08
Group:		roll
Pages:		23
URL:            https://www.ietf.org/internet-drafts/draft-ietf-roll-efficient-npdao-15.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-roll-efficient-npdao/
Htmlized:       https://tools.ietf.org/html/draft-ietf-roll-efficient-npdao-15
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-roll-efficient-npdao
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-roll-efficient-npdao-15

Abstract:
   This document explains the problems associated with the current use
   of NPDAO messaging and also discusses the requirements for an
   optimized route invalidation messaging scheme.  Further a new
   proactive route invalidation message called as "Destination Cleanup
   Object" (DCO) is specified which fulfills requirements of an
   optimized route invalidation messaging.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat