>>>> i like the philosophy of "multi-protocol socket". however, i moderately
>>>> doubt the "multi-protocol socket v2.0" is a perfect plan for every cases.
>>>> in a quite good hotel, we see typically one 'multi-protocol socket' while
>>>> a lot of local-standard sockets. i never think it will make me happy if i
>>>> see every socket in my room is *multi-protocol*, occupying much spaces and
>>>> quite noticeable on the walls. we need one to deploy somewhere not the
>>>> only one type to deploy anywhere. ;-)
>>>
>>> That point would be an operational matter for deploying any standardized
>>> technology. For example, an operator adopt OSPF to use its rich routing
>>> feature but the network is small, the operator does just area 0 routing,
>>> even OSPF allow inter-area routing for scale. Is an another ospf
>>> specification needed for 'OSPF Area 0 Only Routing'?
>>
>> Well if I only have a simple network and I uses RIP, you don't make
>> OSPF somehow compatible with RIP(or just include RIP with an OSPF
>> terminology face? I don't know) and say "hey, just use this super
>> suite, don't consider it overloaded, it's for unity!"
>
> Oh, you don't argue that OSPF covers an use case which is also covered by
> RIP. So then why are you arguing that an use case of MAP is eventually same
> with the LW46 use case?
I'm clearly saying they have different use cases, but that's not the
point. Let me repeat. If I want RIP, you cannot just place RIP into
OSPF, put an OSPF "face" on it, and force me to use the OSPF "suite"
while the essence of the protocol I'm using is still RIP.
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
