BCP 88, RFC 3818 on IANA Considerations for the Point-to-Point Protocol (PPP)
rfc-editor@rfc-editor.org Mon, 21 June 2004 21:34 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02944 for <ietf-announce-archive@ietf.org>; Mon, 21 Jun 2004 17:34:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BcWRE-0004Tn-IH for ietf-announce-archive@ietf.org; Mon, 21 Jun 2004 17:34:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BcWOC-0003YR-00 for ietf-announce-archive@ietf.org; Mon, 21 Jun 2004 17:31:41 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BcWL8-0002eF-00; Mon, 21 Jun 2004 17:28:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BcVfD-0005Lr-Gd; Mon, 21 Jun 2004 16:45:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BcUDz-000496-2l for ietf-announce@megatron.ietf.org; Mon, 21 Jun 2004 15:12:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18111 for <ietf-announce@ietf.org>; Mon, 21 Jun 2004 15:12:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BcUDx-0000FC-MJ for ietf-announce@ietf.org; Mon, 21 Jun 2004 15:12:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BcUCu-0007lh-00 for ietf-announce@ietf.org; Mon, 21 Jun 2004 15:11:53 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BcUC6-0007HG-00 for ietf-announce@ietf.org; Mon, 21 Jun 2004 15:11:02 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i5LJ9gJ11096; Mon, 21 Jun 2004 12:09:42 -0700 (PDT)
Message-Id: <200406211909.i5LJ9gJ11096@boreas.isi.edu>
To: IETF-Announce:;
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 21 Jun 2004 12:09:42 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Mailman-Approved-At: Mon, 21 Jun 2004 16:44:48 -0400
Cc: ietf-ppp@merit.edu, rfc-editor@rfc-editor.org
Subject: BCP 88, RFC 3818 on IANA Considerations for the Point-to-Point Protocol (PPP)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60
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@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@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 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.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce