IETF Logo Mail Archive

Re: [Seamoby] Review Period Reminder

"James Kempf" <kempf@docomolabs-usa.com> Tue, 04 May 2004 16:55 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12453 for <seamoby-archive@odin.ietf.org>; Tue, 4 May 2004 12:55:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL3Ai-0002R9-7U for seamoby-archive@odin.ietf.org; Tue, 04 May 2004 12:53:32 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i44GrWf8009367 for seamoby-archive@odin.ietf.org; Tue, 4 May 2004 12:53:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL353-0000dU-ND for seamoby-web-archive@optimus.ietf.org; Tue, 04 May 2004 12:47:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12078 for <seamoby-web-archive@ietf.org>; Tue, 4 May 2004 12:47:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL352-0001uS-2o for seamoby-web-archive@ietf.org; Tue, 04 May 2004 12:47:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL346-0001px-00 for seamoby-web-archive@ietf.org; Tue, 04 May 2004 12:46:42 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BL33R-0001m3-00 for seamoby-web-archive@ietf.org; Tue, 04 May 2004 12:46:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL2wh-0006vr-AD; Tue, 04 May 2004 12:39:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL2qU-0004pr-7E for seamoby@optimus.ietf.org; Tue, 04 May 2004 12:32:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11602 for <seamoby@ietf.org>; Tue, 4 May 2004 12:32:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL2qS-0000iT-KY for seamoby@ietf.org; Tue, 04 May 2004 12:32:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL2pU-0000ba-00 for seamoby@ietf.org; Tue, 04 May 2004 12:31:36 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx with esmtp (Exim 4.12) id 1BL2oU-0000Rb-00 for seamoby@ietf.org; Tue, 04 May 2004 12:30:34 -0400
Message-ID: <004601c431f5$3379def0$366115ac@dcml.docomolabsusa.com>
From: James Kempf <kempf@docomolabs-usa.com>
To: john.loughney@nokia.com, seamoby@ietf.org
References: <DADF50F5EC506B41A0F375ABEB320636D44D2A@esebe023.ntc.nokia.com>
Subject: Re: [Seamoby] Review Period Reminder
Date: Tue, 04 May 2004 09:31:05 -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-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

John,

>1) Status of this memo section needs to be updated with new boilerplate.

OK. Where is this?

> 2) Abstract margins need fixing.

OK.

> 3) Needs IPR text

My understanding is that IPR text isn't needed unless there are IPR
considerations. As this document is purely instructions to IANA, there
aren't.

> 4) Is this a protocol document or a information document? If it is
>   info, then probably keywords (MUST; SHOULD; MAY, etc) shouldn't
>   be used.

I'll ask Allison. I've heard two stories on this, one that an informational
or experimental document may have such normative text and others that it
shouldn't. The doc is really just informational.

> 5) Section 5.2 - are these all of the possible L2

No, there are possibly more, which is why the registry is being established.
For example, 802.16 might be a possibility in the future. And there might be
others in the future. Was there something you thing needed changing here?

            jak





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

v2.23.0 | Report a Bug | By Email