Re: [AAA-DOCTORS] [Technical Errata Reported] RFC6733 (4931)
Benoit Claise <bclaise@cisco.com> Fri, 10 February 2017 07:52 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 563F612A04B for <aaa-doctors@ietfa.amsl.com>; Thu, 9 Feb 2017 23:52:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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=-0.001, SPF_HELO_PASS=-0.001, 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 o8Du5G2PF4YM for <aaa-doctors@ietfa.amsl.com>; Thu, 9 Feb 2017 23:52:34 -0800 (PST)
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 79B0412A047 for <aaa-doctors@ietf.org>; Thu, 9 Feb 2017 23:52:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8193; q=dns/txt; s=iport; t=1486713153; x=1487922753; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=GLYjkvaI4G9Ch8/xt0KR/NGTfohEcca1gLTe80tb6VU=; b=JZa72c595bK5beSMN2DUueGFcc6GJtEW6pG5rJU7CJ+uAyYRfo/aqE6c 78Y+ncSfuADuiT4Nobz03dwkFwWKp0ZPUuIZFyfknXE2fzyUGzqYbkAu1 RK6f5COdegAwdXjzchY5TI795yrHMsP7IrotxDZAaug0ID4POTpyGqlP1 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A3AgBEcJ1Y/xbLJq1DEQkZAQEBAQEBAQEBAQEHAQEBAQGEMwMnX41hcpB7H4I6hVKEc4g3gg0fC4V4AoMvGAECAQEBAQEBAWIohGkBAQEEAQElCwEFNgsQCxEDAQIBJwchBh8JCAYBDAYCAQGJXAMVDi2xDzqHPA2EDgEBAQEBAQEBAQEBAQEBAQEBAQEBAR2GTIIFCIJigTyBFUaBBAsHCgEGQoUaHwEEiQwRh2yES4VkOoZvhwwBhBiBe1OERIMthkaKNVuIBR84E2MIHxMIFRUYJIREDRCBYj81AROHOoItAQEB
X-IronPort-AV: E=Sophos;i="5.35,140,1484006400"; d="scan'208";a="652376989"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Feb 2017 07:52:31 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v1A7qUnp031130; Fri, 10 Feb 2017 07:52:30 GMT
To: lionel.morand@orange.com, Jouni <jouni.nospam@gmail.com>
References: <20170209025634.0538BB80107@rfc-editor.org> <2b129b48-9d8a-333c-1595-3671d43e45f1@cisco.com> <2D7E6B41-F065-478C-8C26-6A0DE98B0A62@gmail.com> <23724_1486686783_589D0A3F_23724_194_1_6B7134B31289DC4FAF731D844122B36E0C038C63@OPEXCLILM43.corporate.adroot.infra.ftgroup>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <88456c05-28d2-9062-e612-543b9c2bbbb3@cisco.com>
Date: Fri, 10 Feb 2017 08:52:26 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <23724_1486686783_589D0A3F_23724_194_1_6B7134B31289DC4FAF731D844122B36E0C038C63@OPEXCLILM43.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/aaa-doctors/lSkw-i6sEnMihwYp80hbq8U1o8Q>
Cc: "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>
Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC6733 (4931)
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: Fri, 10 Feb 2017 07:52:36 -0000
Thank you Lionel and Jouni. Regards, B. > The Route-Record is primarily used to detect loops: > > 6.1.3. Receiving Requests > > A relay or proxy agent MUST check for forwarding loops when receiving > requests. A loop is detected if the server finds its own identity in > a Route-Record AVP. When such an event occurs, the agent MUST answer > with the Result-Code AVP set to DIAMETER_LOOP_DETECTED. > > How to populate the Route-Record is described twice: > > Section 2.9: > > As noted in Section 6.1.9, a relay or proxy agent MUST append a > Route-Record AVP to all requests forwarded. The AVP contains the > identity of the peer from which the request was received. > > 6.7.1. Route-Record AVP > > The Route-Record AVP (AVP Code 282) is of type DiameterIdentity. The > identity added in this AVP MUST be the same as the one received in > the Origin-Host of the Capabilities Exchange message. > > Therefore the "rather clear" used by Jouni is almost an euphemism :) > > I think that Luis was maybe misled by the following text: > > 6.1.3. Receiving Requests > > A relay or proxy agent MUST check for forwarding loops when receiving > requests. A loop is detected if the server finds its own identity in > a Route-Record AVP. When such an event occurs, the agent MUST answer > with the Result-Code AVP set to DIAMETER_LOOP_DETECTED. > > in which "find its own identity" might have been confusing out of context. But sections 2.9 and 6.7.1 should have clarified this misunderstanding. > > Whatever the reason for the proposed errata, it can be safely rejected. > > Regards, > > Lionel > > >> -----Message d'origine----- >> De : AAA-DOCTORS [mailto:aaa-doctors-bounces@ietf.org] De la part de Jouni >> Envoyé : jeudi 9 février 2017 22:31 >> À : Benoit Claise >> Cc : aaa-doctors@ietf.org >> Objet : Re: [AAA-DOCTORS] [Technical Errata Reported] RFC6733 (4931) >> >> RFC6733 Sections 2.9 and 6.1.9 are rather clear that a relay and a proxy MUST >> append a Route-Record to all requests forwarded with the identity of the peer >> from which the request was received. There is no text that a relay or a proxy >> should add its own identity. If the agent were to add its own identity it would >> result duplicate entries of Route-Records if there are more than one agent on >> the path. Additionally an agent adding its own identity to a Route-Record seems >> to go against a MUST Section 6.7.1. >> >> This errata should be rejected. >> >> - Jouni >> >>> On 09 Feb 2017, at 01:52, Benoit Claise <bclaise@cisco.com> wrote: >>> >>> AAA doctors, >>> >>> What do you think of this errata? >>> >>> Regards, B. >>> >>> >>> -------- Forwarded Message -------- >>> Subject: [Technical Errata Reported] RFC6733 (4931) >>> Date: Wed, 8 Feb 2017 18:56:34 -0800 >>> From: RFC Errata System <rfc-editor@rfc-editor.org> >>> To: vf0213@gmail.com, jari.arkko@ericsson.com, >> john.loughney@nokia.com, glenzorn@gmail.com, bclaise@cisco.com, >> joelja@bogus.com, jouni.nospam@gmail.com, lionel.morand@orange.com >>> CC: luizsolis@hotmail.com, dime@ietf.org, text/plain@rfc-editor.org, >> charset=UTF-8@rfc-editor.org >>> 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=4931 >>> >>> >>> -------------------------------------- >>> Type: Technical >>> Reported by: Luiz Solis >>> <luizsolis@hotmail.com> >>> >>> >>> Section: 6.1.9 >>> >>> Original Text >>> ------------- >>> Figure 6.1 provides an example of message routing using the procedures >>> listed in these sections. >>> >>> (Origin-Host=nas.example.net) (Origin-Host=nas.example.net) >>> (Origin-Realm=example.net) (Origin-Realm=example.net) >>> (Destination-Realm=example.com) (Destination-Realm=example.com) >>> (Route-Record=nas.example.net) >>> >>> +------+ ------> +------+ ------> +------+ >>> | | (Request) | | (Request) | | >>> | NAS +-------------------+ DRL +-------------------+ HMS | >>> | | | | | | >>> +------+ <------ +------+ <------ +------+ >>> example.net (Answer) example.net (Answer) example.com >>> (Origin-Host=hms.example.com) (Origin-Host=hms.example.com) >>> (Origin-Realm=example.com) (Origin-Realm=example.com) >>> >>> Figure 6: Routing of Diameter messages >>> >>> Corrected Text >>> -------------- >>> Figure 6.1 provides an example of message routing using the procedures >>> listed in these sections. >>> >>> (Origin-Host=nas.example.net) (Origin-Host=nas.example.net) >>> (Origin-Realm=example.net) (Origin-Realm=example.net) >>> (Destination-Realm=example.com) (Destination-Realm=example.com) >>> (Route-Record=nas.example.net)* (Route-Record=nas.example.net) >>> (Route-Record=drl.example.net)* >>> +------+ ------> +------+ ------> +------+ >>> | | (Request) | | (Request) | | >>> | NAS +-------------------+ DRL +-------------------+ HMS | >>> | | | | | | >>> +------+ <------ +------+ <------ +------+ >>> example.net (Answer) example.net (Answer) example.com >>> (Origin-Host=hms.example.com) (Origin-Host=hms.example.com) >>> (Origin-Realm=example.com) (Origin-Realm=example.com) >>> >>> *Optional. >>> >>> Figure 6: Routing of Diameter messages >>> >>> Notes >>> ----- >>> The relay or proxy agent should append their own identity optionally in an >> additional Route-Record AVP (282). >>> 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. >>> >>> -------------------------------------- >>> 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 >>> . >>> >>> >>> _______________________________________________ >>> AAA-DOCTORS mailing list >>> AAA-DOCTORS@ietf.org >>> https://www.ietf.org/mailman/listinfo/aaa-doctors >> _______________________________________________ >> AAA-DOCTORS mailing list >> AAA-DOCTORS@ietf.org >> https://www.ietf.org/mailman/listinfo/aaa-doctors > _________________________________________________________________________________________________________________________ > > 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. > > . >
- [AAA-DOCTORS] Fwd: [Technical Errata Reported] RF… Benoit Claise
- Re: [AAA-DOCTORS] [Technical Errata Reported] RFC… Jouni
- Re: [AAA-DOCTORS] [Technical Errata Reported] RFC… lionel.morand
- Re: [AAA-DOCTORS] [Technical Errata Reported] RFC… Benoit Claise