Supporting Authentication Trailer for OSPFv3
draft-acee-ospf-rfc6506bis-03

Document Type Replaced Internet-Draft (individual)
Last updated 2013-12-17 (latest revision 2013-06-23)
Replaced by draft-ietf-ospf-rfc6506bis
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-ospf-rfc6506bis
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-acee-ospf-rfc6506bis-03.txt

Abstract

Currently, OSPF for IPv6 (OSPFv3) uses IPsec as the only mechanism for authenticating protocol packets. This behavior is different from authentication mechanisms present in other routing protocols (OSPFv2, Intermediate System to Intermediate System (IS-IS), RIP, and Routing Information Protocol Next Generation (RIPng)). In some environments, it has been found that IPsec is difficult to configure and maintain and thus cannot be used. This document defines an alternative mechanism to authenticate OSPFv3 protocol packets so that OSPFv3 does not only depend upon IPsec for authentication. This document obsoletes RFC 6506.

Authors

Manav Bhatia (manav.bhatia@alcatel-lucent.com)
Vishwas Manral (vishwas.manral@hp.com)
Acee Lindem (acee.lindem@ericsson.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)