draft-ietf-mpls-in-ip-or-gre-00.txt   draft-ietf-mpls-in-ip-or-gre-01.txt 
Network Working Group Tom Worster Network Working Group Tom Worster
Internet Draft Internet Draft
Expiration Date: July 2003 Expiration Date: January 2004
Yakov Rekhter Yakov Rekhter
Juniper Networks, Inc. Juniper Networks, Inc.
Eric C. Rosen, editor Eric C. Rosen, editor
Cisco Systems, Inc. Cisco Systems, Inc.
January 2003 July 2003
Encapsulating MPLS in IP or GRE Encapsulating MPLS in IP or GRE
draft-ietf-mpls-in-ip-or-gre-00.txt draft-ietf-mpls-in-ip-or-gre-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 5, line 18 skipping to change at page 5, line 18
reachable from the tunnel head, and if the result of this reachable from the tunnel head, and if the result of this
encapsulation would be a packet whose size exceeds the Tunnel MTU, encapsulation would be a packet whose size exceeds the Tunnel MTU,
then the tunnel head SHOULD use the Tunnel MTU value for the purposes then the tunnel head SHOULD use the Tunnel MTU value for the purposes
of fragmentation and PMTU discovery outside the tunnel. of fragmentation and PMTU discovery outside the tunnel.
4.2. TTL 4.2. TTL
The tunnel head MAY place the TTL from the MPLS label stack into the The tunnel head MAY place the TTL from the MPLS label stack into the
encapsulating IP header. The tunnel tail MAY place the TTL from the encapsulating IP header. The tunnel tail MAY place the TTL from the
encapsulating IP header into the MPLS header, but only if that does encapsulating IP header into the MPLS header, but only if that does
not cause the TTL value in the MPLS header to become smaller. not cause the TTL value in the MPLS header to become larger.
Whether such modifications are made, and the details of how they are Whether such modifications are made, and the details of how they are
made, will depend on the configuration of the tunnel tail and the made, will depend on the configuration of the tunnel tail and the
tunnel head. tunnel head.
4.3. EXP and DSCP fields 4.3. EXP and DSCP fields
The tunnel head MAY consider the EXP field of the encapsulated MPLS The tunnel head MAY consider the EXP field of the encapsulated MPLS
packet when setting the DSCP field of the encapsulating IP header. packet when setting the DSCP field of the encapsulating IP header.
The tunnel tail MAY modify the EXP field of the encapsulated MPLS The tunnel tail MAY modify the EXP field of the encapsulated MPLS
skipping to change at page 7, line 23 skipping to change at page 7, line 23
Email: fsb@thefsb.org Email: fsb@thefsb.org
Yakov Rekhter Yakov Rekhter
Juniper Networks, Inc. Juniper Networks, Inc.
1194 N. Mathilda Ave. 1194 N. Mathilda Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
Email: yakov@juniper.net Email: yakov@juniper.net
Eric Rosen Eric Rosen
Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive 1414 Massachusetts Avenue
Chelmsford, MA, 01824 Boxborough, MA 01719
e-mail: erosen@cisco.com Email: erosen@cisco.com
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/