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 ]
Jan Zorz @ go6.si
jan at go6.si
Sat Jul 23 00:11:39 CEST 2011
On 7/22/11 3:57 PM, Isacco Fontana wrote: > Hi, > relating on following sentence: "If MPLS Traffic Engineering is used in > combination with IS-IS routing protocol, the equipment MUST support > "M-ISIS: Multi-Topology (MT) Routing in Intermediate System to > Intermediate Systems (IS-ISs)" [RFC 5120]" > > I think the Multitopology ISIS can be used also without TE ad said in > RFC 5120 with IPv6: "This document describes how to run, within a single > IS-IS domain, a set of independent IP topologies that we call > Multi-Topologies (MTs). This MT extension can be used for a variety of > purposes, such as an in-band management network "on top" of the original > IGP topology, maintaining separate IGP routing domains for isolated > multicast or IPv6 islands within the backbone, or forcing a subset of an > address space to follow a different topology. ".... thnx for comment. What would be suggested change in text? Let's see if Ivan "mpls-master" Pepelnjak agree on proposed change :) Cheers, Jan
- 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 ]