| |
PA2AGA > HDDIG 18.07.00 22:16l 189 Lines 7649 Bytes #-9313 (0) @ EU
BID : HD_2000_185B
Read: GUEST
Subj: HamDigitalDigest 2000/185B
Path: DB0AAB<DB0ZKA<DB0KFB<DB0CZ<F6KFG<DB0PSC<DB0ACH<PI8JOP<PI8ZAA<PI8HGL
Sent: 000711/1945Z @:PI8HGL.#ZH1.NLD.EU #:61027 [Den Haag] FBB $:HD_2000_185B
From: PA2AGA@PI8HGL.#ZH1.NLD.EU
To : HDDIG@EU
Date: Tue, 11 Jul 00 20:50:45 MET
Message-Id: <hd_2000_185B>
From: pa2aga@pe1mvx.ampr.org
To: hd_broadcast@pa2aga.ampr.org
X-BBS-Msg-Type: B
Date: (null)
From: (null)
Hello all,
recent msgs originating in Europe and some requests from SysOps to translate
into English language a document (see ref. 4 of attached text), concerning
some notes about 'Forwarding designator elements' written in italian language,
prompt me to collect, and then, studying and synthetizing, the most recent
'official' documentation, with the aim also to revisit and up-to-date our ham
documentation.
I hope to be suceeded in elaborating the present work and that, this might
help someone on the matter and so, as a contribute for all ham-radio
community.
--
73 de Gus i0ojj
------------------------------cut here--------------------------------------
22 June 2000
HIERARCHICAL ADDRESSES AND FORWARDING DESIGNATOR ELEMENTS
(A revisited and up-to-dated proposal for packet-radio
*standards* by Gus, i0ojj)
References:
-----------
1. BBS Hierarchical Addressing Protocol - Dave Wolf, WO5H et
al. - August 30th, 1994.
2. International Routing Designators - Jenkins, Lew N6VV et
al. - October 1, 1988.
3. Some comments on the Hierarchical Continent Address
Designator - Clark, Tom W3IWI - September 22, 1990.
4. Elementi designatori del forwarding (only IT) - Gus Ponza,
I0OJJ - 5 February 1998 (up-to-dated and superseded by the
present proposal).
5. Working Paper on Creation of Dot-EU Top-Level Domain -
European Commission - 2 February 2000 - approved last days
also at level of individual Governments of European Union.
6. Countries or areas, codes and abbreviations - revised 16
February 2000 (ISO ALPHA-3 code).
7. Composition of macro geographical (continental) regions and
component geographical regions - revised 16 February 2000.
8. Various documentation collected from packet-radio network
during about a decade as PBBS SysOp.
Foreword:
---------
The following would be a *further* attempt to define the
information that should be placed in the "TO" and the "@"
portions of a message.
These info will help to comprise the HIERARCHIAL ADDRESS
of a message and consequently it concerns with the correct
compilation of forwarding files.
The two types of messages that are discussed here are
PERSONAL and BULLETINS.
If it is a Personal message, the first line that is sent may
look like |
this: +---+-------------- (S)end the (P)ersonal message
| +------- (TO) IK1GKJ
| | +--- distribute to the PBBS IK1MSL
| | | located in Piemonte region
| | | in ITA
| | | in EUROPE
-+ -----+ +-----------------
example 1: SP IK1GKJ @ IK1MSL.IPIE.ITA.EU
----------
Or, if it is a Bulletin, it may look something like this:
|
+-----+------- (S)end a (B)ulletin
| +-- addressed (TO) anyone interested
| | to (AMSAT) informations
| | +- distribute to the geographic
| | | location (Lazio region)
-+ --+-- +---
example 2: SB AMSAT @ ILAZ
----------
In example 1 the message being sent is Personal and needs a
specific GEOGRAPHIC HIERARCHICAL address. The hierarchy of the
address is parsed from right to left and identifies the
location of the station to whom the message is addressed. The
format of that address is as follows:
+---- Send Personal +- AF - Africa
| +- NA - NAmerica
-+ +- SA - SAmerica
SP IK1GKJ @ IK1MSL.IPIE.ITA.EU +- AS - Asia
+----- +----- +--- -+- | +- EU - Europe
| | | | +- CONTINENT -+- OC - Oceania
| | | | (see Note 2)
| | | +-- COUNTRY -----+- PRT - Portugal
| | | (see Note 2) +- ESP - Spain
| | +-- REGION +- FRA - France
| | (see Note 1) +- xxx - yyyyyyy
| +-- DESTINATION PBBS CALLSIGN
+---- ADDRESSEE CALLSIGN
NOTE 1:
-------
In our italian system, the administrative part (and also a
manageable area for packet-radio purposes) wich characterizes
a distinct *geographical area* below the *country area* is
called Region (there are 20 Regions wich, in some instances,
identify also a *call area*) and to wich we can (or *must*)
address the forwarding, in a well defined mode, without any
possible ambiguity of *geographic route*. See Annex 1.
The just done considerations make clear that adding another
field to our r-lines between, PBBS callsign and Region, filled
for example with the abbreviation (numberplate) of our
(italian) 'provinces' (in many instances a consistent number
within each region), prefixed with, or without a '#' sign,
besides being useless (unproductive) as per forwarding rule,
could be lead also (in general) to an incorrect messages
routing.
NOTE 2:
-------
The Country and Continental H designators are *ignored* when
the message is in its particular domain. Example: in a msg
wich originates inside Lazio region and addressed to a
station of the same region, the Nation and Continent
designators (.ITA.EU) will be ignored.
Proposal:
---------
The *general* format, wich could be represent almost all
over the world realities follows:
+---- Send Personal
-+
sp call @ pbbs.region.state.country.continent
(a) (a) (b) (c) (d) (e)
(a) = valid callsigns as defined by local communications
autority.
(b) = may be a 'Region', an 'Area routing number', a
'Sub-region';
*or*
any other 'large' Administrative/Postal district
existing *below* the Country, or *below* the
State/Province areas (as defined into the next (c)
note).
This field *MUST* be defined by each Country.
(c) = the names of 'States' or 'Provinces' into wich some
Countries are subdivided. This field is applicable
*ONLY* for such a systems in wich this situation is
foreseen. Classic situations in wich 'State' or
'Province' applies are, for example: USA 'states',
Canada 'provinces', Mexican 'states', Chinese
'provinces', Brasilian 'states', Australian
'provinces'(?) an so on; for all other countries
this field *must* not exist.
At the risk to be repetitious I guess that, while
the reference to the "State" appear be generally
understood, that for "Province", *not yet*, in
particular, in this context, I would stress the
the concept that we refer to the word "Province" as
To be continued in digest: hd_2000_185C
Read previous mail | Read next mail
| |
