Mobile Ad hoc Networks I. Chakeres Internet-Draft Motorola Intended status: Standards Track January 14, 2008 Expires: July 17, 2008 MANET_ID TLV draft-chakeres-manet-manetid-01.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 July 17, 2008. Copyright Notice Copyright (C) The IETF Trust (2008). Abstract This document defines a packet and a message TLV named MANET_ID. The MANET_ID TLV is used by DYMO routers to identify information that should be processed. Chakeres Expires July 17, 2008 [Page 1] Internet-Draft MANET-ID January 2008 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. MANET_ID TLV Structure . . . . . . . . . . . . . . . . . . . . 3 4. DYMO Protocol Operation . . . . . . . . . . . . . . . . . . . . 3 4.1. DYMO Router Configuration . . . . . . . . . . . . . . . . . 3 4.2. Packet Processing . . . . . . . . . . . . . . . . . . . . . 3 4.3. Message Processing . . . . . . . . . . . . . . . . . . . . 4 4.4. Sending Packets/Messages . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5 8.2. Informative References . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Intellectual Property and Copyright Statements . . . . . . . . . . 6 Chakeres Expires July 17, 2008 [Page 2] Internet-Draft MANET-ID January 2008 1. Introduction This document specifies a TLV structure named MANET_ID for the generalize packet/message format [I-D.ietf-manet-packetbb]. This TLV is used by DYMO routers to identify information that should be processed and/or forwarded. This TLV type can be attached to a packet or a message. 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]. 3. MANET_ID TLV Structure A MANET_ID TLV may be a packet or a message TLV. If the MANET_ID TLV is attached a packet or message, then it must be a single value TLV as defined in [I-D.ietf-manet-packetbb]. The of the MANET_ID TLV is a integer value. The maximum length is 64-bits (8-bytes). 4. DYMO Protocol Operation This document recommends specific DYMO protocol instance behavior based on the MANET_ID TLV value. 4.1. DYMO Router Configuration A DYMO router must be administratively configured to only process packets/messages with a specific certain MANET_ID value. For simplicity, we will refer the configured MANET_ID value as MY_MANET_ID. 4.2. Packet Processing When a packet is received without a MANET_ID TLV, the packet's MANET_ID value is assumed to be zero (0). When a packet is received containing a MANET_ID TLV, its MANET_ID value is contained. Chakeres Expires July 17, 2008 [Page 3] Internet-Draft MANET-ID January 2008 If the packet's MANET_ID value matches MY_MANET_ID, then the packet is processed normally. Otherwise, the packet is discarded and ignored. When a packet is received containing a MANET_ID TLV, the MANET_ID value is attributed to all messages contained within the packet. 4.3. Message Processing When a message is received without a MANET_ID TLV and its containing packet does not contain a MANET_ID TLV value, the message's MANET_ID value is assumed to be zero (0). When a message is received containing a MANET_ID TLV, its MANET_ID value is contained. If the message's MANET_ID value matches MY_MANET_ID, then the message is processed normally. Otherwise, the message is discarded and ignored. 4.4. Sending Packets/Messages When issuing DYMO routing protocol packets/messages, the information should be identified by tagging it with a MANET_ID TLV containing this DYMO router's MY_MANET_ID value. 5. IANA Considerations TLV Assignments +----------+----------+---------------------+ | Mnemonic | TLV Type | Assigned Type Value | +----------+----------+---------------------+ | MANET_ID | Packet | TBD1 | | MANET_ID | Message | TBD2 | +----------+----------+---------------------+ Table 1 6. Security Considerations There are no security considerations associated with this document. Chakeres Expires July 17, 2008 [Page 4] Internet-Draft MANET-ID January 2008 7. Acknowledgements Portions of this document were based upon [I-D.ietf-manet-timetlv]. 8. References 8.1. Normative References [I-D.ietf-manet-packetbb] Clausen, T., "Generalized MANET Packet/Message Format", draft-ietf-manet-packetbb-10 (work in progress), October 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 time in MANETs", draft-ietf-manet-timetlv-02 (work in progress), August 2007. 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 July 17, 2008 [Page 5] Internet-Draft MANET-ID January 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 July 17, 2008 [Page 6]