| Internet-Draft | 3GPP-IETF Collaboration | July 2024 |
| Dawkins, et al. | Expires 24 January 2025 | [Page] |
This document describes the standardization collaboration between 3GPP and IETF.¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at https://SpencerDawkins.github.io/moq-requirements/#go.draft-dawkins-iab-rfc3113bis.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-dawkins-iab-rfc3113bis/.¶
Discussion of this document takes place on the 3GPP IETF Coordination Working Group mailing list (mailto:3gpp-ietf-coord@ietf.org), which is archived at https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord. Subscribe at https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord/.¶
Source for this draft and an issue tracker can be found at https://github.com/SpencerDawkins/rfc3113bis.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 24 January 2025.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.¶
This document contains a set of principles and guidelines that serves as the basis for establishing the collaboration between 3GPP and IETF, with the objective of securing timely development of technical specification that facilitate maximum interoperability with existing (fixed and mobile) Internet systems, devices, and protocols.¶
Each organization will operate according to their own rules and procedures including rules governing IPR policy, specification elaboration, approval and maintenance.¶
This document uses significant terminology that is specialized to IETF, 3GPP, or their areas of work. See Appendix A for definitions of acronyms. The organizational definitions can be found in their respective web-sites.¶
In the further development of 3GPP specifications, the benefit of adopting Internet specifications has been identified.¶
The preferred 3GPP approach is to use the Internet standards unchanged, if feasible. In any case, 3GPP has no intention to duplicate work performed in IETF.¶
However, while this document recognizes the importance of 3GPP interoperability with the existing Internet and hence the use of IETF standards, 3GPP recognizes that additions or modifications might be needed in order to make the IETF internet specification fulfill the needs of 3GPP. In such cases, 3GPP will take its concerns directly to the appropriate IETF working groups for resolution, or to an appropriate Area Director if no appropriate working group can be found.¶
The technical work in 3GPP is organized in Technical Specification Groups TSGs each with their area of responsibilities. Details of the groups within 3GPP can be found at see www.3gpp.org/3gpp-groups.¶
Both 3GPP and IETF encourage the sharing of draft documents that are of mutual interest.¶
3GPP documents are available on its official web-site (http://www.3gpp.org/ and is 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 representatives can obtain information about the 3GPP document and web-site structures by contacting the relevant 3GPP contact points indicated at the 3GPP web-site http://www.3gpp.org/.¶
3GPP representatives can obtain information about the IETF document and web-site structures by contacting the relevant IETF contact points (the Area Directors indicated at the IETF web-site http://www.ietf.org/).¶
Whenever possible, informal communication at working level is encouraged.¶
The vast majority of the technical discussions and decision making in both IETF and 3GPP is done over mailing lists. Both 3GPP and IETF web sites contain information concerning the associated mailing lists.¶
It is recommended that interested individuals subscribe to and participate in these lists.¶
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 such communications when needed.¶
The TSG-CT chair (https://www.3gpp.org/dynareport?code=TSG-WG--CP--officials.htm) is assigned to do the coordination from 3GPP towards IETF. The in dividual(s) appointed to undertake the responsibility of this function should be the initial contact point in 3GPP for matters pertaining to the 3GPP-IETF cooperation.¶
The preferred way for organizations to work with IETF is through the working groups. However, IETF has a limited number of liaison relationships with other organizations when conditions warrant the appointment of 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 collaboration that cannot easily be handled in other ways (e.g., at a technical level by interactions with IETF Working Groups or Area Directors). It is agreed that the role does not carry the expectation of attendance at 3GPP meetings or participation in 3GPP administrative processes and anticipated that all liaison efforts assigned to this individual will be carried out by electronic mail. It is understood that the liaison will not have the ability to make exceptions to, or special provisions for, IETF policies and procedures.¶
In order to assist the information flow between the organizations, the IETF can on 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 of the IETF meetings, in accordance with the existing IETF procedures.¶
This type of non-protocol document does not directly affect the security of the Internet.¶
3GPP is tracking IANA interactions via their homepage see https://www.3gpp.org/delegates-corner/delegates-corner-home/iana-v2.¶
| Acronym | Expansion |
|---|---|
| 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 |
TODO acknowledge.¶