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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2009 Actions

    Problem Report Number 2009
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.1001
    Raised 1999-11-11 08:00
    Updated 2003-03-13 08:00
    Published 1999-11-18 08:00
    Product Standard Transport Service XTI V2
    Certification Program The Open Brand certification program
    Test Suite VST version 5.2.4
    Test Identification XTI.os/cots/T.sndv 1
    Problem Summary TSDT5.003 Test case T.sndv{1} is based on the assumption that the total amount of data sent off by a single call to t_sndv() is transferred across the network as ONE complete message, thus enabling the slave ap...
    Problem Text
    Test case T.sndv{1} is based on the assumption that the total amount
    of data sent off by a single call to t_sndv() is transferred across
    the network as ONE complete message, thus enabling the slave
    application to obtain all data by a single call to t_rcv().
    Though this works fine for message-oriented transport systems, it does
    not for byte-stream-oriented transport systems as these do not support
    the concept of messages and message boundaries.
    As TCP IS a byte-stream-oriented transport system, one can't take for
    granted that the very amount of data will be available by calling
    t_rcv() once.
    Therefore, we suggest either to drop this test case for TCP providers
    or to change it such an extent that the slave application collects
    incoming data by calling t_rcv() in a loop. In this way, the test
    suite could make sure that no data are lost but drops any assumption
    about data fragmentation.
    Moreover, the XTI specification just describes how to deal with data
    in non-contiguous buffers at APPLICATION INTERFACE level but does in
    no way indicate how these data are to be transmitted at a lower level.
    To put these data in a single "message" is just one way to do it.

    Test Output
    ************************************************************************
    /tset/XTI.os/cots/sndv/T.sndv 1 Unresolved

    Test Description:
    If the implementation supports a connection-oriented transport
    service:
    When the current state of the endpoint is T_DATAXFER, then a
    successful call to t_sndv( fd, iov, iovcount, flags ) sends data
    over the connection, from the first iovcount number of buffers in
    the iov buffer array, leaves the state of the endpoint unchanged
    from T_DATAXFER, and returns the total number of bytes sent from
    the first iovcount number of buffers in the iov buffer array

    Test Information:

    Test Information From Slave:
    t_rcv() on TCP endpoint with normal data
    RETURN VALUES: expected: 6, observed: 3

    ************************************************************************

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    This is accepted as a Test Suite Deficiency and it is recommended that a
    waiver is granted.

    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