Commits (3)
......@@ -57,7 +57,7 @@ IMPORTS
FROM Ieee1609Dot2BaseTypes {iso(1) identified-organization(3) ieee(111)
standards-association-numbered-series-standards(2) wave-stds(1609) dot2(2)
base(1) base-types(2) major-version-2(2) minor-version-4(4)}
--WITH SUCCESSORS
WITH SUCCESSORS
EtsiOriginatingHeaderInfoExtension
FROM EtsiTs103097ExtensionModule {itu-t(0) identified-organization(4) etsi(0)
......@@ -199,7 +199,7 @@ ToBeSignedData ::= SEQUENCE {
* structure contains at least one of the optional elements, and may contain
* more than one. See 5.2.4.3.4 for more details.
* The security profile in Annex C allows an implementation of this standard
* to state which forms of SignedDataPayload are supported by that
* to state which forms of SignedDataPayload are supported by that
* implementation, and also how the signer and verifier are intended to obtain
* the external data for hashing. The specification of an SDEE that uses
* external data is expected to be explicit and unambiguous about how this
......@@ -369,14 +369,14 @@ MissingCrlIdentifier ::= SEQUENCE {
*
* @param tlsHandshake: indicates that the Signed SPDU is not to be directly
* consumed as an application PDU and is to be used to provide information
* about the holders permissions to a Transport Layer Security (TLS)
* about the holders permissions to a Transport Layer Security (TLS)
* (IETF 5246 [B15], IETF 8446 [B16]) handshake process operating to secure
* communications to an application process. See IETF [B15] and ISO 21177
* [B20] for further information.
*
* @param iso21177ExtendedAuth: indicates that the Signed SPDU is not to be
* directly consumed as an application PDU and is to be used to provide
* additional information about the holders permissions to the ISO 21177
* additional information about the holders permissions to the ISO 21177
* Security Subsystem for an application process. See ISO 21177 [B20] for
* further information.
*
......@@ -544,7 +544,7 @@ Countersignature ::= Ieee1609Dot2Data (WITH COMPONENTS {...,
/**
* @brief This data structure encodes data that has been encrypted to one or
* more recipients using the recipients public or symmetric keys as
* more recipients using the recipients public or symmetric keys as
* specified in 5.3.4.
*
* @param recipients: contains one or more RecipientInfos. These entries may
......@@ -694,7 +694,7 @@ SymmRecipientInfo ::= SEQUENCE {
* - If the containing RecipientInfo structure indicates
* signedDataRecipInfo, this field contains the HashedId8 of the
* Ieee1609Dot2Data of type signedData that contained the encryption key,
* with that Ieee��1609Dot2��Data canonicalized per 6.3.4. The HashedId8 is
* with that Ieee1609Dot2Data canonicalized per 6.3.4. The HashedId8 is
* calculated with the hash algorithm determined as specified in 5.3.9.5.
* - If the containing RecipientInfo structure indicates rekRecipInfo, this
* field contains the HashedId8 of the COER encoding of a PublicEncryptionKey
......@@ -767,7 +767,7 @@ SymmetricCiphertext ::= CHOICE {
* @note In the name of this structure, "One28" indicates that the
* symmetric cipher block size is 128 bits. It happens to also be the case
* that the keys used for both AES-128-CCM and SM4-CCM are also 128 bits long.
* This is, however, not what One28 refers to. Since the cipher is used in
* This is, however, not what One28 refers to. Since the cipher is used in
* counter mode, i.e., as a stream cipher, the fact that that block size is 128
* bits affects only the size of the MAC and does not affect the size of the
* raw ciphertext.
......@@ -1324,7 +1324,7 @@ Ieee1609HeaderInfoExtensions EXT-TYPE ::= {
* AppExtension type is associated with consistency conditions, specific to
* that extension, that govern its consistency with SPDUs signed by the
* certificate holder and with the CertIssueExtensions in the CA certificates
* in that certificate holders chain. Those consistency conditions are
* in that certificate holders chain. Those consistency conditions are
* specified for each individual AppExtension below.
*/
SequenceOfAppExtensions ::= SEQUENCE (SIZE(1..MAX)) OF AppExtension
......@@ -1353,7 +1353,7 @@ AppExtension ::= SEQUENCE {
* specific to that extension, that govern its consistency with
* AppExtensions in certificates issued by the certificate holder and with
* the CertIssueExtensions in the CA certificates in that certificate
* holders chain. Those consistency conditions are specified for each
* holders chain. Those consistency conditions are specified for each
* individual CertIssueExtension below.
*/
SequenceOfCertIssueExtensions ::=
......@@ -1390,7 +1390,7 @@ CertIssueExtension ::= SEQUENCE {
* specific to that extension, that govern its consistency with
* AppExtensions in certificates issued by the certificate holder and with
* the CertRequestExtensions in the CA certificates in that certificate
* holders chain. Those consistency conditions are specified for each
* holders chain. Those consistency conditions are specified for each
* individual CertRequestExtension below.
*/
SequenceOfCertRequestExtensions ::= SEQUENCE (SIZE(1..MAX)) OF CertRequestExtension
......
......@@ -6,7 +6,7 @@
## Imports:
* **[Ieee1609Dot2BaseTypes](Ieee1609Dot2BaseTypes.md)** *{iso(1) identified-organization(3) ieee(111) standards-association-numbered-series-standards(2) wave-stds(1609) dot2(2) base(1) base-types(2) major-version-2(2) minor-version-4(4)}*<br/>
* **[Ieee1609Dot2BaseTypes](Ieee1609Dot2BaseTypes.md)** *{iso(1) identified-organization(3) ieee(111) standards-association-numbered-series-standards(2) wave-stds(1609) dot2(2) base(1) base-types(2) major-version-2(2) minor-version-4(4)} WITH SUCCESSORS*<br/>
* **[EtsiTs103097ExtensionModule](EtsiTs103097ExtensionModule.md)** *{itu-t(0) identified-organization(4) etsi(0) itsDomain(5) wg5(5) secHeaders(103097) extension(2) major-version-1(1) minor-version-1(1)}*<br/>
......@@ -196,7 +196,7 @@ This structure contains the data payload of a ToBeSignedData. This
structure contains at least one of the optional elements, and may contain
more than one. See 5.2.4.3.4 for more details.
The security profile in Annex C allows an implementation of this standard
to state which forms of Signed�Data�Payload are supported by that
to state which forms of SignedDataPayload are supported by that
implementation, and also how the signer and verifier are intended to obtain
the external data for hashing. The specification of an SDEE that uses
external data is expected to be explicit and unambiguous about how this
......@@ -621,7 +621,7 @@ Countersignature ::= Ieee1609Dot2Data (WITH COMPONENTS {...,
### <a name="EncryptedData"></a>EncryptedData
This data structure encodes data that has been encrypted to one or
more recipients using the recipients� public or symmetric keys as
more recipients using the recipients public or symmetric keys as
specified in 5.3.4.
Fields:
......@@ -796,7 +796,7 @@ Fields:
- If the containing RecipientInfo structure indicates
signedDataRecipInfo, this field contains the HashedId8 of the
Ieee1609Dot2Data of type signedData that contained the encryption key,
with that Ieee��1609�Dot2��Data canonicalized per 6.3.4. The HashedId8 is
with that Ieee1609Dot2Data canonicalized per 6.3.4. The HashedId8 is
calculated with the hash algorithm determined as specified in 5.3.9.5.
- If the containing RecipientInfo structure indicates rekRecipInfo, this
field contains the HashedId8 of the COER encoding of a PublicEncryptionKey
......@@ -904,7 +904,7 @@ Fields:
NOTE:&emsp;In the name of this structure, "One28" indicates that the
symmetric cipher block size is 128 bits. It happens to also be the case
that the keys used for both AES-128-CCM and SM4-CCM are also 128 bits long.
This is, however, not what �One28� refers to. Since the cipher is used in
This is, however, not what One28 refers to. Since the cipher is used in
counter mode, i.e., as a stream cipher, the fact that that block size is 128
bits affects only the size of the MAC and does not affect the size of the
raw ciphertext.
......@@ -1590,7 +1590,7 @@ This structure contains any AppExtensions that apply to the
AppExtension type is associated with consistency conditions, specific to
that extension, that govern its consistency with SPDUs signed by the
certificate holder and with the CertIssueExtensions in the CA certificates
in that certificate holder�s chain. Those consistency conditions are
in that certificate holders chain. Those consistency conditions are
specified for each individual AppExtension below.
```asn1
SequenceOfAppExtensions ::= SEQUENCE (SIZE(1..MAX)) OF AppExtension
......@@ -1630,7 +1630,7 @@ This field contains any CertIssueExtensions that apply to the
specific to that extension, that govern its consistency with
AppExtensions in certificates issued by the certificate holder and with
the CertIssueExtensions in the CA certificates in that certificate
holder�s chain. Those consistency conditions are specified for each
holders chain. Those consistency conditions are specified for each
individual CertIssueExtension below.
```asn1
SequenceOfCertIssueExtensions ::=
......@@ -1681,7 +1681,7 @@ This field contains any CertRequestExtensions that apply to the
specific to that extension, that govern its consistency with
AppExtensions in certificates issued by the certificate holder and with
the CertRequestExtensions in the CA certificates in that certificate
holder�s chain. Those consistency conditions are specified for each
holders chain. Those consistency conditions are specified for each
individual CertRequestExtension below.
```asn1
SequenceOfCertRequestExtensions ::= SEQUENCE (SIZE(1..MAX)) OF CertRequestExtension
......