Mobile Ad hoc Networks I. Chakeres
Internet-Draft Motorola
Intended status: Standards Track February 2, 2008
Expires: August 5, 2008
MANET_ID TLV
draft-chakeres-manet-manetid-03.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 5, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract
This document defines a message TLV named MANET_ID. The MANET_ID TLV
is used by a (DYMO) process to identify information as belonging to a
particular (DYMO) instance. This specification enables multiple
instances of (DYMO) to run independently on the same node over the
same interfaces.
Chakeres Expires August 5, 2008 [Page 1]
Internet-Draft MANET-ID February 2008
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. MANET_ID TLV . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. (DYMO) Protocol Operation . . . . . . . . . . . . . . . . . . . 4
4.1. (DYMO) Configuration . . . . . . . . . . . . . . . . . . . 4
4.2. Message Reception . . . . . . . . . . . . . . . . . . . . . 4
4.3. Sending Control Messages . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . . . 7
Chakeres Expires August 5, 2008 [Page 2]
Internet-Draft MANET-ID February 2008
1. Introduction
This specification enables multiple instances of (DYMO
[I-D.ietf-manet-dymo]) to run independently on the same node over the
same interface(s). This document specifies a message TLV structure
named MANET_ID for [I-D.ietf-manet-packetbb]. This TLV is used by a
(DYMO) process to identify its information. On reception of a
routing protocol message, if the value of the MANET_ID TLV is
different from the (DYMO) routing process's configured MANET ID
value, then the message is discarded without processing.
2. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Additionally, this document uses terminology from
[I-D.ietf-manet-packetbb].
In this document, we define the following terminology:
Process
A (DYMO) process is a running instantiation of the (DYMO) routing
protocol.
Instance
A (DYMO) instance is a separate protocol instance complete with
its own protocol data structures (e.g. routing table), protocol
state machines, and protocol processes (e.g. route discovery).
MANET ID
The MANET ID enables multiple instances of a (DYMO) routing
protocol to be run independently on the same node over the same
interface(s). Received messages whose MANET ID value is not
identical to the routing protocol instance's MANET ID value are
discarded without processing.
Process's MANET ID Value (<p_manet_id>)
The MANET ID value associated with a (DYMO) routing process is
referred to as its <p_manet_id>.
Message's MANET ID Value (<m_manet_id>)
The MANET ID value associated with a (DYMO) routing protocol
message is carried in a MANET_ID TLV, and it is referred to as the
message's <m_manet_id>.
Chakeres Expires August 5, 2008 [Page 3]
Internet-Draft MANET-ID February 2008
3. MANET_ID TLV
The MANET_ID TLV is a message TLV. The MANET_ID TLV is a single
value TLV as defined in [I-D.ietf-manet-packetbb].
4. (DYMO) Protocol Operation
This section describes specific (DYMO) routing protocol behavior
based on <p_manet_id> and <m_manet_id>.
NOTE: The placement of the protocol operation text within this
document serves as a temporary location for discussion. The protocol
operation text here will be shifted into the protocol specifications
of protocols that wish to use the MANET_ID TLV in the future.
4.1. (DYMO) Configuration
A (DYMO) routing protocol instance must be administratively
configured to only process messages with a specific MANET_ID value,
<p_manet_id>.
4.2. Message Reception
When a message is received without an MANET_ID TLV, the message's
MANET_ID value (<m_manet_id>) is assumed to be zero (0).
When a message is received with more than one MANET_ID TLV, it is
invalid and MUST NOT be processed.
When a message is received with one MANET_ID TLV, <m_manet_id> is
contained.
If <p_manet_id> is identical to <m_manet_id>, then the message is
processed normally. Otherwise, the message MUST NOT be not
processed.
4.3. Sending Control Messages
When a (DYMO) process with a configured <p_manet_id> sends routing
protocol control messages, the information MUST be identified by
tagging it with an MANET_ID TLV containing <p_manet_id>.
If the (DYMO) process does not have a configured <p_manet_id>, then
it SHOULD NOT include an MANET_ID TLV. If an MANET_ID TLV is
included the value MUST be set to zero (0).
Chakeres Expires August 5, 2008 [Page 4]
Internet-Draft MANET-ID February 2008
5. IANA Considerations
TLV Assignments
+----------+----------+--------------------------------------------+
| Mnemonic | TLV Type | Assigned Type Value |
+----------+----------+--------------------------------------------+
| MANET_ID | Message | TBD1 - IANA please allocate from 0-7 range |
+----------+----------+--------------------------------------------+
Table 1
6. Security Considerations
The TLV specified in this document and the protocol operation
described, do not provide any security (e.g. authentication or
certification).
7. Acknowledgements
Portions of this document were based upon [I-D.ietf-manet-timetlv]
and [RFC2740].
8. References
8.1. Normative References
[I-D.ietf-manet-dymo]
Chakeres, I. and C. Perkins, "Dynamic MANET On-demand
(DYMO) Routing", draft-ietf-manet-dymo-11 (work in
progress), November 2007.
[I-D.ietf-manet-packetbb]
Clausen, T., Dearlove, C., Dean, J., and C. Adjih,
"Generalized MANET Packet/Message Format",
draft-ietf-manet-packetbb-11 (work in progress),
November 2007.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
8.2. Informative References
[I-D.ietf-manet-timetlv]
Clausen, T. and C. Dearlove, "Representing multi-value
Chakeres Expires August 5, 2008 [Page 5]
Internet-Draft MANET-ID February 2008
time in MANETs", draft-ietf-manet-timetlv-04 (work in
progress), November 2007.
[RFC2740] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6",
RFC 2740, December 1999.
Author's Address
Ian D Chakeres
Motorola
Bagmane Tech Park
66/1, Plot 5, CV Raman Nagar
Bangalore, Karnataka 560093
India
Email: ian.chakeres@gmail.com
URI: http://www.ianchak.com/
Chakeres Expires August 5, 2008 [Page 6]
Internet-Draft MANET-ID February 2008
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Chakeres Expires August 5, 2008 [Page 7]