Re: [i2rs] I-D Action: draft-ietf-i2rs-problem-statement-08.txt

["Susan Hares" <[e-mail]>]

Qin: 

Thank you for your editorial review of this document.   

Sue Hares 

-----Original Message-----
From: i2rs [mailto:[e-mail]] On Behalf Of Qin Wu
Sent: Monday, January 04, 2016 10:41 PM
To: [e-mail]
Cc: 'Jeffrey Haas'; Susan Hares; [e-mail]; Alia Atlas
Subject: Re: [i2rs] I-D Action: draft-ietf-i2rs-problem-statement-08.txt

Hi, Alia:
Thanks for the update to address Nabil comments and AD's comments.
I have re-read this draft, I agree with you that section 5 and section 4
have great value and provide a clear goal and good guidance for all the I2RS
related work. I think this draft is ready for publication.
Here are a few editorial comments and suggestions for your consideration.
1. Section2, paragraph 5:
s/with in/within
2. Section 2,Figure 1:
In the figure 1, “<== I2RS protocol” is used to indicate I2RS protocol is
used on the interface between I2RS client and I2RS agent.
But In the legend following the figure 1, there is no legend description for
“<==”.
3.Section 2, paragraph 7:
Is this component(i.e., subscription and configuration) a kind of data
source for measurement data or event data? Why configuration is specially
needed for this component rather than other component? How this logical
component is used to collect measurement data, statistics, how event is
collected?
I know the subscription and configuration component is not in the scope of
I2RS? However I am curious to know whether subscription and configuration
also used for providing authentication and authorization or security
purpose? 
4. Section 3, paragraph 1:
What is the difference between Next hop indirection and routing indirection?
5. Section 4, last paragraph:
Not sure policy decision is made by application? If my understanding is
correct, Application should describe goal or objective, the policy decision
is made by I2RS client, the I2RS agent enforce policy in the routing system.
6. Section 5, bullet 4:
/”i.e.:”/”i.e.,”
7. Section 5, bullet 4:
If my understanding is correct, Duplex means bidirectional communication
between I2RS agent and I2RS client, however when I read the second sentence
and the third sentence in this paragraph, I feel a little bit confused, For
the second sentence, yes, operation and acknowledgements can be sent by both
parties, however I am not sure the failure or event can be sent by the
application or I2RS client to I2RS agent embedded in the router.
For the third sentence, why we use negative sentence? Do we mean both pull
model and push should be supported? What is the pure pull model? can pull
model be used by router to pull response from application?

-Qin
-----邮件原件-----
发件人: I-D-Announce [mailto:[e-mail]] 代表
[e-mail]
发送时间: 2015年12月19日 7:06
收件人: [e-mail]
抄送: [e-mail]
主题: I-D Action: draft-ietf-i2rs-problem-statement-08.txt


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-08.txt
	Pages           : 11
	Date            : 2015-12-18

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
   dynamically 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-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-problem-statement-08


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
[e-mail]
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
[e-mail]
https://www.ietf.org/mailman/listinfo/i2rs