R
E
F
E
R
E
N
C
E

Registry of Reserved TPM 2.0
Handles and Localities
Version 1.2
Revision 0.91
September 8, 2023
Contact: admin@trustedcomputinggroup.org
Public Review

Work in ProgressThis document is an intermediate
draft for comment only and is subject
to change without notice. Readers
should not design products based on
this document.

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | Public Review© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

DISCLAIMERS, NOTICES, AND LICENSE TERMS
THIS DOCUMENT IS PROVIDED "AS IS" WITH NO WARRANTIES WHATSOEVER, INCLUDING ANYWARRANTY OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE, OR
ANY WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL, DOCUMENT OR SAMPLE.
Without limitation, TCG disclaims all liability, including liability for infringement of any proprietary rights, relating touse of information in this document and to the implementation of this document, and TCG disclaims all liability forcost of procurement of substitute goods or services, lost profits, loss of use, loss of data or any incidental,
consequential, direct, indirect, or special damages, whether under contract, tort, warranty or otherwise, arising in
any way out of use or reliance upon this document or any information herein.
This document is copyrighted by Trusted Computing Group (TCG), and no license, express or implied, is granted
herein other than as follows: You may not copy or reproduce the document or distribute it to others without written
permission from TCG, except that you may freely do so for the purposes of (a) examining or implementing TCG
documents or (b) developing, testing, or promoting information technology standards and best practices, so long as
you distribute the document with these disclaimers, notices, and license terms.
Contact the Trusted Computing Group at www.trustedcomputinggroup.org for information on document licensing
through membership agreements.
Any marks and brands contained herein are the property of their respective owners.

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 1© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

CHANGE HISTORYREVISIONDATE

DESCRIPTION

1.00/0January 6, 2013

• Initial Release

1.00/1

April 1, 2015

• The meaning of bits 22 and 23 emphasized in a new table(Table 2)• Specific values of bits 22 and 23 incorporated into specifichandle values in Table 3.
New Tables 4, 5, and 6 inserted in anticipation of future values of“Component OEM“, “TPM OEM“ and “Platform OEM” NV handles

1.10/0Feb 6, 2019

• Added reference to the list of OIDs and Catalog.
• Added comment about TPM enforcing some bits of the key
handle.
• Added requested handles by companies and TCG Workgroups• Added note that organizations are responsible for sub-dividing
NV Indices if necessary.
• Deprecated certain Platform Classes• Referenced TPM 2 Library specification for numbering format
instead of copying it.
• NOTE: Will change Revision to 0 when ported to new templateand remove this note.

1.2/.9July 26, 2023

• Added External Standards Development Organization Range• Assigned a range to the FIDO Alliance1.2/.91

Sept 08, 2023

• TCG Membership and public review

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 2© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

1 Contents
DISCLAIMERS, NOTICES, AND LICENSE TERMS ..................................................................................................... 1
CHANGE HISTORY ....................................................................................................................................................... 2
1

Introduction and Scope ........................................................................................................................................... 5
1.1 References ...................................................................................................................................................... 5

2

Numbers 6

2

Handles (indices) .................................................................................................................................................... 7
2.1 PCR Handles .................................................................................................................................................. 7
2.2 NV Indices ....................................................................................................................................................... 8
2.2.1 TPM Specification Defined .................................................................................................................... 8
2.2.2 TCG Conventional NV Indices Usage ................................................................................................... 8
2.3 Key Handles .................................................................................................................................................. 15
2.3.1 Key Handle Assignments .................................................................................................................... 15
2.3.2 Key Handle and Certificate Handle Relationships .............................................................................. 16

3

Localities 17

4

Platform Class ...................................................................................................................................................... 18

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 3© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

Table of Tables
Table 1: Reserved Handles for PCR ............................................................................................................. 7
Table 2: Reserved Handles for NV indices ................................................................................................... 8
Table 3: Example NV Unassigned Usages ................................................................................................... 9
Table 4: Known NV Index Unassigned Usages .......................................................................................... 10
Table 5: Endorsement NV Index Usages .................................................................................................... 10
Table 6: Handles for Global NV indices assigned to Component OEMs .................................................... 11
Table 7: Handles for Global NV indices assigned to TPM OEMs ............................................................... 11
Table 8: Handles for Global NV indices assigned to Platform OEMs ......................................................... 12
Table 9: NV Indices assigned by TCG for specific usages ......................................................................... 13
Table 10: NV Handles for PC Client WG .................................................................................................... 13
Table 11 NV Handles Assigned to External Standards .............................................................................. 14
Table 12: Key Handles for Persistent Objects ............................................................................................ 15
Table 13: Localities Reserved for Platform-Specific Workgroups ............................................................... 17
Table 14: Platform Class Values ................................................................................................................. 18

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 4© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

1 Introduction and Scope
This registry is a companion to the TPM 2.0 library specification [1]. This registry describes TCG's convention forallocating TPM 2.0 handles and localities. Many of the values in this document specify ranges for vendors to use
and these ranges are reserved by TCG for those vendors’ use.

1.1 References[1]

TPM 2.0 Library Specification
URL: https://trustedcomputinggroup.org/work-groups/trusted-platform-module

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 5© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

2 Numbers
The numbers used in this document are formatted as defined by the TPM Library specification in Section 7.3
Numbers (as of revision 1.46).

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 6© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

2 Handles (indices)A handle is a 32-bit value. Its most significant octet identifies the type of resource. At any given instant, a handle’s
low-order bits identify a unique resource. The actual resource identified by the low-order bits may change with time.
Platform-specific workgroups choose the resources whose handles they wish to register and define those handles intheir individual TCG specifications. However, all TPM 2.0 handle definitions must be consistent with the TPM 2.0
specification and the definitions in this registry.

2.1 PCR Handles
Table 1 of this registry states the range that is assigned by TCG to PCR handles. Note that Table 1 reserves theentire range of handles that is available for PCR. All handles used by PCR must be within the range stated in Table
1.

Table 1: Reserved Handles for PCR

Handle Type

Entity that further refines
the handle type

PCR indices

TPM workgroup

Refinedhandle type

Handle Range
00 00 00 0016 – 00 FF FF FF16

The proper interpretation of Table 1 is that the lower 24 bits of a PCR handle have the same value as the PCR’s
number. For example, the handle of PCR-0 is 00 00 00 0016, the handle of PCR-2 is 00 00 00 0216. The handle forthe same PCR (PCR-0, PCR-1, etc.) is always the same, irrespective of workgroup, although the integrity metrics
recorded in a PCR may vary with workgroup.

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 7© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

2.2 NV Indices2.2.1 TPM Specification Defined
The TPM 2.0 library specification Part-II section “NV Storage Structures” defines how a TPM interprets handles for
NV indices. The TPM Library Specification defines bits 31-24 as reserved for NV Indices.1

2.2.2 TCG Conventional NV Indices Usage
This section defines TCG’s convention for bits 23-00.
NOTE: The TPM does not enforce the conventional usage (i.e., bits 23 -00) for NV Indices defined in this section.

Table 2 defines the entire range of handles available for NV indices. How each range is used and assigned isdefined by the handle type’s assignee. Note that this registry does not assign NV space in a TPM.

Handle TypeNV indicesunassigned by
TCG
See Section
2.2.2.1

NV indicesassigned by TCG
per platform
component level
See Sections
2.2.2.2 and 2.2.2.3

Table 2: Reserved Handles for NV indices
Refined Handle
Source ofType
Handle Type
Handle Range
TPM

TPM
manufacturer

01 00 00 0016 – 01 3F FF FF16

Platform

Platform
Manufacturer

01 40 00 0016 – 01 7F FF FF16

Owner

Owner

01 80 00 0016 – 01 BF FF FF16

Endorsement

Individual
handles are
determined byindividual
workgroups

01 C0 00 0016 – 01 C0 7F FF16

Platform

Individual
handles are
determined byindividual
workgroups

01 C0 80 0016 – 01 C0 FF FF16

Technical
Committee

01 C1 00 0016 – 01 C1 FF FF16

Technical
Committee

01 C2 00 0016 – 01 C2 FF FF16

Component OEM(See Table 6 ofthis registry)
TPM OEM(See Table 7 ofthis registry)

TPM_HT_NV_INDEX = 0x01; HR_SHIFT= 24(decimal); HR_NV_INDEX = (TPM_HT_NV_INDEX <<HR_SHIFT)
1

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 8© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

Handle Type

Refined Handle
Type

Source ofHandle Type

Handle Range

Platform OEM(See Table 8 ofthis registry)
NV Indicesassigned by TCG
for specific usages

TCG
Specifications andWorkgroups

See Section
2.2.2.4(See Table 9 andTable 10)2.2.2.1

Technical
Committee

01 C3 00 0016 – 01 C3 FF FF16

Technical
Committee

01 C4 00 0016 – 01 FF FF FF16

NV indices unassigned by TCG

2.2.2.1.1 General Description
An NV index within these ranges are assigned by entities outside TCG. This NV Indices do not have the same
meaning across all platform classes. It is anticipated that some of these NV indices will be assigned by firmware orsoftware applications.
1. The indices defined by one individual Owner may or may not be the same as those defined by anotherindividual Owner.
2. The indices defined by one individual platform manufacturer may or may not be the same as those definedby another platform manufacturer.
3. The indices defined by a platform manufacturer for one type of platform may or may not be the same as
those defined by the same manufacturer for another type of platform.
4. The indices defined by one individual TPM manufacturer may or may not be the same as those defined byanother TPM manufacturer.
5. The indices defined by a TPM manufacturer for one type of TPM may or may not be the same as thosedefined by the same manufacturer for another type of TPM.
This range is divided into sub-ranges allocated to the platform component that uses the NV Index. Example usages
are in Table 3 below.

Refined Handle Type

Table 3: Example NV Unassigned Usages
Example UsageTPM

TPM Manufacturer-specific information about the TPM which is not
represented by a Capability.

Platform

Platform information which is kept secure using Platform Policies

Owner

OS or application specific usages

2.2.2.1.2 Known Usages
Within these ranges Table 4 identifies known NV Index ranges or specific NV Indices in use. Note these values
are informative and are not enforced by TCG. It is possible other uses exist (some may overlap those listed

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 9© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

here) that are not identified. Entities wanting to list their usage should contact TCG admin at:admin@trustedcomputinggroup.org.

Platform

Table 4: Known NV Index Unassigned Usages
NV Index or NV Range
Known usage<N/A>
01 40 00 00 – 01 40 FF FF16
Dell, Inc.
Dell, Inc.
01 70 00 00 – 01 70 FF FF16

Owner

<N/A>

Refined Handle TypeTPM

2.2.2.2

NV indices assigned by TCG per platform component level

2.2.2.2.1 Endorsement
This range contains NV Indices to support the Endorsement Hierarchy such as Endorsement Certificates,
Endorsement Key templates, etc.
Within the Endorsement Certificate range, the Infrastructure Working Group has defined specific NV Indices to allow
EK authorization. See the relevant specification for a description of each NV Index range. The following range isreserved for creating these policies.

Usage
EK Policies

Table 5: Endorsement NV Index Usages
NV Index or NV Range
Description / Specification
Policy NV Indices
01 C0 7F 0016 – 01 C0 7F FF16
TCG EK Credential Profile

2.2.2.2.2 Platform
This range contains NV Indices to support Certificates to identity the Platform such as Platform Certificates.

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 10© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

2.2.2.3 NV indices Assigned to OEMs
Component OEMs (such as chipset manufacturers), TPM OEMs, and platform OEMs, may request the TCG
Technical Committee to assign global handles for resources. The only such global handles are those defined in thisregistry.
The ranges assigned have a large address space. TCG expects to issue a minimal (ideally only one) range perregistrant. For large or complex organizations, each registrant is expected to sub-divide, if necessary, its range
amongst its various internal units.
2.2.2.3.1 NV Handles for Component OEM
Table 6 reserves the handles of global NV indices for Component OEMs. They are in the range 01C1 0000-FFFF16
stipulated by Table 2 of this registry.

Table 6: Handles for Global NV indices assigned to Component OEMs
Purpose / Registered toHandle value / Range
Intel, Corp.

01 C1 01 0016 – 01 C1 01 3F16

Cisco

01 C1 01 4016 – 01 C1 01 7F16

IBM

01 C1 01 8016 – 01 C1 01 BF16

