BGP attributes and traffic flow passes transit AS

From: forwardtruth@yahoo.com
Date: Sun Jul 02 2006 - 14:56:13 ART

As a general rule, these attributes should be applied in the following manner to
affect the following traffic flow :
(( Weight and Local-Preference are used to affect how traffic leaves the
autonomous system. AS-Path and MED are used to affect how traffic enters the
AS. Since Weight and Local-Preference are higher in the decision process than
AS-Path and MED, you (generally) have control of how traffic leaves your AS )).

Does the same rule applied to a traffic that passes transit AS in the following scenarios :

Lab 2 V3 Task 5.4
"Parts of the acquisition agreement between AS400 and AS 100 stipulates that AS 400 will not provide transit for traffic coming from AS 54 and its customers that is destined for AS 254. Configure AS 400 to reflect this policy".

Lab 4 V3 Task 6.2
"AS 100s corporate policy dictates that it should not provide transit service to get to any of ASs 54s customers. However, AS100 should still be able to reach the prefixes of AS 54s customers,,,,,,etc".

Now my query if I want to control traffics that originate in AS54 towards AS 100 (destination) via AS 400 (transit AS) , do I need to control the AS 54s traffics, when it enters AS 400 (Traffic flow affected inbound) or when It leaves AS 400 (Traffic flow affected outbound) towards AS 100 (destination) ??

This archive was generated by hypermail 2.1.4 : Tue Aug 01 2006 - 07:13:46 ART