One document matched: draft-ietf-manet-iana-05.txt
Differences from draft-ietf-manet-iana-04.txt
Mobile Ad hoc Networks I. Chakeres
Internet-Draft Motorola
Intended status: Standards Track June 9, 2007
Expires: December 11, 2007
Internet Assigned Numbers Authority (IANA) Allocations for the Mobile
Ad hoc Networks (MANET) Working Group
draft-ietf-manet-iana-05.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 December 11, 2007.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
This document enumerates IANA allocations for use by MANET WG
protocols. Specifically, a UDP port and two link-local multicast
group addresses (IPv4 & IPv6).
Chakeres Expires December 11, 2007 [Page 1]
Internet-Draft MANET-IANA June 2007
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 . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4
Intellectual Property and Copyright Statements . . . . . . . . . . 6
Chakeres Expires December 11, 2007 [Page 2]
Internet-Draft MANET-IANA June 2007
1. Introduction
This document enumerates IANA allocations for MANET WG protocols. A
well-known UDP port for MANET WG protocols. Well-known link-local
multicast addresses (IPv4 & IPv6) for link-local communication
between neighboring MANET routers.
2. UDP Port for MANET Protocols
MANET routing protocols require a well-known UDP port to send and
receive MANET routing protocol packets. The title of this UDP port
is "manet". The value of this UPD port is TBD1.
3. Link-local Multicast Group for MANET Routers
MANET protocols require a well-known link-local multicast address
[RFC4291] to send and receive MANET routing protocol packets. The
name of the multicast address to reach link-local (LL) MANET routers
is "LL MANET Routers".
MANET routers will use this well-known LL scoped multicast address to
receive routing protocol packets and use it for LL transmissions of
routing protocol packets.
For IPv4, a well-known, 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 well-known, 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.
4. IANA Considerations
UDP Port Assignment
+-------+-------+
| Name | Value |
+-------+-------+
| manet | TBD1 |
+-------+-------+
Table 1
Chakeres Expires December 11, 2007 [Page 3]
Internet-Draft MANET-IANA June 2007
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
5. Security Considerations
There are no security considerations associated with this document.
6. Acknowledgements
Fred Templin, Bill Fenner, and Alexandru Petrescu provided valuable
input to this document.
7. References
7.1. Normative References
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
7.2. Informative References
[IANAv4Multicast]
"IPv4 Multicast Address Assignments", May 2007,
<http://www.iana.org/assignments/multicast-addresses>.
[IANAv6Multicast]
"IPv6 Multicast Address Assignments", May 2007,
<http://www.iana.org/assignments/
ipv6-multicast-addresses>.
Chakeres Expires December 11, 2007 [Page 4]
Internet-Draft MANET-IANA June 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
Chakeres Expires December 11, 2007 [Page 5]
Internet-Draft MANET-IANA June 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 December 11, 2007 [Page 6]
| PAFTECH AB 2003-2026 | 2026-04-22 23:10:18 |