As per Relevance of the word assignment, we have this rfc below:
Network Working Group B.
Request for Comments: 2860
Category: Informational F.
M.
June 2000
Memorandum of Understanding Concerning the
Work of the Internet Assigned Numbers
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document places on record the text of the Memorandum
Understanding concerning the technical work of the IANA that
signed on March 1, 2000 between the IETF and ICANN, and ratified
the ICANN Board on March 10, 2000.
MoU text as
MEMORANDUM OF UNDERSTANDING CONCERNING THE TECHNICAL WORK OF
INTERNET ASSIGNED NUMBERS
1. This Memorandum of Understanding ("MOU") defines an
between the Internet Engineering Task Force and the
Corporation for Assigned Names and Numbers. Its intent is
to define the technical work to be carried out by the
Assigned Numbers Authority on behalf of the Internet Engineering
Force and the Internet Research Task Force. It is recognized
ICANN may, through the IANA, provide similar services to
organisations with respect to protocols not within IETF's scope (i.e
registries not created by IETF or IRTF action); nothing in this
limits ICANN's ability to do so
Carpenter, et al. Informational [Page 1]
RFC 2860 MoU Between IETF and ICANN concerning IANA June 2000
2. This MOU will remain in effect until either modified or
by mutual consent of the Internet Engineering Task Force and
Internet Corporation for Assigned Names and Numbers, or cancelled
either party with at least six (6) months notice
3. Definition of terms and abbreviations used in this document
ICANN - Internet Corporation for Assigned Names and Numbers,
California non-profit corporation
IANA - Internet Assigned Numbers Authority (a traditional name,
here to refer to the technical team making and publishing
assignments of Internet protocol technical parameters). The
technical team is now part of ICANN
IETF - the Internet Engineering Task Force, the
association operating under such name that creates Internet
and related documents
IAB - the Internet Architecture Board, an oversight committee of
IETF. The IAB is chartered to designate the IANA on behalf of
IETF
IESG - the Internet Engineering Steering Group, a
committee of the IETF
IRTF - the Internet Research Task Force, an
association also overseen by the IAB
IRSG - the Internet Research Steering group, a management
of the IRTF
RFC - "Request For Comments", the archival document series of
IETF, also used by the IRTF and by third parties
ISOC - the Internet Society, a not-for-profit corporation
supports the IETF
4. Agreed technical work items. ICANN agrees that during the term
this MOU it shall cause IANA to comply, for protocols within IETF'
scope, with the following requirements, which ICANN and
acknowledge reflect the existing arrangements under which the IANA
operated
4.1. The IANA will assign and register Internet protocol
only as directed by the criteria and procedures specified in RFCs
including Proposed, Draft and full Internet Standards and
Current Practice documents, and any other RFC that calls for
Carpenter, et al. Informational [Page 2]
RFC 2860 MoU Between IETF and ICANN concerning IANA June 2000
assignment. If they are not so specified, or in case of ambiguity
IANA will continue to assign and register Internet
parameters that have traditionally been registered by IANA,
past and current practice for such assignments, unless
directed by the IESG
If in doubt or in case of a technical dispute, IANA will seek
follow technical guidance exclusively from the IESG.
appropriate the IESG will appoint an expert to advise IANA
The IANA will work with the IETF to develop any missing criteria
procedures over time, which the IANA will adopt when so instructed
the IESG
4.2. In the event of technical dispute between the IANA and the IESG
both will seek guidance from the IAB whose decision shall be final
4.3. Two particular assigned spaces present policy issues in
to the technical considerations specified by the IETF: the
of domain names, and the assignment of IP address blocks.
policy issues are outside the scope of this MOU
Note that (a) assignments of domain names for technical uses (such
domain names for inverse DNS lookup), (b) assignments of
address blocks (such as multicast or anycast blocks), and (c
experimental assignments are not considered to be policy issues,
shall remain subject to the provisions of this Section 4. (
purposes of this MOU, the term "assignments" includes allocations.)
In the event ICANN adopts a policy that prevents it from
with the provisions of this Section 4 with respect to the
described in (a) - (c) above, ICANN will notify the IETF, which
then exercise its ability to cancel this MOU under Section 2 above
4.4. The IANA shall make available to the public, on-line and free
charge, information about each current assignment, including
details for the assignee. Assignments published in RFCs by the
Editor and available publicly will be deemed to meet the
of this Section 4.4.
4.5. The IANA shall provide on-line facilities for the public
request Internet protocol parameter assignments and shall
execute such assignments, or deny them for non- conformance
applicable technical requirements, in a timely manner. There shall
no charge for assignments without the consent of the IAB.
shall only be denied on legitimate technical grounds
Carpenter, et al. Informational [Page 3]
RFC 2860 MoU Between IETF and ICANN concerning IANA June 2000
For protocols within the IETF scope (i.e., registries created by
action), appeals against such denials may be made to the IESG
subsequently to the IAB as provided in 4.2 above
4.6. The IANA shall have non-voting liaison seats on appropriate
committees as determined by the IETF, and may participate in all
discussions concerning technical requirements for protocol
assignment through such liaisons
4.7. The IANA shall review all documents in IETF Last Call
identify any issues of concern to the IANA, and shall raise
issues with the IESG
5. Application to IRTF/IRSG. The parties understand that certain
the protocol parameters to be assigned by IANA will be relevant
IRTF, rather than IETF. With respect to these protocol parameters
IANA will comply with the procedures set forth in Section 4, with
understanding that IRTF and IRSG shall be substituted for IETF
IESG, respectively, in such procedures. In the event of any
as to whether a particular protocol parameter relates principally
IETF or IRTF, the IAB shall have the authority to answer
question in its discretion
6. General. This MOU does not constitute any of the parties as
partner, joint venturer, agent, principal or franchisee of any
party. The waiver of any provision of this MOU on any occasion
not constitute a waiver for purposes of any other occasion. No
may transfer or assign any interest, right or obligation
under this MOU without the prior written consent of each other
to this MOU
7. Effectiveness of MOU. This Agreement requires the approval
ratification of the ICANN Board of Directors. The signatory
ICANN shall use his best efforts to secure and deliver to IETF
approval or ratification within two months of signing
Carpenter, et al. Informational [Page 4]
RFC 2860 MoU Between IETF and ICANN concerning IANA June 2000
IN WITNESS WHEREOF, this Memorandum of Understanding is executed
of this first day of March 2000 by the undersigned, acting
their duly authorized representatives
INTERNET ENGINEERING TASK
By: __________________________ Fred Baker, IETF
Approved by
INTERNET ARCHITECTURE
By: __________________________ Brian Carpenter, IAB
INTERNET CORPORATION FOR ASSIGNED NAMES AND
By:___________________________ Mike Roberts,
Security
This document does not directly impact the security of the Internet
Carpenter, et al. Informational [Page 5]
RFC 2860 MoU Between IETF and ICANN concerning IANA June 2000
The technical heart of this document was discussed in the
POISSON working group in 1998 and 1999 and reviewed by the IESG
IAB. Jorge Contreras, Joyce K. Reynolds, and Louis Touton assisted
its finalisation
Authors'
Brian E.
Suite 150
1890 Maple
Evanston IL 60201
EMail: brian@icair.
Fred
519 Lado
Santa Barbara, CA 93111
EMail: fred@cisco.
Michael M.
Internet Corporation for Assigned Names and Numbers (ICANN
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
EMail: roberts@icann.
Carpenter, et al. Informational [Page 6]
RFC 2860 MoU Between IETF and ICANN concerning IANA June 2000
Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Carpenter, et al. Informational [Page 7]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
