<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.dasmith-mpls-ip-options" target="https://datatracker.ietf.org/doc/html/draft-dasmith-mpls-ip-options-01">
   <front>
      <title>Requirements for Label Edge Router Forwarding of IPv4 Option Packets</title>
      <author initials="W." surname="Jaeger" fullname="William Jaeger">
         <organization>AT&amp;T</organization>
      </author>
      <author initials="J." surname="Mullooly" fullname="John Mullooly">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="T." surname="Scholl" fullname="Tom Scholl">
         <organization>AT&amp;T Labs</organization>
      </author>
      <author initials="D." surname="Smith" fullname="David Smith">
         <organization>Cisco Systems</organization>
      </author>
      <date month="October" day="6" year="2008" />
      <abstract>
	 <t>This document imposes a new requirement on Label Edge Routers (LER)
specifying that when determining whether to MPLS encapsulate an IP
packet, the determination is made independent of any IP options that
may be carried in the IP packet header.  Lack of a formal standard
may result in a different forwarding behavior for different IP
packets associated with the same prefix-based Forwarding Equivalence
Class (FEC).  While an IP packet with either a specific option type
or no header option may follow the MPLS label switched path (LSP)
associated with a prefix-based FEC, an IP packet with a different
option type but associated with the same prefix-based FEC may bypass
MPLS encapsulation and instead be IP routed downstream.  IP option
packets that fail to be MPLS encapsulated simply due to their header
options present a security risk against the MPLS infrastructure.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-dasmith-mpls-ip-options-01" />
   
</reference>
