Source routed Notify message

["Diego Caviglia" <Diego.Caviglia@marconi.com>]

Hi all,
              is there anyone interested in having source routed, may by
means of standard ERO obj, Notify [RFC3473] message?

The motivation to use a source routing mechanism for Notify is avoiding
OSPF convergence time during a network failure.

The scenario I've in mind is the following:

            A---------------B---------------C
            |               |               |
            |               |               |
            |               |               |
            D---------------E---------------F
            |               |               |
            |               |               |
            |               |               |
            G---------------H---------------H

Suppose there is a LSP (SDN/SONET) from H (Ingress) to A (Egress) and an
unidirectional failure occours between C and F in the H-->A direction.
Low layer mechanism (e.g AIS), informs A that a failure has occourred.  TNE
A wants to notify H about the failure but OSPF tables have not been updated
thus TNA A knows that "normal routing" will have some problem in delivering
the Notify to TNE H.

A source routed path calculated using Link diversity with respect to the
failed LSP can avoid OSPF convergence time and inform efficently TNE H
about the failure of the LSP.

That can be done either using the source route of the Ip header or using
the ERO object.  The former has some limitation while the latter is
larghely used in GMPLS.

Ragrds

Diego