Network Working Group I. Chakeres
Internet-Draft Boeing
Expires: March 22, 2007 September 18, 2006
MANET IANA Needs
draft-chakeres-manet-iana-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 March 22, 2007.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document enumerates IANA assignments for immediate use in MANET
routing protocols.
Chakeres Expires March 22, 2007 [Page 1]
Internet-Draft MANET-IANA September 2006
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. UDP Port for MANET Protocols . . . . . . . . . . . . . . . . . 3
3. Link-local Multicast Group for MANET Routers . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5
Intellectual Property and Copyright Statements . . . . . . . . . . 6
Chakeres Expires March 22, 2007 [Page 2]
Internet-Draft MANET-IANA September 2006
1. Introduction
This document enumerates a port and two link-local multicast address
assignments (one IPv4 and one IPv6) for MANET protocols.
2. UDP Port for MANET Protocols
To aggregate MANET routing protocol traffic it must be sent to the
same IP destination address and the same port. Therefore, all
interoperable MANET routing protocol traffic should be sent to the
same UDP port. The proposed title for this port is "MANET". In
order to be interoperable, all packets sent to this port MUST conform
to the packetbb specification [I-D.ietf-manet-packetbb].
UDP Port Assignment
+-------+-------+
| Name | Value |
+-------+-------+
| MANET | TBD1 |
+-------+-------+
Table 1
3. Link-local Multicast Group for MANET Routers
MANET protocols need a link-local multicast address [RFC4291] to
disseminate information. This section proposes and names this link-
local multicast address.
The name of the multicast address to reach all link-local (LL) MANET
routers is "LL MANET Routers". MANET routers subscribe to this
scoped multicast address and use it for link-local transmissions of
routing protocol packets.
For IPv4, a statically assigned, link-local scope multicast address
is used. The address for LL MANET Routers is 224.0.0.TBD2 to appear
in the [IANAv4Multicast] registry.
For IPv6, a statically assigned, link-local scope multicast address
is used. The address for LL MANET Routers is FF02:0:0:0:0:0:0:TBD3
to appear in the [IANAv6Multicast] registry.
Chakeres Expires March 22, 2007 [Page 3]
Internet-Draft MANET-IANA September 2006
Link-local multicast address assignment
+------------------+--------------+-----------------------+
| Name | IPv4 | IPv6 |
+------------------+--------------+-----------------------+
| LL MANET Routers | 224.0.0.TBD2 | FF02:0:0:0:0:0:0:TBD3 |
+------------------+--------------+-----------------------+
Table 2
4. IANA Considerations
A summary of the decided IANA assignments will appear here.
5. Security Considerations
There are no security considerations associated with this document.
6. Acknowledgements
Fred Templin provided valuable input to this document.
7. References
7.1. Normative References
[I-D.ietf-manet-packetbb]
Clausen, T., "Generalized MANET Packet/Message Format",
draft-ietf-manet-packetbb-01 (work in progress),
June 2006.
7.2. Informative References
[IANAv4Multicast]
"IPv4 Multicast Address Assignments", <http://http://
www.iana.org/assignments/multicast-addresses>.
[IANAv6Multicast]
"IPv6 Multicast Address Assignments", <http://http://
www.iana.org/assignments/ipv6-multicast-addresses>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
Chakeres Expires March 22, 2007 [Page 4]
Internet-Draft MANET-IANA September 2006
Author's Address
Ian D Chakeres
Boeing
P.O. Box 3707 MC 7L-49
Seattle, WA 98124
USA
Email: ian.chakeres@gmail.com
Chakeres Expires March 22, 2007 [Page 5]
Internet-Draft MANET-IANA September 2006
Intellectual Property Statement
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.
Disclaimer of Validity
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 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.
Copyright Statement
Copyright (C) The Internet Society (2006). 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.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Chakeres Expires March 22, 2007 [Page 6]