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:

• While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
• Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
• Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
• Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
• Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

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

1. BSFT

Product Information

Environment Specification

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

1.1 Scope of the Implementation

1.1.1 FTAM Roles Supported

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

Response

Yes   No

Rationale

An implementation of BSFT implementation must provide the initiator role, but the responder role is optional.

Reference

CAE Specification, Byte Stream File Transfer (BSFT), Chapter 6, BSFT Requirements.

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

The implementation converts the hostname supplied by the BSFT user into a presentation address that identifies the responder to be accessed. BSFT does not define the mechanism used to perform the conversion.

Reference

CAE Specification, Byte Stream File Transfer (BSFT), Section 7.2, Addressing and Related Issues.

1.2.2 Responder - Use of Filestore Password

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

Response

If the default answer does not correctly reflect your validation technique, replace it.

Rationale

BSFT does not define the mechanism used by a responder to validate this password.

Reference

CAE Specification, Byte Stream File Transfer (BSFT), Section 7.3, Passwords.

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

If the default answer does not correctly reflect your validation technique, replace it.

Rationale

BSFT does not define the mechanism used to determine the type of a file being sent.

Reference

CAE Specification, Byte Stream File Transfer (BSFT), Section 7.5, File Types.

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

Select one of the items from the list.

IA5 GraphicString VisibleString GeneralString

Rationale

BSFT does not define a default value for this parameter.

Reference

CAE Specification, Byte Stream File Transfer (BSFT), Appendix A, BSFT User Interface Definition.

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

If the default answer does not correctly reflect your determination technique, replace it.

Rationale

BSFT does not define the mechanism used to determine the type of a file being processed.

Reference

CAE Specification, Byte Stream File Transfer (BSFT), Section 7.5, File Types.

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

Select one of the items from the list.

Rationale

BSFT does not define a default value for this parameter.

Reference

CAE Specification, Byte Stream File Transfer (BSFT), Section 7.5, File Types.

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

If the default answer does not correctly reflect your generation technique, replace it.

Rationale

BSFT does not define the mechanism used to determine a valid local filename.

Reference

CAE Specification, Byte Stream File Transfer (BSFT), Section 7.9, Invalid Filenames.

1.2.8 Underlying Protocol Support

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

Response

Rationale

The BSFT specification is specific about the support required for FTAM profiles; these profiles in turn state requirements for the upper layers of the OSI protocol stack. Thus, the only question that remains relates to support for transport profiles. BSFT states that it requires the support of the OSI Connection-oriented Transport Service.

Reference

CAE Specification, Byte Stream File Transfer (BSFT), Appendix B, Requirements on the Lower Levels.

2. Appendix

Copyright © 
All rights reserved.

3. Change History