Re: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt

[Yakov Rekhter <yakov@juniper.net>]

Raymond,

[clipped..]

> > > Can you propose some wording which can be incorporated into the final
> > > version after the last call commenting period ?
> >
> >Here is the proposed text, although I think that the text has to be
> >incorporated *prior* (and not after) the last call commenting period.
> 
> Surely.. I will post -05 for it.
> 
> >In  5.1.5 replace
> >     Once an inter-AS TE LSP has been established and should there be any
> >     resource or other changes inside anyone of transiting ASes, the
> >     solution MUST be able to re-optimize the LSP accordingly and
> >     non-disruptively, either upon expiration of a configurable timer or
> >     triggered by a network event or a manual request at the TE tunnel
> >     Head-end.
> >
> >     The solution SHOULD provide an option for the Head-End LSRs to
> >     control if re-optimizing or not should there exist a more optimal
> >     path in one of the transit ASes along the inter-AS TE LSP path.
> > 
> >with the following:
> >
> >     Once an inter-AS TE LSP has been established and should there be any
> >     resource or other changes inside anyone of the ASes, the
> >     solution MUST be able to re-optimize the LSP accordingly and
> >     non-disruptively, either upon expiration of a configurable timer or
> >     triggered by a network event or a manual request at the TE tunnel
> >     Head-end.
> >
> >     The solution SHOULD provide an option for the Head-End LSRs to
> >     control if re-optimizing or not should there exist a more optimal
> >     path in one of the ASes.

I am quite suprprised (to say the least) that after you agreed with
the change I proposed to 5.1.5, the -05 version still has doesn't fully 
incorporate that change. Specifically, the first sentence in 5.1.5 is 
still from the old text. 

Yakov.