RE: your support: [Mip4] Working Group Last Call fordraft-ietf-mip4-radius-requirements-02.txt
"Adrangi, Farid" <farid.adrangi@intel.com> Wed, 09 May 2007 20:01 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 1HlsME-0006IX-BP; Wed, 09 May 2007 16:01:54 -0400
Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1HlsMD-0006IS-JD for mip4-confirm+ok@megatron.ietf.org; Wed, 09 May 2007 16:01:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlsMD-0006IK-9g for mip4@ietf.org; Wed, 09 May 2007 16:01:53 -0400
Received: from mga03.intel.com ([143.182.124.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlsMB-0000MO-Uv for mip4@ietf.org; Wed, 09 May 2007 16:01:53 -0400
Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 09 May 2007 13:01:51 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.14,510,1170662400"; d="scan'208";a="226288412"
Received: from orsmsx334.jf.intel.com ([10.22.226.45]) by azsmga001.ch.intel.com with ESMTP; 09 May 2007 13:01:53 -0700
Received: from orsmsx418.amr.corp.intel.com ([10.22.226.87]) by orsmsx334.jf.intel.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 May 2007 13:01:50 -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: your support: [Mip4] Working Group Last Call fordraft-ietf-mip4-radius-requirements-02.txt
Date: Wed, 09 May 2007 13:01:28 -0700
Message-ID: <34B734D4F6C5BE4FB378F15FCD763A6103183CDF@orsmsx418.amr.corp.intel.com>
In-Reply-To: <001001c7925b$128788e0$2f01a8c0@china.huawei.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: your support: [Mip4] Working Group Last Call fordraft-ietf-mip4-radius-requirements-02.txt
Thread-Index: AceM8+qZ6xjwEQu1TuCXEa1eFUhoKQFZsQ+wAAZRF5A=
From: "Adrangi, Farid" <farid.adrangi@intel.com>
To: mip4@ietf.org, radiusext@ops.ietf.org
X-OriginalArrivalTime: 09 May 2007 20:01:50.0416 (UTC) FILETIME=[E1B84500:01C79274]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc:
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
Given the proposed attributes help support Mobile IP in a way that is
uniform across SDOs & ensures interoperability,
"I support the advancement of this document to the IESG with a
request for publication as an Informational RFC."
Thanks,
Farid
-----Original Message-----
From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]
Sent: Wednesday, May 02, 2007 12:56 PM
To: mip4@ietf.org; radiusext@ops.ietf.org
Cc: Henrik Levkowetz
Subject: [Mip4] Working Group Last Call
fordraft-ietf-mip4-radius-requirements-02.txt
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/
- RE: your support: [Mip4] Working Group Last Call … Adrangi, Farid