Hi all:
thank you very much to answer my questions.
Now I have understood the meaning of extensionContainer,I'm very glad to discuss with
you.
If I have some questions about ASN.1&BER,I will ask again.
thanks.
����
======= 2002-07-12 09:31:00 in your letter=======
>Hi,
>
>I think the answer to the first question:
>
>> >>> Is it for future use ? So shall we ignore ExtensionContainer ?
>> >>>for example :
>> >>>
>> >>> MAP-AcceptInfo ::= SEQUENCE {
>> >>> ...,
>> >>> extensionContainer ExtensionContainer OPTIONAL
>> >>> -- extensionContainer must not be used in version 2
>> >>> }
>> >>>
>> >>>��how can I decode it?
>
>is:
>
>Yes, it is for future use and was added at some point after a version 1
>definition that only contained a '...' on the end (indicating more
>extensions would follow later). For BER, this is simply decoded as an
>optional element as you would if the '...' wasn't there. Even if the
>element was not marked as optional, it needs to be decoded under the
>assumption it may not be there because if a version 1 system sends a
>message, it will not have this item in it. The rules for PER for this case
>are more complicated and special handling is required.
>
>As to the 2nd question:
>
>> VLR-Capability ::= SEQUENCE{
>> supportedCamelPhases [0] SupportedCamelPhases OPTIONAL,
>> extensionContainer ExtensionContainer OPTIONAL,
>> ... }
>>
>> if extensionContainer can ignore ,then the tag 0x30 of SEQUENCE will be
>> encode in?
>
>If extensionContainer is not present, then the entire encoding for
>ExtensionContainer (including the 0x30 tag if that type is in fact an
>untagged SEQUENCE) will not be present.
>
>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)
>
>
tong
[EMAIL PROTECTED]
2002-07-15
