.rs .\" Troff code generated by TPS Convert from ITU Original Files .\" Not Copyright ( c) 1991 .\" .\" Assumes tbl, eqn, MS macros, and lots of luck. .TA 1c 2c 3c 4c 5c 6c 7c 8c .ds CH .ds CF .EQ delim @@ .EN .nr LL 40.5P .nr ll 40.5P .nr HM 3P .nr FM 6P .nr PO 4P .nr PD 9p .po 4P .rs \v | 5i' .ce 1000 ANNEX\ D .ce 0 .ce 1000 (to Recommendation Q.921) .sp 9p .RT .ce 0 .ce 1000 \fBState transition table of the point\(hyto\(hypoint procedures\fR .EF '% Fascicle\ VI.10\ \(em\ Rec.\ Q.921'' .OF '''Fascicle\ VI.10\ \(em\ Rec.\ Q.921 %' .sp 1P .RT .ce 0 .ce 1000 \fBof the data link layer\fR .ce 0 .PP D.1 The state transition table presented in Tables D\(hy1/Q.921 to D\(hy3/Q.921 is based on the eight basic states (see \(sc\ B.2) recognized in the SDL representation and the related transmitter and receiver conditions. .sp 1P .RT .PP The state transition table relinquishes to any partitioning of the procedures. It is conceptual and does not prevent a designer from partitioning in his implementation. Moreover, all the processes related to primitive procedures, the management of queues and the exchange of information between adjacent layers are conceptual, not visible from outside of the system and would not impose any constraints on the implementation. .PP The eight basic states apply to both the transmitter and the receiver within one data link layer entity. However, some of the conditions are confined to the transmitter (e.g.\ \*Qpeer receiver busy\*U), whilst some are confined to the receiver (e.g.\ \*QREJ recovery\*U). This implies, if the concept of non\(hypartitioning is adopted, that each transmitter condition has to be combined with each receiver condition resulting in composite states. This state transition table comprises 24\ composite states representing the 8\ basic states and the related combinations of transmitter and receiver conditions. .PP Events are defined as follows: .RT .LP a) primitives; .LP b) repertoire of frames to be received; .LP \(em unnumbered frames (SABME, DISC, UA, DM, UI, FRMR) .LP \(em supervisory frames (RR, REJ, RNR) .LP \(em information frame (I); .LP c) internal events (servicing of queues, expiry of timers, receiver busy condition). .PP The actions to be taken when an event occurs whilst in a specific state comprise: .LP i) transition to another state .LP ii) peer\(hyto\(hypeer frame to be transmitted .LP iii) primitives to be issued .LP iv) timer actions .LP v) retry counters .LP vi) state variables .LP vii) P/F bit setting .LP viii) discarding contents of queues. .sp 2P .LP D.2 \fIKey to the state transition table\fR .sp 1P .RT .sp 1P .LP D.2.1 \fIDefinition of a cell of the state transition table\fR .sp 9p .RT .LP .rs .sp 9P .ad r \fBDiagram [T17.921], p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP D.2.2 \fIKey to the contents of a cell\fR .sp 9p .RT .LP | Impossible by the definition of the data link layer service. .LP / Impossible by the definition of the peer\(hyto\(hypeer data link procedures. .LP \(em No action, no state change. .LP V(S) = V(A) = N(R) Collective term for the two actions V(S) = N(R) and V(A) = N(R). .LP Timer T200 Start timer T200 if not already running. .LP TX ACK The acknowledgement of the received I frame may be conveyed by an I\ frame associated with the information flow in the opposite direction or a supervisory response frame, as appropriate. .LP \*QDISCARD\*U Indicates the discarding of the information contained in the information field of the I\ frame. .LP (A\(hyO) The codes used in MDL\(hyERROR\(hyINDICATION signals are defined in Table\ II\(hy1/Q.921 in Appendix\ II. When multiple codes are shown, only one applies. .LP .rs .sp 10P .ad r \fBDiagram [T18.921] + Note, p.\fR .sp 1P .RT .ad b .RT .LP .rs .sp 23P .ad r blanc .ad b .RT .LP .bp .ce \fBH.T. [1T19.921]\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(342p) . TABLE\ D\(hy1/Q.921 (1 of 10) .T& cw(342p) . { \fBState transition table: receiving primitive\fR } .TE .TS cw(54p) | cw(36p) | cw(36p) | cw(36p) | cw(36p) | cw(108p) | cw(36p) . BASIC STATE TEI UNASSIGNED ASSIGN AWAITING TEI ESTABLISH AWAITING TEI TEI ASSIGNED AWAITING ESTABLISHMENT AWAITING RELEASE .T& lw(54p) | lw(36p) | lw(36p) | lw(36p) | lw(36p) | lw(36p) | lw(36p) | lw(36p) | lw(36p) . .T& lw(54p) | lw(36p) | lw(36p) | lw(36p) | lw(36p) | lw(36p) | lw(36p) | cw(36p) | lw(36p) . RECEIVER CONDITION See Note .T& lw(54p) | cw(36p) | cw(36p) | cw(36p) | cw(36p) | cw(36p) | cw(36p) | cw(36p) | cw(36p) . STATE NUMBER\fR 1 2 3 4 5.0 5.1 5.2 6 .T& lw(54p) | lw(36p) | rw(36p) | cw(36p) | lw(36p) | cw(36p) | lw(36p) | cw(36p) | cw(36p) . DL\(hyESTABLISH\(hyREQUEST { MDL\(hyASS\(hyIDN | | | | 3 \fR } | | | | | | 3 I { RC=0 TX SABME P=1 START T200 5.0 } I { | | DISC. I QUEUE | | 5.0 } I I _ .T& lw(54p) | cw(36p) | cw(36p) | cw(36p) | lw(36p) | cw(36p) | rw(36p) | cw(36p) | cw(36p) . DL\(hyRELEASE\(hyREQUEST I I I DL\(hyREL\(hyCONF I | | 5.2 I I _ .T& lw(54p) | cw(36p) | cw(36p) | cw(36p) | cw(36p) | cw(36p) | lw(36p) | cw(36p) | cw(36p) . DL\(hyDATA\(hyREQUEST I I I I I DATA INTO I QUEUE I I _ .T& lw(54p) | cw(36p) | cw(36p) | cw(36p) | cw(36p) | cw(36p) | lw(36p) | cw(36p) | cw(36p) . I FRAME IN QUEUE V(S)\ V(M)], then set V(M) equal to the N(S) of the received frame. .RT .LP .rs .sp 3P .ad r Blanc .ad b .RT .LP .bp .ce 1000 APPENDIX\ II .ce 0 .ce 1000 (to Recommendation Q.921) .sp 9p .RT .ce 0 .ce 1000 \fBOccurrence of\fR \fBMDL\(hyERROR\(hyINDICATION\fR .sp 1P .RT .ce 0 .ce 1000 \fBwithin the basic states and actions\fR .ce 0 .sp 1P .ce 1000 \fBto be taken by the management entity\fR .ce 0 .sp 1P .LP II.1 \fIIntroduction\fR .sp 1P .RT .PP Table II\(hy1/Q.921 gives the error situations in which the MDL\(hyERROR\(hyINDICATION primitive will be generated. This primitive notifies the data link layer's connection management entity of the occurred error situation. The associated error parameter contains the error code that describes the unique error conditions. Table\ II\(hy1/Q.921 also identifies the associated connection management actions to be taken from the network and the user side, based on the types of error conditions reported. .PP This appendix does not incorporate the retransmission of REJ response frames described in Appendix\ I. .RT .sp 2P .LP II.2 \fILayout of Table II\(hy1/Q.921\fR .sp 1P .RT .PP The \*QError code\*U column gives the identification value of each error situation to be included as a parameter with the MDL\(hyERROR\(hyINDICATION primitive. .PP The column entitled \*QError condition\*U together with the \*QAffected states\*U describes unique protocol error events and the basic state of the data link layer entity at the point that the MDL\(hyERROR\(hyINDICATION primitive is generated. .PP For a given error condition, the column entitled \*QNetwork management action\*U describes the preferred action to be taken by the network management entity. .PP The column entitled \*QUser management action\*U describes the preferred action to be taken by the user side management entity on a given error condition. .RT .sp 2P .LP II.3 \fIPreferred management actions\fR .sp 1P .RT .PP The various preferred layer management actions on an error situation may be described as one of the following: .RT .LP a) Error log .LP This suggests that the network side connection management entity has the preferred action of logging the event into an error counter. The length and the operation of the counter mechanisms for the error situations is implementation dependent. .LP b) TEI check .LP This means that the network side layer management entity invokes the TEI check procedure. .LP c) TEI verify .LP This means that the user side layer management entity may optionally invoke a TEI verify request procedure that asks the network side layer management entity to issue a TEI check procedure. .LP d) TEI remove .LP This means that the user side layer management entity may directly remove its TEI value from service. .PP In most of the described error situations, there is either no action to be taken on the user side layer management or the action to be taken is implementation dependent, as Table\ II\(hy1/Q.921 shows. \*QImplementation dependent\*U means that it is optional whether the user side layer management has incorporated any form of error counter to log (store) the reported event. If action is taken, the layer management has to take into account that the data link layer will have initiated a recovery procedure. .LP .rs .sp 3P .ad r Blanc .ad b .RT .LP .bp .ce \fBH.T. [T22.921]\fR .ce TABLE\ II\(hy1/Q.921 .ce \fBManagement Entity Actions for MDL Error Indications\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(36p) | cw(24p) | cw(48p) | cw(24p) | cw(48p) | cw(48p) . \fIError Type\fR \fIError Code\fR \fIError Condition\fR { \fIAffected\fR \fIstates\fR \fI(See Note\fR \fI1)\fR } { \fINetwork\fR \fIManagement Action\fR } { \fIUser\fR \fIManagement Action\fR } _ .T& cw(36p) | lw(24p) | lw(48p) | lw(24p) | lw(48p) | lw(48p) , ^ | l | l | l | l | l ^ | l | l | l | ^ | ^ , ^ | l | l | l | l | l ^ | l | l | l | l | l. { Receipt of unsolicited response A Supervisory (F = 1) 7 Error log implementation dependent B DM (F = 1) 7,8 Error log implementation dependent C UA (F = 1) 4,7,8 D UA (F = 1) 4,5,6,7,8 TEI removal procedure or TEI check procedure; then, if TEI: \(em free, remove TEI \(em single, no action \(em multiple, TEI removal procedure TEI identity verify procedure or remove TEI E Receipt of DM response (F = 0) 7,8 Error log implementation dependent } _ .T& lw(36p) | lw(24p) | lw(48p) | lw(24p) | lw(48p) | lw(48p) . Unable to convert table .TE .nr PS 9 .RT .ad r \fBTable II\(hy1/Q.921 [T22.921] + Notes, p.\fR .sp 1P .RT .ad b .RT .LP .rs .sp 6P .ad r Blanc .ad b .RT .LP .bp .ce 1000 APPENDIX\ III .ce 0 .ce 1000 (to Recommendation Q.921) .sp 9p .RT .ce 0 .sp 1P .ce 1000 \fBOptional basic access deactivation procedures\fR .sp 1P .RT .ce 0 .sp 1P .LP III.1 \fIIntroduction\fR .sp 1P .RT .PP This appendix provides one example of a deactivation procedure which can be used by the network side system management to control deactivation of the access. Figure\ III\(hy1/Q.921 provides a conceptual model of the interactions which are required for this deactivation procedure. .RT .LP .rs .sp 29P .ad r \fBFigure III\(hy1/Q.921, p.\fR .sp 1P .RT .ad b .RT .sp 2P .LP III.2 \fIDescription of the Conceptual Model\fR .sp 1P .RT .PP The monitor function uses layer 2 activity as the basis for establishing whether deactivation of the access can take place. The signal INFORMATION is used to report the layer\ 2 activity in the following manner: .RT .LP \(em INFORMATION (FREE) indicates that there is no data link connection in the multiple\(hyframe mode of operation; .LP \(em INFORMATION (IN USE) indicates that there is at least one data link connection in the mode\(hysetting or multiple\(hyframe mode of operation; and .LP \(em INFORMATION (UNIT DATA) indicates that a UI frame is about to be transmitted, or has just been received. .bp .PP Within the data link layer entity the DL\(hyESTABLISH\(hyREQUEST/INDICATION primitives and DL\(hyRELEASE\(hyINDICATION/CONFIRM mark the duration of the multiple\(hyframe mode of operation, and the MDL/DL/UNIT DATA\(hyREQUEST/INDICATION primitives mark the transmission and reception of UI\ frames. .PP A signal Status is used to represent the ability of higher layers to enable or disable the deactivation procedures: .RT .LP \(em STATUS (ENABLE) deactivation procedures enabled; and .LP \(em STATUS (DISABLE) deactivation procedures disabled. .PP The MPH\(hyDEACTIVATE\(hyREQ, MPH\(hyDEACTIVATE\(hyIND and MPH\(hyACTIVATE\(hyIND primitives are used as described in \(sc\ 4. The definition and usage of these primitives are also described in Recommendation\ I.430\ [4] which specifies layer\ 1. .PP Since, in Recommendation I.430, the usage of the MPH\(hyDEACTIVATE\(hyIND primitive is an implementation option, two cases of deactivation are described below. .PP \(sc III.3 provides a description of the deactivation procedure when the MPH\(hyDEACTIVATE\(hyIND primitive is delivered to the system management entity. .PP \(sc III.4 provides a description of the deactivation procedure when the MPH\(hyDEACTIVATE\(hyIND primitive is not delivered to the system management entity. .PP \fINote\fR \ \(em\ These procedures require that all layer 3 entities making use of the acknowledged information transfer service, must release the data link connection at an appropriate point after the completion of the information transfer. .RT .sp 2P .LP III.3 \fIDeactivation procedure with MPH\(hyDEACTIVATE\(hyIND\fR .sp 1P .RT .PP This deactivation procedure makes use of the MPH\(hyDEACTIVATE\(hyIND primitive to provide an option of layer\ 1 implementation. .PP Figure III\(hy2/Q.921 provides a state transition diagram of the deactivation procedure with the MPH\(hyDEACTIVATE\(hyIND primitive. .PP This deactivation procedure can be represented by six states: .RT .LP State 1 Information transfer not available and free; .LP (\fINo info xfer and free\fR ) .LP State 2 Information transfer available and free; .LP (\fIInfo xfer and free\fR ) .LP State 3 Information transfer available and in use; .LP (\fIInfo xfer and in use\fR ) .LP State 4 Information transfer not available and in use; .LP (\fINo info transfer and in use\fR ) .LP State 5 Information transfer interrupted and free; .LP (\fIInfo interrupted and free\fR ) .LP State 6 Information transfer interrupted and in use; .LP (\fIInfo interrupted and in use\fR ) .PP These six states are described as follows: .LP \(em State 1 represents the state where the access is assumed to be deactivated and no data link connections are in a mode setting or multiple\(hyframe mode of operation. .LP \(em State 2 represents the state where the access is activated and no data link connection is in a mode setting or multiple\(hyframe mode of operation. Timer TM01 is running, and upon its expiry, if deactivation is enabled, then an MPH\(hyDEACTIVATE\(hyREQ primitive may be issued to layer\ 1. The access is then assumed to be deactivated. .LP \(em State 3 represents the state where the access is activated and at least one data link connection is in a mode setting or multiple\(hyframe mode of operation. .bp .LP \(em State 4 represents the state where the access is regarded as being in an transient state (neither deactivated nor activated) and at least one data link connection is in a mode setting or multiple\(hyframe mode of operation. [This state can be entered, for example, due to the arrival of an INFORMATION (IN USE) signal before an MPH\(hyACTIVATE\(hyIND primitive.] .LP \(em State 5 represents the state where the access is regarded as being in a transient state (neither deactivated nor activated) and no data link connection is in a mode setting or multiple\(hyframe mode of operation. Timer TM01 is running and upon its expiry, if deactivation is enabled, then an MPH\(hyDEACTIVATE\(hyREQ primitive will be issued to layer\ 1. The access is assumed to be deactivated. .LP \(em State 6 represents the state where the access is regarded as being in the transient state (neither deactivated nor activated) and at least one data link connection is in a mode setting or multiple frame mode of operation. .PP Timer TM01 is started whenever state 2 is entered: .LP \(em on receipt of an MPH\(hyACTIVATE\(hyIND primitive in state\ 1; and .LP \(em on receipt of an INFORMATION (FREE) signal in state 3. .PP Timer TM01 is started whenever state 5 is entered: .LP \(em on receipt of an INFORMATION (FREE) signal in state 6. .PP Timer TM01 is restarted in states 2 and 3 when: .LP \(em TM01 expires while deactivation is disabled by the receipt of a STATUS (DISABLE) signal; and .LP \(em an INFORMATION (UNIT DATA) signal is received in order to allow sufficient time for current and further unacknowledged information transfer. .PP Timer TM01 has a value of ten seconds at the network side. .LP .rs .sp 30P .ad r Blanc .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure III\(hy2/Q.921, p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 2P .LP III.4 \fIDeactivation procedure without MPH\(hyDEACTIVATE\(hyIND\fR .sp 1P .RT .PP This deactivation procedure does not make use of the MPH\(hyDEACTIVATE\(hyIND primitive to provide an option of layer\ 1 implementation. Thus this procedure can be represented by only four states, i.e.\ state\ 1, state\ 2, state\ 3, and state\ 4. States\ 5 and\ 6 have disappeared. .PP Figure III\(hy3/Q.921 provides a state transition diagram of this deactivation procedure without the MPH\(hyDEACTIVATE\(hyIND primitive. .RT .LP .rs .sp 44P .ad r \fBFigure III\(hy3/Q.921, p.\fR .sp 1P .RT .ad b .RT .LP .bp .ce 1000 APPENDIX\ IV .ce 0 .ce 1000 (to Recommendation Q.921) .sp 9p .RT .ce 0 .sp 1P .ce 1000 \fBAutomatic negotiation of data link layer parameters\fR .sp 1P .RT .ce 0 .sp 1P .LP IV.1 \fIGeneral\fR .sp 1P .RT .PP Each data link layer entity has an associated data link connection management entity. The data link connection management entity has the responsibility for initializing the link parameters necessary for correct peer\(hyto\(hypeer information transport. .PP The method of initialization of the parameters follows one of the two\ methods below: .RT .LP \(em initialization to the default values as specified in \(sc 5.9; or .LP \(em initialization based on the values supplied by its peer entity. .PP The latter method utilizes the parameter negotiation procedure described in this appendix. Typically, after the assignment of a TEI value to the management entity, the data link connection management entity is notified by its layer management entity that parameter initialization is required. .PP The data link connection management entity will invoke the peer\(hyto\(hypeer notification procedure . After parameter initialization, the data link connection management entity will notify the layer management entity that parameter initialization has occurred, and the layer management entity will issue the MDL\(hyASSIGN\(hyREQUEST. .RT .sp 2P .LP IV.2 \fIParameter initialization\fR .sp 1P .RT .PP The parameter initialization procedure may invoke either the internal initialization procedure or the automatic notification of data link parameter procedure. .RT .sp 2P .LP IV.3 \fIInternal parameter initialization\fR .sp 1P .RT .PP When the layer management entity notifies the connection management entity of TEI assignment, the connection management entity shall initialize the link parameters to the default values and notify the layer management of task completion. .RT .sp 2P .LP IV.4 \fIAutomatic notification of data link layer parameter values\fR .sp 1P .RT .PP For each data link layer an exchange of certain data link layer parameters may take place between the peer data link connection management entities before entering the \fITEI\(hyassigned\fR state. This exchange may be initiated after acquiring a TEI, that is, after: .RT .LP \(em receipt of a DL\(hyESTABLISH\(hyREQUEST or a DL\(hyUNIT DATA\(hyREQUEST primitive following a power\(hyup condition associated with non\(hyautomatic TEI user equipment. .LP \(em receipt of the Identity assigned response for automatic TEI assignment user equipment. This message contains the TEI received by the layer management entity. .PP The data link connection management entity, following assignment of a TEI from the layer management entity, shall issue an XID command with the P\ bit set to 0 and containing the parameter message shown in Figure\ IV\(hy1/Q.921, and start the connection management timer\ TM20. .PP The I field of the XID command frame shall reflect the parameters desired for future communications across this data link layer connection. .PP The peer data link connection management entity, upon receipt of this XID command frame, shall transmit an XID response with the F\ bit set to 0 containing the list of parameter values that the peer can support. .bp .PP If the data link connection management entity receives the above XID response prior to expiry of timer\ TM20, it shall stop the timer, and shall notify the layer management entity of a successful parameter exchange. However, if timer\ TM20 expires before receiving the XID response, the data link connection management entity shall retransmit the XID command, increment the retransmission counter and restart timer\ TM20. This retransmission process is repeated if timer\ TM20 expires again. Should the retransmission counter equal NM20, or an XID response frame with a zero length I\ field be received, the data link connection management entity shall issue an indication to the layer management entity and initialize the parameters to the default values. The layer management entity may log this condition and then issue the MDL\(hyASSIGN\(hyREQUEST primitive to the data link layer. .PP The timer TM20 is set to 2.5 seconds and NM20 is set to\ 3. .RT .LP .rs .sp 40P .ad r \fBFigure IV\(hy3/Q.921 [T23.921], p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .ce 1000 \fBABBREVIATIONS\ AND\ ACRONYMS\ USED\ IN\ RECOMMENDATION\ Q.921\fR .sp 1P .RT .ce 0 .sp 1P .sp 2P .LP \fIAbbreviation\fR \fIMeaning\fR .sp 1P .RT .LP \fIof acronym\fR .sp 1P .LP Ai Action indicator .sp 9p .RT .LP ASP Assignment source point .LP CEI Connection endpoint identifier .LP CES Connection endpoint suffix .LP C/R Command/response field bit .LP DISC Disconnect .LP DL\(hy Communication between Layer 3 and data link layer .LP DLCI Data link connection identifier .LP DM Disconnected mode .LP EA Extended address field bit .LP ET Exchange termination .LP FCS Frame check sequence .LP FRMR Frame reject .LP I Information .LP ID Identity .LP ISDN Integrated Services Digital Network .LP L1 Layer 1 .LP L2 Layer 2 .LP L3 Layer 3 .LP LAPB Link access procedure \(em Balanced .LP LAPD Link access procedure on the D\(hychannel .LP M Modifier function bit .LP MDL\(hy Communication between management entity and data link layer .LP MPH\(hy Communication between system management and physical layer .LP N(R) Receive sequence number .LP N(S) Send sequence number .LP P/F Poll/Final bit .LP PH\(hy Communication between data link layer and physical layer .LP RC Retransmission counter .LP REC Receiver .LP REJ Reject .LP Ri Reference number .LP RNR Receive not ready .LP RR Receive ready .bp .LP S Supervisory .LP S .FS A different acronym has to be found for Supervisory function bit. .FE Supervisory function bit .LP SABME Set asynchronous balanced mode extended .LP SAP Service access point .LP SAPI Service access point identifier .LP TE Terminal equipment .LP TEI Terminal endpoint identifier .LP TX Transmit .LP U Unnumbered .LP UA Unnumbered acknowledgement .LP UI Unnumbered information .LP V(A) Acknowledge state variable .LP V(M) Recovery state variable .LP V(R) Receive state variable .LP V(S) Send state variable .LP XID Exchange identification .sp 2P .LP \fBReferences\fR .sp 1P .RT .LP [1] CCITT Recommendation Q.920 (I.440), \fIISDN user\(hynetwork interface data\fR \fIlink layer \(em General aspects\fR . .LP [2] CCITT Recommendation Q.930 (I.450), \fIISDN user\(hynetwork interface\fR \fIlayer 3 \(em General aspects\fR . .LP [3] CCITT Recommendation Q.931 (I.451), \fIISDN user\(hynetwork interface\fR \fIlayer 3 specification\fR . .LP [4] CCITT Recommendation I.430, \fIBasic user\(hynetwork interface layer 1\fR \fIspecification\fR . .LP [5] CCITT Recommendation I.431, \fIPrimary rate user\(hynetwork interface\fR \fIlayer 1 specification\fR . .LP [6] CCITT Recommendation X.25, \fIInterface between data terminal equipment\fR \fI(DTE) and data circuit terminating equipment (DCE) for terminals\fR \fIoperating in the packet mode and connected to public data networks\fR \fIby dedicated circuit\fR . .sp 1P .ce 1000 .sp 1P .RT .ce 0 .sp 1P .LP .sp 18 .bp .LP \fBMONTAGE: PAGE PAIRE = PAGE BLANCHE\fR .sp 1P .RT .LP .bp