Internet-Draft 3GPP-IETF Standardization Collaboration March 2025
Krishnan, et al. Expires 17 September 2025 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-kes-rfc3113bis-00
Obsoletes:
3113 (if approved)
Published:
Intended Status:
Informational
Expires:
Authors:
S. Krishnan
Cisco
C. Eckel
Cisco
P. Schmitt
Huawei

3GPP-IETF Standardization Collaboration

Abstract

This document contains a set of principles and guidelines that serve as the basis for the collaboration between 3GPP and IETF, with the objective of securing timely development of technical specifications, and to facilitate maximum interoperability with existing fixed and mobile Internet systems, devices, and protocols.

About This Document

This note is to be removed before publishing as an RFC.

Status information for this document may be found at https://datatracker.ietf.org/doc/draft-kes-rfc3113bis/.

Discussion of this document takes place on the Internet Architecture Board Internet Engineering Task Force mailing list (mailto:iab@iab.org), which is archived at https://mailarchive.ietf.org/arch/browse/iab/. Subscribe at https://www.ietf.org/mailman/listinfo/iab/.

Status of This Memo

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 17 September 2025.

Table of Contents

1. Introduction

The IETF and 3GPP formalized a set of principles and guidelines for co-operation in [RFC3113]. While the high level principles remain intact in the collaboration many of the details in that document have become out of date due to changes in the organizational structures of both IETF and 3GPP as well as in the way the co-ordination activities are conducted in practice. e.g. both the IETF and 3GPP have reorganized and renamed areas so that the RFC3113 contains incorrect and misleading information. The document access mechanisms have also been changed even as the open access principles still remain intact. It is also difficult to keep this information up to date due to the fairly dynamic nature of both of the SDOs. This document intends to reiterate the high level principles of co-operation and the co-ordination mechanisms while leaving out the detailed descriptions to be specified and maintained by the co-ordination function itself.

2. Administrative support groups

IAB Administrative Support Groups are groups with dedicated membership, similar to directorates, that act as an arm of the IAB, assisting the IAB in discharging its responsibilities. One of those responsibilities is that the IAB acts as representative of the interests of the IETF and the Internet Society in technical liaison relationships with other organizations concerned with standards and other technical and organizational issues relevant to the world-wide Internet. In 2023, the IAB decided to create an administrative support group to work on the co-ordination activities between IETF and 3GPP [IETF-3GPP].

3. IETF-3GPP Administrative Support Group

The purpose of this [IETF-3GPP].group is to support coordination activities between IETF and 3GPP. This group is led jointly by the respective liaison managers from both organizations, IETF and 3GPP. This group has no fixed membership, but participation from relevant IETF Area Directors, IETF WG Chairs, 3GPP WG Chairs, and document authors/editors is encouraged. The group co-leads will review and update the mailing list yearly prior to the July meeting, in order to adjust for changes in the IESG and IAB.

4. High level principles

As stated in RFC3113, 3GPP has identified the benefit of adopting Internet specifications and 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. While this is the preferred scenario, 3GPP recognizes that additions or modifications might be needed in order to make the IETF internet specification fulfill the needs of 3GPP, and in such cases, these concerns will be directly brought up at the IETF-3GPP administrative support group to be addressed by the relevant IETF areas and WGs. This document also reiterates the principle that informal communication at working level is encouraged whenever possible, and formal communications are to be used only when deemed necessary.

5. Changes from RFC3113

6. Security Considerations

This document is concerned with the relationship between 3GPP and IETF and does not bring up any new security considerations.

7. IANA Considerations

This document has no IANA actions.

8. References

8.1. Normative References

[RFC3113]
Rosenbrock, K., Sanmugam, R., Bradner, S., and J. Klensin, "3GPP-IETF Standardization Collaboration", RFC 3113, DOI 10.17487/RFC3113, , <https://www.rfc-editor.org/rfc/rfc3113>.

8.2. Informative References

[IETF-3GPP]
IAB, "IETF-3GPP Administrative Support Group", https://datatracker.ietf.org/group/ietf3gpp/about/ , .

Acknowledgments

Authors' Addresses

Suresh Krishnan
Cisco
Charles Eckel
Cisco
Peter Schmitt
Huawei