[erlang-questions] Relay is adding Route-Record of client instead of self

Arshad Ansari <>
Wed Aug 10 20:38:05 CEST 2016


I'm sorry about misunderstanding the role of route record avp. I was
corrected by my collegue on this regard and I forgot to close this chain/
Thanks for the reply


On Wed, Aug 10, 2016 at 3:46 PM Anders Svensson <>
wrote:

> Oops, missed my CC to the list. You can reply there if you prefer. /Anders
>
>
> On Wed, Aug 10, 2016 at 12:11 PM, Anders Svensson <>
> wrote:
> > Hi Arshad.
> >
> > Where are you reading this? I see this in both RFC 3588 (6.1.8) and
> > RFC6733 (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.
> >
> > Anders
> >
> >
> >
> > On Tue, Aug 9, 2016 at 2:24 PM, Arshad Ansari <>
> wrote:
> >> Hello there,
> >>
> >> I have found that when relay forwards the request to the server that it
> >> receives from the client, it adds Route-Record with value of client's
> >> Origin-Host. However, RFC 3588 says that the route-record must be
> relay's
> >> own Origin-Host value that is shared with Server during CER. Can anyone
> shed
> >> light as to why the default behavior of Erlang-Diameter module is not in
> >> sync with the RFC? Also, how can I modify the said AVP in
> prepare_request
> >> method of relay_callback module?
> >>
> >> May be I'm misreading the specs, however; I would really appreciate if
> >> someone can clarify it a bit for me.
> >>
> >> Regards,
> >> Arshad Ansari
> >>
> >> _______________________________________________
> >> erlang-questions mailing list
> >> 
> >> http://erlang.org/mailman/listinfo/erlang-questions
> >>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160810/0b3181a9/attachment.html>


More information about the erlang-questions mailing list