60 likes | 204 Views
OSPF v2/3 System Name. Danny McPherson danny@tcb.net. Overview. Define mechanism for OSPF routers to learn about symbolic hostnames Much akin to IS-S dynamic hostname exchange mechanism - RFC 2763. Motivators.
E N D
OSPF v2/3 System Name Danny McPherson danny@tcb.net
Overview • Define mechanism for OSPF routers to learn about symbolic hostnames • Much akin to IS-S dynamic hostname exchange mechanism - RFC 2763
Motivators • Current mechanism, DNS, relies on IP connectivity - may not be able to resolve if reachability problems • May want system name different than that in DNS, or new routers not yet in DNS • DNS resolution introduces extra load, could be particularly problematic in times of problem resolution • RI LSA (4970) is standardized, offers convenient place to advertise system name • Move to IPv6 will result in more difficult human parsing of IP addresses
Other Considerations • OSPFv3 contains single 32-bit router-ID, may be an issue as IPv6 is further deployed - out of scope here but likely needs attention • draft-venkata-ospf-dynamic-hostname-01.txttook a stab at definition mechanism in 2003 - using Opaque LSAs, RFC 2763 as base for ID
Actions? • Is there sufficient interest in definiung system name mapping mechanism for OSPF? • If so, define with RI Opaque LSA or other mechanism? • Anything to use from venkata draft? • What about 32-bit router ID for OSPF v3?