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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1984 Actions

    Problem Report Number 1984
    Submitter's Classification Minor System Fault
    State Resolved
    Resolution Minor System Fault (MSF)
    Problem Resolution ID MSF.X.0085
    Raised 1996-10-07 08:00
    Updated 2003-03-13 08:00
    Published 1996-10-18 08:00
    Expiry Date 1997-10-17
    Product Standard Transport Service XTI
    Certification Program The Open Brand certification program
    Test Suite VST version 4.1.4
    Test Identification XTI.os/cots/rcv 5
    Problem Summary MSFT4.004 The test failure here is identical to the failure in Waiver request req.xti.4.1.027, which was rejected for another submitter. The X/Open consultant's response in that interpretation quotes a certain...
    Problem Text

    The test failure here is identical to the failure in Waiver
    request req.xti.4.1.027, which was rejected for another submitter.

    The X/Open consultant's response in that interpretation quotes a certain
    part of the XTI specification regarding semantics expected from t_look()
    running over TCP (Appendix B, page 113, description of t_look()).
    These semantics of t_look() behavior are hard to implement in a Streams
    framework based XTI library.

    In such a framework, the existing interfaces under Unix allow only
    access to the first queued message at the Stream head. In protocols
    like TCP, where expedited data flows in the same Streams priority band
    as regular data, the interfaces do not allow access to the fact that the
    TCP receive buffer has already queued urgent data.

    To implement what is desired by this test suite, new framework features
    are needed to enable t_look() returning a T_EXDATA event as soon as a TCP
    urgent pointer is received (and even when there is regular data queued
    ahead on the read side).

    Our current t_look() implementation will return a T_EXDATA event
    only when the expedited data message is the first message on the stream
    head.

    We would like some time to develop new internal interfaces to implement
    the t_look() semantics as implied by the specification.

    We would like to request a Minor System Fault waiver for this failure
    for the purpose of branding the product.

    Test Output

    /tset/XTI.os/cots/rcv/T.rcv 5 Unresolved

    Test Information:
    Unexpected event on TCP endpoint
    Expected 8 (T_EXDATA), actual 4 (T_DATA)

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    This is a matter of judgement as to the importance of providing an
    indication of incoming expedited data when ordinary data is already
    in the received data queue. Irrespective of whether or not the
    T_EXDATA event is indicated, the application has to read the ordinary
    data before the expedited data can be retrieved at which point the
    expedited data becomes available and is indicated as expedited. The
    only applications that should be affected are ones which use t_look()
    to identify the existence of data at the receiving end-point. This
    is probbaly a small subset of applications, since most applications
    would prefer to use t_rcv() in asynchronous mode to both check and
    receive data in a single operation.

    I would recommend that a temporary waiver is granted.

    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