ASTN Layer Network Architecture

[Maarten Vissers <mvissers@lucent.com>]

All,

The automatic switched transport network is a multi-layer network. The
architectural aspects of this multi layer nature for ASTN are to be
understood when developing the ASTN specifications (in ITU-T as well as
IETF and OIF). I have tried to address (some of) those aspects in the
following correspondence document:

http://ties.itu.int/u/tsg15/sg15/wp3/q12/0106/cd-astn-ln01.doc
http://ties.itu.int/u/tsg15/sg15/wp3/q12/0106/cd-astn-ln01.pdf

If you do not have access to the ITU-T TIES ftp area, you can download
your copy from: 
ftp://ftp.t1.org/T1X1/X1.5/1X151230.doc (for the moment still at
ftp://ftp.t1.org/pub/upload/1x151230.doc)
ftp://ftp.t1.org/T1X1/X1.5/1X151230.pdf



-----------------

Abstract
========
Today's switched transport networks (i.e. voice, ATM, IP) are single
layer networks. The future switched optical network however is a
multi-layer network, posing additional requirements on its control plane
compared to the control plane of single layer switched networks.

This document introduces these multi layer aspects, the associated
relationships between the layer networks, the set of layer networks
within the switched optical network and its signals, the architecture of
each layer network, its components (fabrics, ports and links),
associated port management aspects, the need for common terminology with
connection management by the management plane, and more…

The concepts of a semi automatic switched transport network (SASTN) and
a fully automatic switched transport network (FASTN) are defined.
Examples of connection creation in a multi-layer transport network are
presented for illustration of the principles.

This document doesn't describe the control plane functionality or
protocols, it presents the transport network architecture the control
plane has to operate. Current control plane specifications (G.dcm,
G.ndisc, G.sdisc and GMPLS) can be evaluated and where necessary adapted
as a result; i.e. the control plane must fit the transport plane, not
the other way around…

The document shows that there can be either one control plane with
multiple instances (one per layer network) of the traffic engineering
and network engineering processes, or multiple control planes (one per
layer network) each with a traffic engineering and network engineering
process which are derived from a generic traffic engineering process and
network engineering process. I.e. one or multiple control planes is
about semantics only.

The document briefly addresses the implications of the multi layer
network for the "overlay" and "peering" relationships and the UNI, I-NNI
and E-NNI.

This document presents "work in progress"; updates will be created based
on additional knowledge gained and  feedback received. The objective is
to create text proposals for the ASTN/ASON series of recommendations for
the upcoming June 2001 Q.12/15 and Q.14/15 meeting.

-----------------

Please email me your comment, enhancements, extensions, ...

Regards,

Maarten
begin:vcard 
n:Vissers;Maarten
tel;cell:+31 62 061 3945
tel;fax:+31 35 687 5976
tel;home:+31 35 526 5463
tel;work:+31 35 687 4270
x-mozilla-html:FALSE
org:Lucent Technologies Nederland;NA&CPSE
version:2.1
email;internet:mvissers@lucent.com
adr;quoted-printable:;;Botterstraat 45=0D=0A=0D=0A;1271 XL Huizen;;;The Netherlands
fn:Maarten Vissers
end:vcard