|
STUDY GROUP 4 |
||
|
TELECOMMUNICATION STUDY PERIOD 2001-2004 |
||
|
Original: English |
||
|
Question(s): |
||
|
Source: |
||
|
Title: |
||
This document is a draft revision of
Recommendation Q.811. It supports the
work plan of Q18/4 to revise Q.811 and Q.812 to split at the layer 3/4 boundary
as well as editing instructions from question 18/4 meeting in February 2003. It
also contains an additional IPsec profile.
|
|
INTERNATIONAL TELECOMMUNICATION UNION |
|
ITU-T |
|
|
TELECOMMUNICATION |
SERIES Q: SWITCHING AND
SIGNALLING
Specifications of Signalling System
No. 7 ? Q interface
Lower layer protocol
profiles for the Q and
X interfaces
ITU-T Q-SERIES
RECOMMENDATIONS
For further
details, please refer to ITU-T List of Recommendations.
|
ITU-T RECOMMENDATION Q.811 lower layer protocol profiles for the Q and x interfaces |
|
Summary This Recommendation provides the lower layer protocol profiles for the Q and X interfaces as defined in Recommendation M.3010. It also provides a method for interworking. |
|
Source ITU-T Recommendation Q.811 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 5th of June 1997. |
|
Keywords DCN, ISDN, NSAP and Interworking,
Protocol Profiles, Q Interface, TMN, X Interface, X.25. |
FOREWORD
ITU (International
Telecommunication Union) is the United Nations Specialized Agency in the field
of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T)
is a permanent organ of the ITU. The 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 Conference (WTSC), which meets every four
years, establishes the topics for study by the ITU‑T Study Groups which,
in their turn, produce Recommendations on these topics.
The approval of
Recommendations by the Members of the ITU‑T is covered by the procedure
laid down in WTSC Resolution No. 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.
INTELLECTUAL PROPERTY RIGHTS
The ITU draws
attention to the possibility that the practice or implementation of this
Recommendation may involve the use of a claimed Intellectual Property Right.
The ITU takes no position concerning the evidence, validity or applicability of
claimed Intellectual Property Rights, whether asserted by ITU members or others
outside of the Recommendation development process.
As of the date of
approval of this Recommendation, the ITU had/had not received notice of intellectual
property, protected by patents, which may be required to implement this
Recommendation. However, implementors are cautioned that this may not represent
the latest information and are therefore strongly urged to consult the TSB
patent database.
ă ITU 2003
All rights
reserved. No part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and
microfilm, without permission in writing from the ITU.
CONTENTS
4.2........ CONS2,
CONS3, CLNS3
5 Lower
layer protocol profiles: Overview
6 Requirements
for network layer/transport layer interface
7.1........ Connectionless-mode
protocol profiles
7.1.2..... WAN,
LAN (see Figure 3)
7.1.3..... ISDN
(see Figure 3)
7.2........ Connection-mode protocol profiles
7.2.1..... X.25/LAPB
[see Figure 2 (1), (3), (2), (6), (5)]
7.3........ CL-LAN
profile (CLNS1)
7.3.1..... Physical
layer profile
7.3.2..... Data
link layer profile
7.3.2.1.. Media
Access Control (MAC) profile
7.3.2.2.. Logical
Link Control (LLC) profile
7.3.3..... Network
layer profile
7.3.3.3.. Network
layer attributes
7.3.3.5.. IS-IS
Intra-Domain Routing
7.3.3.6.. IS-IS
Inter Domain Routing
7.4........ CL-WAN
profile (CLNS2)
7.4.1..... Physical
layer profile
7.4.2..... Data
link layer profile
7.4.3..... Network
layer profile
7.4.3.3.. Network
layer attributes
7.5........ ISDN
protocol profile (CLNS3)
7.5.1..... ISDN
protocol profile for connectionless-mode network service
7.6........ IP protocol profiles
7.6.2..... Ipv4
with IPSec Profile
7.7.1..... Ethernet
Physical Termination Function
7.7.2..... [Network
Layer PDU into Ethernet Frame] Encapsulation Function
7.8........ X.25/LAPB
protocol profile (CONS1)
7.8.1..... Physical
layer profile
7.8.2..... Data
link layer profile
7.8.3..... Network
layer profile
7.9........ Packet
mode bearer service on the D-channel (CONS2)
7.9.1..... Physical
layer profile
7.9.2..... Link
layer C-plane profile
7.9.3..... Network
layer C-plane profile
7.9.4..... Link
layer U-plane profile
7.9.5..... Network
layer U-plane profile
7.9.6..... Provision
of OSI-CONS
7.10...... Packet
mode bearer service on the B-channel (CONS3)
7.10.1... Physical
layer profile
7.10.2... Link
layer C-plane profile
7.10.3... Network
layer C-plane profile
7.10.4... Link
layer U-plane profile
7.10.5... Network
layer U-plane profile
7.10.6... Provision
of OSI-CONS
7.11...... Signalling
System No. 7 networks (CONS5)
7.12...... Connection
oriented LAN (CONS6)
7.12.1... Physical
layer profile
7.12.2... Data
link layer profile
7.12.3... Network
layer profile
7.13...... Conformance
requirements
7.13.1... CL-LAN
profile (CLNS1)
7.13.2... CL-WAN
profile (CLNS2)
7.13.3... X.25/LAPB
profile (CONS1)
Connection
oriented LAN (CONS6)
8.1........ Network
layer profiles
8.1.1..... Existing
lower layer profiles
8.1.2..... Network
layer service description for new subnetworks
8.1.3..... Non-conforming
Network layer profile
8.2.1..... Interworking
between TMN entities supporting OSI only with entities supporting IP
A.2........ Network
profile CONS4
A.2.1..... Physical
layer profile
A.2.2..... Link
layer C-plane profile
A.2.3..... Network
layer C-plane profile
A.2.4..... Supplementary
services
A.2.5..... Link
layer U-plane profile
A.2.6..... Network
layer U-plane profile
A.2.7..... Provision
of OSI-CONS
1 Introduction
1.1 Scope
1.2 References
1.3 Abbreviations
1.4 Terms
2 DCN model
2.1 CONS1
2.2 CONS2,
CONS3, CLNS3
2.3 CLNS1
2.4 CLNS2
2.5 CONS6
2.6 IP
2.7 IPSec
3 Lower
layer protocol profiles: Overview
4 Requirements
for network layer/transport layer interface
5 Defined
protocol profiles 21
5.1 Connectionless-mode
protocol profiles 21
5.1.1 LAN (see
Figure 3)
5.1.2 WAN, LAN
(see Figure 3)
5.1.3 ISDN (see
Figure 3)
5.2 Connection-mode
protocol profiles 21
5.2.1 X.25/LAPB
[see Figure 2 (1), (3), (2), (6), (5)]
5.3 CL-LAN
profile (CLNS1)
5.3.1 Physical
layer profile
5.3.1.1 Service
profile
5.3.1.2 Protocol
profile
5.3.1.3 Physical
interface
5.3.2 Data link
layer profile
5.3.2.1 Media
Access Control (MAC) profile
5.3.2.2 Logical
Link Control (LLC) profile
5.3.3 Network
layer profile
5.3.3.1 Services
profile
5.3.3.2 Protocol
profile
5.3.3.3 Network
layer attributes 27
5.3.3.4 ES-IS
routing
5.3.3.5 IS-IS
Intra-Domain Routing
5.3.3.6 IS-IS
Inter Domain Routing
5.4 CL-WAN
profile (CLNS2)
5.4.1 Physical
layer profile
5.4.1.1 Service
profile
5.4.1.2 Protocol
profile
5.4.1.3 Connector
5.4.2 Data link
layer profile
5.4.2.1 Service
profile
5.4.2.2 Protocol
profile
5.4.3 Network
layer profile
5.4.3.1 Service
profile
5.4.3.2 Protocol
profiles
5.4.3.3 Network
layer attributes 36
5.5 ISDN
protocol profile (CLNS3)
5.5.1 ISDN
protocol profile for connectionless-mode network service
5.5.2 Network
layer
5.5.2.1 B-channel
5.5.2.2 D-channel
5.5.3 Data link
layer
5.5.3.1 B-channel
5.5.3.2 D-channel
5.5.4 Physical
layer
5.6 IP
protocol profile 38
5.7 IPSec:
Security Architecture for the Internet Protocol
5.8 X.25/LAPB
protocol profile (CONS1)
5.8.1 Physical
layer profile
5.8.2 Data link
layer profile
5.8.3 Network
layer profile
5.8.3.1 Numbering
plans
5.8.3.2 Services
profile
5.8.3.3 Protocol
profile
5.9 Packet
mode bearer service on the D-channel (CONS2)
5.9.1 Physical
layer profile
5.9.2 Link layer
C-plane profile
5.9.3 Network
layer C-plane profile
5.9.4 Link layer
U-plane profile
5.9.5 Network
layer U-plane profile
5.9.6 Provision
of OSI-CONS
5.10 Packet
mode bearer service on the B-channel (CONS3)
5.10.1 Physical
layer profile
5.10.2 Link layer
C-plane profile
5.10.3 Network
layer C-plane profile
5.10.4 Link layer
U-plane profile
5.10.5 Network
layer U-plane profile
5.10.6 Provision
of OSI-CONS
5.11 Signalling
System No. 7 networks (CONS5)
5.12 Connection
oriented LAN (CONS6)
5.12.1 Physical
layer profile
5.12.2 Data link
layer profile
5.12.3 Network
layer profile
5.13 Conformance
requirements
5.13.1 CL-LAN
profile (CLNS1)
5.13.2 CL-WAN
profile (CLNS2)
5.13.3 ISDN
profile (CLNS3)
5.13.4 IP profile
5.13.5 X.25/LAPB
profile (CONS1)
5.13.6 Packet
mode bearer on ISDN D-channel profile (CONS2)
5.13.7 Packet
mode bearer on ISDN B-channel profile (CONS3)
5.13.8 Signalling
System No. 7 profile (CONS5)
5.13.9 Connection
oriented LAN (CONS6)
6 Network
layer service
6.1 Network
layer profiles
6.1.1 Existing
lower layer profiles
6.1.2 Network
layer service description for new subnetworks
6.1.3 Non-conforming
Network layer profile
6.1.4 Security
6.2 Internetworking
Annex A
A.1 Introduction
A.2 Network
profile CONS4
A.2.1 Physical
layer profile
A.2.2 Link layer
C-plane profile
A.2.3 Network
layer C-plane profile
A.2.4 Supplementary
services
A.2.5 Link layer
U-plane profile
A.2.6 Network
layer U-plane profile
A.2.7 Provision
of OSI-CONS
Recommendation Q.811
LOWER LAYER PROTOCOL
PROFILES FOR THE Q and X INTERFACES
(revised in 2003)
This Recommendation is a part of a series of Recommendations dealing with the transfer of information for the management of telecommunications systems. This Recommendation defines the requirements of lower layer protocol profiles for the Q and X interfaces[1], as defined in Recommendation M.3010 [1] and in other M.3000-Series Recommendations. The companion Recommendation Q.812 [2] defines the requirements of the upper layer protocol profiles for the Q and X interfaces. The Q and X interfaces will support bidirectional data transfer for the management of telecommunications systems.
The need for security functionality is recognized, but is not fully addressed in this Recommendation and is for further study. Users may need to use mechanisms outside this Recommendation in order to address their specific security needs. Security mechanisms chosen may depend on the network configuration being used.
If new operational requirements are developed that imply distinctions need to made here between the Q and X interfaces, future versions of this Recommendation, or possibly new Recommendations, will reflect these differences.
This Recommendation defines:
? the layer service profiles for the defined supported networks;
? the layer protocol profiles for the defined supported networks;
? 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 [64] and ISO/IEC TR 10000-2 [65]. 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.
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, all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendation and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
[1] CCITT ITU-T Recommendation
M.3010 (19922000), Principles
for a telecommunications management network.
[2] ITU-T Recommendation Q.812 (1997), Upper layer protocol profiles for the Q and X interfaces.
[3] ITU-T Recommendation X.200 (1994) | ISO/IEC 7498-1:1994, Information technology ? Open Systems Interconnection ? Basic reference model: The basic model.
[4] ISO/IEC 8802-3:19962000,
Information technology ? Telecommunications and information exchange between
systems ? Local and metropolitan area networks ? Specific requirements ? Part
3: Carrier sense multiple access with collision detection (CSMA/CD) ? Access
method and physical layer specifications.
[5] ISO/IEC 8802-2:19941998,
Information technology ? Telecommunications and information exchange between
systems ? Local and metropolitan area networks ? Specific requirements ?
Part 2: Logical link control.
[6] CCITT ITU-T Recommendation
X.213 (19922001) | ISO/IEC
8348:19932001, Information
technology ? Open Systems Interconnection ? Network service definition.
[7] ITU-T
Recommendation X.233 (19973) | ISO/IEC
8473-1:19984, Information
technology ? Protocol for providing the connectionless-mode network service:
Protocol specification.
[8] ISO/IEC 8473-2:1996, Information technology ? Protocol for providing the connectionless-mode network service, Part 2: Provision of the underlying service by an ISO/IEC 8802 subnetwork.
[9] ITU-T Recommendation X.622 (1994) | ISO/IEC 8473-3:1995, Information technology ? Protocol for providing the connectionless-mode network service: Provision of the underlying service by an X.25 subnetwork.
[10] ITU-T Recommendation X.623 (1994) | ISO/IEC 8473-4:1995, Information technology ? Protocol for providing the connectionless-mode network service: Provision of the underlying service by a subnetwork that provides the OSI data link service.
[11] ITU-T Recommendation
X.625 (1996) | ISO/IEC 8473-5:19976,
Information technology ? Protocol for providing the connectionless-mode
network service: Provision of the underlying service by ISDN circuit-switched
B-channels.
[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] ISO/IEC 7776:1995, Information technology ? Telecommunications and information exchange between systems ? High-level data link control procedures ? Description of the X.25 LAPB-compatible DTE data link procedures.
[14] ISO/IEC 8880-3:1990, Information technology ? Telecommunications and information exchange between systems ? Protocol combinations to provide and support the OSI Network Service ? Part 3: Provision and support of connectionless-mode Network Service.
[15] ISO 8648:1988, Information processing systems ? Open Systems Interconnection ? Internal organization of the Network Layer.
[16] ISO/IEC 8208:19952000,
Information technology ? Data communications ? X.25 Packet layer Protocol
for Data Terminal Equipment.
[17] CCITT ITU-T Recommendation
X.223 (19881993), Use
of X.25 to provide the OSI connection-mode network service for CCITT ITU-T applications.
[18] ITU-T Recommendation E.164 (1997), The international public telecommunication numbering plan.
[19] ITU-T Recommendation
X.121 (19962000), International
numbering plan for public data networks.
[20] CCITT Recommendation X.244 (1988), Procedure for the exchange of protocol identification during virtual call establishment on packet switched public data networks.
[21] ISO/IEC TR 9577:19996,
Information technology ? Protocol identification in the network layer.
[22] ITU-T Recommendation I.430 (1995), Basic user-network interface ? Layer 1 specification.
[23] ITU-T Recommendation I.431 (1993), Primary rate user-network interface ? Layer 1 specification.
[24] ITU-T Recommendation
Q.921 (19931997), ISDN
user-network interface ? Data link layer specification.
[25] ITU-T Recommendation X.31 (1995), Support of packet mode terminal equipment by an ISDN.
[26] ISO/IEC 8878:1992, Information technology ? Telecommunications and information exchange between systems ? Use of X.25 to provide the OSI Connection-mode Network Service.
[27] CCITT Recommendation Q.702 (1988), Signalling data link.
[28] ITU-T Recommendation Q.703 (1996), Signalling link.
[29] ITU-T Recommendation Q.704 (1996), Signalling network functions and messages.
[30] ITU-T Recommendation
Q.711 (19962001), Functional
description of the signalling connection control part.
[31] ITU-T Recommendation Q.712 (1996), Definition and function of signalling connection control part messages.
[32] ITU-T Recommendation
Q.713 (19962001), Signalling
connection control part formats and codes.
[33] ITU-T Recommendation
Q.714 (19962001), Signalling
connection control part procedures.
[34] ITU-T Recommendation Q.716 (1993), Signalling Connection Control Part (SCCP) performance.
[35] ITU-T Recommendation
V.24 (19962000),
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 double-current interchange circuits.
[37] CCITT Recommendation V.36 (1988), Modems for synchronous data transmission using 60-108 kHz group band circuits.
[38] ISO 2110:1989, Information technology ? Data communication ? 25-pole DTE/DCE interface connector and contact number assignments.
[39] ISO/IEC 2593:19932000,
Information technology ? Telecommunications and information exchange between
systems ? 34-pole DTE/DCE interface connector mateability dimensions and
contact number assignments.
[40] CCITT Recommendation X.612 (1992) | ISO/IEC 9574:1992, Information technology ? Provision of the OSI connection-mode network service by packet-mode terminal equipment connected to an Integrated Services Digital Network (ISDN).
[41] ITU-T Recommendation X.214 (1995) | ISO/IEC 8072:1996, Information technology ? Open Systems Interconnection ? Transport service definition.
[42] ISO/IEC 8073:19972,
Information technology ? Telecommunications and information exchange between
systems ? Open Systems Interconnection ? Protocol for providing the
connection-mode transport service.
[43] ITU-T Recommendation
X.224 (19953), Protocol
for providing the OSI connection-mode transport service.
[44] ISO/IEC 8881:1989, Information processing systems ? Data communications ? Use of the X.25 packet level protocol in local area networks.
[45] ISO/IEC ISP 10608:1992, Information technology ? International Standardized Profile TAnnnn ? Connection-mode Transport Service over Connectionless-mode Network Service.
Part 1: General overview and subnetwork-independent requirements.
Part 2: TA51 profile including subnetwork-dependent requirements for CSMA/CD Local Area Networks (LANs).
Part 5: TA1111/TA1121 profiles including subnetwork-dependent requirements for X.25 packet-switched data networks using virtual circuits.
[46] ISO/IEC ISP 10609:1992, Information technology - International Standardized Profiles TB, TC, TD, and TE ? Connection-mode Transport service over Connection-mode Network Service.
Part 1: Subnetwork-type independent requirements for Group TB.
Part 5: Definition of Profiles TB1111/TB1121.
Part 9: Subnetwork-type dependent requirements for Network Layer, Data Link Layer and Physical Layer concerning permanent access to a packet switched data network using virtual calls.
[47] ISO 9542:1988, Information processing systems ? Telecommunications and information exchange between systems ? End system to Intermediate system routeing exchange protocol for use in conjunction with the Protocol for providing the connectionless-mode network service.
[48] ISO/IEC 10589:19922002,
Information technology ? Telecommunications and information exchange between
systems ? Intermediate system to Intermediate system intra-domain
routeing information exchange protocol for use in conjunction with the protocol
for providing the connectionless-mode Network Service.
[49] ISO/IEC 10747:1994, Information technology ? Telecommunications and information exchange between systems ? Protocol for exchange of inter-domain routeing information among intermediate systems to support forwarding of ISO 8473 PDUs.
[50] ITU-T Recommendation
X.75 (19963), Packet-switched
signalling system between public networks providing data transmission services.
[51] CCITT ITU-T Recommendation
X.325 (19881996), General
arrangements for interworking between Packet Switched Public Data Networks
(PSPDNs) and Integrated Services Digital Networks (ISDNs) for the provision of
data transmission services. (Same as Recommendation I.550.)
[52] CCITT Recommendation X.326 (1988), General arrangements for interworking between Packet Switched Public Data Networks (PSPDNs) and Common Channel Signalling Network (CCSN).
[53] CCITT ITU-T Recommendation
X.327 (19881993), General
arrangements for interworking between Packet Switched Public Data Networks
(PSPDNs) and private data networks for the provision of data transmission
services.
[54] ITU-T Recommendation X.211 (1995) | ISO/IEC 10022:1996, Information technology ? Open Systems Interconnection ? Physical service definition.
[55] ISO/IEC 11570:1992, Information technology ? Telecommunications and information exchange between systems ? Open Systems Interconnection ? Transport protocol identification mechanism.
[56] ISO/IEC 10177:1993, Information technology ? Telecommunications and information exchange between systems ? Provision of the connection-mode Network internal layer service by intermediate systems using ISO/IEC 8208, the X.25 Packet Layer Protocol.
[57] ISO/IEC 10028:1993, Information technology ? Telecommunications and information exchange between systems ? Definition of the relaying functions of a Network layer intermediate system.
[58] ITU-T Recommendation
Q.708 (19993), Numbering
ofAssignment procedures for
international signalling point codes.
[59] ITU-T Recommendation X.273 (1994) | ISO/IEC 11577:1995, Information technology ? Open Systems Interconnection ? Network layer security protocol.
[60] ISO/IEC 11575:1995, Information technology ? Telecommunications and information exchange between systems ? Protocol mappings for the OSI Data Link service.
[61] ITU-T Recommendation X.212 (1995) | ISO/IEC 8886:1996, Information technology ? Open Systems Interconnection ? Data link service definition.
[62] ITU-T Recommendation
Q.931 (19983), ISDN
user-network interface layer 3 specification for basic call control.
[63] ITU-T Recommendation I.320 (1993), ISDN protocol reference model.
[64] ISO/IEC TR
10000-1:19985, Information
technology ? Framework and taxonomy of International Standardized Profiles ?
Part 1: General principles and documentation framework.
[65] ISO/IEC TR
10000-2:19985 Information
technology ? Framework and taxonomy of International Standardized Profiles ?
Part 2: Principles and Taxonomy for OSI Profiles.
[66] ISO 4902:1989, Information technology ? Data communication ? 37-pole DTE/DCE interface connector and contact number assignments.
[67] ISO 4903:1989, Information technology ? Data communication ? 15-pole DTE/DCE interface connector and contact number assignments.
[68] CCITT ITU-T Recommendation
V.10 (or X.26) (19881993), Electrical
characteristics for unbalanced double-current interchange operating at data signalling
rates nominally up to 100 kbit/scircuits for general use
with integrated circuit equipment in the field of data communications.
[69] CCITT ITU-T Recommendation
V.11 (or X.27) (199688), Electrical
characteristics for balanced double-current interchange operating at data signalling
rates up to 10 Mbit/scircuits for general use with integrated circuit
equipment in the field of data communications.
[70] IETF RFC 2401 (1998)
“Security
Architecture for the Internet Protocol”
[71] IETF RFC 2460 (1998) Internet Protocol, Version 6
(IPv6) Specification
[72] IETF RFC 2402 (1998) IP Authentication Header
[73] IETF RFC 2406 (1998) IP Encapsulating Security Payload
(ESP)
[74] ITU-T G.7712 (2003) Architecture and
specification of data communication network
[75] IETF RFC 1122 (1989) Requirements for Internet
Hosts
[76] ITU-T Recommendation M.3030 (2002) Telecommunications Markup
Language (tML) framework
[77] IETF RFC 894 (1984) A Standard for the Transmission
of IP Datagrams over Ethernet Networks
[78] IETF RFC 826 (1982) An Ethernet Address Resolution Protocol
This Recombination uses the following abbreviations.
AFI Authority and Format Identifier
AH Authentication Header
BIS Border Intermediate System
CCITT Comité Consultatif
International Téléphonique et Télégraphique
CD Collision Detection
CLNP Connectionless-mode Network layer Protocol
CLNS Connectionless-mode Network layer Service
Conf Confirm
CONP Connection-mode Network layer Protocol
CONS Connection-mode Network layer Service
COTS Connection-mode Transport Service
CSMA Carrier Sense Multiple Access
CUG Closed User Group
DCE Data Communications Equipment
DCF Data Communications Functions
DCN Data Communication Network
DIS Draft International Standard
DLC Data Link Connection
DLS Data Link Service
DSP Domain Specific Part
DTE Data Terminal Equipment
ES End System
ESP Encapsulation Security Payload
HDLC High-level Data Link Control
IDI Initial
Domain Identifier
IDP Initial
Domain Part
IDRP Inter Domain Routing (or Routeing) Protocol
Ind Indication
IETF Internet Engineering Task Force
IP Internetworking Protocol
IPSec Security Infrastructure for Internet Protocol
IS Intermediate System
ISDN Integrated Services Digital Network
ISO International Organization for Standardization
ISP International Standardized Profile
IW Interworking Unit
LLC Logical Link Control
LME Layer
Management Entity
LSP Link State Protocol Data Unit
MAC Media Access Control
MD Mediation Device
MTP Message Transfer Part
NDM Normal Disconnect Mode
NE Network Element
NLR Network Layer Relay
NPDU Network Protocol Data Unit
NS Network Service
NSAP Network Service Access Point
OS Operations System
OSI Open Systems Interconnection
PDU Protocol Data Unit
PhC Physical Connection
Ph Physical
PhS Physical
Service
PICS Protocol
Implementation Conformance Statement
PVC Permanent
Virtual Circuit
QA Q
Adapter
QOS Quality of Service
Req Request
Res Result
RFC Request For Comments
SAP Service Advertising Protocol
SAPI Security Application Program
Interfaces
SCCP Signalling Connection Control Part
SCF Service Control Function
SGFS Special Group on Functional Standards
SLP Service Location Profile
SNDCF Subnetwork Dependent Convergence Function
SNP Sequence Numbers Protocol Data Unit
SNPA Subnetwork Point of Attachment
SVC[2] Switched Virtual Circuit
TCP Transmission Control Protocol
TMN Telecommunications Management Network
VC Virtual Circuit
Table 24 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: A connection-mode packet interface using X.25.
? CONS2: A connection-mode packet interface using X.31 on an ISDN D-channel.
? CONS3: A connection-mode packet interface using
X.31 on an ISDN B-channel.
? CONS5: A
connection-mode interface using Signalling System No. 7 MTP and SCCP[3]. This area
is for future study.
? CONS6: A connection-mode packet interface X.25 over LAN.
? CLNS1: A connectionless-mode interface using ISO/IEC 8802-2 type LANs using CSMA/CD.
? CLNS2: A connectionless-mode interface using ISO CLNP over a connection-mode X.25 protocol.
? CLNS3: A connectionless-mode interface using ISO
CLNP over ISDN B-channels (see 5.57.5).
? IP: Internet Protocol
for use in the TMN (see 7.6 5.6).
- IPSec: Security Architecture for the Internet Protocol
(see 5.7)
This subclause provides typical examples of the application of these profiles at the Q and X interfaces. Other fields of application are not precluded by this Recommendation. The differences between the following profiles will be further discussed in Q.812
CONS1 is applied to the reference point between PSPDN and OS/MD/QA/NE which communicates with OS accommodated in PSPDN and ISDN.
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.
CLNS1 is applied to the reference point between LAN and OS/MD/QA/NE which communicates with OS accommodated in LAN or PSPDN.
CLNS2 is applied to the reference point between PSPDN and OS/MD/QA/NE which communicates with OS accommodated in LAN.
CONS6 is applied to OS/MD/QA/NE which is connected to the reference point on connection-mode oriented LAN.
IP is applied to OS/MD/QA/NE and LANS which communicate with OS using IP accommodated in the LAN.
IP Sec [70] is applied to OS/MD/QA/NE and LANS
which communicate with OS using IP accommodated
in the LAN with additional security requirements.
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 (CCITT) Recommendations and/or ISO/IEC Standards.
The protocol profiles can be applied to DCN, as defined by Recommendation 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.
See clause 6 and its subclauses.
NOTE ? Figure 3/Q.811 (1993), Protocol profile for network management, has been deleted.
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 |
The possible bit rate will be 1 Mbit/s, 10 Mbit/s, or higher.
Administrations will select the appropriate physical medium, e.g. coaxial cable, screened pairs, optical fibre according to technological and operational requirements.
The Data Link layer provides the unacknowledged connectionless-mode service. The access method employed is Carrier Sense Multiple Access with Collision Detection (CSMA/CD).
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.
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.
The definition of the connectionless-mode Network service shall comply with that specified in CCITT Rec. X.213 | ISO/IEC 8348 [6]. Address formats supported shall also conform to CCITT Rec. X.213 | ISO/IEC 8348 [6].
The Network layer shall provide the N-UNITDATA service as specified in CCITT Rec. X.213 | ISO/IEC 8348 [6].
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].
Characteristics of the connectionless-mode Network layer service and the connectionless-mode Network layer protocol shall be as shown in Table 2.
|
Table 2/Q.811 ? Connectionless-mode network layer service/protocol parameters |
|
|
a |
Destination and Source Addresses used by this Protocol shall conform to one of the Network Service Access Points (NSAPs) address formats specified in CCITT 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 CCITT Rec. X.213 | ISO/IEC 8348 [6]. |
|
b |
The setting of Error Reporting Flag (E/R) shall be a local matter (Note). |
|
c |
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. |
|
d |
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. |
|
e |
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. |
|
f |
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. |
|
g |
Lifetime Control ? The lifetime parameter shall be used as specified in 6.4 of ITU‑T Rec. X.233 | ISO/IEC 8473‑1. This parameter shall have an initial value of at least three times the network span (number of network entities) or three times the maximum transmission delay (in units of 500 milliseconds), whichever is greater. The default initial PDU lifetime control shall be 10 seconds. |
|
h |
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. |
|
i |
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. |
|
j |
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. |
|
TMN entities that use the CLNP shall support the ISO 9542 [47] 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 |
General topology (Note 3) |
|
Configuration |
M |
M |
NS |
|
M mandatory
support NOTE 1 ? An example of a point-to-point subnetwork is the SDH DCC. NOTE 2 ? An example of a broadcast subnetwork is a CSMA/CD LAN. NOTE 3 ? An example of a general topology subnetwork is an X.25 packet network. |
|||
|
Table 4/Q.811 ? ES-IS protocol timers and options for the end system role |
||
|
|
Value/Range/Option |
Default |
|
Timers: |
|
|
|
Functions: |
|
|
|
Supplemental Functions per Annex B of
ISO/IEC 9542: |
|
|
|
NOTE 1 ? Applies to Configuration Information (CI) subset. NOTE 2 ? Applies to the Redirection Information (RI) subset. NOTE 3 ? See recommendation in 6.7 of ISO/IEC 9542. NOTE 4 ? See B.4 of ISO/IEC 9542. |
||
|
Table 5/Q.811 ? ES-IS protocol timers
and options for the intermediate system role |
||
|
|
Value/Range/Option |
Default |
|
Timers: |
|
|
|
Functions: |
|
|
|
Supplemental Functions per Annex B
of ISO/IEC 9542: |
|
|
|
NOTE 1 ? Applies to Configuration Information (CI) subset. NOTE 2 ? Applies to the Redirection Information (RI) subset. NOTE 3 ? See recommendation in 6.7 of ISO/IEC 9542. |
||
ISO/IEC 10589 [48], 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.
|
Table 6/Q.811 ? IS-IS general protocol functions |
||
|
Protocol function |
Value/Range/Option |
Default |
|
Authentication |
Optional, use, non-use |
(Non-use) |
|
Table 7/Q.811 ? IS-IS general processes |
||
|
Function |
Value/Range/Option |
Default |
|
Decision Process: |
|
|
|
Table 8/Q.811 ? IS-IS Level 1 specific functions |
||
|
Function |
Value/Range/Option |
Default |
|
Protocol Summary: |
|
|
|
NOTE ? These numbers are preliminary and are subject for study and possible change. |
||
|
Table 9/Q.811 ? IS-IS Level 2 specific functions |
||
|
Function |
Value/Range/Option |
Default |
|
Protocol Summary: |
|
|
|
Decision Process: |
|
|
|
Forward/Receive Process |
|
|
|
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. |
||
|
Table 10/Q.811 ? Level 2 subnetwork dependent functions |
||
|
Function |
Value/Range/Option |
Default |
|
ISO/IEC 8208 Dynamic Assignment: |
|
|
|
Table 11/Q.811 ? IS-IS parameter values and timers |
||
|
Type |
Value/Range/Option |
Default |
|
Parameter Values: |
|
|
|
Timers: |
|
|
Border Intermediate Systems (BISs), using the ISO/IEC 10747 Inter Domain Routing Protocol (IDRP) [49], may be employed for routing ITU-T Rec. X.233 | ISO/IEC 8473-1 CLNP PDUs between Administrative Domains as defined in CCITT Rec. X.213 | ISO/IEC 8348.
The Physical layer service shall be as defined in ITU-T Rec. X.211 | ISO/IEC 10022 [54].
The protocol of the Physical layer of Protocol Profile CLNS2 shall comply with the following specifications:
? X.21 interface in accordance with 1.1/X.25 [12];
? X.21 bis interface in accordance with 1.2/X.25;
? V-Series interface in accordance with 1.3/X.25.
The supported bit rates are: 1200, 2400, 4800, 9600, 19 200, and 64 000 bit/s. The bit rates 48 000 bit/s and 56 000 bit/s may be used for an interim period (see Note 1 to Table 19).
Table 13 lists the connectors to be used in accessing the X.21 and X.21 bis interfaces. Tables 14, 15, and 16 list respectively the pin descriptions of ISO 2110 [38], ISO/IEC 2593 [39], ISO 4902 [66], and ISO 4903 [67].
|
Table 13/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 4903 |
|
56 000 bit/s |
ISO/IEC 2593 |
ISO/IEC 2593 |
|
64 000 bit/s |
ISO 4902 |
ISO 4903 |
|
Table 14/Q.811 ? ISO 2110 [38] pin description (see Note 6) |
|||
|
Pin |
V.24 [35] |
Description |
Notes |
|
1 |
101 |
Protective ground (Shield) |
1 |
|
2 |
103 |
Transmitted Data |
2 |
|
4 |
105 |
Request to Send |
2 |
|
Table 14/Q.811 ? ISO 2110 [38] pin description (see Note 6) (concluded) |
|||
|
Pin |
V.24 [35] |
Description |
Notes |
|
24 |
113 |
Transmitter Signal Element Timing
(DTE to DCE) |
4 |
|
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 Recommendations V.24 [35], V.28 [36], and ISO 2110 [38]. |
|||
|
Table 15/Q.811 ? V.36 [37], ISO/IEC 2593 [39] pin description (see Note 3) |
|||
|
Pin |
Circuit |
Description |
Notes |
|
A |
101 |
Protective Ground |
1 |
|
P |
103 |
Transmitted Data A-wire |
2 |
|
C |
105 |
Request to Send |
|
|
Y |
114 |
Transmitter Signal Element Timing A (DCE
to DTE) |
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 Recommendation V.36 [37]. All other circuits shall conform to Recommendation 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 Recommendations V.36 [37], V.24 [35], V.28 [36], and ISO/IEC 2593 [39]. |
|||
|
Table 16/Q.811 ? ISO 4903 [67] pin description (see Note 2) |
|||
|
Pin |
X.21
circuit |
Description |
Notes |
|
1 |
? |
Protective ground |
1 |
|
2 |
T |
Transmit A-wire |
|
|
3 |
C |
Control A-wire |
|
|
6 |
S |
Signal element timing A-wire |
|
|
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 Recommendations V.10 [68], V.11 [69], X.21, and ISO 4903. |
|||
It is mandatory that the Data Link layer conforms to LAPB as defined in Recommendation 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].
The Data Link layer service shall be as defined in ITU-T Rec. X.212 | ISO/IEC 8886 [61].
When a packet switched network is used to connect systems, they are each designated "Data Terminal Equipment" (DTE) and the network acts as a "Data Circuit-terminating Equipment" (DCE). When a dedicated or dial-up link is provided, other means must be used to supply the DCE role.
At the Physical layer the modems will provide the DCE interface, supplying bit synchronization.
At the link level, the procedures specified in ISO/IEC 7776 [13] shall be followed. A system must be able to start the set-up or reset of the link (a DCE function in Recommendation X.25 [12]). In addition, provision must be made for assignments of the A/B addresses. This mandatory option is to be field-settable and stored in non-volatile memory. Equipment which meets this requirement is compatible with connection to either a DCE or remote DTE.
Support of modulo 8 is mandatory. The window for unacknowledged frames is to be optional between 1 and 7 frames and 1 to 127 with modulo 128. The standard default is 7. For efficient operation over satellite links modulo 128 operation is required, with a default window size of 35.
The user information is to be arranged in an integral number of octets.
The maximum length of the user information shall be user settable, consistent with the range of values for the N1 parameter as shown in Table 17. Maximum information field lengths that shall be supported are 131 and 259 octets with 515, 1027, 2051, and 4099 octets optional. These values provide for three packet header octets and maximum length of User Data Field of 128, 256, 512, 1024, 2048, and 4096 octets, respectively.
Certain other frame parameters shall be set by the user to be consistent with the bit rate, frame size and characteristics of the connecting network. A system design should be sufficiently flexible to accommodate parameter sets for diverse networks, both as order options and later reconfigurations. The range of parameters is shown in Table 17. These options, like those of the Physical layer, are to be set at installation, changeable by the user, and non-volatile.
The connectionless-mode Network layer service shall be as specified in CCITT Rec. X.213 | ISO/IEC 8348.
The protocols for the Network layer shall
be identical to the Network layer protocol of Protocol Profile CONS1 (see 7.85.7.3) 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 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.
|
Table 17/Q.811 ? LAPB Protocol ? Octet
aligned ? |
|||
|
Parameter |
Function |
Range |
Default |
|
K |
I-Frames Window |
1 to 7 (with Modulo 8) |
(7) |
|
T1 |
Waiting Acknowledgment |
|
|
|
T2 |
Response
delay par a) |
Not greater than 0.3 seconds |
|
|
T3 |
Disconnect
Timer |
T3 >> T4b) |
|
|
T4 |
No activity Timer |
4 to 120 seconds |
(20) |
|
N1 |
Bits per I-Frame, excluding flags |
1080, 2104 (with Modulo 8) |
(2104) |
|
N2 |
Retransmission Count |
2 to 16 |
(7) |
|
A/B |
Address Assignment |
Selectable by the user |
|
|
a) Further guidelines on the use of T1 and T2 can be found in Recommendation 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. |
|||
Characteristics of the connectionless-mode Network layer service, and the connectionless-mode Network layer protocol shall be as shown in Table 2.
This subclause defines a Protocol Profile for operation of ISO/IEC 8073 [42] and Recommendation X.224 [43] 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].
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.35.3.3 (and its subclauses) for the
CLNS1 and CLNS2 Protocol Profile cases.
On the B-channel a connection may be provisioned to provide either an OSI Data Link service, or an X.25 packet service.
For B-channels providing the OSI Data Link service defined in ITU-T Rec. X.212 | ISO/IEC 8886 [61], 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.
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.
Recommendation Q.931 [62] shall be used over the D-channel for the purpose of ISDN connection establishment.
ISO/IEC 7776 [13], used in accordance with ITU-T Rec. X.273 | ISO/IEC 11577 [59], shall be used in the B-channel.
Recommendation Q.921 [24] shall be used in the D-channel.
Either Recommendation I.430 [22] (basic rate) or Recommendation I.431 [23] (primary rate) shall be used in the Physical layer.
This subclause defines an additional
protocols profile for use as TMN lower layer
protocols. Theise
profiles areis
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
G.7712 [74] sections 7.1.6 for Network
Layer PDU forwarding function and 7.1.10 for Network Layer Routing Function:
? For
Layer 3 ? STD0005 "Internet Protocol", J. September 1981. (Includes
RFC0791, RFC0950, RFC0919, RFC0922, RFC792, RFC1112).
? The
lower layers are defined in the Ethernet Profile
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 [70] defined by the Internet Engineering Task
Force (IETF). IPsec uses two protocols to provide traffic
security -- Authentication Header (AH) [72] and
Encapsulating Security Payload (ESP)[73]. 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
? For
Layer 3 ? RFC 2460 "Internet Protocol, Version 6 (IPv6) Specification"
[71]
? The
lower layers are specified in the Ethernet Profile.
Note that it is mandatory to
implement IPsec with IPv6.
? For Layer 3 ? STD0005 "Internet
Protocol", J. September 1981. (Includes RFC0791, RFC0950, RFC0919,
RFC0922, RFC792, RFC1112). In addition, when larger addresses are required
RFC1752 (reference RFC1752 "The Recommendation for the IP Next Generation
Protocol", January 1995) should be used when approved.
NOTE ? Currently, RFC1752 is at the Proposed Standard
status.
? The lower layers are not specified.
.[Editor’s Note:
Contributions required for IPv6]
This subclause defines an
additional protocol profile for use as TMN lower layer protocols. This profile
is based on the use of Secure Internet
Protocols [70] defined by the Internet Engineering Task Force (IETF).
When the
DCF within the TMN entities support Ethernet interfaces,
the following functions are required to be support Ethernet Physical Layer Termination
Function and [Network Layer PDU into
Ethernet Frame] Encapsulation Function
An Ethernet Physical Termination Function
terminates the physical Ethernet interface.
One or more of the following rates shall be
supported: 1 Mbps, 10Mbps, 100 Mbps.
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 [77].
·
IP
addresses shall be mapped to Ethernet MAC addresses utilizing the Address
Resolution Protocol in RFC 826 [78].
It shall determine the received frame type (802.3
or Ethernet version 2 ) as per Section 2.3.3 in
RFC 1122 [75].
See 5.4.1.
See 5.4.2.
It is mandatory that the packet layer conforms to Recommendation 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 Recommendation X.223 [17] shall apply.
The attributes which must be supported are summarized in Tables 18 and 19. 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).
|
Table 18/Q.811 ? X.25 [12] packet layer attributes for permanent virtual circuits |
||
|
Feature |
Range |
Default |
|
Extended Packet |
Modulo 128 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. |
||
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 Recommendations 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 CCITT Rec. X.213 | ISO/IEC 8348 [6] shall be supported.
Additional numbering plans, such as Q.708 for SS7 [58], may be supported in the future as the evolution of new subnetwork technologies require.
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 Appendix I.
The initiator shall be capable of proposing the non-use of the expedited data service. Responders shall be capable of receiving requests for the expedited data service, but shall be capable of responding with non-use of the service. The expedited data service is neither required nor precluded by this Recommendation.
|
Table 19/Q.811 ? X.25 [12] packet layer attributes for switched virtual circuits |
||
|
Feature |
Range |
Default |
|
Flow Control Parameter |
128, 256 |
128 |
|
Window size |
1-7 (with Modulo 8) |
2 |
|
Extended Sequence |
1-127 (with optional Modulo 128) |
2 (Note 5) |
|
Throughput Class (Note 1) |
1200, 2400, 4800, 9600, 19 200 and 64 000 |
2400 |
|
Expedited Data Negotiation Bilateral Closed User Group Selection |
Optional |
|
|
Fast Select |
128 octets |
|
|
Hunt Group |
Optional |
|
|
Transit Delay Selection and Indication |
|
|
|
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.2.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 A negotiation rules specified in the International Standards. NOTE 5 ? The default window size for satellite operations is 35. |
||
The initiator shall be capable of setting bit 7 of the General Format Identifier to 0. Responders shall be capable of receiving bit 7 set to 1, but shall be capable of responding with bit 7 set to 0. The Receipt Confirmation Service is neither required nor precluded by this Recommendation.
When the end system requires only one Network layer connection on a physical access port, support of throughput classes up to the access line transmission rate is required. When multiple Network layer connections are required, support of the throughput class equal to the access line transmission rate is optional. Further study of Throughput Class range and default values at various access line rates is needed.
Interoperability is achieved by having the initiator propose a packet size from the set specified in Tables 18 and 19 and by the responder selecting the most appropriate packet size between 128 and the proposed packet size. The rules for negotiation of the size of the packet to be used in a given instance of communication are specified in ISO/IEC 8208 [16].
The choice of packet size is a local issue which can depend on, for example, the overall Quality of Service requested or needed by the user or Application Layer, and the subnetwork characteristics.
When the packet level X.25 interface is used, automatic selection of the DCE/DTE role during restart is required, as specified in ISO/IEC 8208 [16].
The packet layer attributes are summarized in Tables 18 and 19.
When layers above X.25 are used, the initial octets of (N)-DATA primitive and the corresponding user data field are used for peer-to-peer protocol data for those layers.
In following the procedures of Recommendation X.244 [20], ISO/IEC TR 9577 [21], and Annex B of ISO/IEC 8073 [42] and Recommendation X.224 [43], the initial octets of the user data field of the call request packet may only be used for protocol identification. For those cases in which the fast select feature is used, the call request packet may contain a call user data field of up to 128 octets.
The Physical layer conforms to Recommendations I.430 [22] for basic rate access and I.431 [23] for primary rate access.
The link layer C-plane conforms to Recommendation Q.921 [24] with the default parameters specified for links within the SAP identified by SAPI = 0.
The Network layer C-plane conforms to Recommendation Q.931 [62]. Q.931 procedures are used as described in Recommendation X.31 [25] with encodings for information elements according to Recommendation X.31.
The link layer U-plane profile conforms to Recommendation Q.921 [24] with the default parameters specified for links within the SAP identified by SAPI = 16.
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 19.
CCITT Rec. X.612 | ISO/IEC 9574 [40] provides the connection-mode Network service to packet mode terminal equipment connected to ISDN.
The Physical layer conforms to Recommendations I.430 [22] for basic rate access and I.431 [23] for primary rate access.
The link layer C-plane conforms to Recommendation Q.921 with the default parameters specified for links within the SAP identified by SAPI = 0.
The Network layer C-plane conforms to Recommendation Q.931. Q.931 procedures are used as described in Recommendation X.31 with encodings for information elements according to Recommendation X.31.
The link layer U-plane conforms to International Standard ISO/IEC 7776 for Single Link Procedures (SLPs) in DTE-DCE operation. The link layer attributes are specified in Table 17.
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 B-channel which is 64 kbit/s. The Network layer attributes are specified in Table 19.
CCITT Rec. X.612 | ISO/IEC 9574 [40] provides the connection-mode Network service to packet mode terminal equipment connected to ISDN.
? Layer 1 conforms to MTP (Level 1) [27].
? Layer 2 conforms to MTP (Level 2) [28].
? Layer 3 conforms to MTP (Level 3) [29] and SCCP [30] to [34].
NOTE ? Further study is needed for the function of SCCP at the boundary of Network layer and Transport layer.
? Layer 4 ? OSI Transport layer per ITU-T Rec. X.214 | ISO/IEC 8072 [41], ISO/IEC 8073 [42] and Recommendation X.224 [43].
See 7.3.15.3.1.
See 5.3.2, and replace "Type 1" by "Type 2".
For further study.
This subclause 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 23.
|
Table 23/Q.811 ? Summary of ISP-based protocol profile conformance requirements |
||||
|
|
|
|
Q.811 references |
|
|
Protocol |
Protocol |
|
|
|
|
CONS1 |
|
|
4.1 |
Table 24 |
|
|
|
|
|
|
|
|
Network |
ISO/IEC ISP
10609-9 [46] Subnetwork Dependent Requirements (TB1111/TB1121) as modified by
Table |
7.8.3 |
Tables 18, 19
and |
|
|
Data Link |
ISO/IEC ISP
10609-9 Subnetwork Dependent Requirements (TB1111/TB1121) as modified by
Table |
7.8.2 |
Tables 17 and |
|
|
Physical |
ISO/IEC ISP
10609-9 Subnetwork Dependent Requirements (TB1111/TB1121). |
7.8.1 |
Tables 13, 14,
15 and 16 |
|
CLNS1 |
|
|
4.3 |
Table 24 |
|
|
|
|
|
|
|
|
Network ISO/IEC
8473 CLNP |
ISO/IEC ISP
10608-1 Subnetwork Independent Requirements as modified by Table |
7.3.3 |
Table 2, Tables
3 to 11 (where applicable), Table |
|
|
Data Link |
ISO/IEC ISP
10608-2 (TA51) [45]. |
7.3.2 |
|
|
|
Physical |
ISO/IEC ISP
10608-2 (TA51). |
7.3.1 |
Table 1 |
|
CLNS2 |
|
|
4.4 |
Table 24 |
|
|
|
|
|
|
|
|
Network ISO/IEC
8473 CLNP |
ISO/IEC ISP
10608-1 Subnetwork |
7.4.3 |
Table 2, Tables
3 to 11 (where applicable) |
|
|
Network ISO/IEC
8208 X.25 PLP |
ISO/IEC ISP
10608-5 |
7.4.3.2 |
Tables |
|
|
Data Link |
ISO/IEC ISP
10608-5 (TA1111/TA1121) |
7.4.2 |
Tables 17 and |
|
|
Physical |
ISO/IEC ISP 10608-5 |
7.4.1 |
Tables 13, 14,
15 and 16 |
|
CLNS1/ CLNS2
Int'work |
Network |
ISO/IEC ISP
10613-7, 10613-8, 10613‑9 (RA51.11x1). |
|
|
|
IPv4 |
Network |
STD0005
"Internet Protocol", J. September 1981. (Includes RFC0791, RFC0950,
RFC0919, RFC0922, RFC792, RFC1112). |
7.6.1 |
|
|
IPv4
with IPsec |
Network |
RFC 2401
(1998) “Security Architecture for the Internet Protocol” with additional
required specified in Section 7.6.2 |
7.6.2 |
|
|
IPv6 |
Network |
RFC 2460
"Internet Protocol, Version 6 (IPv6) Specification" [71] |
7.6.3 |
|
|
Ethernet |
Data
Link |
RFC 1122 |
0 |
|
Network layers shall conform to ISO/IEC ISP
10608, Part-1, as modified by Table III.5.
Physical and Data link layers shall conform to ISO/IEC ISP 10608, Part-2
(TA51).
Network (CLNP) layers shall conform to
ISO/IEC ISP 10608, Part-1, as modified by Table III.5.
Packet layer shall conform to ISO/IEC ISP 10608-5 as modified by Tables III.2
and III.4.
Physical and Data link layers shall conform to ISO/IEC ISP 10608, Part-5
(TA1111/TA1121).
Network and lower layers are
under study.
Packet layer shall conform to ISO/IEC ISP
10609-9, as modified by Table III.2. Data link
and Physical layer profiles shall conform to ISO/IEC ISP 10609-9
(TB1111/TB1121), as modified by Table III.3.
Network shall conform to ISO/IEC ISP 10609-9.
Data link (LLC and MAC) and Physical layers shall conform to ISO/IEC ISP 10609-10.
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.
The group of subnetworks described in clause 5 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).
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 CCITT Rec. X.213 | ISO/IEC 8348.
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].
ITU-T Rec. X.273 | ISO/IEC 11577 [59] 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].
This subclause 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, ISO/IEC 8073 [42] and Recommendation X.224 [43], 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;
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 [57]. How the Network internal layer service is provided for relaying between X.25 packet systems is given in ISO/IEC 10177 [56].
A general guide to interworking between the various Transport profile groups is given is ISO/IEC TR 10000-2 [65].
How relaying is performed between CLNS-based subnetworks is defined in ITU‑T Rec. X.233 | ISO/IEC 8473-1 [7].
Table 24 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.
|
Table 24/Q.811 ? Interworking between protocol profiles |
|||||||||
|
|
CONS1 |
CONS2 |
CONS3 |
CONS5 |
CONS6 |
CLNS1 |
CLNS2 |
CLNS3 |
ISO TP0/TCP/IP |
|
CONS1 |
Rec. |
Rec. |
Rec. |
Rec. |
Rec. |
Non-OSI |
Non-OSI |
Non-OSI |
Non-OSI |
|
CONS2 |
|
OSI |
OSI |
OSI |
OSI |
Non-OSI |
Non-OSI |
Non-OSI |
Non-OSI |
|
CONS3 |
|
|
OSI |
OSI |
OSI |
Non-OSI |
Non-OSI |
Non-OSI |
Non-OSI |
|
CONS5 |
|
|
|
OSI |
OSI |
Non-OSI |
Non-OSI |
Non-OSI |
Non-OSI |
|
CONS6 |
|
|
|
|
OSI |
Non-OSI |
Non-OSI |
Non-OSI |
Non-OSI |
|
CLNS1 |
|
|
|
|
|
OSI (CLNS) |
OSI (CLNS) |
OSI (CLNS) |
Non-OSI |
|
CLNS2 |
|
|
|
|
|
|
OSI (CLNS) |
OSI (CLNS) |
Non-OSI |
|
CLNS3 |
|
|
|
|
|
|
|
OSI (CLNS) |
Non-OSI |
|
IP |
|
|
|
|
|
|
|
|
|
|
Non-OSI Interworking above the Network layer may be required. OSI Interworking is either connectionless-mode (CLNS) or connection-mode (CONS) within the Network layer. NLR Interworking is within the
Internet Network layer (i.e. the IP layer). |
|||||||||
Two functions as defined by
G.7712 shall be supported by TMN entity when IP is
connected to an entity with OSI only for inter-working. These are Network Layer
PDU interworking and IP Routing Interworking. The PDU interworking is supported
using Network Layer PDU Encapsulation function (section 7.1.8 of G.7712) and
Network Layer PDU tunnelling function (section 7.1.9 of G.7712). The IP Routing
Interworking function is supported using Integrated IS-IS routing as defined in
section 7.1.10 of G.7712.”
Protocol stack for information transfer over ISDN transparent B-channel
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.
The Physical layer conforms to Recommendations I.430 for basic rate access and I.431 for primary rate access.
A.2.2 Link layer C-plane profile
The link layer C-plane conforms to Recommendation Q.921 with the default parameters specified for links within the SAP identified by SAPI = 0.
A.2.3 Network layer C-plane profile
The Network layer C-plane conforms to Recommendation Q.931 for circuit-switched call control procedures using codings of information element as in Table A.1.
|
Table A.1/Q.811 ? Q.931 Information element encodings in support of CONS4 |
|
|
Bearer Capability (BC) information element codings |
|
|
Coding
standard (octet 3) |
CCITT |
|
Called party number information element codings |
|
|
Type of number (octet 3) |
International/national/subscriber |
|
Called/calling party subaddress information element codings |
|
|
Type of number (octet 3) |
NSAP |
|
Low Layer Compatibility (LLC) information element codings |
|
|
Coding standard (octet 3) User information layer 3 protocol (octet 7) |
CCITT Normal (modulo 8)/extended (modulo 128) |
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 endsystems which are the members of a TMN.
A.2.5 Link layer U-plane profile
The link layer U-plane conforms to International Standard ISO/IEC 7776 for Single Link Procedures (SLPs) in DTE-DTE operation. The link layer attributes are specified in Table 17.
A.2.6 Network layer U-plane profile
The Network layer U-plane conforms to International Standard ISO/IEC 8208 for DTE-DTE operation over circuit-switched connections.
Determining "DTE" or "DCE" characteristics is based on restart procedure:
a) acts as "DCE" when receiving RESTART INDICATION packet with the restarting cause field "DTE originated" and no restart collision occurred;
b) acts as "DTE" when a RESTART REQUEST packet is subsequently confirmed with a RESTART CONFIRMATION packet (no restart collision occurred);
c) re-initiates a restart procedure when a randomly-chosen time has elapsed following the detection of a restart collision.
The Network layer attributes specified in Table 19 apply with the additions contained in Table A.2.
|
Table A.2/Q.811 ? Additional U-plane
network layer attributes and |
||
|
? |
The throughput class corresponds to the access-line bit rate of the B‑channel which is 64 kbit/s. |
|
|
? |
The Network layer parameters which apply are: |
|
|
T20 |
Restart
requires response timer |
180 seconds |
|
T21 |
Call request
response timer |
200 seconds |
|
T22 |
Reset request
response timer |
180 seconds |
|
T23 |
Clear request
response timer |
180 seconds |
|
T24 |
Window status transmission timer |
Not applicable |
|
T25 |
Window rotation timer |
Not applicable |
|
T26 |
Interrupt
response timer |
180 seconds |
|
T27 |
Reject response timer |
Not applicable |
|
T28 |
Registration
request response timer |
Not applicable |
|
|
|
|
|
R20 |
Restart request retransmission count |
1 |
|
R22 |
Reset request retransmission count |
1 |
|
R23 |
Clear request retransmission count |
1 |
|
R25 |
Data packet retransmission count |
Not applicable |
|
R27 |
Reject retransmission count |
Not applicable |
|
R28 |
Registration request retransmission count |
Not applicable |
The Synchronization and Coordination Function (SCF) (see Recommendation I.320 [63]) provides the connection-mode Network service to the Network service user.
Examples of NSAP structures for CLNP
This Appendix summarizes four examples of NSAP structure. Figures I.1, I.2, and I.3 show NSAP structures based on ISO-DCC. Figure I.4 shows an NSAP structure based on ISO-ICD.
|
|
IDP |
DSP |
||||
|
|
AFI |
IDI |
|
|||
|
|
39 |
a) |
JDI# |
AREA |
SYSTEM |
SEL |
|
Number of octets |
1 |
2 |
3 |
n |
6 |
1 |
|
|
a) ISO DCC
(value of 392 as Japan). # JDI
(value of 100009 as NTT) |
|||||
Figure B.1/Q.811 ? DCC type NSAP address format in Japan Standard
|
|
IDP |
DSP |
||||
|
|
AFI |
IDI |
|
|||
|
|
39 |
a) |
ORG |
AREA |
SYSTEM |
SEL |
|
Number of octets |
1 |
2 |
3 |
2 |
0-6 |
1 |
|
|
a) ISO DCC. ORG Organization
Identifier |
|||||
Figure B.2/Q.811 ? ECMA 117 NSAP format
|
|
IDP |
DSP |
|||||||
|
|
AFI |
IDI |
DFI |
|
|||||
|
|
39 |
a) |
128 |
org |
res |
rd |
AREA |
SYSTEM |
SEL |
|
Number of octets |
1 |
2 |
1 |
3 |
2 |
2 |
2 |
6 |
1 |
|
|
a) ISO DCC. DFI The
DSP Format Identifier |
||||||||
Figure B.3/Q.811 ? ANSI NSAP address format
|
|
IDP |
DSP |
||||
|
|
AFI |
IDI |
|
|||
|
|
47 |
a) |
DI |
FI |
TI |
SEL |
|
Number of
octets |
1 |
2 |
3 |
1 |
12 |
1 |
|
|
a) ISO ICD. DI Domain Identifier |
|||||
Figure B.4/Q.811 ? ICD type NSAP address format for AOTC-Australia
Changes to ISP Conformance requirements
(Normative)
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 16 and 17 uses either a one-or two-character notation. The one-character 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.
2) Dynamic:
m Mandatory (use is mandatory).
x Excluded (use is prohibited within the context of this profile).
? Not applicable.
Table I.1/Q.811 ? Network layer |
||||||
|
Base
Standard |
ISP |
Rec. Q.811 |
||||
|
Ident. |
Feature |
Subclause |
Status |
Status |
Subclause |
Status |
|
Et/d |
DTE/DTE with
dynamic role selection |
4.5 |
Vs: O.2 |
oi |
5.7.3.3.1 |
mm |
|
M128 |
Modulo 128 |
13.2, |
O.3 |
ox |
Table 19 |
oo |
|
V2s |
Default
window sizes |
16.2.2.6 |
M8: 1-7 |
M8: 1-7 |
Table 19
Table 19 |
M8: 2 |
|
V2r |
Default
window sizes |
16.2.2.6 |
M8: 1-7 |
M8: 1-7 |
Table 19
Table 19 |
M8: 2 |
|
V10s |
Window sizes |
15.2.2.1.2 |
M128: 1-127 |
M128: o- |
Table 19 |
M128: |
|
V10r |
Window sizes |
15.2.2.1.2 |
M128: 1-127 |
M128: o- |
Table 19 |
M128: 1-1 |
|
T24 |
Window
Status |
|
O |
ox |
Table 19 |
oo |
|
T25 |
Window Rotation
Timer |
|
O |
ox |
Table 19 |
oo |
|
FS5 |
Bilateral Closed
User Group Selection |
13.15 |
O |
|
Table 19 |
oo |
|
Table I.2/Q.811 ? Data link layer |
||||||
|
Base
Standard |
ISP |
Rec. Q.811 |
||||
|
Ident. |
Feature |
Subclause |
Status |
Status |
Subclause |
Status |
|
|
DTE/DTE
Interworking |
0 |
O |
oi |
5.4.2.2.1 |
m |
|
T2 |
Parameter T2 procedure |
5.7.1.2, |
O |
|
Table 17 |
m |
|
T3 |
Parameter T3 procedure |
5.7.1.3 |
O |
|
Table 17 |
m |
|
T4 |
Parameter T4 procedure |
5.7.1.4, |
O |
|
Table 17 |
m |
|
SP8 |
If Modulo 8 was
checked with SLP |
5.7.3 |
M |
|
Table 17 |
m |
|
SP128 |
If Modulo 128
was checked with SLP |
|
M |
|
Table 17 |
m |
NOTE for Tables III.1,
III.2
and III.3
? The referenced ISP is ISO/IEC ISP 10609, Parts 1 and 9 (TB1111/TB1121) [46].
|
Table I.3/Q.811 ? CLNS2 protocol case ? Packet layer |
||||||
|
Base
Standard |
ISP |
Rec. Q.811 |
||||
|
Ident. |
Feature |
Subclause |
Status |
Status |
Subclause |
Status |
|
Vp |
PVC |
|
O.1 |
i |
|
& |
|
Vs |
VC |
|
O.1 |
mm |
|
& |
|
Et/d |
DTE/DTE with |
4.5 |
Vs: O.2 |
Vs: i |
7.5.3 |
mm |
|
Table I.4/Q.811 ? CLNS2 and CLNS1
protocol cases ? |
||||||
|
Base Standard |
ISP |
Rec. Q.811 |
||||
|
Ident. |
Feature |
Subclause |
Status |
Status |
Subclause |
Status |
|
|
QOS Maintenance |
7.5.6 |
O |
i |
Table 2 |
mm |
NOTE for Tables III.4
and III.5
? Reference is to ISO/IEC ISP 10608, Parts 1, 2 (TA51), and Part 5
(TA1111/TA1121) [45].
______________________
