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

Benoit Claise <bclaise@cisco.com> Tue, 17 May 2016 08:27 UTC

Return-Path: <bclaise@cisco.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 ED78112B048 for <dime@ietfa.amsl.com>; Tue, 17 May 2016 01:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level:
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, 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 xbCeMXtkvlbc for <dime@ietfa.amsl.com>; Tue, 17 May 2016 01:27:26 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A808812B041 for <dime@ietf.org>; Tue, 17 May 2016 01:27:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3624; q=dns/txt; s=iport; t=1463473645; x=1464683245; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=8kEAdLSVTXK1OmzJZmva+SxUzP96u5og52akW1si6zY=; b=OEocDtM9Df3bs6Wrp8BDLLoA8X4boinMCCY23Ar80JcJaOM8N/tgvc5l XBbOStFsaqeGCWDuac1RsWYVvtn6X4R2a4pzM2ybnXmZyLwYoBiogQFnp nbg8cRTyj/uIMHQJcHytjqR0x6AG5hGlReblxnP5pgfXyMh6EUsK1Kq9R k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CsBABm1TpX/xbLJq1DGoQMfq4PjWoih?= =?us-ascii?q?W8CggABAQEBAQFmJ4RDAQEEMgEFQAEQCyEWCAcJAwIBAgEPJREGAQwGAgEBiBE?= =?us-ascii?q?DFw4svigNhCcBAQEBAQEBAQEBAQEBAQEBAQEBAQEchiWETYE5gQqBThEBhXUBB?= =?us-ascii?q?Id+CocJiGcxjCaBeYFphE+DB4Vahi6BL4dlYoIGDQ6BTToyAROGPYE1AQEB?=
X-IronPort-AV: E=Sophos;i="5.26,324,1459814400"; d="scan'208";a="637502816"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 May 2016 08:27:23 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u4H8RMfM010457; Tue, 17 May 2016 08:27:22 GMT
To: lionel.morand@orange.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>
References: <20151201175847.12786181B3D@rfc-editor.org> <24274_1449136067_56600FC3_24274_506_1_6B7134B31289DC4FAF731D844122B36E01D7CF60@OPEXCLILM43.corporate.adroot.infra.ftgroup>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <573AD5EA.6050108@cisco.com>
Date: Tue, 17 May 2016 10:27:22 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <24274_1449136067_56600FC3_24274_506_1_6B7134B31289DC4FAF731D844122B36E01D7CF60@OPEXCLILM43.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/EjvZBosSlKHyC6PG6LQ-EBYpdQE>
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 08:27:28 -0000

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