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

<lionel.morand@orange.com> Sun, 07 August 2016 13:55 UTC

Return-Path: <lionel.morand@orange.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 F409012D60B for <dime@ietfa.amsl.com>; Sun, 7 Aug 2016 06:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.846
X-Spam-Level:
X-Spam-Status: No, score=-3.846 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 yH3vX--TWSPF for <dime@ietfa.amsl.com>; Sun, 7 Aug 2016 06:55:44 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor35.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CEDE12D600 for <dime@ietf.org>; Sun, 7 Aug 2016 06:55:43 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id 76DDB2124D; Sun, 7 Aug 2016 15:55:41 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.75]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 47DFD120073; Sun, 7 Aug 2016 15:55:41 +0200 (CEST)
Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe%18]) with mapi id 14.03.0301.000; Sun, 7 Aug 2016 15:55:41 +0200
From: <lionel.morand@orange.com>
To: 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?RE=A0:_Re:_[Dime]_draft_reply_LS_to_3GPP_SA5_on_RFC_4006..?=
Thread-Index: AQHR8LNhmVHbzGPaO0utFH07mEYQFQ==
Date: Sun, 7 Aug 2016 13:55:40 +0000
Message-ID: <6993_1470578141_57A73DDD_6993_8490_1_6B7134B31289DC4FAF731D844122B36E01F52BC2@OPEXCLILM43.corporate.adroot.infra.ftgroup>
References: <15d3fa95-db4d-d3c5-273c-8d4419e1b156@gmail.com>, <C43C255C7106314F8D13D03FA20CFE4930CC1120@wtl-exchp-2.sandvine.com>
In-Reply-To: <C43C255C7106314F8D13D03FA20CFE4930CC1120@wtl-exchp-2.sandvine.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_6B7134B31289DC4FAF731D844122B36E01F52BC2OPEXCLILM43corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/Bsr6kGky8ywQcsFG8t9q1cZV82I>
Subject: [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: Sun, 07 Aug 2016 13:55:46 -0000

Of course :)

Lionel

Le 7 août 2016 07:54, Yuval Lifshitz <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
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
https://www.ietf.org/mailman/listinfo/dime

_______________________________________________
DiME mailing list
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.