Re: [i2rs] Call for Adoption by WG: draft-atlas-i2rs-architecture-01 (ends Aug 12)

[Alia Atlas <[e-mail]>]

Hi Carlos,

Responses in-line with stuff agreed and no longer relevant cut for easier
reading.

On Wed, Aug 14, 2013 at 2:22 PM, Carlos Pignataro (cpignata) <
[e-mail]> wrote:

> On Aug 13, 2013, at 2:44 PM, Alia Atlas <[e-mail]> wrote:
>
> On Sun, Jul 28, 2013 at 6:06 PM, Carlos Pignataro (cpignata) <
> [e-mail]> wrote:
>
>>
>> What is your specific concern and how would you want to see the reach and
> scope confined in the architecture draft?
>
>
>
> Perhaps simply by aligning with the problem statement wording, in terms of
> "routing and signaling". Or is the "signaling" piece confined to label
> distribution?
>

[Alia] Sure - happy to change the "Routing" to "Routing and Signaling" in
the description and in the figure.

> 4.1.  Example Network Application: Topology Manager
>>
>>    One example of such an application is a Topology Manager.  Such an
>>    application includes an I2RS client which uses the I2RS protocol to
>>    collect information about the state of the network.  The Topology
>>    Manager would collect device and interface state from devices it
>>    interacts with directly.
>>
>> CMP: Tunnels are some times key elements in a topology. Are tunnels
>> considered as "interfaces" or should those be called out explicitly?
>>
>
> [Alia] Tunnels aren't interfaces - but the details of what should be in
> the topology depends on the topology info-model and isn't specified in the
> architecture.
>
>
>
> Fair enough -- I agree it's not within the scope here, but I do thing that
> tunnels require some looking into.
>

[Alia] Absolutely - I'd suggest talking to Joel Halpern, Jan Medved, Adrian
Farrell, Tom Nadeau, and others interested in the topology info-model.

>
>>
> -- Carlos.
> PS: and thanks for not responding earlier, others were on vacation as well
> :-)
>
:-)  I hope yours was fun too!   The Pergamon Museum was amazing.

Alia