RFC 3113

3GPP-IETF Standardization Collaboration

📅 published June 2001, from ietf

RFC 3113: 3GPP-IETF Standardization Collaboration 💖

okay bestie, this is RFC 3113 🎀 and the header is giving a whole team. it's an Informational doc from June 2001, written in the Network Working Group. the authors are K. Rosenbrock (3GPP PCG Chair), R. Sanmugam (Ericsson), S. Bradner (Harvard University), and J. Klensin (AT&T). there's no Obsoletes or Updates line in the header, so it isn't replacing or changing any other RFC 🦋

Status of this Memo 📜

this memo is here to give info to the Internet community 🌸 it does not specify an Internet standard of any kind. distribution of this memo is unlimited.

Copyright (C) The Internet Society (2001). All Rights Reserved.

Abstract ✨

this doc describes the standardization collab between 3GPP and IETF 🫶

1. Conventions used in this document 💅

this doc uses terminology that's specialized to IETF, 3GPP, or their areas of work. see Appendix A for acronym definitions. the organizational definitions live on their respective websites.

2. Introduction 🧚

okay so this doc is a set of principles and guidelines that act as the basis for setting up the 3GPP and IETF collab. the goal is securing timely development of technical specs that facilitate maximum interoperability with existing (fixed and mobile) Internet systems, devices, and protocols 🔥

each org keeps running by its own rules and procedures, including IPR policy, spec elaboration, approval, and maintenance. no mixing up the rulebooks 💀

3. Reasons For Collaboration 👑

3.1 3GPP use of IETF Internet Standards 🦋

the benefit of adopting Internet specs has been identified as 3GPP keeps developing its specs, and we're obsessed 😭

the preferred 3GPP approach is to use Internet standards unchanged, if feasible. in any case, 3GPP has no intention to duplicate work performed in IETF. slay 💅

BUT 👀 this doc recognizes how important it is for 3GPP to interoperate with the existing Internet, and so the use of IETF standards. 3GPP also knows that additions or modifications might be needed so the IETF Internet spec fulfills 3GPP's needs. when that happens, 3GPP will take its concerns straight to the appropriate IETF working groups for resolution, or to an appropriate Area Director if no appropriate working group can be found 🫶

3.2 IETF access to 3GPP Wireless expertise 📡

the technical work in 3GPP is organized into Technical Specification Groups TSGs, each with their own area of responsibilities. the expertise is split up like this:

  • TSG-RAN and TSG-GERAN are responsible for the Radio Access networks based on UTRAN and GERAN, so they're the experts on the characteristics of the physical transport 📶
  • TSG CN is responsible for Mobility Management and other core network protocols and functionalities 🌐
  • TSG-T is responsible for Terminal aspects and applications 📱
  • TSG-SA is responsible for service and system aspects, including overall architecture, security, and O&M aspects 🔐

contacts for the TSGs can be found on the 3GPP web-site http://www.3gpp.org/ 🌈

4. Document Sharing 📂

both 3GPP and IETF encourage sharing draft documents that are of mutual interest. it's giving collab 🤝

