[rfc-dist] RFC 3988 on Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Wed Feb 2 12:42:06 PST 2005


A new Request for Comments is now available in online RFC libraries.


        RFC 3988

        Title:      Maximum Transmission Unit Signalling Extensions
                    for the Label Distribution Protocol
        Author(s):  B. Black, K. Kompella
        Status:     Experimental
        Date:       January 2005
        Mailbox:    ben at layer8.net, kireeti at juniper.net
        Pages:      9
        Characters: 18841
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mpls-ldp-mtu-extensions-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3988.txt


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.

This document specifies experimental extensions to LDP in support
of LSP MTU discovery.

This document is a product of the Multiprotocol Label Switching
Working Group of the IETF.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  Distribution of this memo
is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative


More information about the rfc-dist mailing list