[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-chakeres-manet-iana) 00 01 02 03 04 05 06 07 RFC 5498

Mobile Ad hoc Networks                                       I. Chakeres
Internet-Draft                                                  Motorola
Intended status: Informational                              May 10, 2007
Expires: November 11, 2007


                            MANET IANA Needs
                      draft-ietf-manet-iana-02.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 November 11, 2007.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This document enumerates IANA assignments for use by MANET WG
   protocols.  Specifically, a UDP port, two link-local multicast group
   addresses (IPv4 & IPv6), and two site-local multicast group addresses
   (IPv4 & IPv6).







Chakeres                Expires November 11, 2007               [Page 1]

Internet-Draft                 MANET-IANA                       May 2007


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  UDP Port for MANET Protocols  . . . . . . . . . . . . . . . . . 3
   3.  Link-local Multicast Group for MANET Routers  . . . . . . . . . 3
   4.  Site-local Scoped Multicast Groups for MANET Routers  . . . . . 3
     4.1.  Site-local Scoped Multicast Group for IPv4  . . . . . . . . 4
     4.2.  Site-local Scoped Multicast Group for IPv6  . . . . . . . . 4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   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 November 11, 2007               [Page 2]

Internet-Draft                 MANET-IANA                       May 2007


1.  Introduction

   This document enumerates assignments 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.  Well-known site-local multicast
   addresses (IPv4 & IPv6) for site-local multihop communication between
   MANET routers within the same site.


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 SHOULD subscribe to 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.  Site-local Scoped Multicast Groups for MANET Routers

   MANET protocols need a well-known site-local scoped multicast address
   [RFC4291] to disseminate information over multiple hops.  This
   section names the multicast address, defines the scope, and clarifies
   router behavior.

   The name of the multicast address to reach the MANET routers is
   "MANET Routers".  MANET routers SHOULD subscribe to this well-known
   site-local scoped multicast address to receive routing protocol
   packets and use it for multihop site-local transmissions of routing



Chakeres                Expires November 11, 2007               [Page 3]

Internet-Draft                 MANET-IANA                       May 2007


   protocol packets.

   MANET routers that forward site-local scoped multicast traffic must
   use additional criteria as specified in [RFC2365] and [RFC4007].

4.1.  Site-local Scoped Multicast Group for IPv4

   For IPv4, well-known, scope-relative multicast address (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).

4.2.  Site-local Scoped Multicast Group 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 ([RFC4291]).  A well-known assigned multicast address
   is used for site-local scoped MANET Routers multicast communication.
   See [RFC4291] and the [IANAv6Multicast] registry for IPv6 multicast
   assignments.

   The well-known IPv6 multicast address for MANET Routers/IPv6 is
   FF05:0:0:0:0:0:0:TBD3.


5.  IANA Considerations

                            UDP Port Assignment

                             +-------+-------+
                             |  Name | Value |
                             +-------+-------+
                             | manet |  TBD1 |
                             +-------+-------+

                                  Table 1






Chakeres                Expires November 11, 2007               [Page 4]

Internet-Draft                 MANET-IANA                       May 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

                  Site-local multicast address assignment

    +---------------+------------------------+-----------------------+
    |      Name     |          IPv4          |          IPv6         |
    +---------------+------------------------+-----------------------+
    | MANET Routers | 239.255.255.(255-TBD4) | FF05:0:0:0:0:0:0:TBD3 |
    +---------------+------------------------+-----------------------+

                                  Table 3


6.  Security Considerations

   There are no security considerations associated with this document.


7.  Acknowledgements

   Fred Templin, Bill Fenner, and Alexandru Petrescu provided valuable
   input to this document.


8.  References

8.1.  Normative References

   [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.

   [RFC4291]  Hinden, R. and S. Deering, "IP Version 6 Addressing
              Architecture", RFC 4291, February 2006.






Chakeres                Expires November 11, 2007               [Page 5]

Internet-Draft                 MANET-IANA                       May 2007


8.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>.


Author's Address

   Ian D Chakeres
   Motorola
   Bangalore
   India

   Email: ian.chakeres@gmail.com
































Chakeres                Expires November 11, 2007               [Page 6]

Internet-Draft                 MANET-IANA                       May 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 November 11, 2007               [Page 7]


Html markup produced by rfcmarkup 1.108, available from http://tools.ietf.org/tools/rfcmarkup/