Description of problem:

When a valid  shorthand notation of ipv6 address (Ex:-'2003::1') is specified as value to volume set option auth.allow/reject, nfs.rpc-auth-allow/reject , the operation is unsuccessful and reports the ipv6 address as invalid. 

[04/06/12 - 17:42:23 root@APP-SERVER1 ~]# gluster volume set dstore auth.allow 2003::1
option auth.addr./export1/dstore1.allow 2003::1: '2003::1' is not a valid internet-address-list
Set volume unsuccessful

Note:-
---------
The volume set operation is successful when we specify full notation of ipv6 address or ipv6 address with wild characters.

[04/06/12 - 17:56:09 root@APP-SERVER1 ~]# gluster volume set dstore auth.allow 2003:1:1:1:1:1:1:1
Set volume successful

[04/06/12 - 17:58:24 root@APP-SERVER1 ~]# gluster volume set dstore auth.allow 2003:*
Set volume successful

[04/06/12 - 18:23:12 root@APP-SERVER1 ~]# gluster volume set dstore auth.allow 0:*:*:0:007F:0:0001:*
Set volume successful


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

How reproducible:
often

Steps to Reproduce:
1.Create a distribute-replicate volume. 
2.volume set <volume-name> auth.allow <shorthand_notation_of_ipv6_address>

Actual results:
[04/06/12 - 17:49:51 root@APP-SERVER1 ~]# gluster volume set dstore auth.allow 2003::1
option auth.addr./export1/dstore1.allow 2003::1: '2003::1' is not a valid internet-address-list
Set volume unsuccessful

Additional info:-
------------------
The same also happens with "peer probe  <shorthand_notation_of_ipv6_address>"

[04/06/12 - 17:52:12 root@APP-SERVER1 ~]# gluster peer probe 2003::1
Usage: peer probe <HOSTNAME>