This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/

[ipv6-wg] next version of RIPE-501, v.2

Previous message (by thread): [ipv6-wg] next version of RIPE-501, v.2
Next message (by thread): [ipv6-wg] next version of RIPE-501, v.2

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Isacco Fontana isacco.fontana at trentinonetwork.it
Sun Jul 24 18:00:57 CEST 2011

I agree ...

Isacco 

Inviato da iPad

Il giorno 24/lug/2011, alle ore 16:12, Sander Steffann <sander at steffann.nl> ha scritto:

> Hi,
> 
>> If the equipment doesn't support IS-IS, then you can't expect it to support IS-IS MT ;)
>> 
>> Anyway, making IS-IS mandatory makes absolutely no sense; it's rarely used in Enterprise environments.
>> 
>> What we could do is to change the current requirement into "If the equipment supports IS-IS routing protocol, it MUST support IS-IS MT ..." (don’t cut/paste, use the wording from the document ;)
> 
> Sounds like good advise :)
> 
> Thanks,
> 
> Sander
>

Previous message (by thread): [ipv6-wg] next version of RIPE-501, v.2
Next message (by thread): [ipv6-wg] next version of RIPE-501, v.2

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]