Re: [ Àüüȸ½Å ] spc connections

["Adrian Farrel" <adrian@olddog.co.uk>]

Jonathan,

Thanks for helping to nail down these requirement issues.

> > - G.7713.2/RFC 3474 can not support inter-as *te* ?
> I'm not certain how to parse your question -- could you please clarify?

On the subject of inter-AS TE, I think Dimitri is thinking as follows...

You said:

> > > realized acrossed a service provider's network. However, the ERO is an
> > > attribute of a connection, not a call, and may not necessarily be passed
> > > over the E-NNI reference point.  Consequently, the use of explicit label
> > > control in an ERO is not a possible way to handle SPCs that traverse an
> > > E-NNI.  This is why the egress point identification appears in the call
> > > object in G.7713.2.

Inter-AS, head-end-controlled TE requires that the ERO may include some 
information to help control the path on the other side of the E-NNI (if we
assume that the E-NNI lies on an AS boundary).

Your statement that the ERO "may not necessarily be passed over the
E-NNI" suggests that this form of TE cannot be applied.

I wonder if you could clarify "may not necessarily". What are the constraints?

Cheers,
Adrian