(started a tad late...) Matvey's preso - some interest in the work still, moving forward BGP Graceful Shutdown - Pierre Francois (UCL-be) - Loss of ... during planned maintenance slow nextpath selection during convergence, leads to loss of packets during planned maintenances. leads to longer maintenances, longer outages when predictable events occur (maintenances) - graceful-shutdown dealing with outbound traffic from an AS under maint, reconfig/re-pref announcements to not prefer this path routes are maintained on the affected device though convergences starts across the AS and traffic shifts to other exits. shutdown of session occurs when all traffic is migrated away - graceful-shutdown dealing with inbound traffic from an AS use a well-known community (GSHUT) to signal this actiivty outside ASN's will be preconfigured for dealing with GSHUT take the right actions and move traffic away from the affected interconnects one-well-known is better than provider-by-provider communities less complications, simpler global configurations - deployment is incremental, new bgp speakers configured as necessary to understand this new policy and community - next-steps comments included understanding if LocalPref is already being overridden what is the transitivity of the new community need more feedback should a submit -01 go forward? Routing System Stability - Dimitri ... - Problem statement - Describe, document and measure stability of the Routing table as a whole. - oh gosh... math... (describing the proper efforts to find stability metrics) - graphs showing the math in action with real preifxes from RIS data - next steps work for how features exacerbate or damp the current stability moving forward using RIS data for this analysis (short call to stay longer than the cutoff, overly packed schedule most answers 'no') LISP Deployment Status - Dave Meyer - Initial observations Much different from current overlay examples - LISP control plane and LISP operations examples skipped past quickly - LISP-ALT == 'just like BGP only in a VRF' prefixes of endpoint-ids only runs over GRE mostly can run over .1q or native as well (think direct connect ethernet ... why use GRE?) - ALT discussion/walk-through ALT is only for map-requests to/from ETR ALT is NOT used for actual traffic - ALT can be colocated with ETR's, or in Provider-Space (ALT mapping and LISP traffic explanation) rbonica - L3vpn -> LISP compare/contrast? yakov - how can you determine ALT vs normal-routing? - deployment info about boxes doing LISP today equipment: titaniums, IOS-alike, OpenLISP (see luigi @ ucl.be) Addressing for EIDs: geographic aggragation ALT-Aggragators - hub/spoke deployment by regions GRE tunnels run the mesh, no requirement for GRE pointers to draft-lewis-lisp-interworking-01.txt http://www.lisp[46].net - EID prefixes in notes/slides - network diagrams and discussion of address allocations - config examples for ITR/ETR both BGP and BGP-free - possiblities to do v4 and v6 at a site without provider support for v6 (or v4) using LISP - LISP Translate discussion + PTR configuration and packet walk through - stress on 'this is all working today in a live network'... GROW ends