[rfc-dist] BCP 88, RFC 3818 on IANA Considerations for the Point-to-Point Protocol (PPP)

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Mon Jun 21 12:09:43 PDT 2004

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

        BCP 88
        RFC 3818

        Title:      IANA Considerations for the Point-to-Point
                    Protocol (PPP)
        Author(s):  V. Schryver
        Status:     Best Current Practice
        Date:       June 2004
        Mailbox:    vjs at rhyolite.com
        Pages:      4
        Characters: 6321
        SeeAlso:    BCP 88

        I-D Tag:    draft-schryver-pppext-iana-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3818.txt

The charter of the Point-to-Point Protocol (PPP) Extensions working
group (pppext) includes the responsibility to "actively advance PPP's
most useful extensions to full standard, while defending against
further enhancements of questionable value."  In support of that
charter, the allocation of PPP protocol and other assigned numbers
will no longer be "first come first served."

This document is a product of the Point-to-Point Protocol Extensions
Working Group of the IETF. 

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

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

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the rfc-dist mailing list