> & does the CONSTRAINED BY which is a user-defined constraint, can it
> be ignored here?
I think the anwser may be yes. According to the ASN.1 standard X.682, user-defined
constraint is
equivalent to a special ASN.1 comment. If you are designing a general testing device,
ignoring
the user-defined constraint is a good idea because the general tool can not deal with
it easily.
However, if you are constructing a tool to handle the H.323 protocol suite specially,
you may
need the constraint and develop a special H.323 tool to extract the constraint and
handle it.
Author Name: Wang Hao
Phone:+86-755-89650628
EMail:[EMAIL PROTECTED]
*****************************************************************
This e-mail and its attachments contain confidential information from HUAWEI, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or
partial disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the
sender by phone or email immediately and delete it!
*****************************************************************
----- Original Message -----
From: "nav b" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, October 30, 2004 12:24 AM
Subject: [ASN1] <REAL> How to define SIGNED{ToBeSigned} ::= ..& otherH.235structures
> sorry i had to resend cos few of them had problem with my domain
>
> In the ITU-T Recommendation H.235 I found the ASN.1 expression
>
> SIGNED { ToBeSigned } ::= SEQUENCE {
> toBeSigned ToBeSigned,
> algorithmOID OBJECT IDENTIFIER,
> paramS Params, -- any "runtime" parameters
> signature BIT STRING -- could be an RSA or an ASN.1
>
> coded ECGDSASignature
> } ( CONSTRAINED BY { -- Verify or Sign Certificate -- } )
>
> this is my understanding of above structure
> N::= SIGNED { XYZ }
>
> is equalent of
>
> N::=SEQUENCE
> {
> toBeSigned XYZ,
> algorithmOID OBJECT IDENTIFIER,
> paramS Params, -- any "runtime" parameters
> signature BIT STRING -- could be an RSA or an ASN.1
>
> coded ECGDSASignature
> } ( CONSTRAINED BY { -- Verify or Sign Certificate -- } )
>
> is my understanding right?
>
> & does the CONSTRAINED BY which is a user-defined constraint, can it
> be ignored here?
>
> ENCRYPTED { ToBeEncrypted } ::= SEQUENCE {
> algorithmOID OBJECT IDENTIFIER,
> paramS Params, -- any "runtime" parameters
> encryptedData OCTET STRING
> } ( CONSTRAINED BY { -- Encrypt or Decrypt -- ToBeEncrypted } )
>
> HASHED { ToBeHashed } ::= SEQUENCE {
> algorithmOID OBJECT IDENTIFIER,
> paramS Params, -- any "runtime" parameters
> hash BIT STRING
> } ( CONSTRAINED BY { -- Hash -- ToBeHashed } )
>
> the ENCRYPTED & HASHED structures, also have same issues as SIGNED
>
> Thanks a lot
>
> Naveen Kumar B K
> Encore Software Limited
> _______________________________________________
> ASN1 mailing list
> [EMAIL PROTECTED]
> http://lists.asn1.org/mailman/listinfo/asn1
_______________________________________________
ASN1 mailing list
[EMAIL PROTECTED]
http://lists.asn1.org/mailman/listinfo/asn1
