Commit 546a662e authored by YannGarcia's avatar YannGarcia
Browse files

Building AtsPki with latest version of IEEE1609.2.1 ASN files

parent e73196f1
Loading
Loading
Loading
Loading
Loading
+9 −9
Original line number Diff line number Diff line
@@ -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 Signed¬Data¬Payload are supported by that 
 * to state which forms of Signed�Data�Payload 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 holder’s permissions to a Transport Layer Security (TLS) 
 * about the holder�s 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 holder’s permissions to the ISO 21177 
 * additional information about the holder�s 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¬¬1609¬Dot2¬¬Data canonicalized per 6.3.4. The HashedId8 is 
 * with that Ieee��1609�Dot2��Data 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 holder’s chain. Those consistency conditions are 
 * in that certificate holder�s 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 
 * holder’s chain. Those consistency conditions are specified for each 
 * holder�s 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 
 * holder’s chain. Those consistency conditions are specified for each 
 * holder�s chain. Those consistency conditions are specified for each 
 * individual CertRequestExtension below.
 */
SequenceOfCertRequestExtensions ::= SEQUENCE (SIZE(1..MAX)) OF CertRequestExtension
+5 −5
Original line number Diff line number Diff line
@@ -317,7 +317,7 @@ CircularRegion ::= SEQUENCE {
}

/**
 * @brief This structure specifies a “rectangle” on the surface of the WGS84 ellipsoid where the 
 * @brief This structure specifies a �rectangle� on the surface of the WGS84 ellipsoid where the 
 * sides are given by lines of constant latitude or longitude. 
 * A point which contains an elevation component is considered to be within the rectangular region 
 * if its horizontal projection onto the reference ellipsoid lies within the region. 
@@ -427,8 +427,8 @@ SequenceOfIdentifiedRegion ::= SEQUENCE OF IdentifiedRegion
 * area identifier as defined by the United Nations Statistics Division in 
 * October 2013 (see normative references in Clause 0).
 * A conformant implementation that implements IdentifiedRegion shall 
 * recognize (in the sense of “be able to determine whether a two dimensional 
 * location lies inside or outside the borders identified by”) at least one 
 * recognize (in the sense of �be able to determine whether a two dimensional 
 * location lies inside or outside the borders identified by�) at least one 
 * value of UnCountryId. The Protocol Implementation Conformance Statement 
 * (PICS) provided in Annex A allows an implementation to state which 
 * UnCountryId values it recognizes.
@@ -510,8 +510,8 @@ CountryAndRegions ::= SEQUENCE {
 * shall support a regionAndSubregions field containing at least eight 
 * entries.
 * A conformant implementation that implements this type shall recognize 
 * (in the sense of “be able to determine whether a two dimensional location 
 * lies inside or outside the borders identified by”) at least one value of 
 * (in the sense of �be able to determine whether a two dimensional location 
 * lies inside or outside the borders identified by�) at least one value of 
 * country and at least one value for a region within the country indicated 
 * by that recognized country value. In this version of this standard, the 
 * only means to satisfy this is for a conformant implementation to recognize