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

Hans Sjostrand <hans@ipunplugged.com> Mon, 18 December 2006 21:38 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQBe-0002e8-BO; Mon, 18 Dec 2006 16:38:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQBc-0002c9-Kv for mip4@ietf.org; Mon, 18 Dec 2006 16:38:16 -0500
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 1GwQBa-0006Qe-O2 for mip4@ietf.org; Mon, 18 Dec 2006 16:38:16 -0500
Received: from [127.0.0.1] (c43.local.ipunplugged.com [192.168.4.242]) by mailgw.local.ipunplugged.com (8.12.8/8.12.3) with ESMTP id kBILc6pI005649; Mon, 18 Dec 2006 22:38:08 +0100
Message-ID: <45870A3C.1090803@ipunplugged.com>
Date: Mon, 18 Dec 2006 22:38:04 +0100
From: Hans Sjostrand <hans@ipunplugged.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] Some comments on WGLC:draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB90325133C90D0@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB90325133C90D0@NAEX13.na.qualcomm.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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: mip4@ietf.org, Vijay Devarapalli <vijay.devarapalli@azairenet.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

> The problem is that if there are any statements about using
> RFC3846-style FAAs, the document also has to talk about security issues
> with masquerading FAs. I'm not sure that is worth getting into. But, I'd
> be fine with such text, as long as the security implications are
> appropriately pointed out. 
>
> Regards,
> Vidya
>
>   

It wasn't a good idea at all to mix implementation and specification. 
I'll simply pull back anything I've proposed along with "Besides that, a 
good assumption is often a good idea....." It will just confuse people 
and possibly delay the draft.

What matters is that the draft doesn't prevent these things by 
overspecifying the order events of which things could be made. Then I'm 
happy.

Best regards
/// Hasse




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