RFC 3131

3GPP2-IETF Standardization Collaboration

📅 published June 2001, from ietf

RFC 3131: 3GPP2-IETF Standardization Collaboration 🎀

Part 1 of 2 💖 Okay bestie, this one is from June 2001 and it's the handshake deal between 3GPP2 and the IETF. It's an Informational doc, so it's sharing info for the Internet community and it does not set any Internet standard 🫶

It was written under the Network Working Group by Scott Bradner (Harvard University), Pat Calhoun (Sun Microsystems, Inc.), Henry Cuschieri (TIA), Steve Dennett (Motorola), Gerry Flynn (Verizon Wireless), Mark Lipford (Sprint PCS), and Mike McPheters (Lucent Technologies). The header has no Obsoletes or Updates lines, so it isn't replacing or changing anything 🌈

Status of this Memo 📌

This memo is info for the Internet community. It is not a standard of any kind 🌸 Distribution of this memo is unlimited, so share it with everyone ✨

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

Abstract 🦋

This doc describes the standardization collaboration between 3GPP2 and IETF. That's the whole tea, honestly 🍓

1. Conventions used in this document 📚

This doc uses a lot of terms that are specific to IETF, 3GPP2, or their areas of work, so don't panic if it looks like alphabet soup 🥹 Check appendix A for what the acronyms mean. The organizations' own definitions live on their websites 💻

2. Introduction 🌷

This doc is a set of principles and guidelines. It's the foundation for the collaboration between 3GPP2 and IETF, and the goal is getting technical specifications built on time so they work well with existing fixed and mobile Internet systems, devices, and protocols. Maximum interoperability, bestie 🤝

Each org runs on its own rules and procedures. That covers IPR policy, how specs get written, approved, and maintained, all of it 📜

3. Reasons For Collaboration 🧩

3.1 3GPP2 use of IETF Internet Standards 🌐

3GPP2 has figured out that adopting Internet specs is a huge win for its own specs 🙌

The preferred approach is to use Internet standards unchanged, if that's feasible. Either way, 3GPP2 has no plans to duplicate work that's already being done in the IETF. Duplicate work is giving wasteful 🙅‍♀️

Still, 3GPP2 knows that working well with the existing Internet is important, and that's why IETF standards matter to it. It also admits that additions or modifications might be needed so an IETF Internet spec can meet 3GPP2's needs. If that happens, 3GPP2 will take its concerns straight to the right IETF working group to get them resolved. If no suitable working group exists, it'll go to an appropriate Area Director instead 💜

3.2 IETF access to 3GPP2 Wireless expertise 📡

3GPP2 work is organized into Technical Specification Groups (TSGs). Each one owns its own area of responsibility 🗂️

TSG-A and TSG-C handle the Radio Access networks based on CDMA. That makes them the experts on the characteristics of the physical transport 📶

TSG-N handles Mobility Management and other core network protocols and functionality 🛰️

TSG-P handles data services and applications 📱

TSG-S handles service and system aspects, including the overall architecture, security, and O&M aspects 🔐

You can find contacts for the TSGs on the 3GPP2 website, www.3gpp2.org 🔗

4. Document Sharing 📂

Both 3GPP2 and IETF love sharing draft docs that they both care about 🫶

3GPP2 working docs live on its official website and get sorted by meeting. They're on the 3GPP2 ftp server, which is open to anyone, at ftp://ftp.3gpp2.org 💾 3GPP2 specs that have finished the 15-day Steering Committee review are over here:

http://www.3gpp2.org/Public_html/Specs/index.cfm

IETF docs are on its website at http://www.ietf.org/, along with preliminary working docs called "Internet Drafts" and a bunch of shadow sites too 🪞

IETF reps who want to learn how the 3GPP2 doc and website setup works can contact the right 3GPP2 contacts listed on www.3gpp2.org 🙋‍♀️

3GPP2 reps who want the same info about IETF can contact the right IETF contacts, which are the Area Directors listed on www.ietf.org 🙋

5. Communication 💬

Informal working-level chats are encouraged whenever they're possible. Low-key, high-value 🫠

The vast majority of IETF's technical discussion and decision making happens on mailing lists. Interested people are recommended to subscribe and participate in them 📧

3GPP2 mailing lists aren't open to the general public, though. For work that both groups care about, it's recommended to discuss it on the relevant IETF mailing lists instead 🙃

Formal communication between 3GPP2 and IETF is also allowed when it's needed. Relevant IETF Area Directors and 3GPP2 technical leadership are encouraged and authorized to make that happen 💌

6. Rapporteurs/coordinators 🧚‍♀️

6.1 IETF coordination support in 3GPP2 🤝

An IETF rapporteur function gets set up inside the 3GPP2 Steering Committee ✨

Whoever takes on this function should be the first contact point in 3GPP2 for anything about the 3GPP2-IETF cooperation. The chairman of the Steering Committee can always be contacted too 📞

So the 3GPP2-IETF rapporteur is expected to work with the concerned working groups and TSGs and keep the 3GPP2 and IETF talking to each other 🗣️

6.2 3GPP2 Liaison in IETF 🎀

Organizations usually work with IETF through its working groups, and that's the preferred route 🛤️ IETF also has a small number of liaison relationships with other orgs, for when the situation really calls for a specific person 💁‍♀️

It's proposed that a specific person in the IESG act as a "3GPP2 liaison" 🌸

The liaison is the first contact point in IETF for admin stuff that can't easily be handled another way, like technical stuff that goes through working groups or Area Directors. The role doesn't mean going to 3GPP2 meetings or joining 3GPP2 admin processes. It's expected that the liaison's work will happen over email. The liaison also can't make exceptions to, or special provisions for, IETF policies and procedures, so no VIP passes here 🙅‍♀️

7. Participation 🦋

To keep info flowing between the two orgs, IETF can appoint an observer on a case-by-case basis to attend and represent IETF at 3GPP2 technical meetings 👀

IETF meetings are open to any interested individuals. Come join the fun 🎉

3GPP2 partners (OPs, MRPs) or individual members can join any IETF meeting, following the existing IETF procedures 📋

3GPP2 meetings are open to any interested individual too, but those individuals don't get voting privileges 🗳️ The meeting schedule is on the 3GPP2 website 🗓️

Okay so, the legal bit, but make it cute 🎀. The Internet Society owns the copyright here: Copyright (C) The Internet Society (2001). All Rights Reserved. 💅

You're allowed to copy this document and share it with others, and you can even write derivative works that comment on it, explain it, or help people implement it 🫶. You can publish and distribute those too, in whole or in part, with no restriction of any kind. The one condition is that the above copyright notice and this paragraph stay on every copy and every derivative work 📜.

BUT (and this is important, bestie) this document itself may not be modified in any way. You can't remove the copyright notice, and you can't remove references to the Internet Society or other Internet organizations. The exceptions are: you need it for developing Internet standards, in which case you follow the copyright procedures in the Internet Standards process, or you need to translate it into languages other than English 🌍.

These permissions are perpetual. The Internet Society and its successors or assigns won't revoke them 💜.

The document and everything in it is provided on an "AS IS" basis 🫠. 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. Not gonna lie, that's a lot of caps, but the message is clear 😭.

Acknowledgement 🌸

Funding for the RFC Editor function is currently provided by the Internet Society. So the Internet Society keeps the RFC Editor running, which is honestly iconic of them 👑🦋

📦 where this page comes from