{subsection: Machine ClassAds}
+To make it possible for Condor to have network related policy integrated when scheduling submitted jobs, we also need to design the corresponding Machine ClassAds that adequately advertises its network related attributes. There are some repetitions or overlaps between the Machine Ad and Job Ad. For the purpose of completeness, we also list those attributes in this section. The list of Machine ClassAds are demonstrated below:
+
+*: IPProtocol ---- This attribute indicates which IP protocol the machine is using. There are two options for this attribute: "IPv4" and "IPv6". The attribute value is supposed to be string, which is double quoted characters. For instance, IPProtocol="IPv6".
+*: AvailBandwidth ---- This attribute indicates the available bandwidth for the network in which the machine is. The machine can be matched on some specific jobs only if the machine can provide network bandwidth larger than the required value during the job execution. The attribute value is a real number, and the unit for bandwidth is ‘Mbps’. The unit is omitted though. For example: BandWidth = 5.5, simply means that the required bandwidth is 5.5Mbps. In reality, AvailMaxBandwidth and AvailMinScheddBandwidth are used.
+*: NetworkAccounting ---- This attribute indicates whether the machine can provide network accounting functionality. The value could be TRUE or FALSE. For example: NetworkAccounting = TRUE. In real scenarios, attributes NetworkLoad, NetworkIn, NetworkOut are provided.
+*: VLAN ---- This attribute indicates which VLAN the machine is in. The value of this attribute is string. There should be some predefined VLAN names that are known to the users. For instance, VLAN = "CMS" means that only when the attribute PreferVLAN = "CMS", the machines can be matched to run the user job.
+*: Latency ---- This attribute indicates the network latency the where the machine is in. The attribute should be a real number with unit as ‘second’. For instance: Latency = 0.05, means the preferred latency is less than 50ms. The machine can be matched to the job that requires latency larger than this value.
+
{subsection: Network Related Policy}
+
+In this section, we talk about the network related policy for Condor. More accurately, we demonstrate the designed policies corresponding to the user case examples mentioned above in details.
+
+The following three policies match the user case examples respectively:
+
+
+*: Since the incoming job only has requirement on the bandwidth, the policy here is kind of simple. As long as the machine has a larger bandwidth than the user request, it can be matched to the submitted job.
+*: The machine can be matched to the job if it supports IPv6 and is in the same VLAN the user requests. If the machined is matched to the job, the attribute value of InboundConnectivity and OutboundConnectivity will be used to setup the network. (In this example, bridge is preferred.)
+*: The machine can be matched to the job if it has a larger bandwidth than the job requires. Also, since the job asks for network accounting, the machine running the job would invoke the network accounting module in the corresponding daemons of Condor and report the network load, incoming traffic and outgoing traffic information.
