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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1989 Actions

    Problem Report Number 1989
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0575
    Raised 1995-09-13 08:00
    Updated 2003-03-13 08:00
    Published null
    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.open 8
    Problem Summary PGT4R.004 The t_info structure's etsdu attriute is expected to be able to be unlimited for the Transmission Control Protocol in the t_open{8} assertion. That is, the clause in the test is checking that the max...
    Problem Text
    The t_info structure's etsdu attriute is expected to be able to be unlimited
    for the Transmission Control Protocol in the t_open{8} assertion. That is, the
    clause in the test is checking that the maximum size of an Expedited Transport
    Service Data Unit that is supported by the TCP transport provider indicates
    that it be of an unlimited size. i.e.

    struct t_info openinfo;
    ...
    if ( openinfo.etsdu != -1L )
    error;

    However, even though TCP allows support for an unlimited amount of expedited
    data, by default, it supports only a single octet of "out-of-band data".
    The size actually supported by the TCP/IP protocol stack, as it turns out then,
    is implementation dependent.

    The specification for t_info's etsdu, as described in the t_open() section, on
    page 74 of the X/Open Networking Services, Issue 4 indicates that legal values
    for this element actually are -2, -1, 0 and >0. Therefore we submit that this
    clause of the t_open{8} test assertion is insuffiently robust and it's execution
    on platforms whose TCP implementations support only the default out-of-band data
    size will conclude with an erroneous result.
    Test Output
    200|16 8 14:11:27|TP Start
    520|16 8 00001761 1 1|t_open(fd,...) on TCP endpoint
    520|16 8 00001761 1 2|Expected info.etsdu equal to -1
    520|16 8 00001761 1 3|Actual info.etsdu 1
    220|16 8 1 14:11:27|FAIL
    410|16 8 1 14:11:27|IC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The statements contained in the specification of the t_open() interface
    state that "the semantics of expedited data may be quite different for
    different transport providers" and then provides a reference to the
    transport provider specific Appendices. Appendix B, which deals with the
    IP protocol specific aspects states that the value returned for the
    etsdu member in a t_info structure on a call to t_open() should be -1.

    The only question that arises is whether the use of "should" in this sentence
    is meant to provide some flexibility between implementations. The word
    "should" is not used in the description of the t_info structure for other
    transport providers and it is difficult to know whether the usage in the
    IP protocol specific section was deliberate.

    It is recommended that this request is refused, though it should be reviewed
    by the XNET working group in order to determine whether this is 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
    XNET agrees with the consultant that the waiver request in XoTGnet 5252
    should be refused and does not believe that there is a grey area in
    the specification on this issue. A resolution to this effect was passed,
    without objection.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority