Hierarchical Addressing Protocol

Appendix B: Hierarchical Addressing Protocol

This is an extract and update from the original document. The specific regional and area designators have been removed, since they are determined on a local basis.

Authors:

Dave Wolf, WO5H

Barry Buelow, WA0RJT

Roy Engehausen, AA4RE

Hank Oredson, W0RLI

Greg Jones, WD5IVD

Date:

August 30th, 1994

Adopted by TAPR:

March 3rd, 1995

Introduction

The TAPR BBS Special Interest Group recommends the adoption of the x.3.4 hierarchical address protocol.

After discussion of previous articles on hierarchical addressing standards (1,2) and taking into account international issues of regional/state name sizes, the TAPR BBS Special Interest Group recommends the adoption of the x.3.4 standard on an international basis. x is defined as 2, 3, or 4 letter region names as defined by the country.

Examples of x.3.4:

@WA6GVD.CA.USA.NOAM

@EA2CMO.EAZ.ESP.EURO

@F5JGK.FAQI.FRA.EURO

Regional identifiers may be duplicated in different countries (i.e. AK, Alaska, USA, could be used in another country as a regional identifier); however, Country and Continental identifiers SHOULD NOT be used as regional names.

It is important to note that there is a distinct and significant difference between HIERARCHICAL ADDRESSES and FLOOD DESIGNATORS. Hierarchical address elements are common to all messages (bulletins, P and T types) and are the foundation of the digital forwarding system. Flood designators are used for routing and filtering bulletins. Geographical flood designators are likely based upon hierarchical address elements. It is therefore important that any attempt to establish standards concentrate first on hierarchical address elements. Standards for flood designators can follow.

It is the purpose of this document to generate a changing recommendation that reflects current hierarchical routing. Reference Tables at the end will be changed as necessary to reflect current configurations within the international BBS network. These tables will need to be changed and updated in order to meet future needs of user and sysops.

Hierarchical Routing Syntax Summary

This summary uses a modified Backus-Naur form to summarize the syntax for hierarchical addressing. Optional fields are shown within square braces.

Hierarchial_address = bbs.["#"area.]region.country.continent

bbs = Callsign as defined by the local communications authority.

Area = additional identifier depending on local requirements.

Region = As defined by the local country. This is normally the abbreviation for the state, province, prefecture, etc.

Country = 3-character country identifier as defined by ANSI X.12 and EDIFACT. Published in ISO 3166-1981(E/F).

Continent = 4-character continental identifier from the following table.

TABLE 1: Continent Identifiers

EURO	Europe
MEDR	Mediterranean
INDI	Indian Ocean including the Indian subcontinent
MDLE	Middle East
SEAS	South-East Asia
ASIA	The Orient

NOAM	North America (Canada, USA, Mexico)
CEAM	Central America
CARB	Caribbean
SOAM	South America

AUNZ	Australia/New Zealand
EPAC	Eastern Pacific
NPAC	Northern Pacific
SPAC	Southern Pacific
WPAC	Western Pacific

NAFR	Northern Africa
CAFR	Central Africa
SAFR	Southern Africa

ANTR	Antarctica

Examples:

F6CNB.#SETX.TX.USA.NOAM

KB7WE.#WWA.WA.USA.NOAM

OH6RBV.#VAA.FIN.EURO

SK2AT.AC.SWE.EURO

OH6RBG.FIN.EURO

KE7KD.#NONEV.NV.USA.NOAM

WX3K.#NOCAL.CA.USA.NOAM

References:

1. Jenkins, Lew (N6VV), Dave Toth (VE3GYQ), and Hank Oredson (W0RLI). International Routing Designators. Proceedings of the ARRL 7th Computer Networking Conference. Columbia Maryland. October 1, 1988. pp. 91-93.

2. Clark, Tom (W3IWI). Some comments on the Hierarchical Continent Address Designator. Proceedings of the ARRL 9th Computer Networking Conference. London, Ontario Canada. September 22, 1990. Pp. 278-279.