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


        RFC 1675:

        Title:      Security Concerns for IPng
        Author:     S. Bellovin
        Mailbox:    smb@research.att.com
        Pages:      4
        Characters: 8,290
        Updates/Obsoletes:  none


This document was submitted to the IETF IPng area in response to RFC
1550.  Publication of this document does not imply acceptance by the
IPng area of any ideas expressed within.  Comments should be
submitted to the big-internet@munnari.oz.au mailing list.

A number of the candidates for IPng have some features that are
somewhat worrisome from a security perspective.  While it is not
necessary that IPng be an improvement over IPv4, it is mandatory that
it not make things worse.  In this memo, the author outlines a number
of areas of concern.  In some cases, there are features that would
have a negative impact on security if nothing else is done.  It may be
desirable to adopt the features anyway, but in that case, the
corrective action is mandatory.

This memo provides information for the Internet community.  This memo
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@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

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

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute