On Nov 7, 2013:12:39 PM, at 12:39 PM, Joe Marcus Clarke <[email protected]> wrote:
> On 11/7/13, 12:11 AM, Eric Osborne (eosborne) wrote:
>> If Not: what problems arise that would be solved by having a network model,
>> do we need one, and where would it come from if not i2rs?
>
> I think it is useful to have a network-wide topology model that is accessible
> at a device level. Meaning, topology could be distributed into the network
> and retrievable either as a whole network or in parts based on filters.
That is definitely the right way to go here, and is indeed explained in
the topology-related architecture. The idea is much along the lines of a
network service that lets say has a ReSTful interface whereby you specify
various filtering options in a GET request and are returned a subset of the
topology. Asking for just devices, hops, links, etc... is just one option we
definitely envisioned.
--Tom
> For example, given an I2RS Agent, give me the Agent plus two routed hops.
> This would be very useful, for example, in the support case where we need to
> understand what a network looks like in order to help troubleshoot problems.
>
> But, I could also ask this same Agent to give me the whole routed network
> from a given instance. This would give me the graph (edges, nodes) of that
> topology.
>
> Joe
>
> --
> Joe Marcus Clarke, CCIE #5384, | |
> SCJP, SCSA, SCNA, SCSECA, VCP ||||| |||||
> Distinguished Services Engineer ..:|||||||||::|||||||||:..
> Phone: +1 (919) 392-2867 c i s c o S y s t e m s
> Email: [email protected]
>
> ----------------------------------------------------------------------------
> _______________________________________________
> i2rs mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/i2rs
>
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
