r9 - 09 Feb 2007 - 16:31:14 - VictorFajardoYou are here: TWiki >  Dime Web  >  DiameterInterop2007 > ToshibaTests

Toshiba Tests: Open Diameter

Role: Server (EAP, NASREQ) and Relay

Legend

  • (ST) Successful tests
  • (NT) Not tested (but implemented)
  • (NI) Not implemented

Diameter Base Protocol Test Suite

Test Case Result Test Partners
3.1.1.1. Capabilities Negotiation ST 5
3.1.1.2. Election NT  
3.1.1.3. Disconnection NT  
3.1.1.4. Re-Connection Algorithms ST 5
3.1.1.5. Failover and Failback NT  
3.1.2.1. Peer Based Request Routing ST 5
3.1.2.2. Realm Based Routing ST 5
3.1.2.3. Answer Message Routing ST 5
3.1.2.4. Loop Detection NT  
3.1.3. Relay Agent ST 5
3.1.4. Redirection NT  
3.2.1. General Statemachine ST 5
3.2.2. Dynamic Peer Discovery NI  
Duplicate Detection Test NI

Test Case Result Test Partners
TLS NI  
SCTP ST 1

Diameter EAP Test Suite

Test Case Result Test Partners
4.5.1.1. Non-Roaming case NT  
4.5.1.2. Roaming scenario NT  
4.5.2. Optional Tests NT  

Diameter NASREQ Test Suite

Test Case Result Test Partners
4.6.1.1. Auth Session ST 1
4.6.1.2. Diameter/RADIUS Gateway NI  
4.6.1.3. Multi-domain Scenario NT  
4.6.2.1. Auth Session NT  

Diameter MIP Test Suite

Test Case Result Test Partners
4.7.1. Generic MIP Test Scenarios NT  
4.7.2.1. Co-located Registration NT  
4.7.2.2. Intra-Domain Registration NT  
4.7.2.3. Inter-Domain Registration NT  
4.7.2.4. Allocation of HA in Foreign Network NT  
4.7.3.1. Co-located Registration (optional features) NT  
4.7.3.2. Inter-Domain Registration with Redirect NT  
4.7.3.3. Inter-Domain Registration with Proxy/Relay NT  

Day 1 Testing: Jan 29, 2007

  • Completed basic capabilities request/answer exchange from multiple participants
  • Started testing with relaying functionality
  • Areas of General discussion
    1. Significance/Usage/Relevance of Vendor-Id
    2. Mixture of Auth and Acct app id in the VSA Some usage maybe useful for 3GPP but assumptions maybe broken
    3. We need to update the NAI references in the base
    4. We need to test Redirect behavior
    5. Election clarification when it comes to lex results and reverse winning

Day2 Testing: Jan 30, 2007

  • Attempted to accomplish the setup failover test topology with majority of the participants (diagram below)
  • Misc. Test performed with other participants in parallel
    1. SCTP Test
    2. Diameter EAP Test

Diameter Routing Topology

dime-interop-topology.JPG


Day3 Testing: Jan 31, 2007

  • Continued with tests from the faiover topology in day2
  • The following are test results (see topology above):

FAILOVER Result
125->112->128, 134 (Failover node) Success
125->112->128, 111 (Failover node) Not Tested
125->112, 111 (Failover node) Not Tested
125->111->128->116->113, 134 (Failover node) Not Tested
125->111->112, 128 (Failover node) Not Tested
113->116, 134 (Failover node) Not Tested
120->111->128,134->128 (Failover node) Success

  • Notes: Majority of the test scenario above was not performed because some implementations took certain assumptions on failover specifically:
    1. Some implementations are not performing request queuing when forwarding
    2. Some implementations made assumptions that failover is dependent on domains/realm names
    3. Some implementations made assumptions that failover is an active/backup relationship

LOOP DETECTION Result
125->112->128->134->116->128 Not Tested
113->116->128->134->116 Not Tested

  • Notes: All the test scenario above was not performed because of lack of time in setting up complex routing scenarios

-- DimeGroup - 29 Jan 2007

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r9 < r8 < r7 < r6 < r5 | More topic actions
 
Powered by TWiki
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback