A new Request for Comments is now available in online RFC libraries.


        RFC 2367:

        Title:      PF_KEY Key Management API, Version 2
	Author(s):  D. McDonald, C. Metz, B. Phan
	Status:     Informational
	Date:       July 1998
        Mailbox:    danmcd@eng.sun.com, cmetz@inner.net,
		    phan@itd.nrl.navy.mil
	Pages:      68
        Characters: 146754
        Updates/Obsoletes: None


        URL:        ftp://ftp.isi.edu/in-notes/rfc2367.txt


A generic key management API that can be used not only for IP Security
but also for other network security services is presented in this
document.  Version 1 of this API was implemented inside 4.4-Lite BSD
as part of the U. S. Naval Research Laboratory's freely distributable
and usable IPv6 and IPsec implementation.  It is documented here for
the benefit of others who might also adopt and use the API, thus
providing increased portability of key management applications (e.g. a
manual keying application, an ISAKMP daemon, a GKMP daemon, a Photuris
daemon, or a SKIP certificate discovery protocol daemon).

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute