ISO/IEC 23001-7:2012/Amd 1:2012
(Amendment)Information technology — MPEG systems technologies — Part 7: Common encryption in ISO base media file format files — Amendment 1: AES-CBC-128 and key rotation
Information technology — MPEG systems technologies — Part 7: Common encryption in ISO base media file format files — Amendment 1: AES-CBC-128 and key rotation
Technologies de l'information — Technologies des systèmes MPEG — Partie 7: Cryptage commun des fichiers au format de fichier de médias de la base ISO — Amendement 1: AES-CBC-128 et rotation de la clé
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 23001-7
First edition
2012-02-01
AMENDMENT 1
2012-11-01
Information technology — MPEG systems
technologies —
Part 7:
Common encryption in ISO base media
file format files
AMENDMENT 1: AES-CBC-128 and key
rotation
Technologies de l'information — Technologies des systèmes MPEG —
Partie 7: Cryptage commun des fichiers au format de fichier de médias
de la base ISO
AMENDEMENT 1: AES-CBC-128 et rotation de la clé
Reference number
ISO/IEC 23001-7:2012/Amd.1:2012(E)
©
ISO/IEC 2012
---------------------- Page: 1 ----------------------
ISO/IEC 23001-7:2012/Amd.1:2012(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2012
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 x CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2012 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 23001-7:2012/Amd.1:2012(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
Amendment 1 to ISO/IEC 23001-7:2012 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia
information.
© ISO/IEC 2012 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 23001-7:2012/Amd.1:2012(E)
Information technology — MPEG systems technologies —
Part 7:
Common encryption in ISO base media file format files
AMENDMENT 1: AES-CBC-128 and key rotation
Page 2, 3.2
Add the following abbreviated term:
AES-CBC AES Cipher-Block Chaining Mode as specified in Recommendation of Block Cipher Modes of
Operation, NIST, NIST Special Publication 800-38A
Page 2, Clause 4
Replace the first bullet with the following:
x The scheme_type field is set to a value of ‘cenc’ (Common Encryption). As an optional alternative,
AES-CBC may be used in which case the scheme_type field shall be set to the value `cbc1’.
Page 2, Clause 5
Replace the introductory sentence with the following:
The encryption metadata defined by schemes conforming to this standard can be categorized as follows:
Page 4, 8.1
Replace 8.1 with the following:
8.1 Protection System Specific Header Box
8.1.1 Definition
Box Type: `pssh’
Container: Movie (‘moov’) or Movie Fragment (‘moof’)
Mandatory: No
Quantity: Zero or more
This box contains information needed by a Content Protection System to play back the content. The data
format is specified by the system identified by the ‘pssh’ parameter SystemID, and is considered opaque
for the purposes of this specification. The collection of Protection System Specific Header boxes from the
initial movie box, together with those in a movie fragment, shall provide all the required Content Protection
System information to decode that fragment.
© ISO/IEC 2012 – All rights reserved 1
---------------------- Page: 4 ----------------------
ISO/IEC 23001-7:2012/Amd.1:2012(E)
The data encapsulated in the Data field may be read by the identified Content Protection System client to
enable decryption key acquisition and decryption of media data. For license/rights-based systems, the header
information may include data such as the URL of license server(s) or rights issuer(s) used, embedded
licenses/rights, embedded keys(s), and/or other protection system specific metadata.
A single file may be constructed to be playable by multiple key and digital rights management (DRM) systems,
by including Protection System Specific Header boxes for each system supported. In order to find all of the
Protection System Specific data that is relevant to a sample in the presentation readers shall:
x Examine all Protection System Specific Header boxes in the Movie Box and in the Movie Fragment
Box associated with the sample (but not those in other Movie Fragment Boxes).
x Match the SystemID field in this box to the SystemID(s) of the DRM System(s) they support
x Match the KID associated with the sample (either from the default_KID field of the Track
Encryption Box or the KID field of the appropriate sample group description entry) with one of the KID
values in the Protection System Specific Header Box. Boxes without a list of applicable KID values, or
with an empty list, shall be considered to apply to all KIDs in the file or movie fragment.
Protection System Specific Header data shall be associated with a sample based on a matching KID value in
the ‘pssh’ and sample group description or default ‘tenc’ describing the sample. If a sample or set of samples
is moved due to file defragmentation or refragmentation or removed by editing, then the associated Protection
System Specific Header boxes for the remaining samples shall be stored following the above requirements.
NOTE Multiple Protection System Specific Header boxes may be associated with a given KID and SystemID.For
storage efficiency, Protection System Specific Header boxes containing the same KID(s) and SystemID should not be
duplicated in a movie fragment or movie box resulting from defragmentation or refragmentation.
8.1.2 Syntax
aligned(8) class ProtectionSystemSpecificHeaderBox extends FullBox(‘pssh’,
version, flags=0)
{
unsigned int(8)[16] SystemID;
if (version > 0)
{
unsigned int(32) KID_count;
{
unsigned int(8)[16] KID;
} [KID_count]
}
unsigned int(32) DataSize;
unsigned int(8)[DataSize] Data;
}
8.1.3 Semant
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.