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

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1981 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 1981.

Report 1981 Actions

    Problem Report Number 1981
    Submitter's Classification Minor System Fault
    State Resolved
    Resolution Minor System Fault (MSF)
    Problem Resolution ID MSF.X.0082
    Raised 1995-08-24 08:00
    Updated 2003-03-13 08:00
    Published 1995-09-08 08:00
    Expiry Date 1996-09-07
    Product Standard Transport Service XTI
    Certification Program The Open Brand certification program
    Test Suite VST version 4.1.3
    Test Identification XTI.os/common/T.sync 2
    Problem Summary MSFT4.001 Test cases affected are sync 2, sync 3, sync 4, and snd 19. We request that this implementation be allowed to pass as is, returning T_DATAXFER instead of T_OUTCON in these cases. The problem occurs wh...
    Problem Text
    Test cases affected are sync 2, sync 3, sync 4, and snd 19. We request
    that this implementation be allowed to pass as is, returning T_DATAXFER
    instead of T_OUTCON in these cases.

    The problem occurs when an asynchronous t_connect() is called, followed
    by a t_sync(). Since the connect confirmation can be received by the
    transport provider and passed to the XTI library before the t_sync() call
    occurs, t_sync() will return the state T_DATAXFER instead of T_OUTCON
    based on the transport provider state.

    While this is technically incorrect, it would be impossible for the
    transport provider in this case to determine whether or not the confirmation
    has been received by the application (this interface is STREAMS-based).
    Also, since the purpose of t_sync() is to synchronize with state of the
    transport provider, it's not desirable to ignore the provider's state.
    For instance, when multiple processes are sharing a single endpoint, it may
    be the case that the other process has received the connect confirmation,
    and therefore our local library data structure showing T_OUTCON state is
    no longer accurate.
    Test Output
    T.sync output:
    400|0 2 1 15:11:31|IC Start
    200|0 2 15:11:31|TP Start
    520|0 2 00025196 1 1|t_sync() on TCP did not return correct state
    520|0 2 00025196 1 2|RETURN VALUES: expected: 3, observed: 5
    220|0 2 1 15:11:32|FAIL
    410|0 2 1 15:11:32|IC End
    400|0 3 1 15:11:32|IC Start
    200|0 3 15:11:32|TP Start
    520|0 3 00025200 2 1|t_sync() on TCP did not return correct state
    520|0 3 00025200 2 2|RETURN VALUES: expected: 3, observed: 5
    220|0 3 1 15:14:55|FAIL
    410|0 3 1 15:14:55|IC End
    400|0 4 1 15:14:55|IC Start
    200|0 4 15:14:55|TP Start
    520|0 4 00025386 1 1|t_sync() on TCP did not return correct state
    520|0 4 00025386 1 2|RETURN VALUES: expected: 3, observed: 5
    220|0 4 1 15:14:56|FAIL
    410|0 4 1 15:14:56|IC End

    T.snd output:
    400|0 19 1 13:54:24|IC Start
    200|0 19 13:54:24|TP Start
    520|0 19 00004112 1 1|For TCP endpoint
    520|0 19 00004112 1 2|STATE VALUES: expected: 3 (T_OUTCON), observed: 5 (T_DATAX
    FER)
    220|0 19 1 13:54:25|FAIL
    410|0 19 1 13:54:25|IC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    It is recognised that, because of the manner in which the TCP protocol layer
    deals with a connect request, the asynchronous connect facility is not
    particularly useful for TCP based applications. Even in the case that the
    application is written with an asynchronous request to allow portability
    across different transports, the fact that the application is informed that
    data transfer can take place should not create a problem.

    It is recommended that this is treated as a Minor System Fault.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Minor System Fault (MSF)
    Review Conclusion
    A Temporary Waiver is granted.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority