[Dime] Diameter request routing clarification needed

Iliya Peregoudov <iperegudov@cboss.ru> Wed, 04 June 2014 10:39 UTC

Message-ID: <538EF73F.3070309@cboss.ru>
Date: Wed, 04 Jun 2014 14:38:55 +0400
From: Iliya Peregoudov <iperegudov@cboss.ru>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20131118 Thunderbird/17.0.11
MIME-Version: 1.0
To: dime@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/ZRi57e7P7f8cLby5A1TyhIkTvMc
Subject: [Dime] Diameter request routing clarification needed
Precedence: list

Hello all,

I need clarification about Diameter request routing.
Consider the use-case:

host: pcef, realm: example.com
   |      A
   |CCR   |RAR
   V      |
host: relay, realm: example.com
   |      A
   |CCR   |RAR
   V      |
host: ocs, realm: example.com

RFC6733 says that request routing should be controlled by routing table.

Host `ocs' has to consume CCR requests to realm example.com of 
application 4, so it should have route

   (example.com, 4) -> (LOCAL)

Host `ocs' also has to send locally generated RAR requests to realm 
example.com of application 4, so it should have route

   (example.com, 4) -> (RELAY, relay)

How `ocs' host should operate to select correct route?

Does it mean that Diameter host should maintain two routing tables, one 
for handling of incoming requests, and one another for handling locally 
generated requests?

Thank you in advance.

Iliya Peregoudov
Software engineer, CBOSS Group

[Dime] Diameter request routing clarification nee… Iliya Peregoudov