docs: add supported protocol options

Fixes: firewalld/firewalld#991

Author: TorontoMedia

documentation/helper/options.md

@@ -39,4 +39,4 @@ The port string can be a single port number or a port range portid-portid or als
 
     protocol="string"
 
-The protocol value can either be tcp or udp.
+The protocol value can either be tcp, udp, sctp, or dccp.

documentation/service/options.md

@@ -33,7 +33,7 @@ The port string can be a single port number or a port range portid-portid or als
 
     protocol="string"
 
-The protocol value can either be tcp or udp. 
+The protocol value can either be tcp, udp, sctp, or dccp.
 
 For compatibility with older firewalld versions, it is possible to add protocols with the port option where the port is empty. With the addition of native protocol support in the service, this it not needed anymore. These entries will automatically be converted to protocols. With the next modification of the service file, the entries will be listed as protocols. 
 
@@ -55,7 +55,7 @@ The port string can be a single port number or a port range portid-portid.
 
     protocol="string"
 
-The protocol value can either be tcp or udp. 
+The protocol value can either be tcp, udp, sctp, or dccp.
 
 ## module
 

documentation/zone/options.md

@@ -65,9 +65,9 @@ Is an optional empty-element tag and can be used several times to have more than
 
 The port can either be a single port number portid or a port range portid-portid.
 
-    protocol="tcp|udp"
+    protocol="tcp|udp|sctp|dccp"
 
-The protocol can either be tcp or udp.
+The protocol can either be tcp, udp, sctp, or dccp.
 
 ## protocol
 
@@ -105,9 +105,9 @@ The local port and protocol to be forwarded.
 
 The port can either be a single port number portid or a port range portid-portid.
 
-    protocol="tcp|udp"
+    protocol="tcp|udp|sctp|dccp"
 
-The protocol can either be tcp or udp.
+The protocol can either be tcp, udp, sctp, or dccp.
 
 ### Optional attributes:
 
@@ -129,9 +129,9 @@ Is an optional empty-element tag and can be used several times to have more than
 
 The port can either be a single port number portid or a port range portid-portid.
 
-    protocol="tcp|udp"
+    protocol="tcp|udp|sctp|dccp"
 
-The protocol can either be tcp or udp.
+The protocol can either be tcp, udp, sctp, or dccp.
 
 ## rule
 
@@ -144,12 +144,12 @@ The general rule structure:
       [ <destination address="address[/mask]" [invert="True"]/> ]
       [
         <service name="string"/> |
-        <port port="portid[-portid]" protocol="tcp|udp"/> |
+        <port port="portid[-portid]" protocol="tcp|udp|sctp|dccp"/> |
         <protocol value="protocol"/> |
         <icmp-block name="icmptype"/> |
         <masquerade/> |
-        <forward-port port="portid[-portid]" protocol="tcp|udp" [to-port="portid[-portid]"] [to-addr="address"]/> |
-        <source-port port="portid[-portid]" protocol="tcp|udp"/> |
+        <forward-port port="portid[-portid]" protocol="tcp|udp|sctp|dccp" [to-port="portid[-portid]"] [to-addr="address"]/> |
+        <source-port port="portid[-portid]" protocol="tcp|udp|sctp|dccp"/> |
       ]
       [ 
         <log [prefix="prefixtext"] [level="emerg|alert|crit|err|warn|notice|info|debug"]/> [<limit value="rate/duration"/>] </log> |

documentation/zone/parts.md

@@ -11,7 +11,7 @@ A service is a combination of port and/or protocol entries. Optionally netfilter
 
 ### Ports, source ports and protocols
 
-Definition of tcp or udp ports, where ports can be a single port or a port range.
+Definition of tcp, udp, sctp, or dccp ports, where ports can be a single port or a port range.
 
 ### ICMP blocks