Re: cleaned up question sheet

[Tom Reddington <treddington@bell-labs.com>]

>
> > > > 2. Horizontal (between two areas or administrative subdivisions within
> > > >     the same network layer):
> > > >
> > > >     (a) What are the criteria that trigger the creation of protocol or
> > > >           administrative boundaries pertaining to restoration? (e.g.,
> > > >           scalability?  multi-vendor interoperability? what are the
> > > >           practical issues?)  multi-provider? Should multi-vendor
> > > >           necessitate hierarchical seperation?
> > > >
> > > >     When such boundaries are defined:
> > > >
> > > >     (b) What are the requirements on how protection/restoration is
> > > >           performed end-to-end across such boundaries?
> > > >
> > > >     (c) If different restoration mechanisms are implemented on two
> > > >           sides of a boundary, what are the requirements on their
> > > >           interaction?

                  (d) What information must be shared across administrative boundaries
for detection and restoration?
                   (e) What information must NOT be shared across administrative
boundaries?

Same questions for vertical

>
> > > >    What is the primary driver of horizontal hierarchy? (select one)
> > > >     - functionality (e.g. metro -v- backbone)
> > > >     - routing scalability
> > > >     - signalling scalability
> > > >     - current network architecture, trying to layer on TE ontop of
> > > >       already hiearchical network architecture
> > > >     - routing and signalling

                 - security?

> > > >
> > > > E. Signaling Mechanisms
> > > >
> > > > 1. What are the requirements on the signaling transport mechanism
> > > >    (e.g., in-band over sonet/sdh overhead bytes, out-of-band over
> > > >    an IP network, etc.) used to communicate restoration protocol
> > > >    messages between network elements. What are the bandwidth and
> > > >    other requirements on the signaling channels?

                security requirements