Inserting, Processing And Deleting IPv6 Extension Headers
draft-bonica-6man-ext-hdr-update-03
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-03-16
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
6man R. Bonica
Internet-Draft Juniper Networks
Updates: RFC 8200 (if approved) T. Jinmei
Intended status: Standards Track Infoblox
Expires: September 17, 2020 March 16, 2020
Inserting, Processing And Deleting IPv6 Extension Headers
draft-bonica-6man-ext-hdr-update-03
Abstract
This document provides guidance regarding the processing, insertion
and deletion of IPv6 extension headers. It updates RFC 8200.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 17, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Bonica & Jinmei Expires September 17, 2020 [Page 1]
Internet-Draft IPv6 Extension Headers March 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Updates To RFC 8200 . . . . . . . . . . . . . . . . . . . . . 3
3.1. Original Text . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Updated Text . . . . . . . . . . . . . . . . . . . . . . 4
4. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
8. Normative References . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
In IPv6 [RFC8200] optional internet-layer information is encoded in
extension headers. As specified by [RFC8200], "extension headers
(except for the Hop-by-Hop Options header) are not processed,
inserted, or deleted by any node along a packet's delivery path,
until the packet reaches the node (or each of the set of nodes, in
the case of multicast) identified in the Destination Address field of
the IPv6 header".
The statement quoted above identifies nodes upon which extension
headers are not processed, inserted or deleted. It does not imply
that extension headers can be processed, inserted or deleted on any
other node along a packet's delivery path.
This document provides guidance regarding the processing, insertion
and deletion of IPv6 extension headers. It clarifies the statement
quoted above and updates [RFC8200].
2. Terminology
The following terms are used in this document:
o Source node - An IPv6 source node accepts data from an upper-layer
protocol, prepends an IPv6 header, and sends the resulting IPv6
packet to a destination node.
o Final destination node - An IPv6 final destination node receives
an IPv6 packet and delivers its payload to an upper-layer
protocol. If a packet contains a Routing header, its destination
address may represent an interface that belongs to a node other
than the final destination node.
Bonica & Jinmei Expires September 17, 2020 [Page 2]
Internet-Draft IPv6 Extension Headers March 2020
o Delivery path - A packet's delivery path is a series of nodes that
a packet traverses on route to its final destination. The
delivery path includes the final destination node.
o Segment - A segment is a series of links and nodes in a packet's
delivery path. An IPv6 Routing header steers packets from segment
to segment along the delivery path. If a packet contains a
Show full document text