draft-ietf-manet-timetlv-03.txt   draft-ietf-manet-timetlv-04.txt 
Mobile Ad hoc Networking (MANET) T. Clausen Mobile Ad hoc Networking (MANET) T. Clausen
Internet-Draft LIX, Ecole Polytechnique, France Internet-Draft LIX, Ecole Polytechnique, France
Intended status: Standards Track C. Dearlove Intended status: Standards Track C. Dearlove
Expires: May 18, 2008 BAE Systems Advanced Technology Expires: May 19, 2008 BAE Systems Advanced Technology
Centre Centre
November 15, 2007 November 16, 2007
Representing multi-value time in MANETs Representing multi-value time in MANETs
draft-ietf-manet-timetlv-03 draft-ietf-manet-timetlv-04
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 18, 2008. This Internet-Draft will expire on May 19, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document describes a general and flexible TLV (type-length-value This document describes a general and flexible TLV (type-length-value
structure) for representing time using the generalized MANET packet/ structure) for representing time using the generalized MANET packet/
message format. It defines two message and two address block TLVs message format. It defines two message and two address block TLVs
skipping to change at page 2, line 28 skipping to change at page 2, line 28
4. Protocol Overview and Functioning . . . . . . . . . . . . . . 6 4. Protocol Overview and Functioning . . . . . . . . . . . . . . 6
5. Representing Time . . . . . . . . . . . . . . . . . . . . . . 7 5. Representing Time . . . . . . . . . . . . . . . . . . . . . . 7
6. General Time TLV Structure . . . . . . . . . . . . . . . . . . 8 6. General Time TLV Structure . . . . . . . . . . . . . . . . . . 8
7. Message TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 10 7. Message TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. VALIDITY_TIME TLV . . . . . . . . . . . . . . . . . . . . 10 7.1. VALIDITY_TIME TLV . . . . . . . . . . . . . . . . . . . . 10
7.2. INTERVAL_TIME TLV . . . . . . . . . . . . . . . . . . . . 10 7.2. INTERVAL_TIME TLV . . . . . . . . . . . . . . . . . . . . 10
8. Address Block TLVs . . . . . . . . . . . . . . . . . . . . . . 11 8. Address Block TLVs . . . . . . . . . . . . . . . . . . . . . . 11
8.1. VALIDITY_TIME TLV . . . . . . . . . . . . . . . . . . . . 11 8.1. VALIDITY_TIME TLV . . . . . . . . . . . . . . . . . . . . 11
8.2. INTERVAL_TIME TLV . . . . . . . . . . . . . . . . . . . . 11 8.2. INTERVAL_TIME TLV . . . . . . . . . . . . . . . . . . . . 11
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
9.1. Message TLV tyepes . . . . . . . . . . . . . . . . . . . . 12 9.1. Message TLV Types . . . . . . . . . . . . . . . . . . . . 12
9.2. Address Block TLV tyepes . . . . . . . . . . . . . . . . . 13 9.2. Address Block TLV Types . . . . . . . . . . . . . . . . . 13
10. Security Considerations . . . . . . . . . . . . . . . . . . . 14 10. Security Considerations . . . . . . . . . . . . . . . . . . . 14
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
11.1. Normative References . . . . . . . . . . . . . . . . . . . 15 11.1. Normative References . . . . . . . . . . . . . . . . . . . 15
11.2. Informative References . . . . . . . . . . . . . . . . . . 15 11.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 16 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 18 Intellectual Property and Copyright Statements . . . . . . . . . . 18
1. Introduction 1. Introduction
skipping to change at page 7, line 33 skipping to change at page 7, line 33
An algorithm for computing the time-code representing the smallest An algorithm for computing the time-code representing the smallest
representable time-value not less than the time-value t is: representable time-value not less than the time-value t is:
1. find the largest integer b such that t/C >= 2^b; 1. find the largest integer b such that t/C >= 2^b;
2. set a = 8 * (t / (C * 2^b) - 1), rounded up to the nearest 2. set a = 8 * (t / (C * 2^b) - 1), rounded up to the nearest
integer; integer;
3. if a == 8 then set b = b + 1 and set a = 0; 3. if a == 8 then set b = b + 1 and set a = 0;
4. if 0 <= a <= 7, and 0 lt;= b <= 31, then the required time-value 4. if 0 <= a <= 7, and 0 &lt;= b <= 31, then the required time-value
can be represented by the time-code 8 * b + a, otherwise it can can be represented by the time-code 8 * b + a, otherwise it can
not. not.
The minimum time-value that can be represented in this manner is C. The minimum time-value that can be represented in this manner is C.
The maximum time-value that can be represented in this manner is 15 * The maximum time-value that can be represented in this manner is 15 *
2^28 * C, or about 4.0 * 10^9 * C. If, for example, C = 1/1024 2^28 * C, or about 4.0 * 10^9 * C. If, for example, C = 1/1024
second, then this is about 45 days. second, then this is about 45 days.
A protocol using this time representation MUST define the value of C. A protocol using this time representation MUST define the value of C.
A protocol using this specification MAY specify that the all bits A protocol using this specification MAY specify that the all bits
skipping to change at page 12, line 16 skipping to change at page 12, line 16
This specification defines two message TLV types, which must be This specification defines two message TLV types, which must be
allocated from the "Assigned Message TLV Types" repository of [1] as allocated from the "Assigned Message TLV Types" repository of [1] as
specified in Table 1 and two address block TLV types, which must be specified in Table 1 and two address block TLV types, which must be
allocated from the "Assigned Address Block TLV Types" repository of allocated from the "Assigned Address Block TLV Types" repository of
[1] as specified in Table 2. [1] as specified in Table 2.
IANA is requested to assign the same numerical value to the message IANA is requested to assign the same numerical value to the message
TLV and address block TLV types with the same mnemonic. TLV and address block TLV types with the same mnemonic.
9.1. Message TLV tyepes 9.1. Message TLV Types
+---------------+------+-----------+--------------------------------+ +---------------+------+-----------+--------------------------------+
| Name | Type | Type | Description | | Name | Type | Type | Description |
| | | Extension | | | | | Extension | |
+---------------+------+-----------+--------------------------------+ +---------------+------+-----------+--------------------------------+
| VALIDITY_TIME | TBD1 | 0 | The time from receipt of the | | VALIDITY_TIME | TBD1 | 0 | The time from receipt of the |
| | | | message during which the | | | | | message during which the |
| | | | information contained in the | | | | | information contained in the |
| | | | message is to be considered | | | | | message is to be considered |
| | | | valid | | | | | valid |
skipping to change at page 13, line 5 skipping to change at page 13, line 5
| | | | received | | | | | received |
| | | | | | | | | |
| | | 1-255 | RESERVED | | | | 1-255 | RESERVED |
+---------------+------+-----------+--------------------------------+ +---------------+------+-----------+--------------------------------+
Table 1 Table 1
Type extensions indicated as RESERVED may be allocated by standards Type extensions indicated as RESERVED may be allocated by standards
action, as specified in [3]. action, as specified in [3].
9.2. Address Block TLV tyepes 9.2. Address Block TLV Types
+---------------+------+-----------+--------------------------------+ +---------------+------+-----------+--------------------------------+
| Name | Type | Type | Description | | Name | Type | Type | Description |
| | | extension | | | | | extension | |
+---------------+------+-----------+--------------------------------+ +---------------+------+-----------+--------------------------------+
| VALIDITY_TIME | TBD1 | 0 | The time from receipt of the | | VALIDITY_TIME | TBD1 | 0 | The time from receipt of the |
| | | | address during which the | | | | | address during which the |
| | | | information regarding this | | | | | information regarding this |
| | | | address is to be considered | | | | | address is to be considered |
| | | | valid | | | | | valid |
 End of changes. 8 change blocks. 
9 lines changed or deleted 9 lines changed or added

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