HomeAbout Us A-Z IndexSearchInquiries RegisterLoginPress Shop
Conformance Statement

Product Standard: BSFT

This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

Organization
Author


1. BSFT

Product Information

Enter the product name, version/release number, and product supplier for each product required to meet the conformance requirements.

Product IdentificationVersion/Release NumberProduct Supplier
 
 
 
 
 

Environment Specification

Product registration applies to software products operating in a specific hardware or hardware/software environment.

A product may be registered in all members of a binary-compatible family of products on the basis of a single test report.

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

Testing Environment Binary-compatible Family Portability Environment Indicator of Compliance Compliance Details
None. None. None.
None. None. None.
None. None. None.
None. None. None.
None. None. None.

Temporary Waivers

Enter the waiver number and expiry date for each temporary waiver granted by The Open Group.

Waiver NumberExpiry Date


1.1 Scope of the Implementation

1.1.1 FTAM Roles Supported

Question 1: Does the product support the FTAM responder role?

Response

Rationale

Reference


1.2 Technical Requirements

1.2.1 Initiator - Generation of Presentation Addresses

Question 2: What mechanism is used by the initiator to generate presentation addresses from user-supplied information?

Response

Rationale

Reference


1.2.2 Responder - Use of Filestore Password

Question 3: If the responder role is supported, how does BSFT validate a filestore password?

Response

Rationale

Reference


1.2.3 Initiator - Default Document Type for Files Sent

Question 4: How does an initiator determine the document type to be sent to a responder when the BSFT user does not specify this?

Response

Rationale

Reference


1.2.4 Initiator - Default Data Type for Files Sent

Question 5: What is the contents type FTAM parameter value specified for an FTAM-1 file sent to a responder when the BSFT user does not specify a value via the BSFT encode command?

Response

Rationale

Reference


1.2.5 Responder Default Document Type for Files Sent

Question 6: If the responder role is supported, how does the implementation determine the document type of the file in its local filestore?

Response

Rationale

Reference


1.2.6 Responder - Data Type for Files Sent

Question 7: What is the contents type FTAM parameter value specified for FTAM-1 files sent to an initiator?

Response

Rationale

Reference


1.2.7 Initiator - Generation of Local Filenames

Question 8: How does an initiator generate a valid local filename when the user has not specified it and the remote filename cannot be used in the local filestore?

Response

Rationale

Reference


1.2.8 Underlying Protocol Support

Question 9: Over which connection-oriented transport profiles ("T-profiles") can the product operate?

Response

Rationale

Reference


2. Appendix

This appendix contains additional, explanatory material that was provided by the vendor.


Copyright © 
All rights reserved.


3. Change History

DateNameComment
New

 Copyright © 1998-2002 The Open Group. All Rights Reserved.

 OSF/1, Motif, UNIX, and the "X" device are registered trademarks in the U.S. and other countries, and IT DialTone and The Open Group are trademarks of The Open Group.


[ Home ] [ Testing Home ] [ Conformance Statement Library Home ] [ Search Conformance Statements ] [ Send Feedback ]