One document matched: draft-ietf-manet-iana-06.txt
Differences from draft-ietf-manet-iana-05.txt
Mobile Ad hoc Networks I. Chakeres
Internet-Draft Motorola
Intended status: Standards Track October 26, 2007
Expires: April 28, 2008
IANA Allocations for Mobile Ad hoc Network (MANET) Protocols
draft-ietf-manet-iana-06.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 April 28, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
This document enumerates several common IANA allocations for use by
MANET protocols. The following well-known numbers are required: a
UDP port number, an IP protocol number, and a link-local multicast
group address.
Chakeres Expires April 28, 2008 [Page 1]
Internet-Draft MANET-IANA October 2007
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. UDP Port Number for MANET Protocols . . . . . . . . . . . . . . 3
3. IP Protocol Number for MANET Protocols . . . . . . . . . . . . 3
4. Link-local Multicast Group for MANET Routers . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . . . 7
Chakeres Expires April 28, 2008 [Page 2]
Internet-Draft MANET-IANA October 2007
1. Introduction
This document enumerates several common IANA allocations for use by
one or more protocols that conform to [I-D.ietf-manet-packetbb],
MANET protocols. The following well-known numbers are required: a
UDP port number, an IP protocol number, and a link-local multicast
group address. All interoperable protocols running on these well-
known IANA allocations MUST confirm to [I-D.ietf-manet-packetbb].
[I-D.ietf-manet-packetbb] provides a common format that enables one
or more MANET protocols to share the IANA allocations defined in this
document unambiguously.
2. UDP Port Number for MANET Protocols
MANET routers require a well-known UDP port number [IANAPort] to send
and receive MANET routing protocol packets. The title of this UDP
port is "manet". The value of this UDP port is TBD1.
3. IP Protocol Number for MANET Protocols
MANET routers require a well-known IP protocol number [IANAProtocol]
to send and receive MANET routing protocol packets. The title of
this IP protocol number is "manet". The value of this IP protocol
number is TBD2.
4. Link-local Multicast Group for MANET Routers
MANET routers 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".
For IPv4, a well-known, link-local scope multicast address is
required. The address for LL-MANET-Routers is 224.0.0.TBD3 to appear
in the [IANAv4Multicast] registry.
For IPv6, a well-known, link-local scope multicast address is
required. The address for LL-MANET-Routers is FF02:0:0:0:0:0:0:TBD4
to appear in the [IANAv6Multicast] registry.
5. IANA Considerations
This document enumerates several common IANA allocations for use by
one or more MANET protocols that conform to
Chakeres Expires April 28, 2008 [Page 3]
Internet-Draft MANET-IANA October 2007
[I-D.ietf-manet-packetbb]. Specifically, the following well-known
numbers have been assigned: a UDP port (Section 2), an IP protocol
number (Section 3), and a link-local multicast group address
(Section 4).
Action 1:
Upon approval of this document, the IANA will make the following
assignments in the "PORT NUMBERS" registry located at
http://www.iana.org/assignments/port-numbers
sub-registry "WELL KNOWN PORT NUMBERS"
Keyword Decimal Description References
------- ------- ----------- ----------
manet [TBD1]/udp MANET Protocols [I-D.ietf-manet-iana]
Action 2:
Upon approval of this document, the IANA will make the following
assignments in the "PROTOCOL NUMBERS" registry located at
http://www.iana.org/assignments/protocol-numbers
sub-registry "WELL KNOWN PORT NUMBERS"
Keyword Decimal Description References
------- ------- ----------- ----------
manet TBD2 MANET Protocols [I-D.ietf-manet-iana]
Action 3:
Upon approval of this document, the IANA will make the following
assignments in the "Internet Multicast Addresses" registry located at
http://www.iana.org/assignments/multicast-addresses
sub-registry "224.0.0.0 - 224.0.0.255 (224.0.0/24)
Local Network Control Block Date registered"
224.0.0.TBD3 LL-MANET-Routers [I-D.ietf-manet-iana]
Action 4:
Chakeres Expires April 28, 2008 [Page 4]
Internet-Draft MANET-IANA October 2007
Upon approval of this document, the IANA will make the following
assignments in the "INTERNET PROTOCOL VERSION 6 MULTICAST ADDRESSES"
registry located at
http://www.iana.org/assignments/ipv6-multicast-addresses
sub-registry "Fixed Scope Multicast Addresses"
sub-sub-registry "Link-Local Scope"
FF02:0:0:0:0:0:0:TBD4 LL-MANET-Routers [I-D.ietf-manet-iana]
6. Security Considerations
The security issues associated with using the same UDP port/multicast
address/IP protocol number for multiple protocols are addressed in
[I-D.ietf-manet-packetbb]. The security considerations for each
protocol using these IANA allocations are addressed in each
protocol's specification.
7. Acknowledgements
Fred Templin, Bill Fenner, Alexandru Petrescu, and Sam Weiler
provided valuable input to this document.
8. References
8.1. Normative References
[I-D.ietf-manet-iana]
Chakeres, I., "Internet Assigned Numbers Authority (IANA)
Allocations for the Mobile Ad hoc Networks (MANET)
Working Group", draft-ietf-manet-iana-05 (work in
progress), June 2007.
[I-D.ietf-manet-packetbb]
Clausen, T., "Generalized MANET Packet/Message Format",
draft-ietf-manet-packetbb-08 (work in progress),
July 2007.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
Chakeres Expires April 28, 2008 [Page 5]
Internet-Draft MANET-IANA October 2007
8.2. Informative References
[IANAPort]
"IANA Port Numbers",
<http://www.iana.org/assignments/port-numbers>.
[IANAProtocol]
"IANA Protocol Numbers",
<http://www.iana.org/assignments/protocol-numbers>.
[IANAv4Multicast]
"IPv4 Multicast Address Assignments",
<http://www.iana.org/assignments/multicast-addresses>.
[IANAv6Multicast]
"IPv6 Multicast Address Assignments",
<http://www.iana.org/assignments/
ipv6-multicast-addresses>.
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 April 28, 2008 [Page 6]
Internet-Draft MANET-IANA October 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 April 28, 2008 [Page 7]
| PAFTECH AB 2003-2026 | 2026-04-23 21:08:03 |