[Mip6] [Fwd: Fwd: I-D ACTION:draft-devarapalli-mip6-vsm-01.txt]

Vijay Devarapalli <vijay.devarapalli@azairenet.com> Tue, 10 October 2006 22:00 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXPdu-0001MC-Hs; Tue, 10 Oct 2006 18:00:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXPdt-0001M7-7d for mip6@ietf.org; Tue, 10 Oct 2006 18:00:05 -0400
Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6] helo=moe.corp.azairenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXPdr-0005uK-S3 for mip6@ietf.org; Tue, 10 Oct 2006 18:00:05 -0400
Received: from [10.1.201.21] ([66.92.223.6]) by moe.corp.azairenet.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Oct 2006 14:57:34 -0700
Message-ID: <452C17E0.8010107@azairenet.com>
Date: Tue, 10 Oct 2006 15:00:00 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Oct 2006 21:57:35.0041 (UTC) FILETIME=[17E0B310:01C6ECB7]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Subject: [Mip6] [Fwd: Fwd: I-D ACTION:draft-devarapalli-mip6-vsm-01.txt]
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

hello,

here is the revised version of the vendor specific
message document. the earlier version had both a
vendor specific mobility header message and a vendor
specific mobility option. at the last IETF, there
was some discussion on how it can be dangerous
(interoperability reasons) to have a vendor specific
mobility header message. so thats been removed.

comments are welcome.

Vijay

---------- Forwarded message ----------
From: Internet-Drafts@ietf.org <Internet-Drafts@ietf.org>
Date: Oct 9, 2006 12:50 PM
Subject: I-D ACTION:draft-devarapalli-mip6-vsm-01.txt
To: i-d-announce@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


        Title           : Mobile IPv6 Vendor Specific Messages
        Author(s)       : V. Devarapalli
        Filename        : draft-devarapalli-mip6-vsm-01.txt
        Pages           : 6
        Date            : 2006-10-9

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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-devarapalli-mip6-vsm-01.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
"get draft-devarapalli-mip6-vsm-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-devarapalli-mip6-vsm-01.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.




_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6