ISO/IEC 11518-1:1995
(Main)Information technology — High-Performance Parallel Interface — Part 1: Mechanical, electrical and signalling protocol specification (HIPPI-PH)
Information technology — High-Performance Parallel Interface — Part 1: Mechanical, electrical and signalling protocol specification (HIPPI-PH)
Provides the mechanical, electrical and signalling protocol specifications for an efficient simplex high-performance point-to-point interface between pieces of data-processing equipment. Facilitates the development and use of computer systems by providing a common interface at the physical and data framing layers. Provides an efficient interconnection between computers, high-performance display systems, and high-performance, intelligent block-transfer peripherals.
Technologies de l'information — Interface parallèle à haute performance — Partie 1: Spécification du protocole mécanique, électrique et de signalisation (HIPPI-PH)
General Information
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 11518-1
First edition
1995-06-01
Information technology -
High-Performance Parallel Interface -
Part 1:
Mechanical, electrical and signalling protocol
specification (H I PPI-PH)
Technologies de I’information - Interface paralkle 2 haute
Performance -
Partie 7: Sp&ification du protocole mkanique, blectrique et de
signakation (HIPP/-PH)
---------------------- Page: 1 ----------------------
lSO/IEC 11518=1:1995(E)
Page
Contents
V
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.*.
Introduction . . . . . . . . . . . . . . . . . . . . . . .
1 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
2 Definitions, editorial conventions, and abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . 1
2
.............................................................................
3 HIPP1 structure
.2
characteristics.
3.1 Configuration .
2
....................................................
3.2 Logical framing hierarchy
2
.........................................................................
4 Service interface.
2
..............................................................
4.1 Service primitives
.................................................... .3
4.2 Sequences of primitives
.3
summary.
4.3 Service primitives .
.3
.....................................................
4.4 Operational sequences
................................... .4
4.5 Initiate connection Service primitives
........................... .4
4.6 Complete the connection Service primitives
............................................ .5
4.7 Flow control Service primitives
6
..................................................
4.8 Packet Service primitives.
7
primitives .
4.9 Data transfer Service
7
...................................................
4.10 Hangup Service primitives
.8
primitives.
4.1 1 Control Service .
9
....................................................
4.1 2 Status Service primitives
........................................................ IO
5 Interface format and Signals.
................................................ IO
5.1 Physical framing hierarchy
11
5.2 Data rate Options. .
11
.............................................................
5.3 Usage of Signals
13
..............................................................
5.4 Error detection.
14
.........................................................................
6 State transitions
..................................................................... 14
6.1 State exit.
...................................................................... 14
6.2 Interlocks
............................................. 14
6.3 Source READY pseudo-code
14
.......................................
6.4 Destination READY pseudo-code
15
........................................................
6.5 Source pseudo-code
.................................................. 18
6.6 Destination pseudo-code
21
7 Timing. .
....................................................... 21
7.1 Source CLOCK Signal
................................................. 22
7.2 Destination CLOCK Signal
..................................... 22
7.3 DATA BUS and PARITY BUS timing
.................................................... 22
Signals.
7.4 Source control
22
information. .
7.5 1-Field
22
7.6 LLRC .
22
................................................
7.7 Destination control Signals
22
gaps. .
7.8 Source wait
....................................................... 22
7.9 Destination wait gaps
............................................................... 23
8 Physical characteristics
....................................... 23
8.1 Differential circuit characteristics
............................... 24
8.2 INTERCONNECT Signal characteristics
24
...............................................................
8.3 Ground Signals
24
............................................................
8.4 Reserved Signals
24
........................................................
8.5 Cable specifications
25
..............................................................
8.6 Cable grounding
25
..................................................
8.7 Connector specifications
............................................... 25
8.8 Connector pin assignments
0 ISO/IEC 1995
All rights reserved. Unless otherwise specified, no patt of this publication may be reproduced or utilized in any form or
by an means, electronie or mechanical, including photocopying and microfilm, without Permission in writing from the
publisher.
ISO/IEC Copyright Office l Case postale 56 l CH-121 1 Geneve 20 l Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
ISOAEC 11518=1:1995(E)
29
.........................................................
Annex A Waveform examples
29
...................................................................
A.l Introduction
29
..............................................
A.2 Connection and Start packet
30
.......................................................
A.3 End burst, Start burst
.................... 31
A.4 End burst, end packet, Start packet, Start burst
..................................... 31
A.5 End burst, end packet, disconnect
...................................................... 32
A.6 Illegal end termination
.......................................... 32
A.7 Rejected connection sequence
........................................... 33
A.8 Aborted connection sequence
.............................................. 34
B Implementation suggestions
Annex
34
B.l Data rate Option control .
34
....................................................
B .2 Source READY counter
34
.............................................................
B.3 1-Field sampling.
................................................................... 34
B. 4 Short bursts
................................................... 35
Switching and the 1-Field
B .5
35
................................................................
B .6 Byte ordering.
36
................................................................
Annex C Error checking
36
Byte parity .
c.1
36
............................................................................
C .2 LLRC
36
..........................................................
C .3 Burst length check
36
.........................................................
C .4 Sample LLRC circuit
38
................................
Annex D Propagation delay calculation example
38
D.l CLOCK .
.................................................................. 38
D .2 Loading data
38
....................................................................
D .3 Cable skew
38
D. 4 Setup time .
38
.......................................................................
D.5 Hold time
38
...................................................................
D .6 Tuning delay
40
..........................................................
Annex E Component Options
40
.....................................
E.l Cable availability and colour coding
40
.................................................................
E.2 Cable lengths
40
................................................
E.3 Connector alignment guide
40
.............................................
E.4 Maximum connector footprint
40
.......................................................
E.5 Connector availability
....................................................... 40
E.6 Connector jackscrew torque
............................................ 40
E. 7 Line driver and receiver availability
43
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alphabetical index
. . .
Ill
---------------------- Page: 3 ----------------------
0 ISOAEC
ISOAEC 11518=1:1995(E)
Tables
11
Table 1 Data rate Options .
....................................... 26
Table 2 Connector pin assignments
................................................... 35
Table B.l Byte assignments
...................................... 41
Table E.1 Connector wire assignments
Figures
vi
Figure 1 Control hierarchy .
2
Logical framing hierarchy .
Figure 2
...... 2
HIPPI-PH Service interface .
Figure 3
Initiate the connection Service primitives . .4
Figure 4
Complete the connection Service primitives . .4
Figure 5
Flow control Service primitives . 5
Figure 6
Packet Service primitives . 6
Figure 7
primitives . 7
Figure 8 Data transfer Service
Hangup Service primitives . .7
Figure 9
Control Service primitives . 8
Figure 10
........................................... 9
Figure 11 Status Service primitives
....................................... IO
Figure 12 Physical framing hierarchy
Interface Signal summary . IO
Figure 13
......................................................... 12
Figure 14 Data packing
..................................... 14
Figure 15 Source READY flow diagram
............................... 14
Figure 16 Destination READY flow diagram
................................................ 16
Figure 17 Source flow diagram
.......................................... 19
Figure 18 Destination flow diagram
........................... 21
Figure 19 Source driven Signals at the Source
..................... 21
Figure 20 Source driven Signals at the Destination
................................................. 23
Figure 21 Differential circuit.
I NTERCONN ECT circuit . 24
Figure 22
............................................ 27
Figure 23 Cable connector - tabs
.............................. 28
Figure 24 Bulkhead connector - receptacle
.................................. 29
Figure A.1 Typical HIPPI-PH waveforms.
.............................. 30
Figure A.2 Connect, Start packet, Start burst
.............................................. 30
Figure A.3 End burst, Start burst
........... 31
Figure A.4 End burst, end packet, Start packet, Start burst
............................ 31
Figure A.5 End burst, end packet, disconnect
32
Figure A.6 Illegal end termination .
................................. 32
Figure A.7 Rejected connection sequence
Figure A.8 Aborted connection sequence . 33
Figure B.1 Physical layer switching . 35
35
Figure B.2 Switching with intermediate nodes .
Ordered byte stream mapping . 35
Figure 8.3
Figure B.4 Bit significance within byte 0 . 35
......................................... 37
Figure C.l Parity and LLRC example
Representative LLRC circuit . 37
Figure C.2
Propagation delay example block diagram . 39
Figure D.1
Figure E.l Connector alignment guide . 42
Maximum connector footprint . 42
Fiqure E.2
iv
---------------------- Page: 4 ----------------------
0 ISOAEC
ISOAEC 115184:1995(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the Inter-
national Electrotechnical Commission) form the specialized System for
worldwide standardization. National bodies that are members of ISO or
IEC participate in the development of International Standards through
technical committees established by the respective organization to deal
with particular fields of technical activity. ISO and IEC technical com-
mittees collaborate in fields of mutual interest. Other international organ-
izations, governmental and non-governmental, in liaison with ISO and IEC,
also take part in the work.
In the field of information technology, ISO and IEC have established a joint
technical committee, ISO/IEC JTC 1. Draft International Standards adopted
by the joint technical committee are circulated to national bodies for vot-
ing. Publication as an International Standard requires approval by at least
75 % of the national bodies casting a vote.
International Standard lSO/IEC 11518-1 was prepared by Joint Technical
Committee lSO/IEC JTC 1, Information technology, Subcommittee SC 25,
In terconnection of informa tion technology equipmen t.
lSO/lEC 11518 consists of the following Parts, under the general title In-
forma Gon technology - High-Performance Parallel Interface:
- Part 7: Mechanical, electrical and signalling protocol specifica tion
(HIPP/-PH)
- Part 2: Framing Protocol (HIPP/-FP)
- Part 3: Encapsulation of ISO 8802-3 - L ogical /in k con trol pro tocol
data units (HIPP/-LE)
- Part 4: Mapping of HIPP/ to /PI device generic command sets
(Hl PP/-/ PI)
- Part 5: Memory Interface (HIPP/-MI)
- Part 6: Physical Switch Control (HIPP/-SC)
Annexes A to E of this part of ISO/IEC 11518 are for information only.
---------------------- Page: 5 ----------------------
ISOAEC 11518=1:1995(E) 0 ISO/IEC
Introduction
This part of ISO/IEC 11518 defines the physical layer of an efficient simplex high-
Performance Point-to-Point interface operating at Speeds of 800 or 1 600 Mbit/s. The
-PH abbreviation Stands for “physical layer”.
Characteristics of this HIPP1 physical layer interface include
-
Point-to-Point connections use one or two topper twisted-pair cables for distances
of up to 25 m.
-
the HIPPI-PH is a simplex interface, capable of transferring data in one direction
only. Two HIPPI-PHs may be used to implement a full-duplex interface.
-
data transfers are performed and flow controlled in increments of bursts, each burst
normally containing 256 words.
-
signalling and control sequences are kept simple, and a look-ahead flow control is
used, to allow average transfer rates for large file transfers to approach the peak
transfer rate, even over distances longer than specified for the HIPPI-PH cables.
-
the HIPPI-PH provides support for low-latency, real-time, and variable size packet
transfers.
-
the HIPPI-PH is designed to facilitate use in a circuit-switched environment. In sup-
port of this feature, a limited information field is available for subdevice addressing or
other nonspecified control functions during the connection Phase of Operation. One
round-trip cable delay is required to establish or terminate a connection.
-
the HIPPI-PH is also designed to transmit multiple packets after a connection has
been established. No round-trip cable delays are required between packets.
Figure 1 Shows the interrelationship of the different clauses of this part of ISO/IEC
11518. The upper-layer protocols and Station management protocols are not covered in
this patt of ISOAEC 11518.
-1-11111-111111111
I I
I Upper-layer and sta tion I
I I
management protocols
I
I
Service interface
(Clause 4)
I
v--
State transitions
(Clause 6)
1
Electrical Signals
(Clauses 5,7,8)
Figure 1 - Control hierarchy
vi
---------------------- Page: 6 ----------------------
ISO/lEC 11518~1:1995 (E)
INTERNATIONAL STANDARD 0 ISOAEC
Information technology -
High-Performance Parallel Interface -
Part 1:
Mechanical, electrical, and signalling protocol specification
(HIPPI-PH)
1 Scope
2.1.5 IengthAongitudinal redundancy check-
A Single word that is sent on the DATA
word (LLRC):
BUS from Source to Destination after each burst.
This part of ISO/IEC 11518 provides the mechanical,
2.1.6 optional: Features that are not required by this
electrical and signalling protocol specifications for an
part of ISO/IEC 11518. However, if any optional feature
efficient simplex high-performance Point-to-Point interface
defined by this part of ISO/IEC 11518 is implemented, it
between pieces of data-processing equipment.
shall be implemented according to this part of ISO/IEC
11518.
The interface described in this patt of ISO/IEC 11518 tan
be operated at peak data rates of 800 or 1 600 Mbit/s, over
2.1.7 packet: A data set sent from Source to Desti-
distances of up to 25 m by means of topper cabling. A
nation. A packet is composed of one or more bursts. The
distance-independent signalling protocol allows the average
HIPPI-PH specification does not limit the maximum packet
data rates to approach the peak data rates, even over
size, but a maximum size may be imposed by a given HIPPI-
distances longer than specified for the HIPPI-PH.
PH implementation, or by an upper-layer protocol.
The purpose of this part of ISO/IEC 11518 is to facilitate the
2.1.8 Service interface (SI): The means by which
development and use of Computer Systems by providing a
the HIPPI-PH provides Services to upper-layer protocols.
common interface at the physical and data framing layers.
2.1.9 Source: The equipment that transmits the data.
lt provides an efficient interconnection between Computers,
high-performance display Systems, and high-performance,
2.1 ,IO state: The current condition of the HIPPI-PH,
The interface is
intelligent block-transfer peripherals.
excluding transitions, as indicated by the control Signals.
optimized for large block transfers.
2.1 .ll Station management (SMT): The super-
visory entity that monitors and controls the HIPPI-PH.
2.1 .12 upper-layer protocol (ULP): The protocols
2 Definitions, editorial conventions, and
above the Service interface. These could be done in
abbreviations
hardware or Software, or they could be distributed between
the two.
2.1 Definitions
2.1 .13 wait: Wait is every CLOCK period when there is
no valid information on the DATA BUS. Some wait times are
For the purposes of this part of ISO/IEC 11518, the follow-
required by the HIPPI-PH signalling protocol; others may be
ing definitions apply.
the result of flow control or upper-layer protocol operations.
2.1 .l burst: A group of words, sent during contiguous
2.1 .14 word: A unit of information, consisting of 32 or
CLOCK periods. A burst may be sent by the Source for
64 bits, matthing the DATA BUS width, and transferred
each READY indication received from the Destination.
from the Source to the Destination during a CLOCK period.
Bursts contain 1 to 256 words. Bursts that contain less
than 256 words are called short bursts. A packet contains
no more than one short burst. A short burst will be either the
2.2 Editorial conventions
first or last burst of a packet.
Condition of the HIPPI-PH when
2.1.2 connection: In this patt of ISO/IEC 11518, certain terms that are proper
data transfers from Source to Destination are possible. names of Signals or similar terms are printed in upper case
to avoid possible confusion with other uses of the same
2.1.3 Destination: The equipment that receives the
words (e.g., REQUEST, CONNECT, BURST). Any lower
data.
case uses of these words have the normal technical English
meaning.
2.1.4 I-Field: A 32-bit information field sent as part of
the sequence of operations establishing a connection from
A number of conditions, sequences Parameters, events,
a Source to a Destination.
states, or similar terms are printed with the first letter of
NOTE - The contents of the I-Field are defined by an upper-layer
each word in upper case and the rest lower case (e.g.,
protocol and are not defined in this part of ISO/IEC 11518.
Source, Destination). Any lower case uses of these words
have the normal technical English meaning.
1
---------------------- Page: 7 ----------------------
0 ISOAEC
ISOAEC 11518=1:1995(E)
2.3 Abbreviations 4 Service interface
CCI Connection Control Information
This clause specifies the Services provided by HIPPI-PH.
ECL Emitter Coupled Logic
The intent is to allow ULPs to operate correctly with this
HIPPI-PH H igh-Performance Parallel I nterface -
HIPPI-PH. How many of the Services described herein are
Mechanical, electrical, and signalling protocol
Chosen for a given implementation is up to that implernentor;
specification - P hysical (Layer)
however, a set of HIPPI-PH Services must be supplied
LLRC LenghlLongitudinal Redundancy Check
sufficient to satisfy the ULP(s) being used. The Services as
PHSM Physical (layer) Station Management
defined herein do not imply any particular implementation, or
any interface.
SI Service Interface
SMT Station Management
Figure 3 Shows the relationship of the HIPPI-PH interfaces.
ULP Upper-Layer Protocol
Upper-layer
protocols
3 HIPP1 structure
WV
Data transfer
3.1 Configuration characteristics
Service interface
The HIPPI-PH has been designed in a modular fashion to
support different peak bandwidth requirements.
Station
3.1 .l 800 Mbit/s
6 HIPPI-PH
management 5
An HIPPI-PH with a DATA BUS width of 32-bit words
(SW
Management
provides 800 Mbit/s data transfer rates.
Service interface
(PHSM-.)
3.1.2 1 600 Mbit/s
An HIPPI-PH with a DATA BUS width of 64-bit words
Figure 3 - HIPPI-PH Service interface
provides 1 600 Mbit/s data transfer rates.
4.1 Service primitives
3.2 Logical framing hierarchy
The primitives, in the context of the state transitions in
Figure 2 Shows the basic organization of the information on
clause 5, are declared required or optional. Additionally,
the HIPPI-PH.
Parameters are either required, conditional, or optional. All
of the primitives and Parameters are considered as required
Once a connection is established a packet (or multiple
except where explicitly stated otherwise.
packets) tan be sent from the Source to the Destination.
Esch packet shall contain one or more bursts. Bursts shall
HIPPI-PH Service primitives are of four types.
contain 1 to 256 words. Bursts that contain less than 256
words are called short bursts. A packet shall contain no
- ßequest primitives are issued by a Service user to
more than one short burst. A short burst shall be either the
initiate a Service provided by the HIPPI-PH. In this patt of
first or last burst of a multi-burst packet.
ISO/IEC 11518, a second Request primitive of the same
name shall not be issued until the Confirm for the first
request is received.
-
Confirm primitives are issued by the HIPPI-PH to
1 E::t$t,d ( ::i-iiii?l!i IF E 1:
acknowledge a Request.
HH@
dd
dd
-
-1-m Indicate primitives are issued by the HIPPI-PH to notify
the Service user of a local event. This primitive is similar
Packet
Packet
I
in nature to an unsolicited interrupt. Note that the local
event may have been caused by a Service Request. In
dH-
#
this part of ISO/IEC 11518, a second Indicate primitive of
the same name shall not be issued until the Response for
Burst Burst
c x
the first Indicate is received.
HH
--1
-
ßesponse primitives are issued by a Service user to
256 words of 32 or 64 bits each acknowledge an Indicate.
Figure 2 - Logical framing hierarchy
2
---------------------- Page: 8 ----------------------
ISOAEC 11518=1:1995(E)
0 ISOAEC
4.2 Sequences of primitives 4.4 Operational sequences
Primitives issued by the ULP shall be serviced by the
The Order of execution of Service primitives is not arbitrary.
HIPPI-PH in the sequences defined in the state transitions
Logical and time sequence relationships exist for all
of clause 6. An implementation may present the HIPPI-PH
described Service primitives. Time sequence diagrams are
with multiple requests for Services, but the HIPPI-PH shall
used to illustrate a valid sequence. Other valid sequences
Service the requests one at a time.
may exist. The sequence of events between peer users
across the user/provider interface is illustrated. In the time
The following sequence of Service primitives is an example
sequence diagrams the HIPPI-PH users are depicted on
of normal Operation of the HIPPI-PH.
either side of the vertical bars while the HIPPI-PH acts as
the Service provider.
4.4.1 Enable the interface
The interface may be enabled using whatever
4.3 Service primitives summary
implementation dependent enabling method, if any, is
specified.
Initiate a Connection
PH-RING.Request (CCI)
4.4.2 Initiate a connection
PH RING.Confirm
PHIRING.lndicate (CCI)
PH RING primitives shall be used to initiate a connection
PH RING.Response
-
from the Source to the Destination. The Connection Control
Information (CCI) may be used for non-specified control
Complete the Connection
functions.
PH-ANSWER.Request (AcceptIReject)
PH ANSWER.Confirm
4.4.3 Complete the connection
PHIANSWER.lndicate (AcceptIReject)
PH ANSWER.Response PH ANSWER primitives shall be used to establish or reject
-
theconnection.
Flow Control
4.4.4 Enable Destination reception
PH FLOW.Request
PH-FLOW.Confirm
When it is ready, the Destination ULP may use the
PHIFLOW. Indicate (Enabled)
PH FLOW.Request primitive to indicate that it is willing to
PH FLOW.Response
-
accept bursts from the HIPPI-PH.
Packet Control
4.4.5 Start a packet
PH PACKET.Request (Begin/End)
PHIPACKET.Confirm (Accept/Reject)
PH PACKET (Begin) primitives shall be used to indicate the
PH-PACKET.Indicate (Begin/End,Status)
staz of a packet.
PH PACKET.Response
-
4.4.6 Send burst
Burst Transfer
PH-TRANSFER.Request (Length,Burst)
PH TRANSFER primitives shall be used to transfer one
PH-TRANSFER.Confirm (AcceptIReject)
hurst of a packet.
PH-TRANSFERJndicate (Status,Length,Burst)
4.4.7 Send more bursts
PH TRANSFER.Response
-
More bursts may be sent for this packet by returning to
Terminate the Connection
4.4.6.
PH HANGUP.Request
PH-HANGUP.Confirm
4.4.8 Terminate the packet
PH-HANGUP.lndicate
PH-HANGUP.Response
-
PH PACKET (End) primitives shall be used to indicate the
endof a packet.
Control Interface
PHSM-CONTROL. Request (Parameter-List)
4.4.9 Send more packets
PHSM CONTROL.Confirm (Status,Status-List)
-
More packets may be sent by returning to 4.4.5.
Interface Status
PHSM STATUS.Request
4.4.10 Terminate the connection
PHSMISTATUS.Confirm (Status)
The Source or Destination may terminate the connection by
PHSM STATUS.lndicate
using the PH-HANGUP primitives. Note that dedicated
PHSM-STATUS.Response
-
Point-to-Point HIPPI-PHs may never need to terminate the
connection once it is established, or only terminate the
connection as an error recovery process. See the
cautionary note in 5.3.6.
3
---------------------- Page: 9 ----------------------
0 ISOAEC
ISOAEC 11518=1:1995(E)
PH RING.Indicate
Initiate another connection 4.5.3 _
4.4.11
This primitive indicates to the Destination ULP an attempt
Return to 4.4.2 to initiate another connection.
by a Source ULP to establish a connection.
PH-RING.lndicate ( CCI )
Semantics -
4.5 Initiate connection Service primitives
The CCI Parameter is a 32-bit field that may be used for
Figure 4 is a diagram of these primitives. They shall be used
non-specified control operations for connection estab-
to request that a connection be established between the
This CCI may be different from the CCI
lishment.
Source and Destination.
supplied by the PH-RlNG.Request primitive due to the
action of intermediate devices, such as switches,
between the Source and Destination.
Des tina tion
Source
HIPP/-PH
ULP ULP
Issued - The HIPPI-PH shall issue this primitive to the
Destination ULP when it has received a connection
PH RING
request.
PH RING
* .Indicate Effect - The Destination ULP should accept or reject the
connection request.
PH RING
.C&nfirm
PH RING
. Response
4.5.4 PH RING.Response
-
This primitive acknowledges the PH RING.Indicate from the
-
Figure 4 - Initiate the connection
HIPPI-PH.
Service primitives
PH RING.Response
Semantics -
-
PH RING.Request
4.5.1 - The Destination ULP issues this primitive to
Issued -
acknowledge receipt of the PH-RING.Indicate.
Issued by the Source ULP to request establishment of a
connection from the Source to the Destination. In the case
Effect - The HIPPI-PH is enabled to issue another
where a previous connection attempt did not complete with
PH RING.Indicate.
-
a PH-ANSWER.Indicate, and was aborted with a Source
ULP issued PH HANGUP.Request, the Source must wait a
time Tl beforeinitiating another connection. Tl shall be a
round-trip
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.