[Last-Call] Why a 2nd Last Call ? Re: Last Call: <draft-ietf-anima-autonomic-control-plane-24.txt> (An Autonomic Control Plane (ACP)) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



	
The previous IETF Last Call on this document was in February 2018 for revision -13. Since then, the authors have made substantive changes in the document and we are now at revision -24. The authors and myself believe that the document is ready for IESG evaluation but I, as the shepherding AD, consider that the amount of changes requires a new IETF Last Call.

Thank you for the review and thank you for the authors and the WG for the efforts put in this document

Best regards

-éric vyncke

-----Original Message-----
From: <iesg-secretary@xxxxxxxx> on behalf of The IESG <iesg-secretary@xxxxxxxx>
Reply-To: "last-call@xxxxxxxx" <last-call@xxxxxxxx>
Date: Tuesday, 7 April 2020 at 15:35
To: IETF-Announce <ietf-announce@xxxxxxxx>
Cc: Sheng Jiang <jiangsheng@xxxxxxxxxx>, "jiangsheng@xxxxxxxxxx" <jiangsheng@xxxxxxxxxx>, "anima@xxxxxxxx" <anima@xxxxxxxx>, Eric Vyncke <evyncke@xxxxxxxxx>, "anima-chairs@xxxxxxxx" <anima-chairs@xxxxxxxx>, "draft-ietf-anima-autonomic-control-plane@xxxxxxxx" <draft-ietf-anima-autonomic-control-plane@xxxxxxxx>
Subject: Last Call: <draft-ietf-anima-autonomic-control-plane-24.txt> (An Autonomic Control Plane (ACP)) to Proposed Standard

    
    The IESG has received a request from the Autonomic Networking Integrated
    Model and Approach WG (anima) to consider the following document: - 'An
    Autonomic Control Plane (ACP)'
      <draft-ietf-anima-autonomic-control-plane-24.txt> as Proposed Standard
    
    The IESG plans to make a decision in the next few weeks, and solicits final
    comments on this action. Please send substantive comments to the
    last-call@xxxxxxxx mailing lists by 2020-04-21. Exceptionally, comments may
    be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
    of the Subject line to allow automated sorting.
    
    Abstract
    
    
       Autonomic functions need a control plane to communicate, which
       depends on some addressing and routing.  This Autonomic Control Plane
       should ideally be self-managing, and as independent as possible of
       configuration.  This document defines such a plane and calls it the
       "Autonomic Control Plane", with the primary use as a control plane
       for autonomic functions.  It also serves as a "virtual out-of-band
       channel" for Operations, Administration and Management (OAM)
       communications over a network that provides automatically configured
       hop-by-hop authenticated and encrypted communications via
       automatically configured IPv6 even when the network is not
       configured, or misconfigured.
    
    
    
    
    The file can be obtained via
    https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/
    
    IESG discussion can be tracked via
    https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/ballot/
    
    The following IPR Declarations may be related to this I-D:
    
       https://datatracker.ietf.org/ipr/2407/
    
    
    
    
    
    
    

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux