|
Hi Woj, All explanations sound
reasonable, but we are talking about an AN implementation and not an ANCP
protocol issue. ANCP has to report the
port status. That’s the basic task of ANCP per definition. Let me distinguish between
two scenarios: Scenario
1 Regular operation: If line is up but line
rate changes happen then option a) “Send a new
Port-up with Rate Y” is preferable. Scenario
2 Fault condition: If a port is toggling the
AN has to integrate a certain period of time the port status and to decide then
if the port is up or down. So the port has to send a
port down message following the periodically change between port up/down status.
The period is determined by timer value to be set by configuration. So this happens in option
b) “Send a Port-down followed by a Port-Up with rate Y”. Result: Sending a port down
message followed by a port up message is necessary during resynchronisation in
case of fault condition. IMO this is an implementation issue of an AN. ANCP has
to be prepared to support both scenarios! Regards Thomas Von: Philippe
Champagne (pchamp) [mailto:pchamp at cisco.com] Hi Woj I agree with (a) otherwise it implies
twice as many messages There is that
part in section 5.4.2: The message SHOULD be generated when
a line first comes UP, or any of the So, it sounds like it is covering that. Is
that what you were referring to but to be worded more
specifically? Or perhaps you missed this text or I'm the one off
track? Regards Phil
|
_______________________________________________ ANCP mailing list ANCP at ietf.org http://www.ietf.org/mailman/listinfo/ancp