Re: [AAA-DOCTORS] [Technical Errata Reported] RFC6733 (4931)

[Jouni <[e-mail]>]

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 <[e-mail]> 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 <[e-mail]>
> To:	[e-mail], [e-mail], [e-mail], [e-mail], [e-mail], [e-mail], [e-mail], [e-mail]
> CC:	[e-mail], [e-mail], text/[e-mail], charset=[e-mail]
> 
> 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 
> <[e-mail]>
> 
> 
> 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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/aaa-doctors