[mpls] draft-nadeau-mpls-interas-lspping-02.txt

"Greg Mirsky" <gmirsky@turinnetworks.com> Thu, 09 November 2006 01:06 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhyN7-000238-KA; Wed, 08 Nov 2006 20:06:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhyN6-000230-6f for mpls@ietf.org; Wed, 08 Nov 2006 20:06:24 -0500
Received: from mail.turinnetworks.com ([63.197.247.126] helo=milan.turin.turinnetworks.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhyN4-0004AL-SB for mpls@ietf.org; Wed, 08 Nov 2006 20:06:24 -0500
Received: from clavin.turin.turinnetworks.com ([10.1.1.33]) by milan.turin.turinnetworks.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Nov 2006 17:06:21 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: [mpls] draft-nadeau-mpls-interas-lspping-02.txt
Date: Wed, 08 Nov 2006 17:06:20 -0800
Message-ID: <B7C1959C59020E40B0F6456A2F1E91A5117A5C@clavin.turin.turinnetworks.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mpls] draft-nadeau-mpls-interas-lspping-02.txt
Thread-Index: AccB8TxuoLcBUAAtSeyCQwTMt4mwEwBoAzMR
References: <67FBA6A55FF15B46B8B572062529D26A059764@USDALSMBS03.ad3.ad.alcatel.com> <60FB7D3D-5B9A-492B-B3CC-A2E3C495CE33@cisco.com>
From: Greg Mirsky <gmirsky@turinnetworks.com>
To: "Thomas D. Nadeau" <tnadeau@cisco.com>
X-OriginalArrivalTime: 09 Nov 2006 01:06:21.0287 (UTC) FILETIME=[44D36F70:01C7039B]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: mpls@ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1484719401=="
Errors-To: mpls-bounces@lists.ietf.org

Dear Tom,
please find my comments to this document below (extending my question asked earlier today):
- in Section 4. Motivation written "In this case, it is commonly desirable for providers to NOT distribute the IP addresses of any of the intermediate P routers between PE1 and PE2." I think that not distributing addresses of intermediate routers would not contribute to the problem addressed in the document. Perhaps it was meant to state that addresses of LSP LERs, PE1 and PE2, might be not advertised into other provider's AS. 
- further in Section 4 said "However, because the address of PE1 is actually private to AS1 by virtue of not being distributed by ASBR1 into AS2, the P router cannot correctly forward the reply to PE1." If an AS can be characterized as "stub" AS then it is unlikely that its operator wants traffic from other ASes to traverse it. If AS, as a whole, is not stub but only part of it, e.g. OSPF stub area, then a default route must be injected by ABR into the stub area. The default route will provide "exit" for intermediate LSR P when it sends LSP Echo Reply message to the PE1. Perhaps input from network operators will help to clarify if addressed scenario is likely to happen.

Regards,
Greg
_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls