Lower Layer Q and X Protocol
Lower Layer Q and X Protocol
Lower Layer Q and X Protocol
ITU-T
TELECOMMUNICATION
STANDARDIZATION SECTOR
OF ITU
Q.811
(02/2004)
Q.1Q.3
Q.4Q.59
Q.60Q.99
Q.100Q.119
Q.120Q.499
Q.500Q.599
Q.600Q.699
Q.700Q.799
Q.800Q.849
Q.850Q.999
Q.1000Q.1099
Q.1100Q.1199
Q.1200Q.1699
Q.1700Q.1799
Q.1900Q.1999
Q.2000Q.2999
Summary
This Recommendation provides the lower layer protocol profiles for the Q and X interfaces as
defined in ITU-T Rec. M.3010. It also provides a method for interworking.
Source
ITU-T Recommendation Q.811 was approved on 13 February 2004 by ITU-T Study Group 4
(2001-2004) under the ITU-T Recommendation A.8 procedure.
FOREWORD
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of
telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of
ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations
on them with a view to standardizing telecommunications on a worldwide basis.
The World Telecommunication Standardization Assembly (WTSA), which meets every four years,
establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these
topics.
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
In some areas of information technology which fall within ITU-T's purview, the necessary standards are
prepared on a collaborative basis with ISO and IEC.
NOTE
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a
telecommunication administration and a recognized operating agency.
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain
mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the
Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some
other obligatory language such as "must" and the negative equivalents are used to express requirements. The
use of such words does not suggest that compliance with the Recommendation is required of any party.
ITU 2004
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the
prior written permission of ITU.
ii
CONTENTS
Page
1
Scope ............................................................................................................................
References ....................................................................................................................
Abbreviations ...............................................................................................................
DCN model...................................................................................................................
4.1
CONS1 ...........................................................................................................
4.2
CONS2, CONS3, CLNS3 ..............................................................................
4.3
CLNS1............................................................................................................
4.4
CLNS2............................................................................................................
4.5
CONS6 ...........................................................................................................
4.6
IP ....................................................................................................................
8
8
8
8
8
9
9
9
9
10
11
16
21
22
23
23
26
27
27
27
28
29
29
30
Annex A Protocol stack for information transfer over ISDN transparent B-channel..........
A.1
Introduction ....................................................................................................
A.2
Network profile CONS4.................................................................................
32
32
32
35
36
iii
Scope
the requirements at the layer 3/layer 4 service boundary for any network used to support the
Q and X interfaces of the TMN.
This Recommendation conforms to the "T" profiles in framework for International Standardized
Profiles (ISP) as specified in ISO/IEC TR 10000-1 [63] and ISO/IEC TR 10000-2 [64]. Profiles in
this Recommendation align with equivalent ISPs (as specified in conformance clause) if available.
It is the intention to align those profiles for which there are no equivalent ISPs at present to ISPs as
they are standardized by ISO SGFS.
2
References
The following ITU-T Recommendations and other references contain provisions which, through
reference in this text, constitute provisions of this Recommendation. At the time of publication, the
editions indicated were valid. All Recommendations and other references are subject to revision;
users of this Recommendation are therefore encouraged to investigate the possibility of applying the
most recent edition of the Recommendations and other references listed below. A list of the
currently valid ITU-T Recommendations is regularly published. The reference to a document within
this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
[1]
[2]
ITU-T Recommendation Q.812 (2004), Upper layer protocol profiles for the Q and
X interfaces.
[3]
____________________
1
This protocol is also applicable to the Qx interface when a full seven layer stack is required.
ITU-T Rec. Q.811 (02/2004)
[4]
[5]
[6]
[7]
[8]
[9]
[10]
[11]
[12]
ITU-T Recommendation X.25 (1996), Interface between Data Terminal Equipment (DTE)
and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode
and connected to public data networks by dedicated circuit.
[13]
[14]
[15]
[16]
[17]
ITU-T Recommendation X.223 (1993) | ISO/IEC 8878:1992, Use of X.25 to provide the
OSI connection-mode Network service for ITU-T applications.
[18]
[19]
ITU-T Recommendation X.121 (2000), International numbering plan for public data
networks.
[20]
[21]
[22]
[23]
[24]
ITU-T Recommendation Q.921 (1997), ISDN user-network interface Data link layer
specification.
[25]
[26]
[27]
[28]
[29]
[30]
[31]
[32]
ITU-T Recommendation Q.713 (2001), Signalling connection control part formats and
codes.
[33]
[34]
[35]
ITU-T Recommendation V.24 (2000), List of definitions for interchange circuits between
Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE).
[36]
ITU-T Recommendation V.28 (1993), Electrical characteristics for unbalanced doublecurrent interchange circuits.
[37]
ITU-T Recommendation V.36 (1988), Modems for synchronous data transmission using
60-108 kHz group band circuits.
[38]
[39]
[40]
[41]
[42]
[43]
[44]
[45]
[46]
[47]
[48]
[49]
[50]
[51]
[52]
[53]
[54]
[55]
[56]
[57]
[58]
[59]
[60]
[61]
[62]
[63]
[64]
[65]
[66]
[67]
[68]
ITU-T Recommendation V.11/X.27 (1996), Electrical characteristics for balanced doublecurrent interchange circuits operating at data signalling rates up to 10 Mbit/s.
[69]
IETF RFC 2401 (1998), Security Architecture for the Internet Protocol.
[70]
[71]
[72]
[73]
[74]
IETF RFC 1122 (1989), Requirements for Internet Hosts Communication Layers.
[75]
[76]
IETF RFC 894 (1984), A Standard for the Transmission of IP Datagrams over Ethernet
Networks.
[77]
Abbreviations
AH
Authentication Header
BIS
CD
Collision Detection
CLNP
CLNS
Conf
Confirm
CONP
CONS
COTS
CSMA
CUG
DCE
DCF
DCN
DIS
DLC
DLS
DSP
DTE
ES
End System
ESP
HDLC
IDI
IDP
IDRP
IETF
Ind
Indication
IP
Internetworking Protocol
IPSec
IS
Intermediate System
ISDN
ISO
ISP
IW
Interworking Unit
LLC
LME
LSP
MAC
MD
Mediation Device
MTP
NDM
NE
Network Element
NLR
NPDU
NS
Network Service
NSAP
OS
Operations System
OSI
PDU
Ph
Physical
PhC
Physical Connection
PhS
Physical Service
PICS
PVC
QA
Q Adapter
QoS
Quality of Service
Req
Request
Res
Result
RFC
SAP
SAPI
SCCP
SCF
SGFS
SLP
SNDCF
SNP
SNPA
SVC2
TCP
TMN
VC
Virtual Circuit
DCN model
Table 20 identifies the lower layer protocols for interfaces requiring interworking as well as the
interworking method.
The following briefly describes the individual lower layer protocol profiles:
CONS1
CONS1 is applied to the reference point between PSPDN and OS/MD/QA/NE which communicates
with OS accommodated in PSPDN and ISDN.
4.2
CONS2 and CONS3 are applied to the reference point between ISDN and OS/MD/QA/NE which
communicates with OS accommodated in PSPDN or ISDN.
4.3
CLNS1
CLNS1 is applied to the reference point between LAN and OS/MD/QA/NE which communicates
with OS accommodated in LAN or PSPDN.
4.4
CLNS2
CLNS2 is applied to the reference point between PSPDN and OS/MD/QA/NE which communicates
with OS accommodated in LAN.
____________________
2
Switched Virtual Circuit corresponds to "Virtual call" used in ITU-T Rec. X.25.
ITU-T Rec. Q.811 (02/2004)
4.5
CONS6
CONS6 is applied to OS/MD/QA/NE which is connected to the reference point on connectionmode oriented LAN.
4.6
IP
The communication services and protocol referred to in this Recommendation are in accordance
with the Open Systems Interconnection (OSI) reference model [3].
The protocols for the different layers are based on ITU-T Recommendations and/or
ISO/IEC Standards.
The protocol profiles can be applied to DCN, as defined by ITU-T Rec. M.3010 [1].
Any Administration may use any existing network that meets the requirements at the layer 3/layer 4
service boundary.
For the Protocol Profiles defined in this Recommendation, interoperability mechanisms are to be
defined as a part of this Recommendation. For networks not using these profiles, it is the
responsibility of the individual Administration to solve any interoperability problems that may
exist.
6
7.1
7.1.1
NOTE Figure 3/Q.811 (1993), Protocol profile for network management, has been deleted.
7.1.2
7.1.3
7.2
7.2.1
X.25 PLC
ISO/IEC 8208
(ISO/IEC 8878)
U-Plane
Q.931
procedures used
as described in
Rec. X.31
ISO/IEC 8878
ISO/IEC 8208
DTE/DCE
operations
C-Plane
U-Plane
Q.931
procedures used
as described in
Rec. X.31
ISO/IEC 8878
ISO/IEC 8208
ISO/IEC 8208
DTE/DCE
operations
ISO/IEC 8881
X.25 LAPB
ISO/IEC 7776
SLP
Rec. Q.921
(SAPI = 0)
Rec. Q.921
(SAPI = 16)
Rec. Q.921
(SAPI = 0)
ISO/IEC 7776
SLP-DTE/DCE
operation
ISO/IEC
8802-2 LLC
(Type 2)
ISO/IEC
8802-3 MAC
CSMA/CD
(1) CONS1
D-channel
D-channel
B-channel
(2) CONS2
(3) CONS3
NOTE Further study is needed for the function of SCCP at the boundary of Network layer and Transport Layer.
10
Not specified
(5) CONS6
X.25 PLP
(ISO/IEC 8208)
IP
ITU-T
Rec. Q.931
X.25 LAPB
ISO/IEC 7776
SLP
Ethernet
ISO/IEC 8208
ISO/IEC 11575
Rec.
Q.921
Not specified
ISO/IEC 7776
Not specified
Not specified
D-channel or B-channel
I.430 (BA) or I.431 (PRA)
(4) CLNS1
(7) CLNS2
(8) CLNS3
IP
7.3.1
7.3.1.1
Service profile
The service definition for the Physical layer shall comply with that specified in clause 6 of
ISO/IEC 8802-3 [4].
All of the primitives defined and listed in Table 1 are mandatory.
Table 1/Q.811 Primitives of the Physical layer
Primitive
PLS-DATA-request
PLS-DATA-indication
PLS-CARRIER-indication
PLS-SIGNAL-indication
7.3.1.2
Protocol profile
Physical interface
Administrations will select the appropriate physical medium, e.g., coaxial cable, screened pairs,
optical fibre according to technological and operational requirements.
11
7.3.2
The Data Link layer provides the unacknowledged connectionless-mode service. The access method
employed is Carrier Sense Multiple Access with Collision Detection (CSMA/CD).
7.3.2.1
The services and protocol of the CSMA/CD access method shall comply with those specified in
ISO/IEC 8802-3 [4].
The address length used at the MAC sub-layer shall be 48 bits.
7.3.2.2
The definition of the unacknowledged connectionless-mode LLC service shall comply with that
specified in ISO/IEC 8802-2 [5]. All of the primitives defined for "Type 1" operation shall be
supported.
The protocol used to provide the unacknowledged connectionless-mode LLC service shall be as
specified in ISO/IEC 8802-2 [5]. All of the commands and responses defined for "Type 1"
operation shall be supported.
7.3.3
7.3.3.1
Services profile
The definition of the connectionless-mode Network service shall comply with that specified in
ITU-T Rec. X.213 | ISO/IEC 8348 [6]. Address formats supported shall also conform to ITU-T
Rec. X.213 | ISO/IEC 8348 [6].
The Network layer shall provide the N-UNITDATA service as specified in ITU-T Rec. X.213 |
ISO/IEC 8348 [6].
7.3.3.2
Protocol profile
The protocol shall be in accordance with the full protocol subset of category "Type 1" functions, as
specified in ITU-T Rec. X.233 | ISO/IEC 8473-1 [7].
7.3.3.3
Destination and Source Addresses used by this Protocol shall conform to one of the Network Service
Access Points (NSAPs) address formats specified in ITU-T Rec. X.213 | ISO/IEC 8348 [6].
The Destination and Source Addresses are of variable length. The Destination and Source Address
fields shall be as Network Protocol Address Information using the preferred Binary Encoding
specified in ITU-T Rec. X.213 | ISO/IEC 8348 [6].
The setting of Error Reporting Flag (E/R) shall be a local matter (Note).
Partial Source Routing shall NOT be supported. A defect exists with this option which can cause
PDUs to loop in the network until their lifetime expires.
Inactive Subset Implementations shall not transmit PDUs encoded using the
ITU-T Rec. X.233 | ISO/IEC 8473-1 inactive subset. Received PDUs encoded with the inactive
subset shall be discarded.
Segmentation The non-segmentation subset shall NOT be used. However, implementations shall
be capable of receiving and correctly processing PDUs which do not contain the segmentation part.
12
Segmentation Permitted Flag Implementations shall NOT generate data PDUs without a
segmentation part, i.e., the Segmentation Permitted Flag (SP) shall be set to 1 and the segmentation
part shall be included.
Quality of Service (QoS) The use of the QoS Maintenance Parameter shall be dependent upon the
QoS requirements of the subnetworks supporting an instance of OS-NE communications. When QoS
is used, it shall comply with the specifications in 6.16, 6.19, and 7.5.6 of
ITU-T Rec. X.233 | ISO/IEC 8473-1. It is recommended that Quality of Service Maintenance be
supported and that the globally unique QoS format be used which includes the Congestion
Experienced (CE) bit used by the Congestion Notification option.
Reassembly timer The reassembly timer must be less than the largest value of all the lifetime
parameters contained in all derived PDUs. The default Reassembly timer shall be 12 seconds.
Congestion Notification The use of Congestion Notification option is recommended. The default
value should be 0 when originating PDUs. For NEs and MDs that act as ISs, it is recommended that
Congestion Notification be supported so that end systems can take appropriate action to avoid and
recover from network congestion.
NOTE The use of error Reporting and setting the E/R flag to 1 may lead to excessive network traffic.
7.3.3.4
ES-IS routing
TMN entities that use the CLNP shall support the ISO 9542 [46] for ES-IS routing exchange. The
ES-IS protocol is provisioned as either an End System (ES) role, or an Intermediate System (IS)
role. The Data Communication Function (DCF) within the TMN entities must therefore be
provisioned in accordance with their role(s).
The ES-IS protocol subsets: Configuration Information (CI) and Redirection Information (RI) shall
be supported in accordance with the type of subnetwork, as shown in Table 3. Tables 4 and 5 give
the timer values and options for the ES and IS roles, respectively.
Table 3/Q.811 ES-IS subsets
Type of subnetwork
Protocol subset
Point-to-point (Note 1)
Broadcast (Note 2)
NS
Configuration
Information (CI)
Redirection
Information (RI)
M
Mandatory support
NS
Not supported
NS
13
Table 4/Q.811 ES-IS protocol timers and options for the end system role
Value/Range/Option
Default
Timers:
Configuration Timer
Holding Timer
1-200 s
1-500 s
(50 s)
(105 s)
Functions:
PDU Header Checksum Generation
Configuration Notification (Notes 1, 3)
Refresh Redirect (Note 2)
Address and SNPA Mask Processing (Note 2)
(Non-use)
(Use)
(Use)
(Use)
(Use)
Table 5/Q.811 ES-IS protocol timers and options for the intermediate system role
Value/Range/Option
Default
Timers:
Configuration Timer
Holding Timer
1-200 s
1-500 s
(10 s)
(25 s)
Functions:
PDU Header Checksum Generation
Configuration Notification (Notes 1, 3)
Address and SNPA Mask Processing (Note 2)
(Non-use)
(Use)
(Use)
7.3.3.5
ISO/IEC 10589 [47], the IS-IS intra-domain protocol for use with the CLNP, shall be used by TMN
entities that operate as Intermediate Systems for the purpose of routing connectionless NPDUs.
Each IS within the TMN must be capable of routing within their area and therefore must provide the
functionality of a Level 1 IS. Additionally, an IS may be provisioned as a Level 2 IS, which
provides the capability of routing from one area to another and therefore contains routing
information about ISs outside a specific area. The functionality of a Level 2 IS is not needed in each
IS within the TMN. An example of a Level 2 IS might be a gateway NE. Details for use of
ISO/IEC 10589 for TMN applications are found in Tables 6 through 11.
14
Value/Range/Option
Default
(Non-use)
(Non-use)
(Non-use)
(Non-use)
Value/Range/Option
Default
(Non-use)
(Non-use)
Value/Range/Option
0-12
1-512
Default
(3)
(512)
NOTE These numbers are preliminary and are subject for study and possible change.
Value/Range/Option
Default
(Non-use)
(256)
(512)
(Non-use)
(Non-use)
(Non-use)
(Non-use)
(Non-use)
(Non-use)
Use, non-use
(Non-use)
Use, non-use
Use, non-use
(Non-use)
(Non-use)
NOTE 1 These numbers are preliminary and are subject for study and possible change.
NOTE 2 These functions only apply when the IS is a level 2 IS.
NOTE 3 This function is mandatory when the Level 2 functions are supported.
NOTE 4 This function is mandatory when Reachable Address Prefixes are supported.
NOTE 5 This function is mandatory when the Partition repair function is supported.
ITU-T Rec. Q.811 (02/2004)
15
Value/Range/Option
Optional, use, non-use
Optional, use, non-use
Default
(Non-use)
(Non-use)
Value/Range/Option
Default
Parameter Values:
Default Metric
Max Path Metric
Minimum LSP Receive Buffer Size
IS-IS Holding Multiplier
Max Path Splits
Max Virtual Adjacencies
1-63
1023
1492 octets
10
1-32
0-32
(20)
(2)
(2)
Timers:
Max Age
Zero Age Lifetime
IS-IS Hello Timer
Complete SNP Interval Timer
Max LSP Generation Interval Timer
Min LSP Generation Interval Timer
Min LSP Transmission Interval Timer
Partial SNP Interval Timer
Poll ES Hello Rate Timer
Waiting Timer
Reserve Timer
1200 s
60 s
0-3 s
0-10 s
0-15 min
0-30 s
0-5 s
0-2 s
0-50 s
0-60 s
2-6 s
(3 s)
(10 s)
(15 min)
(30 s)
(5 s)
(2 s)
(50 s)
(60 s)
(6 s)
7.3.3.6
Border Intermediate Systems (BISs), using the ISO/IEC 10747 Inter Domain Routing Protocol
(IDRP) [48], may be employed for routing ITU-T Rec. X.233 | ISO/IEC 8473-1 CLNP PDUs
between Administrative Domains as defined in ITU-T Rec. X.213 | ISO/IEC 8348.
7.4
7.4.1
7.4.1.1
Service profile
The Physical layer service shall be as defined in ITU-T Rec. X.211 | ISO/IEC 10022 [53].
7.4.1.2
Protocol profile
The protocol of the Physical layer of Protocol Profile CLNS2 shall comply with the following
specifications:
16
Connector
Table 12 lists the connectors to be used in accessing the X.21 and X.21 bis interfaces. Tables 13,
14, and 15 list respectively the pin descriptions of ISO 2110 [38], ISO/IEC 2593 [39],
ISO 4902 [65] and ISO 4903 [66].
Table 12/Q.811 X.21/X.21 bis connectors
Data signalling rate
X.21 bis
X.21
2 400 bit/s
ISO 2110
ISO 4903
4 800 bit/s
ISO 2110
ISO 4903
9 600 bit/s
ISO 2110
ISO 4903
19 200 bit/s
ISO 2110
ISO 4903
48 000 bit/s
ISO/IEC 2593
ISO/IEC 4902
ISO 4903
56 000 bit/s
ISO/IEC 2593
ISO/IEC 2593
64 000 bit/s
ISO 4902
ISO 4903
V.24 [35]
circuit
Description
Notes
1
7
101
102
1
2
2
3
103
104
Transmitted Data
Received Data
2
2
4
5
6
20
22
8
105
106
107
108.2
125
109
Request to Send
Clear to Send
Data Set Ready (DCE Ready)
Data terminal Ready (DTE Ready)
Ring Indicator
Received Line Signal Detector
2
2
2
3
3
2
24
15
113
114
4
5
NOTE 1 Equipment: removable strap to frame ground or other equivalent grounding arrangement.
Cable: connected to shield.
NOTE 2 Basic interchange circuits, all systems.
NOTE 3 Additional interchange circuits required for switched service.
NOTE 4 Circuit 113 is not used in OS-MD/NE interfaces.
NOTE 5 Additional interchange circuits required for synchronous channel.
NOTE 6 Duplex, interface type D.
NOTE 7 Circuits are grouped by function: ground, data, control, and timing.
NOTE 8 For further information see ITU-T Recs V.24 [35], V.28 [36] and ISO 2110 [38].
17
Table 14/Q.811 V.36 [37], ISO/IEC 2593 [39] pin description (see Note 3)
Pin
Circuit
Description
Notes
A
B
101
102
Protective Ground
Signal Ground
P
S
R
T
103
103
104
104
2
2
2
2
C
D
E
F
105
106
107
109
Request to Send
Ready for Sending
Data Set Ready
Data Channel Receive Line Signal Detector
Y
AA
V
X
114
114
115
115
2
2
2
2
NOTE 1 Equipment: removable strap to frame ground or other equivalent grounding arrangement.
Cable: connected to shield.
NOTE 2 The electrical characteristics of the interchange circuits 103, 104, 114, and 115 shall be
balanced double-current, conforming to ITU-T Rec. V.36 [37].
All other circuits shall conform to ITU-T Rec. V.28 [36].
NOTE 3 The mode is synchronous at 64 000 bit/s.
Some countries may use 56 000 bit/s for an interim period of time.
NOTE 4 Circuits are grouped by function: ground, data, control and timing.
NOTE 5 For further information, see ITU-T Recs V.36 [37], V.24 [35], V.28 [36] and
ISO/IEC 2593 [39].
X.21 circuit
Description
1
8
Protective ground
Signal ground or common return
2
9
4
11
T
T
R
R
Transmit A-wire
Transmit B-wire
Receive A-wire
Receive B-wire
3
10
5
12
C
C
I
I
Control A-wire
Control B-wire
Indication A-wire
Indication B-wire
6
13
S
S
Notes
1
NOTE 1 Equipment: removable strap to frame ground or other equivalent grounding arrangement.
Cable: connected to shield.
NOTE 2 Circuits are grouped by functions: ground, data, control and timing.
NOTE 3 For further information: see ITU-T Recs V.10/X.26 [67], V.11/X.27 [68], X.21 and ISO 4903.
18
7.4.2
It is mandatory that the Data Link layer conforms to LAPB as defined in ITU-T Rec. X.25 [12]. In
addition, provision shall be made for connection between Data Terminal Equipment without an
intervening packet switched network. The interface shall conform to ISO/IEC 7776 [13].
7.4.2.1
Service profile
The Data Link layer service shall be as defined in ITU-T Rec. X.212 | ISO/IEC 8886 [60].
7.4.2.2
Protocol profile
19
Function
Range
Default
1 to 7 (with Modulo 8)
1 to 127 (with optional Modulo 128)
1 to 127 (Modulo 128 with satellite
operations)
(7)
(7)
(35)
Waiting Acknowledgment
(Retry) timera)
For up to 9600 bit/s
For 56 000 bit/s
2 to 20 seconds
0.2 to 20 seconds
(3)
(3)
T2
T3
Disconnect Timer
T3 >> T4b)
T4
No activity Timer
4 to 120 seconds
N1
I-Frames Window
T1
N2
Retransmission Count
2 to 16
A/B
Address Assignment
(20)
(2104)
(2120)
(7)
a)
Further guidelines on the use of T1 and T2 can be found in ITU-T Rec. X.25 [12] and
ISO/IEC 7776 [13]. The Transport layer T1 timer should always be greater than the link layer T1 timer.
b)
The value of timer T3, the disconnect timer, is not critical for successful interworking of OSs and NEs.
Therefore no value is specified.
c)
In some cases, users may need to choose a maximum information field length of 259 octets (N1 = 2104
for Modulo 8 or N1 = 2120 for Modulo 128) with a 128 octets packet data unit in order to accommodate
call request packets containing 128 octets user data fields in addition to the packet header and facility
fields. These values are based on Modulo 8 or Modulo 128 operation at both link and packet layer.
d)
Optional.
The default values shall be part of a vendor's offering. That is, unless otherwise specified by the user,
the default parameters shall be the initial values supplied. They can be subsequently changed by the
user within the specified range.
7.4.3
7.4.3.1
The connectionless-mode Network layer service shall be as specified in ITU-T Rec. X.213 |
ISO/IEC 8348.
7.4.3.2
Protocol profiles
The protocols for the Network layer shall be identical to the Network layer protocol of Protocol
Profile CONS1 (see 7.8) with the inclusion of ITU-T Rec. X.233 | ISO/IEC 8473-1 [7] as specified
in clause 4 of ISO/IEC 8880-3 [14], to provide the connectionless-mode Network service over the
connection-mode Network service.
For those instances of communication requiring interworking between a connection-mode service
(CONS) and a connectionless-mode service (CLNS), ITU-T Rec. X.200 | ISO/IEC 7498-1 [3] and
20
ISO 8648 [15] provide an OSI compatible interworking capability. This capability is known as a
Network Layer Relay (NLR) and utilizes the ITU-T Rec. X.233 | ISO/IEC 8473-1 [7] protocol to
provide this service.
7.4.3.3
7.5.1
This clause defines a Protocol Profile for operation of ITU-T Rec. X.224 | ISO/IEC 8073 [42]
Transport layer protocol over ITU-T Rec. X.233 | ISO/IEC 8473-1 [7] CLNP over ISDN circuit
switched B-channels. This profile is based on the Subnetwork Dependent Convergence Function
(SNDCF) defined in ITU-T Rec. X.625 | ISO/IEC 8473-5 [11].
7.5.2
Network layer
7.5.2.1
B-channel
Requirements for the topmost sub-layer (ITU-T Rec. X.233 | ISO/IEC 8473-1) of the Network layer
in the B-channel are identical with those defined in 7.3.3 (and its subclauses) for the CLNS1 and
CLNS2 Protocol Profile cases.
7.5.2.1.1 Subnetwork dependent convergence function
On the B-channel a connection may be provisioned to provide either an OSI Data Link service, or
an X.25 packet service.
7.5.2.1.1.1
For B-channels providing the OSI Data Link service defined in ITU-T Rec. X.212 | ISO/IEC
8886 [60], the SNDCF shall be as defined in ITU Rec.X.623 | ISO/IEC 8473-4 [10] and ITU-T
Rec. X.625 | ISO/IEC 8473-5.
7.5.2.1.1.2
For B-channels providing the X.25 packet service defined in ISO/IEC 8208 [16], the SNDCF shall
be as defined in ITU-T Rec. X.622 | ISO/IEC 8473-3 [9] and ITU-T Rec. X.625 | ISO/IEC 8473-5.
7.5.2.2
D-channel
ITU-T Rec. Q.931 [61] shall be used over the D-channel for the purpose of ISDN connection
establishment.
7.5.3
7.5.3.1
ISO/IEC 7776 [13], used in accordance with ITU-T Rec. X.273 | ISO/IEC 11577 [58], shall be used
in the B-channel.
7.5.3.2
D-channel
Physical layer
Either ITU-T Rec. I.430 [22] (basic rate) or ITU-T Rec. I.431 [23] (primary rate) shall be used in
the Physical layer.
21
7.6
IP protocol profiles
This clause defines additional protocol profiles for use as TMN lower layer protocols. These
profiles are based on the use of Internet Protocols defined by the Internet Engineering Task Force
(IETF). The way these documents can be referenced in this Recommendation is for further study.
The protocol stack is shown in Figure 3 and uses the following.
The functions to be supported by the DCF within a TMN entity operating as a router shall meet the
requirements specified in 7.1.6/G.7712/Y.1703 [73] sections for Network Layer PDU forwarding
function and 7.1.10/G.7712/Y.1703 for Network Layer Routing Function.
7.6.1
IPv4 profile
For Layer 3 STD0005 "Internet Protocol", September 1981. (Includes RFC 791,
RFC 950, RFC 919, RFC 922, RFC 792, RFC 1112.)
The lower layers are defined in the Ethernet Profile.
7.6.2
This profile defines an additional option of this protocol profile for use as TMN lower layer
protocols. This profile is based on the use of Secure Internet Protocols [69] defined by the Internet
Engineering Task Force (IETF). IPSec uses two protocols to provide traffic security
Authentication Header (AH) [71] and Encapsulating Security Payload (ESP) [72]. Each protocol
supports two modes of use: transport mode and tunnel mode.
Support of ESP is mandatory. Support of AH is optional. Both transport mode and tunnel mode
must be supported for each protocol.
Lower layers are defined in the Ethernet Profile.
7.6.3
IPv6 profile
For Layer 3 RFC 2460 "Internet Protocol, Version 6 (IPv6) Specification" [70].
The lower layers are specified in the Ethernet Profile.
IPSec
RFC 2401
IPv4
IPv6
IPSec
Ethernet
22
7.7
Ethernet profile
When the DCF within the TMN entities supports Ethernet interfaces, the following functions are
required to support Ethernet Physical Layer Termination Function and [Network Layer PDU into
Ethernet Frame] Encapsulation Function.
7.7.1
This function encapsulates and unencapsulates a Network Layer PDU into an 802.3 or Ethernet
(version 2) frame.
It shall encapsulate Network Layer PDUs into 802.3 or Ethernet (version 2) frames according to the
following rules:
It shall encapsulate and unencapsulate CLNP, ISIS, and ESIS PDUs into 802.3.
It shall encapsulate and unencapsulate IP packets into Ethernet (version 2) frames as per
RFC 894 [76].
IP addresses shall be mapped to Ethernet MAC addresses utilizing the Address Resolution
Protocol in RFC 826 [77].
It shall determine the received frame type (802.3 or Ethernet version 2) as per section 2.3.3 in
RFC 1122 [74].
7.8
7.8.1
See 7.3.1.
7.8.2
See 7.3.2.
7.8.3
It is mandatory that the packet layer conforms to ITU-T Rec. X.25 [12]. In addition, the packet
layer must provide for connection of data terminal equipments without an intervening packet
network; the required interface for this purpose conforms to ISO/IEC 8208 [16]. In addition, the
provisions of ISO/IEC 8878 [26] and ITU-T Rec. X.223 [17] shall apply.
The attributes which must be supported are summarized in Tables 17 and 18. Note in particular that
these tables show the different attributes needed to support PVCs [the X.25 Permanent Virtual
Circuit (PVC) procedures] and Switched Virtual Circuits (SVCs) (the X.25/SVC procedures).
23
Table 17/Q.811 X.25 [12] packet layer attributes for permanent virtual circuits
Feature
Extended Packet
Sequence Numbering
Packet size (octets)
Window size
Extended Sequence
Number option
Interrupt packets
Range
Default
128, 256
512, 1024, 2048, 4096 optional
1-7 (with Modulo 8)
1-127 (with optional Modulo 128)
(2)
(2)
Optional
NOTE 1 The default values shall be part of a vendor's offering. That is, unless otherwise specified by the
user, the default parameters shall be the initial values supplied. They can be subsequently changed by the
user within the specified range.
NOTE 2 The attributes which are not marked optional are mandatory.
NOTE 3 The ranges specified for negotiated parameters in no way affect the normal negotiation rules
specified in the International Standards.
Table 18/Q.811 X.25 [12] packet layer attributes for switched virtual circuits
Feature
Flow Control Parameter
Packet size (octets)
Range
Default
128, 256
512 optional
128
Window size
Extended Sequence
Number Option
2 (Note 5)
2400
2 decimal digits
Optional
Fast Select
Fast Select Acceptance
128 octets
Hunt Group
Optional
24
Table 18/Q.811 X.25 [12] packet layer attributes for switched virtual circuits
NOTE 1 Some countries may use 56 000 bit/s for an interim period of time. In addition to the codes
specified in the table in 7.3.2.2/X.25, 56 000 bit/s shall be encoded as binary 1 100. 48 000 bit/s is encoded
as binary 1 100 in that table, but when 56 000 bit/s is supported, the code shall stand for 56 000 bit/s.
NOTE 2 The default values shall be part of a vendor's offering. That is, unless otherwise specified by the
user, the default parameters shall be the initial values supplied. They can be subsequently changed by the
user within the specified range.
NOTE 3 The attributes which are not marked optional are mandatory.
NOTE 4 The ranges specified for negotiated parameters in no way affect the normal negotiation rules
specified in the International Standards.
NOTE 5 The default window size for satellite operations is 35.
7.8.3.1
Numbering plans
To support communications over public networks, public numbering plans may be used on the
packet-switched network between OSs and MDs/QAs/NEs. The 1988 versions of ITU-T
Recs E.164 [18] and X.121 [19] specify public numbering plans. Equipment may be assigned
numbers in accordance with either of these international Recommendations. The escape code values
of "0" and "9" shall be supported as specified in Table 2/X.121. Where a public numbering plan is
not necessary, a private numbering plan may be used.
Network layer addressing as specified in ITU-T Rec. X.213 | ISO/IEC 8348 [6] shall be supported.
Additional numbering plans, such as ITU-T Rec. Q.708 for SS7 [57], may be supported in the
future as the evolution of new subnetwork technologies require.
7.8.3.1.1 CLNP (ITU-T Rec. X.233 | ISO/IEC 8473-1) communication
When an instance of data communications involves use of the ITU-T Rec. X.233 | ISO/IEC 8473-1
CLNP, a Network Service Access Point (NSAP) address scheme shall be used. For examples of
possible NSAP structures, refer to Annex B.
7.8.3.2
Services profile
25
Protocol profile
7.9.1
The Physical layer conforms to ITU-T Recs I.430 [22] for basic rate access and I.431 [23] for
primary rate access.
7.9.2
The link layer C-plane conforms to ITU-T Rec. Q.921 [24] with the default parameters specified for
links within the SAP identified by SAPI = 0.
7.9.3
The Network layer C-plane conforms to ITU-T Rec. Q.931 [61]. Q.931 procedures are used as
described in ITU-T Rec. X.31 [25] with encodings for information elements according to ITU-T
Rec. X.31.
7.9.4
The link layer U-plane profile conforms to ITU-T Rec. Q.921 [24] with the default parameters
specified for links within the SAP identified by SAPI = 16.
7.9.5
The Network layer U-plane conforms to International Standard ISO/IEC 8208 for DTE-DCE
operation. The throughput class corresponds to the access-line bit rate of the D-channel which is
16 kbit/s. The Network layer attributes are specified in Table 18.
26
7.9.6
Provision of OSI-CONS
ITU-T Rec. X.612 | ISO/IEC 9574 [40] provides the connection-mode Network service to packet
mode terminal equipment connected to ISDN.
7.10
Layer 4 OSI Transport layer per ITU-T Rec. X.214 | ISO/IEC 8072 [41] and ITU-T Rec.
X.224 | ISO/IEC 8073 [42].
7.12
27
7.13
Conformance requirements
This clause specifies the conformance requirements for each profile by reference to its equivalent
ISP (when it exists).
The default values shall be part of a vendor's offering. That is, unless otherwise specified by the
user, the default parameters shall be the initial values supplied. They can be subsequently changed
by the user within the specified range.
The attributes that are not marked optional are mandatory. See Table 19.
Table 19/Q.811 Summary of ISP-based protocol profile conformance requirements
Protocol
profile
Protocol
layer
Requirements
CONS1
CONS1
Table
Table 20
Data Link
7.8.2 (7.4.2)
Physical
Table 20
Table 2, Tables 3
to 11 (where
applicable),
Table I.4
Network
ISO/IEC
8473 CLNP
7.3.3
Data Link
7.3.2
Physical
7.3.1
Table 1
Table 20
CLNS2
28
Clause/Figure
Network
ISO/IEC
8208
X.25 PLP
CLNS1
CLNS1/
Q.811 references
Network
ISO/IEC
8473 CLNP
7.4.3, 7.4.3.2,
7.4.3.3
Table 2, Tables 3
to 11 (where
applicable)
Network
ISO/IEC
8208 X.25
PLP
Data Link
7.4.2
Physical
7.4.1
Network
Protocol
layer
CLNS2
Int'work
Requirements
Q.811 references
Clause/Figure
Table
10613-9 (RA51.11x1).
IPv4
Network
7.6.1
IPv4 with
IPSec
Network
7.6.2
IPv6
Network
7.6.3
Ethernet
Data Link
RFC 1122
8.1
The following subclauses will describe three ways in which the lower three layers of the Protocol
Profiles may be viewed as transparent to the Transport (layer 4) and the upper layers (5, 6 and 7).
NOTE Table 10/Q.811 (1993), Homogeneous lower layer protocol profiles, has been deleted.
8.1.1
The group of subnetworks described in clause 7 have been chosen so that the services provided by
the respective Network layer protocols will ensure operation of the OSI Transport protocol. The
services of the Transport layer, in turn, are those required for operation of the higher OSI layers
(i.e., layers five to seven).
ITU-T Rec. Q.811 (02/2004)
29
8.1.2
On a forward going basis, any subnetwork developed must meet the criteria provided for the
Network layer service as viewed by the Transport layer. There are two services provided by the
Network layer, the Connection-mode Network layer Service (CONS), and the Connectionless-mode
Network layer Service (CLNS).
These services are described in ITU-T Rec. X.213 | ISO/IEC 8348.
8.1.3
For a subnetwork which does not, by itself, provide the CLNS, the addition of ITU-T
Rec. X.233 | ISO/IEC 8473-1 with the proper choice of SNDCP will provide a combination that
will meet the Network layer service description.
Subnetwork Dependent Convergence Protocols (SNDCPs) are described for the use of ITU-T
Rec. X.233 | ISO/IEC 8473-1 over ISO/IEC 8208/X.25 networks, ISO/IEC 8802-2 subnetworks [5],
subnetworks that provide the OSI Data Link service [10], and ISDN circuit-switched
B-channels [11].
8.1.4
Security
ITU-T Rec. X.273 | ISO/IEC 11577 [58] specifies security features for the OSI Network layer, and
some security capabilities are available in the Network layer protocols [e.g., mandatory Closed User
Groups (CUGs) and optional bilateral CUGs in the X.25 packet protocol].
8.2
Internetworking
This clause describes the technical principles for interworking between DCNs within a TMN, and
between TMNs using different protocol stacks. In some cases interworking units have to be
supplied between the different DCNs. It is the responsibility of the two TMN Administrations to
determine which Administration shall provide the IWU. This interworking procedure is known as
Network Layer Relay (NLR).
When networks of different types, such as connection-mode and connectionless-mode, wish to
transfer information across the boundary, internetworking principles are stated in
ITU-T Rec. X.200 | ISO/IEC 7498-1 [3] and ISO 8648 [15]. These standards state that
internetworking should occur within the Network layer. The Transport layer and higher layers
operate on a peer-to-peer basis between the communicating end systems. A family of subnetwork
dependent convergence protocols has been developed [8] to [11] that provide for the operation of
ITU-T Rec. X.233 | ISO/IEC 8473-1 over different subnetworks. Thus, in the example above,
ITU-T Rec. X.233 | ISO/IEC 8473-1 would operate over both the connection-mode subnetworks
and over the connectionless-mode subnetworks. The Transport layer, ITU-T Rec. X.224 | ISO/IEC
8073 [42], would provide for operation over both the connection-mode subnetworks and the
connectionless-mode subnetworks. In this example, the Transport layer would operate in the Class 4
mode. Thus, the internetworking between dissimilar subnetworks would be achieved and the
Transport layer and higher layers of the end systems would operate on a peer-to-peer basis.
There are three basic principles to be followed in adopting interworking solutions between
Q/X protocol stacks.
The three principles are:
1)
interworking should be done in the Network layer;
2)
existing standards should be applied for interworking functions; e.g., X.300-series
Recommendations should be applied for interworking between certain types of
CONS-based networks; and NLR using ITU-T Rec. X.233 | ISO/IEC 8473-1 and associated
SNDCFs should be used for interworking between CLNS-based networks;
30
3)
new interworking functions should be specified only if existing standards for interworking
cannot meet requirements of new network capabilities.
Definition of the relaying functions of a CONS-CONS Network layer intermediate system is given
in ISO/IEC 10028 [56]. How the Network internal layer service is provided for relaying between
X.25 packet systems is given in ISO/IEC 10177 [55].
A general guide to interworking between the various Transport profile groups is given in
ISO/IEC TR 10000-2 [64].
How relaying is performed between CLNS-based subnetworks is defined in ITU-T Rec.
X.233 | ISO/IEC 8473-1 [7].
Table 20 shows Protocol Profiles which are to be applied to a reference point which has
interworking, and defines internetworking methods.
NOTE Table 11/Q.811 (1993), Internetworking functions for Q lower layers, has been deleted.
CONS1
X.25
LAPB
Rec.
X.75 [49]
CONS1
CONS2
ISDN
X.25 (D)
CONS3
CONS5
CONS6
CONS5
SS7
CONS6
CO-LAN
CLNS1
LAN
CLNS3
ISDN
ISO
TP0/TCP/
IP
OSI
(CONS)
OSI
(CONS)
OSI
(CONS)
OSI
(CONS)
OSI
(CONS)
OSI
(CONS)
OSI
(CONS)
OSI
(CONS)
OSI
(CONS)
CLNS1
CLNS2
WAN
CONS2
CONS3
ISDN
X.25 (B)
CLNS2
OSI
(CLNS)
OSI
(CLNS)
Non-OSI
OSI
(CLNS)
OSI
(CLNS)
Non-OSI
OSI
(CLNS)
Non-OSI
CLNS3
See 8.2.1
IP
Non-OSI
OSI
NLR
8.2.1
Interworking between TMN entities supporting OSI only with entities supporting IP
Two functions as defined by ITU-T Rec. G.7712/Y.1703 shall be supported by TMN entity when IP
is connected to an entity with OSI only for interworking. These are Network Layer PDU
interworking and IP Routing Interworking. The PDU interworking is supported using Network
Layer PDU Encapsulation function (see 7.1.8/G.7712/Y.1703) and Network Layer PDU tunnelling
function (see 7.1.9/G.7712/Y.1703). The IP Routing Interworking function is supported using
Integrated IS-IS routing as defined in 7.1.10/G.7712/Y.1703.
31
Annex A
Protocol stack for information transfer over
ISDN transparent B-channel
A.1
Introduction
This annex describes a protocol stack for connection between data terminal equipment without an
intervening packet switched network. End systems are making use of the 64 kbit/s unrestricted
circuit-mode bearer service offered by an ISDN. The OSI connection-mode service (OSI-CONS)
over ISDN transparent B-channel defined in this annex is identified as CONS4 at the Q and X
interfaces.
The CONS4 lower layer protocol profile provides for a connection-mode interface using ISDN
transparent B-channel.
A.2
A.2.1
The Physical layer conforms to ITU-T Recs I.430 for basic rate access and I.431 for primary rate
access.
A.2.2
The link layer C-plane conforms to ITU-T Rec. Q.921 with the default parameters specified for
links within the SAP identified by SAPI = 0.
A.2.3
The Network layer C-plane conforms to ITU-T Rec. Q.931 for circuit-switched call control
procedures using codings of information element as in Table A.1.
32
ITU-T
Unrestricted digital information
Circuit mode
64 kbit/s
International/national/subscriber
ISDN/telephony numbering plan
(ITU-T Rec. E.164)
NSAP
A.2.4
ITU-T
Unrestricted digital information
Circuit mode
64 kbit/s
Not applicable (omit octet 5)
ISO/IEC 7776 DTE-DTE operation
Normal/extended (selectable by user whereby
normal is a mandatory mode while extended is an
optional mode)
1-7 (for modulo 8) (default 7)
1-127 (for modulo 128) (default 7)
1-127 (for modulo 128) (default 35 for satellite
operations)
ISO/IEC 8208 DTE-DTE operation
Normal (modulo 8)/extended (modulo 128)
128, 256, 512 octets (default 128)
1-7 (for modulo 8)(default 2)
1-127 (for modulo 128)(default 2)
Supplementary services
The supplementary service Sub-addressing (SUB) is required in order to convey the called and
calling NSAP address in the called and calling party subaddress information element, respectively.
In addition, the supplementary service Closed User Group (CUG) may be used to restrict, in a
public Data Communication Network (DCN), access of end systems which are the members of a
TMN.
A.2.5
The link layer U-plane conforms to ISO/IEC 7776 for Single Link Procedures (SLPs) in DTE-DTE
operation. The link layer attributes are specified in Table 16.
A.2.6
The Network layer U-plane conforms to ISO/IEC 8208 for DTE-DTE operation over circuitswitched connections.
33
The throughput class corresponds to the access-line bit rate of the B-channel which is
64 kbit/s.
T20
180 seconds
T21
200 seconds
T22
180 seconds
T23
180 seconds
T24
Not applicable
T25
Not applicable
T26
180 seconds
T27
Not applicable
T28
Not applicable
R20
R22
R23
R25
Not applicable
R27
Not applicable
R28
Not applicable
A.2.7
Provision of OSI-CONS
The Synchronization and Coordination Function (SCF) (see ITU-T Rec. I.320 [62]) provides the
connection-mode Network service to the Network service user.
34
Annex B
Examples of NSAP structures for CLNP
This annex summarizes four examples of NSAP structure. Figures B.1, B.2, and B.3 show NSAP
structures based on ISO-DCC. Figure B.4 shows an NSAP structure based on ISO-ICD.
IDP
AFI
39
1
Number of octets
DSP
IDI
a)
JDI#
3
AREA
n
SYSTEM
6
SEL
1
a)
Number of octets
DSP
IDI
a)
ORG
3
AREA
2
a)
SYSTEM
0-6
SEL
1
ISO DCC.
Organization Identifier
Subnetwork Identifier
Subnetwork address
ORG
AREA
SYSTEM
Number of octets
AFI
39
1
DSP
IDI
a)
DFI
128
1
a)
DFI
org
res
rd
org
3
res
2
rd
2
AREA
2
SYSTEM
6
SEL
1
ISO DCC.
The DSP Format Identifier
Organization Identifier
Reserved
Routing domain prefix
35
IDP
Number of octets
AFI
47
1
DSP
IDI
a)
DI
3
2
a)
DI
FI
TI
SEL
FI
1
TI
12
SEL
1
ISO ICD.
Domain Identifier
Format Identifier
Terminal Identifier
NSAP selector
Appendix I
Changes to ISP conformance requirements
The "Identifier", "Feature", and "Status" fields under "Base Reference Standard" refer to the PICS
for the particular base standard protocol; whereas the "Clause" field refers to the base protocol
specification.
Notation:
a)
Base standard status notation
1) Base standard type or range:
M
Mandatory.
O
Optional.
Not applicable.
O.<n>
Optional, but support of at least one of the group of options labelled by
the same numeral <n> is required.
<index>:
This predicate symbol means that the status following applies only when
the PICS states that one or more of the items identified by the index is
supported. In the simplest case, <index> is the identifying tag of a single
PICS item. <index> may also be a Boolean expression composed of
several indices.
<index>::
When this group predicate is true the associated clause should be
completed.
b)
Q.811 status notation
The status column in Tables I.1 to I.4 uses either a one-or two-character notation. The onecharacter notation indicates the static requirements only. For the two-character notation, the
first character is the static requirements and the second character is the dynamic
requirements.
1) Static:
m
Mandatory, mandatory to be implemented.
i
Out of scope. Not relevant to this profile.
o
Optional, optional to be implemented.
&
Same as Base Standard.
36
2) Dynamic:
m
x
Ident.
Feature
ISP
Clause
Status
Status
Status
Et/d
DTE/DTE with
dynamic role selection
4.5
Vs: O.2
oi
7.8.3.3.1
mm
M128
Modulo 128
(extended)
13.2,
12.1.1,
Table 3
O.3
ox
Table 18
oo
V2s
16.2.2.6
M8: 1-7
M128: 1-127
M8: 1-7
M128: o-
Table 18
Table 18
M8: 2
M128: 2
V2r
16.2.2.6
M8: 1-7
M128: 1-127
M8: 1-7
M128: o-
Table 18
Table 18
M8: 2
M128: 2
V10s
Window sizes
supported, sending
15.2.2.1.2
M128: 1-127
M128: o-
Table 18
M128:
1-127
V10r
Window sizes
supported, receiving
15.2.2.1.2
M128: 1-127
M128: o-
Table 18
M128: 1-1
T24
Window Status
Transmission Timer
ox
Table 18
oo
T25
Window Rotation
Timer
ox
Table 18
oo
FS5
FR5
Table 18
oo
13.15
15.2.2.5
37
Feature
ISP
Clause
Status
DTE/DTE
Interworking
T2
Parameter T2
procedure
5.7.1.2,
5.7.1.1
T3
Parameter T3
procedure
T4
Status
oi
Status
7.4.2.2.1
Table 16
5.7.1.3
Table 16
Parameter T4
procedure
5.7.1.4,
5.3.2
Table 16
SP8
If Modulo 8 was
checked with SLP
(N1 1080)
5.7.3
Table 16
SP128
Table 16
NOTE for Tables I.1 and I.2 The referenced ISP is ISO/IEC ISP 10609, Parts 1 and 9
(TB1111/TB1121) [45].
Feature
ISP
Clause
Status
Status
Status
Vp
PVC
O.1
&
Vs
VC
O.1
mm
&
Et/d
DTE/DTE with
dynamic role selection
Vs: O.2
Vs: i
4.5
7.5.3
mm
Feature
QoS Maintenance
ISP
Clause
7.5.6
Status
O
Status
i
Status
mm
NOTE for Tables I.3 and I.4 Reference is to ISO/IEC ISP 10608, Parts 1, 2 (TA51), and Part 5
(TA1111/TA1121) [44].
38
Series B
Series C
Series D
Series E
Overall network operation, telephone service, service operation and human factors
Series F
Series G
Series H
Series I
Series J
Cable networks and transmission of television, sound programme and other multimedia signals
Series K
Series L
Construction, installation and protection of cables and other elements of outside plant
Series M
Series N
Series O
Series P
Series Q
Series R
Telegraph transmission
Series S
Series T
Series U
Telegraph switching
Series V
Series X
Series Y
Global information infrastructure, Internet protocol aspects and Next Generation Networks
Series Z
Printed in Switzerland
Geneva, 2004