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

"Tsirtsis, George" <tsirtsis@qualcomm.com> Wed, 16 May 2007 07:40 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 1HoE7q-0000RM-AJ; Wed, 16 May 2007 03:40:46 -0400
Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1HoE7p-0000RD-3N for mip4-confirm+ok@megatron.ietf.org; Wed, 16 May 2007 03:40:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoE7k-0000Hi-Ty for mip4@ietf.org; Wed, 16 May 2007 03:40:40 -0400
Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HoE7j-0008St-G0 for mip4@ietf.org; Wed, 16 May 2007 03:40:40 -0400
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l4G7ebPl018026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 16 May 2007 00:40:37 -0700
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com [172.30.36.175]) by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l4G7eZLQ028641; Wed, 16 May 2007 00:40:36 -0700 (PDT)
Received: from NAEX16.na.qualcomm.com ([10.47.6.157]) by sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 May 2007 00:40:36 -0700
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 fordraft-ietf-mip4-radius-requirements-02.txt
Date: Wed, 16 May 2007 00:40:33 -0700
Message-ID: <2309978910A6A6478C2C7585692B0AF457A2A7@NAEX16.na.qualcomm.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD13018C8595@de01exm67.ds.mot.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mip4] Working Group Last Call fordraft-ietf-mip4-radius-requirements-02.txt
Thread-Index: AceM8+qZ6xjwEQu1TuCXEa1eFUhoKQKJwZywAByfGeA=
References: <BE4B07D4197BF34EB3B753DD34EBCD130185ACDE@de01exm67.ds.mot.com> <BE4B07D4197BF34EB3B753DD34EBCD13018C8595@de01exm67.ds.mot.com>
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: McCann Peter-A001034 <pete.mccann@motorola.com>, mip4@ietf.org, radiusext@ops.ietf.org
X-OriginalArrivalTime: 16 May 2007 07:40:36.0388 (UTC) FILETIME=[7E066640:01C7978D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
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

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

George
-----Original Message-----
From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] 
Sent: Tuesday, May 15, 2007 7:02 PM
To: mip4@ietf.org; radiusext@ops.ietf.org
Cc: Henrik Levkowetz
Subject: RE: [Mip4] Working Group Last Call
fordraft-ietf-mip4-radius-requirements-02.txt


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/


-- 
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/