Mobile Ad hoc Networks I. Chakeres Internet-Draft Motorola Intended status: Standards Track July 4, 2007 Expires: January 5, 2008 MANET Region ID TLV draft-chakeres-manet-manetid-00.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 January 5, 2008. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document defines a packet, message, and address TLV, named MANET_ID. The MANET_ID TLV can be used to specify a administratively configured MANET region for which the related piece of information is intended. Chakeres Expires January 5, 2008 [Page 1] Internet-Draft MANET-ID July 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. MANET_ID TLV Structure . . . . . . . . . . . . . . . . . . . . 3 4. Protocol Recommendations . . . . . . . . . . . . . . . . . . . 3 4.1. MANET_ID Configuration . . . . . . . . . . . . . . . . . . 4 4.2. Transmitting Information . . . . . . . . . . . . . . . . . 4 4.3. Processing Untagged Information . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 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 January 5, 2008 [Page 2] Internet-Draft MANET-ID July 2007 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 to tag information as belonging to an administratively configured MANET region. The TLV can be attached to a packet, message, or address. 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, message, or address 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. Protocol Recommendations This document recommends specific protocol instance behavior based on the existence of the MANET_ID TLV. A protocol instance processing a packet, message, or address with MANET_ID TLVs should be administratively configured to participate in a network region identified by a particular MANET_ID value. Participation in multiple regions is allowed, but the behavior is not specified in this document. If a protocol instance does participate in multiple MANET_ID regions (or both tagged and untagged information), it SHOULD maintain the MANET_ID attached to any stored information. Upon evaluating a particular piece of information, a protocol instance SHOULD ignore information tagged with a MANET_ID TLV that contains a MANET_ID different from their own configured values. Chakeres Expires January 5, 2008 [Page 3] Internet-Draft MANET-ID July 2007 4.1. MANET_ID Configuration Protocol instance configuration of MANET_ID should be administratively configured. WARNING: Improper assignment of MANET_ID can result in improper processing and distribution of tagged information. 4.2. Transmitting Information The behavior of a protocol instance to transmit information as tagged or untagged SHOULD be administratively configured. Network designers should decide whether transmitting untagged information will result in improper behavior. 4.3. Processing Untagged Information The processing behavior of a protocol instance to untagged information SHOULD be administratively configured. Network designers should decide whether processing of untagged information can result in improper behavior. 5. IANA Considerations TLV Assignments +----------+----------+---------------------+ | Mnemonic | TLV Type | Assigned Type Value | +----------+----------+---------------------+ | MANET_ID | Packet | TBD1 | | MANET_ID | Message | TBD2 | | MANET_ID | Address | TBD3 | +----------+----------+---------------------+ Table 1 6. Security Considerations There are no security considerations associated with this document. 7. Acknowledgements Portions of this document were based upon [I-D.ietf-manet-timetlv]. 8. References Chakeres Expires January 5, 2008 [Page 4] Internet-Draft MANET-ID July 2007 8.1. Normative References [I-D.ietf-manet-packetbb] Clausen, T., "Generalized MANET Packet/Message Format", draft-ietf-manet-packetbb-06 (work in progress), June 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-00 (work in progress), April 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 January 5, 2008 [Page 5] Internet-Draft MANET-ID July 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). 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 January 5, 2008 [Page 6]