Re: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt

Jouni Korhonen <jouni.korhonen@teliasonera.com> Wed, 29 November 2006 10:57 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpN7k-0007O4-G4; Wed, 29 Nov 2006 05:57:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpN7j-0007Nz-7k for mip4@ietf.org; Wed, 29 Nov 2006 05:57:07 -0500
Received: from ceiling.dave.sonera.fi ([131.177.130.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpN7h-00034t-Oi for mip4@ietf.org; Wed, 29 Nov 2006 05:57:07 -0500
Received: from ceiling.dave.sonera.fi (localhost [127.0.0.1]) by ceiling.dave.sonera.fi (Sendmail) with ESMTP id kATAutCx020363 for <mip4@ietf.org>; Wed, 29 Nov 2006 12:56:56 +0200 (EET)
Received: from [131.177.37.116] (l50029133.pool.sonera.fi [131.177.37.116]) by ceiling.dave.sonera.fi (Sendmail) with ESMTP id kATAusYk020347; Wed, 29 Nov 2006 12:56:54 +0200 (EET)
Message-ID: <456D6775.4050905@teliasonera.com>
Date: Wed, 29 Nov 2006 12:56:53 +0200
From: Jouni Korhonen <jouni.korhonen@teliasonera.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com> <456CA2B2.9010708@azairenet.com>
In-Reply-To: <456CA2B2.9010708@azairenet.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: mip4@ietf.org, McCann Peter-A001034 <pete.mccann@motorola.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

Hi Vijay,

I think it was me who asked for this appendix. I'm happy to have it 
there now. I'm not sure whether it makes any additional value to mention 
in appendix A that the operator trusted network could also be 
implemented as the home link from MNs. For certain wireless technologies 
this would give a nice optimization.

Apart from the above "I support the advancement of this document to the 
IESG with a request for publication as proposed standard."

Cheers,
	Jouni

Vijay Devarapalli kirjoitti:
> just wanted to point out that the only major change
> since the last WG last call was to add a new section
> in the Appendix to show how the solution can be
> applied to a mobile operator network.
> 
> Vijay
> 
> McCann Peter-A001034 wrote:
>> This message announces a (second) WG last call on:
>>
>>    "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>>    draft-ietf-mip4-mobike-connectivity-01.txt
>>
>> The last call will conclude at 24:00 UTC on Tuesday, 12 December 2006.
>>
>> "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>> describes a solution using Mobile IPv4 and mobility extensions to 
>> IKEv2 (MOBIKE)
>> to provide secure connectivity and mobility.
>>
>> A URL for this internet draft is:
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-connectivity-
>> 01.txt
>>
>>
>> Please respond to this WG 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 proposed standard."
>>
>>
>>   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 proposed standard, for the following
>>     reasons:"
>>    ...
>>
>>
>>
>>
>>     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/