signature.rst - NDN-TLV - Gitiles

 .. _Signature:

 Signature
 ---------

 NDN Signature is defined as two consecutive TLV blocks: ``SignatureInfo`` and ``SignatureValue``.
 The following general considerations about SignatureInfo and SignatureValue blocks that apply for all signature types:

 1. ``SignatureInfo`` is **included** in signature calculation and fully describes the signature, signature algorithm, and any other relevant information to obtain parent certificate(s), such as :ref:`KeyLocator`

 2. ``SignatureValue`` is **excluded** from signature calculation and represent actual bits of the signature and any other supporting signature material.

 ::

     Signature ::= SignatureInfo
                   SignatureBits

     SignatureInfo ::= SIGNATURE-INFO-TYPE TLV-LENGTH
                         SignatureType
                         ... (SignatureType-specific TLVs)

     SignatureValue ::= SIGNATURE-BITS-TYPE TLV-LENGTH
                         ... (SignatureType-specific TLVs and
                         BYTE+

 SignatureType
 ~~~~~~~~~~~~~

 ::

     SignatureType ::= SIGNATURE-TYPE-TYPE TLV-LENGTH
                         nonNegativeInteger


 This specification defines the following SignatureType values:

 +-------+----------------------------------------+-------------------------------------------------+
 | Value | Reference                              | Description                                     |
 +=======+========================================+=================================================+
 | 0     | :ref:`DigestSha256`                    | Integrity protection using SHA-256 digest       |
 +-------+----------------------------------------+-------------------------------------------------+
 | 1     | :ref:`SignatureSha256WithRsa`          | Integrity and provenance protection using       |
 |       |                                        | RSA signature over a SHA-256 digest             |
 +-------+----------------------------------------+-------------------------------------------------+
 | 2-200 |                                        | reserved for future assignments                 |
 +-------+----------------------------------------+-------------------------------------------------+
 | >200  |                                        | unassigned                                      |
 +-------+----------------------------------------+-------------------------------------------------+

 .. +-------+----------------------------------------+-------------------------------------------------+
 .. | 2     | :ref:`SignatureSha256WithRsaAndMerkle` | Integrity and provenance protection using       |
 .. |       |                                        | RSA signature over SHA-256-Merkle-Hash digest.  |
 .. |       |                                        |                                                 |
 .. |       |                                        | This signature type defines an aggregated       |
 .. |       |                                        | signing algorithm that reduces cost of signing  |
 .. |       |                                        | of a large segmented content (e.g., video file).|

 .. _DigestSha256:

 DigestSha256
 ^^^^^^^^^^^^

 ``DigestSha256`` provides no provenance of a Data packet or any kind of guarantee that packet is from the original source.
 This signature type is indended only for debug purposes and limited circumstances when it is necessary to protect only against unexpected modification during the transmition.

 ``DigestSha256`` is defined as a SHA256 hash of the :ref:`Name`, :ref:`MetaInfo`, :ref:`Content`, and :ref:`SignatureInfo <Signature>` TLVs:

 ::

     SignatureInfo ::= SIGNATURE-INFO-TYPE TLV-LENGTH(=3)
                         SIGNATURE-TYPE-TYPE TLV-LENGTH(=1) 0

     SignatureValue ::= BYTE{32}(=SHA256{Name, MetaInfo, Content, SignatureInfo})


 .. _SignatureSha256WithRsa:

 SignatureSha256WithRsa
 ^^^^^^^^^^^^^^^^^^^^^^

 ``SignatureSha256WithRsa`` is the basic signature algorithm that MUST be supported by any NDN-compliant software.
 As suggested by the name, it defines an RSA public key signature that is calculated over SHA256 hash of the :ref:`Name`, :ref:`MetaInfo`, :ref:`Content`, and :ref:`SignatureInfo <Signature>` TLVs.


 ::

     SignatureInfo ::= SIGNATURE-INFO-TYPE TLV-LENGTH
                         SIGNATURE-TYPE-TYPE TLV-LENGTH(=1) 1
                         KeyLocator

     SignatureValue ::= BYTE+(=RSA over SHA256{Name, MetaInfo, Content, SignatureInfo})

 .. note::

    SignatureValue size varies (typically 128 or 256 bytes) depending on the private key length used during the signing process.

 This type of signature ensures strict provenance of a Data packet, provided that the signature verifies and signature issuer is authorized to sign the Data packet.
 The signature issuer is idenfified using :ref:`KeyLocator` block in :ref:`SignatureInfo <Signature>` block of ``SignatureSha256WithRsa``.
 See :ref:`KeyLocator section <KeyLocator>` for more detail.

 .. note::

     It is application's responsibility to define rules (trust model) of when a specific issuer (KeyLocator) is authorized to sign a specific Data packet.
     While trust model is outside the scope of the current specification, generally, trust model needs to specify authorization rules between KeyName and Data packet Name, as well as clearly define trust anchor(s).
     For example, an application can elect to use hierarchical trust model :cite:`testbed-key-management` to ensure Data integrity and provenance.

     .. bibliography:: ndnspec-refs.bib

 .. .. _SignatureSha256WithRsaAndMerkle:

 .. SignatureSha256WithRsaAndMerkle
 .. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

 .. ::

 ..     SignatureInfo ::= SIGNATURE-INFO-TYPE TLV-LENGTH
 ..                         SIGNATURE-TYPE-TYPE TLV-LENGTH(=1) 2
 ..                         KeyLocator

 ..     SignatureValue ::= BYTE{32}(=RSA over SHA256{Name, MetaInfo, Content, SignatureInfo})
 ..                        Witness

 ..     Witness ::= WITNESS-TYPE TLV-LENGTH BYTE+

 .. _KeyLocator:

 KeyLocator
 ~~~~~~~~~~

 A ``KeyLocator`` specifies a name that points to another Data packet containing certificate or public key, or can be used by the specific trust model in another way to verify the the content.

 ::

     KeyLocator ::= KEY-LOCATOR-TYPE TLV-LENGTH KeyLocatorValue

     KeyLocatorValue ::= Name |
                         KeyLocatorDigest |
                         ...

     KeyLocatorDigest ::= KEY-LOCATOR-DIGEST-TYPE TLV-LENGTH BYTE+

 .. note::

     KeyLocator has meaning only for specific trust model and the current specification does not imply or suggest use of any specific trust model.
     Generally, KeyLocator should point to another Data packet which is interpreted by the trust model, but trust model can allow alternative forms of the KeyLocator.

     For example, one can define a trust model that does not interpret KeyLocator at all (KeyLocator MUST be present, but TLV-LENGTH could be 0) and uses naming conventions to infer proper public key or public key certificate for the name of the Data packet itself.
     Another possibility for the trust model is to define digest-based KeyLocatorValue (``KeyLocatorDigest``), where RSA public key will be identified using SHA256 digest, assuming that the trust model has some other means to obtain the public key.


 Changes from CCNx
 ~~~~~~~~~~~~~~~~~

 - ``Signature`` is moved to the end of Data packet.

 - ``KeyLocator`` is moved to be a part of the ``SignatureInfo`` block, if it is applicable for the specific signature type.
   The rationale for the move is to make Signature (sequence of ``SignatureInfo`` and ``SignatureValue`` TLVs) self-contained and self-sufficient.

 - Signature type (or signing method information) is expressed as an assigned integer value (with no assumed default), rather than OID.

 - Added support for cheaper signatures

 - The current specification does not define Merkle Hash Tree Aggregated Signatures, but it is expected that such (or similar) signatures will be defined in future version of this specification.
	.. _Signature:

	Signature
	---------

	NDN Signature is defined as two consecutive TLV blocks: ``SignatureInfo`` and ``SignatureValue``.
	The following general considerations about SignatureInfo and SignatureValue blocks that apply for all signature types:

	1. ``SignatureInfo`` is included in signature calculation and fully describes the signature, signature algorithm, and any other relevant information to obtain parent certificate(s), such as :ref:`KeyLocator`

	2. ``SignatureValue`` is excluded from signature calculation and represent actual bits of the signature and any other supporting signature material.

	::

	Signature ::= SignatureInfo
	SignatureBits

	SignatureInfo ::= SIGNATURE-INFO-TYPE TLV-LENGTH
	SignatureType
	... (SignatureType-specific TLVs)

	SignatureValue ::= SIGNATURE-BITS-TYPE TLV-LENGTH
	... (SignatureType-specific TLVs and
	BYTE+

	SignatureType
	~~~~~~~~~~~~~

	::

	SignatureType ::= SIGNATURE-TYPE-TYPE TLV-LENGTH
	nonNegativeInteger


	This specification defines the following SignatureType values:

	+-------+----------------------------------------+-------------------------------------------------+
	\| Value \| Reference \| Description \|
	+=======+========================================+=================================================+
	\| 0 \| :ref:`DigestSha256` \| Integrity protection using SHA-256 digest \|
	+-------+----------------------------------------+-------------------------------------------------+
	\| 1 \| :ref:`SignatureSha256WithRsa` \| Integrity and provenance protection using \|
	\| \| \| RSA signature over a SHA-256 digest \|
	+-------+----------------------------------------+-------------------------------------------------+
	\| 2-200 \| \| reserved for future assignments \|
	+-------+----------------------------------------+-------------------------------------------------+
	\| >200 \| \| unassigned \|
	+-------+----------------------------------------+-------------------------------------------------+

	.. +-------+----------------------------------------+-------------------------------------------------+
	.. \| 2 \| :ref:`SignatureSha256WithRsaAndMerkle` \| Integrity and provenance protection using \|
	.. \| \| \| RSA signature over SHA-256-Merkle-Hash digest. \|
	.. \| \| \| \|
	.. \| \| \| This signature type defines an aggregated \|
	.. \| \| \| signing algorithm that reduces cost of signing \|
	.. \| \| \| of a large segmented content (e.g., video file).\|

	.. _DigestSha256:

	DigestSha256
	^^^^^^^^^^^^

	``DigestSha256`` provides no provenance of a Data packet or any kind of guarantee that packet is from the original source.
	This signature type is indended only for debug purposes and limited circumstances when it is necessary to protect only against unexpected modification during the transmition.

	``DigestSha256`` is defined as a SHA256 hash of the :ref:`Name`, :ref:`MetaInfo`, :ref:`Content`, and :ref:`SignatureInfo <Signature>` TLVs:

	::

	SignatureInfo ::= SIGNATURE-INFO-TYPE TLV-LENGTH(=3)
	SIGNATURE-TYPE-TYPE TLV-LENGTH(=1) 0

	SignatureValue ::= BYTE{32}(=SHA256{Name, MetaInfo, Content, SignatureInfo})


	.. _SignatureSha256WithRsa:

	SignatureSha256WithRsa
	^^^^^^^^^^^^^^^^^^^^^^

	``SignatureSha256WithRsa`` is the basic signature algorithm that MUST be supported by any NDN-compliant software.
	As suggested by the name, it defines an RSA public key signature that is calculated over SHA256 hash of the :ref:`Name`, :ref:`MetaInfo`, :ref:`Content`, and :ref:`SignatureInfo <Signature>` TLVs.


	::

	SignatureInfo ::= SIGNATURE-INFO-TYPE TLV-LENGTH
	SIGNATURE-TYPE-TYPE TLV-LENGTH(=1) 1
	KeyLocator

	SignatureValue ::= BYTE+(=RSA over SHA256{Name, MetaInfo, Content, SignatureInfo})

	.. note::

	SignatureValue size varies (typically 128 or 256 bytes) depending on the private key length used during the signing process.

	This type of signature ensures strict provenance of a Data packet, provided that the signature verifies and signature issuer is authorized to sign the Data packet.
	The signature issuer is idenfified using :ref:`KeyLocator` block in :ref:`SignatureInfo <Signature>` block of ``SignatureSha256WithRsa``.
	See :ref:`KeyLocator section <KeyLocator>` for more detail.

	.. note::

	It is application's responsibility to define rules (trust model) of when a specific issuer (KeyLocator) is authorized to sign a specific Data packet.
	While trust model is outside the scope of the current specification, generally, trust model needs to specify authorization rules between KeyName and Data packet Name, as well as clearly define trust anchor(s).
	For example, an application can elect to use hierarchical trust model :cite:`testbed-key-management` to ensure Data integrity and provenance.

	.. bibliography:: ndnspec-refs.bib

	.. .. _SignatureSha256WithRsaAndMerkle:

	.. SignatureSha256WithRsaAndMerkle
	.. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

	.. ::

	.. SignatureInfo ::= SIGNATURE-INFO-TYPE TLV-LENGTH
	.. SIGNATURE-TYPE-TYPE TLV-LENGTH(=1) 2
	.. KeyLocator

	.. SignatureValue ::= BYTE{32}(=RSA over SHA256{Name, MetaInfo, Content, SignatureInfo})
	.. Witness

	.. Witness ::= WITNESS-TYPE TLV-LENGTH BYTE+

	.. _KeyLocator:

	KeyLocator
	~~~~~~~~~~

	A ``KeyLocator`` specifies a name that points to another Data packet containing certificate or public key, or can be used by the specific trust model in another way to verify the the content.

	::

	KeyLocator ::= KEY-LOCATOR-TYPE TLV-LENGTH KeyLocatorValue

	KeyLocatorValue ::= Name \|
	KeyLocatorDigest \|
	...

	KeyLocatorDigest ::= KEY-LOCATOR-DIGEST-TYPE TLV-LENGTH BYTE+

	.. note::

	KeyLocator has meaning only for specific trust model and the current specification does not imply or suggest use of any specific trust model.
	Generally, KeyLocator should point to another Data packet which is interpreted by the trust model, but trust model can allow alternative forms of the KeyLocator.

	For example, one can define a trust model that does not interpret KeyLocator at all (KeyLocator MUST be present, but TLV-LENGTH could be 0) and uses naming conventions to infer proper public key or public key certificate for the name of the Data packet itself.
	Another possibility for the trust model is to define digest-based KeyLocatorValue (``KeyLocatorDigest``), where RSA public key will be identified using SHA256 digest, assuming that the trust model has some other means to obtain the public key.


	Changes from CCNx
	~~~~~~~~~~~~~~~~~

	- ``Signature`` is moved to the end of Data packet.

	- ``KeyLocator`` is moved to be a part of the ``SignatureInfo`` block, if it is applicable for the specific signature type.
	The rationale for the move is to make Signature (sequence of ``SignatureInfo`` and ``SignatureValue`` TLVs) self-contained and self-sufficient.

	- Signature type (or signing method information) is expressed as an assigned integer value (with no assumed default), rather than OID.

	- Added support for cheaper signatures

	- The current specification does not define Merkle Hash Tree Aggregated Signatures, but it is expected that such (or similar) signatures will be defined in future version of this specification.