7216 Federal Register / Vol. 62, No. 32 / Tuesday, February 18, 1997 / Notices

f. ANSI X9.17–1985, Financial Institution

Key Management (Wholesale).

g. ISO/IEC 9798–1:1991, Information

technology—Security techniques—Entity

authentication mechanisms—Part 1: General

model.

h. ISO/IEC 9798–3:1993, Information

technology—Security techniques—Entity

authentication mechanisms—Part 3: Entity

authentication using a public key algorithm.

Other NIST publications maybe applicable

to the implementation and use of this

standard. A list (NIST Publications List 91)

of currently available computer security

publications, including ordering information,

can be obtained from NIST.

7. Applicability. This standard is

applicable to all Federal departments and

agencies that use pubic key based

authentication systems to protect

unclassified information within computer

and digital telecommunications systems that

are not subject to Section 2315 of Title 10,

U.S. Code, or Section 3502(2) of Title 44, U.S.

Code. This standard shall be used by all

Federal departments and agencies in

designing, acquiring and implementing

public key based, challenge-response

authentication systems at the application

layer within computer and digital

telecommunications systems. This includes

all systems that Federal departments and

agencies operate or that are operated for them

under contact. In addition, this standard may

be used at other layers within computer and

digital telecommunications systems.

This standard may be adopted and used by

non-Federal Government organizations. Such

use is encouraged when it is either cost

effective or provides interoperability for

commercial and private organizations.

8. Applications. Numerous applications

can benefit from the incorporation of entity

authentication based on public key

cryptography, when the implementation of

such technology is considered cost-effective.

Networking applications that require remote

login will be able to authenticate clients who

have not previously registered with the host,

since secret material (e.g., a password) does

not have to be exchanged beforehand. Also,

point-to-point authentication can take place

between users who are unknown to one

another. The authentication protocols in this

standard may be used in conjunction with

other pubic key-based systems (e.g., a public

key infrastructure that uses public key

certificates) to enhance the security of a

computer system.

9. Specifications. Federal Information

Processing Standard (FIPS) 196, Entity

Authentication Using Public Key

Cryptography (affixed).

10. Implementations. The authentication

protocols described in this standard may be

implemented in software, firmware,

hardware, or any combination thereof.

11. Export Control. Implementations of this

standard are subject to Federal Government

export controls as specified in Title 15, Code

of Federal Regulations, Parts 768 through

799. Exporters are advised to contact the

Department of Commerce, Bureau of Export

Administration, for more information.

12. Implementation Schedule. This

standard becomes effective April 6, 1997.

13. Qualifications. The authentication

technology described in this standard is

based upon information provided by sources

within the Federal Government and private

industry. Authentication systems are

designed to protect against adversaries (e.g.,

hackers, organized crime, economic

competitors) mounting cost-effective attacks

on unclassified government or commercial

data. The primary goal in designing an

effective security system is to make the cost

of any attack greater than the possible payoff.

While specifications in this standard are

intended to maintain the security of an

authentication protocol, conformance to this

standard does not guarantee that a particular

implementation is secure. It is the

responsibility of the manufacturer to build

the implementation of an authentication

protocol in a secure manner. This standard

will be reviewed every five years in order to

assess its adequacy.

14. Waivers. Under certain exceptional

circumstances, the heads of Federal

departments and agencies may approve

waivers to Federal Information Processing

Standards (FIPS). The head of such agency

may re-delegate such authority only to a

senior official designated pursuant to section

3506(b) of Title 44, U.S. Code. Waivers shall

be granted only when:

a. Compliance with a standard would

adversely affect the accomplishment of the

mission of an operator of a Federal computer

system, or

b. Cause a major adverse financial impact

on the operator which is not offset by

Government-wide savings.

Agency heads may act upon a written

waiver request containing the information

detailed above. Agency heads may also act

without a written waiver request when they

determine that conditions for meeting the

standard cannot be met. Agency heads may

approve waivers only by a written decision

which explains the basis on which the

agency head made the required finding(s). A

copy of each such decision, with

procurement sensitive classified portions

clearly identified, shall be sent to: National

Institute of Standards and Technology,

ATTN: FIPS Waiver Decisions, Building 820,

Room 509, Gaithersburg, MD 20899.

In addition, notice of each waiver granted

and each delegation of authority to approve

waivers shall be sent promptly to the

Committee on Government Operations of the

House of Representatives and the Committee

on Governmental Affairs of the Senate and

shall be published promptly in the Federal

Register.

When the determination on a waiver

applies to the procurement of equipment

