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

jouni korhonen <jouni.nospam@gmail.com> Fri, 16 September 2016 20: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 0452112B028 for <dime@ietfa.amsl.com>; Fri, 16 Sep 2016 13:47:18 -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 cjAd-nyKD5ue for <dime@ietfa.amsl.com>; Fri, 16 Sep 2016 13:47:16 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (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 C3F0C12B027 for <dime@ietf.org>; Fri, 16 Sep 2016 13:47:15 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id t67so93079215ywg.3 for <dime@ietf.org>; Fri, 16 Sep 2016 13:47:15 -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; bh=uJlXWQAHvpzAsn+iBv9a4+EJ1sgBmx1vGQjOH77qEZA=; b=a1MpTED9mXzwEIePFN2FfBHw7pXafLDa8YHoLYQLlW9wWXfBTdrbWYxwxzUp61NiDO 6R3n+wGXd7h0/QE2w5I8OUbem1Ktkoar897DObIa8YSbcVY2mFfKVIq3sEXRKFh5UZKv PSRDb4gMzvNtlX0XW4nqSyVADEHVW6uYOJV1omDEvNlgtVMBwxMEiGLVWG4f1c8mjOHC k8rJ7ow/KCzK/1cWuXnQqGIArUG1yKnC0SMYz4ps8W+6VCG20yx0fntRZh6/fS6TfSxH RCBqVQcCgmfdukSnHfevSmOuGJMv5oITr5auYCvERBVLC/E1YTLBk0uJ2lYWiuPliKfB 2a+g==
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; bh=uJlXWQAHvpzAsn+iBv9a4+EJ1sgBmx1vGQjOH77qEZA=; b=fjWEN9LrdjqxHYAFdEyIr/NEmOjkGVqDhNPzh1CGn6CxNgDxH50JK8ggTs/4JO/xHh lBedw8Topj87cJUZZKlPio+yGthAdTXFMoRVJawoewRTCJcLIhBWjVU9NBoCnxsl28i7 pN6VpTm0B+lKfxGdBjSMzxM/vPZw7QJRnh5BdegzSmY1LCT25NK1pS11bD533XjMA09l AOlUf8qGcUuZqroSSHBWbXzPCAEiaEQGrESeg8zyx9R/1sfoZMo5qvHP9ZsoFH6E2uZo Cik7BF4PldmRjBA26uAQU6P4ceG215s9hu6UI6f2tbujeQ09PY/GvwgZl4E43SG3U+Zc LzwA==
X-Gm-Message-State: AE9vXwOOrRjsRECq3YAtVfgBVw7TJWteEITbgz5Hcoi6oiubDv+rpzagFoPFbRsRu46F8S+kCgiDvNnhFMbhTw==
X-Received: by 10.129.73.135 with SMTP id w129mr11973153ywa.288.1474058834833; Fri, 16 Sep 2016 13:47:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.95.67 with HTTP; Fri, 16 Sep 2016 13:47:14 -0700 (PDT)
In-Reply-To: <15d3fa95-db4d-d3c5-273c-8d4419e1b156@gmail.com>
References: <15d3fa95-db4d-d3c5-273c-8d4419e1b156@gmail.com>
From: jouni korhonen <jouni.nospam@gmail.com>
Date: Fri, 16 Sep 2016 13:47:14 -0700
Message-ID: <CAC8SSWuNu_vHFrd6OC53Nh7nKD3N+4kSQjvOfUPVENbX+Y3-Zw@mail.gmail.com>
To: "dime@ietf.org" <dime@ietf.org>
Content-Type: multipart/alternative; boundary=001a114dd0943a98de053ca6111a
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/rCFC01WJxjTjHa9at4bCqCDUvkM>
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: Fri, 16 Sep 2016 20:47:18 -0000

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