Re: [Dime] RE : Re: draft reply LS to 3GPP SA5 on RFC 4006..

"Gardella, Maryse (Nokia - FR)" <maryse.gardella@nokia.com> Tue, 09 August 2016 07:30 UTC

Return-Path: <maryse.gardella@nokia.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D88312D123 for <dime@ietfa.amsl.com>; Tue, 9 Aug 2016 00:30:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qvxiOyhNQ6GM for <dime@ietfa.amsl.com>; Tue, 9 Aug 2016 00:30:55 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2167112D0DF for <dime@ietf.org>; Tue, 9 Aug 2016 00:30:55 -0700 (PDT)
Received: from fr712umx3.dmz.alcatel-lucent.com (unknown [135.245.210.42]) by Websense Email Security Gateway with ESMTPS id 8E2428A9E9D5E; Tue, 9 Aug 2016 07:30:50 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx3.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u797Uplh023970 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 9 Aug 2016 07:30:51 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id u797UpTw021003 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 9 Aug 2016 09:30:51 +0200
Received: from FR712WXCHMBA09.zeu.alcatel-lucent.com ([169.254.5.95]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Tue, 9 Aug 2016 09:30:51 +0200
From: "Gardella, Maryse (Nokia - FR)" <maryse.gardella@nokia.com>
To: "lionel.morand@orange.com" <lionel.morand@orange.com>, Yuval Lifshitz <ylifshitz@sandvine.com>, "jouni.nospam@gmail.com" <jouni.nospam@gmail.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: =?iso-8859-1?Q?[Dime]_RE=A0:_Re:__draft_reply_LS_to_3GPP_SA5_on_RFC_4006.?= =?iso-8859-1?Q?.?=
Thread-Index: AQHR8LNpoLzyw34jtEqZaswum8xBhKBAPdbw
Date: Tue, 9 Aug 2016 07:30:49 +0000
Message-ID: <F77ED24D51A356439EE433AD28B990DFC5126379@FR712WXCHMBA09.zeu.alcatel-lucent.com>
References: <15d3fa95-db4d-d3c5-273c-8d4419e1b156@gmail.com>, <C43C255C7106314F8D13D03FA20CFE4930CC1120@wtl-exchp-2.sandvine.com> <6993_1470578141_57A73DDD_6993_8490_1_6B7134B31289DC4FAF731D844122B36E01F52BC2@OPEXCLILM43.corporate.adroot.infra.ftgroup>
In-Reply-To: <6993_1470578141_57A73DDD_6993_8490_1_6B7134B31289DC4FAF731D844122B36E01F52BC2@OPEXCLILM43.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: multipart/alternative; boundary="_000_F77ED24D51A356439EE433AD28B990DFC5126379FR712WXCHMBA09z_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/jTHME9iB38fQYaz6pjTkJi6JBqw>
Subject: Re: [Dime] =?iso-8859-1?q?RE=A0=3A_Re=3A__draft_reply_LS_to_3GPP_SA5_?= =?iso-8859-1?q?on_RFC_4006=2E=2E?=
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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, 09 Aug 2016 07:30:58 -0000

Hi,

I would also favor having the two questions from the 3GPP LS repeated as per suggestion below:

"The IETF DIME WG has discussed both options raised in the LS from 3GPP SA5:
*             Is IETF RFC 4006 planned to be updated in order to rely on IETF RFC 6733 as the new Diameter Base protocol?
*             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 first option."

Beside this, I am not sure to understand the sentence below in the context of this LS:
"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". Especially what is intended to be conveyed  behind "In the present case"?

Maryse

From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of lionel.morand@orange.com
Sent: dimanche 7 août 2016 15:56
To: Yuval Lifshitz; jouni.nospam@gmail.com; dime@ietf.org
Subject: [Dime] RE : Re: draft reply LS to 3GPP SA5 on RFC 4006..


Of course :)

Lionel
Le 7 août 2016 07:54, Yuval Lifshitz <ylifshitz@sandvine.com<mailto:ylifshitz@sandvine.com>> a écrit :
Did you mean?

" 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."

-----Original Message-----
From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of Jouni Korhonen
Sent: Friday, August 05, 2016 8:41 PM
To: dime@ietf.org<mailto:dime@ietf.org>
Subject: [Dime] draft reply LS to 3GPP SA5 on RFC 4006..

Folks,

Lionel and I have been drafting a reply LS to 3GPP SA5 (and CC CT3/CT4).
This is the current draft. Comments are welcome. One question is (Lionel favours, I disagree ;) whether we should repeat the two questions 3GPP asked from us or assume they can look it up from the origial LS.

- Jouni & Lionel

-------------------------------------------------------------------------
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 and the decision was made to update of the IETF RFC 4006 (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 and 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 3588 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.
-------------------------------------------------------------------------



_______________________________________________
DiME mailing list
DiME@ietf.org<mailto:DiME@ietf.org>
https://www.ietf.org/mailman/listinfo/dime

_______________________________________________
DiME mailing list
DiME@ietf.org<mailto:DiME@ietf.org>
https://www.ietf.org/mailman/listinfo/dime

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.