RE: [Seamoby] Status of WG Last Call

Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com> Mon, 14 January 2002 20:58 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 PAA18791 for <seamoby-archive@odin.ietf.org>; Mon, 14 Jan 2002 15:58:31 -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 PAA23674; Mon, 14 Jan 2002 15:37:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA23647 for <seamoby@optimus.ietf.org>; Mon, 14 Jan 2002 15:37:17 -0500 (EST)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17971 for <seamoby@ietf.org>; Mon, 14 Jan 2002 15:37:13 -0500 (EST)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate.mot.com (motgate 2.1) with ESMTP id NAA29334 for <seamoby@ietf.org>; Mon, 14 Jan 2002 13:37:16 -0700 (MST)]
Received: [from il75exm04.cig.mot.com ([136.182.110.113]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id NAA20235 for <seamoby@ietf.org>; Mon, 14 Jan 2002 13:37:15 -0700 (MST)]
Received: by IL75EXM04 with Internet Mail Service (5.5.2654.52) id <CGJJ5TN6>; Mon, 14 Jan 2002 14:37:15 -0600
Message-ID: <35DBB8B7AC89D4118E98009027B1009B0464FD50@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: 'Govind Krishnamurthi' <govs23@hotmail.com>, seamoby@ietf.org
Subject: RE: [Seamoby] Status of WG Last Call
Date: Mon, 14 Jan 2002 14:37:15 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
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

Govind, 
 you got it. But lets not get into "how much prior" right now :)

Madjid

-----Original Message-----
From: Govind Krishnamurthi [mailto:govs23@hotmail.com]
Sent: Friday, January 11, 2002 6:02 PM
To: seamoby@ietf.org
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