Add compliance exceptions for server renegotiation (#3498)

Author: lrstewart

compliance/specs/exceptions/rfc5746/4.6.toml renamed to compliance/specs/exceptions/rfc5746/3.6.toml

@@ -0,0 +1,48 @@
+target = "https://tools.ietf.org/rfc/rfc5746#3.7"
+
+[[exception]]
+quote = '''
+o  When a ClientHello is received, the server MUST verify that it
+does not contain the TLS_EMPTY_RENEGOTIATION_INFO_SCSV SCSV.
+'''
+reason = '''
+s2n-tls servers do not support renegotiation.
+'''
+
+[[exception]]
+quote = '''
+If the SCSV is present, the server MUST abort the handshake.
+'''
+reason = '''
+s2n-tls servers do not support renegotiation.
+'''
+
+[[exception]]
+quote = '''
+o  The server MUST verify that the "renegotiation_info" extension is
+present; if it is not, the server MUST abort the handshake.
+'''
+reason = '''
+s2n-tls servers do not support renegotiation.
+'''
+
+[[exception]]
+quote = '''
+o  The server MUST verify that the value of the
+"renegotiated_connection" field is equal to the saved
+client_verify_data value; if it is not, the server MUST abort the
+handshake.
+'''
+reason = '''
+s2n-tls servers do not support renegotiation.
+'''
+
+[[exception]]
+quote = '''
+o  The server MUST include a "renegotiation_info" extension
+containing the saved client_verify_data and server_verify_data in
+the ServerHello.
+'''
+reason = '''
+s2n-tls servers do not support renegotiation.
+'''