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/[email protected]/

[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 ]

Sander Steffann sander at steffann.nl
Sun Jul 24 22:03:40 CEST 2011

Hi,

> "When IS-IS routing protocol is requested, the equipment SHOULD support "M-ISIS: Multi-Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)" [RFC 5120] (highly recommended)"
> What do you guys think?


I would put this in 'mandatory':

- If the IS-IS routing protocol is requested the equipment MUST support "M-ISIS: Multi-Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)" [RFC 5120]

Met vriendelijke groet,
Sander Steffann

• 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 ]