As you have doubted this is not permitted by ASN.1. The extension marker act as a place holder following which elements are added one after another. The spec is as such not incorrect, but then the 2 versions don't have version compatibility between them. And the idea of having the extensibility marker is to make communication possible between two versions which is defeated in the case explained.

Regd.
Ramaswamy

[EMAIL PROTECTED] wrote:

The extension in Version 2 is specified after h245SecuityMode, however in version 4 (11/2002) the extension is specified after fastStart field, can someone help on confirming the following syntax in v4:

Progress-UUIE ::= SEQUENCE
{
protocolIdentifier ProtocolIdentifier,
destinationInfo EndpointType,
h245Address TransportAddress OPTIONAL,
callIdentifier CallIdentifier,
h245SecurityMode H245Security OPTIONAL,
tokens SEQUENCE OF ClearToken OPTIONAL, cryptoTokens SEQUENCE OF CryptoH323Token OPTIONAL,
fastStart SEQUENCE OF OCTET STRING OPTIONAL,
...,
multipleCalls BOOLEAN,
maintainConnection BOOLEAN,
fastConnectRefused NULL OPTIONAL
}


Thanks

Ken





-- Hi ,

Regds
Ram
--------------------------------------------------------------------------------
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a 
touch of genius -- and a lot of courage -- to move in the opposite direction." - Albert 
Einstein
--------------------------------------------------------------------------------
Information contained and transmitted by this E-MAIL is proprietary to
Synergy Infotech Private Limited and is intended for use only by the
individual or entity to which it is addressed, and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law. If this is a forwarded message, the content of this E-MAIL may not have
been sent with the authority of the Company. If you are not the intended
recipient, an agent of the intended recipient or a  person responsible for
delivering the information to the named recipient,  you are notified that any
use, distribution, transmission, printing, copying or dissemination of this
information in any way or in any manner is strictly prohibited. We have taken
precautions to minimize the risk of transmitting software viruses, but we
advise you to carry out your own virus checks on any attachment to this
message. We cannot accept liability for any loss or damage caused by software
viruses. If you have received this communication in error, please delete this
mail & notify us immediately at mailto:[EMAIL PROTECTED]





Reply via email to