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

jouni korhonen <jouni.nospam@gmail.com> Mon, 19 September 2016 19:49 UTC

Return-Path: <jouni.nospam@gmail.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 72AFF12B036 for <dime@ietfa.amsl.com>; Mon, 19 Sep 2016 12:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JyYs2QcYdrnE for <dime@ietfa.amsl.com>; Mon, 19 Sep 2016 12:49:24 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB1DF12B02B for <dime@ietf.org>; Mon, 19 Sep 2016 12:49:23 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id g192so162324454ywh.1 for <dime@ietf.org>; Mon, 19 Sep 2016 12:49:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eY+uyQhQsgM1sSgHsHozQUEXX0vJ2k+fkIJetnvqHh4=; b=CNuc1Piy/R/UGK/oRm7i4/1/M1Wcp4ZDCkrV3lfQz64buXUW9lq3DPliOrO0UlpzrE urFhiIRP45Y9s2Wm5a8JmgFItHD5lRM9SO4EB/8u+mbWJgLVDL4q0vZb6I7akFjRRd8X PKhpRtJAVWy3l8iHX0+HxKD3F4ZyQcfoE3XvpQGasPqDpx8Sy9AyOyZriKEq99TEhWBJ QATIy11rXyuKtzLqHa6/7PoK0PXJYwv39SpBkOynTnHNNVjx3WPldZMx9blAHYsmG+3u U183ceZe97MgQe5ZeFx5B+tJEoSCsN4Q2Vp7M171fu9NEtFaOBYs/kK+5IPnDP9j0USK 9zzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eY+uyQhQsgM1sSgHsHozQUEXX0vJ2k+fkIJetnvqHh4=; b=VHsNMDYb1HCd4rxfey1tJOpeK1TlW0ybu59jITOBVhU3WD1QaRjl7HKWzbbTS5j6Xi jMnkqSDDc8VVucPvZlqalElySt7iPPlk3vIM1cWFelzoJrDG2490wN2/tGzzdm1A9FK0 uvibum2BBUv9dIxftaZ8W0ClgoTLlGDw24XbZDaSEerQDbli6DeHpkwrYTyZa/Kvcfd0 amuRIuCVZ/gY4+6WRP3TFhw7imzMxkazqL639o97Aw+X/ttLIo0SaxhqYnUSdbuUn84+ 1vyDK19uiqxV8kdc3UI5HM3WRhcMotyIYAbcw62WMgqp+91d41FIKjEbwrBBrocjLQXM Rbwg==
X-Gm-Message-State: AE9vXwOa9mYy458kM81G3Usv1PtXRwUU1j04dCUkFtp+eDVzQZ6y0/596Blis+/jajpF6k7Ctp+BygbEBHJR+g==
X-Received: by 10.129.109.66 with SMTP id i63mr27154437ywc.171.1474314563096; Mon, 19 Sep 2016 12:49:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.95.67 with HTTP; Mon, 19 Sep 2016 12:49:22 -0700 (PDT)
In-Reply-To: <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> <E8355113905631478EFF04F5AA706E98310D5384@wtl-exchp-2.sandvine.com>
From: jouni korhonen <jouni.nospam@gmail.com>
Date: Mon, 19 Sep 2016 12:49:22 -0700
Message-ID: <CAC8SSWu2BDfM84AG=ho2PuA-Sme-aQYgib5d4G+1xYaAjafOjg@mail.gmail.com>
To: Dave Dolson <ddolson@sandvine.com>
Content-Type: multipart/alternative; boundary=001a114db3c2d22e7f053ce19ba8
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/KM_pPJWCyViEPyClRUa2_aU2Epk>
Cc: "dime@ietf.org" <dime@ietf.org>
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:49:26 -0000

Ok. I think we can move forward send this reply to 3GPP.

- Jouni

On Mon, Sep 19, 2016 at 12:21 PM, Dave Dolson <ddolson@sandvine.com> wrote:

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