Automatic Router Configuration Protocol (ARCP) v1.1, 18 Nov Jeb Linton, EarthLink

Linton, IETF 11/022 Overview ARCP uses a Client-Server model like DHCP, rather than a Peer-to-Peer model Routers first become DHCP “Hosts”, then get router configuration through ARCP Configuration messages use an “Option”- based format similar to DHCP Router configuration is set by ARCP Server, not chosen by client

Linton, IETF 11/023 Standard Operation 3. More Clients join in the same way DHCP/ARCP Server (on Home Gateway, NAT Firewall, or PC) Internet 1. ARCP Client Is connected, Obtains DHCP config 2. Client Registers with ARCP Server, Obtains Routing config, acts as DHCP Relay Agent 4. New connections and addressing collisions are detected and arbitrated by the ARCP Server

Linton, IETF 11/024 ? AutoServer Operation 1.An AutoServer-enabled Router is turned on, initially acting as an ARCP client. 3. After a timeout, the first router will begin to act as a DHCP/ARCP Server in response to any client requests ! 4. Further operation is ARCP Standard ARCP AutoServer routers are set to give out basic RFC1918 addresses, passwords, routing protocol data and multicast parameters. AutoServer timeout is greater than the DHCP request period. 2. Other routers may be linked, but there is no Server at first ?

Linton, IETF 11/025 ARCP Messages and Options Two Message Formats, Five Types Total Two-tiered Option structure including Option Type and Option Number Main Option Types:  Router Options  Interface Options  Protocol Options  Vendor-Specific Options

Linton, IETF 11/026 Advantages No arbitration between peers Easy implementation Routing protocol independent High security possible using existing protocols Highly scalable/expandable Compatible with virtually all common routing configurations

Linton, IETF 11/027 Work Areas Next Draft revision will address:  Textual errata (e.g. Sections 7.6 and 7.7)  TLS for Secure operation instead of IPSec  Option for Multilink Subnet operation?  Issues arising today…? Separate Drafts to address:  Multiserver ops for Redundancy and Scaling  Secure Operations