and/or services, a notice of the waiver

determination must be published in the

Commerce Business Daily as a part of the

notice of solicitation for offers of an

acquisition or, if the waiver determination is

made after that notice is published, by

amendment to such notice.

A copy of the waiver, any supporting

documents, the document approving the

waiver and any supporting and

accompanying documents, with such

deletions as the agency is authorized and

decides to make under 5 U.S.C. Section

552(b), shall be part of the procurement

documentation and retained by the agency.

15. Where to Obtain Copies. Copies of this

publication are available for sale by the

National Technical Information Service, U.S.

Department of Commerce, Springfield, VA

22161. When ordering, refer to Federal

Information Processing Standards

Publication 196 (FIPS PUB 196), and identify

the title. When microfiche is desired, this

should be specified. Payment may be made

by check, money order, credit card, or

deposit account.

[FR Doc. 97–3824 Filed 2–14–97; 8:45 am]

BILLING CODE 3510–CN–M

National Oceanic and Atmospheric

Administration

[I.D. 020797A]

Gulf of Mexico Fishery Management

Council; Public Meetings

AGENCY: National Marine Fisheries

Service (NMFS), National Oceanic and

Atmospheric Administration (NOAA),

Commerce.

ACTION: Notice of public meeting.

SUMMARY: The Gulf of Mexico Fishery

Management Council will convene

public meetings.

DATES: The meetings will be held on

March 10–13,1997.

ADDRESSES: These meetings will be held

at the Holiday Inn on the Beach, 365

East Beach Boulevard, Gulf Shores,

Alabama; telephone: 334–948–6191.

Council address: Gulf of Mexico

Fishery Management Council, 3018 U.S.

Highway 301 North, Suite 1000, Tampa,

FL 33619.

FOR FURTHER INFORMATION CONTACT:

Wayne E. Swingle, Executive Director,

Gulf of Mexico Fishery Management

Council; telephone: (813) 228–2815.

SUPPLEMENTARY INFORMATION:

Council

March 12

8:30 a.m.—Convene.

8:45 a.m. - 11:30 a.m.—Receive public

testimony on Vermilion Snapper Total

Allocable Catch (TAC).

1:00 p.m. - 2:30 p.m.—Receive a

report of the Reef Fish Management

Committee.

2:30 p.m. - 3:30 p.m.—Receive a

report of the Scientific and Statistical

(SSC) Selection Committee. (CLOSED

SESSION).

3:30 p.m. - 5:00 p.m.—Receive a

report of the Advisory Panel (AP)

Selection Committee. (CLOSED

SESSION).

March 13

8:30 a.m. - 9:30 a.m.—Receive a

report of the Shrimp Management

Committee.
Federal Register / Vol. 62, No. 32 / Tuesday, February 18, 1997 / Notices 7217

9:30 a.m. - 9:45 a.m.—Receive a

report of the Habitat Protection

Committee.

9:45 a.m. - 10:15 a.m.—Receive a

report of the Law Enforcement

Committee.

10:15 a.m. - 10:45 a.m.—Receive a

report of the Administrative Policy

Committee.

10:45 a.m. - 11:00 a.m.—Receive a

report of the Stone Crab Management

Committee.

11:00 a.m. - 11:15 a.m.—Receive a

report on the South Atlantic Fishery

Management Council Liaison.

11:15 a.m. - 11:30 a.m.—Receive

Enforcement Reports.

11:30 a.m. - 11:45 a.m.— Receive

Director’s Reports.

11:45 p.m. - 12:00 noon—Other

business to be discussed.

Committees

March 10

9:30 a.m. - 12:30 p.m.—Convene the

AP Selection Committee. (CLOSED

SESSION).

1:30 p.m. - 4:00 p.m.—Convene the

SSC Selection Committee. (CLOSED

SESSION).

4:00 p.m. - 5:30 p.m.—Convene the

Administrative Policy Committee.

March 11

8:00 a.m. - 11:30 p.m.—Convene the

Reef Fish Management Committee.

12:30 p.m. - 4:00 p.m.—Convene the

Shrimp Management Committee.

4:00 p.m. - 4:45 p.m.—Convene the

Stone Crab Management Committee.

4:45 p.m. - 5:30 p.m.—Convene the

Habitat Protection Committee.

Special Accommodations

These meetings are physically

accessible to people with disabilities.

Requests for sign language

interpretation or other auxiliary aids

should be directed to Anne Alford at the

Council (see ADDRESSES) by March 3,

1997.

Dated: February 11, 1997.

Bruce Morehead,

Acting Director, Office of Sustainable

