1 files changed, 0 insertions, 23 deletions

diff --git a/draft-summermatter-set-union.xml b/draft-summermatter-set-union.xml
index dcecd87..1a82d3d 100644
--- a/draft-summermatter-set-union.xml
+++ b/draft-summermatter-set-union.xml
@@ -2510,29 +2510,6 @@ FUNCTION END
                     surface as possible and makes it more difficult for the attacker to send the
                     protocol into an endless loop, for example.
                 </t>
-                <t>
-                    The following function is executed every time a message is processed.
-                    The array allowed_state, which contains a list of allowed messages for
-                    the current state of the application.
-                </t>
-                <figure anchor="security_generic_functions_check_valid_state_code">
-                    <artwork name="" type="" align="left" alt=""><![CDATA[
-# Input:
-# as: A array containing all states in which the message can be received
-# s: The state in which the protocol is in
-# Output:
-# Returns TRUE if message is valid in state and FALSE if not
-
-FUNCTION check_valid_state (as, s)
-    FOR (as in as) ## FIXME: WTF? as in as??? Also: overall terrible way to do this -- where would 'as' come from? Also, I do not think this function SHOULD even be in the RFC (technically, all you want to say is 's in as').
-        IF (as == s)
-            RETURN TRUE
-        END IF
-    FOR END
-    RETURN FALSE
-FUNCTION END # FIXME: you did not use FUNCTION END above... Be consistent!
-                    ]]></artwork>
-                </figure>
             </section>
             <section anchor="security_generic_functions_mfc" numbered="true" toc="default">
                 <name>Message Flow Control</name>