< draft-ietf-manet-dlep-13.txt		draft-ietf-manet-dlep-14.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: November 13, 2015		Expires: November 14, 2015
	S. Jury		S. Jury
	Cisco Systems		Cisco Systems
	D. Satterwhite		D. Satterwhite
	Broadcom		Broadcom
	R. Taylor		R. Taylor
	Airbus Defence & Space		Airbus Defence & Space
	May 12, 2015		May 13, 2015
	Dynamic Link Exchange Protocol (DLEP)		Dynamic Link Exchange Protocol (DLEP)
	draft-ietf-manet-dlep-13		draft-ietf-manet-dlep-14
	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 44 ¶
	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 November 13, 2015.		This Internet-Draft will expire on November 14, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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
	skipping to change at page 3, line 23 ¶		skipping to change at page 3, line 23 ¶
	8.5. Peer Type . . . . . . . . . . . . . . . . . . . . . . . . 36		8.5. Peer Type . . . . . . . . . . . . . . . . . . . . . . . . 36
	8.6. Heartbeat Interval . . . . . . . . . . . . . . . . . . . 36		8.6. Heartbeat Interval . . . . . . . . . . . . . . . . . . . 36
	8.7. Extensions Supported . . . . . . . . . . . . . . . . . . 37		8.7. Extensions Supported . . . . . . . . . . . . . . . . . . 37
	8.8. Experimental Definition . . . . . . . . . . . . . . . . . 38		8.8. Experimental Definition . . . . . . . . . . . . . . . . . 38
	8.9. MAC Address . . . . . . . . . . . . . . . . . . . . . . . 38		8.9. MAC Address . . . . . . . . . . . . . . . . . . . . . . . 38
	8.10. IPv4 Address . . . . . . . . . . . . . . . . . . . . . . 39		8.10. IPv4 Address . . . . . . . . . . . . . . . . . . . . . . 39
	8.11. IPv6 Address . . . . . . . . . . . . . . . . . . . . . . 40		8.11. IPv6 Address . . . . . . . . . . . . . . . . . . . . . . 40
	8.12. IPv4 Attached Subnet . . . . . . . . . . . . . . . . . . 40		8.12. IPv4 Attached Subnet . . . . . . . . . . . . . . . . . . 40
	8.13. IPv6 Attached Subnet . . . . . . . . . . . . . . . . . . 41		8.13. IPv6 Attached Subnet . . . . . . . . . . . . . . . . . . 41
	8.14. Maximum Data Rate (Receive) . . . . . . . . . . . . . . . 42		8.14. Maximum Data Rate (Receive) . . . . . . . . . . . . . . . 42
	8.15. Maximum Data Rate (Transmit) . . . . . . . . . . . . . . 42		8.15. Maximum Data Rate (Transmit) . . . . . . . . . . . . . . 43
	8.16. Current Data Rate (Receive) . . . . . . . . . . . . . . . 43		8.16. Current Data Rate (Receive) . . . . . . . . . . . . . . . 43
	8.17. Current Data Rate (Transmit) . . . . . . . . . . . . . . 44		8.17. Current Data Rate (Transmit) . . . . . . . . . . . . . . 44
	8.18. Latency . . . . . . . . . . . . . . . . . . . . . . . . . 45		8.18. Latency . . . . . . . . . . . . . . . . . . . . . . . . . 45
	8.19. Resources (Receive) . . . . . . . . . . . . . . . . . . . 45		8.19. Resources (Receive) . . . . . . . . . . . . . . . . . . . 46
	8.20. Resources (Transmit) . . . . . . . . . . . . . . . . . . 46		8.20. Resources (Transmit) . . . . . . . . . . . . . . . . . . 46
	8.21. Relative Link Quality (Receive) . . . . . . . . . . . . . 47		8.21. Relative Link Quality (Receive) . . . . . . . . . . . . . 47
	8.22. Relative Link Quality (Transmit) . . . . . . . . . . . . 47		8.22. Relative Link Quality (Transmit) . . . . . . . . . . . . 48
	8.23. Link Characteristics ACK Timer . . . . . . . . . . . . . 48		8.23. Link Characteristics ACK Timer . . . . . . . . . . . . . 48
	9. Credit-Windowing . . . . . . . . . . . . . . . . . . . . . . 48		9. Credit-Windowing . . . . . . . . . . . . . . . . . . . . . . 49
	9.1. Credit-Windowing Signals . . . . . . . . . . . . . . . . 49		9.1. Credit-Windowing Signals . . . . . . . . . . . . . . . . 49
	9.1.1. Destination Up Signal . . . . . . . . . . . . . . . . 49		9.1.1. Destination Up Signal . . . . . . . . . . . . . . . . 49
	9.1.2. Destination Up ACK Signal . . . . . . . . . . . . . . 49		9.1.2. Destination Up ACK Signal . . . . . . . . . . . . . . 50
	9.1.3. Destination Update Signal . . . . . . . . . . . . . . 49		9.1.3. Destination Update Signal . . . . . . . . . . . . . . 50
	9.2. Credit-Windowing Data Items . . . . . . . . . . . . . . . 50		9.2. Credit-Windowing Data Items . . . . . . . . . . . . . . . 50
	9.2.1. Credit Grant . . . . . . . . . . . . . . . . . . . . 50		9.2.1. Credit Grant . . . . . . . . . . . . . . . . . . . . 51
	9.2.2. Credit Window Status . . . . . . . . . . . . . . . . 51		9.2.2. Credit Window Status . . . . . . . . . . . . . . . . 52
	9.2.3. Credit Request . . . . . . . . . . . . . . . . . . . 52		9.2.3. Credit Request . . . . . . . . . . . . . . . . . . . 52
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 53		10. Security Considerations . . . . . . . . . . . . . . . . . . . 53
	11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53		11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53
	11.1. Registrations . . . . . . . . . . . . . . . . . . . . . 53		11.1. Registrations . . . . . . . . . . . . . . . . . . . . . 53
	11.2. Expert Review: Evaluation Guidelines . . . . . . . . . . 53		11.2. Expert Review: Evaluation Guidelines . . . . . . . . . . 54
	11.3. Signal Type Registration . . . . . . . . . . . . . . . . 54		11.3. Signal Type Registration . . . . . . . . . . . . . . . . 54
	11.4. DLEP Data Item Registrations . . . . . . . . . . . . . . 54		11.4. DLEP Data Item Registrations . . . . . . . . . . . . . . 55
	11.5. DLEP Status Code Registrations . . . . . . . . . . . . . 56		11.5. DLEP Status Code Registrations . . . . . . . . . . . . . 56
	11.6. DLEP Extensions Registrations . . . . . . . . . . . . . 56		11.6. DLEP Extensions Registrations . . . . . . . . . . . . . 56
	11.7. DLEP Well-known Port . . . . . . . . . . . . . . . . . . 56		11.7. DLEP Well-known Port . . . . . . . . . . . . . . . . . . 57
	11.8. DLEP Multicast Address . . . . . . . . . . . . . . . . . 57		11.8. DLEP Multicast Address . . . . . . . . . . . . . . . . . 57
	12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57		12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57
	13. References . . . . . . . . . . . . . . . . . . . . . . . . . 57		13. References . . . . . . . . . . . . . . . . . . . . . . . . . 57
	13.1. Normative References . . . . . . . . . . . . . . . . . . 57		13.1. Normative References . . . . . . . . . . . . . . . . . . 57
	13.2. Informative References . . . . . . . . . . . . . . . . . 57		13.2. Informative References . . . . . . . . . . . . . . . . . 57
	Appendix A. Peer Level Signal Flows . . . . . . . . . . . . . . 57		Appendix A. Peer Level Signal Flows . . . . . . . . . . . . . . 57
	A.1. Discovery . . . . . . . . . . . . . . . . . . . . . . . . 57		A.1. Discovery . . . . . . . . . . . . . . . . . . . . . . . . 57
	A.2. Session Initialization . . . . . . . . . . . . . . . . . 58		A.2. Session Initialization . . . . . . . . . . . . . . . . . 58
	A.3. Session Initialization - Refused . . . . . . . . . . . . 59		A.3. Session Initialization - Refused . . . . . . . . . . . . 59
	A.4. Router Changes IP Addresses . . . . . . . . . . . . . . . 59		A.4. Router Changes IP Addresses . . . . . . . . . . . . . . . 59
	skipping to change at page 41, line 22 ¶		skipping to change at page 41, line 22 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| IPv4 Attached Subnet | Prefix Len. |		| IPv4 Attached Subnet | Prefix Len. |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Data Item Type: TBD		Data Item Type: TBD
	Length: 5		Length: 5
	IPv4 Subnet: The IPv4 subnet reachable at the destination.		IPv4 Subnet: The IPv4 subnet reachable at the destination.
	Prefix Length: Length of the prefix (0-32) for the IPv4 subnet.		Prefix Length: Length of the prefix (1-32) for the IPv4 subnet. A
			prefix length outside the speficied range MUST be considered as
			invalid.
	8.13. IPv6 Attached Subnet		8.13. IPv6 Attached Subnet
	The DLEP IPv6 Attached Subnet allows a device to declare that it has		The DLEP IPv6 Attached Subnet allows a device to declare that it has
	an IPv6 subnet (e.g., a stub network) attached, or that it has become		an IPv6 subnet (e.g., a stub network) attached, or that it has become
	aware of an IPv6 subnet being present at a remote destination. The		aware of an IPv6 subnet being present at a remote destination. The
	IPv6 Attached Subnet data item MAY appear in the Destination Up		IPv6 Attached Subnet data item MAY appear in the Destination Up
	(Section 7.9) and Destination Update (Section 7.13) signals. As in		(Section 7.9) and Destination Update (Section 7.13) signals. As in
	the case of the IPv4 attached Subnet data item above, once an IPv6		the case of the IPv4 attached Subnet data item above, once an IPv6
	attached subnet has been declared, it can NOT be withdrawn without		attached subnet has been declared, it can NOT be withdrawn without
	skipping to change at page 42, line 4 ¶		skipping to change at page 42, line 18 ¶
	| Data Item Type| Length | IPv6 Attached Subnet |		| Data Item Type| Length | IPv6 Attached Subnet |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| IPv6 Attached Subnet |		| IPv6 Attached Subnet |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| IPv6 Attached Subnet |		| IPv6 Attached Subnet |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| IPv6 Attached Subnet |		| IPv6 Attached Subnet |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| IPv6 Attached Subnet | Prefix Len. |		| IPv6 Attached Subnet | Prefix Len. |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Data Item Type: TBD		Data Item Type: TBD
	Length: 17		Length: 17
	IPv4 Subnet: The IPv6 subnet reachable at the destination.		IPv4 Subnet: The IPv6 subnet reachable at the destination.
	Prefix Length: Length of the prefix (0-128) for the IPv6 subnet.		Prefix Length: Length of the prefix (1-128) for the IPv6 subnet. A
			prefix length outside the specified range MUST be considered as
			invalid.
	8.14. Maximum Data Rate (Receive)		8.14. Maximum Data Rate (Receive)
	The Maximum Data Rate (Receive) (MDRR) data item MUST appear in the		The Maximum Data Rate (Receive) (MDRR) data item MUST appear in the
	Peer Initialization ACK signal (Section 7.4), and MAY appear in the		Peer Initialization ACK signal (Section 7.4), and MAY appear in the
	Peer Update (Section 7.5), Destination Up (Section 7.9), Destination		Peer Update (Section 7.5), Destination Up (Section 7.9), Destination
	Update (Section 7.13) and Link Characteristics ACK (Section 7.16)		Update (Section 7.13) and Link Characteristics ACK (Section 7.16)
	signals to indicate the maximum theoretical data rate, in bits per		signals to indicate the maximum theoretical data rate, in bits per
	second, that can be achieved while receiving data on the link.		second, that can be achieved while receiving data on the link.
	skipping to change at page 47, line 27 ¶		skipping to change at page 47, line 46 ¶
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Data Item Type| Length | RLQR |		| Data Item Type| Length | RLQR |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Data Item Type: TBD		Data Item Type: TBD
	Length: 1		Length: 1
	Relative Link Quality (Receive): A non-dimensional 8-bit integer,		Relative Link Quality (Receive): A non-dimensional 8-bit integer,
	1-100, representing relative link quality. A value of 100		0-100, representing relative link quality. A value of 100
	represents a link of the highest quality. Any value greater than		represents a link of the highest quality. Any value greater than
	100 MUST be considered as invalid.		100 MUST be considered as invalid.
	If a device cannot calculate the RLQR, this data item SHOULD NOT be		If a device cannot calculate the RLQR, this data item SHOULD NOT be
	issued.		issued.
	8.22. Relative Link Quality (Transmit)		8.22. Relative Link Quality (Transmit)
	The Relative Link Quality (Transmit) (RLQT) data item MAY appear in		The Relative Link Quality (Transmit) (RLQT) data item MAY appear in
	the Peer Initialization ACK signal (Section 7.4), Peer Update		the Peer Initialization ACK signal (Section 7.4), Peer Update
	skipping to change at page 48, line 4 ¶		skipping to change at page 48, line 23 ¶
	The Relative Link Quality (Transmit) data item contains the following		The Relative Link Quality (Transmit) data item contains the following
	fields:		fields:
	0 1 2		0 1 2
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Data Item Type| Length | RLQT |		| Data Item Type| Length | RLQT |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Data Item Type: TBD		Data Item Type: TBD
	Length: 1		Length: 1
	Relative Link Quality (Transmit): A non-dimensional 8-bit integer,		Relative Link Quality (Transmit): A non-dimensional 8-bit integer,
	1-100, representing relative link quality. A value of 100		0-100, representing relative link quality. A value of 100
	represents a link of the highest quality. Any value greater than		represents a link of the highest quality. Any value greater than
	100 MUST be considered as invalid.		100 MUST be considered as invalid.
	If a device cannot calculate the RLQT, this data item SHOULD NOT be		If a device cannot calculate the RLQT, this data item SHOULD NOT be
	issued.		issued.
	8.23. Link Characteristics ACK Timer		8.23. Link Characteristics ACK Timer
	The Link Characteristics ACK Timer data item MAY appear in the Link		The Link Characteristics ACK Timer data item MAY appear in the Link
	Characteristics Request signal (Section 7.15) to indicate the desired		Characteristics Request signal (Section 7.15) to indicate the desired
End of changes. 19 change blocks.
	19 lines changed or deleted		25 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/