Title: ADS - Unbounded ASN.1 Types PDR Reference: 97060005 Originator Reference: A044PD0A SARPs Document Reference: ADS SARPs, Section 2.2.1.4.2.1 Status: WITHDRAWN PDR Revision Date: 28/08/97 (SME Rec : ACCEPTED -> WITHDRAWN) PDR Submission Date: 27/06/97 Submitting State/Organization: Aérospatiale Submitting Author Name: Monteil, A Submitting Author E-mail Address: arnaud.monteil@avions.aerospatiale.fr Submitting Author Supplemental Contact Information: SARPs Date: IV1.1, March 97 SARPs Language: English Summary of Defect: Unbounded types are not implementable on an on-board computer. Page 233: SET OF without limited size NoncomplianceNotification ::= CHOICE { demand-ncn [0] SET OF ReportType, event-ncn [1] SET OF EventTypeContracted, periodic-ncn [2] SET OF ReportTypeAndPeriod, ... } Page 238 : SEQUENCE OF without limited size GroundSystemsUsingService ::= SEQUENCE OF IA5String (SIZE(4..8)) -- contains a sequence of ICAO facility designators Assigned SME: Sub-Volume II SME Proposed SARPs amendment: Change the ASN.1 definition above to: NoncomplianceNotification ::= CHOICE { demand-ncn [0] SET SIZE(1..7,...) OF ReportType, event-ncn [1] SET SIZE(1..11,...) OF EventTypeContracted, periodic-ncn [2] SET SIZE(1..8,...) OF ReportTypeAndPeriod, ... } GroundSystemsUsingService ::= SEQUENCE SIZE(4..Max) OF IA5String (SIZE(4..8)) -- contains a sequence of ICAO facility designators SME Recommendation to CCB: WITHDRAWN SME2 Team members considers the problem as a local issue, since the problem arises from the use of a specific tool (ASN.1 compilation + automatic code generation) in a specific environment (Aerospatiale). There is nothing wrong in the ASN.1. It seems that the problem could be fixed without modification of the ASN.1 (by using compiler specific commands, for instance). The initiator accepts to withdraw the PDR. CCB Decision: CCB-2(Langen): ACCEPTED