Re: [mpls] [MPLS] A doubt about RFC 6428

[David Allan I <[e-mail]>]

Hi Alan:

It is kind of implied, as in "received DOWN while NOT in a misconnectivity state". I'm not sure adding that to the state machine diagram would actually improve the clarity....I'll let others comment.

cheers
Dave

________________________________
From: [e-mail] [mailto:[e-mail]] On Behalf Of Alan Davey
Sent: Friday, May 03, 2013 9:29 AM
To: [e-mail]
Cc: [e-mail]
Subject: [mpls] [MPLS] A doubt about RFC 6428

Folks

I have a doubt about RFC 6428.  Could you please let me know what you think of the following.

Section 3.7.4.2., Exit from a Mis-Connectivity Defect, states that "Exit from a mis-connectivity defect state occurs when no CV messages with mis-connectivity defects have been received for a period of 3.5 seconds".

However, the State Machines in section 3.7.5 have no input corresponding to an "Exit from a Mis-Connectivity Defect" timer pop.  (Although they do have a MIS-CONNECTIVITY input added by RFC 6428.)  If the State Machine is followed then Down state is exited as soon as the remote system signals Down state.

Should the State Machines be modified such that Down state following a MIS-CONNECTIVITY input is only exited after an "Exit from a Mis-Connectivity Defect" timer pop input or am I missing something?

Regards
Alan Davey

Network Technologies
Metaswitch Networks

[e-mail]<mailto:[e-mail]>
[phone]
network-technologies.metaswitch.com<http://network-technologies.metaswitch.com/>