IETF Logo Mail Archive

[Mip6] Experimental and Vendor specific messages

Vijay Devarapalli <vijay.devarapalli@azairenet.com> Mon, 24 September 2007 17:49 UTC

Return-path: <mip6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IZs43-0003JJ-0Z; Mon, 24 Sep 2007 13:49:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IZs42-0003E2-BS for mip6@ietf.org; Mon, 24 Sep 2007 13:49:46 -0400
Received: from mail2.azairenet.com ([207.47.15.6]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IZs41-0001Mu-RX for mip6@ietf.org; Mon, 24 Sep 2007 13:49:46 -0400
Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Sep 2007 10:49:43 -0700
Message-ID: <46F7F8B3.9050409@azairenet.com>
Date: Mon, 24 Sep 2007 10:49:39 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Sep 2007 17:49:43.0269 (UTC) FILETIME=[49C72150:01C7FED3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [Mip6] Experimental and Vendor specific messages
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,

A few changes were made to the two documents that describe the 
Experimental and Vendor specific messages and options to address IESG 
comments. I believe most of the comments have been addressed. The 
changes were related to added some text on deployment and security 
considerations. For the Vendor specific mobility option a new sub-type 
field was added to identify the type of vendor specific information that 
is carried in the option. You can see the diff with the earlier versions at

http://tools.ietf.org/wg/mip6/draft-ietf-mip6-experimental-messages/draft-ietf-mip6-experimental-messages-02-from-01.diff.html

http://tools.ietf.org/wg/mip6/draft-ietf-mip6-vsm/draft-ietf-mip6-vsm-02-from-01.diff.html

Let me know if you have any comments.

Vijay

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

v2.23.0 | Report a Bug | By Email