As per Relevance of the word collaboration, we have this rfc below:
Network Working Group K.
Request for Comments: 3113 3GPP PCG
Category: Informational R.
S.
Harvard
J.
AT&
June 2001
3GPP-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
3GPP and IETF
1. Conventions used in this
This document uses significant terminology that is specialized
IETF, 3GPP, 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 3GPP
IETF, with the objective of securing timely development of
specification that facilitate maximum interoperability with
(fixed and mobile) Internet systems, devices, and protocols
Each organization will operate according to their own rules
procedures including rules governing IPR policy,
elaboration, approval and maintenance
Rosenbrock, et al. Informational [Page 1]
RFC 3113 3GPP-IETF Standardization Collaboration June 2001
3. Reasons For
3.1 3GPP use of IETF Internet
In the further development of 3GPP specifications, the benefit
adopting Internet specifications has been identified
The preferred 3GPP approach is to use the Internet
unchanged, if feasible. In any case, 3GPP has no intention
duplicate work performed in IETF
However, while this document recognizes the importance of 3
interoperability with the existing Internet and hence the use of
standards, 3GPP recognizes that additions or modifications might
needed in order to make the IETF internet specification fulfill
needs of 3GPP. In such cases, 3GPP 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 3GPP Wireless
The technical work in 3GPP is organized in Technical
Groups TSGs each with their area of responsibilities. TSG-RAN
TSG-GERAN are responsible for the Radio Access networks based
UTRAN and GERAN and thus the experts in the areas of
characteristics of the physical transport. TSG CN is responsible
the Mobility Management and other core network protocol
functionalities. TSG-T is responsible for Terminal aspects
applications. TSG-SA is responsible for the service and
aspects including the overall architecture, security and O&M aspects
Contacts for the TSGs can be found on the 3GPP web-
http://www.3gpp.org/.
4. Document
Both 3GPP and IETF encourage the sharing of draft documents that
of mutual interest
3GPP documents are available on its official web-
(http://www.3gpp.org/) and is open to anyone. IETF documents
including preliminary working documents ("Internet Drafts")
available on its web-site (http://www.ietf.org/) and various
sites
IETF representatives can obtain information about the 3GPP
and web-site structures by contacting the relevant 3GPP
points indicated at the 3GPP web-site http://www.3gpp.org/.
Rosenbrock, et al. Informational [Page 2]
RFC 3113 3GPP-IETF Standardization Collaboration June 2001
3GPP representatives can obtain information about the IETF
and web-site structures by contacting the relevant IETF
points (the Area Directors indicated at the IETF web-
http://www.ietf.org/).
5.
Whenever possible, informal communication at working level
encouraged
The vast majority of the technical discussions and decision making
both IETF and 3GPP is done over mailing lists. Both 3GPP and
web sites contain information concerning the associated
lists
It is recommended that interested individuals subscribe to
participate in these lists
When deemed necessary, formal communication between 3GPP and IETF
also permitted. Relevant IETF Area Directors and 3GPP
leadership are encouraged and authorized to facilitate
communications when needed
6. Rapporteurs/
6.1 IETF coordination support in 3
An IETF rapporteur function is established in 3GPP TSG-SA
The individual(s) appointed to undertake the responsibility of
function should be the initial contact point in 3GPP for
pertaining to the 3GPP-IETF cooperation. Of course, the chairman
TSG-SA can always be contacted
The 3GPP-IETF rapporteur function, therefore, is expected to
with the concerned working groups and TSGs and support
interaction between 3GPP and IETF
6.2 3GPP 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, by the IAB, of a specific person to function as
"3GPP liaison" is proposed
Rosenbrock, et al. Informational [Page 3]
RFC 3113 3GPP-IETF Standardization Collaboration June 2001
The role of the 3GPP Liaison is to act as an initial contact point
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
3GPP meetings or participation in 3GPP 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
9.
In order to assist the information flow between the organizations
the IETF can on per case basis appoint a rapporteur to
and represent IETF at 3GPP technical meetings
IETF meetings are open to any interested individuals
3GPP partners (OPs, MRPs) or individual members can participate
any of the IETF meetings, in accordance with the existing
procedures
8. Security
This type of non-protocol document does not directly affect
security of the Internet
Rosenbrock, et al. Informational [Page 4]
RFC 3113 3GPP-IETF Standardization Collaboration June 2001
9. Authors'
Questions about this memo can be directed to
Karl Heinz
06921 Sophia
Phone: +33 492 94 4212
EMail: rosenbrock@etsi.
Raj
Director, Systems and
Ericsson Canada Inc
8400 Decarie
TMR,
H4P 2N
Phone: +1 514 345 7862
Email: Raj.Sanmugam@ericsson.
Scott
Harvard
Cambridge, MA 02138
Phone: +1 617 495 3864
EMail: sob@harvard.
John C.
AT&T
99 Bedford
Boston, MA 02111
Phone: +1 617 513 7285
EMail: Klensin+iab@jck.
Note: Changes to the contents of this memo requires the approval
3GPP PCG: EMail: 3GPPContact@etsi.
Rosenbrock, et al. Informational [Page 5]
RFC 3113 3GPP-IETF Standardization Collaboration June 2001
Appendix A:
Glossary Of Acronyms
3GPP Third Generation Partnership
BCP Best Current
IAB Internet Architecture
IESG Internet Engineering Steering
IETF Internet Engineering Task
IPR Intellectual Property
MRP Market Representation
OP Organizational
O&M Operation and
PCG Project coordination
RFC Request for
TSG Technical Specification
TSG-SA TSG Services and systems
TSG-CN TSG Core
TSG-RAN TSG Radio Access
TSG-GERAN TSG GSM Radio Access
TSG-T TSG
UTRAN Universal Terrestrial Radio Access
WWW World Wide
Rosenbrock, et al. Informational [Page 6]
RFC 3113 3GPP-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
Rosenbrock, 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
