May 16, 2005

(Section III, Question I C Revised May 19, 2005)

SENT VIA EMAIL TO: CHIEF INFORMATION OFFICERS

CHIEF HUMAN CAPTIAL OFFICERS

PHYSICAL SECURITY COMMITTEE MEMBERS

FROM: Glenn Schlarman

Branch Chief, Information Policy and Technology Branch

Office of Management and Budget

SUBJECT: Reporting Format for Homeland Security Presidential Directive
(HSPD) 12 -- Policy for a Common Identification Standard for Federal
Employees and Contractors

The President signed HSPD-12, Policy for a Common Identification
Standard for Federal Employees and Contractors, on August 27, 2004,
which required you, by June 27, 2005, to have a program in place to
ensure identification issued by your department or agency to Federal
employees and contractors meets a common standard. This guidance
provides the reporting instructions.

When completing your implementation plan, refer to HSPD-12 Standard
(Federal Information Processing Standard 201) and the Office of
Management and Budget's implementation guidance. OMB is developing
implementation guidance, which will be available at
[www.omb.gov](http://www.omb.gov/), under memoranda.

Send your HSPD-12 implementation plan to OMB by June 27, 2005, using the
attached template to Jeanette Thornton via email at <eauth@omb.eop.gov>.
Senior agency officials should call Jeanette Thornton at 202-395-3562
with questions.

We appreciate your ongoing efforts to implement this Directive and for
completing the attached template in an accurate and timely manner.

Attachments

Attachment A: Instructions

Attachment B: HSPD-12 Reporting Template

**Attachment A**

**Instructions**

The attached reporting template must be used by agencies to report the
status of your HSPD-12 program. However, to complete this report, you
will need to first develop a detailed implementation plan specific to
your Executive Department and Agency. Please complete all questions.

**Who should prepare and send the report?**

An agency senior official for management must send your plan. In
preparing the report, the senior official should coordinate closely with
the Chief Information Officer, the agency lead for physical security,
and the agency human resources lead.

**My agency has several bureaus or components. What should my plan
cover? Can each bureau send in a separate report?**

Separate plans covering a part of an executive department or agency will
**not** be accepted. The plan should cover your entire agency (including
various bureaus or components). For example if your agency has 6
components, your plan should roll-up of the components.

Agencies can collaborate at a regional level (for examples, all
employees who work at a Federal Building). Information on potential
collaborations will be provided by the General Services Administration.

**How should I use the sliding scale?**

The sliding scale will help you to determine your phase of
implementation. The scale spans the entire implementation process, from
the beginning stages to completion. Agencies with existing identity
credentialing systems should determine whether their existing processes
and implementation meet the requirements of the HSPD-12 standard.

**1 -- Not started.** Agency has not begun implementing the specific
requirement or current process/implementation is not sufficient.

**2 -- Planning in progress.** Agency has begun the planning necessary
to meet the specific requirement.

**3 -- Planning complete.** Agency has completed the necessary planning
to meet the specific requirement. For example, the acquisition plan is
complete.

**4 -- Implementation in progress.** Agency is acquiring or implementing
the products or services to meet the specific requirement.

**5 -- Implementation Complete.** Agency has fully met the specific
requirement.

**\
The procedures in place at my agency's headquarters are different than
what is in place at regional or rural locations. What should I enter in
the sliding scale?**

Base your answers on your entire agency, combining plans for agency
headquarters and regional locations. If there are wide variations
between headquarters and regional or local deployments, agencies should
present an average that generally reflects your entire agency's HSPD-12
implementation.

**How will OMB define full implementation of HSPD-12?**

Full implementation exists when all of the requirements associated with
each question is a "5" on the sliding scale. For example, an agency has
implemented the requirements of FIPS 201 Part II when all the
appropriate employees and contractors have received compliant cards, and
the required components described in the Standard have been implemented
(e.g. front end, access control, card issuance and management).

**Question 1(a) asks if my credential issuance and maintenance process
is approved. What does this mean? Who must approve my process?**

An approved process meets the FIPS 201 requirements and is approved in
writing by the head of your executive department or agency. Agencies
have the option of using the example identity proofing and registration
processes in Appendix A of the Standard or developing one that confirms
to the listed control objectives. The General Services Administration is
developing a set of criteria to aid in this approval.

**What is a visible security feature, referred to in question 4?**

These are features on the identity credential that protect the integrity
of the data printed on the front or the back of the identity credential.
Examples include optical varying structures and inks, laser etching and
engraving, holograms, holographic images, and watermarks.

**What is an electronic security feature, referred to in question 5?
What does it mean to use these security features?**

These are features of the identity credential that protect the integrity
of the data stored on the electronic chip or on the card. These features
are explained on pages 45-51 of the Standard. An example of using the
security feature, is your agency has issued a "smart" card to employees
and contractors, and its capabilities are used to gain access to a
building our resource. Your agency may also use a card that has a
wireless capability to authenticate itself to the card reader installed
at your doors. OMB's implementation guidance will discuss further how
these electronic security features should be used.

**Where can I find the text of FIPS 201?**

[*http://www.csrc.nist.gov/publications/fips/fips201/FIPS-201-022505.pdf*](http://www.csrc.nist.gov/publications/fips/fips201/FIPS-201-022505.pdf)

**Where can I find the text of HSPD-12?**

[*http://www.whitehouse.gov/news/releases/2004/08/20040827-8.html*](http://www.whitehouse.gov/news/releases/2004/08/20040827-8.html)

**Who will review my plan?**

A technical review board comprised of agency technical experts and OMB,
chaired by National Institute of Standards and Technology, will review
your plan. If your plan is approved you will be notified by July 27,
2005. The board's membership list will be posted at
http://csrc.nist.gov/piv-project/.

**ATTACHMENT B\
**

**HSPD-12 REPORTING TEMPLATE**

<table style="width:100%;">
<colgroup>
<col style="width: 38%" />
<col style="width: 20%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 2%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 11%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="16"><h4 id="i.-general-information">I. General
Information</h4></td>
</tr>
<tr class="even">
<td colspan="16">Submission Date:</td>
</tr>
<tr class="odd">
<td colspan="16">Agency/Department Name:</td>
</tr>
<tr class="even">
<td colspan="16">Agency HSPD-12 Point of Contact:</td>
</tr>
<tr class="odd">
<td>Phone Number:</td>
<td colspan="15">Email:</td>
</tr>
<tr class="even">
<td colspan="16"><h4 id="section"></h4></td>
</tr>
<tr class="odd">
<td colspan="16"><h4 id="ii.-timeline">II. Timeline</h4></td>
</tr>
<tr class="even">
<td colspan="16">1) Planned date for compliance with Part 1, Personal
Identity Verification (PIV) I:</td>
</tr>
<tr class="odd">
<td colspan="2" rowspan="2">2) Agency is undergoing a full migration
(e.g. has no existing electronic personal identity verification
system)</td>
<td colspan="4"><strong>Yes</strong></td>
<td colspan="3"><strong>No</strong></td>
<td colspan="7" rowspan="2">Comments:</td>
</tr>
<tr class="even">
<td colspan="4"></td>
<td colspan="3"></td>
</tr>
<tr class="odd">
<td colspan="2">3) Agency is migrating a legacy system (e.g. has a
deployed/or is in the process of deploying electronic identity
credentials i.e. smart cards)</td>
<td colspan="4"><strong>Yes</strong></td>
<td colspan="3"><strong>No</strong></td>
<td colspan="7">Comments:</td>
</tr>
<tr class="even">
<td colspan="16">4) Planned Date to implement Part 2, PIV II (i.e.
starting to issue compliant cards):</td>
</tr>
<tr class="odd">
<td colspan="16">5) Date for full compliance with HSPD-12 (All
employees/contractors using a compliant card):</td>
</tr>
<tr class="even">
<td colspan="16"><h4 id="section-1"></h4></td>
</tr>
<tr class="odd">
<td colspan="16"><h4
id="iii.-agency-implementation-of-fips-201-part-1-piv-i">III. Agency
Implementation of FIPS 201 Part 1: PIV I</h4></td>
</tr>
<tr class="even">
<td colspan="16"><p><strong>Scale: 1 – Not started 2 – Planning in
progress 3 – Planning complete</strong></p>
<p><strong>4 – Implementation in progress 5 – Implementation
complete</strong></p></td>
</tr>
<tr class="odd">
<td colspan="3">Instructions: Place an “x” in the column that
corresponds to your agency’s current environment.</td>
<td colspan="2">1</td>
<td colspan="3">2</td>
<td colspan="3">3</td>
<td colspan="2">4</td>
<td colspan="2">5</td>
<td>Planned completion date</td>
</tr>
<tr class="even">
<td colspan="3"><strong>1) Identification Issued based on sound criteria
for verifying an individuals identity</strong></td>
<td colspan="13"></td>
</tr>
<tr class="odd">
<td colspan="3">a) Approved credential issuance and maintenance process,
as defined in FIPS 201 section 2.0.</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="3">b) National Agency Check with Inquiries (NACI) or
equivalent is initiated prior to credential issuance.</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="3">c) National Agency Check (NAC) or equivalent is
completed <del>within 60 days of</del> before credential issuance.</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="3">d) Controls are in place to ensure all individuals to
whom your agency ID is issued are the same intended
applicants/recipients, approved by the appropriate authority.</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="3">e) Training is provided for all roles associated with
your approved identity proofing and issuance processes.</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="16">Comments:</td>
</tr>
<tr class="odd">
<td colspan="16"></td>
</tr>
<tr class="even">
<td colspan="16"><p
id="iv.-agency-implementation-fips-201-part-2-piv-ii"
class="heading"><strong>IV. Agency Implementation FIPS 201 Part 2: PIV
II</strong></p></td>
</tr>
<tr class="odd">
<td colspan="16"><p><strong>Scale: 1 – Not started 2 – Planning in
progress 3 – Planning complete</strong></p>
<p><strong>4 – Implementation in progress 5 – Implementation
complete</strong></p></td>
</tr>
<tr class="even">
<td colspan="2" rowspan="2"><strong>1) Do you have an implementation
plan developed to meet the FIPS 201 PIV II technology card
specification?</strong></td>
<td colspan="4"><strong>Yes</strong></td>
<td colspan="3"><strong>No</strong></td>
<td colspan="7" rowspan="2">If no, when?</td>
</tr>
<tr class="odd">
<td colspan="4"></td>
<td colspan="3"></td>
</tr>
<tr class="even">
<td colspan="16">a) If yes, describe your high level milestones.</td>
</tr>
<tr class="odd">
<td colspan="16"></td>
</tr>
<tr class="even">
<td colspan="3"></td>
<td colspan="2">1</td>
<td colspan="3">2</td>
<td colspan="3">3</td>
<td colspan="2">4</td>
<td colspan="2">5</td>
<td>Planned completion date</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>2) Identification that is issued only by
providers whose reliability has been established by an official
accreditation process</strong></td>
<td colspan="13"></td>
</tr>
<tr class="even">
<td colspan="3">a) PIV credentials are issued through systems and
providers whose reliability has been established by the Agency, and
documented and approved in writing, i.e., accredited.</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="3">b) Providers (services and/or systems) of components in
the credentialing system comply with all applicable Federal Acquisition
regulations or other applicable purchasing authority.</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="16">Comments</td>
</tr>
<tr class="odd">
<td colspan="16"></td>
</tr>
<tr class="even">
<td colspan="3"></td>
<td colspan="2">1</td>
<td colspan="3">2</td>
<td colspan="3">3</td>
<td colspan="2">4</td>
<td colspan="2">5</td>
<td>Planned completion date</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>3) Identification that is strongly resistant to
identity fraud, tampering, counterfeiting, and terrorist
exploitation</strong></td>
<td colspan="13"></td>
</tr>
<tr class="even">
<td colspan="3">a) All agency ID’s issued with FIPS 201 visible external
security features.</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="16">Comments:</td>
</tr>
<tr class="even">
<td colspan="16"></td>
</tr>
<tr class="odd">
<td colspan="3"></td>
<td colspan="2">1</td>
<td colspan="3">2</td>
<td colspan="3">3</td>
<td colspan="2">4</td>
<td colspan="2">5</td>
<td>Planned completion date</td>
</tr>
<tr class="even">
<td colspan="3"><strong>4) Identification that can be rapidly
authenticated electronically</strong></td>
<td colspan="13"></td>
</tr>
<tr class="odd">
<td colspan="3">a) All agency ID’s are issued with FIPS 201 electronic
security features.</td>
<td colspan="2"><mark></mark></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="3">b) Agency employees and contractors routinely use these
electronic security features to gain access to facilities and/or systems
(or “to authenticate identity”).</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="16">Comments:</td>
</tr>
<tr class="even">
<td colspan="16"></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="2">1</td>
<td colspan="3">2</td>
<td colspan="3">3</td>
<td colspan="2">4</td>
<td colspan="2">5</td>
<td colspan="2"><p>Planned</p>
<p>completion date</p></td>
</tr>
<tr class="even">
<td colspan="2"><strong>5) Using PIV credential for physical and logical
access to Federally controlled facilities and information
systems</strong></td>
<td colspan="14"></td>
</tr>
<tr class="odd">
<td colspan="2">a) All credentials issued by your agency contain a
biometric and can be electronically authenticated to the holder using a
biometric match.</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td colspan="2">b) All credentials issued by your agency have the
capability to be electronically verified to determine the
employee/contractor is in good standing (i.e., the credential has not
been revoked).</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="2">c) My agency will authenticate another agency’s FIPS 201
compliant credentials for access to my facility.</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td colspan="2">d) My agency will authenticate another agency’s FIPS 201
compliant credentials for logical access to an information system (where
necessary).</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="16">Comments:</td>
</tr>
</tbody>
</table>

