idrp-ps-att on Export Tests


Local Route Generation


The local route generation has three variables: 
generate from static, import,  export.

Each has a place to filter. What happens if the route: 
  1. route generated form static, not imported, export allowed
  2. reconfig with static, import, and no export
  3. reconfig with static, import, and export

idrp-ps-att in export statement


The export statement be modified via the idrp-ps-att clause
policy can occur on the import statement.  This allows a user
to change idrp path policy for specific routes, and then run
export policy on a combine set of routes.   

idrp_atts_clause



	export proto idrp rdi 0x490130   
	idrp-ps-att
	{
	(policy-statments)
	}
	{
	route export clauses
	}

Example on export

	export proto idrp rdi 0x490130   
	idrp-ps-att
	{
	(policy-statments)
	}
	{
	proto idrp rdi 0x490129;
		{
		all;
		}
	}



Policy statements for idrp-ps-att


 idrp_ps_route_option group 

	routeserver yes/no;
	ext-info null/restrict 
	hierarch_rec null/restrict
	multiexit null/restrict/ / value



 idrp_ps_pref_calc group 


	hopcount_offset (idrp_preference)


 idrp_ps_dist_option 


	prohibit-dist {rdi1 rdi2 ... rdin }
	allow-dist { rdi1 rdi2 .. rdin }


 idrp_ps_QOS_option 


	delay value
	rdle value
	expense value
	priority value
	capacity value

 For version 2.0 only the capacity portion is valid    

   

Tests


For each of the attributes above add the condition to
the attribute, and then transmit it out.   

Export all Based on a match condition, add a the routes to the node. Export all routes.
Export only some routes with this addition Based on a match condition add a the routes to the node. Export other routes without any additional path policy added.
Export two different types of outbound policy Based on a match condition, add a the routes to the node. Export only routes with this function routes.

Do this for internal and external peers.