RE: ason-routing-reqts: issue 1 addressing

[Kireeti Kompella <kireeti@juniper.net>]

Hi Lyndon,

On Tue, 16 Mar 2004, Ong, Lyndon wrote:

> Maybe the issue needs to be worded more clearly...
>
> Can existing address reachability mechanisms support
> (and if so, how)
>
> a) distinguishing between the control plane address
> for a client and the data plane address for a client
> which might be two different things?
>
> b) distinguishing between the internal network address
> space and an external client address space?
>
> c) advertising reachability to a client whose address
> space is non-IP?

All excellent questions.  Thanks for the summary.

I'll go back to my meta-question:

Are these ASON routing requirements?  If so, can you quote chapter and
verse?  The clear charter of the ASON Routing Reqts DT is to take
*existing* ASON routing requirements, evaluate them against what's in
GMPLS routing, and come up with a list of remaining requirements to
set the stage for an ASON Routing Extensions document.  Not to come up
with new requirements, however excellent they may be.

Kireeti.
-------