Microsoft

01 C1 01 C016 – 01 C1 01 FF16AMD

01 C1 02 0016 – 01 C1 02 3F16

HP

01 C1 02 4016 – 01 C1 02 7F16

HPE

01 C1 02 8016 – 01 C1 02 BF16

2.2.2.3.2 NV Handles for TPM OEMs
Table 7 reserves the handles of global NV indices for TPM OEMs. They are in the range 01C2 0000-FFFF16
stipulated by Table 2 of this registry.

PurposeInfineon

Table 7: Handles for Global NV indices assigned to TPM OEMs
Handle value
01 C2 00 0016 – 01 C2 00 7F16

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 11© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

2.2.2.3.3 NV Handles for Platform OEMs
Table 8 reserves the handles of global NV indices for Platform OEMs. They are in the range 01C3 0000-FFFF16
stipulated by Table 2 of this registry.
Note: Requesters are urged to implement the lowest values within their range. This would allow splitting ranges in the future (with therequestor’s permission) if address space becomes scarce.

Purpose2.2.2.4

Table 8: Handles for Global NV indices assigned to Platform OEMs
Handle valueIntel

01 C3 01 0016 – 01 C3 01 3F16

Cisco

01 C3 01 4016 – 01 C3 01 7F16

HPE

01 C3 01 8016 – 01 C3 01 BF16

IBM

01 C3 01 C016 – 01 C3 01 FF16

Juniper

01 C3 02 0016 – 01 C3 02 3F16

General Electric

01 C3 02 4016 – 01 C3 02 7F16

Raytheon, Inc.

01 C3 02 8016 – 01 C3 02 BF16

HP

01 C3 02 C016 – 01 C3 02 FF16AMD

01 C3 03 0016 – 01 C3 03 3F16

Qualcomm

01 C3 03 4016 – 01 C3 03 7F16

NV Indices assigned by TCG for specific usages

2.2.2.4.1 General Description
Individual TCG workgroups may assign handles for specific NV Indices within the ranges defined in Table 2. The NV
Index for a particular type of object (e.g., a certificate) in one type of platform may be different from the NV Index forthe same type of object in another type of platform.

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 12© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

2.2.2.4.2 NV Indices assigned by TCG for specific usages

PurposeTable 9: NV Indices assigned by TCG for specific usages
Range

PC-Client workgroup

01 C4 00 0016 – 01 C4 FF FF16

Server workgroup

01 C5 00 0016 – 01 C5 FF FF16

Virtualized Platform workgroup

01 C6 00 0016 – 01 C6 FF FF16

MPWG

01 C7 00 0016 – 01 C7 FF FF16

Embedded workgroup

01 C8 00 0016 – 01 C8 FF FF16

Infrastructure workgroup

01 C9 00 0016 – 01 C9 FF FF16

<Reserved>

01 CA 00 0016 – 01 CF FF FF16

TPM Workgroup

01 D0 00 0016 – 01 D0 FF FF16

External Standards Development Orgs

01 D1 00 0016 – 01 D1 FF FF16

<Reserved>

01 D2 00 0016 – 01 FF FF FF16

2.2.2.4.3 Workgroup Specific Usages
2.2.2.4.3.1 NV Handles for PC Client WG
Table 10 reserves the handles of global NV indices for PC Client WGs. They are in the range 01C4 000016 – FFFF16
stipulated by Table 2 of this registry.

PurposeTable 10: NV Handles for PC Client WG
Handle value

GPIO

01 C4 00 0016 – 01 C4 00 0F16

Reserved

01 C4 00 1016 – 01 C4 00 FF16

Enhanced Peripheral Interface

01 C4 01 0016 – 01 C4 01 FF16

2.2.2.4.4 External Standards Development Organizations
This range is assigned to standards development organizations (SDO) that have requested TCG register a range of
NV indices which they will manage. These are not enforced by TCG and are not defined in a TCG specification.
These are provided for informational purposes to help various industries use the TPM.
TCG does not provide higher resolution use of the NV Indices beyond the range assigned to the SDO. The SDO is
responsible for allocating from within their assigned range for that SDO’s purposes (i.e., likely their own
specification.)Standards Development Organizations may initiate a request for an NV Index range by contacting
admin@trustedcomputinggroup.org.
Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 13© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

