1. 1 BGP ACCEPT_OWN Well-known Community Attribute L3VPN WG – Dublin July 2008 James Uttaro AT&T Labs Pradosh Mohapatra David J. Smith Cisco Systems, Inc. Robert Raszuk John Scudder Juniper Networks, Inc.

2. 2 Current L3 VPN deployments MGMT Extranet provisioning:

3. 3 Current L3 VPN deployments Example: 100s PEs.. Assume all have at least one site which requires to participate in the extranet MGMT

4. 4 Current L3 VPN deployments Configuration based provisioning works well for static configuration.. Does not work well for dynamic configs Great deal of configuration overhead for providing granular stitching at a large set of PEs Some extranets may be on demand.. Triggered by customer dynamic request Provisioning time becomes an issue Multivendor environments do not make things easier to provision... What is the alternative ?

5. 5 New L3 VPN operational model Answer: To instruct RR to make an extranet ! MGMT Answer: Are we done then ?

6. 6 New L3 VPN operational model Answer: NO.... All works except the original PEs. Modified routes will be dropped as those routes were originally src-ed by those PEs MGMT We need to mark those modified routes for the PEs to recognize them for special handling and accept.

7. 7 ACCEPT_OWN bgp community This draft proposes a very simple marking of those reflected routes for special handling by originator PEs We propose to define an ACCEPT_OWN BGP Community Route may be accepted at the originator when: Processing of the ACCEPT_OWN community is enabled by configuration. The route in question carries the ACCEPT_OWN community. The route in question was originated from a source VRF on the router (as determined by inspecting the Route Distinguisher) The route in question is targeted to one or more destination VRFs on the router (as determined by inspecting the Route Target(s)). At least one destination VRF is different from the source VRF.

8. 8 ACCEPT_OWN bgp community A route MUST never be accepted back into its source VRF, even if it carries one or more Route Targets (RTs) which match that VRF. ACCEPT_OWN community can only be attached to those address families which are utilizing concept of independent routing and forwarding contexts (for example VRFs) ACCEPT_OWN community is local to an AS and is design to work with single layer of route reflectors. Routers that do not understand ACCEPT_OWN community operate as per the current behavior. Authors propose (pending IANA approval) that the value of ACCEPT_OWN standard BGP community be 0xFFFFFF05. Questions... Comments... Input... Shall we move to the list... Ask for WG interest in this work...