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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1982 Actions

    Problem Report Number 1982
    Submitter's Classification Minor System Fault
    State Resolved
    Resolution Minor System Fault (MSF)
    Problem Resolution ID MSF.X.0083
    Raised 1996-09-20 08:00
    Updated 2003-03-13 08:00
    Published 1996-10-03 08:00
    Expiry Date 1997-10-02
    Product Standard Transport Service XTI
    Certification Program The Open Brand certification program
    Test Suite VST version 4.1.4
    Test Identification XTI.os/util/getprotad 4
    Problem Summary MSFT4.002 The specification states that "If the transport endpoint is not in the T_DATAXFER state, zero is returned in the len field of peeraddr". The test is indeed testing for that. This above sentence of the...
    Problem Text
    The specification states that "If the transport endpoint is not in the
    T_DATAXFER state, zero is returned in the len field of peeraddr". The
    test is indeed testing for that.

    This above sentence of the specification does not seem to be designed with
    orderly release transports in mind. In our implementation we return
    the "peer" address in states other than T_DATAXFER particularly,
    the T_INREL and T_OUTREL states.

    The problem is that for orderly release transports such as TCP, the states
    T_INREL and T_OUTREL represent states where one direction of connection
    data transfer is completed but the other direction can remain open and
    communicating for days or forever.

    Many TCP applications that do orderly release have a request-response
    style of architecture and spend almost the entire connection lifetime in
    these states transferring data. [At the TCP protocol level, the equivalent
    of T_INREL and T_OUTREL states would be the CLOSE_WAIT and
    FIN_WAIT_2 states].

    It is not reasonable to DISALLOW retrieval of remote address in what
    is a fully functioning one-way connection between transport endpoints.
    Existing applications expect the remote address to be available for their
    use during such connections.

    We would like the failure of this test case and the behavior of
    our implementation to be considered a "minor system fault".
    We also request that this matter to be referred to the specification
    working group for consideration as an allowed behavior through a
    Corrigenda to the specification and in future versions of the
    specification.
    Test Output
    /tset/XTI.os/util/getprotad/T.getprotad 4 Failed

    Test Information:
    t_getprotaddr(fd,...) on TCP endpoint
    Endpoint state is T_OUTREL(6)
    Expected peer address len: 0
    Actual peer address len: 16
    t_getprotaddr(fd,...) on TCP endpoint
    Endpoint state is T_INREL(7)
    Expected peer address len: 0
    Actual peer address len: 16

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The provision of additional information in the peer address structure
    should not affect the portability of applications. While this is out of
    step with the XTI specification, it is not considered to be a significant
    problem and it is recommended that a waiver is granted for this "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