< draft-ietf-v6ops-ipv6-ehs-packet-drops-04.txt		draft-ietf-v6ops-ipv6-ehs-packet-drops-05.txt >
	IPv6 Operations Working Group (v6ops) F. Gont		IPv6 Operations Working Group (v6ops) F. Gont
	Internet-Draft SI6 Networks		Internet-Draft SI6 Networks
	Intended status: Informational N. Hilliard		Intended status: Informational N. Hilliard
	Expires: August 14, 2021 INEX		Expires: August 15, 2021 INEX
	G. Doering		G. Doering
	SpaceNet AG		SpaceNet AG
	W. Kumari		W. Kumari
	Google		Google
	G. Huston		G. Huston
	APNIC		APNIC
	W. Liu		W. Liu
	Huawei Technologies		Huawei Technologies
	February 10, 2021		February 11, 2021
	Operational Implications of IPv6 Packets with Extension Headers		Operational Implications of IPv6 Packets with Extension Headers
	draft-ietf-v6ops-ipv6-ehs-packet-drops-04		draft-ietf-v6ops-ipv6-ehs-packet-drops-05
	Abstract		Abstract
	This document summarizes the operational implications of IPv6		This document summarizes the operational implications of IPv6
	extension headers specified in the IPv6 protocol specification		extension headers specified in the IPv6 protocol specification
	(RFC8200), and attempts to analyze reasons why packets with IPv6		(RFC8200), and attempts to analyze reasons why packets with IPv6
	extension headers are often dropped in the public Internet.		extension headers are often dropped in the public Internet.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 42 ¶		skipping to change at page 1, line 42 ¶
	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 August 14, 2021.		This Internet-Draft will expire on August 15, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 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 7, line 23 ¶		skipping to change at page 7, line 23 ¶
	next-hop. Technical constraints mean that there is a trade-off		next-hop. Technical constraints mean that there is a trade-off
	between the amount of data sent to the lookup engine and the overall		between the amount of data sent to the lookup engine and the overall
	performance of the lookup engine. If more data is sent, the lookup		performance of the lookup engine. If more data is sent, the lookup
	engine can inspect further into the packet, but the overall		engine can inspect further into the packet, but the overall
	performance of the system will be reduced. If less data is sent, the		performance of the system will be reduced. If less data is sent, the
	overall performance of the router will be increased but the packet		overall performance of the router will be increased but the packet
	lookup engine may not be able to inspect far enough into a packet to		lookup engine may not be able to inspect far enough into a packet to
	determine how it should be handled.		determine how it should be handled.
	NOTE:		NOTE:
	For example, some contemporary high-end routers are known to use		For example, some contemporary high-end routers are known to
	up to 192 bytes or 384 bytes of header.		inspect up to 192 bytes, while others are known to parse up to 384
			bytes of header.
	If a hardware forwarding engine on a contemporary router cannot make		If a hardware forwarding engine on a contemporary router cannot make
	a forwarding decision about a packet because critical information is		a forwarding decision about a packet because critical information is
	not sent to the look-up engine, then the router will normally drop		not sent to the look-up engine, then the router will normally drop
	the packet. Section 6 discusses some of the reasons for which a		the packet. Section 6 discusses some of the reasons for which a
	contemporary router might need to access layer-4 information to make		contemporary router might need to access layer-4 information to make
	a forwarding decision.		a forwarding decision.
	Historically, some packet forwarding engines punted packets of this		Historically, some packet forwarding engines punted packets of this
	form to the control plane for more in-depth analysis, but this is		form to the control plane for more in-depth analysis, but this is
End of changes. 5 change blocks.
	6 lines changed or deleted		7 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/