Document Action: 'Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol' to Experimental RFC
The IESG <iesg-secretary@ietf.org> Wed, 01 September 2004 19:40 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25426; Wed, 1 Sep 2004 15:40:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2b0L-0001Qz-UZ; Wed, 01 Sep 2004 15:42:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2ajm-0003I2-OU; Wed, 01 Sep 2004 15:25:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2aeZ-0006Cx-6A; Wed, 01 Sep 2004 15:20:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23146; Wed, 1 Sep 2004 15:20:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2agl-0008KO-HT; Wed, 01 Sep 2004 15:22:35 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1C2aOt-0002Kg-Ip; Wed, 01 Sep 2004 15:04:07 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1C2aOt-0002Kg-Ip@megatron.ietf.org>
Date: Wed, 01 Sep 2004 15:04:07 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: mpls chair <swallow@cisco.com>, mpls mailing list <mpls@ietf.org>, Internet Architecture Board <iab@iab.org>, mpls chair <loa@pi.se>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Document Action: 'Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol' to Experimental RFC
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
The IESG has approved the following document: - 'Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol ' <draft-ietf-mpls-ldp-mtu-extensions-03.txt> as an Experimental RFC This document is the product of the Multiprotocol Label Switching Working Group. The IESG contact persons are Alex Zinin and Bill Fenner. Technical Summary Proper functioning of RFC 1191 path Maximum Transmission Unit (MTU) discovery requires that IP routers have knowledge of the MTU for each link to which they are connected. As currently specified, the Label Distribution Protocol (LDP) does not have the ability to signal the MTU for a Label Switched Path (LSP) to the ingress Label Switching Router (LSR). In the absence of this functionality, the MTU for each LSP must be statically configured by network operators or by equivalent, off-line mechanisms. Working Group Summary The WG originally submitted the doc for PS. However, since no implementations have been identified, the target status has been changed to Experimental. Protocol Quality The document has been reviewed for the IESG by Alex Zinin. RFC Editor Note 1. Disregard the following lines in the document header: "Updates: 3036" "Category: Standards Track" The document target status in Experimental. 2. Second para in Abstract: OLD: This document specifies extensions to LDP in support of LSP MTU discovery. NEW: This document specifies experimental extensions to LDP in support of LSP MTU discovery. 3. Section 5.1 "Interaction With LSRs Which Do Not Support MTU Signalling" OLD: Changes in MTU for sections of an LSP may cause intermediate LSRs to generate unsolicited label Mapping messages to advertise the new MTU. LSRs which do not support MTU signalling MUST accept these messages, but MAY ignore them (see Section 2.1). NEW: Changes in MTU for sections of an LSP may cause intermediate LSRs to generate unsolicited label Mapping messages to advertise the new MTU. LSRs which do not support MTU signalling will, due to message and TLV processing mechanisms specified in RFC3036 [2] accept the messages carrying the MTU TLV, but will ignore the TLV and forward the TLV to the upstream nodes (see Section 2.4). 4. Section "Security Considerations" OLD: This mechanism does not introduce any new weaknesses in LDP. It is possible to spoof TCP packets belonging to an LDP session to manipulate the LSP MTU, but LDP has mechanisms to thwart these types of attacks. NEW: This mechanism does not introduce any new weaknesses in LDP. It is possible to spoof TCP packets belonging to an LDP session to manipulate the LSP MTU, but LDP has mechanisms to thwart these types of attacks. See section 5 of [2] for more information on security aspects of LDP. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce