Re: [Dime] [Technical Errata Reported] RFC7683 (4549)

<lionel.morand@orange.com> Tue, 17 May 2016 10:05 UTC

Return-Path: <lionel.morand@orange.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 50A9212B05D for <dime@ietfa.amsl.com>; Tue, 17 May 2016 03:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.345
X-Spam-Level:
X-Spam-Status: No, score=-3.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, 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 Ee6x0Wk1qlvM for <dime@ietfa.amsl.com>; Tue, 17 May 2016 03:05:40 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D4F012B030 for <dime@ietf.org>; Tue, 17 May 2016 03:05:40 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 77E53C08D5; Tue, 17 May 2016 12:05:38 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.27]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 196101A005E; Tue, 17 May 2016 12:05:38 +0200 (CEST)
Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILM7C.corporate.adroot.infra.ftgroup ([fe80::8007:17b:c3b4:d68b%19]) with mapi id 14.03.0294.000; Tue, 17 May 2016 12:05:37 +0200
From: <lionel.morand@orange.com>
To: Benoit Claise <bclaise@cisco.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "jouni.nospam@gmail.com" <jouni.nospam@gmail.com>, "srdonovan@usdonovans.com" <srdonovan@usdonovans.com>, "ben@nostrum.com" <ben@nostrum.com>, "joelja@bogus.com" <joelja@bogus.com>
Thread-Topic: [Technical Errata Reported] RFC7683 (4549)
Thread-Index: AQHRsBXwo+Ag62eyc0qNLHaJgF0B9Z+85g1Q
Date: Tue, 17 May 2016 10:05:37 +0000
Message-ID: <22162_1463479538_573AECF2_22162_1631_1_6B7134B31289DC4FAF731D844122B36E01E66E22@OPEXCLILM43.corporate.adroot.infra.ftgroup>
References: <20151201175847.12786181B3D@rfc-editor.org> <24274_1449136067_56600FC3_24274_506_1_6B7134B31289DC4FAF731D844122B36E01D7CF60@OPEXCLILM43.corporate.adroot.infra.ftgroup> <573AD5EA.6050108@cisco.com>
In-Reply-To: <573AD5EA.6050108@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.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/txVLJ4lulaT3F6sQ7RzpO30iWow>
X-Mailman-Approved-At: Tue, 17 May 2016 03:06:38 -0700
Cc: "jkayser@netnumber.com" <jkayser@netnumber.com>, "dime@ietf.org" <dime@ietf.org>
Subject: Re: [Dime] [Technical Errata Reported] RFC7683 (4549)
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: Tue, 17 May 2016 10:05:44 -0000

Hi Benoit,

I think that the note could just say: 

"When the overload report is of type "REALM_REPORT", the overloaded realm is identified by the Origin-Realm AVP of the Diameter command i.e. the realm of the originator of the Diameter command with the overload report."

Is it OK for you, Jan?

Regards,

Lionel

> -----Message d'origine-----
> De : Benoit Claise [mailto:bclaise@cisco.com]
> Envoyé : mardi 17 mai 2016 10:27
> À : MORAND Lionel IMT/OLN; RFC Errata System; jouni.nospam@gmail.com;
> srdonovan@usdonovans.com; ben@nostrum.com; joelja@bogus.com
> Cc : jkayser@netnumber.com; dime@ietf.org; Kathleen Moriarty; Stephen
> Farrell
> Objet : Re: [Technical Errata Reported] RFC7683 (4549)
> 
> Dear all,
> 
> Can someone update the justification, so that this errata can be verified.
> Alternatively, send me the correct justification text.
> 
> Regards, B.
> > The errata is correct but not the justification. The overloaded realm is
> obviously the one identified as source of the command, whatever the type
> (request or answer). So it must be the Origin-Realm of the command.
> >
> > Regards,
> >
> > Lionel
> >
> > -----Message d'origine-----
> > De : RFC Errata System [mailto:rfc-editor@rfc-editor.org]
> > Envoyé : mardi 1 décembre 2015 18:59
> > À : jouni.nospam@gmail.com; srdonovan@usdonovans.com;
> ben@nostrum.com;
> > MORAND Lionel IMT/OLN; bclaise@cisco.com; joelja@bogus.com;
> > jouni.nospam@gmail.com; MORAND Lionel IMT/OLN Cc :
> > jkayser@netnumber.com; dime@ietf.org; rfc-editor@rfc-editor.org Objet
> > : [Technical Errata Reported] RFC7683 (4549)
> >
> > The following errata report has been submitted for RFC7683, "Diameter
> Overload Indication Conveyance".
> >
> > --------------------------------------
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata_search.php?rfc=7683&eid=4549
> >
> > --------------------------------------
> > Type: Technical
> > Reported by: Jan Kayser <jkayser@netnumber.com>
> >
> > Section: 4.3
> >
> > Original Text
> > -------------
> > The overloaded realm is identified by the Destination-Realm AVP of the
> message containing the OLR.
> >
> > Corrected Text
> > --------------
> > The overloaded realm is identified by the Origin-Realm AVP of the message
> containing the OLR.
> >
> > Notes
> > -----
> > OLRs (OC-OLR AVPs) are sent exclusively in answer messages and not in
> requests. Therefore, the OLR message (answer) does not include a
> Destination-Realm AVP, but only a Origin-Realm AVP.
> >
> > 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 (IESG) can log in to change the status
> and edit the report, if necessary.
> >
> > --------------------------------------
> > RFC7683 (draft-ietf-dime-ovli-10)
> > --------------------------------------
> > Title               : Diameter Overload Indication Conveyance
> > Publication Date    : October 2015
> > Author(s)           : J. Korhonen, Ed., S. Donovan, Ed., B. Campbell, L. Morand
> > Category            : PROPOSED STANDARD
> > Source              : Diameter Maintenance and Extensions
> > 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, France Telecom - 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 authorization.
> > If you have received this email in error, please notify the sender and delete
> this message and its attachments.
> > As emails may be altered, France Telecom - Orange shall not be liable if this
> message was modified, changed or falsified.
> > Thank you.
> >
> > .
> >


_________________________________________________________________________________________________________________________

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.