[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: ASON reqts



Hi Deborah,

Regarding the requirements, it sounds to me as if the scope
of ccamp efforts is somewhat different from the scope of
the sg15 effort, so the result of discussion may be also
different.  I would hope that we can make an extra effort
to avoid diverging.

Cheers,

Lyndon

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


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