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


        RFC 1762:

        Title:      The PPP DECnet Phase IV Control Protocol (DNCP)
        Author:     S. Senum
        Date:       March 1995
        Mailbox:    sjs@digibd.com
        Pages:      7
        Characters: 12,709
        Obsoletes:  1376

        URL:        ftp://ds.internic.net/rfc/rfc1762.txt


The Point-to-Point Protocol (PPP) provides a standard method of
encapsulating Network Layer protocol information over point-to-point
links.  PPP also defines an extensible Link Control Protocol, and
proposes a family of Network Control Protocols (NCPs) for establishing
and configuring different network-layer protocols.  This document
defines the NCP for establishing and configuring Digital's DNA Phase
IV Routing protocol (DECnet Phase IV) over PPP.  This document applies
only to DNA Phase IV Routing messages (both data and control), and not
to other DNA Phase IV protocols (MOP, LAT, etc).  This RFC is the
product of the Point-to-Point Protocol Extensions Working Group of the
IETF.

This is now a Draft Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  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