OSPF inter-AS extensions for GMPLS (RFC5392) questions

"Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com> Thu, 05 March 2009 07:52 UTC

Envelope-to: ccamp-data0@psg.com
Delivery-date: Thu, 05 Mar 2009 07:54:51 +0000
From: "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com>
To: <ccamp@ops.ietf.org>
Subject: OSPF inter-AS extensions for GMPLS (RFC5392) questions
Date: Thu, 5 Mar 2009 08:52:56 +0100
Message-ID: <012001c99d67$69d04920$b407a8c0@marbenproducts.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcmdZ2UnkMtM9RPdS/+AzCunXMthmA==

Hello,

Sorry to come a little late on this but I have a question on inter-AS
extensions RFC5392 (also applicable on ISIS extensions).
In section 4:
" Only some essential TE information for the link needs to be
   advertised; i.e., the Link Type, the Remote AS number, and the Remote
   ASBR ID."

First what does "remote" mean here? is it remote in the context of the
proxied link or in the context of the Router?
i.e.

RouterA in AS1 ------TE Link------ RouterB in AS2

I guess it is in the context of the link. That is in LSA generated by router
A for B->A link (proxied) we put AS1 and routerA ASBR Id. Is that correct?

Second question: I'm not sure about the purpose of "only some essential TE
information for the link needs to be advertised" sentence.
Does it mean it not allowed to put other information like bandwidth,
protection type? (in case the link has asymetric characteristic)
Besides I think another essential information is the remote link Id or
remote IP address in order to correlate the proxied B->A link with the A->B
link.
Do you agree?


Thanks
Fabien

-----------------------------------

Fabien Verhaeghe (Senior consultant)
Marben Products