Re: [Mip4] Comments on draft-devarapalli-mip4-mobike-connectivity-00

Vijay Devarapallli <dvijay@gmail.com> Fri, 30 September 2005 23:14 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ELU5b-0001GO-2T; Fri, 30 Sep 2005 19:14:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ELU5Z-0001GJ-Ud for mip4@megatron.ietf.org; Fri, 30 Sep 2005 19:14:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25539 for <mip4@ietf.org>; Fri, 30 Sep 2005 19:14:47 -0400 (EDT)
Received: from xproxy.gmail.com ([66.249.82.201]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ELUDW-0001Ko-4c for mip4@ietf.org; Fri, 30 Sep 2005 19:23:03 -0400
Received: by xproxy.gmail.com with SMTP id t13so1310wxc for <mip4@ietf.org>; Fri, 30 Sep 2005 16:14:39 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MmcuVXySLqiKhFJ+fT7HQ63L9tJYWP+B+6Pd+pn8l0a2ZhyV56wCEQqc+uqOqVTEUy4tXlx8u/8arRg5GX6vYZRMBtljwnjwXUwYIPZKbti1FJGhLbsEo0p1fjF2ZtgEOXkeO9B74go3D5j/1JNqPAQn46wor19QZ+KDJB4zxkc=
Received: by 10.70.109.7 with SMTP id h7mr1084178wxc; Fri, 30 Sep 2005 16:14:39 -0700 (PDT)
Received: by 10.70.28.18 with HTTP; Fri, 30 Sep 2005 16:14:39 -0700 (PDT)
Message-ID: <f1f4dcdc0509301614r2027ad99sb727739d670a683c@mail.gmail.com>
Date: Fri, 30 Sep 2005 16:14:39 -0700
From: Vijay Devarapallli <dvijay@gmail.com>
To: "T.J. Kniveton" <tj@kniveton.com>
Subject: Re: [Mip4] Comments on draft-devarapalli-mip4-mobike-connectivity-00
In-Reply-To: <D7815C85-3C12-4C31-B4A2-514B20C19EF7@kniveton.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <D7815C85-3C12-4C31-B4A2-514B20C19EF7@kniveton.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: quoted-printable
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Vijay Devarapallli <dvijay@gmail.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

hi TJ,

thanks for the detailed review.

I made most of the changes you suggested.

> bullet 3.
> Is it possible to abandon the step 1 exchange if step 2 is
> successful, or must the tunnel be set up and optionally torn down?

it may not be possible to interrupt the exchange. it could be
torn down later on. Or we can just let it expire.

Vijay

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