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

Jouni <jouni.nospam@gmail.com> Mon, 19 September 2016 17:47 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 C5AB612B135 for <dime@ietfa.amsl.com>; Mon, 19 Sep 2016 10:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, 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 WoD1r8bNjnJl for <dime@ietfa.amsl.com>; Mon, 19 Sep 2016 10:47:01 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 9B45512B12D for <dime@ietf.org>; Mon, 19 Sep 2016 10:47:01 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id q2so33018432pfj.3 for <dime@ietf.org>; Mon, 19 Sep 2016 10:47:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=j0iOp4rFIVatPCwlYOLBqG0ilUCA7JgbTQLY8PPoi4w=; b=QVRJPZp6lMOLSo+8y1qmKLS52ZD8gHnXj/9PAgXrPMc4JmjcuQF77atGEZg2g9J/le 3ZGL7WGxpIru+Yvpi0HTwxjVDI6WjZrYcpN4kAxCipQ5N1LkIy0lP0MCkWRopC3oNhEl ifcEb5rE/I1c2oI7bQhqr4SGxJwqOInRvPVegPVMDGzIuXqBZ9Z4X5we1V4FUF9fBHTA URfIO0fHYfrl3lJiQRtjQay3NjTY/vcvzU6ZCKHImbQeVMUJ0P2znE3JKphxV7oTBynT T6DujAdQ9lYI0+j/mt5UAsct8ys/jFSA6hdIhIFdzTxO3Q4eBwJ3wBXmcIo2994S1pCE 1LZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=j0iOp4rFIVatPCwlYOLBqG0ilUCA7JgbTQLY8PPoi4w=; b=N/neZ0AjnYOuYxGH21aEm6aOYgHgaH4IHjNDpGvEknRxVenWRWhcF2Aj7tLqUjfqbU CgFKpbMPJgWrr9+NVf1pfqdLXZc2OoDM8rFMnFuPvRNSYEfGmh2ZHJ1T+l45oIdlWpaa wE149tf1U2sMQtJmcpfpPWu1+OGOeIdZVaBUANe5amjKzuWQoIia1ShE1Lte87RBXUrq C5Q/oyIUqJETODWa6MLlwbjyQX7OXJnWNgdv61wZhTUoAhta4OzheVTgkQfET4Bg2bX1 JPLXVw1+EJ0Nw//5dnOrdZrEPgqepktE0lwut6zNY82r638uPnNJu/Tovx2GLfQUUNq2 1I0g==
X-Gm-Message-State: AE9vXwMrV7EgZnQu1/DhlS0ckEXYqnmAaEzWjELz6VxKXt/7dNLPYHgksT+de7Y8u+XkBw==
X-Received: by 10.98.68.148 with SMTP id m20mr49430758pfi.0.1474307221043; Mon, 19 Sep 2016 10:47:01 -0700 (PDT)
Received: from ?IPv6:2601:647:4200:e520:51f6:e092:3a5d:beb4? ([2601:647:4200:e520:51f6:e092:3a5d:beb4]) by smtp.gmail.com with ESMTPSA id an11sm33095392pac.26.2016.09.19.10.47.00 for <dime@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 19 Sep 2016 10:47:00 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Jouni <jouni.nospam@gmail.com>
In-Reply-To: <CAC8SSWuNu_vHFrd6OC53Nh7nKD3N+4kSQjvOfUPVENbX+Y3-Zw@mail.gmail.com>
Date: Mon, 19 Sep 2016 10:46:59 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D66DA74F-379E-4B7B-913E-C2FC5D2AE864@gmail.com>
References: <15d3fa95-db4d-d3c5-273c-8d4419e1b156@gmail.com> <CAC8SSWuNu_vHFrd6OC53Nh7nKD3N+4kSQjvOfUPVENbX+Y3-Zw@mail.gmail.com>
To: "dime@ietf.org" <dime@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/4_lh-iizmu_Q3QQ6zFpAh_qqqzA>
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 17:47:04 -0000

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