Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1956 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1956.

Report 1956 Actions

    Problem Report Number 1956
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0983
    Raised 1996-10-10 08:00
    Updated 2003-03-13 08:00
    Published 1996-11-11 08:00
    Product Standard Transport Service XTI
    Certification Program The Open Brand certification program
    Test Suite VST version 4.1.3
    Test Identification XTI.os/cots/accept 22
    Problem Summary TSDT4.021 The test is supposed to work as follows: SLAVE MASTER t_conrq() > T_CONNECT event t_listen() t_disrq() > T_DISCONNECT event t_accept() ==> TLOOK This test sequence works perfectly for transport provid...
    Problem Text
    The test is supposed to work as follows:
    SLAVE MASTER

    t_conrq() ----> T_CONNECT event
    t_listen()
    t_disrq() ----> T_DISCONNECT event
    t_accept() ==> TLOOK


    This test sequence works perfectly for transport providers different from
    ISO class 2.
    In case of ISO cl.2 the test sequence looks a bit different:
    SLAVE MASTER

    t_conrq() ----> T_CONNECT event
    t_listen()
    t_disrq()
    (NOT TRANSMITTED BUT
    STORED LOCALLY) t_accept() ==> T_OK

    For ISO cl.2 the t_disrq() won't be transmitted as long as the connection
    request is still "pending" (i.e. neither confirmed nor rejected) but is
    stored locally. As a consequence, the T_DISCONNECT event does not occur
    on master side causing the t_accept() call to complete successfully.
    Acc. to ISO 8073, a connection request leads to state WFCC; a
    subsequent disconnect request changes the state to WBCL without further
    action (see IS 8073, Appendix A, table 15 for details).
    We think this test is simply not applicable for an ISO cl.2 transport provider.
    Test Output
    /tset/XTI.os/cots/accept/T.accept 22 Unresolved
    Test Description:
    If the implementation supports a connection-oriented transport service:
    When a T_DISCONNECT event that requires immediate attention has
    occurred on fd, then t_accept() returns (int)-1, sets t_errno to
    TLOOK and the states of the endpoints fd and resfd are not changed.

    Test Information:
    NO EVENT occurred on ISO CLASS 2 endpoint instead of expected
    T_DISCONNECT event

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    This looks like a grey area in the specification. It is not clear what
    happens when t_snddis() is called on an endpoint in the T_OUTCON state.
    The description of t_snddis() says it is "used to initiate an abortive
    release on an already established connection, or to reject a connect
    request." It does not mention using it to cancel an outgoing connect
    request. However T_OUTCON is listed under "VALID STATES" on the t_snddis()
    page, and the state tables show that t_snddis() causes a transition from
    T_OUTCON to T_IDLE. If its use in the T_OUTCON state works differently
    for different transport providers, then the behaviour for each provider
    should be described in the relevant appendix.

    The XNET specification does not include any statement that suggests that
    different ISO CLASS transports should deal with a T_DISCONNECT event in
    a manner different from that specified in the test case description above.
    This may be an oversight in the specification, but the test suite seems to
    correctly implement the specification and it is recommended that this request
    is forwarded to the XNET group for consideration as a grey area in the
    specification.

    Review Type Expert Group Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    The concensus in XoTGnet is that the test in question should not be carried
    out for ISO Transport Class 2 because the action taken in the slave system
    does not have the effect of generating the precondition for the test in
    the system under test.

    There is a grey area in the specification regarding the generation of a
    protocol disconnect, but this applies to the slave system not the system
    under test.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion
    This is an agreed Test Suite Deficiency.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority