[Mip4] WGLC: draft-ietf-mip4-rfc2006bis-06.txt

"McCann Peter-A001034" <pete.mccann@motorola.com> Tue, 07 April 2009 14:54 UTC

Return-Path: <pete.mccann@motorola.com>
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1B273A6801 for <mip4@core3.amsl.com>; Tue, 7 Apr 2009 07:54:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Am7fwbt7pkwn for <mip4@core3.amsl.com>; Tue, 7 Apr 2009 07:54:05 -0700 (PDT)
Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with ESMTP id 2CE983A6818 for <mip4@ietf.org>; Tue, 7 Apr 2009 07:54:05 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-2.tower-128.messagelabs.com!1239116109!9442199!1
X-StarScan-Version: 6.0.0; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 17186 invoked from network); 7 Apr 2009 14:55:09 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-2.tower-128.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Apr 2009 14:55:09 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.14.3/8.14.3) with ESMTP id n37Et62p019543 for <mip4@ietf.org>; Tue, 7 Apr 2009 07:55:08 -0700 (MST)
Received: from il06vts01.mot.com (il06vts01.mot.com [129.188.137.141]) by il06exr04.mot.com (8.13.1/Vontu) with SMTP id n37Et6hZ007013 for <mip4@ietf.org>; Tue, 7 Apr 2009 09:55:06 -0500 (CDT)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id n37Et6BI007010 for <mip4@ietf.org>; Tue, 7 Apr 2009 09:55:06 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 07 Apr 2009 10:54:44 -0400
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD130386232E@de01exm67.ds.mot.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: WGLC: draft-ietf-mip4-rfc2006bis-06.txt
Thread-Index: Acm3kMmy8RMlSPfqR0CdnNViGKaNZw==
From: McCann Peter-A001034 <pete.mccann@motorola.com>
To: mip4@ietf.org
X-CFilter-Loop: Reflected
Cc: Henrik Levkowetz <henrik@levkowetz.com>
Subject: [Mip4] WGLC: draft-ietf-mip4-rfc2006bis-06.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mip4>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2009 14:54:06 -0000

This message announces a 2-week working group last call on:

"The Definitions of Managed Objects for IP Mobility Support using SMIv2,
revised"
draft-ietf-mip4-rfc2006bis-06.txt

The last call will end at 24:00 UTC on Tuesday, April 21 2009.

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. 
In particular, it describes managed objects used for managing the Mobile
Node, Foreign Agent and Home Agent of the Mobile IP Protocol.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-rfc2006bis-06.txt

Please respond to this working group last call:

* If you have no comments on the draft, and support its advancement,
  simply respond with a line containing something like

    "I support the advancement of this document to the IESG with a
     request for publication as a Proposed Standard RFC."

   If you have comments, please use a line similar to the one above,
   and supplement this with your comments.


* If you *don't* support its advancement, respond with a line
  containing something like the following, supplemented by your
  comments -

    "I don't support the advancement of this document to the IESG with
     a request for publication as a Proposed Standard RFC, for the
     following reasons:"
    ...

Please direct all replies to the Mobile IPv4 mailing list,
mip4@ietf.org.


-Pete