[mpls] A question about RFC 4379 "Detecting MPLS Data Plane Failures"
Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Wed, 20 June 2012 14:11 UTC
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F0B721F8724 for <mpls@ietfa.amsl.com>; Wed, 20 Jun 2012 07:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tsi5OL2fZvyD for <mpls@ietfa.amsl.com>; Wed, 20 Jun 2012 07:11:13 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.34]) by ietfa.amsl.com (Postfix) with ESMTP id 21A0021F870B for <mpls@ietf.org>; Wed, 20 Jun 2012 07:11:12 -0700 (PDT)
Received: from [85.158.138.51:3733] by server-9.bemta-3.messagelabs.com id 64/E2-10419-FF9D1EF4; Wed, 20 Jun 2012 14:11:11 +0000
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-9.tower-174.messagelabs.com!1340201464!28715583!1
X-Originating-IP: [168.87.1.157]
X-StarScan-Version: 6.5.10; banners=-,-,-
Received: (qmail 3122 invoked from network); 20 Jun 2012 14:11:04 -0000
Received: from unknown (HELO fridlpvsb005.ecitele.com) (168.87.1.157) by server-9.tower-174.messagelabs.com with SMTP; 20 Jun 2012 14:11:04 -0000
X-AuditID: a8571406-b7f656d0000010a7-9f-4fe1d9f6af6b
Received: from FRIDWPPCH002.ecitele.com (fridwppch002.ecitele.com [10.1.16.53]) by fridlpvsb005.ecitele.com (Symantec Messaging Gateway) with SMTP id AA.FD.04263.6F9D1EF4; Wed, 20 Jun 2012 16:11:02 +0200 (CEST)
Received: from FRIDWPPMB001.ecitele.com ([169.254.3.23]) by FRIDWPPCH002.ecitele.com ([10.1.16.53]) with mapi id 14.01.0339.001; Wed, 20 Jun 2012 16:10:58 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "kireeti@juniper.net" <kireeti@juniper.net>, "swallow@cisco.com" <swallow@cisco.com>
Thread-Topic: A question about RFC 4379 "Detecting MPLS Data Plane Failures"
Thread-Index: Ac1O7oIIKGcMgCvNTI29FIMsYNRQ/A==
Date: Wed, 20 Jun 2012 14:10:56 +0000
Message-ID: <F9336571731ADE42A5397FC831CEAA02093A51@FRIDWPPMB001.ecitele.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.4.42.92]
Content-Type: multipart/alternative; boundary="_000_F9336571731ADE42A5397FC831CEAA02093A51FRIDWPPMB001ecite_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA3VTbUgTYRzv2W2303Z1zukeh8RxEUHlmJSwwI0KQ6XEyKKQcF3b03a03Y3d NO1Lyz5E9iEL6WUUWa1Se7HWh5L8YCaUL5QfknzrRdQwCwmjV1F6zksTovv0e/6/F37P3f8o wjhOWihBDKOQyPs5MlGbCBZZMr71DRXaGtpS7T8exvX2/mv1OvtATSXYQOTVTN3T5cViPzV5 ryp79NuI4gjI5kVRCvNhxHqQ7HZw20JCGe+u4FjB4+AyOTbo590ogMSwg+ODQSR6OGci+8+T jWWCyCLRLXkE0evg8osKM+z2rPUZmZxzh0+QWZQR4AU/G0CyzHsRiydKb9Gz9w7h+9w9qA++ Lyi/0P1FFwEnc6pAAgWZdXD6Ra1Wxamw+00jWQUSKSPzEsA7LT/+HGIA9rUO6hQVyThg/OZr UsEmphjePvJs1k0w2+HF9lGg4GQmF3Y1xTCmsGYrPNa5W5Vb4YeRBr2CtcwKeOL61dlImimA kcHp2RiAS3zvuKVRI82wf+SSRi3HwFjzC0LFKfDD8IxOxctgZf1LvaqXYPNME6lmJsH28yN/ LpYGH9f1aquBKbogNrrAEl1gUedrYO2jSVLFq+H1yx+JOdzVMqxZOK8F+gYA94cEjz9YJu+z 2bKsyC2EkR9Z3VIgDvDC1O0ykQ9BpNraChgKcAa6Lmuo0Kjjy+SKQCtIozRcCl3Qi0dL9kme Ch8v+1yhUj+SWwGkCM5Ej93FHO3hKw6hkDRHbcYv8RRhWeyWlE8cdq212f5/4Mx043ZnoZHx 4iU8gFAQheZy0imKg7QTr7MxKYS8qHy/4A//pTVUglLDgGtkKxpaDvIBWfCqfAdIs5jpVIVg FMJXKs57x4EZXzaZzlFYA17Eedc4DtTgwF+575RA/GPMU5YIcG05ntZ5+Keh7Yk0tVNX0nFm wFU21nHWLK0sKunquxi9v0NX3jgqnK4mD6cEl5j6Z/wPiNHMo3lvS5InPp2Tx6n0XNOeUp9L POhi4w5X9aaJZ2uuTManlkeeHml6PrA0bLj69Ub7op4ioq3zU1vW4gsbnMWu6ZXW/OaR5vSN M1FOK/v4zFVESOZ/AyHhmPP9AwAA
Cc: "mpls@ietf.org" <mpls@ietf.org>, Evgeny Sandler <Evgeny.Sandler@ecitele.com>
Subject: [mpls] A question about RFC 4379 "Detecting MPLS Data Plane Failures"
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 14:11:15 -0000
Kireeti and Gorge, hi! My colleague and I have found the following test in Section 4.5 "Sending an MPLS Echo Reply" of RFC 4379<http://datatracker.ietf.org/doc/rfc4379/?include_text=1>: If the Reply Mode in the echo request is "Reply via an IPv4 UDP packet with Router Alert", then the IP header MUST contain the Router Alert IP option. If the reply is sent over an LSP, the topmost label MUST in this case be the Router Alert label (1) (see [LABEL-STACK]). I think that this text admits two different interpretations: 1. Always add the Router Alert label on top of the label stack of the LSP thru which the MPLS Echo reply is sent 2. Add the Router Alert label on top of the label stack of the LSP thru which the MPLS Echo reply is sent if the requested reply mode is "Reply with Router Alert". The ambiguity exists because: 1. The text is broken into two sentences separated by full stop 2. The meaning of "this case" in the 2nd sentence is not clear. My gut feeling is that the 2nd interpretation is correct, but no the 1st. Did I miss something? If not, do you think a new erratum is required? (I've checked the current ones, and they do not deal with this issue). Regards, and lots of thanks in advance, Sasha This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof.
- [mpls] A question about RFC 4379 "Detecting MPLS … Alexander Vainshtein