TRIP: Recent Changes and Open Issues

1
TRIP Recent Changes and Open Issues

• Jonathan Rosenberg, Hussein Salama, Matt Squire
• Pittsburgh IETF
• August 3, 2000

2
Next Hop Server Format

• Host domain name or IP address in DNS format
  Server host port (RFC 1123)
• proxy.ietf.org
• 172.21.127.671725
• Open Issue UDP/ TCP
• proxy.ietf.orgtransporttcp
• Open Issue IPv6

3
Capabilities

• Current capabilities Route Types Supported and
  Send Receive Capability
• IANA considerations
• Reserved capability code 0
• Capability codes 32768 to 65535 for
  vendor-specific capabilities
• Open Issue making Route Types Supported
  mandatory
• Open Issue adding Capability Mismatch error code

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.

5
Attribute Type Codes

• Assigned type codes to all attributes
• IANA considerations
• Reserved type codes 224 to 255

6
Application Protocols

• Added two new application protocols RAS and Annex
  G.
• IANA considerations

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
ITAD Numbers

• Reserved ITAD numbers 0 and 65535
• ITAD numbers 64512 to 65534 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

9
MED and Tie Breaking Rules

• MED usage consistent. Higher MED is preferable
• Changed tie breaking rules to favor internal
  routes over external routes

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

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?

12
UPDATE Rate Limiting

• Recommendation Follow the same rules as in ISIS

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

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?

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
16
ITAD Boundaries
LS2
GW1
LS1
I-TRIP
TRIP-Lite
I-TRIP
TRIP-Lite
LS3
GW2
TRIP-Lite
I-TRIP
ITAD A
ITAD B
GW3
Aggregation