As per Relevance of the word collaboration, we have this rfc below:
Network Working Group S.
Request for Comments: 3131 Harvard
Category: Informational P.
Sun Microsystems, Inc
H.
S.
G.
Verizon
M.
Sprint
M.
Lucent
June 2001
3GPP2-IETF Standardization
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 (2001). All Rights Reserved
This document describes the standardization collaboration
3GPP2 and IETF
1. Conventions used in this
This document uses significant terminology that is specialized
IETF, 3GPP2, or their areas of work. See appendix A for
of acronyms. The organizational definitions can be found in
respective web-sites
2.
This document contains a set of principles and guidelines that
as the basis for establishing the collaboration between 3GPP2
IETF, with the objective of securing timely development of
specification that facilitate maximum interoperability with
(fixed and mobile) Internet systems, devices, and protocols
Bradner, et al. Informational [Page 1]
RFC 3131 3GPP2-IETF Standardization Collaboration June 2001
Each organization will operate according to their own rules
procedures including rules governing IPR policy,
elaboration, approval and maintenance
3. Reasons For
3.1 3GPP2 use of IETF Internet
In the further development of 3GPP2 specifications, the benefit
adopting Internet specifications has been identified
The preferred 3GPP2 approach is to use the Internet
unchanged, if feasible. In any case, 3GPP2 has no intention
duplicate work performed in IETF
However, while this document recognizes the importance of 3GPP
interoperability with the existing Internet and hence the use of
standards, 3GPP2 recognizes that additions or modifications might
needed in order to make the IETF internet specification fulfill
needs of 3GPP2. In such cases, 3GPP2 will take its concerns
to the appropriate IETF working groups for resolution, or to
appropriate Area Director if no appropriate working group can
found
3.2 IETF access to 3GPP2 Wireless
The technical work in 3GPP2 is organized in Technical
Groups TSGs each with their area of responsibilities. TSG-A
TSG-C are responsible for the Radio Access networks based on CDMA
thus the experts in the areas of the characteristics of the
transport. TSG-N is responsible for the Mobility Management
other core network protocol and functionalities. TSG-P
responsible for data services and applications. TSG-S is
for the service and system aspects including the
architecture, security and O&M aspects. Contacts for the TSGs can
found on the 3GPP2 web-site www.3gpp2.org
4. Document
Both 3GPP2 and IETF encourage the sharing of draft documents that
of mutual interest
3GPP2 working documents are available on its official web-site,
are grouped according to the meeting. These documents can be
on the 3GPP2 ftp server, which is open to anyone,
ftp://ftp.3gpp2.org. 3GPP2 specifications, those that have
the 15-day Steering Committee review, can be found at
Bradner, et al. Informational [Page 2]
RFC 3131 3GPP2-IETF Standardization Collaboration June 2001
http://www.3gpp2.org/Public_html/Specs/index.
IETF documents, including preliminary working documents ("
Drafts") are available on its web-site (http://www.ietf.org/)
various shadow sites
IETF representatives can obtain information about the 3GPP2
and web-site structures by contacting the relevant 3GPP2
points indicated at the 3GPP2 web-site (www.3gpp2.org).
3GPP2 representatives can obtain information about the IETF
and web-site structures by contacting the relevant IETF
points, which are the Area Directors indicated at the IETF web-
(www.ietf.org).
5.
Whenever possible, informal communication at working level
encouraged
The vast majority of the technical discussions and decision making
IETF is done over mailing lists. It is recommended that
individuals subscribe to and participate in these lists
3GPP2 mailing lists, however, are not open to the general public.
is recommended that work of mutual interest be discussed on
relevant IETF mailing lists
When deemed necessary, formal communication between 3GPP2 and IETF
also permitted. Relevant IETF Area Directors and 3GPP2
leadership are encouraged and authorized to facilitate
communications when needed
6. Rapporteurs/
6.1 IETF coordination support in 3GPP
An IETF rapporteur function is established in 3GPP2
Committee
The individual(s) appointed to undertake the responsibility of
function should be the initial contact point in 3GPP2 for
pertaining to the 3GPP2-IETF cooperation. Of course, the chairman
Steering Committee can always be contacted
The 3GPP2-IETF rapporteur function, therefore, is expected to
with the concerned working groups and TSGs and support
interaction between 3GPP2 and IETF
Bradner, et al. Informational [Page 3]
RFC 3131 3GPP2-IETF Standardization Collaboration June 2001
6.2 3GPP2 Liaison in
The preferred way for organizations to work with IETF is through
working groups. However, IETF has a limited number of
relationships with other organizations when conditions warrant
appointment of a specific person
The appointment of a specific person in IESG to function as a "3GPP
liaison" is proposed
The role of the 3GPP2 Liaison is to act as an initial contact
in IETF for administrative aspects of this collaboration that
easily be handled in other ways (e.g., at a technical level
interactions with IETF Working Groups or Area Directors). It
agreed that the role does not carry the expectation of attendance
3GPP2 meetings or participation in 3GPP2 administrative processes
anticipated that all liaison efforts assigned to this individual
be carried out by electronic mail. It is understood that the
will not have the ability to make exceptions to, or
provisions for, IETF policies and procedures
7.
In order to assist the information flow between the organizations
IETF can on a per case basis appoint an observer to participate
represent IETF at 3GPP2 technical meetings
IETF meetings are open to any interested individuals
3GPP2 partners (OPs, MRPs) or individual members can participate
any of the IETF meetings, in accordance with the existing
procedures
3GPP2 meetings are also open to any interested individual,
such individuals do not have voting privileges. The meeting
can be found on the 3GPP2 web site
8. Security
This type of non-protocol document does not directly affect
security of the Internet
9.
This memo took guidance from and borrowed text from RFC 3113.[4]
Bradner, et al. Informational [Page 4]
RFC 3131 3GPP2-IETF Standardization Collaboration June 2001
10.
[1] Bradner, S., "The Internet Standards Process -- Revision 3",
9, RFC 2026, October 1996.
[2] Postel, J. and J. Reynolds, "Instructions to RFC Authors",
2223, October 1997.
[3] Bradner, S., "IETF Working Group Guidelines and Procedures",
25, RFC 2418, September 1998.
[4] Rosenbrock, K., Sanmugam, R., Bradner, S. and J. Klensin, "3GPP
IETF Standardization Collaboration", RFC 3113, June 2001.
10. Authors'
Scott O.
Harvard
Holyoke Center, Room 813
1350 Mass. Ave
Cambridge, MA 02138
Phone: +1 617-495-3864
EMail: sob@harvard.
Pat R.
Network and Security Research Center, Sun
Sun Microsystems, Inc
15 Network
Menlo Park, California, 94025
Phone: +1 650-786-7733
Fax: +1 650-786-6445
EMail: pcalhoun@eng.sun.
Henry
2500 Wilson
Arlington, VA 22201
Phone: +1 703-907-7497
Fax: +1 703-907-7728
EMail: hcuschie@tia.eia.
Bradner, et al. Informational [Page 5]
RFC 3131 3GPP2-IETF Standardization Collaboration June 2001
Steve
Motorola/3GPP2
1900 W. Winchester
Libertyville, IL 60048
Phone: +1 847-523-6868
Fax: +1 847-523-0375
EMail: S.Dennett@motorola.
Gerry
Verizon
180 Washington Valley
Bedminster, NJ 07921
Phone: +1 908-306-4154
Fax: +1 908-306-7731
EMail: gerry.flynn@verizonwireless.
Mark
Sprint
15405 College
Lenexa, KS 66219
Phone: +1 913-890-4248
Fax +1 913-890-4291
Email: Mlipfo01@sprintspectrum.
Mike
Lucent
263 Shuman
Naperville, IL 60566
Phone: +1 630-713-4182
Fax: +1 630-713-4182
EMail: mjmcpheters@lucent.
Bradner, et al. Informational [Page 6]
RFC 3131 3GPP2-IETF Standardization Collaboration June 2001
Appendix A:
Glossary Of Acronyms
3GPP2 Third Generation Partnership Project 2
BCP Best Current
CDMA Code Division Multiple
IAB Internet Architecture
IESG Internet Engineering Steering
IETF Internet Engineering Task
IPR Intellectual Property
OP Organizational
O&M Operation and
RFC Request for
SC 3GPP2 Steering
TSG Technical Specification
TSG-A TSG A-Interface
TSG-C TSG CDMA2000 Air
TSG-P TSG Wireless Packet Data
TSG-N TSG ANSI-41/
TSG-S TSG Service And System
WWW World Wide
Bradner, et al. Informational [Page 7]
RFC 3131 3GPP2-IETF Standardization Collaboration June 2001
Full Copyright
Copyright (C) The Internet Society (2001). 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
Bradner, et al. Informational [Page 8]
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
