IPv6 Hop-by-Hop Options Processing Procedures
draft-hinden-6man-hbh-processing-00
Network Working Group R. Hinden
Internet-Draft Check Point Software
Updates: 8200 (if approved) G. Fairhurst
Intended status: Standards Track University of Aberdeen
Expires: 6 June 2021 3 December 2020
IPv6 Hop-by-Hop Options Processing Procedures
draft-hinden-6man-hbh-processing-00
Abstract
This document specifies procedures for how IPv6 Hop-by-Hop options
are processed. It modifies the procedures specified in the IPv6
Protocol Specification (RFC8200) to make processing in routers more
practical with the goal of making IPv6 Hop-by-Hop options useful to
deploy in the Internet. When published, this document updates
RFC8200.
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 6 June 2021.
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
Hinden & Fairhurst Expires 6 June 2021 [Page 1]
Internet-Draft HBH Options Processing December 2020
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. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Background . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Hop-by-Hop Header Processing Procedures . . . . . . . . . . . 5
5.1. Hop-by-Hop Options Per Packet . . . . . . . . . . . . . . 5
5.2. Hop-by-Hop Headers Processing . . . . . . . . . . . . . . 6
5.3. Configuration . . . . . . . . . . . . . . . . . . . . . . 6
6. Hop-by-Hop Option Header Alignment . . . . . . . . . . . . . 7
6.1. Hop-by-Hop Options that Meet Alignment Requirement . . . 7
6.2. Hop-by-Hop Options that Must be Deprecated or Modified . 8
6.3. Destination Options and Deprecated Hop-by-Hop Options . . 8
7. New Hop-by-Hop Options . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
9. Security Considerations . . . . . . . . . . . . . . . . . . . 8
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
11. Change log [RFC Editor: Please remove] . . . . . . . . . . . 8
12. Normative References . . . . . . . . . . . . . . . . . . . . 9
13. Informative References . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
This document specifies procedures for how IPv6 Hop-by-Hop options
are processed. It modifies the procedures specified in the IPv6
Protocol Specification (RFC8200) to make processing in routers more
practical with the goal of making IPv6 Hop-by-Hop options useful to
deploy in the Internet.
When published this document updates [RFC8200].
The current list of defined Hop-by-Hop options can be found at
[IANA-HBH].
2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Hinden & Fairhurst Expires 6 June 2021 [Page 2]
Internet-Draft HBH Options Processing December 2020
3. Terminology
This document uses the following loosely defined terms:
* Fast path: Hardware or Application-Specific Integrated Circuit
(ASIC) processing path for packets. This is the usual processing
Show full document text