Re: [Seamoby] Status of WG Last Call

"James Kempf" <kempf@docomolabs-usa.com> Fri, 11 January 2002 22:22 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01864 for <seamoby-archive@odin.ietf.org>; Fri, 11 Jan 2002 17:22:34 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA18823; Fri, 11 Jan 2002 17:12:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA18793 for <seamoby@optimus.ietf.org>; Fri, 11 Jan 2002 17:12:15 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01577 for <seamoby@ietf.org>; Fri, 11 Jan 2002 17:12:12 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126]) by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id g0BMBhS19656; Fri, 11 Jan 2002 14:11:43 -0800 (PST)
Message-ID: <024301c19aec$ba3d1850$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: George Tsirtsis <G.Tsirtsis@flarion.com>, Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>, seamoby@ietf.org
References: <8C92E23A3E87FB479988285F9E22BE465AB939@ftmail>
Subject: Re: [Seamoby] Status of WG Last Call
Date: Fri, 11 Jan 2002 14:10:07 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit


> >From what I remember Gary said that he supports the removal of 3 out
of the
> 4 points....so the 2 opinions against the removal do not constitute
what I
> would call....WG consensus do they? In fact only Madjid said that "we
could
> re-word but not remove"...who was the 2nd person against removal?
>
> Maybe you should ask "who cares?"
>

Alright, but this is *the very last time*. We do really need to get this
document on the way.
This is a concensus call. Is there any opposition to removing the
following requirements
from draft-ietf-seamoby-ct-reqs-02.txt:

4.12 The context information to be transferred MUST be available at the
AR
performing the transfer, prior to the initiation of a given phase of the
context transfer.
4.13 The context transfer solution WILL NOT verify the context
information
prior to transfer.
4.15 The context transfer solution MAY include methods for interworking
with
non-IETF mobility solutions.
5.5.2 A context update MUST preserve the integrity, and thus the
meaning, of
the context at each receiving AR.

Speak until Monday 3 PM Pacific Standard time or forever hold your
peace.

            jak



_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby