Re: [Dime] regarding test case in interop doc for same host on both sides

[Himanshu Bahl <himanshu.bahl at aricent.com>]

Hi victor,

I don`t think option 3 will be such
a good one. As the peer might resend the request in case of silent discard.

I think the most viable solution would
be either returning UNKNOW_HOST. UNABLE TO COMPLY also seems a good solution
since the receiving node is in fact in really unable to process the request
because the peer`s Identity has turned out to be same.

Regarding the test case document I think
this case is already present in the document. draft-fajardo-dime-interop-test-suite-01
in section 3.1.1.2 , point 3.


Sincerely,
Himanshu.

Know Me

http://www.aricent.com

Victor Fajardo <vfajardo at tari.toshiba.com>

12/12/2006 10:33 PM

To	himanshu bahl <hbahl52 at yahoo.com>
cc	dime at ietf.org, "'Tschofenig, Hannes'" <hannes.tschofenig at siemens.com>
Subject	Re: [Dime] regarding test case in interop doc for same host on         bothsides

Hi,

Sorry for the late reply.
> hi all,
> I have asked this before also.
> please clarify me on this one. suppose we get the same
> host id on both sides . i.e on both peers we have
> host1.x.com for example.
> then what kind of processing are we supposed to do ?
>
> 1. will there be election lost hence an error code of
> 4003 ( Election lost) be returned on both sides.?
>
> 2. Will there be an error returned with code 5012 
> (unable to comply ) ?
>
> 3. will the message be silently be discarded with no
> answer messages and connection will be torn down ?
>   
Obviously this scenario is a mis-configuration. Are you proposing to add
this to the test document ?

In general, I would prefer option (3) just to maintain interoperability.
Also, election is independent of this scenario and your implementation
can always check for this case and revert to (3) instead of going ahead
with the election.

regards,
victor

> a fast reply will be help full.
>
> Sincerely,
> Himanshu.
> http://thebahls.blogspot.com
>
>
>
> --- Tony Zhang <zhangtao_hw at huawei.com> wrote:
>
>   
>> Hi All
>>        I suggest add test cases:
>>       (1)Use DWR/DWA detect connection status.
>>       (2)Routing based on
>> longest-match-from-the-right on the realm      
>> rather than requiring an exact match.      
>>       (3)For Redirect,the loop maybe happen, should
>> test it?
>>       (4)Routing should test default route entry?
>>       (5)For connection ,should test more Negative
>> test?like no response.no CER etc?
>> Thanks!
>> Tony
>>
>> -----Original Message-----
>> From: Tschofenig, Hannes
>> [mailto:hannes.tschofenig at siemens.com] 
>> Sent: Wednesday, December 06, 2006 12:03 AM
>> To: Tom-PT Taylor; Hannes Tschofenig
>> Cc: dime at ietf.org
>> Subject: AW: [Dime] Re: Input for Diameter Test
>> Cases
>>
>> Thanks Tom. 
>>
>> We are looking forward to inspect the input. 
>>
>> In the meanwhile we need to work on the test cases.
>> Would you like to give us some feedback? Here is the
>> current draft version: 
>>
>>     
> http://www.opendiameter.org/public/draft-fajardo-dime-interop-test-suite-02.txt
>   
>> I have created a Wiki page to collect information. 
>>
>> Ciao
>> Hannes 
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Tom-PT Taylor [mailto:taylor at nortel.com] 
>> Gesendet: Dienstag, 5. Dezember 2006 16:59
>> An: Hannes Tschofenig
>> Cc: dime at ietf.org
>> Betreff: [Dime] Re: Input for Diameter Test Cases
>>
>> The MultiService Forum (MSF) is working through
>> their liaison process. 
>> We should have the material to you in two to three
>> weeks.
>>
>> Hannes Tschofenig wrote:
>>     
>>> Hi Tom,
>>>
>>> during the DIME meeting you mentioned that you
>>>       
>> could provide us with 
>>     
>>> some test cases (collected from another interop
>>>       
>> event).
>>     
>>> Ciao
>>> Hannes
>>>
>>>       
>> _______________________________________________
>> DiME mailing list
>> DiME at ietf.org
>> https://www1.ietf.org/mailman/listinfo/dime
>>
>> _______________________________________________
>> DiME mailing list
>> DiME at ietf.org
>> https://www1.ietf.org/mailman/listinfo/dime
>>
>>
>>
>> _______________________________________________
>> DiME mailing list
>> DiME at ietf.org
>> https://www1.ietf.org/mailman/listinfo/dime
>>
>>     
>
>
>
>  
> ____________________________________________________________________________________
> Any questions? Get answers on any topic at www.Answers.yahoo.com.
 Try it now.
>
> _______________________________________________
> DiME mailing list
> DiME at ietf.org
> https://www1.ietf.org/mailman/listinfo/dime
>
>
>   


_______________________________________________
DiME mailing list
DiME at ietf.org
https://www1.ietf.org/mailman/listinfo/dime




***********************  Aricent-Private   ***********************

"DISCLAIMER: This message is proprietary to Aricent  and is intended solely for the use of 
the individual to whom it is addressed. It may contain privileged or confidential information and should not be 
circulated or used for any purpose other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for 
loss or damage arising from the use of the information transmitted by this email including damage from virus."

_______________________________________________
DiME mailing list
DiME at ietf.org
https://www1.ietf.org/mailman/listinfo/dime