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

<lionel.morand@orange.com> Tue, 03 January 2017 10:22 UTC

Return-Path: <lionel.morand@orange.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 5FAD1129500; Tue, 3 Jan 2017 02:22:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level:
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[BAD_CREDIT=2.415, BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 9p0Hjn3BGQJe; Tue, 3 Jan 2017 02:22:28 -0800 (PST)
Received: from relais-inet.orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C1CB129434; Tue, 3 Jan 2017 02:22:27 -0800 (PST)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 51DE01C0C00; Tue, 3 Jan 2017 11:22:26 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.57]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id 2F30360064; Tue, 3 Jan 2017 11:22:26 +0100 (CET)
Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILM23.corporate.adroot.infra.ftgroup ([fe80::787e:db0c:23c4:71b3%19]) with mapi id 14.03.0319.002; Tue, 3 Jan 2017 11:22:25 +0100
From: lionel.morand@orange.com
To: Benoit Claise <bclaise@cisco.com>, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>, "sec-ads@ietf.org" <sec-ads@ietf.org>
Thread-Topic: [AAA-DOCTORS] Fwd: [Technical Errata Reported] RFC4006 (4892)
Thread-Index: AQHSWeL84EnpJ9EndkmU6ufRj5ZM+aEmof+w
Date: Tue, 03 Jan 2017 10:22:25 +0000
Message-ID: <784_1483438946_586B7B62_784_1775_1_6B7134B31289DC4FAF731D844122B36E0BFC5C89@OPEXCLILM43.corporate.adroot.infra.ftgroup>
References: <20161219091457.EF44BB80224@rfc-editor.org> <c046a2ac-a008-012e-4ad0-405066c26063@cisco.com>
In-Reply-To: <c046a2ac-a008-012e-4ad0-405066c26063@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_6B7134B31289DC4FAF731D844122B36E0BFC5C89OPEXCLILM43corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/aaa-doctors/6RPB-P7kjl67RHuxatHLwRpUebI>
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 10:22:30 -0000

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.