On Mon, 17 Mar 2014 11:31:23 +0800 Wei-Li Tang <[email protected]> wrote:
> Openflow 1.1 and later versions allow the use of IP address with > arbitrary bitmask in match fields. This enables related fields > to be interpreted in the following order: > > 1. Standard CIDR: > > 192.168.1.0/24 > fe80::/10 > > 2. Hybrid CIDR format (IP address with dotted decimal or > colon-hexadecimal mask): > > 192.168.1.0/255.255.255.0 > fe80::/ffc0:: > > 3. ACL hybrid CIDR format (Cisco-like ACL bitmask): > > 192.168.1.0/0.0.0.255 (equivalent to 192.168.1.0/24) > fe80::/3f:ffff:ffff:ffff:ffff:ffff:ffff:ffff (equivalent to fe80::/10) > > 4. IP address with arbitrary bitmask: > > 192.168.1.0/0.255.0.255 > fe80::dead:beaf/ffff:0000:ffff:ffff:ffff:ffff:ffff:ffff > > Please note that a bitmask with only continuous '1' bits starting from > LSB (e.g. 0.0.0.255) will be considered an ACL hybrid CIDR hostmask, > not an arbitrary bitmask. > > You can explicitly specify arbitrary bitmask in separate fields as below: > > nw_src_w, nw_dst_w, ipv4_src_w, ipv4_dst_w, > arp_spa_w, arp_tpa_w, ipv6_src_w, ipv6_dst_w. Thanks a lot for the updated patch. But why we need new fields? The existing fields can be extended to handle an arbitrary mask? I think that that's the discussion point. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
