Search
×
FR

Placeholder headline

This is just a placeholder headline

API Technical Report TDB-6 Chapter 6 – Density

$

204

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 560: Fired Heaters for General Refinery Services

$

721

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 64: Diverter Equipment Systems

$

324

BUY NOW

Placeholder headline

This is just a placeholder headline

API MPMS CH 17.10.1: Refrigerated Light Hydrocarbon Fluids – Measurement of Cargoes on Board LNG Carries

$

417

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 13B-1: Testing Water-based Drilling Fluids

$

418

BUY NOW

Placeholder headline

This is just a placeholder headline

API Technical Report TDB-12 Chapter 12 – Thermal Conductivity

$

214

BUY NOW

Placeholder headline

This is just a placeholder headline

API 16FI Frac Iron Guidelines and Requirements

$

129

BUY NOW

ISO 10021:1999

ISO 10021:1999 Information technology – Message Handling Systems (MHS): MHS Routing – Guide for messaging systems managers – Part 11:

CDN $351.00

SKU: 06a61e81de03 Categories: ,

Description

This Recommendation | Technical Report specifies the means by which the administrator of various aspects of an MHS

system may configure information into the directory for MTAs to use to determine the routing of messages.

ITU-T Rec. X.412 | ISO/IEC 10021-10 provides a set of directory structures that may be configured in many different

ways to support a particular MHS routing strategy. In order to illustrate the use of these directory structures, this

document contains advice on how an MHS Administrator might organize the configuration of directory trees and entries

in the directory. In particular, it contains suggestions on the following:

? The types, construction and location of different OR-address subtrees that may be needed;

? The location of routing collective and MTA entries in the directory.

Other ways of using the routing capabilities specified in ITU-T Rec. X.412 | ISO/IEC 10021-10 are also valid.

Other Recommendations | International Standards define other aspects of the MHS. ITU-T Rec. F.400/X.400 |

ISO/IEC 10021-1 defines the user-oriented services provided by the MHS. ITU-T Rec. X.402 | ISO/IEC 10021-2

provides an architectural overview of the MHS. ITU-T Rec. X.411 | ISO/IEC 10021-4 defines the abstract-service of the

Message Transfer System. ITU-T Rec. X.412 | ISO/IEC 10021-10 defines MHS Routing using the directory.

Edition

1

Published Date

1999-12-15

Status

PUBLISHED

Pages

57

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

This Recommendation | Technical Report specifies the means by which the administrator of various aspects of an MHS

system may configure information into the directory for MTAs to use to determine the routing of messages.

ITU-T Rec. X.412 | ISO/IEC 10021-10 provides a set of directory structures that may be configured in many different

ways to support a particular MHS routing strategy. In order to illustrate the use of these directory structures, this

document contains advice on how an MHS Administrator might organize the configuration of directory trees and entries

in the directory. In particular, it contains suggestions on the following:

? The types, construction and location of different OR-address subtrees that may be needed;

? The location of routing collective and MTA entries in the directory.

Other ways of using the routing capabilities specified in ITU-T Rec. X.412 | ISO/IEC 10021-10 are also valid.

Other Recommendations | International Standards define other aspects of the MHS. ITU-T Rec. F.400/X.400 |

ISO/IEC 10021-1 defines the user-oriented services provided by the MHS. ITU-T Rec. X.402 | ISO/IEC 10021-2

provides an architectural overview of the MHS. ITU-T Rec. X.411 | ISO/IEC 10021-4 defines the abstract-service of the

Message Transfer System. ITU-T Rec. X.412 | ISO/IEC 10021-10 defines MHS Routing using the directory.

Previous Editions

Can’t find what you are looking for?

Please contact us at: