1. IDR WG draft-chakrabarti-idr-as4-route-cap-01.txt Samita Chakrabarti, IPInfusion IETF 72, Dublin July 29, 2008

2. Introduction draft-rekhter-as4octet-ext-community-03.txt defines AS4- specific extended communities and RFC 4364 describes AS4-specific RD and SOO This document provides mechanism to allow PE routers to exchange capabilities for handling AS4-specific RD/RT/SOO This is useful in a provider network with large number of PE routers and with Inter-AS provider networks

3. Typical BGP-MPLS-VPN topology PE1PE2ABR1 CE1 CE2 AS4-specific RT format (4b:2b) AS2 specific RT format (2b:4b) Routes will be Rejected here NOTE: Compliance with RFC 4893 is independent Of AS4-specific RT/RD/SOO support

4. New Route-Capability Optional capability with OPEN message Used to negotiate AS4-specific RT/RD/SOO between two PE routers - Can specify whether AS4-specific RT or RD or SOO or all of them are supported - In case of RT, it can specify whether AS4-specific RT is supported for export or import side Advantages - Allows dynamic configuration across PEs - Useful in large deployment or in inter-AS provider network where PE routers may not run same router software

5. New Route-Capability Capability Type (TBD –IANA) Length (2) 0 715 Rsvd DSR RT-Val RSVDRSVD D – on (AS4-specific RD capable), RT-Val =0 S - on (AS4-specific origin capable) RT-val = 0 R - on ( AS4-specific RT capable) RT-val = 1 (able to export As4 format) = 2 (able to import AS4 format) = 3 (able to export/import AS4 format) Rsvd bits are set to 0

6. Comments and next step?