SCBA@?>=<;:9876543210/.-,+*)('&%$#"!  х` ()‚ `^BLT TTT * normally be given in a PIXIT.*Аях мях мях.  Table: D-6/X.403Рях   аях_ЄHK nditions. This information isGЈяхaT@Y@PM available in a PIXIT and in such cases a reference to the PIXITMќях` L normally can be made in the constraints-field, if the parameterLћях.ІІІ is not fixed.Рях!ІІІ  Эях_ K In a recovery, the SessionConnectionId is used in the PConnectKџях\ H and the PAccept. This SessionConnectionId may or may not be- the CONS IMP columns in the proforma to specify the actualHўяхD 0 constraints of the implementation.0єях   аяхW C For some parameters only one value is applicable (e.g.C§яхZ F DataTransferSyntax : 0). There are other parameters (e.g.F¤яхZ F checkpointSize, RefuseReason) that may vary under variousF¤ях[¦TLРRG circumstances and run-time coan implementation should use:4¶яхЄH  аях^O J - the STATUS IMP column in the proforma to specify informationJ яхa M concerning the support of protocol elements. For convenience itMќяхb N is suggested that suppliers need only indicate with an "X" thoseNњяхK 7 protocol elements that are not supported.7іях   аях\ H Hўях-  following keys:Сях   аях8 $ M : Mandatory element$Жях7 # O : Optional element#Зях   аях\ H The pragmatic constraints of the X.400 Implementor's Guide areHўях_ K shown in the CONS STD columns of the proforma in table D-6/X.403.Kџях   аяхH 4 Suppliers of мях мях мях мях мях мях мях мях мях мяхЄHмях8 $ D.4 RTS Protocol Elements$Жях   аях\;OH The requirements of the X.400 Recommendations are shown in theHўях\ H STATUS STD column of the proforma in table D-6/X.403 using theO мях мях мях   аяхO ; Table: D-4/X.403 Table: D-5/X.403;Їях   аях мях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях мях мях;Oмяхмях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях мях мях;Oмях мях мях мях мях мях мях мях мях мях мяхЄHмяхort of serviceKџях` L elements. For convenience it is suggested that suppliers need onlyLћяхa M indicate with an "X" those service elements that are not supported.Mќях   аях мяхO¦TLРR; Table: D-2/X.403 Table: D-3/X.403;Їях   аяхa M Mќях х   аях; ' M : Mandatory parameters'Гях: & O : Optional parameters&Дях= ) C : Conditional parameters)БяхH 4 - : Not applicable service parameters4¶ях   аях^ЄHJ Suppliers of an implementation should use the IMP columns in theJ ях_O K proforma to specify information concerning the supp  аях` L Tables D-2/X.403 to D-5/X.403 are useful nevertheless because theyLћях^;OJ make sure that all the mandatory parameters are really supportedJ яхW C and because they make a static conformance review easier.C§ях   аях` L The requirements of the X.400 Recommendations are shown in the STDLћяхO ; columns of the proforma using the following keys:;Їяuse./»ях   аяхZ¦TLРRF Since all OPEN service parameters are mapped to the PConnectF¤ях\T@Y@PH protocol element (apart from Response-address and Initial-turnHўяхV B which are mandatory) there is an apparent duplication ofBЁях^ІІІJ information requested in Tables D-2/X.403 to D-5/X.403 with thatJ ях;ІІІ' requested in Table D-6/X.403.'Гях  L - Responder/Initiator-address and Initial-turn are mapped to theLћях+  SCONNECT.Уях   аях^ J - Dialogue-mode, Application-protocol and User-data are mappedJ ях2  to the PConnect.Мях   аях_ K - The parameters of the OPEN.Response and OPEN.Confirmation areKџяхC / all mapped to PAccept or PRef   аях^ J RTS service parameters are mapped to Session and Presentation asJ ях$  below:Ъях   аях` L - The parameters of the OPEN.Request and the OPEN.Indication areLћях_ЄHK mapped to the SCONNECT.Request and SCONNECT.Indication and toKџях=O ) the corresponding PConnect.)Бях   аях` мях мях мях мях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях мях мях;Oмях мях мях мях мяхG 3 D.3 RTS PICS service parameters proforma3·яхce primitives that are notD¦ях(  supported.Цях;O  аях.  Table: D-1/X.403Рях   аяхT @ @Єях мях мях мях мях мях мяхЄHмяхO мях мях мяхях8 $ M : Mandatory element$Жях7¦TLРR# O : Optional element#ЗяхT@Y@P  аях^ J Suppliers of an implementation should use the IMP columns in theJ ях_ІІІK proforma to specify information concerning the support of serviceKџях`ІІІL elements. For convenience it is suggested that suppliers need onlyLћяхX D indicate with an "X" those servictets,F¤яхYO E bits,...) or a value (32) depending on the element beingEҐях-  constrained.Сях   аяхG 3 D.2 RTS PICS service primitives proforma3·ях   аях` L The requirements of the X.400 Recommendations are shown in the STDLћяхO ; columns of the proforma using the following keys:;Їях   аnder is indicated by theJ яхO ; supplier in the column labelled "STATUS IMP",;Їях   аях^ J - the actual constraints of the implementation as initiator orJ яхa M responder are indicated by the supplier in the columns labelledMќях.  "CONST IMP".Рях   аяхZЄHF Constraints may be expressed as a length or size (o%Еях   аях\ H - any implementation constraints are indicated in the columnHўях];OI labelled "CONST STD" where constraints are interpreted as aIЎяхV B minimum for reception and a maximum for origination,BЁях   аяхS ? - the actual support of the protocol element by the?«ях^ J implementation as initiator or respo columns labelled "IMP".%Еях мях] I Information on protocol element support is requested in tabularIЎяхD¦TLРR0 form where, for each protocol element,0єяхT@Y@P  аяхb N - the status of the protocol element where the IUT is initiator orNњях\ІІІH responder is indicated as mandatory (M) or optional (O) inHўях9ІІІ% columns labelled "STD",]O I - the status of the service element is indicated as mandatoryIЎях] I (M), optional (O), conditional (C) or not applicable (-) inIЎях9 % columns labelled "STD",%Еях   аяхa M - the actual support of the service element by the implementationMќях[ G as initiator or responder is indicated by the supplier inGЈях9 % rted" if any of their parameters are notJ ях+  supported.Уях   аяхY E - A part requesting information concerning the support ofEҐях4  protocol elements. Кях   аяхa M Information on service element support is requested in tabular formMќях> * where, for each service element,*АяхЄH  аях! improperly implemented.!ЙяхІІІ  аях=ІІІ) The RTS PICS is in three parts:)Бях   аях` L - Two parts requesting information concerning the support of RTSLћях5;O! service primitives.!Йях   аях\ H If primitives have only mandatory parameters they should beHўях^ J marked as "not suppo   аяхY E The proforma RTS PICS contained in this Annex specifies theEҐях9 % information to be supplied.%Еях   аях[ G This information is needed for test case selection. SuppliersGЈях]¦TLРRI should note that tests will be performed to check that servicesIЎяхXT@Y@PD shown as not supported are in fact not present rather thanD¦ях5 Y@Pмях мяхІІІмяхІІІмях9 % Annex D RTS PICS Proformas%ЕяхЄH  аях*O  D.1 GeneralФях   аяхT @ As a prerequisite to the conformance testing of an RTS@Єях` L implementation the supplier must provide a Protocol ImplementationLћях; ' Conformance Statement (PICS).'Гях мях мях мях мях мях мях мях мях мях мяхЄHмяхO мях мях мях мях мях мях мях мях мях мях мях¦TLРRмяхT@ мях мях;Oмях мях мях мях мях мях мях мях мях мях мяхQ = Table: C-6/X.403 ProbeMPDU Proforma (part 2 of 2)=­ях   аяхa;OM Mќяхмях мяхІІІмяхІІІмях мях мяхQ = Table: C-6/X.403 ProbeMPDU Proforma (part 1 of 2)=­ях   аяхa M Mќях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях мях мях мях мях мях мях мях мях мях мяхЄHмяхO мях мях мях мях мях мях мях мях мях мях мях¦TLРRмяхT@Y@P мях мях мяхЄHмяхO мях мях мях мях мях мях мях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях мях мях;Oмях мях мях мях мяхЄHмяхO мях мях мях мях мях мях мях мях мях мях мях   аяхZ F Table: C-5/X.403 DeliveryReportMPDU Proforma (part 2 of 2)F¤ях   аях мях мях мях мях мях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях мях мях;Oмях мях мях мях мях мях мяхorma (part 1 of 2)F¤яхІІІ  аяхaІІІM Mќях мях мях;Oмях мях мях мях мях мях мях мях мях мях мяхЄHмяхO мях мяхмяхІІІмях мях мях;Oмях мях мях мях мях мях мях мях мях мях мяхЄHмяхO мях мях мях мях мяхZ F Table: C-5/X.403 DeliveryReportMPDU Prof мяхІІІмяхІІІмях мяхP < Table: C-4/X.403 UserMPDU Proforma (part 2 of 2)<®ях   аяхa M Mќях мях мях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІ мях мях мях мях мях мях мях мях мяхЄHмяхO мях мях мях мях мях мях мях мях мях мях мях¦TLРRмяхT@Y@Pмях  мях мяхЄHмяхO мях мях мях мях мях мях мях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях мях мях;Oмях мяхT@Y@Pмях мяхІІІмяхІІІмях мях мях;Oмях мях мях мях мях мях мях мяхP < Table: C-4/X.403 UserMPDU Proforma (part 1 of 2)<®ях   аях мях мях мях мяхмях мях мях мях мях мях мях мях мях мях мяхЄHмяхO мях мях мях мях мях мях мях мях мях мях мях¦TLРRмях  аях] I - the CONS IMP columns in each proforma to specify the actualIЎяхD 0 constraints of the implementation.0єях   аях мяхZ F Table: C-3/X.403 ORName and EncodedInformationType ProformaF¤ях¦TLРR  аяхT@Y@Pмях мяхІІІмяхІІІмях мях мях;O 4 Suppliers of an implementation should use:4¶ях   аях_ K - the STATUS IMP column in each proforma to specify informationKџяхa M concerning the support of protocol elements. For convenience itMќяхb N is suggested that suppliers need only indicate with an "X" thoseNњяхKЄH7 protocol elements that are not supported.7іяхO  ctions, protocol elements are indicated as mandatoryKџяхW C or optional based only on their status in the P1 protocolC§ях,;O specification.Тях   аях\ H The pragmatic constraints of the X.400 Implementor's Guide areHўях` L shown in the CONS STD columns of the proformas in Tables C-3/X.403Lћях+  to C-6/X.403.Уях   аяхH are shown in X.401 (1984) as Basic or EssentialJ ях_¦TLРRK Optional, and as optional if their corresponding service elementsKџях^T@Y@PJ are shown in X.401 (1984) as Additional Optional. Other protocolJ ях` L elements are indicated as mandatory or optional according to theirLћяхRІІІ> designation in the MPDU definitions in X.411 (1984).>¬яхІІІ  аях_ K For relay funwing keys:#Зях   аях\ H M : Mandatory element (X.401 Basic or Essential Optional)HўяхT @ O : Optional element (X.401 Additional Optional)@Єях   аях` L In the tables below protocol elements which correspond directly toLћях` L service elements are indicated as mandatory if their correspondingLћях^ J service elements M Mќях¦TLРRмяхT@Y@Pмях мяхFЄH2 C.4 MTS(P1) Protocol Elements Proformas2ёяхO   аях\ H The requirements of the X.400 Recommendations are shown in theHўяхa M STATUS STD column of the proformas in Tables C-3/X.403 to C-6/X.403Mќях7 # using the folloмях мях;Oмях мях мях мях мях мях мях мях мях мях мяхЄHмяхO мях мях мях мях мях мях мях мях мях мяхa мях мях мях мях мях мяхЄHмяхO мях мях мях мях мях мях мях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях ed that suppliers need onlyLћяхa M indicate with an "X" those service elements that are not supported.Mќях   аях мяхR > Table: C-2/X.403 MTS(P1) Service Elements Proforma.>¬ях   аяхa;OM Mќях мях мях мях мях ory element (X.401 Basic or Essential Optional)HўяхT @ O : Optional element (X.401 Additional Optional)@ЄяхE 1 - : Not applicable service element1№ях   аях^ J Suppliers of an implementation should use the IMP columns in theJ ях_ K proforma to specify information concerning the support of serviceKџях` L elements. For convenience it is suggest мях мях мях мях мях   аяхI 5 C.3 MTS(P1) PICS Service Elements Proforma5µях   аях` L The requirements of the X.400 Recommendations are shown in the STDLћяхOЄH; columns of the proforma using the following keys:;ЇяхO   аях\ H M : Mandat аяхK 7 Suppliers of an implementation should specify7іях_ K Originator/Recipient/Relay capabilities in the IMPLEMENTED columnKџях1  of Table C-1/X.403.Нях¦TLРR  аях.T@Y@P Table: C-1/X.403Рях   аях@ІІІ, ,ѕяхІІІмях мях мях;Oмяхer in the columnsF¤ях7ІІІ# labelled "CONST IMP".#ЗяхІІІ  аяхZ F Constraints may be expressed as a length or size (octets,F¤яхZ F bits,...), a value (32k-1) or a number of occurrences (4)F¤яхL;O8 depending on the element being constrained.8Іях мяхH 4 C.2 Originator/Recipient/Relay Capability4¶ях     аяхS ? - the actual support of the protocol element by the?«ях` L implementation on origination and on reception is indicated byLћяхS ? the supplier in the column labelled "STATUS IMP",?«ях¦TLРR  аяхaT@Y@PM - the actual constraints of the implementation on origination andMќяхZ F on reception is indicated by the supplicol element on origination and receptionMќяхZ F is indicated as mandatory (M) or optional (O) in columnsF¤ях1  labelled "STD",Нях   аях\ H - any implementation constraints are indicated in the columnHўях] I labelled "CONST STD" where constraints are interpreted as aIЎяхV B minimum for reception and a maximum for origination,BЁяхal support of the service element by the implementationMќях^ J on origination and reception is indicated by the supplier inJ ях9 % columns labelled "IMP".%Еях   аях] I Information on protocol element support is requested in tabularIЎяхD 0 form where, for each protocol element,0єяхЄH  аяхaO M - the status of the protoa M Information on service element support is requested in tabular formMќях> * where, for each service element,*Аях;O  аях] I - the status of the service element is indicated as mandatoryIЎях] I (M), optional (O) or not applicable (-) in columns labelledIЎях(  "STD",Цях   аяхa M - the actunted.!Йях   аях? + The MTS(P1) PICS is in two parts:+їях   аяхa M - a part requesting information concerning the support of serviceMќях+¦TLРR elements,УяхT@Y@P  аяхY E - a part requesting information concerning the support ofEҐях4ІІІ protocol elements. КяхІІІ  аяхO I The proforma MTS(P1) PICS contained in this Annex specifies theIЎях9 % information to be supplied.%Еях   аях[ G This information is needed for test case selection. SuppliersGЈях] I should note that tests will be performed to check that servicesIЎяхX D shown as not supported are in fact not present rather thanD¦ях5 ! improperly impleme