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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1978 Actions

    Problem Report Number 1978
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0241
    Raised 1997-02-21 08:00
    Updated 2003-03-13 08:00
    Published 1997-02-25 08:00
    Product Standard Transport Service XTI
    Certification Program The Open Brand certification program
    Test Suite VST version 4.1.4
    Test Identification /tset/XTI.os/cots/accept/T.accept 26
    Specification Networking Services Issue 4
    Location in Spec See Problem Text
    Problem Summary PINT4.007 There exists a grey area (documented in the VST release notes) in the specification concerning the conditions under which a call to t_accept() will return the error TPROVMISMATCH. The test suite uses ...
    Problem Text
    There exists a grey area (documented in the VST release notes) in the
    specification concerning the conditions under which a call to t_accept()
    will return the error TPROVMISMATCH.

    The test suite uses 2 entries in the transport provider details file,
    ISO CLASS 2 and ISO CLASS 4, and expects to obtain this error return.
    The same device name is used to open and initialise the 2 providers.

    This does not produce the expected behaviour on our implementation as
    no error is observed.

    When configured to use the transport providers ISO CLASS 4 (say) and
    TCP, the same test case breaks on a preceeding t_bind() giving rise to
    an UNRESOLVED result. It is possible that a userintf.c file could be
    constructed to handle both types of provider, but the test case would
    still fail using ISO CLASS 2 and 4.

    We request that a PIN be accorded to waive this test result.

    The test report is as follows :

    ------------------------------------------------------------------
    /tset/XTI.os/cots/accept/T.accept 26 Failed

    Test Description:
    If the implementation supports two or more connection-oriented
    transport providers:
    When fd and resfd do not refer to the same transport
    provider,
    then t_accept() returns (int)-1, sets t_errno to
    TPROVMISMATCH,
    and the states of the endpoints fd and resfd are not
    changed.

    Test Strategy:
    OBTAIN provider details for a T_COTS or T_COTS_ORD provider
    using
    nextprov()
    REPEAT until nextprov() indicates no more providers:
    OBTAIN provider details for another T_COTS or T_COTS_ORD
    provider
    using nextprov()
    OBTAIN an endpoint for this provider, in T_INCON state, using
    provsetup()
    OPEN an endpoint for the previous provider using t_open()
    INITIALISE endpoint using u_provinit()
    ACCEPT connection using t_accept() with resfd as endpoint
    just
    opened
    VERIFY that t_accept() returned -1 and set t_errno to
    TPROVMISMATCH
    VERIFY that the states of the endpoints have not changed
    CLOSE both endpoints using t_close()

    Test Information:
    t_accept() with fd as ISO CLASS 2 endpoint and resfd as ISO
    CLASS 4
    endpoint
    RETURN VALUES: expected: -1, observed: 0
    TERRNO VALUES: expected: 25 (TPROVMISMATCH), observed: 0 (NO
    ERROR)
    -------------------------------------------------------------------

    Test Output
    15|0 2.3 1|TCM Start
    400|0 26 1 16:15:08|IC Start
    200|0 26 16:15:08|TP Start
    520|0 26 00017670 1 1|t_accept() with fd as ISO CLASS 2 endpoint and
    resfd as ISO
    CLASS 4 endpoint
    520|0 26 00017670 1 2|RETURN VALUES: expected: -1, observed: 0
    520|0 26 00017670 1 3|TERRNO VALUES: expected: 25 (TPROVMISMATCH),
    observed: 0 (NO
    ERROR)
    220|0 26 1 16:15:09|FAIL
    410|0 26 1 16:15:09|IC End
    80|0 0 16:15:09|TC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The XNET specification is somewhat vague regarding the circumstances in
    which the EPROVMISMATCH error is generated. The current set of release
    notes for VST note that there is the potential for different interpretations
    in this case and that this may depend on the particular pair of providers
    that are chosen.

    It is recommended that a Permanent Interpretation is granted.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Permanent Interpretation (PIN)
    Review Conclusion
    A Permanent Interpretation is granted.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority