Question: When decoding RRC message PDUs containing ASN.1 Contents Constraints (e.g., 'CONTAINING'), what is the recommended approach to handle potential errors in the contained type?
Option 1: Automatically decode the entire PDU, relying on error correction mechanisms to handle any mistakes.
Option 2: Decode the outer PDU first, then separately decode the contained type nested within (e.g., OCTET STRING or BIT STRING).
Option 3: Reject the entire RRC message if any error is detected in the decoding of the contained type.
Option 4: Ignore Contents Constraints and treat all types as unconstrained for simplicity.
Explanation: This approach (decoding the outer PDU first, then the contained type separately) is recommended to prevent errors in the contained type from causing the entire RRC message PDU decoding to fail, ensuring more robust error handling in telecom networks.