Hi, Once a PER range constraint gets above 64K, the constraint is effectively thrown out. So as long as the tool uses a reasonably large value, you should not have interoperability problems.
Regards, Ed Day Principal Engineer Objective Systems, Inc. [EMAIL PROTECTED] (484) 875-3020 (main) (610) 608-4930 (mobile) (610) 321-0361 (fax) (877) 307-6855 (toll-free) ----- Original Message ----- From: "Bujji krishna R B" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 03, 2001 8:20 AM Subject: RE: [ASN.1] The value of MAX > Hi , > Thanks for your reply. > But I am still not clear as to what value this MAX primitive shall take. > PER encoding depends on the subconstraints and how do I encode the > following > value x using Basic Aligned PER. > x INTEGER(0..MAX):2 > > If two implementations have two different values of MAX ,then I guess there > will be > interoperability problems. > > Thanks > krishna > > > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Conrad > > Sigona > > Sent: Monday, December 03, 2001 10:17 AM > > To: Bujji krishna R B > > Cc: [EMAIL PROTECTED] > > Subject: Re: [ASN.1] The value of MAX > > > > > > > I would like to know the value of MAX , which is an ASN.1 > > reserved word. > > > > > > For Instance : > > > x INTEGER(0..MAX), > > > > > > What value does the ASN.1 compiler assign to MAX > > > > MAX represents the largest value possible for the constrained type. Your > > definition ends up saying that x is non-negative. > > > >
