RFC 5094 on Mobile IPv6 Vendor Specific Option
rfc-editor@rfc-editor.org Tue, 18 December 2007 01:04 UTC
Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4QsW-0002EL-3g; Mon, 17 Dec 2007 20:04:12 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4QsG-0001yV-7v; Mon, 17 Dec 2007 20:03:56 -0500
Received: from bosco.isi.edu ([128.9.168.207]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4QsA-0006OY-N2; Mon, 17 Dec 2007 20:03:56 -0500
Received: by bosco.isi.edu (Postfix, from userid 70) id 6B5F8100336; Mon, 17 Dec 2007 17:03:50 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20071218010350.6B5F8100336@bosco.isi.edu>
Date: Mon, 17 Dec 2007 17:03:50 -0800
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: mip6@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 5094 on Mobile IPv6 Vendor Specific Option
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>
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries. RFC 5094 Title: Mobile IPv6 Vendor Specific Option Author: V. Devarapalli, A. Patel, K. Leung Status: Standards Track Date: December 2007 Mailbox: vijay.devarapalli@azairenet.com, alpesh@cisco.com, kleung@cisco.com Pages: 7 Characters: 11430 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip6-vsm-03.txt URL: http://www.rfc-editor.org/rfc/rfc5094.txt There is a need for vendor-specific extensions to Mobility Header messages so that Mobile IPv6 vendors are able to extend the protocol for research or deployment purposes. This document defines a new vendor-specific mobility option. [STANDARDS TRACK] This document is a product of the Mobility for IPv6 Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: 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. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce