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

Jouni Korhonen <jouni.nospam@gmail.com> Fri, 05 August 2016 17: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 []) by ietfa.amsl.com (Postfix) with ESMTP id 756F512D688 for <dime@ietfa.amsl.com>; Fri, 5 Aug 2016 10:49:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id jUCDxyYY9gzS for <dime@ietfa.amsl.com>; Fri, 5 Aug 2016 10:49:04 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::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 8DBE212D10C for <dime@ietf.org>; Fri, 5 Aug 2016 10:49:04 -0700 (PDT)
Received: by mail-pa0-x22f.google.com with SMTP id pp5so94718479pac.3 for <dime@ietf.org>; Fri, 05 Aug 2016 10:49:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=reply-to:to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=CJw/g0OI93tQztQJAGWd7ehgBOrvOEc1P6d61SQMXc4=; b=OJbQuym0Ra+QTvMQDUVUO0nHPM5d4XF//B1ys6FcYM3+hxhYA14IrUPFr52v+LBl2o hM+vtTuIIquRZFtiURdVyyFhTmejeYh8RNdU6FlDuYu72lJZZ13zDEbysKRqN1pro28X GCVuhPedxgYhTseHzX/q1Nr0T8v2L4FlDtw8U+XmAeixZhF5dU4uPcxBfKrWE9/M0FxA F27W8c1XMpwm73c4JbZPpCL3Hbq6Hk/kgWM278C5qda2kA8uJLCpu8YzozfC5z1thSjy PxeLltiV5eGaUJ3zP5XbtlbRRdA9gYhHi7WiC9YE43KR3YjQvdFDwd40Aq86g8X+MO3o grhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:to:from:subject:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=CJw/g0OI93tQztQJAGWd7ehgBOrvOEc1P6d61SQMXc4=; b=ZiZ0D74uc0NA+d0eghf1QfzQJvYz0CRnc/mxUPrcFVVe4CwqaIOyC6rc9zgiUY3SWd +uioslPRA04tV1lDVN4gLSEX91bnLdQ5rNyohG5kuRp0/NXRdWkzgzbXnijY0ijgP4S3 WJCIJ7kXtYqaOwMbjszfqqtQAdMniI7GOPW9Dmr1Da9SoGY+ZNDsRfr1GhGC7xCH7wvr aN6T7nVBD4L2mn5lh6CHxu73JnBWXrTv+aof9hmuy9eOWQGg3/b43jiX9oLVQHzFNNI6 OA+VMpNXgRgJrjUiKBvpdADOjJJV5cEktHaKJVJRL3Ogxr33fZTvCalIL89AtQR5EYfa f2Kg==
X-Gm-Message-State: AEkooutW/hMYjLhR4XaXA7Q4ju45dbLMY8gXhGbU8Sy84NTm6m9hYl+WL0Hbglcd3w2Ceg==
X-Received: by with SMTP id bt2mr136253905pab.139.1470418870959; Fri, 05 Aug 2016 10:41:10 -0700 (PDT)
Received: from [] ([]) by smtp.googlemail.com with ESMTPSA id te10sm29603407pac.4.2016. for <dime@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Aug 2016 10:41:10 -0700 (PDT)
To: "dime@ietf.org" <dime@ietf.org>
From: Jouni Korhonen <jouni.nospam@gmail.com>
Message-ID: <15d3fa95-db4d-d3c5-273c-8d4419e1b156@gmail.com>
Date: Fri, 5 Aug 2016 10:41:06 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/qDUf5-MEalCA7vA8--EPcfazMeM>
Subject: [Dime] draft reply LS to 3GPP SA5 on RFC 4006..
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jouni.nospam@gmail.com
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, 05 Aug 2016 17:49:06 -0000


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:


       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.