IETF Logo Mail Archive

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

Yingzhe Wu <ywu@huawei.com> Tue, 15 May 2007 18:13 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 1Ho1Wy-0002jY-4F; Tue, 15 May 2007 14:13:52 -0400
Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1Ho1Wx-0002jN-0g for mip4-confirm+ok@megatron.ietf.org; Tue, 15 May 2007 14:13:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ho1Ww-0002jF-NK for mip4@ietf.org; Tue, 15 May 2007 14:13:50 -0400
Received: from usaga01-in.huawei.com ([206.16.17.211]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ho1Wv-0001WH-EH for mip4@ietf.org; Tue, 15 May 2007 14:13:50 -0400
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JI30085OHB0M1@usaga01-in.huawei.com> for mip4@ietf.org; Tue, 15 May 2007 11:13:48 -0700 (PDT)
Received: from YingzheWu ([10.192.25.73]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JI300850HAUJ9@usaga01-in.huawei.com> for mip4@ietf.org; Tue, 15 May 2007 11:13:48 -0700 (PDT)
Date: Tue, 15 May 2007 11:13:40 -0700
From: Yingzhe Wu <ywu@huawei.com>
Subject: RE: [Mip4] Working Group Last Call fordraft-ietf-mip4-radius-requirements-02.txt
In-reply-to: <BE4B07D4197BF34EB3B753DD34EBCD130185ACDE@de01exm67.ds.mot.com>
To: 'McCann Peter-A001034' <pete.mccann@motorola.com>, mip4@ietf.org, radiusext@ops.ietf.org
Message-id: <001a01c7971c$c49d4c70$4919c00a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: AceM8+qZ6xjwEQu1TuCXEa1eFUhoKQKIBS6Q
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
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

It would be great if MIP4 attributes could be standardized. That will
benefit many SDOs.

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

Thanks,
Yingzhe

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

v2.23.0 | Report a Bug | By Email