Susan,
Many people don't know what NLRI abbreviation stands for (Network Layer
Reachability Information , so writing it out first time would be a good idea.
Throughout the text, the requirement number sequence is confusing until you get
to the very and where all requirements are listed and then it makes sense.
REQ04: The ability to interact with various policies configured on
the forwarding devices, in order to inform the policies
implemented by the dynamic routing processes. This interaction
should be through existing configuration mechanisms, such as
NETCONF, and should be recorded in the configuration of the local
device so operators are aware of the full policy implemented in
the network from the running configuration.
It is not clear to me if your requirement is that dynamic protocols should
impose persistent policies? It says it should be recorded in the configuration
of the local device.
I agree that those policies should be visible to operators and other
applications, but not sure if dynamic protocols should be allowed to implement
persistent policies. IMO, those should be ephemeral policies.
So maybe text should look like this
This interaction should be through existing configuration mechanisms, such as
NETCONF, and should be recorded in the running or ephemeral configuration of
the local device so operators are aware of the full policy implemented in the
network from the running configuration.
I'm trying to see major difference between REQ01/REQ02 and REQ08/REQ09?
In general I'm not sure if changing entries by dynamic protocol in RIB is a
good idea. If you plan to change only what is configured on the local device,
then that is OK, but if you start changing entries that are pushed from other
devices in the network, the system would get unstable. And it looks to me that
REQ09 would allow that.
Dean
On Jun 5, 2014, at 4:47 AM, Susan Hares <[email protected]> wrote:
> Tom:
>
> I'm glad to change the citation in the abstract. On the authors, this was
> merge of two drafts.
>
> Sue
>
> -----Original Message-----
> From: t.petch [mailto:[email protected]]
> Sent: Thursday, June 05, 2014 4:35 AM
> To: Susan Hares; [email protected]
> Cc: 'Keyur Patel (keyupate)'; Hannes Gredler; Russ White; 'Susan Hares';
> [email protected]
> Subject: Re: [i2rs] FW: I-D Action: draft-keyupate-i2rs-bgp-usecases-02.txt
>
> Sue
>
> Currently you have six authors which is too many for an RFC - someone's
> got to go! For me, this is not just an admin point - when commenting,
> I like to have one or two names, no more, as the clear pen holders whom I
> can expect to act. Too often, with so many names, everyone thinks that
> someone else will do something and nothing happens, so, in all seriousness,
> I oppose adoption until you sort this out amongst yourselves.
>
> Note too that you have a citation in the Abstract, again not allowed - this
> can be surprising difficult to get round but get round it you, one or more
> thereof, must.
>
> Tom Petch
>
>
> ----- Original Message -----
> From: "Susan Hares" <[email protected]>
> To: <[email protected]>
> Cc: "'Keyur Patel (keyupate)'" <[email protected]>; "Hannes Gredler"
> <[email protected]>; "Russ White" <[email protected]>; "'Susan Hares'"
> <[email protected]>; <[email protected]>
> Sent: Wednesday, June 04, 2014 7:49 PM
> Subject: [i2rs] FW: I-D Action: draft-keyupate-i2rs-bgp-usecases-02.txt
>
>
>> Jeff and Ed:
>>
>> This updated draft has all the changes that Keyur Patel promised and
> updates
>> to the reference the current i2rs internet drafts.
>>
>> Would you please do a Working Group adoption call?
>>
>> Thank you,
>> Sue Hares
>>
>>
>> -----Original Message-----
>> From: i2rs [mailto:[email protected]] On Behalf Of
>> [email protected]
>> Sent: Wednesday, June 04, 2014 1:44 PM
>> To: [email protected]
>> Cc: [email protected]
>> Subject: [i2rs] I-D Action: draft-keyupate-i2rs-bgp-usecases-02.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 : Use Cases for an Interface to BGP Protocol
>> Authors : Keyur Patel
>> Rex Fernando
>> Hannes Gredler
>> Shane Amante
>> Russ White
>> Susan Hares
>> Filename : draft-keyupate-i2rs-bgp-usecases-02.txt
>> Pages : 17
>> Date : 2014-06-04
>>
>> Abstract:
>> A network routing protocol like BGP is typically configured and
>> analyzed through some form of Command Line Interface (CLI) or
>> NETCONF. These interactions to control BGP and diagnose its
>> operation encompass: configuration of protocol parameters, display
> of
>> protocol data, setting of certain protocol state and debugging of
> the
>> protocol.
>>
>> Interface to the Routing System's (I2RS) Programmatic interfaces,
> as
>> defined in draft-ietf-i2rs-architecture, provides an alternate way
> to
>> control and diagnose the operation of the BGP protocol. I2RS may
> be
>> used for the configuration, manipulation, analyzing or collecting
> the
>> protocol data. This document describes set of use cases for which
>> I2RS can be used for BGP protocol. It is intended to provide a
> base
>> for the solution draft describing a set of interfaces to the BGP
>> protocol.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-keyupate-i2rs-bgp-usecases/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-keyupate-i2rs-bgp-usecases-02
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-keyupate-i2rs-bgp-usecases-02
>>
>>
>> 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/
>>
>> _______________________________________________
>> i2rs mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/i2rs
>>
>> _______________________________________________
>> i2rs mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/i2rs
>>
>
>
> _______________________________________________
> i2rs mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/i2rs
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
