The IPv6 Segment Endpoint Option
draft-bonica-6man-seg-end-opt-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-03-10
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
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
Intended status: Standards Track J. Halpern
Expires: September 10, 2019 Ericsson
X. Xu
Alibaba Inc
G. Chen
Baidu
Y. Zhu
G. Yang
China Telecom
March 9, 2019
The IPv6 Segment Endpoint Option
draft-bonica-6man-seg-end-opt-02
Abstract
This document defines the IPv6 Segment Endpoint Option. Source nodes
can use this option to convey internet-layer information to selected
segment endpoints along a packet's delivery path.
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 10, 2019.
Copyright Notice
Copyright (c) 2019 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
Bonica, et al. Expires September 10, 2019 [Page 1]
Internet-Draft Segment Endpoint Option March 2019
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
4. Option Format . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Option Processing . . . . . . . . . . . . . . . . . . . . . . 5
6. Mutability . . . . . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
10.1. Normative References . . . . . . . . . . . . . . . . . . 6
10.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
IPv6 [RFC8200] options convey optional internet-layer information to
selected nodes along a packets delivery path. IPv6 options can be
encoded as follows:
o In a Hop-by-hop Options header.
o In a Destination Options header that precedes a Routing header.
o In a Destination Options header that precedes an upper-layer
header.
If an option is encoded in a Hop-by-hop Options header, it conveys
information to every node along the packet's delivery path, including
the destination node. (See NOTE 1). If an option is encoded in a
Destination Options header that precedes a Routing header, it conveys
information to every segment endpoint along the packet's delivery
path, including the destination node. If an option is encoded in a
Destination Options header that precedes an upper-layer header, it
conveys information to the destination node only. (See Section 4.3.4
of [RFC8200] )
This document defines the IPv6 Segment Endpoint option. The IPv6
Segment Endpoint option provides a mechanism through which a source
Bonica, et al. Expires September 10, 2019 [Page 2]
Internet-Draft Segment Endpoint Option March 2019
node can convey optional internet-layer information to selected
Show full document text