rfc9892v3.txt		rfc9892.txt
	skipping to change at line 94 ¶		skipping to change at line 94 ¶
	specification does not include any flow identification beyond DLEP		specification does not include any flow identification beyond DLEP
	endpoints, i.e., flows are identified based on their DLEP endpoint.		endpoints, i.e., flows are identified based on their DLEP endpoint.
	This document defines DLEP Data Item formats that provide flow		This document defines DLEP Data Item formats that provide flow
	identification on a more granular basis. Specifically, it enables a		identification on a more granular basis. Specifically, it enables a
	router to use traffic flow classification information provided by the		router to use traffic flow classification information provided by the
	modem to identify traffic flows based on a combination of information		modem to identify traffic flows based on a combination of information
	found in a data plane header. (For general background on traffic		found in a data plane header. (For general background on traffic
	classification, see Section 2.3 of [RFC2475].) The Data Item is		classification, see Section 2.3 of [RFC2475].) The Data Item is
	structured to allow for the use of the defined traffic classification		structured to allow for the use of the defined traffic classification
	information with applications such as credit window control as		information with applications such as credit window flow control as
	specified in [RFC9893]. [RFC9893] provides an example of combining		specified in [RFC9893]. [RFC9893] provides an example of combining
	traffic classification and credit window flow control.		traffic classification and credit window flow control.
	This document defines traffic classification based on a DLEP		This document defines traffic classification based on a DLEP
	destination and flows identified by either Differentiated Services		destination and flows identified by either Differentiated Services
	Code Points (DSCPs) [RFC2475] or IEEE 802.1Q Ethernet Priority Code		Code Points (DSCPs) [RFC2475] or IEEE 802.1Q Ethernet Priority Code
	Points (PCPs) [IEEE8021Q]. The defined mechanism allows for flows to		Points (PCPs) [IEEE8021Q]. The defined mechanism allows for flows to
	be described in a flexible fashion and, when combined with		be described in a flexible fashion and, when combined with
	applications such as credit window control, allows credit windows to		applications such as credit window flow control, allows credit
	be (1) shared across traffic sent to multiple DLEP destinations and		windows to be (1) shared across traffic sent to multiple DLEP
	as part of multiple flows or (2) used exclusively for traffic sent to		destinations and as part of multiple flows or (2) used exclusively
	a particular destination and/or belonging to a particular flow. The		for traffic sent to a particular destination and/or belonging to a
	extension also supports the "wildcard" matching of any flow (DSCP or		particular flow. The extension also supports the "wildcard" matching
	PCP). Traffic classification information is provided such that it		of any flow (DSCP or PCP). Traffic classification information is
	can be readily extended to support other traffic classification		provided such that it can be readily extended to support other
	techniques or can be used by extensions that are not related to		traffic classification techniques or can be used by extensions that
	credit windows, such as the extension defined in [RFC8651] or even		are not related to credit windows, such as the extension defined in
	5-tuple IP flows.		[RFC8651] or even 5-tuple IP flows.
	This document defines support for traffic classification using a		This document defines support for traffic classification using a
	single new Data Item (see Section 2.1) for general support and		single new Data Item (see Section 2.1) for general support and
	defines two new Sub-Data Items to support identification of flows		defines two new Sub-Data Items to support identification of flows
	based on DSCPs and PCPs (see Sections 2.2 and 2.3).		based on DSCPs and PCPs (see Sections 2.2 and 2.3).
	1.1. Key Words		1.1. Key Words
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
End of changes. 2 change blocks.
	11 lines changed or deleted		11 lines changed or added
This html diff was produced by rfcdiff 1.48.