1 / 5

KMART BOF

KMART BOF. Key Management for Routing Co-Chairs: Acee Lindem acee@redback.com Donald Eastlake 3rd Donald.Eastlake@motorola.com. Note Well !.

rian
Download Presentation

KMART BOF

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. KMART BOF Key Management for Routing Co-Chairs: Acee Lindem acee@redback.com Donald Eastlake 3rd Donald.Eastlake@motorola.com IETF KMART BoF

  2. Note Well ! • Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: • the IETF plenary session, • any IETF working group or portion thereof, • the IESG, or any member thereof on behalf of the IESG, • the IAB or any member thereof on behalf of the IAB, • any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, • the RFC Editor or the Internet-Drafts function • All IETF Contributions are subject to the rules of RFC 3978 (updated by RFC 4748) and RFC 3979. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. • Please consult RFC 3978 (and RFC 4748) for details. • A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. • A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public. IETF KMART BoF

  3. Agenda WEDNESDAY, 1300-1500, Room: Franklin 3 / 4 • 5 min. Administrativia (scribe etc), Agenda Bashing Goals and Ground Rules of BoF - Chairs • 5 min. Goals - Tim Polk • 10 min. Constraints on Automated Key Management for Routing Protocols - Ross Callon • 15 min. Routing Threats and Key Management - Sandy Murphy • 10 min. Operational Considerations - Ron Bonica • 10 min. Issues with Existing Cryptographic Protection Methods for Routing Protocols - Dave Ward • 15 min. Key Management - Eric Rescorla • 45 min. Open Microphone (limited to 5 minute or less per speaker) • 5 min. Where to go from here - Area Directors IETF KMART BoF

  4. Goals • Improved understanding • Of the constraints and practices of routing deployment and operation. • Of the Routing Area view of Routing Security. • Of the threats which key management can defend against. • Of the Security Area view of Automated Key Management. • It is NOT a goal to form a working group solely based on this BOF. IETF KMART BoF

  5. Ground Rules • We have 50 minutes of open microphone time but we need to stick to the schedule to actually get it. • Generally speaking, questions should be held until the open microphone time. • During open microphone time, you can ask as many questions as you want but at the end of your five minutes, you have to go to the back of the line. • You don’t have to use all the time you are allowed! IETF KMART BoF

More Related