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

Dave Dolson <ddolson@sandvine.com> Mon, 19 September 2016 19:21 UTC

Return-Path: <ddolson@sandvine.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 C0D4E12B4E3 for <dime@ietfa.amsl.com>; Mon, 19 Sep 2016 12:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.216
X-Spam-Level:
X-Spam-Status: No, score=-4.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-2.316] 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 n-k2kwLB87aw for <dime@ietfa.amsl.com>; Mon, 19 Sep 2016 12:21:17 -0700 (PDT)
Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4A8112B015 for <dime@ietf.org>; Mon, 19 Sep 2016 12:21:17 -0700 (PDT)
Received: from WTL-EXCHP-2.sandvine.com ([fe80::68ac:f071:19ff:3455]) by wtl-exchp-1.sandvine.com ([::1]) with mapi id 14.03.0319.002; Mon, 19 Sep 2016 15:21:16 -0400
From: Dave Dolson <ddolson@sandvine.com>
To: "lionel.morand@orange.com" <lionel.morand@orange.com>, Jouni <jouni.nospam@gmail.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] draft reply LS to 3GPP SA5 on RFC 4006..
Thread-Index: AQHR70GrXGVt+Nt0EkuX481hGuyqjqB9G4wAgASEooCAABQhgP//wxgQ
Date: Mon, 19 Sep 2016 19:21:15 +0000
Message-ID: <E8355113905631478EFF04F5AA706E98310D5384@wtl-exchp-2.sandvine.com>
References: <15d3fa95-db4d-d3c5-273c-8d4419e1b156@gmail.com> <CAC8SSWuNu_vHFrd6OC53Nh7nKD3N+4kSQjvOfUPVENbX+Y3-Zw@mail.gmail.com> <D66DA74F-379E-4B7B-913E-C2FC5D2AE864@gmail.com> <17142_1474311542_57E03576_17142_6918_1_6B7134B31289DC4FAF731D844122B36E01FB9D9E@OPEXCLILM43.corporate.adroot.infra.ftgroup>
In-Reply-To: <17142_1474311542_57E03576_17142_6918_1_6B7134B31289DC4FAF731D844122B36E01FB9D9E@OPEXCLILM43.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.200.63]
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/9snpt264Ayn22Rq-DG7wXDQXR08>
Subject: Re: [Dime] draft reply LS to 3GPP SA5 on RFC 4006..
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: Mon, 19 Sep 2016 19:21:20 -0000

+1

-----Original Message-----
From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of lionel.morand@orange.com
Sent: Monday, September 19, 2016 2:59 PM
To: Jouni; dime@ietf.org
Subject: Re: [Dime] draft reply LS to 3GPP SA5 on RFC 4006..

I'm fine too.

Lionel

> -----Message d'origine-----
> De : DiME [mailto:dime-bounces@ietf.org] De la part de Jouni
> Envoyé : lundi 19 septembre 2016 19:47
> À : dime@ietf.org
> Objet : Re: [Dime] draft reply LS to 3GPP SA5 on RFC 4006..
> 
> Everybody happy with the text?
> 
> - Jouni
> 
> 
> > On 16 Sep 2016, at 13:47, jouni korhonen <jouni.nospam@gmail.com> wrote:
> >
> > Folks,
> >
> > I updated the draft LS based on the input. See below and comment.
> >
> > - Jouni
> >
> > ----------------------------------------------------------------------
> > --------- 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 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 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.
> > ----------------------------------------------------------------------
> > ---------
> >
> >
> > On Fri, Aug 5, 2016 at 10:41 AM, Jouni Korhonen <jouni.nospam@gmail.com>
> wrote:
> > 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

_________________________________________________________________________________________________________________________

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.

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