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

Henrik Levkowetz <henrik@levkowetz.com> Tue, 19 December 2006 20:42 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwlnL-0000Si-BQ; Tue, 19 Dec 2006 15:42:39 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwlnK-0000QO-37 for mip4@ietf.org; Tue, 19 Dec 2006 15:42:38 -0500
Received: from av10-1-sn2.hy.skanova.net ([81.228.8.181]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GwlnI-0006lv-7F for mip4@ietf.org; Tue, 19 Dec 2006 15:42:38 -0500
Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502) id 139DB3840C; Tue, 19 Dec 2006 21:42:35 +0100 (CET)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP id F039138358; Tue, 19 Dec 2006 21:42:34 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id E0C1037E42; Tue, 19 Dec 2006 21:42:34 +0100 (CET)
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from <henrik@levkowetz.com>) id 1GwlnG-0005av-J7; Tue, 19 Dec 2006 21:42:34 +0100
Message-ID: <45884EB8.1010909@levkowetz.com>
Date: Tue, 19 Dec 2006 21:42:32 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: McCann Peter-A001034 <pete.mccann@motorola.com>
Subject: Re: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: pete.mccann@motorola.com, mip4@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: mip4@ietf.org
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>
Content-Type: multipart/mixed; boundary="===============1595474028=="
Errors-To: mip4-bounces@ietf.org

Hi Pete,

on 2006-12-19 17:08 McCann Peter-A001034 said the following:
> Here is an attempted round-up of the issues that have been discussed:
> 

...
> 2. Bypass VPN for Registration Requests
> 
> There was discussion on whether it is feasible to bypass a VPN tunnel 
> for the Registration Request.  I think the discussion concluded that
> it was possible, but perhaps some text needs to be added describing
> the SAD.  Does anyone have some concrete text to propose?

[Co-chair hat off]

Actually, I'd say this is a bit of over-specification, too.  Although
bypass rules should work fine, there are other ways of doing this than
to add bypass rules, too; for some implementations it would be much more
natural to simply use for instance a BPF tap or equivalent to do this.


	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/