Fisheries, National Marine Fisheries Service.

[FR Doc. 97–3951 Filed 2–14–97; 8:45 am]

BILLING CODE 3510–22–F

DEPARTMENT OF DEFENSE

Office of the Secretary

Public Information Collection

Requirement Submitted to the Office of

Management and Budget (OMB) for

Review

ACTION: Notice.

The Department of Defense has

submitted to OMB for clearance, the

following proposal for collection of

information under the provisions of the

Paperwork Reduction Act (44 U.S.C.

Chapter 35).

Title and OMB Control Number:

Defense Federal Acquisition Regulation

Supplement (DFARS) Part 232, Contract

Financing, and the Clause at 252.232–

7002, Progress Payments for Foreign

Military Sales Acquisitions; OMB

Number 0704–0321.

Type of Request: Extension of a

currently approved collection.

Number of Respondents: 414.

Responses Per Respondent: 12.

Annual Responses: 4,968.

Average Burden Per Response: 30

minutes.

Annual Burden Hours: 7,452

(includes 4,968 recordkeeping hours).

Needs and Uses: The Arms Export

Control Act requires, in the absence of

a special Presidential Finding, that the

U.S. Government purchase military

equipment for foreign governments

using foreign funds and without any

charge to appropriated funds. In order to

comply with this requirement, the

Government needs to know how much

to charge each country as progress

payments are made for foreign military

sales (FMS) purchases. The Government

can only obtain this information from

the contractor preparing the progress

payment request. The clause at 252.232–

7002 requires contractors, whose

contracts include FMS requirements, to

submit a progress payment request with

a supporting schedule which clearly

distinguishes the contract’s FMS

requirements from U.S. contract

requirements. The Government uses this

information to determine how much of

each country’s funds to disburse to the

contractor.

Affected Public: Business or other for

profit; not for profit institutions.

Frequency: On occasion.

Respondent’s Obligation: Required to

obtain or retain benefits.

OMB Desk Officer: Mr. Peter N. Weiss.

Written comments and

recommendations on the proposed

information collection should be sent to

Mr. Weiss at the Office of Management

and Budget, Desk Officer for DoD, Room

10236, New Executive Office Building,

Washington, DC 20503.

DOD Clearance Officer: Mr. William

Pearce.

Written requests for copies of the

information collection proposal should

be sent to Mr. Pearce, WHS/DIOR, 1215

Jefferson Davis Highway, Suite 1204,

Arlington, VA 22202–4302.

Dated: February 12, 1997.

Patricia L. Toppings,

Alternate OSD Federal Register Liaison

Officer, Department of Defense.

[FR Doc. 97–3881 Filed 2–14–97; 8:45 am]

BILLING CODE 5000–04–M

Defense Science Board Task Force on

Underground Facilities

ACTION: Notice of advisory committee

meetings.

SUMMARY: The Defense Science Board

Task Force on Underground Facilities

will meet in closed session on March

12–13, 1997 at U.S. Strategic Command,

Omaha, Nebraska.

The mission of the Defense Science

Board is to advise the Secretary of

Defense through the Under Secretary of

Defense for Acquisition and Technology

on scientific and technical matters as

they affect the perceived needs of the

Department of Defense. At this meeting

the Task Force will address the threat to

U.S. interests posed by the growth of

underground facilities in unfriendly

nations. The Task Force should

investigate technologies and techniques

to meet the international security and

military strategy challenges posed by

these facilities.

In accordance with Section 10(d) of

the Federal Advisory Committee Act,

Public Law 92–463, as amended (5

U.S.C. App. II, (1994)), it has been

determined that this DSB Task Force

meeting concerns matters listed in 5

U.S.C. 552b(c)(1) (1994), and that

accordingly this meeting will be closed

to the public.

Dated: February 12, 1997.

L.M. Bynum,

Alternate OSD Federal Register Liaison

Officer, Department of Defense.

[FR Doc. 97–3879 Filed 2–14–97; 8:45 am]

BILLING CODE 5000–04–M

Defense Science Board Task Force on

Stealth Technology and Future S&T

Investments

ACTION: Notice of advisory committee

meetings.

SUMMARY: The Defense Science Board

Task Force on Stealth Technology and

Future S&T Investments will meet in

closed session on March 19–20, April 1–

2, and April 28–29, 1997 at Science

Applications International Corporation,

4001 N. Fairfax Drive, Arlington,

Virginia.

The mission of the Defense Science

Board is to advise the Secretary of

Defense through the Under Secretary of

Defense for Acquisition and Technology