RE: [Mip4] Working Group Last Call for draft-ietf-mip4-radius-requirements-02.txt

"McCann Peter-A001034" <pete.mccann@motorola.com> Tue, 15 May 2007 18:02 UTC

Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ho1Lz-0005Hc-LJ; Tue, 15 May 2007 14:02:31 -0400
Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1Ho1Ly-0005HX-Db for mip4-confirm+ok@megatron.ietf.org; Tue, 15 May 2007 14:02:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ho1Ly-0005HP-3j for mip4@ietf.org; Tue, 15 May 2007 14:02:30 -0400
Received: from mail153.messagelabs.com ([216.82.253.51]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ho1Lw-0004Wj-NF for mip4@ietf.org; Tue, 15 May 2007 14:02:30 -0400
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-14.tower-153.messagelabs.com!1179252146!9860987!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 11426 invoked from network); 15 May 2007 18:02:26 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-14.tower-153.messagelabs.com with SMTP; 15 May 2007 18:02:26 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l4FI2P4m010940 for <mip4@ietf.org>; Tue, 15 May 2007 11:02:26 -0700 (MST)
Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144]) by il06exr04.mot.com (8.13.1/Vontu) with SMTP id l4FI2PB5002839 for <mip4@ietf.org>; Tue, 15 May 2007 13:02:25 -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 l4FI2O4m002821 for <mip4@ietf.org>; Tue, 15 May 2007 13:02:24 -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
Subject: RE: [Mip4] Working Group Last Call for draft-ietf-mip4-radius-requirements-02.txt
Date: Tue, 15 May 2007 14:02:23 -0400
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD13018C8595@de01exm67.ds.mot.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130185ACDE@de01exm67.ds.mot.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mip4] Working Group Last Call for draft-ietf-mip4-radius-requirements-02.txt
thread-index: AceM8+qZ6xjwEQu1TuCXEa1eFUhoKQKJwZyw
References: <BE4B07D4197BF34EB3B753DD34EBCD130185ACDE@de01exm67.ds.mot.com>
From: McCann Peter-A001034 <pete.mccann@motorola.com>
To: mip4@ietf.org, radiusext@ops.ietf.org
X-Vontu: Pass
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Reminder: this WGLC ends tomorrow, Wednesday the 16th.
Please respond with your comments.  So far we only have
one response.  If we do not see more support for the
draft it will not be advanced.

-Pete

McCann Peter-A001034 wrote:
> This message announces a 2 week working group last call
> on:
> 
> "Mobile IPv4 RADIUS Requirements"
> draft-ietf-mip4-radius-requirements-02.txt.
> 
> The last call will end at 24:00 UTC on Wednesday, May 16th.
> 
> "Mobile IPv4 RADIUS Requirements" lists a set of goals and
> assumptions to lay the groundwork for future RADIUS extensions in
> support of Mobile IPv4.  
> 
> A URL for this internet draft is:
> 
>
http://www.ietf.org/internet-drafts/draft-ietf-mip4-radius-requirements-
02.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 an Informational 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 an Informational RFC, for the
>      following reasons:"
>     ...
> 
> Please direct all replies to the Mobile IPv4 mailing list,
> mip4@ietf.org. 
> 
> -Pete & Henrik



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/