+-----------------------------------------+---+---+---+---+---+---+---+-------+
| #### V. Security and Privacy            |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| **Scale: 1 -- Not started 2 -- Planning |   |   |   |   |   |   |   |       |
| in progress 3 --** **Planning           |   |   |   |   |   |   |   |       |
| complete**                              |   |   |   |   |   |   |   |       |
|                                         |   |   |   |   |   |   |   |       |
| **4 -- Implementation in progress 5 --  |   |   |   |   |   |   |   |       |
| Implementation complete**               |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| **1) Provide the name of the individual | N |   |   |   |   |   |   |       |
| responsible for privacy matters in      | a |   |   |   |   |   |   |       |
| implementing HSPD-12.**                 | m |   |   |   |   |   |   |       |
|                                         | e |   |   |   |   |   |   |       |
|                                         | : |   |   |   |   |   |   |       |
|                                         |   |   |   |   |   |   |   |       |
|                                         | T |   |   |   |   |   |   |       |
|                                         | i |   |   |   |   |   |   |       |
|                                         | t |   |   |   |   |   |   |       |
|                                         | l |   |   |   |   |   |   |       |
|                                         | e |   |   |   |   |   |   |       |
|                                         | : |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
|                                         |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
|                                         | 1 | 2 |   | 3 |   | 4 | 5 | A     |
|                                         |   |   |   |   |   |   |   | ntici |
|                                         |   |   |   |   |   |   |   | pated |
|                                         |   |   |   |   |   |   |   | compl |
|                                         |   |   |   |   |   |   |   | etion |
|                                         |   |   |   |   |   |   |   | date  |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| **2) Agency meets all security and      |   |   |   |   |   |   |   |       |
| privacy control objectives**            |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| a\) Ensures personal information        |   |   |   |   |   |   |   |       |
| contained in Privacy Act systems of     |   |   |   |   |   |   |   |       |
| records related to HSPD-12 are handled  |   |   |   |   |   |   |   |       |
| in a manner consistent with the Privacy |   |   |   |   |   |   |   |       |
| Act of 1974.                            |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| b\) Has completed a comprehensive       |   |   |   |   |   |   |   |       |
| privacy impact assessment the IT        |   |   |   |   |   |   |   |       |
| systems used to implement HSPD-12.      |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| c\) Has updated agency system of        |   |   |   |   |   |   |   |       |
| records notice (related to HSPD-12) to  |   |   |   |   |   |   |   |       |
| reflect any changes in the disclosure   |   |   |   |   |   |   |   |       |
| of information to other Federal         |   |   |   |   |   |   |   |       |
| agencies (i.e. routine uses).           |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| d\) Is collecting information to        |   |   |   |   |   |   |   |       |
| conduct background checks with OMB      |   |   |   |   |   |   |   |       |
| approval under the Paperwork Reduction  |   |   |   |   |   |   |   |       |
| Act (where appropriate).                |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| e\) Identification privacy policy is    |   |   |   |   |   |   |   |       |
| developed, implemented and posted in    |   |   |   |   |   |   |   |       |
| appropriate locations (e.g., agency     |   |   |   |   |   |   |   |       |
| intranet site, human resource offices,  |   |   |   |   |   |   |   |       |
| regional offices, etc.).                |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| Comments:                               |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
|                                         |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| #                                       |   |   |   |   |   |   |   |       |
| ### VI. Special Security Risk Provision |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| 1\) Agency is planning to issue         | * |   | * |   | I |   |   |       |
| credentials under the special security  | * |   | * |   | f |   |   |       |
| risk provision.                         | Y |   | N |   | y |   |   |       |
|                                         | e |   | o |   | e |   |   |       |
|                                         | s |   | * |   | s |   |   |       |
|                                         | * |   | * |   | , |   |   |       |
|                                         | * |   |   |   | h |   |   |       |
|                                         |   |   |   |   | o |   |   |       |
|                                         |   |   |   |   | w |   |   |       |
|                                         |   |   |   |   | m |   |   |       |
|                                         |   |   |   |   | a |   |   |       |
|                                         |   |   |   |   | n |   |   |       |
|                                         |   |   |   |   | y |   |   |       |
|                                         |   |   |   |   | ? |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| ####  {#section-2}                      |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| #### VII. Status                        |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
|                                         | C |   |   |   | I |   |   |       |
|                                         | o |   |   |   | f |   |   |       |
|                                         | m |   |   |   | N |   |   |       |
|                                         | p |   |   |   | o |   |   |       |
|                                         | l |   |   |   | , |   |   |       |
|                                         | e |   |   |   | w |   |   |       |
|                                         | t |   |   |   | h |   |   |       |
|                                         | e |   |   |   | e |   |   |       |
|                                         |   |   |   |   | n |   |   |       |
|                                         |   |   |   |   | ? |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| 1\) On October 27, 2005 my agency will  | Y |   | N |   |   |   |   |       |
| be compliant with Part 1 of the         | e |   | o |   |   |   |   |       |
| Standard. (i.e. will implement a FIPS   | s |   |   |   |   |   |   |       |
| 201 compliant enrollment and issuance   |   |   |   |   |   |   |   |       |
| process)                                |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
|                                         |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| 2\) On October 27, 2006 my agency will  | Y |   | N |   |   |   |   |       |
| be compliant with Part 2 of the         | e |   | o |   |   |   |   |       |
| Standard. (i.e. will begin issuing and  | s |   |   |   |   |   |   |       |
| utilizing FIPS 201 compliant            |   |   |   |   |   |   |   |       |
| credentials)                            |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| Name:                                   |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+
| Title:                                  |   |   |   |   |   |   |   |       |
+-----------------------------------------+---+---+---+---+---+---+---+-------+

#  {#section-3}