3GPP documents are available on its official web-site (http://www.3gpp.org/) and are open to anyone. IETF documents, including preliminary working documents ("Internet Drafts"), are available on its web-site (http://www.ietf.org/) and various shadow sites 🦋

IETF reps can get info about 3GPP document and web-site structures by contacting the relevant 3GPP contact points listed on the 3GPP web-site http://www.3gpp.org/ 🧚

3GPP reps can get info about IETF document and web-site structures by contacting the relevant IETF contact points (the Area Directors listed on the IETF web-site http://www.ietf.org/) 💜

5. Communication 💬

informal communication at the working level is encouraged whenever possible. no cap, that's the vibe 🌸

the vast majority of technical discussion and decision making in both IETF and 3GPP happens over mailing lists. both web-sites have info about the associated lists 📬

it is recommended that interested individuals subscribe to and participate in these lists. lowkey the best way to be in the loop 🙈

when deemed necessary, formal communication between 3GPP and IETF is also permitted. Relevant IETF Area Directors and 3GPP technical leadership are encouraged and authorized to facilitate these communications when needed ✨

6. Rapporteurs/coordinators 🎀

6.1 IETF coordination support in 3GPP 🧩

an IETF rapporteur function is established in 3GPP TSG-SA 👑

the individual(s) appointed to this function should be the initial contact point in 3GPP for matters pertaining to 3GPP-IETF cooperation. and of course, the chairman of TSG-SA can always be contacted 💅

so the 3GPP-IETF rapporteur function is expected to work with the concerned working groups and TSGs and support the interaction between 3GPP and IETF. main character energy 🌟

6.2 3GPP Liaison in IETF 🌷

the preferred way for orgs to work with IETF is through working groups. however, IETF has a limited number of liaison relationships with other orgs, for when conditions warrant appointing a specific person 🫶

the appointment, by the IAB, of a specific person to function as a "3GPP liaison" is proposed 🔥

the role of the 3GPP Liaison is to act as an initial contact point in IETF for administrative aspects of this collab that can't easily be handled in other ways (for example, technically through interactions with IETF Working Groups or Area Directors). it's agreed that the role does not carry an expectation of attending 3GPP meetings or taking part in 3GPP administrative processes. all liaison efforts assigned to this person are expected to be handled by electronic mail 📧

the liaison will not have the ability to make exceptions to, or special provisions for, IETF policies and procedures. no special treatment, periodt 💀

9. Participation 🌈

to help info flow between the orgs, the IETF can, on a per-case basis, appoint a rapporteur to participate and represent IETF at 3GPP technical meetings 🧚

IETF meetings are open to any interested individuals 🦋

3GPP partners (OPs, MRPs) or individual members can participate in any IETF meetings, following the existing IETF procedures 🎀

8. Security Considerations 🔐

okay this part is giving serious 😭 this type of non-protocol document does not directly affect the security of the Internet. no protocol means no direct security impact, but still 🫶

9. Authors' Addresses 📮

questions about this memo can be directed to:

Karl Heinz Rosenbrock
ETSI
06921 Sophia Antipolis
CEDEX
France

Phone: +33 492 94 4212
EMail: rosenbrock@etsi.fr


Raj Sanmugam
Director, Systems and Technology
Ericsson Canada Inc.
8400 Decarie Blvd
TMR, Quebec
H4P 2N2

Phone: +1 514 345 7862
Email: Raj.Sanmugam@ericsson.ca


Scott Bradner
Harvard University
Cambridge, MA 02138
USA

Phone: +1 617 495 3864
EMail: sob@harvard.edu


John C. Klensin
AT&T Labs
99 Bedford St
Boston, MA 02111
USA

Phone: +1 617 513 7285
EMail: Klensin+iab@jck.com
Note: Changes to the contents of this memo requires the approval from 3GPP PCG: EMail: 3GPPContact@etsi.fr 🚨

Appendix A: Acronyms 📖

glossary of acronyms, bestie 🍓

3GPP         Third Generation Partnership Project
BCP          Best Current Practice
IAB          Internet Architecture Board
IESG         Internet Engineering Steering Group
IETF         Internet Engineering Task Force
IPR          Intellectual Property rights
MRP          Market Representation Partner
OP           Organizational Partner
O&M          Operation and Maintenance
PCG          Project coordination Group
RFC          Request for Comments
TSG          Technical Specification Group
TSG-SA       TSG Services and systems aspects
TSG-CN       TSG Core Network
TSG-RAN      TSG Radio Access Network
TSG-GERAN    TSG GSM Radio Access Network
TSG-T        TSG Terminals
UTRAN        Universal Terrestrial Radio Access Network
WWW          World Wide Web

Copyright (C) The Internet Society (2001). All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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.

Acknowledgement 🫶

funding for the RFC Editor function is currently provided by the Internet Society 💖

📦 where this page comes from