IETF Logo Mail Archive

Re: [Mobopts] IRSG review of draft-irtf-mobopts-location-privacy-solutions-08.txt

"Rajeev Koodli" <rajeev.koodli@gmail.com> Wed, 21 May 2008 03:48 UTC

Return-Path: <mobopts-bounces@ietf.org>
X-Original-To: mobopts-archive@megatron.ietf.org
Delivered-To: ietfarch-mobopts-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 365663A6911; Tue, 20 May 2008 20:48:10 -0700 (PDT)
X-Original-To: mobopts@core3.amsl.com
Delivered-To: mobopts@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FCE73A6B5C for <mobopts@core3.amsl.com>; Tue, 20 May 2008 20:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level:
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZSUoIMYFjR0 for <mobopts@core3.amsl.com>; Tue, 20 May 2008 20:48:06 -0700 (PDT)
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.178]) by core3.amsl.com (Postfix) with ESMTP id ED74F28DDF7 for <mobopts@irtf.org>; Tue, 20 May 2008 11:23:47 -0700 (PDT)
Received: by el-out-1112.google.com with SMTP id r23so721481elf.10 for <mobopts@irtf.org>; Tue, 20 May 2008 11:23:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=F3W2np67EdBJeyCVionVtQrQkCDL57s/TWHDaEcOFCc=; b=bAgqukmMOj+zgY0ygdbZArksfwzGn0SVYElS2yUo3c9hZfPrPFAW6Df0UYUiv6ySuQXNZ9c6dMhLDeARv3pMuCNXT9Ffq1xCM2X/w3WIBGv8H+GGw37sMQFY7pa3z4meaTjuNgLEzQ1ALUnjuIt3iPcfW6TPZVfV0s205H0M7W4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=rEds4ujBW1g5jQVl2WedvGIs5MG3gk/jcLVbckMcFO34/7FJhUs0DX/eB2ocgMn1anGv9ex53RHkud0rADC9YJE9DrTrqjxk6nK2WzcIRytMH7+76tO/ylgCpp+qk63SI3IYP2eak8Fq8a12C7o78BgL+1jrp6T8qtWja4mvo1M=
Received: by 10.142.156.19 with SMTP id d19mr2446282wfe.261.1211307825676; Tue, 20 May 2008 11:23:45 -0700 (PDT)
Received: by 10.142.203.7 with HTTP; Tue, 20 May 2008 11:23:45 -0700 (PDT)
Message-ID: <3d57679a0805201123w463879d6lcaf87df656442cf@mail.gmail.com>
Date: Tue, 20 May 2008 11:23:45 -0700
From: Rajeev Koodli <rajeev.koodli@gmail.com>
To: Michael Welzl <michael.welzl@uibk.ac.at>
In-Reply-To: <1211184052.3652.55.camel@pc105-c703.uibk.ac.at>
MIME-Version: 1.0
References: <424070.62934.qm@web50302.mail.re2.yahoo.com> <1211184052.3652.55.camel@pc105-c703.uibk.ac.at>
Cc: rajeev_koodli@yahoo.com, irsg@isi.edu, basavaraj.patil@nsn.com, mobopts@irtf.org
Subject: Re: [Mobopts] IRSG review of draft-irtf-mobopts-location-privacy-solutions-08.txt
X-BeenThere: mobopts@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility Optimizations <mobopts.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mobopts>
List-Post: <mailto:mobopts@ietf.org>
List-Help: <mailto:mobopts-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1334611122=="
Sender: mobopts-bounces@ietf.org
Errors-To: mobopts-bounces@ietf.org

Hello Michael,
thank you for your detailed review. The authors will take a look and
respond.

In the meanwhile, couple of quick replies below.

On Mon, May 19, 2008 at 1:00 AM, Michael Welzl <michael.welzl@uibk.ac.at>
wrote:

>
> These rules also state that it must be very clear throughout the
> document that
> it is not an IETF product and is not a standard. I'm not sure if this is
> really so clear in this case.
>

This is a boilerplate issue for an IRTF RFC. The RFC coming from the IRTF
stream makes it evident that it is not an IETF product or a standard. The
boilerplate in the eventual RFC will capture that (it's hard to mention this
throughout the document)

On the whole, the presentation is quite poor; while I have no expertise
> in
> this field (which, by the way, makes it very hard for me to comment on
> technical issues), the document should be easier to read even for
> someone like me than it is in its current form.
>

I understand. However, the document is fairly involved, and does assume
familiarity with the nits and grits of IP mobility.
We will try to address your input below. However, I am afraid we cannot
simplify it further technically.

Thanks again.

-Rajeev

_______________________________________________
Mobopts mailing list
Mobopts@ietf.org
https://www.ietf.org/mailman/listinfo/mobopts

v2.23.0 | Report a Bug | By Email