I have updated this draft in response to Deborah's AD review and Nabil's rtg-dir review.
I would greatly appreciate it if others could read/reread this draft and send additional comments and suggestions. <AD-hat>As you probably know, we're discouraging publishing drafts that don't really need to live as RFCs and a category to examine carefully is certainly problem-statements. </AD-hat> As an author, I feel that this draft has some useful and unique material primarily in Section 5. I also think that Section 4 outlines some of the assumptions and needs for a feedback loop with push notifications, that the architecture draft simply assumes. I do think that this draft provides useful context for I2RS - but I am also very open to hearing others opinions on whether having this information as an RFC is likely to be useful. Thanks, Alia On Thu, Dec 17, 2015 at 11:42 AM, <[email protected]> wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Interface to the Routing System Working > Group of the IETF. > > Title : Interface to the Routing System Problem Statement > Authors : Alia Atlas > Thomas D. Nadeau > Dave Ward > Filename : draft-ietf-i2rs-problem-statement-07.txt > Pages : 11 > Date : 2015-12-17 > > Abstract: > Traditionally, routing systems have implemented routing and signaling > (e.g. MPLS) to control traffic forwarding in a network. Route > computation has been controlled by relatively static policies that > define link cost, route cost, or import and export routing policies. > With the advent of highly dynamic data center networking, on-demand > WAN services, dynamic policy-driven traffic steering and service > chaining, the need for real-time security threat responsiveness via > traffic control, and a paradigm of separating policy-based decision- > making from the router itself, the need has emerged to more > dynamicaly manage and program routing systems in order to control > routing information and traffic paths and to extract network topology > information, traffic statistics, and other network analytics from > routing systems. > > This document proposes meeting this need via an Interface to the > Routing System (I2RS). > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-i2rs-problem-statement/ > > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-i2rs-problem-statement-07 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-problem-statement-07 > > > 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. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > I-D-Announce mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
