Re: [Seamoby] Section 5.2 in CT Requirements

"James Kempf" <kempf@docomolabs-usa.com> Fri, 19 July 2002 13:08 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 JAA07332 for <seamoby-archive@odin.ietf.org>; Fri, 19 Jul 2002 09:08:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04343; Fri, 19 Jul 2002 09:07:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04314 for <seamoby@optimus.ietf.org>; Fri, 19 Jul 2002 09:06:59 -0400 (EDT)
Received: from fridge.docomolabs-usa.com (fwuser@key1.docomolabs-usa.com [216.98.102.225]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07287 for <seamoby@ietf.org>; Fri, 19 Jul 2002 09:06:01 -0400 (EDT)
Message-ID: <003501c22f24$eeac69c0$a86015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: "Pat R. Calhoun" <pcalhoun@bstormnetworks.com>, Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>, seamoby@ietf.org
Cc: mankin@psg.com
References: <35DBB8B7AC89D4118E98009027B1009B08AD55C5@IL27EXM10.cig.mot.com> <200207181459.03702.pcalhoun@bstormnetworks.com>
Subject: Re: [Seamoby] Section 5.2 in CT Requirements
Date: Fri, 19 Jul 2002 06:03:52 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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

Pat,

> I know that there was concern by the IESG on this very topic, and the idea of
> the above text was a compromise with the area director, who was going to
> initiate a discussion with the transport directorate. Unfortunately, this
> never occured, and the text remained. Allison had suggested that we continue
> with the non-transport discussions and that this topic will resurface again
> in the future.
>

I don't think Allison intended that the document go to the IESG with this text
in it, though I have not had an opportunity to speak with her about it. But
ultimately
she is not responsible for the working group documents, that is the
working group's responsiblity. We should have pulled that text out before we
sent it to the IESG, and, ideally, had something to replace it. If, at that
point, the IESG had a technical disagreement with our proposed requirement,
then we would have heard back.

> The question is whether this can occur after the document can be published
> (perhaps without the section).
>

I think we at least have to propose a requirement, which is what the text I sent
was intended to do.

            jak




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