iRule restriction for configuration using route domain and partitioning features

hi All,

I have a questions about iRule and its restriction that need be followed when you write a code that used ip%1 expressions, data groups, and where some objects may be defined on different partitions on LTM. 

Let is only an example of code:


rule myTest {

when HTTP_REQUEST {
set myc1 [class lookup [HTTP::host] myclass1]

if {$myc1 != "" } {
regsub -nocase {(.*)\%[0-9]} [IP::client_addr] {\1} clientip
log local0.info "Checking IP bybass for [HTTP::host] with [IP::client_addr] $clientip in $myc1 ****"

if { [class match $clientip contains $myc1 ] } {
log local0.info "[IP::client_addr] Not allowed Access to [HTTP::host] because not in $myc1 *****"
}
}

}
}

class myclass1 {
{
"www.google.com" { "bypass_google" }
"blabla.co.uk" { "bypass_bla" }
}
}

class bypass_google {
{
network 10.0.0.0%2/8
host 1.1.1.1%2
network 192.168.0.0%2/16
}
}


Q: can the class object exist in different partitions than the irule?
Q: is this kind of expression fully supported?
if { [class match $clientip contains $myc1 ] } {
I found that on v10.2 Final it is not working but is working on v10.2 HF2. Is there some CR I'm missing?
Q: does the route domain is supported and can be used like in the example above?
Q: where the route domain must be defined? Does it has to be in the 'common' partition?