Network Working Group I. Chakeres
Internet-Draft Boeing
Expires: January 24, 2007 July 23, 2006
Discussing MANET IANA Needs
draft-chakeres-manet-iana-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 24, 2007.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document enumerates several possible IANA assignments for MANET
protocols. It is meant to aid and stimulate discussion on this
topic.
Chakeres Expires January 24, 2007 [Page 1]
Internet-Draft MANET-IANA July 2006
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. UDP Port for MANET Routing Protocols . . . . . . . . . . . . . 3
3. Link-local Multicast Group for MANET Routers . . . . . . . . . 3
4. Scoped Multicast Groups for MANET Routers . . . . . . . . . . . 4
4.1. Scoped Multicast Groups for IPv4 . . . . . . . . . . . . . 4
4.2. Scoped Multicast Groups for IPv6 . . . . . . . . . . . . . 5
5. Multicast Groups for MANET Nodes . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8
Intellectual Property and Copyright Statements . . . . . . . . . . 9
Chakeres Expires January 24, 2007 [Page 2]
Internet-Draft MANET-IANA July 2006
1. Introduction
This document enumerates a port and several scoped multicast address
assignments for MANET protocols. It is meant to aid and stimulate
discussion on this topic.
2. UDP Port for MANET Routing 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 January 24, 2007 [Page 3]
Internet-Draft MANET-IANA July 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. Scoped Multicast Groups for MANET Routers
MANET protocols may need several scoped multicast addresses [RFC4291]
to disseminate information more widely. This section names the
multicast addresses, defines their scope, and clarifies router
behavior.
The name of the multicast address to reach the MANET routers is
"Scoped MANET Routers". MANET routers subscribe to these scoped
multicast addresses.
MANET routers must handle forwarding of these scoped multicast
addresses using the additional criteria as specified in [RFC2365] and
[RFC4007].
4.1. Scoped Multicast Groups for IPv4
For IPv4, statically assigned, scope-relative multicast addresses (as
defined by [RFC2365], Section 9) are used. The offset for the scope
relative address for Scoped MANET Routers is TBD4 to appear in
[IANAv4Multicast] registry.
Different scopes are defined by [RFC2365]. The IPv4 Local Scope
(239.255.0.0/16) is the minimal enclosing scope for administratively
scoped multicast and not further divisible -- its exact extent is
site dependent.
For the IPv4 Local Scope, applying the rules of [RFC2365] and using
the assigned offset of TDB4, the multicast address is therefore
239.255.255.(255-TBD4).
For the IPv4 Organization Local Scope, applying the rules of
[RFC2365] and using the assigned offset of TDB5, the multicast
address is therefore 239.192.255.(255-TBD5).
Chakeres Expires January 24, 2007 [Page 4]
Internet-Draft MANET-IANA July 2006
4.2. Scoped Multicast Groups for IPv6
IPv6 has different address ranges for different multicast scopes that
are implemented as a set of address prefixes for the different
address ranges ([RFC2373]). A permanently assigned multicast address
will be used for Scoped MANET Routers multicast communication, i.e.,
an address that is independent of the scope value and that can be
used for all scopes. These addresses begin with FF0X:0:0:0:0:0:0:
where X indicates the scope. Implementations for IPv6 MUST use the
scope-independent address and the appropriate prefix for the selected
scope. For example, for link-local MANET communication the IPv6
link-local scope prefix (FF02) MUST be used. See [RFC4291] and the
[IANAv6Multicast] registry for IPv6 multicast assignments.
The permanent IPv6 multicast address for All MANET Routers/IPv6 is
FF0X:0:0:0:0:0:0:TBD6.
5. Multicast Groups for MANET Nodes
The term nodes refers to all devices that implement IP [RFC2460].
There may exist a need to address messages (using several different
scopes) to nodes within a MANET. We name this address Scoped MANET
Nodes. All nodes within a MANET should subscribe to these scoped
addresses.
MANET routers must handle forwarding of these scoped multicast
addresses using the additional criteria as specified in [RFC2365] and
[RFC4007].
6. IANA Considerations
A summary of the decided IANA assignments will appear here.
7. Security Considerations
Using multicast groups with scopes larger than link-local (LL) may
increase the ability of devices to abuse the network by creating
excessive messaging. Certain precautions should be followed, TBD.
8. Acknowledgements
Sections of this text were adapted from [RFC3259].
Fred Templin provided valuable input to this document.
Chakeres Expires January 24, 2007 [Page 5]
Internet-Draft MANET-IANA July 2006
9. References
9.1. Normative References
[I-D.ietf-manet-packetbb]
Clausen, T., Dearlove, C., Dean, J., and C. Adjih,
"Generalized MANET Packet/Message Format",
draft-ietf-manet-packetbb-01 (work in progress),
June 2006.
[RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23,
RFC 2365, July 1998.
[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and
B. Zill, "IPv6 Scoped Address Architecture", RFC 4007,
March 2005.
9.2. Informative References
[I-D.ietf-manet-dymo]
Perkins, C. and I. Chakeres, "Dynamic MANET On-demand
(DYMO) Routing", draft-ietf-manet-dymo-04 (work in
progress), March 2006.
[I-D.ietf-manet-nhdp]
Clausen, T., Dearlove, C., and J. Dean, "MANET
Neighborhood Discovery Protocol", draft-ietf-manet-nhdp-00
(work in progress), June 2006.
[I-D.ietf-manet-olsrv2]
Clausen, T., "The Optimized Link-State Routing Protocol
version 2", draft-ietf-manet-olsrv2-01 (work in progress),
March 2006.
[I-D.ietf-manet-smf]
Macker, J., "Simplified Multicast Forwarding for MANET",
draft-ietf-manet-smf-02 (work in progress), March 2006.
[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>.
[RFC1466] Gerich, E., "Guidelines for Management of IP Address
Space", RFC 1466, May 1993.
Chakeres Expires January 24, 2007 [Page 6]
Internet-Draft MANET-IANA July 2006
[RFC1884] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 1884, December 1995.
[RFC2050] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., and
J. Postel, "INTERNET REGISTRY IP ALLOCATION GUIDELINES",
BCP 12, RFC 2050, November 1996.
[RFC2373] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 2373, July 1998.
[RFC2375] Hinden, R. and S. Deering, "IPv6 Multicast Address
Assignments", RFC 2375, July 1998.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.
[RFC2908] Thaler, D., Handley, M., and D. Estrin, "The Internet
Multicast Address Allocation Architecture", RFC 2908,
September 2000.
[RFC3171] Albanna, Z., Almeroth, K., Meyer, D., and M. Schipper,
"IANA Guidelines for IPv4 Multicast Address Assignments",
BCP 51, RFC 3171, August 2001.
[RFC3259] Ott, J., Perkins, C., and D. Kutscher, "A Message Bus for
Local Coordination", RFC 3259, April 2002.
[RFC3330] IANA, "Special-Use IPv4 Addresses", RFC 3330,
September 2002.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
Chakeres Expires January 24, 2007 [Page 7]
Internet-Draft MANET-IANA July 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 January 24, 2007 [Page 8]
Internet-Draft MANET-IANA July 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 January 24, 2007 [Page 9]