draft-ietf-manet-timetlv-02.txt   draft-ietf-manet-timetlv-03.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: February 25, 2008 BAE Systems Advanced Technology Expires: May 18, 2008 BAE Systems Advanced Technology
Centre Centre
August 24, 2007 November 15, 2007
Representing multi-value time in MANETs Representing multi-value time in MANETs
draft-ietf-manet-timetlv-02 draft-ietf-manet-timetlv-03
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 February 25, 2008. This Internet-Draft will expire on May 18, 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 12, line 13 skipping to change at page 12, line 13
Section 5. Section 5.
9. IANA Considerations 9. IANA Considerations
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 nummerical 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 tyepes
+---------------+------+---------+----------------------------------+ +---------------+------+-----------+--------------------------------+
| Name | Type | Subtype | Description | | Name | Type | Type | Description |
+---------------+------+---------+----------------------------------+ | | | Extension | |
| VALIDITY_TIME | TBD | 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 |
| | | | | | | | | |
| | | 1-255 | RESERVED | | | | 1-255 | RESERVED |
| | | | | | | | | |
| INTERVAL_TIME | TBD | 0 | The maximum time before another | | INTERVAL_TIME | TBD2 | 0 | The maximum time before |
| | | | message of the same type as this | | | | | another message of the same |
| | | | message from the same originator | | | | | type as this message from the |
| | | | should be received | | | | | same originator should be |
| | | | received |
| | | | | | | | | |
| | | 1-255 | RESERVED | | | | 1-255 | RESERVED |
+---------------+------+---------+----------------------------------+ +---------------+------+-----------+--------------------------------+
Table 1 Table 1
Subtypes indicated as RESERVED may be allocated by standards action, Type extensions indicated as RESERVED may be allocated by standards
as specified in [3]. action, as specified in [3].
9.2. Address Block TLV tyepes 9.2. Address Block TLV tyepes
+---------------+------+---------+----------------------------------+ +---------------+------+-----------+--------------------------------+
| Name | Type | Subtype | Description | | Name | Type | Type | Description |
+---------------+------+---------+----------------------------------+ | | | extension | |
| VALIDITY_TIME | TBD | 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 |
| | | | | | | | | |
| | | 1-255 | RESERVED | | | | 1-255 | RESERVED |
| | | | | | | | | |
| INTERVAL_TIME | TBD | 0 | The maximum time before another | | INTERVAL_TIME | TBD2 | 0 | The maximum time before |
| | | | message of the same type as this | | | | | another message of the same |
| | | | message from the same originator | | | | | type as this message from the |
| | | | and containing this address | | | | | same originator and containing |
| | | | should be received | | | | | this address should be |
| | | | received |
| | | | | | | | | |
| | | 1-255 | RESERVED | | | | 1-255 | RESERVED |
+---------------+------+---------+----------------------------------+ +---------------+------+-----------+--------------------------------+
Table 2 Table 2
Subtypes indicated as RESERVED may be allocated by standards action, Type extensions indicated as RESERVED may be allocated by standards
as specified in [3]. action, as specified in [3].
10. Security Considerations 10. Security Considerations
This document does not specify any security considerations. This document does not specify any security considerations.
11. References 11. References
11.1. Normative References 11.1. Normative References
[1] Clausen, T., Dearlove, C., Dean, J., and C. Adjih, "Generalized [1] Clausen, T., Dearlove, C., Dean, J., and C. Adjih, "Generalized
MANET Packet/Message Format", Work In MANET Packet/Message Format", Work In
Progress draft-ietf-manet-packetbb-08.txt, July 2007. Progress draft-ietf-manet-packetbb-11.txt, November 2007.
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, BCP 14, March 1997. Levels", RFC 2119, BCP 14, March 1997.
[3] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [3] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", October 1998. Considerations Section in RFCs", RFC 2434, BCP 26, October 1998.
11.2. Informative References 11.2. Informative References
[4] Clausen, T. and P. Jacquet, "The Optimized Link State Routing [4] Clausen, T. and P. Jacquet, "The Optimized Link State Routing
Protocol", RFC 3626, October 2003. Protocol", RFC 3626, October 2003.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors would like to thank Brian Adamson and Justin Dean (both The authors would like to thank Brian Adamson and Justin Dean (both
NRL) for their contributions, and Alan Cullen (BAE Systems) for his NRL) for their contributions, and Alan Cullen (BAE Systems) for his
 End of changes. 15 change blocks. 
30 lines changed or deleted 34 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/