Networking.RouteDomain.wsdl in f5-icontrol-0.2.0

- old
+ new

@@ -1,8 +1,8 @@
 <?xml version="1.0" ?>
 <!--
-Copyright (c) 1996-2013, F5 Networks, Inc., Seattle, Washington. All rights reserved.  
+Copyright (c) 1996-2016, F5 Networks, Inc., Seattle, Washington. All rights reserved.  
 
 F5, F5 Networks, the F5 logo, BIG-IP, 3-DNS, iControl, GLOBAL-SITE, SEE-IT, EDGE-FX, FireGuard, Internet Control Architecture, IP Application Switch, iRules, PACKET VELOCITY, SYN Check, CONTROL YOUR WORLD, OneConnect, ZoneRunner, uRoam, FirePass, and TrafficShield are registered trademarks or trademarks of F5 Networks, Inc., in the U.S. and certain other countries. 
 
 All other trademarks mentioned in this document are the property of their respective owners. F5 Networks' trademarks may not be used in connection with any product or service except as permitted in writing by F5.
 
@@ -241,13 +241,11 @@
 
  NOTES
  = If set, packets cannot cross route domain boundaries, i.e., they
    are strictly isolated to the current route domain.
  = For example, if not set, you can add a route to the routing table
-   where the destination is 10.0.0.0%20 (route domain 20) and the
-   gateway is 172.27.84.29%32 (route domain 32).
- = If set, the system may find invalid iRules that passed
+   where the destination is 10.0.0.0   gateway is 172.27.84.29 = If set, the system may find invalid iRules that passed
    validation.
 
         	</documentation>
 		<input message="tns:Networking.RouteDomain.set_strict_stateRequest"/>
 		<output message="tns:Networking.RouteDomain.set_strict_stateResponse"/>
@@ -474,13 +472,11 @@
 
  NOTES
  = If set, packets cannot cross route domain boundaries, i.e., they
    are strictly isolated to the current route domain.
  = For example, if not set, you can add a route to the routing table
-   where the destination is 10.0.0.0%20 (route domain 20) and the
-   gateway is 172.27.84.29%32 (route domain 32).
- = If set, the system may find invalid iRules that passed
+   where the destination is 10.0.0.0   gateway is 172.27.84.29 = If set, the system may find invalid iRules that passed
    validation.
 
         	</documentation>
 		<soap:operation soapAction="urn:iControl:Networking/RouteDomain"/>
 		<input>
@@ -633,11 +629,10 @@
  domains.  Route domains allow you to specify overlapping IP
  addresses for different objects in the system.  This allows a
  service provider, for example, to have two different pool
  members at 10.10.10.1 that represent completely different real
  servers.  The addresses for the two pool members might be
- 10.10.10.1%1 and 10.10.10.1%2 where the numbers after the
- percent signs are numeric ids of route domains.
+ 10.10.10.1 percent signs are numeric ids of route domains.
 
         	</documentation>
 	<port name="Networking.RouteDomainPort" binding="tns:Networking.RouteDomainBinding">
 		<soap:address location="https://url_to_service"/>
 	</port>