draft-ietf-manet-dlep-11.txt   draft-ietf-manet-dlep-12.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 11, 2015 Expires: November 12, 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 10, 2015 May 11, 2015
Dynamic Link Exchange Protocol (DLEP) Dynamic Link Exchange Protocol (DLEP)
draft-ietf-manet-dlep-11 draft-ietf-manet-dlep-12
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
forwarding decisions. In mobile or other environments where these forwarding 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 45 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 11, 2015. This Internet-Draft will expire on November 12, 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 35, line 34 skipping to change at page 35, line 34
number (Section 11.7) to establish the TCP connection. number (Section 11.7) to establish the TCP connection.
8.4. IPv6 Connection Point 8.4. IPv6 Connection Point
The IPv6 Connection Point data item MAY appear in the Peer Offer The IPv6 Connection Point data item MAY appear in the Peer Offer
signal (Section 7.2). The IPv6 Connection Point data item indicates signal (Section 7.2). The IPv6 Connection Point data item indicates
the IPv6 address and, optionally, the TCP port number on the DLEP the IPv6 address and, optionally, the TCP port number on the DLEP
modem available for connections. If provided, the receiver MUST use modem available for connections. If provided, the receiver MUST use
this information to perform the TCP connect to the DLEP server. this information to perform the TCP connect to the DLEP server.
The IPv4 Connection Point data item contains the following fields: The IPv6 Connection Point 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 | IPv6 Address | | Data Item Type| Length | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 45, line 7 skipping to change at page 45, line 7
Current Data Rate (Transmit): A 64-bit unsigned integer, Current Data Rate (Transmit): A 64-bit unsigned integer,
representing the current data rate, in bits per second, that can representing the current data rate, in bits per second, that can
currently be achieved while transmitting traffic on the link. currently be achieved while transmitting traffic on the link.
If there is no distinction between current and maximum transmit data If there is no distinction between current and maximum transmit data
rates, current data rate transmit MUST be set equal to the maximum rates, current data rate transmit MUST be set equal to the maximum
data rate transmit. data rate transmit.
8.18. Latency 8.18. Latency
The Latency data item data item MUST appear in the Peer The Latency data item MUST appear in the Peer Initialization ACK
Initialization ACK signal (Section 7.4), and MAY appear in the Peer signal (Section 7.4), and MAY appear in the Peer Update
Update (Section 7.5), Destination Up (Section 7.9), Destination (Section 7.5), Destination Up (Section 7.9), Destination Update
Update (Section 7.13), and Link Characteristics ACK (Section 7.16) (Section 7.13), and Link Characteristics ACK (Section 7.16) signals
signals to indicate the amount of latency, in microseconds, on the to indicate the amount of latency, in microseconds, on the link.
link.
When used in the Link Characteristics Request signal (Section 7.15), When used in the Link Characteristics Request signal (Section 7.15),
Latency represents the maximum latency desired on the link. Latency represents the maximum latency desired on the link.
The Latency value is reported as delay. The calculation of latency The Latency value is reported as delay. The calculation of latency
is implementation dependent. For example, the latency may be a is implementation dependent. For example, the latency may be a
running average calculated from the internal queuing. running average calculated from the internal queuing.
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 | Latency | | Data Item Type| Length | Latency |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Latency (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Latency (cont.) | | Latency (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: TBD
Length: 4 Length: 8
Latency: A 32-bit unsigned integer, representing the transmission Latency: A 64-bit unsigned integer, representing the transmission
delay, in microseconds, that a packet encounters as it is delay, in microseconds, that a packet encounters as it is
transmitted over the link. transmitted over the link.
8.19. Resources (Receive) 8.19. Resources (Receive)
The Resources (Receive) (RESR) data item MAY appear in the Peer The Resources (Receive) (RESR) data item MAY appear in the Peer
Initialization ACK signal (Section 7.4), Peer Update (Section 7.5), Initialization ACK signal (Section 7.4), Peer Update (Section 7.5),
Destination Up (Section 7.9), Destination Update (Section 7.13) and Destination Up (Section 7.9), Destination Update (Section 7.13) and
Link Characteristics ACK (Section 7.16) signals to indicate the Link Characteristics ACK (Section 7.16) signals to indicate the
amount of resources for reception (with 0 meaning 'no resources amount of resources for reception (with 0 meaning 'no resources
skipping to change at page 57, line 12 skipping to change at page 57, line 12
Greg Harrison, Chris Olsen, Martin Duke, Subir Das, Jaewon Kang, Greg Harrison, Chris Olsen, Martin Duke, Subir Das, Jaewon Kang,
Vikram Kaul, Nelson Powell and Victoria Mercieca. Vikram Kaul, Nelson Powell and Victoria Mercieca.
13. References 13. References
13.1. Normative References 13.1. Normative References
[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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5578] Berry, B., Ratliff, S., Paradise, E., Kaiser, T., and M.
Adams, "PPP over Ethernet (PPPoE) Extensions for Credit
Flow and Link Metrics", RFC 5578, February 2010.
13.2. Informative References 13.2. Informative References
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5578] Berry, B., Ratliff, S., Paradise, E., Kaiser, T., and M.
Adams, "PPP over Ethernet (PPPoE) Extensions for Credit
Flow and Link Metrics", RFC 5578, February 2010.
Appendix A. Peer Level Signal Flows Appendix A. Peer Level Signal Flows
A.1. Discovery A.1. Discovery
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---->|| signal. |-------Peer Discovery---->|| signal.
 End of changes. 12 change blocks. 
18 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/