Re: [AAA-DOCTORS] Fwd: [Technical Errata Reported] RFC4006 (4892)

Benoit Claise <bclaise@cisco.com> Tue, 03 January 2017 12:57 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E04881294BC; Tue, 3 Jan 2017 04:57:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.196
X-Spam-Level:
X-Spam-Status: No, score=-15.196 tagged_above=-999 required=5 tests=[BAD_CREDIT=2.415, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 rHlr0UUxgBmG; Tue, 3 Jan 2017 04:57:48 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5C791295B2; Tue, 3 Jan 2017 04:57:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20561; q=dns/txt; s=iport; t=1483448268; x=1484657868; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=FDCOIF4F6hXLQ5mdSpSxGa68qa7dFZR3A96NYwmBHfg=; b=dRt6n7Ua9RhIFzi4Ikn59QikMoE+Tb4fIIcIqobkimcyzvEjJH5SzLPt 7cIbKWWjH/VJIk7jcWolhCx2ka2PA70CAoWm5/jaP2ThyVBTkkMsDqcy5 FCo4SZXR6EHzHf/19X+KaiF1d2kMuoDflUshXzNhe10nrFvD0Ki7hAC8z o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D+AAB/nmtY/xbLJq1DGhkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJxRgEBAQEBfoEMjVdyk1OCNIVHixGCD4IIKoV4AoIfFAECAQE?= =?us-ascii?q?BAQEBAWIohGgBAQEELUwQCxEDAQIhBwdGCQgGAQwGAgEBiFEDGA4tsHArihMBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEdhkWCAoJfgTuBEzuBDxEBBjYMCoUNHgWIZhG?= =?us-ascii?q?HUYoANYZUhnKDeIF1hQiDJ4Yxh36BdVWDZoQPHzhoHxYNFoN7DQ+BXz00AROFf?= =?us-ascii?q?IIuAQEB?=
X-IronPort-AV: E=Sophos;i="5.33,451,1477958400"; d="scan'208,217";a="649483460"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jan 2017 12:57:43 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v03CvgZM008469; Tue, 3 Jan 2017 12:57:43 GMT
To: lionel.morand@orange.com, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>, "sec-ads@ietf.org" <sec-ads@ietf.org>
References: <20161219091457.EF44BB80224@rfc-editor.org> <c046a2ac-a008-012e-4ad0-405066c26063@cisco.com> <784_1483438946_586B7B62_784_1775_1_6B7134B31289DC4FAF731D844122B36E0BFC5C89@OPEXCLILM43.corporate.adroot.infra.ftgroup>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <602f5ce9-43d8-22d3-3d9a-427ebd8b80c9@cisco.com>
Date: Tue, 3 Jan 2017 13:57:42 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <784_1483438946_586B7B62_784_1775_1_6B7134B31289DC4FAF731D844122B36E0BFC5C89@OPEXCLILM43.corporate.adroot.infra.ftgroup>
Content-Type: multipart/alternative; boundary="------------15EF9249747447D756C405AA"
Archived-At: <https://mailarchive.ietf.org/arch/msg/aaa-doctors/hmsO2Tq8VJqjyoaMJMgGSz8_KiM>
Cc: "Bertz, Lyle T \[CTO\]" <Lyle.T.Bertz@sprint.com>, Dave Dolson <ddolson@sandvine.com>
Subject: Re: [AAA-DOCTORS] Fwd: [Technical Errata Reported] RFC4006 (4892)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aaa-doctors/>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2017 12:57:51 -0000

Thanks, "rejected".

Regards, B.
>
> If I'm correct, this is not an erratum against 4006 but a proposed 
> change in the draft RFC4006bis 
> (https://tools.ietf.org/html/draft-ietf-dime-rfc4006bis-00).
>
> The original text quoted below is not in the RFC4006 but in the draft.
>
> Let me know if I'm correct.
>
> Regards,
>
> Lionel
>
> *De :*AAA-DOCTORS [mailto:aaa-doctors-bounces@ietf.org] *De la part 
> de* Benoit Claise
> *Envoyé :* lundi 19 décembre 2016 11:31
> *À :* aaa-doctors@ietf.org; sec-ads@ietf.org
> *Objet :* [AAA-DOCTORS] Fwd: [Technical Errata Reported] RFC4006 (4892)
>
> Dear all,
>
> What do you think?
>
> Regards, Benoit
>
>
>
> -------- Forwarded Message --------
>
> *Subject: *
>
> 	
>
> [Technical Errata Reported] RFC4006 (4892)
>
> *Date: *
>
> 	
>
> Mon, 19 Dec 2016 01:14:57 -0800
>
> *From: *
>
> 	
>
> RFC Errata System <rfc-editor@rfc-editor.org> 
> <mailto:rfc-editor@rfc-editor.org>
>
> *To: *
>
> 	
>
> Harri.Hakala@ericsson.com <mailto:Harri.Hakala@ericsson.com>, 
> Leena.Mattila@ericsson.com <mailto:Leena.Mattila@ericsson.com>, 
> juha-pekka.koskinen@nokia.com <mailto:juha-pekka.koskinen@nokia.com>, 
> marco.stura@nokia.com <mailto:marco.stura@nokia.com>, 
> John.Loughney@nokia.com <mailto:John.Loughney@nokia.com>, 
> bclaise@cisco.com <mailto:bclaise@cisco.com>, joelja@bogus.com 
> <mailto:joelja@bogus.com>, Bernard_Aboba@hotmail.com 
> <mailto:Bernard_Aboba@hotmail.com>, david@mitton.com 
> <mailto:david@mitton.com>, john.loughney@nokia.com 
> <mailto:john.loughney@nokia.com>
>
> *CC: *
>
> 	
>
> dengzhenjie@huawei.com <mailto:dengzhenjie@huawei.com>, 
> rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>
>
> The following errata report has been submitted for RFC4006,
> "Diameter Credit-Control Application".
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=4006&eid=4892
> --------------------------------------
> Type: Technical
> Reported by: dengzhenjie<dengzhenjie@huawei.com> <mailto:dengzhenjie@huawei.com>
> Section: 7
> Original Text
> -------------
>     | PendingU | CC update answer received     | Terminate   | Idle     |
>     |          | with result code equal to     | end user's  |          |
>     |          | CREDIT_CONTROL_NOT_APPLICABLE | service     |          |
> Corrected Text
> --------------
>     | PendingU | CC update answer received     | Grant     |   Idle   |
>     |          | with result code equal to     | service to|          |
>     |          | CREDIT_CONTROL_NOT_APPLICABLE | end user  |          |
> Notes
> -----
> Note that in Section 9, It said:
>    when the result code in the CCA is DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE 4011, it indicates that the credit-control server determines that the service can be granted to the end user but that no further credit-control is needed for the service (e.g., service is free of charge).
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
> --------------------------------------
> RFC4006 (draft-ietf-aaa-diameter-cc-06)
> --------------------------------------
> Title               : Diameter Credit-Control Application
> Publication Date    : August 2005
> Author(s)           : H. Hakala, L. Mattila, J-P. Koskinen, M. Stura, J. Loughney
> Category            : PROPOSED STANDARD
> Source              : Authentication, Authorization and Accounting
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
> .
> _________________________________________________________________________________________________________________________
>
> 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.