IETF Logo Mail Archive

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

Hans Sjostrand <hans@ipunplugged.com> Wed, 16 May 2007 10:03 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 1HoGLd-0001xe-Jq; Wed, 16 May 2007 06:03:09 -0400
Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1HoGLa-0001xY-Fj for mip4-confirm+ok@megatron.ietf.org; Wed, 16 May 2007 06:03:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoGLa-0001xQ-2P for mip4@ietf.org; Wed, 16 May 2007 06:03:06 -0400
Received: from 213.80.52.78.dataphone.se ([213.80.52.78] helo=mailgw.local.ipunplugged.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HoGLY-0007UN-7q for mip4@ietf.org; Wed, 16 May 2007 06:03:06 -0400
Received: from [127.0.0.1] (c53.local.ipunplugged.com [192.168.4.253]) by mailgw.local.ipunplugged.com (8.12.8/8.12.3) with ESMTP id l4GA2v16030701 for <mip4@ietf.org>; Wed, 16 May 2007 12:03:02 +0200
Message-ID: <464AD6D2.6010200@ipunplugged.com>
Date: Wed, 16 May 2007 12:02:58 +0200
From: Hans Sjostrand <hans@ipunplugged.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: Re: [Mip4] Working Group Last Call for draft-ietf-mip4-radius-requirements-02.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130185ACDE@de01exm67.ds.mot.com> <BE4B07D4197BF34EB3B753DD34EBCD13018C8595@de01exm67.ds.mot.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD13018C8595@de01exm67.ds.mot.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on mailgw.local.ipunplugged.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
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."

Regards
/// Hasse


On 2007-05-15 20:02, McCann Peter-A001034 wrote:
> 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/

v2.23.0 | Report a Bug | By Email