100% agree.
There is however a real risk of a control signaling ("NVOi") creeping in,
Wrecking some the distributed-emergent elegance & resilience of the spec,
and creating long lived states and dependencies which are sizeof(mesh).
It always comes up at some point. So you should probably prepare for it.
This prep can be in the form of optional overlay OAM or Echo spec.
This is be used to measure RTT and such IFF peer NVEs choose to.
Per each Echo option that will come up, and guarantee to be many,
there should be a simple litmus test which is - can it be mapped.
Only if not, then it should be considered.
--szb
> On Nov 15, 2013, at 14:19, Thomas Narten <[email protected]> wrote:
>
> NVO3 does not need an NVE to NVE control protocol.
>
> Calling this out explicitly, as it is consistent with the current
> architecture document. There is no need for an NVE to NVE control
> protocol, for the purpose of maintaining/populating the mapping
> tables. There may well be interactions between NVEs, such as setting
> up tunnels, creating security associations for protecting data plane
> traffic, or providing error indications (e.g., equivalent of ICMP "TS
> unreachable" responses).
>
> If folk disagree, now would be a good time to have that conversation.
>
> "Yves Hertoghs (yhertogh)" <[email protected]> writes:
>
>>>> I disagree with the need for an NVE to NVE control plane.
>>
>>> [Lucy] do you think we need NVE-NVE control plane? I don’t think
>>> this is what you mean from the following statement.
>>
>> No we dont need an NVE to NVE control plane.
>>
>>>> That doesn't mean that you can't colocate a portion of the
>>>> distributed NVA with every NVE, which is the model that
>>>> e.g. BGP/L3VPN or ISIS/TRILL uses.
>>
>>> [Lucy] Agreed. NVA can collocate w/ NVE. (partially or entire).
>>
>> And as a result there is only a need for a control plane between the
>> NVE function and the NVA function.
>
> Thomas
>
> _______________________________________________
> nvo3 mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
