A new Request for Comments is now available in online RFC libraries.
RFC 4064
Title: Experimental Message, Extensions, and Error Codes
for Mobile IPv4
Author(s): A. Patel, K. Leung
Status: Standards Track
Date: May 2005
Mailbox: alpesh@cisco.com, kleung@cisco.com
Pages: 11
Characters: 20748
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mip4-experimental-messages-02.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc4064.txt
Mobile IPv4 message types range from 0 to 255. This document
reserves a message type for use by an individual, company, or
organization for experimental purposes, to evaluate enhancements
to Mobile IPv4 messages before a formal standards proposal is issued.
This document is a product of the Mobility for IPv4 Working Group of
the IETF.
This is now a Proposed 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@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.
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.
Attachment:
2#Part.001
Description: Binary data
Content-Type: text/plain Content-ID: <050523141233.RFC@RFC-EDITOR.ORG>
Attachment:
4#Part.003
Description: Binary data
Attachment:
5#Mime.822
Description: Binary data
AdmID:4DDD0A62EBA77CBE10F8B8E606004A84
_______________________________________________ IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
