RE: ASON reqts

["Brungard, Deborah A, ALABS" <dbrungard@att.com>]

Thanks Lyndon for asking clarification-

I was trying to say that ASON does not require supporting multiple address formats for a E-PC (Protocol Controller) e.g. G7713.1.

Similar to NSAP support of IP, IPv6 supports NSAP.

Can you clarify your take on the requirements discussion? If I read the email, the discussion was related to the definition of a control domain and support of a non-RSVP domain or legacy (management system). The answer for supporting a non-RSVP domain was the need for an interworking function (which was considered out of scope). This is analogous to ITU's work, both for G7713.1 (PNNI) and G7713.2, the interworking functions are considered out of scope. And support of legacy is via SPC (same as G7713.1) and it is included. Were any other requirements identified as missing?

Deborah

-----Original Message-----
From: Ong, Lyndon [mailto:LyOng@Ciena.com]
Sent: Wednesday, May 14, 2003 1:09 PM
To: Brungard, Deborah A, ALABS; Stephen Trowbridge
Cc: Wijnen, Bert (Bert); Bart.Rousseau@alcatel.be; ccamp@ops.ietf.org
Subject: RE: ASON reqts


Hi Deborah,

Just wanted to clear up a point - 7713.1 supports NSAP format
addresses, however there are methods of mapping IPv4 and IPv6
addresses into the NSAP format, so there is no fundamental
limitation in this (also, I believe the ATMF has or is working
on a document on address format mapping).

I think the discussion seems to be pointing out that some
ASON requirements just don't fall within the scope of IETF
work, so it may not be appropriate to address them in IETF
(hmm, sounds like how 3474 was created...)

Cheers,

Lyndon