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

"Nitin Bahadur" <nitinb@juniper.net> Thu, 28 December 2006 19:18 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H00lZ-0003nA-QR; Thu, 28 Dec 2006 14:18:13 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H00lX-0003m5-GI for mpls@ietf.org; Thu, 28 Dec 2006 14:18:11 -0500
Received: from kremlin.juniper.net ([207.17.137.120]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H00lW-0006bw-5x for mpls@ietf.org; Thu, 28 Dec 2006 14:18:11 -0500
Received: from unknown (HELO alpha.jnpr.net) ([172.24.18.126]) by kremlin.juniper.net with ESMTP; 28 Dec 2006 11:14:41 -0800
X-IronPort-AV: i="4.12,216,1165219200"; d="scan'208"; a="631683514:sNHT31425032"
Received: from electron.jnpr.net ([172.24.15.21]) by alpha.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Dec 2006 11:18:09 -0800
x-mimeole: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] draft-nadeau-mpls-interas-lspping-02.txt
Date: Thu, 28 Dec 2006 11:18:08 -0800
Message-ID: <5EB31780BD297F46812C8F495FA08F6207C8DD96@electron.jnpr.net>
In-Reply-To: <EBF874B8-45B6-4A1A-A1CF-14D311830E6F@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mpls] draft-nadeau-mpls-interas-lspping-02.txt
Thread-Index: AccqkBT5WIsZOORKSZmBE6OK3ZExAAAHRRsw
From: Nitin Bahadur <nitinb@juniper.net>
To: "Thomas D. Nadeau" <tnadeau@cisco.com>
X-OriginalArrivalTime: 28 Dec 2006 19:18:09.0021 (UTC) FILETIME=[E8B822D0:01C72AB4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
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>
Errors-To: mpls-bounces@lists.ietf.org

Hi Thomas,

The intentions and theory of operation of the draft look good. As
someone else also pointed out, please clarify behavior for ping vs
traceroute.
   
The draft does not clarify traceroutes spanning IPv4 - IPv6 - IPv4 ASes
and vice-versa. In other words, the traceroute ingress AS is IPv4 AS and
the next transit-AS is IPV6 AS. The draft does not address if this will
work and if it will; how will the visited ASBR stack and failed node
addresses look like in such scenarios. I haven't thought of this in
detail, but it seems there might be other caveats to doing
lsp-traceroute across IPv4 - IPv6 domains.

Some nits on the inter-AS lsp-ping draft.

Section 5.1.
  "The purpose of this object is to allow the upstream router to relay
a"

   I think this should be *downstream* router. Or it should be re-worded
to "to allow the router upstream of the failed node to relay a".

Failed node IP address:
   The sub-section talks about Downstream node IP address and Downstream
node Interface address. I am not clear if this is referring to the DSMAP
TLV or something else. If it is, then note that DSMAP TLV may not be
present if there was an error at the transit router.

Failed Node AS Number:
  This sub-section is repeated twice.


Thanks
Nitin

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