TRIP: Recent Changes and Open Issues Jonathan Rosenberg, Hussein Salama, Matt Squire Pittsburgh IETF August 3, 2000

8/3/00TRIP: Recent Changes and Open Issues 2 Next Hop Server Format –Host domain name or IP address in DNS format Server = host [ : port ] (RFC 1123) proxy.ietf.org :1725 –Open Issue: UDP/ TCP proxy.ietf.org;transport=tcp –Open Issue: IPv6

8/3/00TRIP: Recent Changes and Open Issues 3 Capabilities –Current capabilities: Route Types Supported and Send Receive Capability –IANA considerations –Reserved capability code 0 –Capability codes to for vendor-specific capabilities –Open Issue: making Route Types Supported mandatory –Open Issue: adding Capability Mismatch error code

8/3/00TRIP: Recent Changes and Open Issues 4 Communities Membership Capability –Permits an LS to announce to its peer the communities it is interested in. –The peer then only advertises to the LS routes of these communities.

8/3/00TRIP: Recent Changes and Open Issues 5 Attribute Type Codes –Assigned type codes to all attributes –IANA considerations –Reserved type codes 224 to 255

8/3/00TRIP: Recent Changes and Open Issues 6 Application Protocols –Added two new application protocols RAS and Annex G. –IANA considerations

8/3/00TRIP: Recent Changes and Open Issues 7 Address Families –Had to deviate from IANAs standard set of address families –POTS Numbers: private, local, national, and international Alphabet = [0-9] –Routing Numbers: mainly for European LNP Alphabet = [0-9,A-F] –IANA considerations

8/3/00TRIP: Recent Changes and Open Issues 8 ITAD Numbers –Reserved ITAD numbers 0 and –ITAD numbers to are for private use –IANA considerations –Proposal: use domain names instead of ITAD numbers Issues: –No need for IANA registration –ITAD topology restrictions –Effect on AdvertisementPath and RoutedPath attributes

8/3/00TRIP: Recent Changes and Open Issues 9 MED and Tie Breaking Rules –MED usage consistent. Higher MED is preferable –Changed tie breaking rules to favor internal routes over external routes

8/3/00TRIP: Recent Changes and Open Issues 10 Security Considerations –Protection of peer sessions using IPSec Transparent mode security association Either AH or ESP Use IKE for key exchange RSA signatures and RSA public key encryption

8/3/00TRIP: Recent Changes and Open Issues 11 Security Considerations –Sign a selected set of attributes, always including ReachableRoutes –Include list of signatures in Authentication attribute –Open Issue: What signature mechanisms to use?

8/3/00TRIP: Recent Changes and Open Issues 12 UPDATE Rate Limiting –Recommendation: Follow the same rules as in ISIS

8/3/00TRIP: Recent Changes and Open Issues 13 Application Protocol Manipulation - Example: an LS receives receives a route with application protocol SIP, changes it to Q.931, and advertises the route to an external peer. - Example: an LS receives a SIP route and advertises two routes to its external peer, a SIP route and a Q.931 route - Advantage: provides for more flexible routing, but - Requires manipulating the ReachableRoutes attribute (previously Aggregation was the only possible manipulation of ReachableRoutes

8/3/00TRIP: Recent Changes and Open Issues 14 Multiple TRIP IDs per LS –An LS MUST use the same TRIP ID with all internal peers. –Question: whats the significance of TRIP ID between external peers?

8/3/00TRIP: Recent Changes and Open Issues 15 ITAD Boundaries –On the link between two LSs –On the LS itself. Splits the LS box into two (or more Virtual LSs. Permits route summarization of TRIP-Lite routes. LS2

8/3/00TRIP: Recent Changes and Open Issues 16 ITAD Boundaries VVV GW1 GW2 GW3 TRIP-Lite LS1 LS3 Aggregation LS2 I-TRIP ITAD A ITAD B