Re: [Dime] [Technical Errata Reported] RFC6733 (4615)

Jouni Korhonen <jouni.nospam@gmail.com> Fri, 05 February 2016 21:48 UTC

Return-Path: <jouni.nospam@gmail.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF1B1B2D02 for <dime@ietfa.amsl.com>; Fri, 5 Feb 2016 13:48:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 OLSN8WQRmtE8 for <dime@ietfa.amsl.com>; Fri, 5 Feb 2016 13:48:33 -0800 (PST)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (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 0BC401AC438 for <dime@ietf.org>; Fri, 5 Feb 2016 13:48:33 -0800 (PST)
Received: by mail-pf0-x22a.google.com with SMTP id n128so74720097pfn.3 for <dime@ietf.org>; Fri, 05 Feb 2016 13:48:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=K4amtTi6jWtc/nLiCoxIeQoTvxfDu1MD+BvSjFf1Jgs=; b=MOcqVnAYFh2x7KnpxoZh9CEUiVt6W3zR+xf76rkkuXL9u5TVNMhcbc+X8s4Q+EG515 ViOrPitkQgE7Pukk8ML7L3dcVHVw0mVmvraKcPxREAihWUTP9WovMGw/e0YDsUUxejgC SVfTrC5IrTbrC6wABberbLXMutrnBKA4/Xms1e4ucUdbFLlCYxPffkIMOSmcj+WPGGmD l1T+RF+SNpX9oCaNnspR/BKi5LcYHb0LVbKXoNtJxGYSpZydEfgCceY836KUIEBHYuRq s7fNG32wVfRUFnDDd7a5dcyjUPGzcn34Ef5GuSTeNaadoVvUc6qsBd1BFrDxod8wes1D 0Vbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=K4amtTi6jWtc/nLiCoxIeQoTvxfDu1MD+BvSjFf1Jgs=; b=KKbVSzrlRaRdJNcuReVn1l/vhP0cFlvszhWvC3eP0DybAE1qzkilViGigEqCDRJMuj oCOOelVc13bo112QhmYzLyD+5vXw5X+SBlS75uRbkqfXV8LBW7DuukQh3t1ElVXoY6qn jl1+vP0xm7Vtg49ZU0e0dZ3Qf7PksCcHUjKsJqKF8bWSkTgRplEKawXh+3nCGKzrKqnk T/zKEd9FrmIL/PbzUhcSJ0mXZlXNUi9ZgPq2g7EIPCrPbdt3ei4MAONlBtSD/IxOqJh6 Nkq/gZzjxomuGMQeUuvi9LcB06RNad5Hqgney2SQ5dbjtFy9gZiVFWSVRczEFI4B2vh8 50WQ==
X-Gm-Message-State: AG10YOSomtHNN1IgtRAm5WNa6P3Xsz/iT66ykxBDYT5uIezXIfOTxa72yqz7vt4b9HFhXQ==
X-Received: by 10.98.18.15 with SMTP id a15mr23298670pfj.145.1454708912669; Fri, 05 Feb 2016 13:48:32 -0800 (PST)
Received: from [10.16.86.70] ([216.31.219.19]) by smtp.googlemail.com with ESMTPSA id l14sm26560259pfb.73.2016.02.05.13.48.30 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Feb 2016 13:48:32 -0800 (PST)
To: RFC Errata System <rfc-editor@rfc-editor.org>, vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, glenzorn@gmail.com, bclaise@cisco.com, joelja@bogus.com, lionel.morand@orange.com
References: <20160205185440.F3B23180208@rfc-editor.org>
From: Jouni Korhonen <jouni.nospam@gmail.com>
Message-ID: <56B518AC.8010104@gmail.com>
Date: Fri, 05 Feb 2016 13:48:28 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160205185440.F3B23180208@rfc-editor.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/Fljo9HNfJxm0H5cLmfGCVLNKI3A>
Cc: dime@ietf.org
Subject: Re: [Dime] [Technical Errata Reported] RFC6733 (4615)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 05 Feb 2016 21:48:35 -0000

I think this errata is correct.

- Jouni


2/5/2016, 10:54 AM, RFC Errata System kirjoitti:
> The following errata report has been submitted for RFC6733,
> "Diameter Base Protocol".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6733&eid=4615
>
> --------------------------------------
> Type: Technical
> Reported by: Lionel Morand <lionel.morand@orange.com>
>
> Section: 7.1.5
>
> Original Text
> -------------
>     DIAMETER_AVP_UNSUPPORTED 5001
>
>        The peer received a message that contained an AVP that is not
>        recognized or supported and was marked with the 'M' (Mandatory)
>        bit.  A Diameter message with this error MUST contain one or more
>        Failed-AVP AVPs containing the AVPs that caused the failure.
>
> Corrected Text
> --------------
>     DIAMETER_AVP_UNSUPPORTED 5001
>
>        The peer received a message that contained an AVP that is not
>        recognized or supported and was marked with the 'M' (Mandatory)
>        bit.  A Diameter message with this error MUST contain one
>        Failed-AVP AVP containing the AVPs that caused the failure.
>
> Notes
> -----
> The RFC6733 has clarified that only one instance of Failed-AVP AVP can be present in the command answer. One Failed-AVP AVP is enough because this AVP is defined as Grouped AVP that can contain multiple AVPs. In the present case, each of the nested AVPs in the Failed-AVP AVP are the AVPs that caused the failure.
>
> 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.
>
> --------------------------------------
> RFC6733 (draft-ietf-dime-rfc3588bis-33)
> --------------------------------------
> Title               : Diameter Base Protocol
> Publication Date    : October 2012
> Author(s)           : V. Fajardo, Ed., J. Arkko, J. Loughney, G. Zorn, Ed.
> Category            : PROPOSED STANDARD
> Source              : Diameter Maintenance and Extensions
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
>