Re: [netlmm] Last Call: draft-ietf-netlmm-mip-interactions (Interactions betweenPMIPv6 and MIPv6: scenarios and related issues) to Informational RFC

"Charles E. Perkins" <charles.perkins@earthlink.net> Mon, 17 May 2010 16:49 UTC

DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=pUi4zZ9FxqcgZDYRTICkX+gcpMrJb2QOdL1BJ4p7pjhVjiYo27x4yf3rxQshjFzO; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Message-ID: <4BF17382.3050008@earthlink.net>
Date: Mon, 17 May 2010 09:49:06 -0700
From: "Charles E. Perkins" <charles.perkins@earthlink.net>
Organization: Wichorus Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Giaretta, Gerardo" <gerardog@qualcomm.com>
References: <20100503142438.991523A6CF2@core3.amsl.com> <4BDF35E5.1050500@earthlink.net> <057632CE4CE10D45A1A3D6D19206C3A32679D3A7DF@NASANEXMB08.na.qualcomm.com>
In-Reply-To: <057632CE4CE10D45A1A3D6D19206C3A32679D3A7DF@NASANEXMB08.na.qualcomm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: netlmm@ietf.org, ietf@ietf.org
Subject: Re: [netlmm] Last Call: draft-ietf-netlmm-mip-interactions (Interactions betweenPMIPv6 and MIPv6: scenarios and related issues) to Informational RFC
Precedence: list

Hello Gerardo,

Comments below...

On 5/17/2010 8:17 AM, Giaretta, Gerardo wrote:

> You have one comment on the recommendation in the draft to have
> separate binding cache entries. This was extensively discussed
> in the NETLMM WG and also at the IETF Dublin meeting. There was
> a mailing list discussion after that in September/October 2008
> which led to the conclusion in the current version of the draft.
>
> You can find more information in the archives at:
> http://www.ietf.org/mail-archive/web/netlmm/current/msg05533.html

Thanks for that link.  It was most enlightening,
especially in the context of the ensuing discussion.

Having reviewed the latter, it seems to me quite likely
that the consensus call was (at least) premature.

For instance:

> I object to this. There was absolutely no consensus on this for
> you guys to decide. There were clarifying questions that people
> had on what exactly you meant by multi-homing. You didn't respond
> to any of those emails.

and

> I am sorry, but I thought the discussion was either incomplete or did
> not steer towards one particular way or the other. For instance, I
> didn't get a clear answer for my question on why there would be a single
> BCE when two different interfaces are in use. Could you please clarify?

I could go on.  And, without naming names, I want to emphasize
that the abovementioned objections were made by some real experts.

Do you have any links to discussion that _supports_
the consensus call?

Furthermore, I still suggest (constructively) that
_at the minimum_ a system architect ought to be allowed
to have the design freedom to identify the two mobile
node identities (and thus the relevant BCEs).
What is the downside of enabling new systems to
offer such obvious improvements?

Or, would it be better to start writing the ...bis
document already (just kidding...)?

Regards,
Charlie P.

[netlmm] Last Call: draft-ietf-netlmm-mip-interac… The IESG
Re: [netlmm] Last Call: draft-ietf-netlmm-mip-int… Charles E. Perkins
Re: [netlmm] Last Call: draft-ietf-netlmm-mip-int… Charles E. Perkins
Re: [netlmm] Last Call: draft-ietf-netlmm-mip-int… Giaretta, Gerardo
Re: [netlmm] Last Call: draft-ietf-netlmm-mip-int… Charles E. Perkins
Re: [netlmm] Last Call: draft-ietf-netlmm-mip-int… Narayanan, Vidya
Re: [netlmm] Last Call: draft-ietf-netlmm-mip-int… Jari Arkko