< draft-ietf-manet-dlep-21.txt		draft-ietf-manet-dlep-22.txt >
	Mobile Ad hoc Networks Working Group S. Ratliff		Mobile Ad hoc Networks Working Group S. Ratliff
	Internet-Draft VT iDirect		Internet-Draft VT iDirect
	Intended status: Standards Track B. Berry		Intended status: Standards Track B. Berry
	Expires: September 22, 2016		Expires: October 9, 2016
	S. Jury		S. Jury
	Cisco Systems		Cisco Systems
	D. Satterwhite		D. Satterwhite
	Broadcom		Broadcom
	R. Taylor		R. Taylor
	Airbus Defence & Space		Airbus Defence & Space
	March 21, 2016		April 7, 2016
	Dynamic Link Exchange Protocol (DLEP)		Dynamic Link Exchange Protocol (DLEP)
	draft-ietf-manet-dlep-21		draft-ietf-manet-dlep-22
	Abstract		Abstract
	When routing devices rely on modems to effect communications over		When routing devices rely on modems to effect communications over
	wireless links, they need timely and accurate knowledge of the		wireless links, they need timely and accurate knowledge of the
	characteristics of the link (speed, state, etc.) in order to make		characteristics of the link (speed, state, etc.) in order to make
	routing decisions. In mobile or other environments where these		routing decisions. In mobile or other environments where these
	characteristics change frequently, manual configurations or the		characteristics change frequently, manual configurations or the
	inference of state through routing or transport protocols does not		inference of state through routing or transport protocols does not
	allow the router to make the best decisions. A bidirectional, event-		allow the router to make the best decisions. A bidirectional, event-
	skipping to change at page 1, line 44 ¶		skipping to change at page 1, line 45 ¶
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 September 22, 2016.		This Internet-Draft will expire on October 9, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	skipping to change at page 2, line 26 ¶		skipping to change at page 2, line 29 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
	1.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 7		1.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 7
	2. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 7		2. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 7
	2.1. Assumptions . . . . . . . . . . . . . . . . . . . . . . . 9		2.1. Assumptions . . . . . . . . . . . . . . . . . . . . . . . 9
	3. Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . 9		3. Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	4. DLEP Session Flow . . . . . . . . . . . . . . . . . . . . . . 10		4. DLEP Session Flow . . . . . . . . . . . . . . . . . . . . . . 10
	4.1. Peer Discovery State . . . . . . . . . . . . . . . . . . 11		4.1. Peer Discovery State . . . . . . . . . . . . . . . . . . 11
	4.2. Session Initialization State . . . . . . . . . . . . . . 11		4.2. Session Initialization State . . . . . . . . . . . . . . 12
	4.3. In-Session State . . . . . . . . . . . . . . . . . . . . 12		4.3. In-Session State . . . . . . . . . . . . . . . . . . . . 12
	4.3.1. Heartbeats . . . . . . . . . . . . . . . . . . . . . 12		4.3.1. Heartbeats . . . . . . . . . . . . . . . . . . . . . 13
	4.4. Session Termination State . . . . . . . . . . . . . . . . 13		4.4. Session Termination State . . . . . . . . . . . . . . . . 13
	4.5. Session Reset state . . . . . . . . . . . . . . . . . . . 13		4.5. Session Reset state . . . . . . . . . . . . . . . . . . . 14
	4.5.1. Unexpected TCP connection termination . . . . . . . . 14		4.5.1. Unexpected TCP connection termination . . . . . . . . 14
	5. Transaction Model . . . . . . . . . . . . . . . . . . . . . . 14		5. Transaction Model . . . . . . . . . . . . . . . . . . . . . . 14
	6. Extensions . . . . . . . . . . . . . . . . . . . . . . . . . 15		6. Extensions . . . . . . . . . . . . . . . . . . . . . . . . . 15
	6.1. Experiments . . . . . . . . . . . . . . . . . . . . . . . 15		6.1. Experiments . . . . . . . . . . . . . . . . . . . . . . . 15
	7. Scalability . . . . . . . . . . . . . . . . . . . . . . . . . 16		7. Scalability . . . . . . . . . . . . . . . . . . . . . . . . . 16
	8. DLEP Signal and Message Structure . . . . . . . . . . . . . . 16		8. DLEP Signal and Message Structure . . . . . . . . . . . . . . 16
	8.1. DLEP Signal Header . . . . . . . . . . . . . . . . . . . 16		8.1. DLEP Signal Header . . . . . . . . . . . . . . . . . . . 17
	8.2. DLEP Message Header . . . . . . . . . . . . . . . . . . . 17		8.2. DLEP Message Header . . . . . . . . . . . . . . . . . . . 17
	8.3. DLEP Generic Data Item . . . . . . . . . . . . . . . . . 17		8.3. DLEP Generic Data Item . . . . . . . . . . . . . . . . . 18
	9. DLEP Signals and Messages . . . . . . . . . . . . . . . . . . 18		9. DLEP Signals and Messages . . . . . . . . . . . . . . . . . . 19
	9.1. General Processing Rules . . . . . . . . . . . . . . . . 19		9.1. General Processing Rules . . . . . . . . . . . . . . . . 20
	9.2. Status code processing . . . . . . . . . . . . . . . . . 20		9.2. Status code processing . . . . . . . . . . . . . . . . . 21
	9.3. Peer Discovery Signal . . . . . . . . . . . . . . . . . . 21		9.3. Peer Discovery Signal . . . . . . . . . . . . . . . . . . 21
	9.4. Peer Offer Signal . . . . . . . . . . . . . . . . . . . . 21		9.4. Peer Offer Signal . . . . . . . . . . . . . . . . . . . . 22
	9.5. Session Initialization Message . . . . . . . . . . . . . 22		9.5. Session Initialization Message . . . . . . . . . . . . . 22
	9.6. Session Initialization Response Message . . . . . . . . . 22		9.6. Session Initialization Response Message . . . . . . . . . 23
	9.7. Session Update Message . . . . . . . . . . . . . . . . . 24		9.7. Session Update Message . . . . . . . . . . . . . . . . . 25
	9.8. Session Update Response Message . . . . . . . . . . . . . 25		9.8. Session Update Response Message . . . . . . . . . . . . . 26
	9.9. Session Termination Message . . . . . . . . . . . . . . . 25		9.9. Session Termination Message . . . . . . . . . . . . . . . 26
	9.10. Session Termination Response Message . . . . . . . . . . 26		9.10. Session Termination Response Message . . . . . . . . . . 27
	9.11. Destination Up Message . . . . . . . . . . . . . . . . . 26		9.11. Destination Up Message . . . . . . . . . . . . . . . . . 27
	9.12. Destination Up Response Message . . . . . . . . . . . . . 27		9.12. Destination Up Response Message . . . . . . . . . . . . . 28
	9.13. Destination Announce Message . . . . . . . . . . . . . . 28		9.13. Destination Announce Message . . . . . . . . . . . . . . 29
	9.14. Destination Announce Response Message . . . . . . . . . . 28		9.14. Destination Announce Response Message . . . . . . . . . . 29
	9.15. Destination Down Message . . . . . . . . . . . . . . . . 30		9.15. Destination Down Message . . . . . . . . . . . . . . . . 31
	9.16. Destination Down Response Message . . . . . . . . . . . . 30		9.16. Destination Down Response Message . . . . . . . . . . . . 31
	9.17. Destination Update Message . . . . . . . . . . . . . . . 30		9.17. Destination Update Message . . . . . . . . . . . . . . . 31
	9.18. Link Characteristics Request Message . . . . . . . . . . 32		9.18. Link Characteristics Request Message . . . . . . . . . . 33
	9.19. Link Characteristics Response Message . . . . . . . . . . 32		9.19. Link Characteristics Response Message . . . . . . . . . . 33
	9.20. Heartbeat Message . . . . . . . . . . . . . . . . . . . . 33		9.20. Heartbeat Message . . . . . . . . . . . . . . . . . . . . 34
	10. DLEP Data Items . . . . . . . . . . . . . . . . . . . . . . . 34		10. DLEP Data Items . . . . . . . . . . . . . . . . . . . . . . . 35
	10.1. Status . . . . . . . . . . . . . . . . . . . . . . . . . 35		10.1. Status . . . . . . . . . . . . . . . . . . . . . . . . . 36
	10.2. IPv4 Connection Point . . . . . . . . . . . . . . . . . 37		10.2. IPv4 Connection Point . . . . . . . . . . . . . . . . . 38
	10.3. IPv6 Connection Point . . . . . . . . . . . . . . . . . 37		10.3. IPv6 Connection Point . . . . . . . . . . . . . . . . . 39
	10.4. Peer Type . . . . . . . . . . . . . . . . . . . . . . . 39		10.4. Peer Type . . . . . . . . . . . . . . . . . . . . . . . 40
	10.5. Heartbeat Interval . . . . . . . . . . . . . . . . . . . 39		10.5. Heartbeat Interval . . . . . . . . . . . . . . . . . . . 40
	10.6. Extensions Supported . . . . . . . . . . . . . . . . . . 40		10.6. Extensions Supported . . . . . . . . . . . . . . . . . . 41
	10.7. MAC Address . . . . . . . . . . . . . . . . . . . . . . 40		10.7. MAC Address . . . . . . . . . . . . . . . . . . . . . . 41
	10.8. IPv4 Address . . . . . . . . . . . . . . . . . . . . . . 41		10.8. IPv4 Address . . . . . . . . . . . . . . . . . . . . . . 42
	10.9. IPv6 Address . . . . . . . . . . . . . . . . . . . . . . 42		10.9. IPv6 Address . . . . . . . . . . . . . . . . . . . . . . 43
	10.10. IPv4 Attached Subnet . . . . . . . . . . . . . . . . . . 43		10.10. IPv4 Attached Subnet . . . . . . . . . . . . . . . . . . 44
	10.11. IPv6 Attached Subnet . . . . . . . . . . . . . . . . . . 44		10.11. IPv6 Attached Subnet . . . . . . . . . . . . . . . . . . 45
	10.12. Maximum Data Rate (Receive) . . . . . . . . . . . . . . 45		10.12. Maximum Data Rate (Receive) . . . . . . . . . . . . . . 46
	10.13. Maximum Data Rate (Transmit) . . . . . . . . . . . . . . 45		10.13. Maximum Data Rate (Transmit) . . . . . . . . . . . . . . 46
	10.14. Current Data Rate (Receive) . . . . . . . . . . . . . . 46		10.14. Current Data Rate (Receive) . . . . . . . . . . . . . . 47
	10.15. Current Data Rate (Transmit) . . . . . . . . . . . . . . 47		10.15. Current Data Rate (Transmit) . . . . . . . . . . . . . . 48
	10.16. Latency . . . . . . . . . . . . . . . . . . . . . . . . 48		10.16. Latency . . . . . . . . . . . . . . . . . . . . . . . . 48
	10.17. Resources . . . . . . . . . . . . . . . . . . . . . . . 48		10.17. Resources . . . . . . . . . . . . . . . . . . . . . . . 49
	10.18. Relative Link Quality (Receive) . . . . . . . . . . . . 49		10.18. Relative Link Quality (Receive) . . . . . . . . . . . . 50
	10.19. Relative Link Quality (Transmit) . . . . . . . . . . . . 50		10.19. Relative Link Quality (Transmit) . . . . . . . . . . . . 51
	10.20. Maximum Transmission Unit (MTU) . . . . . . . . . . . . 50		10.20. Maximum Transmission Unit (MTU) . . . . . . . . . . . . 52
	11. Security Considerations . . . . . . . . . . . . . . . . . . . 51		11. Security Considerations . . . . . . . . . . . . . . . . . . . 52
	12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52		12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53
	12.1. Registrations . . . . . . . . . . . . . . . . . . . . . 52		12.1. Registrations . . . . . . . . . . . . . . . . . . . . . 53
	12.2. Signal Type Registration . . . . . . . . . . . . . . . . 52		12.2. Signal Type Registration . . . . . . . . . . . . . . . . 53
	12.3. Message Type Registration . . . . . . . . . . . . . . . 52		12.3. Message Type Registration . . . . . . . . . . . . . . . 53
	12.4. DLEP Data Item Registrations . . . . . . . . . . . . . . 53		12.4. DLEP Data Item Registrations . . . . . . . . . . . . . . 54
	12.5. DLEP Status Code Registrations . . . . . . . . . . . . . 54		12.5. DLEP Status Code Registrations . . . . . . . . . . . . . 55
	12.6. DLEP Extensions Registrations . . . . . . . . . . . . . 54		12.6. DLEP Extensions Registrations . . . . . . . . . . . . . 56
	12.7. DLEP Well-known Port . . . . . . . . . . . . . . . . . . 55		12.7. DLEP Well-known Port . . . . . . . . . . . . . . . . . . 56
	12.8. DLEP IPv4 Link-local Multicast Address . . . . . . . . . 55		12.8. DLEP IPv4 Link-local Multicast Address . . . . . . . . . 57
	12.9. DLEP IPv6 Link-local Multicast Address . . . . . . . . . 55		12.9. DLEP IPv6 Link-local Multicast Address . . . . . . . . . 57
	13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 55		13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57
	14. References . . . . . . . . . . . . . . . . . . . . . . . . . 55		14. References . . . . . . . . . . . . . . . . . . . . . . . . . 57
	14.1. Normative References . . . . . . . . . . . . . . . . . . 55		14.1. Normative References . . . . . . . . . . . . . . . . . . 57
	14.2. Informative References . . . . . . . . . . . . . . . . . 56		14.2. Informative References . . . . . . . . . . . . . . . . . 57
	Appendix A. Discovery Signal Flows . . . . . . . . . . . . . . . 56		Appendix A. Discovery Signal Flows . . . . . . . . . . . . . . . 58
	Appendix B. Peer Level Message Flows . . . . . . . . . . . . . . 57		Appendix B. Peer Level Message Flows . . . . . . . . . . . . . . 58
	B.1. Session Initialization . . . . . . . . . . . . . . . . . 57		B.1. Session Initialization . . . . . . . . . . . . . . . . . 58
	B.2. Session Initialization - Refused . . . . . . . . . . . . 57		B.2. Session Initialization - Refused . . . . . . . . . . . . 59
	B.3. Router Changes IP Addresses . . . . . . . . . . . . . . . 58		B.3. Router Changes IP Addresses . . . . . . . . . . . . . . . 60
	B.4. Modem Changes Session-wide Metrics . . . . . . . . . . . 58		B.4. Modem Changes Session-wide Metrics . . . . . . . . . . . 60
	B.5. Router Terminates Session . . . . . . . . . . . . . . . . 59		B.5. Router Terminates Session . . . . . . . . . . . . . . . . 60
	B.6. Modem Terminates Session . . . . . . . . . . . . . . . . 59		B.6. Modem Terminates Session . . . . . . . . . . . . . . . . 61
	B.7. Session Heartbeats . . . . . . . . . . . . . . . . . . . 59		B.7. Session Heartbeats . . . . . . . . . . . . . . . . . . . 61
	B.8. Router Detects a Heartbeat timeout . . . . . . . . . . . 60		B.8. Router Detects a Heartbeat timeout . . . . . . . . . . . 62
	B.9. Modem Detects a Heartbeat timeout . . . . . . . . . . . . 60		B.9. Modem Detects a Heartbeat timeout . . . . . . . . . . . . 63
	Appendix C. Destination Specific Message Flows . . . . . . . . . 61		Appendix C. Destination Specific Message Flows . . . . . . . . . 63
	C.1. Common Destination Notification . . . . . . . . . . . . . 61		C.1. Common Destination Notification . . . . . . . . . . . . . 63
	C.2. Multicast Destination Notification . . . . . . . . . . . 62		C.2. Multicast Destination Notification . . . . . . . . . . . 64
	C.3. Link Characteristics Request . . . . . . . . . . . . . . 62		C.3. Link Characteristics Request . . . . . . . . . . . . . . 65
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 63		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 66
	1. Introduction		1. Introduction
	There exist today a collection of modem devices that control links of		There exist today a collection of modem devices that control links of
	variable datarate and quality. Examples of these types of links		variable datarate and quality. Examples of these types of links
	include line-of-sight (LOS) terrestrial radios, satellite terminals,		include line-of-sight (LOS) terrestrial radios, satellite terminals,
	and broadband modems. Fluctuations in speed and quality of these		and broadband modems. Fluctuations in speed and quality of these
	links can occur due to configuration, or on a moment-to-moment basis,		links can occur due to configuration, or on a moment-to-moment basis,
	due to physical phenomena like multipath interference, obstructions,		due to physical phenomena like multipath interference, obstructions,
	rain fade, etc. It is also quite possible that link quality and		rain fade, etc. It is also quite possible that link quality and
	skipping to change at page 9, line 12 ¶		skipping to change at page 9, line 32 ¶
	modem implementations to negotiate the available extensions to use on		modem implementations to negotiate the available extensions to use on
	a per-session basis.		a per-session basis.
	2.1. Assumptions		2.1. Assumptions
	DLEP specifies UDP multicast for single-hop discovery signaling, and		DLEP specifies UDP multicast for single-hop discovery signaling, and
	TCP for transport of the Messages. Therefore, DLEP assumes that the		TCP for transport of the Messages. Therefore, DLEP assumes that the
	modem and router have topologically consistent IP addresses assigned.		modem and router have topologically consistent IP addresses assigned.
	It is RECOMMENDED that DLEP implementations utilize IPv6 link-local		It is RECOMMENDED that DLEP implementations utilize IPv6 link-local
	addresses to reduce the administrative burden of address assignment.		addresses to reduce the administrative burden of address assignment.
	DLEP relies on the guaranteed- delivery of its Messages between		DLEP relies on the guaranteed delivery of its Messages between router
	router and modem, once the 1 hop discovery process is complete,		and modem, once the 1 hop discovery process is complete, hence, the
	hence, the specification of TCP to carry the Messages. Other		specification of TCP to carry the Messages. Other reliable
	reliable transports for the protocol are possible, but are outside		transports for the protocol are possible, but are outside the scope
	the scope of this document.		of this document.
	DLEP further assumes that security of the implementations (e.g.,		DLEP further assumes that security of the implementations (e.g.,
	authentication of stations, encryption of traffic, or both) is dealt		authentication of stations, encryption of traffic, or both) is dealt
	with by utilizing Layer 2 security techniques. This reliance on		with by utilizing Layer 2 security techniques. This reliance on
	Layer 2 mechanisms secures all DLEP Messages - both the UDP discovery		Layer 2 mechanisms secures all DLEP Messages - both the UDP discovery
	Signals and the TCP control Messages.		Signals and the TCP control Messages.
	3. Metrics		3. Metrics
	DLEP includes the ability for the router and modem to communicate		DLEP includes the ability for the router and modem to communicate
	skipping to change at page 18, line 49 ¶		skipping to change at page 20, line 5 ¶
	| 2 | Peer Offer Signal (Section 9.4) |		| 2 | Peer Offer Signal (Section 9.4) |
	| 3-65519 | Reserved for future extensions |		| 3-65519 | Reserved for future extensions |
	| 65520-65534 | Private Use. Available for experiments |		| 65520-65534 | Private Use. Available for experiments |
	| 65535 | Reserved |		| 65535 | Reserved |
	+--------------+-----------------------------------------+		+--------------+-----------------------------------------+
	Table 1: DLEP Signal types		Table 1: DLEP Signal types
	The core DLEP Messages are:		The core DLEP Messages are:
	+-------------------+-----------------------------------------------+		+--------------+----------------------------------------------------+
	| Type Code | Description |		| Type Code | Description |
	+-------------------+-----------------------------------------------+		+--------------+----------------------------------------------------+
	| 0 | Reserved |		| 0 | Reserved |
	| 1 | Session Initialization Message (Section 9.5) |		| 1 | Session Initialization Message (Section 9.5) |
	| 2 | Session Initialization Response Message |		| 2 | Session Initialization Response Message (Section |
	| | (Section 9.6) |		| | 9.6) |
	| 3 | Session Update Message (Section 9.7) |		| 3 | Session Update Message (Section 9.7) |
	| 4 | Session Update Response Message (Section 9.8) |		| 4 | Session Update Response Message (Section 9.8) |
	| 5 | Session Termination Message (Section 9.9) |		| 5 | Session Termination Message (Section 9.9) |
	| 6 | Session Termination Response Message (Section |		| 6 | Session Termination Response Message (Section |
	| | 9.10) |		| | 9.10) |
	| 7 | Destination Up Message (Section 9.11) |		| 7 | Destination Up Message (Section 9.11) |
	| 8 | Destination Up Response Message (Section |		| 8 | Destination Up Response Message (Section 9.12) |
	| | 9.12) |		| 9 | Destination Announce Message (Section 9.13) |
	| 9 | Destination Announce Message (Section 9.13) |		| 10 | Destination Announce Response Message (Section |
	| 10 | Destination Announce Response Message |		| | 9.14) |
	| | (Section 9.14) |		| 11 | Destination Down Message (Section 9.15) |
	| 11 | Destination Down Message (Section 9.15) |		| 12 | Destination Down Response Message (Section 9.16) |
	| 12 | Destination Down Response Message (Section |		| 13 | Destination Update Message (Section 9.17) |
	| | 9.16) |		| 14 | Link Characteristics Request Message (Section |
	| 13 | Destination Update Message (Section 9.17) |		| | 9.18) |
	| 14 | Link Characteristics Request Message (Section |		| 15 | Link Characteristics Response Message (Section |
	| | 9.18) |		| | 9.19) |
	| 15 | Link Characteristics Response Message |		| 16 | Heartbeat Message (Section 9.20) |
	| | (Section 9.19) |		| 17-65519 | Reserved for future extensions |
	| 16 | Heartbeat Message (Section 9.20) |		| 65520-65534 | Private Use. Available for experiments |
	| 17-65519 | Reserved for future extensions |		| 65535 | Reserved |
	| 65520-65534 | Private Use. Available for experiments |		+--------------+----------------------------------------------------+
	| 65535 | Reserved |
	+-------------------+-----------------------------------------------+
	Table 2: DLEP Message types		Table 2: DLEP Message types
	9.1. General Processing Rules		9.1. General Processing Rules
	If an unrecognized, or unexpected Signal is received, or a received		If an unrecognized, or unexpected Signal is received, or a received
	Signal contains unrecognized, invalid, or disallowed duplicate Data		Signal contains unrecognized, invalid, or disallowed duplicate Data
	Items, the receiving implementation MUST ignore the Signal.		Items, the receiving implementation MUST ignore the Signal.
	If an unrecognized Message is received, the receiving implementation		If an unrecognized Message is received, the receiving implementation
	skipping to change at page 21, line 8 ¶		skipping to change at page 21, line 51 ¶
	issue a Session Termination Message containing an identical Status		issue a Session Termination Message containing an identical Status
	Data Item, and then transition to the Session Termination state.		Data Item, and then transition to the Session Termination state.
	A DLEP participant receiving a Message containing a Status Data Item		A DLEP participant receiving a Message containing a Status Data Item
	with a status code value with failure mode 'Continue' can continue		with a status code value with failure mode 'Continue' can continue
	normal operation of the session.		normal operation of the session.
	9.3. Peer Discovery Signal		9.3. Peer Discovery Signal
	A Peer Discovery Signal SHOULD be sent by a DLEP router to discover		A Peer Discovery Signal SHOULD be sent by a DLEP router to discover
	DLEP modems in the network Section 4.1.		DLEP modems in the network, see Section 4.1.
	A Peer Discovery Signal MUST be encoded within a UDP packet. The		A Peer Discovery Signal MUST be encoded within a UDP packet. The
	destination MUST be set to the DLEP well-known address and port		destination MUST be set to the DLEP well-known address and port
	number. For routers supporting both IPv4 and IPv6 DLEP operation, it		number. For routers supporting both IPv4 and IPv6 DLEP operation, it
	is RECOMMENDED that IPv6 be selected as the transport. The source IP		is RECOMMENDED that IPv6 be selected as the transport. The source IP
	address MUST be set to the router IP address associated with the DLEP		address MUST be set to the router IP address associated with the DLEP
	interface. There is no DLEP-specific restriction on source port.		interface. There is no DLEP-specific restriction on source port.
	To construct a Peer Discovery Signal, the Signal Type value in the		To construct a Peer Discovery Signal, the Signal Type value in the
	Signal Header is set to 1, from Table 1.		Signal Header is set to 1, from Table 1.
	skipping to change at page 21, line 33 ¶		skipping to change at page 22, line 28 ¶
	9.4. Peer Offer Signal		9.4. Peer Offer Signal
	A Peer Offer Signal MUST be sent by a DLEP modem in response to a		A Peer Offer Signal MUST be sent by a DLEP modem in response to a
	properly formatted and addressed Peer Discovery Signal (Section 9.3).		properly formatted and addressed Peer Discovery Signal (Section 9.3).
	A Peer Offer Signal MUST be encoded within a UDP packet. The IP		A Peer Offer Signal MUST be encoded within a UDP packet. The IP
	destination MUST be set to the IP address and port number received in		destination MUST be set to the IP address and port number received in
	the corresponding Peer Discovery Signal. The source IP address MUST		the corresponding Peer Discovery Signal. The source IP address MUST
	be set to the modem's IP address associated with the DLEP interface.		be set to the modem's IP address associated with the DLEP interface.
	The source port number MUST be set to the DLEP well-known port		The source port number MUST be set to the DLEP well-known port
	number. The Peer Offer Signal completes the discovery process		number. The Peer Offer Signal completes the discovery process, see
	Section 4.1.		Section 4.1.
	To construct a Peer Offer Signal, the Signal Type value in the Signal		To construct a Peer Offer Signal, the Signal Type value in the Signal
	Header is set to 2, from Table 1.		Header is set to 2, from Table 1.
	The Peer Offer Signal MAY contain a Peer Type Data Item		The Peer Offer Signal MAY contain a Peer Type Data Item
	(Section 10.4).		(Section 10.4).
	The Peer Offer Signal MAY contain one or more of any of the following		The Peer Offer Signal MAY contain one or more of any of the following
	Data Items, with different values:		Data Items, with different values:
	skipping to change at page 24, line 13 ¶		skipping to change at page 25, line 7 ¶
	router and modem.		router and modem.
	If any optional extensions are supported by the modem, they MUST be		If any optional extensions are supported by the modem, they MUST be
	enumerated in the Extensions Supported Data Item. If an Extensions		enumerated in the Extensions Supported Data Item. If an Extensions
	Supported Data Item does not exist in a Session Initialization		Supported Data Item does not exist in a Session Initialization
	Response Message, the router MUST conclude that there is no support		Response Message, the router MUST conclude that there is no support
	for extensions in the modem.		for extensions in the modem.
	After the Session Initialization/Session Initialization Response		After the Session Initialization/Session Initialization Response
	Messages have been successfully exchanged, implementations MUST only		Messages have been successfully exchanged, implementations MUST only
	use extensions that are supported by both DLEP participants		use extensions that are supported by both DLEP participants, see
	Section 4.2.		Section 4.2.
	9.7. Session Update Message		9.7. Session Update Message
	A Session Update Message MAY be sent by a DLEP participant to		A Session Update Message MAY be sent by a DLEP participant to
	indicate local Layer 3 address changes, or metric changes on a		indicate local Layer 3 address changes, or metric changes on a
	session-wide basis.		session-wide basis.
	To construct a Session Update Message, the Message Type value in the		To construct a Session Update Message, the Message Type value in the
	Message Header is set to 3, from Table 2.		Message Header is set to 3, from Table 2.
	skipping to change at page 26, line 18 ¶		skipping to change at page 27, line 18 ¶
	participant when a Session Termination Message (Section 9.9) is		participant when a Session Termination Message (Section 9.9) is
	received.		received.
	To construct a Session Termination Response Message, the Message Type		To construct a Session Termination Response Message, the Message Type
	value in the Message Header is set to 6, from Table 2.		value in the Message Header is set to 6, from Table 2.
	There are no valid Data Items for the Session Termination Response		There are no valid Data Items for the Session Termination Response
	Message.		Message.
	Receipt of a Session Termination Response Message completes the tear-		Receipt of a Session Termination Response Message completes the tear-
	down of the DLEP session Section 4.4.		down of the DLEP session, see Section 4.4.
	9.11. Destination Up Message		9.11. Destination Up Message
	Destination Up Messages MAY be sent by a modem to inform its attached		Destination Up Messages MAY be sent by a modem to inform its attached
	router of the presence of a new reachable destination.		router of the presence of a new reachable destination.
	To construct a Destination Up Message, the Message Type value in the		To construct a Destination Up Message, the Message Type value in the
	Message Header is set to 7, from Table 2.		Message Header is set to 7, from Table 2.
	The Destination Up Message MUST contain a MAC Address Data Item		The Destination Up Message MUST contain a MAC Address Data Item
	skipping to change at page 28, line 8 ¶		skipping to change at page 29, line 8 ¶
	MUST set the status code of the included Status Data Item to 0		MUST set the status code of the included Status Data Item to 0
	'Success', see Table 4.		'Success', see Table 4.
	If the router has no interest in the destination identified in the		If the router has no interest in the destination identified in the
	corresponding Destination Up Message, then it MAY set the status code		corresponding Destination Up Message, then it MAY set the status code
	of the included Status Data Item to 1 'Not Interested'.		of the included Status Data Item to 1 'Not Interested'.
	A modem receiving a Destination Up Response Message containing a		A modem receiving a Destination Up Response Message containing a
	Status Data Item with status code of any value other than 0 'Success'		Status Data Item with status code of any value other than 0 'Success'
	MUST NOT send further Destination messages about the destination,		MUST NOT send further Destination messages about the destination,
	e.g. Destination Down (Section 9.15) or Destination Update		e.g. Destination Down (Section 9.15) or Destination Update
	(Section 9.17) with the same MAC address.		(Section 9.17) with the same MAC address.
	9.13. Destination Announce Message		9.13. Destination Announce Message
	Usually a modem will discover the presence of one or more remote		Usually a modem will discover the presence of one or more remote
	router/modem pairs and announce each destination's arrival by sending		router/modem pairs and announce each destination's arrival by sending
	a corresponding Destination Up Message (Section 9.11) to the router.		a corresponding Destination Up Message (Section 9.11) to the router.
	However, there may be times when a router wishes to express an		However, there may be times when a router wishes to express an
	interest in a destination that has yet to be announced, typically a		interest in a destination that has yet to be announced, typically a
	multicast destination. Destination Announce Messages MAY be sent by		multicast destination. Destination Announce Messages MAY be sent by
	skipping to change at page 34, line 7 ¶		skipping to change at page 35, line 7 ¶
	(Section 10.5) of the Session Initialization Message (Section 9.5) or		(Section 10.5) of the Session Initialization Message (Section 9.5) or
	Session Initialization Response Message (Section 9.6).		Session Initialization Response Message (Section 9.6).
	To construct a Heartbeat Message, the Message Type value in the		To construct a Heartbeat Message, the Message Type value in the
	Message Header is set to 16, from Table 2.		Message Header is set to 16, from Table 2.
	There are no valid Data Items for the Heartbeat Message.		There are no valid Data Items for the Heartbeat Message.
	The Message is used by DLEP participants to detect when a DLEP		The Message is used by DLEP participants to detect when a DLEP
	session peer (either the modem or the router) is no longer		session peer (either the modem or the router) is no longer
	communicating Section 4.3.1.		communicating, see Section 4.3.1.
	10. DLEP Data Items		10. DLEP Data Items
	Following is the list of core Data Items that MUST be recognized by a		Following is the list of core Data Items that MUST be recognized by a
	DLEP compliant implementation. As mentioned before, not all Data		DLEP compliant implementation. As mentioned before, not all Data
	Items need be used during a session, but an implementation MUST		Items need be used during a session, but an implementation MUST
	correctly process these Data Items when correctly associated with a		correctly process these Data Items when correctly associated with a
	Signal or Message.		Signal or Message.
	The core DLEP Data Items are:		The core DLEP Data Items are:
	+--------------------+----------------------------------------------+		+-------------+-----------------------------------------------------+
	| Type Code | Description |		| Type Code | Description |
	+--------------------+----------------------------------------------+		+-------------+-----------------------------------------------------+
	| 0 | Reserved |		| 0 | Reserved |
	| 1 | Status (Section 10.1) |		| 1 | Status (Section 10.1) |
	| 2 | IPv4 Connection Point (Section 10.2) |		| 2 | IPv4 Connection Point (Section 10.2) |
	| 3 | IPv6 Connection Point (Section 10.3) |		| 3 | IPv6 Connection Point (Section 10.3) |
	| 4 | Peer Type (Section 10.4) |		| 4 | Peer Type (Section 10.4) |
	| 5 | Heartbeat Interval (Section 10.5) |		| 5 | Heartbeat Interval (Section 10.5) |
	| 6 | Extensions Supported (Section 10.6) |		| 6 | Extensions Supported (Section 10.6) |
	| 7 | MAC Address (Section 10.7) |		| 7 | MAC Address (Section 10.7) |
	| 8 | IPv4 Address (Section 10.8) |		| 8 | IPv4 Address (Section 10.8) |
	| 9 | IPv6 Address (Section 10.9) |		| 9 | IPv6 Address (Section 10.9) |
	| 10 | IPv4 Attached Subnet (Section 10.10) |		| 10 | IPv4 Attached Subnet (Section 10.10) |
	| 11 | IPv6 Attached Subnet (Section 10.11) |		| 11 | IPv6 Attached Subnet (Section 10.11) |
	| 12 | Maximum Data Rate (Receive) (MDRR) (Section |		| 12 | Maximum Data Rate (Receive) (MDRR) (Section 10.12) |
	| | 10.12) |		| 13 | Maximum Data Rate (Transmit) (MDRT) (Section 10.13) |
	| 13 | Maximum Data Rate (Transmit) (MDRT) (Section |		| 14 | Current Data Rate (Receive) (CDRR) (Section 10.14) |
	| | 10.13) |		| 15 | Current Data Rate (Transmit) (CDRT) (Section 10.15) |
	| 14 | Current Data Rate (Receive) (CDRR) (Section |		| 16 | Latency (Section 10.16) |
	| | 10.14) |		| 17 | Resources (RES) (Section 10.17) |
	| 15 | Current Data Rate (Transmit) (CDRT) (Section |		| 18 | Relative Link Quality (Receive) (RLQR) (Section |
	| | 10.15) |		| | 10.18) |
	| 16 | Latency (Section 10.16) |		| 19 | Relative Link Quality (Transmit) (RLQT) (Section |
	| 17 | Resources (RES) (Section 10.17) |		| | 10.19) |
	| 18 | Relative Link Quality (Receive) (RLQR) |		| 20 | Maximum Transmission Unit (MTU) (Section 10.20) |
	| | (Section 10.18) |		| 21-65407 | Reserved for future extensions |
	| 19 | Relative Link Quality (Transmit) (RLQT) |		| 65408-65534 | Private Use. Available for experiments |
	| | (Section 10.19) |		| 65535 | Reserved |
	| 20 | Maximum Transmission Unit (MTU) (Section |		+-------------+-----------------------------------------------------+
	| | 10.20) |
	| 21-65407 | Reserved for future extensions |
	| 65408-65534 | Private Use. Available for experiments |
	| 65535 | Reserved |
	+--------------------+----------------------------------------------+
	Table 3: DLEP Data Item types		Table 3: DLEP Data Item types
	10.1. Status		10.1. Status
	For the Session Termination Message (Section 9.9), the Status Data		For the Session Termination Message (Section 9.9), the Status Data
	Item indicates a reason for the termination. For all response		Item indicates a reason for the termination. For all response
	Messages, the Status Data Item is used to indicate the success or		Messages, the Status Data Item is used to indicate the success or
	failure of the previously received Message.		failure of the previously received Message.
	skipping to change at page 35, line 46 ¶		skipping to change at page 36, line 43 ¶
	Text: UTF-8 encoded string of UNICODE [UNIV8] characters, describing		Text: UTF-8 encoded string of UNICODE [UNIV8] characters, describing
	the cause, used for implementation defined purposes. Since this		the cause, used for implementation defined purposes. Since this
	field is used for description, implementations SHOULD limit		field is used for description, implementations SHOULD limit
	characters in this field to printable characters. Implementations		characters in this field to printable characters. Implementations
	receiving this Data Item SHOULD check for printable characters in		receiving this Data Item SHOULD check for printable characters in
	the field.		the field.
	An implementation MUST NOT assume the Text field is NUL-terminated.		An implementation MUST NOT assume the Text field is NUL-terminated.
	+---------+-----------+---------------+-----------------------------+		+----------+-------------+------------------+-----------------------+
	| Status | Failure | Description | Reason |		| Status | Failure | Description | Reason |
	| Code | Mode | | |		| Code | Mode | | |
	+---------+-----------+---------------+-----------------------------+		+----------+-------------+------------------+-----------------------+
	| 0 | Continue | Success | The Message was processed |		| 0 | Continue | Success | The Message was |
	| | | | successfully. |		| | | | processed |
	| 1 | Continue | Not | The receiver is not |		| | | | successfully. |
	| | | Interested | interested in this Message |		| 1 | Continue | Not Interested | The receiver is not |
	| | | | subject, e.g. in a |		| | | | interested in this |
	| | | | Destination Up Response |		| | | | Message subject, e.g. |
	| | | | Message (Section 9.12) to |		| | | | in a Destination Up |
	| | | | indicate no further |		| | | | Response Message |
	| | | | Messages about the |		| | | | (Section 9.12) to |
	| | | | destination. |		| | | | indicate no further |
	| 2 | Continue | Request | The receiver refuses to |		| | | | Messages about the |
	| | | Denied | complete the request. |		| | | | destination. |
	| 3-111 | Continue | <Reserved> | Reserved for future |		| 2 | Continue | Request Denied | The receiver refuses |
	| | | | extensions. |		| | | | to complete the |
	| 112-127 | Continue | <Private Use> | Available for experiments. |		| | | | request. |
	| 128 | Terminate | Unknown | The Message was not |		| 3-111 | Continue | <Reserved> | Reserved for future |
	| | | Message | recognized by the |		| | | | extensions. |
	| | | | implementation. |		| 112-127 | Continue | <Private Use> | Available for |
	| 129 | Terminate | Unexpected | The Message was not |		| | | | experiments. |
	| | | Message | expected while the device |		| 128 | Terminate | Unknown Message | The Message was not |
	| | | | was in the current state, |		| | | | recognized by the |
	| | | | e.g., a Session |		| | | | implementation. |
	| | | | Initialization Message |		| 129 | Terminate | Unexpected | The Message was not |
	| | | | (Section 9.5) in the In- |		| | | Message | expected while the |
	| | | | Session state. |		| | | | device was in the |
	| 130 | Terminate | Invalid Data | One or more Data Items in |		| | | | current state, e.g., |
	| | | | the Message are invalid, |		| | | | a Session |
	| | | | unexpected or incorrectly |		| | | | Initialization |
	| | | | duplicated. |		| | | | Message (Section 9.5) |
	| 131 | Terminate | Invalid | The destination included in |		| | | | in the In-Session |
	| | | Destination | the Message does not match |		| | | | state. |
	| | | | a previously announced |		| 130 | Terminate | Invalid Data | One or more Data |
	| | | | destination. For example, |		| | | | Items in the Message |
	| | | | in the Link Characteristic |		| | | | are invalid, |
	| | | | Response Message (Section |		| | | | unexpected or |
	| | | | 9.19). |		| | | | incorrectly |
	| 132 | Terminate | Timed Out | The session has timed out. |		| | | | duplicated. |
	| 133-239 | Terminate | <Reserved> | Reserved for future |		| 131 | Terminate | Invalid | The destination |
	| | | | extensions. |		| | | Destination | included in the |
	| 240-254 | Terminate | <Private Use> | Available for experiments. |		| | | | Message does not |
	| 255 | Terminate | <Reserved> | Reserved. |		| | | | match a previously |
	+---------+-----------+---------------+-----------------------------+		| | | | announced |
			| | | | destination. For |
			| | | | example, in the Link |
			| | | | Characteristic |
			| | | | Response Message |
			| | | | (Section 9.19). |
			| 132 | Terminate | Timed Out | The session has timed |
			| | | | out. |
			| 133-239 | Terminate | <Reserved> | Reserved for future |
			| | | | extensions. |
			| 240-254 | Terminate | <Private Use> | Available for |
			| | | | experiments. |
			| 255 | Terminate | <Reserved> | Reserved. |
			+----------+-------------+------------------+-----------------------+
	Table 4: DLEP Status Codes		Table 4: DLEP Status Codes
	10.2. IPv4 Connection Point		10.2. IPv4 Connection Point
	The IPv4 Connection Point Data Item indicates the IPv4 address and,		The IPv4 Connection Point Data Item indicates the IPv4 address and,
	optionally, the TCP port number on the modem available for		optionally, the TCP port number on the modem available for
	connections. If provided, the router MUST use this information to		connections. If provided, the router MUST use this information to
	initiate the TCP connection to the modem.		initiate the TCP connection to the modem.
	skipping to change at page 39, line 50 ¶		skipping to change at page 41, line 4 ¶
	The Heartbeat Interval Data Item contains the following fields:		The Heartbeat Interval Data Item contains the following fields:
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Data Item Type | Length |		| Data Item Type | Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Heartbeat Interval |		| Heartbeat Interval |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Data Item Type: 5		Data Item Type: 5
	Length: 4		Length: 4
	Heartbeat Interval: The interval in milliseconds, expressed as a		Heartbeat Interval: The interval in milliseconds, expressed as a
	32-bit unsigned integer, for Heartbeat Messages.		32-bit unsigned integer, for Heartbeat Messages. This value MUST
	This value MUST NOT be 0.		NOT be 0.
	10.6. Extensions Supported		10.6. Extensions Supported
	The Extensions Supported Data Item is used by the router and modem to		The Extensions Supported Data Item is used by the router and modem to
	negotiate additional optional functionality they are willing to		negotiate additional optional functionality they are willing to
	support. The Extensions List is a concatenation of the types of each		support. The Extensions List is a concatenation of the types of each
	supported extension, found in the IANA DLEP Extensions repository.		supported extension, found in the IANA DLEP Extensions repository.
	Each Extension Type definition includes which additional Signals and		Each Extension Type definition includes which additional Signals and
	Data Items are supported.		Data Items are supported.
	skipping to change at page 50, line 7 ¶		skipping to change at page 51, line 7 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| RLQR |		| RLQR |
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	Data Item Type: 18		Data Item Type: 18
	Length: 1		Length: 1
	Relative Link Quality (Receive): A non-dimensional unsigned 8-bit		Relative Link Quality (Receive): A non-dimensional unsigned 8-bit
	integer, 0-100, representing relative quality of the link for		integer, 0-100, representing relative quality of the link for
	receiving traffic. Any value greater than 100 MUST be considered		receiving traffic. Any value greater than 100 MUST be considered
	as invalid.		as invalid. This is analogous to [RFC5578].
	If a device cannot calculate the Relative Link Quality (Receive),		If a device cannot calculate the Relative Link Quality (Receive),
	this Data Item MUST NOT be issued.		this Data Item MUST NOT be issued.
	10.19. Relative Link Quality (Transmit)		10.19. Relative Link Quality (Transmit)
	The Relative Link Quality (Transmit) (RLQT) Data Item is used to		The Relative Link Quality (Transmit) (RLQT) Data Item is used to
	indicate the quality of the link to a destination for transmitting		indicate the quality of the link to a destination for transmitting
	traffic, with 0 meaning 'worst quality', and 100 meaning 'best		traffic, with 0 meaning 'worst quality', and 100 meaning 'best
	quality'.		quality'.
	skipping to change at page 51, line 42 ¶		skipping to change at page 52, line 47 ¶
	1. An attacker might pretend to be a DLEP participant, either at		1. An attacker might pretend to be a DLEP participant, either at
	DLEP session initialization, or by injection of DLEP Messages		DLEP session initialization, or by injection of DLEP Messages
	once a session has been established, and/or		once a session has been established, and/or
	2. DLEP Data Items could be altered by an attacker, causing the		2. DLEP Data Items could be altered by an attacker, causing the
	receiving implementation to inappropriately alter its information		receiving implementation to inappropriately alter its information
	base concerning network status.		base concerning network status.
	Since DLEP is restricted to operation over a single (possibly		Since DLEP is restricted to operation over a single (possibly
	logical) hop at layer 2, implementations requiring authentication and		logical) hop at layer 2, implementations requiring authentication
	/or encryption of traffic MUST take steps to secure the Layer 2 link.		and/or encryption of traffic MUST take steps to secure the Layer 2
	Examples of technologies that can be deployed to secure the Layer 2		link. Examples of technologies that can be deployed to secure the
	link include [IEEE-802.1AE] and [IEEE-802.1X].		Layer 2 link include [IEEE-802.1AE] and [IEEE-802.1X].
	To avoid potential denial of service attack, it is RECOMMENDED that		To avoid potential denial of service attack, it is RECOMMENDED that
	implementations using the Peer Discovery mechanism maintain an		implementations using the Peer Discovery mechanism maintain an
	information base of hosts that persistently fail Session		information base of hosts that persistently fail Session
	Initialization having provided an acceptable Peer Discovery Signal,		Initialization having provided an acceptable Peer Discovery Signal,
	and ignore subsequent Peer Discovery Signals from such hosts.		and ignore subsequent Peer Discovery Signals from such hosts.
	This specification does not address security of the data plane, as it		This specification does not address security of the data plane, as it
	(the data plane) is not affected, and standard security procedures		(the data plane) is not affected, and standard security procedures
	can be employed.		can be employed.
	12. IANA Considerations		12. IANA Considerations
	This section specifies requests to IANA.		This section specifies requests to IANA.
	12.1. Registrations		12.1. Registrations
	Upon approval of this document, IANA is requested to create a new		Upon approval of this document, IANA is requested to create a new
	protocol registry for Dynamic Link Event Protocol (DLEP). The		protocol registry for Dynamic Link Exchange Protocol (DLEP). The
	remainder of this section requests the creation of new DLEP specific		remainder of this section requests the creation of new DLEP specific
	registries.		registries.
	12.2. Signal Type Registration		12.2. Signal Type Registration
	Upon approval of this document, IANA is requested to create a new		Upon approval of this document, IANA is requested to create a new
	DLEP registry, named "Signal Type Values".		DLEP registry, named "Signal Type Values".
	The following table provides initial registry values and the		The following table provides initial registry values and the
	[RFC5226] defined policies that should apply to the registry:		[RFC5226] defined policies that should apply to the registry:
	skipping to change at page 53, line 31 ¶		skipping to change at page 55, line 5 ¶
	+--------------+------------------------------------------+		+--------------+------------------------------------------+
	12.4. DLEP Data Item Registrations		12.4. DLEP Data Item Registrations
	Upon approval of this document, IANA is requested to create a new		Upon approval of this document, IANA is requested to create a new
	DLEP registry, named "Data Item Values".		DLEP registry, named "Data Item Values".
	The following table provides initial registry values and the		The following table provides initial registry values and the
	[RFC5226] defined policies that should apply to the registry:		[RFC5226] defined policies that should apply to the registry:
	+--------------+------------------------------------------+		+-------------------+------------------------------------------+
	| Type Code | Description/Policy |		| Type Code | Description/Policy |
	+--------------+------------------------------------------+		+-------------------+------------------------------------------+
	| 0 | Reserved |		| 0 | Reserved |
	| 1 | Status |		| 1 | Status |
	| 2 | IPv4 Connection Point |		| 2 | IPv4 Connection Point |
	| 3 | IPv6 Connection Point |		| 3 | IPv6 Connection Point |
	| 4 | Peer Type |		| 4 | Peer Type |
	| 5 | Heartbeat Interval |		| 5 | Heartbeat Interval |
	| 6 | Extensions Supported |		| 6 | Extensions Supported |
	| 7 | MAC Address |		| 7 | MAC Address |
	| 8 | IPv4 Address |		| 8 | IPv4 Address |
	| 9 | IPv6 Address |		| 9 | IPv6 Address |
	| 10 | IPv4 Attached Subnet |		| 10 | IPv4 Attached Subnet |
	| 11 | IPv6 Attached Subnet |		| 11 | IPv6 Attached Subnet |
	| 12 | Maximum Data Rate (Receive) (MDRR) |		| 12 | Maximum Data Rate (Receive) (MDRR) |
	| 13 | Maximum Data Rate (Transmit) (MDRT) |		| 13 | Maximum Data Rate (Transmit) (MDRT) |
	| 14 | Current Data Rate (Receive) (CDRR) |		| 14 | Current Data Rate (Receive) (CDRR) |
	| 15 | Current Data Rate (Transmit) (CDRT) |		| 15 | Current Data Rate (Transmit) (CDRT) |
	| 16 | Latency |		| 16 | Latency |
	| 17 | Resources (RES) |		| 17 | Resources (RES) |
	| 18 | Relative Link Quality (Receive) (RLQR) |		| 18 | Relative Link Quality (Receive) (RLQR) |
	| 19 | Relative Link Quality (Transmit) (RLQT) |		| 19 | Relative Link Quality (Transmit) (RLQT) |
	| 20 | Maximum Transmission Unit (MTU) |		| 20 | Maximum Transmission Unit (MTU) |
	| 21-65407 | Specification Required |		| 21-65407 | Specification Required |
	| 65408-65534 | Private Use |		| 65408-65534 | Private Use |
	| 65535 | Reserved |		| 65535 | Reserved |
	+--------------+------------------------------------------+		+-------------------+------------------------------------------+
	12.5. DLEP Status Code Registrations		12.5. DLEP Status Code Registrations
	Upon approval of this document, IANA is requested to create a new		Upon approval of this document, IANA is requested to create a new
	DLEP registry, named "Status Code Values".		DLEP registry, named "Status Code Values".
	The following table provides initial registry values and the		The following table provides initial registry values and the
	[RFC5226] defined policies that should apply to the registry:		[RFC5226] defined policies that should apply to the registry:
	+--------------+---------------+-------------------------+		+--------------+---------------+-------------------------+
	skipping to change at page 54, line 33 ¶		skipping to change at page 56, line 18 ¶
	| 0 | Continue | Success |		| 0 | Continue | Success |
	| 1 | Continue | Not Interested |		| 1 | Continue | Not Interested |
	| 2 | Continue | Request Denied |		| 2 | Continue | Request Denied |
	| 3-111 | Continue | Specification Required |		| 3-111 | Continue | Specification Required |
	| 112-127 | Continue | Private Use |		| 112-127 | Continue | Private Use |
	| 128 | Terminate | Unknown Message |		| 128 | Terminate | Unknown Message |
	| 129 | Terminate | Unexpected Message |		| 129 | Terminate | Unexpected Message |
	| 130 | Terminate | Invalid Data |		| 130 | Terminate | Invalid Data |
	| 131 | Terminate | Invalid Destination |		| 131 | Terminate | Invalid Destination |
	| 132 | Terminate | Timed Out |		| 132 | Terminate | Timed Out |
	| 132-239 | Terminate | Specification Required |		| 133-239 | Terminate | Specification Required |
	| 240-254 | Terminate | Private Use |		| 240-254 | Terminate | Private Use |
	| 255 | Terminate | Reserved |		| 255 | Terminate | Reserved |
	+--------------+---------------+-------------------------+		+--------------+---------------+-------------------------+
	12.6. DLEP Extensions Registrations		12.6. DLEP Extensions Registrations
	Upon approval of this document, IANA is requested to create a new		Upon approval of this document, IANA is requested to create a new
	DLEP registry, named "Extension Type Values".		DLEP registry, named "Extension Type Values".
	The following table provides initial registry values and the		The following table provides initial registry values and the
	skipping to change at page 55, line 21 ¶		skipping to change at page 57, line 7 ¶
	Upon approval of this document, IANA is requested to assign a single		Upon approval of this document, IANA is requested to assign a single
	value in the "Service Name and Transport Protocol Port Number		value in the "Service Name and Transport Protocol Port Number
	Registry" found at https://www.iana.org/assignments/service-names-		Registry" found at https://www.iana.org/assignments/service-names-
	port-numbers/service-names-port-numbers.xhtml for use by "DLEP", as		port-numbers/service-names-port-numbers.xhtml for use by "DLEP", as
	defined in this document. This assignment should be valid for TCP		defined in this document. This assignment should be valid for TCP
	and UDP. SCTP port allocation is not required.		and UDP. SCTP port allocation is not required.
	12.8. DLEP IPv4 Link-local Multicast Address		12.8. DLEP IPv4 Link-local Multicast Address
	Upon approval of this document, IANA is requested to assign a IPv4		Upon approval of this document, IANA is requested to assign an IPv4
	multicast address registry found at http://www.iana.org/assignments/		multicast address registry found at http://www.iana.org/assignments/
	multicast-addresses for use as the "IPv4 DLEP Discovery Address".		multicast-addresses for use as the "IPv4 DLEP Discovery Address".
	12.9. DLEP IPv6 Link-local Multicast Address		12.9. DLEP IPv6 Link-local Multicast Address
	Upon approval of this document, IANA is requested to assign a IPv6		Upon approval of this document, IANA is requested to assign an IPv6
	multicast address registry found at http://www.iana.org/assignments/		multicast address registry found at http://www.iana.org/assignments/
	multicast-addresses for use as the "IPv6 DLEP Discovery Address".		multicast-addresses for use as the "IPv6 DLEP Discovery Address".
	13. Acknowledgements		13. Acknowledgements
	We would like to acknowledge and thank the members of the DLEP design		We would like to acknowledge and thank the members of the DLEP design
	team, who have provided invaluable insight. The members of the		team, who have provided invaluable insight. The members of the
	design team are: Teco Boot, Bow-Nan Cheng, John Dowdell, and Henning		design team are: Teco Boot, Bow-Nan Cheng, John Dowdell, and Henning
	Rogge.		Rogge.
	We would also like to acknowledge the influence and contributions of		We would also like to acknowledge the influence and contributions of
	Greg Harrison, Chris Olsen, Martin Duke, Subir Das, Jaewon Kang,		Greg Harrison, Chris Olsen, Martin Duke, Subir Das, Jaewon Kang,
	Vikram Kaul, Nelson Powell, Lou Berger, and Victoria Mercieca.		Vikram Kaul, Nelson Powell, Lou Berger, and Victoria Mercieca.
	14. References		14. References
	14.1. Normative References		14.1. Normative References
	[CREDIT] Ratliff, S., "Credit Windowing extension for DLEP", IETF		[CREDIT] Ratliff, S., "Credit Windowing extension for DLEP", IETF
	draft draft-ietf-manet-credit-window-02, March 2016.		draft draft-ietf-manet-credit-window-04, March 2016.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/		Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
	RFC2119, March 1997,		RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
	[UNIV8] , "The Unicode Consortium. The Unicode Standard, Version		[UNIV8] "The Unicode Consortium. The Unicode Standard, Version
	8.0.0, (Mountain View, CA: The Unicode Consortium, 2015.		8.0.0, (Mountain View, CA: The Unicode Consortium, 2015.
	ISBN 978-1-936213-10-8)",		ISBN 978-1-936213-10-8)",
	http://www.unicode.org/versions/Unicode8.0.0/, June 2015.		http://www.unicode.org/versions/Unicode8.0.0/, June 2015.
	14.2. Informative References		14.2. Informative References
	[IEEE-802.1AE]		[IEEE-802.1AE]
	, "IEEE Standards for Local and Metropolitan Area		"IEEE Standards for Local and Metropolitan Area Networks:
	Networks: Media Access Control (MAC) Security", DOI		Media Access Control (MAC) Security", DOI 10.1109/
	10.1109/IEEESTD.2006.245590, August 2006.		IEEESTD.2006.245590, August 2006.
	[IEEE-802.1X]		[IEEE-802.1X]
	, "IEEE Standards for Local and Metropolitan Area		"IEEE Standards for Local and Metropolitan Area Networks:
	Networks: Port based Network Access Control", DOI 10.1109/		Port based Network Access Control", DOI 10.1109/
	IEEESTD.2010.5409813, February 2010.		IEEESTD.2010.5409813, February 2010.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	DOI 10.17487/RFC5226, May 2008,		DOI 10.17487/RFC5226, May 2008,
	<http://www.rfc-editor.org/info/rfc5226>.		<http://www.rfc-editor.org/info/rfc5226>.
	[RFC5578] Berry, B., Ed., Ratliff, S., Paradise, E., Kaiser, T., and		[RFC5578] Berry, B., Ed., Ratliff, S., Paradise, E., Kaiser, T., and
	M. Adams, "PPP over Ethernet (PPPoE) Extensions for Credit		M. Adams, "PPP over Ethernet (PPPoE) Extensions for Credit
	Flow and Link Metrics", RFC 5578, DOI 10.17487/RFC5578,		Flow and Link Metrics", RFC 5578, DOI 10.17487/RFC5578,
	February 2010, <http://www.rfc-editor.org/info/rfc5578>.		February 2010, <http://www.rfc-editor.org/info/rfc5578>.
	Appendix A. Discovery Signal Flows		Appendix A. Discovery Signal Flows
	Router Modem Signal Description		Router Modem Signal Description
	========================================================================		========================================================================
	| Router initiates discovery, starts		| Router initiates discovery, starts
	| a timer, send Peer Discovery		| a timer, send Peer Discovery
	|-------Peer Discovery---->X Signal.		|-------Peer Discovery---->X Signal.
	~ ~ ~ ~ ~ ~ ~ Router discovery timer expires		~ ~ ~ ~ ~ ~ ~ Router discovery timer expires
	without receiving Peer Offer.		without receiving Peer Offer.
	| Router sends another Peer		| Router sends another Peer
	|-------Peer Discovery---------->| Discovery Signal.		|-------Peer Discovery---------->| Discovery Signal.
	|		|
	| Modem receives Peer Discovery		| Modem receives Peer Discovery
	| Signal.		| Signal.
	|		|
	| Modem sends Peer Offer with		| Modem sends Peer Offer with
	|<--------Peer Offer-------------| Connection Point information.		|<--------Peer Offer-------------| Connection Point information.
	:		:
	: Router MAY cancel discovery timer		: Router MAY cancel discovery timer
	: and stop sending Peer Discovery		: and stop sending Peer Discovery
	: Signals.		: Signals.
	Appendix B. Peer Level Message Flows		Appendix B. Peer Level Message Flows
	B.1. Session Initialization		B.1. Session Initialization
			Router Modem Message Description
			========================================================================
	Router Modem Message Description		| Router connects to discovered or
	========================================================================		| pre-configured Modem Connection
			|--TCP connection established---> Point.
	| Router connects to discovered or		|
	| pre-configured Modem Connection		| Router sends Session
	|--TCP connection established---> Point.		|----Session Initialization----->| Initialization Message.
	|		|
	| Router sends Session		| Modem receives Session
	|----Session Initialization----->| Initialization Message.		| Initialization Message.
	|		|
	| Modem receives Session		| Modem sends Session Initialization
	| Initialization Message.		|<--Session Initialization Resp.-| Response, with Success Status Data
	|		| | Item.
	| Modem sends Session Initialization		| |
	|<--Session Initialization Resp.-| Response, with Success Status Data		|<<============================>>| Session established. Heartbeats
	| | Item.		: : begin.
	| |
	|<<============================>>| Session established. Heartbeats
	: : begin.
	B.2. Session Initialization - Refused		B.2. Session Initialization - Refused
	Router Modem Message Description		Router Modem Message Description
	========================================================================		========================================================================
	| Router connects to discovered or		| Router connects to discovered or
	| pre-configured Modem Connection		| pre-configured Modem Connection
	|--TCP connection established---> Point.		|--TCP connection established---> Point.
	|		|
	| Router sends Session		| Router sends Session
	|-----Session Initialization---->| Initialization Message.		|-----Session Initialization---->| Initialization Message.
	|		|
	| Modem receives Session		| Modem receives Session
	| Initialization Message, and will		| Initialization Message, and will
	| not support the advertised		| not support the advertised
	| extensions.		| extensions.
	|		|
	| Modem sends Session Initialization		| Modem sends Session Initialization
	| Response, with 'Request Denied'		| Response, with 'Request Denied'
	|<-Session Initialization Resp.--| Status Data Item.		|<-Session Initialization Resp.--| Status Data Item.
	|		|
	|		|
	| Router receives negative Session		| Router receives negative Session
	| Initialization Response, closes		| Initialization Response, closes
	||---------TCP close------------|| TCP connection.		||---------TCP close------------|| TCP connection.
	B.3. Router Changes IP Addresses		B.3. Router Changes IP Addresses
	Router Modem Message Description		Router Modem Message Description
	========================================================================		========================================================================
	| Router sends Session Update		| Router sends Session Update
	|-------Session Update---------->| Message to announce change of IP		|-------Session Update---------->| Message to announce change of IP
	| address		| address
	|		|
	| Modem receives Session Update		| Modem receives Session Update
	| Message and updates internal		| Message and updates internal
	| state.		| state.
	|		|
	|<----Session Update Response----| Modem sends Session Update		|<----Session Update Response----| Modem sends Session Update
	| Response.		| Response.
	B.4. Modem Changes Session-wide Metrics		B.4. Modem Changes Session-wide Metrics
	Router Modem Message Description		Router Modem Message Description
	========================================================================		========================================================================
	| Modem sends Session Update Message		| Modem sends Session Update Message
	| to announce change of modem-wide		| to announce change of modem-wide
	|<--------Session Update---------| metrics		|<--------Session Update---------| metrics
	|		|
	| Router receives Session Update		| Router receives Session Update
	| Message and updates internal		| Message and updates internal
	| state.		| state.
	|		|
	|----Session Update Response---->| Router sends Session Update		|----Session Update Response---->| Router sends Session Update
	| Response.		| Response.
	B.5. Router Terminates Session		B.5. Router Terminates Session
			Router Modem Message Description
			========================================================================
	Router Modem Message Description		| Router sends Session Termination
	========================================================================		|------Session Termination------>| Message with Status Data Item.
			| |
	| Router sends Session Termination		|-------TCP shutdown (send)---> | Router stops sending Messages.
	|------Session Termination------>| Message with Status Data Item.		|
	| |		| Modem receives Session
	|-------TCP shutdown (send)---> | Router stops sending Messages.		| Termination, stops counting
	|		| received heartbeats and stops
	| Modem receives Session		| sending heartbeats.
	| Termination, stops counting		|
	| received heartbeats and stops		| Modem sends Session Termination
	| sending heartbeats.		|<---Session Termination Resp.---| Response with Status 'Success'.
	|		|
	| Modem sends Session Termination		| Modem stops sending Messages.
	|<---Session Termination Resp.---| Response with Status 'Success'.		|
	|		||---------TCP close------------|| Session terminated.
	| Modem stops sending Messages.
	|
	||---------TCP close------------|| Session terminated.
	B.6. Modem Terminates Session		B.6. Modem Terminates Session
	Router Modem Message Description		Router Modem Message Description
	========================================================================		========================================================================
	| Modem sends Session Termination		| Modem sends Session Termination
	|<----Session Termination--------| Message with Status Data Item.		|<----Session Termination--------| Message with Status Data Item.
	|		|
	| Modem stops sending Messages.		| Modem stops sending Messages.
	|		|
	| Router receives Session		| Router receives Session
	| Termination, stops counting		| Termination, stops counting
	| received heartbeats and stops		| received heartbeats and stops
	| sending heartbeats.		| sending heartbeats.
	|		|
	| Router sends Session Termination		| Router sends Session Termination
	|---Session Termination Resp.--->| Response with Status 'Success'.		|---Session Termination Resp.--->| Response with Status 'Success'.
	|		|
	| Router stops sending Messages.		| Router stops sending Messages.
	|		|
	||---------TCP close------------|| Session terminated.		||---------TCP close------------|| Session terminated.
	B.7. Session Heartbeats		B.7. Session Heartbeats
			Router Modem Message Description
			========================================================================
	Router Modem Message Description		|----------Heartbeat------------>| Router sends heartbeat Message
	========================================================================		|
	|----------Heartbeat------------>| Router sends heartbeat Message		| Modem resets heartbeats missed
	|		| counter.
	| Modem resets heartbeats missed
	| counter.
	~ ~ ~ ~ ~ ~ ~		~ ~ ~ ~ ~ ~ ~
	|---------[Any Message]--------->| When the Modem receives any		|---------[Any Message]--------->| When the Modem receives any
	| Message from the Router.		| Message from the Router.
	|		|
	| Modem resets heartbeats missed		| Modem resets heartbeats missed
	| counter.		| counter.
	~ ~ ~ ~ ~ ~ ~		~ ~ ~ ~ ~ ~ ~
	|<---------Heartbeat-------------| Modem sends heartbeat Message		|<---------Heartbeat-------------| Modem sends heartbeat Message
	|		|
	| Router resets heartbeats missed		| Router resets heartbeats missed
	| counter.		| counter.
	~ ~ ~ ~ ~ ~ ~		~ ~ ~ ~ ~ ~ ~
	|<--------[Any Message]----------| When the Router receives any		|<--------[Any Message]----------| When the Router receives any
	| Message from the Modem.		| Message from the Modem.
	|		|
	| Modem resets heartbeats missed		| Modem resets heartbeats missed
	| counter.		| counter.
	B.8. Router Detects a Heartbeat timeout		B.8. Router Detects a Heartbeat timeout
	Router Modem Message Description		Router Modem Message Description
	========================================================================		========================================================================
	X<----------------------| Router misses a heartbeat		X<----------------------| Router misses a heartbeat
	| X<----------------------| Router misses too many heartbeats		| X<----------------------| Router misses too many heartbeats
	|		|
	|		|
	|------Session Termination------>| Router sends Session Termination		|------Session Termination------>| Router sends Session Termination
	| Message with 'Timeout' Status		| Message with 'Timeout' Status
	| Data Item.		| Data Item.
	:		:
	: Termination proceeds...		: Termination proceeds...
	B.9. Modem Detects a Heartbeat timeout		B.9. Modem Detects a Heartbeat timeout
	Router Modem Message Description
	========================================================================
	|---------------------->X Modem misses a heartbeat		Router Modem Message Description
			========================================================================
	|---------------------->X | Modem misses too many heartbeats		|---------------------->X Modem misses a heartbeat
	|
	|		|---------------------->X | Modem misses too many heartbeats
	|<-----Session Termination-------| Modem sends Session Termination		|
	| Message with 'Timeout' Status		|
	| Data Item.		|<-----Session Termination-------| Modem sends Session Termination
	:		| Message with 'Timeout' Status
	: Termination proceeds...		| Data Item.
			:
			: Termination proceeds...
	Appendix C. Destination Specific Message Flows		Appendix C. Destination Specific Message Flows
	C.1. Common Destination Notification		C.1. Common Destination Notification
			Router Modem Message Description
			========================================================================
	Router Modem Message Description		| Modem detects a new logical
	========================================================================		| destination is reachable, and
			|<-------Destination Up----------| sends Destination Up Message.
	| Modem detects a new logical		|
	| destination is reachable, and		|------Destination Up Resp.----->| Router sends Destination Up
	|<-------Destination Up----------| sends Destination Up Message.		| Response.
	|
	|------Destination Up Resp.----->| Router sends Destination Up
	| Response.
	~ ~ ~ ~ ~ ~ ~		~ ~ ~ ~ ~ ~ ~
	| Modem detects change in logical		| Modem detects change in logical
	| destination metrics, and sends		| destination metrics, and sends
	|<-------Destination Update------| Destination Update Message.		|<-------Destination Update------| Destination Update Message.
	~ ~ ~ ~ ~ ~ ~		~ ~ ~ ~ ~ ~ ~
	| Modem detects change in logical		| Modem detects change in logical
	| destination metrics, and sends		| destination metrics, and sends
	|<-------Destination Update------| Destination Update Message.		|<-------Destination Update------| Destination Update Message.
	~ ~ ~ ~ ~ ~ ~		~ ~ ~ ~ ~ ~ ~
	| Modem detects logical destination		| Modem detects logical destination
	| is no longer reachable, and sends		| is no longer reachable, and sends
	|<-------Destination Down--------| Destination Down Message.		|<-------Destination Down--------| Destination Down Message.
	|		|
	| Router receives Destination Down,		| Router receives Destination Down,
	| updates internal state, and sends		| updates internal state, and sends
	|------Destination Down Resp.--->| Destination Down Response Message.		|------Destination Down Resp.--->| Destination Down Response Message.
	C.2. Multicast Destination Notification		C.2. Multicast Destination Notification
			Router Modem Message Description
			========================================================================
	Router Modem Message Description		| Router detects a new multicast
	========================================================================		| destination is in use, and sends
			|-----Destination Announce------>| Destination Announce Message.
	| Router detects a new multicast		|
	| destination is in use, and sends		| Modem updates internal state to
	|-----Destination Announce------>| Destination Announce Message.		| monitor multicast destination, and
	|		|<-----Dest. Announce Resp.------| sends Destination Announce
	| Modem updates internal state to		Response.
	| monitor multicast destination, and
	|<-----Dest. Announce Resp.------| sends Destination Announce
	Response.
	~ ~ ~ ~ ~ ~ ~		~ ~ ~ ~ ~ ~ ~
	| Modem detects change in multicast		| Modem detects change in multicast
	| destination metrics, and sends		| destination metrics, and sends
	|<-------Destination Update------| Destination Update Message.		|<-------Destination Update------| Destination Update Message.
	~ ~ ~ ~ ~ ~ ~		~ ~ ~ ~ ~ ~ ~
	| Modem detects change in multicast		| Modem detects change in multicast
	| destination metrics, and sends		| destination metrics, and sends
	|<-------Destination Update------| Destination Update Message.		|<-------Destination Update------| Destination Update Message.
	~ ~ ~ ~ ~ ~ ~		~ ~ ~ ~ ~ ~ ~
	| Router detects multicast		| Router detects multicast
	| destination is no longer in use,		| destination is no longer in use,
	|--------Destination Down------->| and sends Destination Down		|--------Destination Down------->| and sends Destination Down
	| Message.		| Message.
	|		|
	| Modem receives Destination Down,		| Modem receives Destination Down,
	| updates internal state, and sends		| updates internal state, and sends
	|<-----Destination Down Resp.----| Destination Down Response Message.		|<-----Destination Down Resp.----| Destination Down Response Message.
	C.3. Link Characteristics Request		C.3. Link Characteristics Request
			Router Modem Message Description
			========================================================================
	Router Modem Message Description		Destination has already been
	========================================================================		~ ~ ~ ~ ~ ~ ~ announced by either peer.
	Destination has already been
	~ ~ ~ ~ ~ ~ ~ announced by either peer.
	| Router requires different		| Router requires different
	| Characteristics for the		| Characteristics for the
	| destination, and sends Link		| destination, and sends Link
	|--Link Characteristics Request->| Characteristics Request Message.		|--Link Characteristics Request->| Characteristics Request Message.
	|		|
	| Modem attempts to adjust link		| Modem attempts to adjust link
	| properties to meet the received		| properties to meet the received
	| request, and sends a Link		| request, and sends a Link
	| Characteristics Response		| Characteristics Response
	|<---Link Characteristics Resp.--| Message with the new values.		|<---Link Characteristics Resp.--| Message with the new values.
	Authors' Addresses		Authors' Addresses
	Stan Ratliff		Stan Ratliff
	VT iDirect		VT iDirect
	13861 Sunrise Valley Drive, Suite 300		13861 Sunrise Valley Drive, Suite 300
	Herndon, VA 20171		Herndon, VA 20171
	USA		USA
	Email: sratliff@idirect.net		Email: sratliff@idirect.net
End of changes. 81 change blocks.
	483 lines changed or deleted		487 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/