[rfc-dist] RFC 6178 on Label Edge Router Forwarding of IPv4 Option Packets

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Tue Mar 15 17:35:25 PDT 2011

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

        RFC 6178

        Title:      Label Edge Router Forwarding of 
                    IPv4 Option Packets 
        Author:     D. Smith, J. Mullooly,
                    W. Jaeger, T. Scholl
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2011
        Mailbox:    djsmith at cisco.com, 
                    jmullool at cisco.com, 
                    wjaeger at att.com,  tscholl at nlayer.net
        Characters: 21645
        Updates:    RFC3031

        I-D Tag:    draft-ietf-mpls-ip-options-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6178.txt

This document specifies how Label Edge Routers (LERs) should behave
when determining whether to MPLS encapsulate an IPv4 packet with
header options.  Lack of a formal standard has resulted in different
LER forwarding behaviors for IPv4 packets with header options despite
being associated with a prefix-based Forwarding Equivalence Class
(FEC).  IPv4 option packets that belong to a prefix-based FEC, yet
are forwarded into an IPv4/MPLS network without being MPLS-
encapsulated, present a security risk against the MPLS
infrastructure.  Further, LERs that are unable to MPLS encapsulate
IPv4 packets with header options cannot operate in certain MPLS
environments.  While this newly defined LER behavior is mandatory to
implement, it is optional to invoke.  [STANDARDS-TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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

The RFC Editor Team
Association Management Solutions, LLC

More information about the rfc-dist mailing list