Re: Working Group Last Call on "Multi-Topology (MT) Routing in OSPF" (draft-ietf-ospf-mt-03.txt) - Corrected

[Acee Lindem <acee at CISCO.COM>]

Yakov Rekhter wrote:

> Folks,
>
>  
>
> > This is the start of a Working Group last call for
> > "Multi-Topology (MT) Routing in OSPF" (draft-ietf-ospf-mt-03.txt).
> > All comments should be sent to this list by 12 AM (EDT), 04/19/2005.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-ospf-mt-03.txt
> >
> > The RFC 3978 IPR notices will be updated in the next revision.
> >    
>
> As the draft correctly points out:
>
>   TOS based routing as described in [RFC1583] was never
>   deployed and was subsequently deprecated.
>
> So, why computing different paths for different classes of service
> be any different ?
>  
Hi Yakov,

In addition to the differences between the two protocol mechanisms, 
we've evolved
technologically since RFC 1583. It is now fairly straight-forward to 
support multiple
topologies (protocol signaling, SPF computations, and logically separate 
RIBs/FIBs).
As for requirements, the example most often given is when a SP wants to 
provide
separate topologies for unicast and multicast services.

Note that there is a similar proposal in the ISIS WG so I'd venture to 
say that there
is some agreement on the requirement - 
draft-ietf-isis-wg-multi-topology-09.txt.

Thanks,
Acee

> Yakov.
>
>