RE: [Seamoby] Minutes of Meeting at IETF 52

George Tsirtsis <G.Tsirtsis@flarion.com> Fri, 04 January 2002 11:19 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 GAA00623 for <seamoby-archive@odin.ietf.org>; Fri, 4 Jan 2002 06:19:41 -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 GAA18617; Fri, 4 Jan 2002 06:08:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA18586 for <seamoby@optimus.ietf.org>; Fri, 4 Jan 2002 06:07:59 -0500 (EST)
Received: from RRMAIL01.RADIOROUTER_NT ([63.103.94.23]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00531 for <seamoby@ietf.org>; Fri, 4 Jan 2002 06:07:55 -0500 (EST)
Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2653.19) id <CFJBZAC8>; Fri, 4 Jan 2002 06:07:27 -0500
Message-ID: <8C92E23A3E87FB479988285F9E22BE465AB8D2@ftmail>
From: George Tsirtsis <G.Tsirtsis@flarion.com>
To: 'James Kempf' <kempf@docomolabs-usa.com>, seamoby@ietf.org
Subject: RE: [Seamoby] Minutes of Meeting at IETF 52
Date: Fri, 04 Jan 2002 06:07:16 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
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

James,

I do not care about the minutes. I pointed to what IMO needs to be changed
in the draft based on the discussion in the meeting.

George

-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Thursday, January 03, 2002 8:46 PM
To: George Tsirtsis; seamoby@ietf.org
Subject: Re: [Seamoby] Minutes of Meeting at IETF 52


George,

So are you proposing that the minutes be amended to
include a statement of what Section 4.13 refers to?

            jak
----- Original Message -----
From: "George Tsirtsis" <G.Tsirtsis@flarion.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>; <seamoby@ietf.org>
Sent: Thursday, January 03, 2002 12:42 PM
Subject: RE: [Seamoby] Minutes of Meeting at IETF 52


> James,
>
> >From the minutes....
>
> "Section 4.13 expanded greatly.
> Q: Is WILL NOT part of the standard terms?
> A: No, is SHOULD be a MUST NOT.
> Q: So if the CT solution verifies the CT info prior to transfer it is
NOT
> acceptable?
> A: We'll take that up on the mailing list."
>
> To remind you 4.13 is "4.13 The context transfer solution WILL NOT
verify
> the context information prior to transfer."
>
> The old "SHOULD" was clearly not acceptable. The new "MUST NOT"
suggestion
> was an obvious and a bit funny :-) mistake...As I pointed out long
time ago
> this requirement should just be removed...it just makes no sense....if
only
> it was the only one... ooops! I did not say that :-0
>
> George
>
>
> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Thursday, January 03, 2002 7:24 PM
> To: seamoby@ietf.org
> Subject: [Seamoby] Minutes of Meeting at IETF 52
>
>
> Attached. There is a one week comment period, ending on January 10.
>
>             jak
>

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