Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

24
Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008

Transcript of Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Page 1: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Directory Service

AMHS Implementation

WorkshopChennai, India

15th – 17th December 2008

Page 2: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

List of Topics

• Concept of Directory Service

• ATN Specific Object Classes

• Uses of Directory

• Asia/Pacific Interim AMHS Database

Page 3: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Definition of Directory

• Definition from SARPs

“The Directory is a collection of systems which cooperate to hold a logical database of information about a set of objects in the real world.”

Page 4: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Concept of Directory Services

• Information Model– Schema– Directory Information Tree (DIT)– Directory Information Base (DIB)– Object Classes– Attributes

Page 5: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Concept of Directory Services

Page 6: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

ATN Directory Systems

• ATN Directory System (ATN DIR) consists of 3 main elements– Directory Information Base (DIB)– Directory Service Agent (DSA)– Directory User Agent (DUA)

Page 7: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

ATN Directory Information Base

• The information held in the ATN DIR is collectively known as the Directory Information Base (DIB).

• The structure of the DIB, called the Directory Information Tree (DIT), defines the hierarchy of record types contained in the directory.

Page 8: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

ATN Directory Information Base

• Each record type is defined by an object class.

• The fields of each record are defined by attributes.

• The Directory Schema defines which attributes are contained in each object class.

Page 9: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

ATN Directory Service Agent

• ATN Directory Service Agent (DSA) • DSA is an application process that provide

access to the DIB to DUAs and/or other DSAs.

• Answers directory information requests.• Maintains the data base locally and interact

with other DSA in order to process requests.

Page 10: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

ATN Directory User Agent

• ATN Directory User Agent (DUA)• Interface to the directory information for

applications.• Requests directory information from attached

DSA. The DSA can subsequently forward the request to relevant DSA.

• Updates information in the DSAs via attached DSA.

Page 11: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Concept of Directory Services

• ICAO Doc 9705 – ATN SARPs Ed. 3 Sub-Volume 7– Definition of Directory for the ATN

environment– Directory Object Class Specification and

Attributes for Directory Service Agent (DSA) and Directory User Agent (DUA)

– Directory System Schema– Directory System Protocol

Page 12: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

ATN Specific Object Classes

• atn-Organization

• atn-OrganizationalUnit

• atn-OrganizationalPerson

• atn-OrganizationalRole

• atn-ApplicationEntity

• atn-CertificationAuthority

• atn-Aircraft

Page 13: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

ATN Specific Object Classes

• atn-AmhsUser• atn-AmhsDistributionList• atn-AmhsUserAgent• atn-AmhsGateway• atn-Facility• atn-AmhsMD• atn-IdrpRouter• atn-DirectorySystemAgent

Page 14: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Uses of Directory

• ATN AMHS– Name to O/R address look-up and broadcast.

• CM– Application capability look-up

• Security– Certificate look-up and broadcast

Page 15: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

AMHS Uses of Directory

• Possible uses of AMHS Directory by AMHS MTAs:– retrieval of remote MTA information

• NSAP• MTA name and password• service capabilities

Page 16: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

AMHS Uses of Directory

• Possible uses of ATN Directory for AMHS Users:– Name Resolution– Distribution-list (DL) Expansion;– Determination of User Capabilities;– Address Conversion; and– Use of certificates for user/message

authentication

Page 17: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Asia/Pacific Interim AMHS DB

• In the ATNTTF 7th in 2005, the issue of AMHS Address database was discussed.

• In 2007, the Asia/Pacific Interim AMHS DB was operational.

• Data format is based on the Asia/Pacific AMHS MTA/UA Naming Registration Table & Contact List

• This DB is “Off-line” database.

Page 18: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Asia/Pacific Interim AMHS DB

• AMHS MTA/UA Registration Table– Contracting State : Authority administering the MTA.– MTA ID : Numbering scheme where each MTA is assigned with

an ordinal number.– User Agent ID : Sub-ordinate number assigned to the User

Agent Name registered under a MTA.– Addressing scheme : Addressing scheme recommended by

ATN SARPS. Values are limited to XF or CAAS.– Country-name : The “C” value of AMHS MD identifier.– Administration-domain-name : The “A” value of AMHS MD

identifier.– Private-domain-name : The “P” value of AMHS MD identifier.– Organization name : The “O” value of attributes identifying an

geographical unit or an organization within MD.

Page 19: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Asia/Pacific Interim AMHS DB

• AMHS MTA/UA Registration Table– Organization-unit-name-1 : The “OU1” value of attributes

identifies 4-letter location indicator within the organization “O”.– User Agent (Direct User only) : The “CN” value (Common

Name) of attributes identifies a User Agent (UA) i.e. direct user within MD.

– Description of user : Brief description of the UA, the direct user. NOC = network operating centre

– MTA Name : The name of the MTA hosting the AMHS user. (Used in AMHS binds.)

– NSAP address : NSAP address of the MTA. TSEL value : TSEL value of the MTA.

– Capability : The type of services supported by the MTA.

Page 20: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Asia/Pacific Interim AMHS DB

• AMHS MTA Administration Contact List– Contracting State : Authority administering the MTA.– MTA ID : Numbering scheme where each MTA is assigned with

an ordinal number.– MTA Name The name of the MTA hosting the AMHS user.

(Used in AMHS binds.)– Point of contact : Name of person responsible for the

administration of the MTA.– Contact e-mail address : E-mail address of the Office or

person responsible for the administration of the MTA.– Contact telephone number & Fax number:– Contact mailing address Official correspondence address of

the Office or person responsible for the administration of the MTA.

Page 21: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Asia/Pacific Interim AMHS DB

http://amhsdb.aerothai.co.th

Page 22: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Asia/Pacific Interim AMHS DB

Page 23: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Asia/Pacific Interim AMHS DB

Page 24: Directory Service AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008.

Thank you