Re: [Dime] Application-id reuse

["Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig at nsn.com>]

Hi Jacob, 

Your question addresses different aspects, namely

* How does Diameter routing work in general?  

This is described in Section 6.1 and Section 6.2 of 
http://www.ietf.org/internet-drafts/draft-ietf-dime-rfc3588bis-12.txt

This should give you an idea how the right node is found and how messages travel back and forth. 

* How does Diameter routing work with a Diameter application like Wm?

This very much depends on how the protocol designers of Wm want it to work. I have to read Wm again to recall the details but based on what you describe it seems that the protocol designers of Wm did not want to create a new Diameter application and hence the additionally specified AVPs are just optional extensions to Diameter EAP and Diameter NASREQ. As such, they should be routed to the respective EAP/NASREQ code and the optional AVPs are interpreted in case that they are understood. 

Ciao
Hannes

>-----Original Message-----
>From: dime-bounces at ietf.org [mailto:dime-bounces at ietf.org] On 
>Behalf Of ext Sebastien Decugis
>Sent: 09 September, 2008 14:02
>To: Jacob Martin
>Cc: dime at ietf.org
>Subject: Re: [Dime] Application-id reuse
>
>Hello,
>
>I think the Application Id in the command header will contain 
>the appropriate identifier to route the message to the correct 
>handler...
>
>Best regards,
>Sebastien.
>
>Jacob Martin a écrit :
>>
>> Hi,
>>  
>>     I am a bit confused about the feasibility of one specific 
>> configuration in Diameter.
>>  
>>     Please look at the diagram below:          
>>  
>>  
>>                                 |
>>                                 |
>>                                 |
>>                                 |     
>>    Local Node                   |
>>                                 |        +----+       +-------+
>>                                 |        |NAS |       |  Wm   |
>>     +--------+   +--------+     |        +----+       +-------+
>>     |        |   |        |     |            |            ---
>>     |NASREQ  |   |  Wm    |     |             |        ---
>>     +----\---+   +---/----+     |             +----- --
>>           \        //           |         ////      \\\\\
>>           \      //             |       |/               |
>>            \   //               |      |        PEER     |
>>         +---\-/------+          |      |                  |
>>         |            |          |       |\               |
>>         |Diameter    |          |         \\\\      /////
>>         |Base process|          |             ------
>>         +----+-------+          |             |
>>              |                  |             |
>>              |                  |             |
>>              +------------------+-------------+
>>                                
>>    I wish to provide support for two applications on my 
>local node i.e 
>> NASREQ and Wm. As per Wm specifications, Wm should reuse the 
>> application identifier of EAP/NASREQ. So, in CEA, I have advertised 
>> '1' and '5' as the applications supported.
>>  
>>    Assume that peer node also has the same configuration as of mine 
>> i.e it also support Wm and NAS applications.
>>  
>>   Now, peer Wm application issues an AAR. After receiving this AAR, 
>> how could my Diameter base process determine that this AAR is for 
>> local Wm application, but not for local NASREQ application?
>>  
>>
>>   Thanks in anticipation,
>>   Martin                             
>>                                
>>                                
>>
>> 
>----------------------------------------------------------------------
>> --
>>
>> _______________________________________________
>> DiME mailing list
>> DiME at ietf.org
>> https://www.ietf.org/mailman/listinfo/dime
>>   
>
>--
>Sebastien Decugis
>Research fellow
>Network Architecture Group
>NICT (nict.go.jp)
>
>_______________________________________________
>DiME mailing list
>DiME at ietf.org
>https://www.ietf.org/mailman/listinfo/dime
>
_______________________________________________
DiME mailing list
DiME at ietf.org
https://www.ietf.org/mailman/listinfo/dime