--- 1/draft-ietf-idr-flowspec-path-redirect-06.txt	2018-12-13 03:13:08.979435284 -0800
+++ 2/draft-ietf-idr-flowspec-path-redirect-07.txt	2018-12-13 03:13:09.007435955 -0800
@@ -1,21 +1,21 @@
 
 IDR Working Group                                   G. Van de Velde, Ed.
 Internet-Draft                                                     Nokia
 Intended status: Standards Track                                K. Patel
-Expires: December 7, 2018                                         Arrcus
+Expires: June 16, 2019                                            Arrcus
                                                                    Z. Li
                                                      Huawei Technologies
-                                                            June 5, 2018
+                                                       December 13, 2018
 
                     Flowspec Indirection-id Redirect
-                draft-ietf-idr-flowspec-path-redirect-06
+                draft-ietf-idr-flowspec-path-redirect-07
 
 Abstract
 
    This document defines a new extended community known as "FlowSpec
    Redirect to indirection-id Extended Community".  This extended
    community triggers advanced redirection capabilities to flowspec
    clients.  When activated, this flowspec extended community is used by
    a flowspec client to retrieve the corresponding next-hop and encoding
    information within a localised indirection-id mapping table.
 
@@ -37,21 +37,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on December 7, 2018.
+   This Internet-Draft will expire on June 16, 2019.
 
 Copyright Notice
 
    Copyright (c) 2018 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -373,23 +373,22 @@
    possible from a semantics perspective to have multiple clashing
    redirect actions defined within a single flowspec rule.  For best and
    consistant compatibility with legacy implementations, the redirect
    functionality as documented by RFC5575 MUST NOT be broken, and hence
    when a clash occurs, then RFC5575 based redirect MUST take priority.
 
    Additionally, if the "Redirect to indirection-id" does not result in
    a valid redirection, then the flowspec rule MUST be processed as if
    the "Redirect to indirection-id" community was not attached to the
    flowspec route.  In addition the flowspec client MUST provide an
-   indication within the BGP routing table that the respective
-   "'Redirect to indirection-id" resulted in an invalid redirection
-   action.
+   indication that the respective "'Redirect to indirection-id" resulted
+   in an invalid redirection action.
 
 7.  Security Considerations
 
    A system using "Redirect to indirection-id" extended community can
    cause during the redirect mitigation of a DDoS attack overflow of
    traffic received by the mitigation infrastructure.
 
 8.  Acknowledgements
 
    This document received valuable comments and input from IDR working