Assignee

Table 11 NV Handles Assigned to External Standards
Handle value

FIDO Alliance

01 D1 00 0016 – 01 D1 00 FF16

Reserved

01 D1 01 0016 – 01 D1 FF FF16

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 14© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

2.3 Key Handles
2.3.1 Key Handle Assignments
The TPM enforces bits 31-24 for all persistent keys, and enforces bit 23 to distinguish platform hierarchy keys fromstorage/endorsement hierarchy keys. However, bits 22-16, which distinguish storage from endorsement are by
convention only and are not enforced by the TPM.
The TPM 2.0 library specification Part-III section “TPM2_EvictControl” defines handles for persistent objects:
1. If auth is TPM_RH_OWNER, the handle for persistent objects is in the inclusive range of 81 00 00 00 16 to 81
7F FF FF16.
2. If auth is TPM_RH_PLATFORM, the handle for persistent objects is in the inclusive range of 81 80 00 00 16
to 81 FF FF FF16.
Table 12 of this registry states the TCG’s convention for handles of keys that have been rendered persistent via thecommand TPM2_EvictControl. Note that Table 12 reserves just part of the entire range of handles that is available
for persistent keys and reserves just the ranges for persistent primary keys. The remainder of the range of handles
for persistent keys is available for persistent non-primary keys.

Scope

Table 12: Key Handles for Persistent Objects
Hierarchy
Handle Type
Range
Storage Primary Key

81 00 00 0016 – 81 00 00 FF16

Reserved

81 00 01 0016 – 81 00 7F FF16

Available

81 00 80 0016 – 81 00 FF FF16

Endorsement PrimaryKey

81 01 00 0016 – 81 01 00 FF16

Reserved

81 01 01 0016 – 81 01 7F FF16

Available

81 01 80 0016 – 81 01 FF FF16

Infrastructure WG

81 02 00 0016 – 81 02 00 FF16

Reserved

81 02 01 0016 – 81 03 FF FF16

Platform

Platform Keys (all)81 80 00 0016 – 81 80 00 FF16

Reserved

Reserved

81 80 01 0016 – 81 FF FF FF16

Storage

Hypervisor,
Operating
System or
Applications
Endorsement

Platform

This registry assigns handle ranges for just 256 “Storage primary keys”, 256 “Endorsement primary keys”, and 256“Platform primary keys”. The handle for a particular primary key in one platform may be different to the handle forthe same type of primary key in another platform. This is because a workgroup may choose to define handles for
persistently stored primary keys that use just the cryptographic algorithms that are mandatory in that workgroup’s
specifications, for example.
Handle types marked as Reserved, should not be used as these may be designated later by TCG. Handle Types
marked as Available are for use by platform manufacturers, Hypervisor or Operating systems (or applications) but
should remain within the ranges designated as Available within the appropriate Hierarchy.

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 15© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

2.3.2 Key Handle and Certificate Handle Relationships
Unlike TPM 1.2, TPM 2.0 does not require persistent endorsement keys. They can be repeatedly created astransient keys on demand, while a persistent EK would consume scarce NV space.
If an EK is made persistent, it may be easier for software if there is a relationship between the EK persistent handle
and the EK certificate NV Index. For example, if an Endorsement Certificate within the Endorsement Certificate
range in Table 2 has an Endorsement Primary Key within Table 12 the offset of each entity could be the same withineach respective range. For example, an Endorsement Certificate at NV Index 01 C0 00 2116 (offset 2116 startingfrom the beginning of the assigned NV Index range) could have an Endorsement Primary Key at handle 81 00 00
2116 (offset 2116 starting from the beginning of the assigned key handle range).

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 16© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

