[Dime] New Liaison Statement, "Reply to the LS to IETF for clarification on RFC 4006 for Diameter base protocol"

Liaison Statement Management Tool <lsmt@ietf.org> Tue, 20 September 2016 14:44 UTC

Return-Path: <lsmt@ietf.org>
X-Original-To: dime@ietf.org
Delivered-To: dime@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E34B412B8FB; Tue, 20 Sep 2016 07:44:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Liaison Statement Management Tool <lsmt@ietf.org>
To: <maryse.gardella@nokia.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.33.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147438269788.29110.11365958556409982905.idtracker@ietfa.amsl.com>
Date: Tue, 20 Sep 2016 07:44:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/vEFnedmLpFjQ01wbVv94ZXwvn9s>
X-Mailman-Approved-At: Tue, 20 Sep 2016 07:50:01 -0700
Cc: Georg Mayer <georg.mayer.huawei@gmx.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Joel Jaeggli <joelja@bogus.com>, Diameter Maintenance and Extensions Discussion List <dime@ietf.org>, 3GPP TSG CT WG3 <3GPP_TSG_CT_WG3@LIST.ETSI.ORG>, 3GPP TSG CT WG4 <3GPP_TSG_CT_WG4@LIST.ETSI.ORG>
Subject: [Dime] New Liaison Statement, "Reply to the LS to IETF for clarification on RFC 4006 for Diameter base protocol"
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Sep 2016 14:44:58 -0000

Title: Reply to the LS to IETF for clarification on RFC 4006 for Diameter base protocol
Submission Date: 2016-09-20
URL of the IETF Web page: https://datatracker.ietf.org/liaison/1493/

From: "Lionel Morand" <lionel.morand@orange.com>
To: maryse.gardella@nokia.com
Cc: Benoit Claise <bclaise@cisco.com>,Lionel Morand <lionel.morand@orange.com>,Joel Jaeggli <joelja@bogus.com>,Jouni Korhonen <jouni.nospam@gmail.com>,Diameter Maintenance and Extensions Discussion List <dime@ietf.org>,Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,Stephen Farrell <stephen.farrell@cs.tcd.ie>,Georg Mayer <georg.mayer.huawei@gmx.com>,3GPP TSG CT WG4 <3GPP_TSG_CT_WG4@LIST.ETSI.ORG>,3GPP TSG CT WG3 <3GPP_TSG_CT_WG3@LIST.ETSI.ORG>
Response Contacts: Jouni Korhonen <jouni.nospam@gmail.com>,Lionel Morand <lionel.morand@orange.com>
Technical Contacts: 
Purpose: In response

Referenced liaison: LS to IETF for clarification on RFC 4006 for Diameter Base Protocol (https://datatracker.ietf.org/liaison/1470/)

Body: The IETF DIME WG thanks the 3GPP SA5 WG for their LS and query regarding the IETF RFC 4006 (https://datatracker.ietf.org/liaison/1470/).

The IETF DIME WG has discussed both options raised in the LS from 3GPP SA5:

1) Is IETF RFC 4006 planned to be updated in order to rely on IETF RFC 6733 as the new Diameter Base protocol?

2) If not, are there any recommendations from IETF on how to address the implicit reference to IETF RFC 3588 as Diameter Base Protocol for 3GPP SA5 Diameter Online charging through use of IETF RFC 4006?   

and the decision was made to update of the IETF RFC 4006 as per the option 1). 

The aim of this update is to:
- align the Diameter Credit-Control application specification with the IETF RFC 6733,
- fix existing known issues in the current specification,
- comply with the recommendations given in the IETF RFC 7423 on the design of Diameter application. 

The time line for the completion of the RFC 4006 update is set to November 2017.

As a reminder, the IETF RFC 6733 does not define a new Diameter base protocol but is a new version of the specification defining the Diameter base protocol. The IETF RFC 3588 is obsoleted by the IETF RFC 6733, as defined in the IETF
RFC 2223:

   Obsoleted-by

      To be used to refer to the newer document(s) that replaces the
      older document.

In the present case, any document using the IETF RFC 3588 as reference for the Diameter base protocol should be updated to refer to the new IETF RFC 6733. Therefore, as a general guideline, the IETF DIME WG recommends 3GPP WGs to follow this recommendation in their specifications when applicable.
The same recommendation will apply for the revision of the IETF RFC 4006 when published by the IETF as for any new RFC obsoleting an old RFC.

Attachments:

No document has been attached