draft-ietf-idr-tunnel-encaps-18.txt   draft-ietf-idr-tunnel-encaps-19.txt 
IDR Working Group K. Patel IDR Working Group K. Patel
Internet-Draft Arrcus, Inc Internet-Draft Arrcus, Inc
Obsoletes: 5512, 5566, 5640 (if G. Van de Velde Obsoletes: 5512, 5566, 5640 (if G. Van de Velde
approved) Nokia approved) Nokia
Intended status: Standards Track S. Sangli Intended status: Standards Track S. Sangli
Expires: March 15, 2021 J. Scudder Expires: March 22, 2021 J. Scudder
Juniper Networks Juniper Networks
September 11, 2020 September 18, 2020
The BGP Tunnel Encapsulation Attribute The BGP Tunnel Encapsulation Attribute
draft-ietf-idr-tunnel-encaps-18 draft-ietf-idr-tunnel-encaps-19
Abstract Abstract
RFC 5512 defines a BGP Path Attribute known as the "Tunnel RFC 5512 defines a BGP Path Attribute known as the "Tunnel
Encapsulation Attribute". This attribute allows one to specify a set Encapsulation Attribute". This attribute allows one to specify a set
of tunnels. For each such tunnel, the attribute can provide the of tunnels. For each such tunnel, the attribute can provide the
information needed to create the tunnel and the corresponding information needed to create the tunnel and the corresponding
encapsulation header. The attribute can also provide information encapsulation header. The attribute can also provide information
that aids in choosing whether a particular packet is to be sent that aids in choosing whether a particular packet is to be sent
through a particular tunnel. RFC 5512 states that the attribute is through a particular tunnel. RFC 5512 states that the attribute is
skipping to change at page 2, line 7 skipping to change at page 2, line 7
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 15, 2021. This Internet-Draft will expire on March 22, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 10, line 51 skipping to change at page 10, line 51
* 22, if the Address Family subfield contains the value for IPv6. * 22, if the Address Family subfield contains the value for IPv6.
* 6, if the Address Family subfield contains the value zero. * 6, if the Address Family subfield contains the value zero.
o The IP address in the sub-TLV's address subfield lies within a o The IP address in the sub-TLV's address subfield lies within a
block listed in the relevant Special-Purpose IP Address Registry block listed in the relevant Special-Purpose IP Address Registry
[RFC6890] with either a "destination" attribute value or a [RFC6890] with either a "destination" attribute value or a
"forwardable" attribute value of "false". (Such routes are "forwardable" attribute value of "false". (Such routes are
sometimes colloquially known as "Martians".) sometimes colloquially known as "Martians".)
o It can be determined according to the procedures below o It can be determined that the IP address in the sub-TLV's address
(Section 3.1.1) that the IP address in the sub-TLV's address
subfield does not belong to the Autonomous System (AS) that subfield does not belong to the Autonomous System (AS) that
originated the route that contains the attribute. originated the route that contains the attribute. Section 3.1.1
describes an optional procedure to make this determination.
Error Handling is detailed in Section 12. Error Handling is detailed in Section 12.
If the Tunnel Egress Endpoint sub-TLV contains an IPv4 or IPv6 If the Tunnel Egress Endpoint sub-TLV contains an IPv4 or IPv6
address that is valid but not reachable, the sub-TLV is not address that is valid but not reachable, the sub-TLV is not
considered to be malformed. considered to be malformed.
3.1.1. Validating the Address Field 3.1.1. Validating the Address Field
This section details a procedure that MAY be applied to validate that This section details a procedure that MAY be applied to validate that
skipping to change at page 27, line 15 skipping to change at page 27, line 15
* The Tunnel Type is supported (i.e., router R knows how to set * The Tunnel Type is supported (i.e., router R knows how to set
up tunnels of that type, how to create the encapsulation header up tunnels of that type, how to create the encapsulation header
for tunnels of that type, etc.) for tunnels of that type, etc.)
* The tunnel is of a type that can be used to carry packet P * The tunnel is of a type that can be used to carry packet P
(e.g., an MPLS-in-UDP tunnel would not be a feasible tunnel for (e.g., an MPLS-in-UDP tunnel would not be a feasible tunnel for
carrying an IP packet, unless the IP packet can first be carrying an IP packet, unless the IP packet can first be
encapsulated in a MPLS packet). encapsulated in a MPLS packet).
* The tunnel is specified in a TLV whose Tunnel Egress Endpoint * The tunnel is specified in a TLV whose Tunnel Egress Endpoint
sub-TLV identifies an IP address that is reachable. This IP sub-TLV identifies an IP address that is reachable. The
address may be reachable via one or more forwarding tables. reachability condition is evaluated as per [RFC4271]. If the
Local policy may determine these forwarding tables and is IP address is reachable via more than one forwarding table,
outside the scope of this document. The reachability condition local policy is used to determine which table to use.
is evaluated as per [RFC4271], but the essence is that if the
router could forward a packet addressed to the IP address, the
IP address is "reachable".
* There is no local policy that prevents the use of the tunnel. * There is no local policy that prevents the use of the tunnel.
Then router R MUST send packet P through one of the feasible tunnels Then router R MUST send packet P through one of the feasible tunnels
identified in the Tunnel Encapsulation attribute of UPDATE U. identified in the Tunnel Encapsulation attribute of UPDATE U.
If the Tunnel Encapsulation attribute contains several TLVs (i.e., if If the Tunnel Encapsulation attribute contains several TLVs (i.e., if
it specifies several feasible tunnels), router R may choose any one it specifies several feasible tunnels), router R may choose any one
of those tunnels, based upon local policy. If any Tunnel TLV of those tunnels, based upon local policy. If any Tunnel TLV
contains one or more Color sub-TLVs (Section 3.4.2) and/or the contains one or more Color sub-TLVs (Section 3.4.2) and/or the
 End of changes. 7 change blocks. 
14 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/