Description of problem:

Submitting per customer request. This could really be defined as a bug or an RFE depending on your perspective on this. 

Unable to add ipsets with brackets per ipv6 RFC, using syntax such as[::2]

Version-Release number of selected component (if applicable):

Any version of RHEL 7 and 8 I was unable to add with brackets. Customer stated they were able to get it to work but did not specify a specific RHEL or Fedora release I was unable to get ipset addition with brackets to work on RHEL 7.7 or 8.1 

How reproducible:

Just about always in my experience. Customer states it works in some cases


Steps to Reproduce:
1. firewall-cmd --permanent --new-ipset=test --type=hash:net --option=family=inet6
2. firewall-cmd --permanent --ipset=test --add-entry=[::2] OR ipset add test [::2]
3.

Actual results:

(in my testing) 

[root@localhost ~]# firewall-cmd --permanent --ipset=test --add-entry=[::1]
Error: INVALID_ENTRY: invalid address '[::1]' in '[::1]' for hash:net (ipv6)


Expected results: success code such as:

[root@localhost ~]# firewall-cmd --permanent --ipset=test --add-entry=::1
success


Additional info:
 
Customer's reasoning is that per RFCs about ipv6 syntax use brackets and this implies that using brackets in ipv6 syntax is a standard that firewalld should adhere to.. I was not provided a specific RFC source from the customer but I found something that seemed vaugely relevant but not directly  https://tools.ietf.org/rfc/rfc2732.txt