Re: [Seamoby] Status of WG Last Call

"James Kempf" <kempf@docomolabs-usa.com> Mon, 14 January 2002 17:50 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 MAA09350 for <seamoby-archive@odin.ietf.org>; Mon, 14 Jan 2002 12:50:38 -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 MAA16069; Mon, 14 Jan 2002 12:32:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA16028 for <seamoby@optimus.ietf.org>; Mon, 14 Jan 2002 12:32:10 -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 MAA08502 for <seamoby@ietf.org>; Mon, 14 Jan 2002 12:31:51 -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 g0EHVJS00846; Mon, 14 Jan 2002 09:31:19 -0800 (PST)
Message-ID: <003201c19d21$0d68d420$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: Satish Jamadagni <satishj@sasken.com>, Govind Krishnamurthi <govs23@hotmail.com>, seamoby@ietf.org
References: <F237RbQghl1c5XGt6xo0001ae1a@hotmail.com> <000a01c19c1a$48991800$9830010a@SATISHJ>
Subject: Re: [Seamoby] Status of WG Last Call
Date: Mon, 14 Jan 2002 09:29:42 -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

Satish,

Thanx for the thoughts, but the concensus call is limited to whether
requirements 4.12, 4.13, 4.15 and 5.5.2 should
be kept or dropped. We have been working on these requirements for the
better part of a year, and we must
advance this draft. If you care to express an opinion on whether the
requirements should be kept or dropped, you
have until 3:00 PM Pacific Time today.

            jak

----- Original Message -----
From: "Satish Jamadagni" <satishj@sasken.com>
To: "Govind Krishnamurthi" <govs23@hotmail.com>; <seamoby@ietf.org>
Sent: Sunday, January 13, 2002 2:08 AM
Subject: Re: [Seamoby] Status of WG Last Call


> Hi All,
> The discussion here seems to have assumed that the nFA or the new AR
CAN and
> WILL ALWAYS accept the mobile terminal demands in terms of its usage
> "context".
>
> Is it appropriate for us to make such an assumption in the face of
varied
> load or QoS considerations. Should it not be the concern of the
context
> transfer WG to evolve some form of "negotiation mechanism" before a
context
> transfer can be effected.
>
> This means that the notion of context integrity during context
transfer
> should be subject to such a negotiation mechanism or signaling.
>
> This is my first attempt to participate in these discussions so please
do
> forgive me if such discussion has taken place or if it has been
deligated to
> some other body or working group.
>
> Regards,
> Satish Jamadagni
> Research Scientist
> Sasken Communiocation Technologies Ltd
> www.sasken.com
> Bangalore.
>
>
>
> ----- Original Message -----
> From: "Govind Krishnamurthi" <govs23@hotmail.com>
> To: <seamoby@ietf.org>
> Sent: Saturday, January 12, 2002 5:32 AM
> Subject: Re: [Seamoby] Status of WG Last Call
>
>
> > Do we loose much by letting 4.12 stay? I don't see this such a big
> > problem as the transferring AR much get the context prior to
transfer
> > anyways.. so the only point is how much prior.
> > Maybe I'm missing something.
> > -Govind.
> >
> > >
> > >
> > > > Since I spoke up before and my name was mentioned in the recent
> > > > exchange....
> > > >
> > > > I do not care about 4.12 or 4.15, one way or another.
> > > >
> > > > I do care about 5.5.2, but these requirements have revisited
> > > > so many times that the rationale behind them are ethereal,
> > > > so I will sit firmly on the fence.
> > > >
> > > > How that for an explicit non-vote?
> > > >
> > > > Gary
> > > >
> > > > > -----Original Message-----
> > > > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > > > Sent: January 11, 2002 17:10
> > > > > To: George Tsirtsis; Nakhjiri Madjid-MNAKHJI1;
seamoby@ietf.org
> > > > > Subject: Re: [Seamoby] Status of WG Last Call
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > >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
> > > > >
> > > >
> > >
> > >
> > >_______________________________________________
> > >Seamoby mailing list
> > >Seamoby@ietf.org
> > >https://www1.ietf.org/mailman/listinfo/seamoby
> >
> >
> >
> >
> > _________________________________________________________________
> > MSN Photos is the easiest way to share and print your photos:
> > http://photos.msn.com/support/worldwide.aspx
> >
> >
> > _______________________________________________
> > Seamoby mailing list
> > Seamoby@ietf.org
> > https://www1.ietf.org/mailman/listinfo/seamoby
>
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
>


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