Last Modifield: 07/02/2002
The products of this working group will be used by routing protocol designers to ensure adequate coverage of security in the future, including well known and possible threats.
The scope of work is limited to router-to-router protocols only for both unicast and multicast systems, and does NOT include host-to-router protocol such as IGMP, ICMP, ARP, or ND. It is also a non-goal at this point to produce new or change the current security mechanisms in the existing routing protocols.
The RPSEC working group is charged with the following tasks:
- Document threat models for routing systems
- Document security requirements for routing systems
- Provide a common area for discussion between security and routing experts on the topic of securing the routing system
Possible Future Work
- Evaluate and document existing and proposed routing security mechanisms with respect to established RPSEC requirements
- Recommend mechanism(s)
| JUL 02 | Submit initial I-D (or set of I-Ds) which details the threats to routing systems. | |
| OCT 02 | Submit initial I-D (or set of I-Ds) which outlines security requirements for routing systems. | |
| DEC 02 | Submit I-Ds documenting threats to routing systems for publication as Informational RFC. | |
| MAR 03 | Submit the I-D documenting security requirements to routing systems for publication as Informational RFC. | |
| MAR 03 | Evaluate progress, recharter with new goals (see possible future work above) or shutdown. |