Mods to ripe181?

Tony,

Please take a look at the example I provided below. That is a real policy of
three major providers.  I tried to regist their policy but could not do it.
If you have a suggestion of how to use 181 to express that.  That will be
a big big help.

						--Jessica


------- Forwarded Message

Return-Path: tony at mci.net
Received: from merit.edu (merit.edu [35.1.1.42]) by home.merit.edu (8.6.9/merit-2.0) with ESMTP id RAA01804 for <jyy at home.merit.edu>; Fri, 3 Feb 1995 17:43:06 -0500
Received: from lovefm.reston.mci.net (lovefm.Reston.mci.net [204.70.128.44]) by merit.edu (8.6.9/merit-2.0) with ESMTP id RAA28258 for <jyy at merit.edu>; Fri, 3 Feb 1995 17:43:05 -0500
Received: from localhost (loopback.mci.net [127.0.0.1]) by lovefm.reston.mci.net (8.6.9/8.6.6) with ESMTP id RAA20505; Fri, 3 Feb 1995 17:42:33 -0500
Message-Id: <199502032242.RAA20505 at lovefm.reston.mci.net>
To: Enke Chen <enke at mci.net>
cc: Jessica Yu <jyy at merit.edu>, rr-impl at ripe.net
Subject: Re: Mods to ripe181? 
In-reply-to: Your message of Fri, 03 Feb 1995 16:15:52 EST.
             <199502032115.QAA04725 at ns.mci.net> 
From: Tony Bates <Tony.Bates at mci.net>
X-Phone: +1 703 715 7521
Date: Fri, 03 Feb 1995 17:42:32 -0500
Sender: tony at mci.net

Here are re-visiting an old discussion. I personally am not in
agreement with Enke on this one so this is not necessarily the whole
view of MCI.
		--Tony.

 Enke Chen <enke at mci.net> writes:
  * I agree with Jessica on the need of AS path in the as policy. 
  * The reality is that AS paths are widely used today in AS policies 
  * today.  Here is a very simple example, currently MCInet does 
  * not re-distribute to other NSPs the routes learned from a NSP.
  * This policy is very difficult (if not impossible) to describe 
  * without AS path. 
  * 
  * -- Enke    
  * 
  * 
  * > Date:    Fri, 03 Feb 1995 15:02:30 -0500
  * > From:    Jessica Yu <jyy at merit.edu>
  * > To:      rr-impl at ripe.net
  * > CC:      jyy at merit.edu
  * 
  * > This issue may come up before but never got addressed.  Now we have real 
  * probl
  * em
  * > to describe three major providers policies who I gather routing policies 
  * from.
  * > 
  * > I think we really need to seriously address this.  Below is an example to
  * > illustrate the problem and a suggestion to the solution.  
  * > 
  * > 
  * >                            ASh
  * >                            |
  * >                      ASi...ASj-------|
  * >                       \  | /         |
  * >                         130          |
  * >                          |          /
  * >                  ----------------- /
  * >                   |       |    |  /
  * >                  50      60    70 
  * >                 / \      / \    \
  * >               ASm...ASn ASx..ASy ASz
  * >                |
  * >               ASa
  * > 
  * > The Policy:
  * > 
  * > AS130 announce to AS50 everything but not any routes whose AS path starts
  *  with
  * > AS50,AS60 and AS70.
  * > 
  * > The difficulties here are 
  * > 
  * > a) AS130 wants to announce ASj to AS50 but not with
  * > the pass of 100 ASj.  Since RIPE181 only has homeAS concept in terms of w
  * hat
  * > AS to accept, we have to either describe to reject ASj or advertise ASj n
  * ot
  * > advertise ASj when path is 130 ASj.
  * > 
  * > b) Usually, certain in this real AS's policy case, one does not know expl
  * icitl
  * y
  * > what's behind AS130 i.e. ASi..Asj, ASh.  So it is near to impossible to 
  * > express such policy in ripe181 format.
  * > 
  * > The problem is that RIPE181 deals with home AS only.  To describe this ca
  * se, w
  * e 
  * > need introduce a concept of AS in the path.
  * > 
  * > Suggested mods:
  * > 
  * > Introduce AS in the path concept.  This will solve both problem a) and b)
  * .  To
  *  
  * > express the policy above:
  * > 
  * > as-out: to AS50 announce ANY AND NOT {AS50in_the_path, AS60in_the_path AS
  * 70in_
  * the_path}
  * > 
  * > I suggest to use cisco's regular expression to represent the AS in the pa
  * th
  * > concept.  It is widely used and therefore more people understands it.
  * > 
  * > as-out: to AS50 announce ANY AND NOT {^AS50_ ^AS60_ ^AS70_}
  * > 
  * > ^ means the right most of the ASpath.
  * > _ same as .* 
  * > 
  * > 
  * > 							--Jessica

------- End of Forwarded Message




-------- Logged at  Mon Feb 6 16:35:22 MET 1995  ---------