3 Localities
Platform-specific workgroups request localities for stated purposes. The values of localities for those purposes are
assigned by the Technical Committee and recorded in this registry.
Localities are a scarce resource. Therefore, all assigned values must be actually used: ranges with unused values
cannot be pre-assigned to individual platform-specific workgroups.
The locality value is represented as a byte. Locality values have two separate interpretations.
1. Localities 0 through 4 are interpreted as bits in the byte with 0000 00012 representing locality 0 and 0001
00002 representing locality 4. This representation allows multiple localities to be represented in a single byte
as long as the localities are in the range of 0-4.
2. A second interpretation applies to localities above 4. These are called extended localities. For extended
localities, the locality byte is an integer value representing the locality. Because of the format for localities 04, the first extended locality is 3210. The range of extended localities is 3210-25510. An extended locality
value may indicate only one locality at a time.
Table 13 of this registry states the assignment of locality values to TCG workgroups, and the interpretation of a
locality value. Table 13 reserves all possible locality values.

Table 13: Localities Reserved for Platform-Specific Workgroups
Workgroup Defining the
Locality
Description of the locality
localityvalue
PC-Client

0016

The Static RTM, its chain of trust and its environment

0116

An environment for use by the Dynamic OS

0216

Dynamically Launched OS (Dynamic OS) “runtime”
environment

0316

Auxiliary components

0416

Trusted hardware component

Unallocated0516 – 1F16

It is impossible to implement these localities becauseof legacy constraints and the representation of
locality as a Byte

MPWG

2016

L_TEE: a locality indicating access from code within
the same TEE as the receiving TPM Mobile

2116

L_ATPM: a locality indicating access from an
Application TPM Mobile residing in the same TEE as
a Platform TPM Mobile. Used for attestation.

2216

Unknown

2316

Unknown

2416

Unknown

2416 – FF16

Reserved by the Technical Committee

Virtualized Platform
Workgroup<reserved values>

Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 17© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

4 Platform Class
Table 14 contains values used to assert the class (or type) of platform. These are just canonical numeric values
used by TCG specifications to identify a platform’s class as defined by that specification.
The values in Table 14 are stated in hexadecimal, however, the actual representation of the values including thenumber of octets and endianness is not declared in this document. The representation of these values is defined by
the specification utilizing them.
Note there are also OIDs defined to designate platform class. Those are listed in the OID registry.
Note to editor: It’s likely when Table 14 is modified the OID registry should also be modified to include the new definition.
NOTE: Adding a canonical set of string values representing Platform Class is within scope of this document, however, there ar e no
specific use cases for them therefore none are defined. If a string value (e.g., “pc_client”) is needed contact the TCG
Technical Committee.

Table 14: Platform Class Values
Comments
Example Use2

Platform Class

Value

Unclassified0016

not platform specific

TPM_PS_MAIN

PC Client

0116

PC Client (see NOTE 1)

TPM_PS_PC

PDA

0216

PDA (includes all mobile
devices that are notspecifically cell phones)

TPM_PS_PDA

CELL_PHONE

0316

Cell Phone

TPM_PS_CELL_PHONESERVER

0416

Server WG (see NOTE 1)

TPM_PS_SERVERPERIPHERAL

0516

Peripheral WG

TPM_PS_PERIPHERAL

TSS

0616

Deprecated3

TPM_PS_TSS

STORAGE

0716

Storage WG

TPM_PS_STORAGE

AUTHENTICATION

0816

Authentication WG

TPM_PS_AUTHENTICATIONEMBEDDED

0916

Embedded WG

TPM_PS_EMBEDDED

HARDCOPY

0A16

Hardcopy WG

TPM_PS_HARDCOPYINFRASTRUCTURE

0B16

Deprecated

TPM_PS_INFRASTRUCTURE

VIRTUALIZATION

0C16

Virtualization WG

TPM_PS_VIRTUALIZATION

TNC

0D16

Deprecated

TPM_PS_TNC

MULTI_TENANT

0E16

Deprecated

TPM_PS_MULTI_TENANT

2 As documented in the TPM 2 Library Specification
3 While these values indicated as Deprecated are documented in the TPM 2 Library, their use is not

anticipated.
Registry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 18© TCG 2023

Registry of Reserved TPM 2.0 Handles and Localities

Platform Class

Value

Comments

Example Use2

TC

0F16

Deprecated

TPM_PS_TC

NOTE 1: In the TCG ACPI specification PC Client has a value of 00 16 and Server has a value of 01 16 .

ENDRegistry of Reserved TPM 2.0 Handles and Localities | Version 1.2 | Revision 0.91 | 9/8/2023 | <Public Review > Page 19© TCG 2023