HomeAbout Us A-Z IndexSearch * Contact Us Register LoginPress Shop

The Open Brand -- Problem Reporting and Interpretations System


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


Report 1995 Actions


    Problem Report Number 1995
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0581
    Raised 1996-03-08 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/clts/rcvudata 2
    Problem Summary PGT4R.010 This interpretation request is for the following assertions: /tset/XTI.os/clts/rcvudata/T.rcvudata 2 Failed /tset/XTI.os/clts/rcvudata/T.rcvudata 6 Failed /tset/XTI.os/cots/connect/T.connect 4 Failed ...
    Problem Text
    This interpretation request is for the following assertions:

    /tset/XTI.os/clts/rcvudata/T.rcvudata 2 Failed
    /tset/XTI.os/clts/rcvudata/T.rcvudata 6 Failed
    /tset/XTI.os/cots/connect/T.connect 4 Failed
    /tset/XTI.os/cots/connect/T.connect 8 Failed
    /tset/XTI.os/cots/listen/T.listen 5 Failed


    The above assertions are failing not because the request is failing,
    but because the associaton-related options used by the test are not
    supported on our system. The specification does not require that specific
    association-related options be supported on all implementations. On
    page 200 of the XPG Neworking Services spec, section B.2 the following
    is stated:

    "... A transport provider compliant to this specification supports none,
    all or any subset of the options defined in Section B.2.1, Section B.2.2
    and Section B.2.3. ..."

    Per X/Open requirements, options on our system are documented in the XTI
    CSQ.
    Test Output
    ************************************************************************
    /tset/XTI.os/clts/rcvudata/T.rcvudata 2 Failed

    Test Description:
    If the implementation supports a connectionless transport service:
    When options have been specified with the data unit sent by
    t_sndudata(), then a successful call to t_rcvudata( fd, unitdata,
    flags ) receives data into unitdata->udata.buf on the transport
    endpoint, consumes the T_DATA event associated with this data on
    the transport endpoint, returns the associated related options
    specified on the corresponding call to t_sndudata(), after these
    have been subject to negotiation, returns the number of bytes
    received in unitdata->udata.len, and returns a value of (int)0.

    Test Strategy:
    MASTER:
    VERIFY that the transport service is of type T_CLTS
    OBTAIN an endpoint in T_IDLE state using provsetup()
    OBTAIN an option buffer using getoptlist() and addoption()
    SEND the option buffer to the slave using putsv_m()
    SYNC with slave using tet_sync()
    WAIT for a T_DATA event using wait_event()
    RECEIVE a data unit from slave using t_rcvudata()
    VERIFY that the endpoint state, outstanding events, and return
    value are as expected
    VERIFY that the options received are as expected
    VERIFY that the udata.len matches the number of bytes received
    VERIFY that the received data in udata.buf is as expected
    SLAVE:
    INITIALISE send buffer with some data
    RECEIVE option buffer from the master using getsv_s()
    SEND a data unit to master using t_sndudata()
    SYNC with master system using tet_sync()

    Test Information:
    t_rcvudata() on UDP endpoint
    Supported option level <17> name <1536> not found in rcvcall buffer
    ************************************************************************

    ************************************************************************
    /tset/XTI.os/clts/rcvudata/T.rcvudata 6 Failed

    Test Description:
    If the implementation supports a connectionless transport service:
    When the number of bytes allocated for incoming address or
    incoming options (maxlen) is greater than 0 but not sufficient to
    store the information, then t_rcvudata() returns (int)-1, sets
    t_errno to TBUFOVFLW, and sets the state of the endpoint as if the
    call had been successful.

    Test Strategy:
    MASTER:
    VERIFY that the transport service is of type T_CLTS
    OBTAIN an endpoint in T_IDLE state using provsetup()
    SLAVE:
    SEND a data unit to master system using t_sndudata()
    MASTER:
    WAIT for a T_DATA event using wait_event()
    SET the addr.maxlen to 1 and opt.maxlen to 0
    ATTEMPT to receive a data unit from slave using t_rcvudata()
    VERIFY that the return value, endpoint state and t_errno are as
    expected
    VERIFY that udata.len is zero
    OBTAIN supported association-related options using getoptlist()
    SEND options to slave using putsv_m()
    SLAVE:
    RECEIVE option buffer from master using getsv_s()
    SEND a data unit to master system using t_sndudata()
    MASTER:
    WAIT for a T_DATA event using wait_event()
    SET the addr.maxlen to 0 and opt.maxlen to 1
    ATTEMPT to receive a data unit from slave using t_rcvudata()
    VERIFY that the return value, endpoint state and t_errno are as
    expected
    VERIFY that udata.len is zero

    Test Information:
    t_rcvudata() on UDP endpoint, with addr.len too small
    expected udata.len = 0, actual = 6
    t_rcvudata() on UDP endpoint, with opt.len too small
    RETURN VALUES: expected: -1, observed: 0
    TERRNO VALUES: expected: 11 (TBUFOVFLW), observed: 0 (NO ERROR)
    ************************************************************************

    ************************************************************************
    /tset/XTI.os/cots/connect/T.connect 4 Failed

    Test Description:
    If the implementation supports a connection-oriented transport
    service:
    When rcvcall is not NULL, and sndcall->opt.len is zero, then a
    successful call to t_connect( fd, sndcall, rcvcall ) returns
    information associated with the connection in rcvcall->opt.

    Test Strategy:
    VERIFY that the transport service is of type T_COTS or T_COTS_ORD
    MASTER:
    GENERATE a suitable option buffer for the transport provider using
    getoptlist() and addoption()
    OBTAIN an endpoint in T_IDLE state using provsetup()
    SEND the option buffer to the slave, using putsv_m()
    INITIATE a connection using t_connect() with sndcall->opt.len==0
    SLAVE:
    RECEIVE option buffer from the master, using getsv_s()
    WAIT for connect request using t_listen()
    ACCEPT connection using t_accept() with the options in call->opt
    MASTER:
    VERIFY that t_connect() returned zero
    VERIFY that rcvcall->opt has the expected contents

    Test Information:
    t_connect() on TCP endpoint
    Association-related option level <0> name <1> not found in rcvcall
    buffer

    Test Information From Slave:
    t_accept() on TCP endpoint
    RETURN VALUES: expected: 0, observed: -1
    TERRNO VALUES: expected: 0 (NO ERROR), observed: 2 (TBADOPT)
    ************************************************************************

    ************************************************************************
    /tset/XTI.os/cots/connect/T.connect 8 Failed

    Test Description:
    If the implementation supports a connection-oriented transport service
    which supports one or more privileged options:
    When sndcall->opt includes one or more privileged options, and the
    user does not have permission to use those options, then a
    successful call to t_connect( fd, sndcall, rcvcall ) ignores those
    options.

    Test Strategy:
    VERIFY that the transport service is of type T_COTS or T_COTS_ORD
    MASTER:
    OBTAIN an endpoint in T_IDLE state using provsetup()
    OBTAIN an option buffer with privileged options using u_priv_opt()
    IF u_priv_opt() indicated no privileged options are supported:
    SKIP to next transport provider
    INITIATE a connection using t_connect() with the options in
    sndcall->opt
    SLAVE:
    IF no privileged options are supported on master:
    SKIP to next transport provider
    WAIT for connect request using t_listen()
    ACCEPT connection using t_accept()
    MASTER:
    VERIFY that t_connect() returned zero
    VERIFY that rcvcall->opt does not contain the privileged option

    Test Information:
    t_connect() on TCP endpoint
    Privileged option <8> found in rcvcall buffer
    ************************************************************************

    ************************************************************************
    /tset/XTI.os/cots/listen/T.listen 5 Failed

    Test Description:
    If the implementation supports a connection-oriented transport service
    which supports one or more association-related options:
    A successful call to t_listen( fd, call ) returns in call->opt the
    association-related options related to the incoming connection,
    and each option has either the same value as that requested by the
    calling transport user or a value of lesser quality.
    Testing Requirement(s):
    The options requested by the calling transport user should, if
    possible, include some that are not association-related, in order
    to test that only association-related options are returned by
    t_listen().

    Test Strategy:
    VERIFY that the transport service is of type T_COTS or T_COTS_ORD
    MASTER:
    OBTAIN an endpoint with qlen 1 in T_IDLE state using provsetup()
    OBTAIN a suitable option buffer using getoptlist()
    SEND the option buffer to the slave using putsv_m()
    WAIT for connect request using t_listen()
    SLAVE:
    RECEIVE the option buffer from the master using getsv_s()
    INITIATE a connection using t_connect() with the options in
    sndcall->opt
    MASTER:
    VERIFY that t_listen() returned zero
    VERIFY that call->opt has the expected contents

    Test Information:
    t_listen() on TCP endpoint:
    association-related option level <0> name <1> not found in call->opt
    t_listen() on TCP endpoint:
    association-related option level <0> name <3> not found in call->opt
    ************************************************************************

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The file userintf.c is available for modification by the user to include
    or exclude specific option sets that may be used to test features of the
    XTI implementation. The settings in the delivered version of this file
    are suitable for some systems, but will need to be modified for the system
    under test.

    It is recommended that this request is refused and that the submitter is
    requested to make the appropriate changes to the user modifiable files.

    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