IETF Logo Mail Archive

RE: [Seamoby] Review Period Reminder

john.loughney@nokia.com Wed, 05 May 2004 04:05 UTC

Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20325 for <seamoby-archive@odin.ietf.org>; Wed, 5 May 2004 00:05:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLDcK-0007PD-DF for seamoby-archive@odin.ietf.org; Wed, 05 May 2004 00:02:45 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4542isY028467 for seamoby-archive@odin.ietf.org; Wed, 5 May 2004 00:02:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLDZ9-0006w8-AR for seamoby-web-archive@optimus.ietf.org; Tue, 04 May 2004 23:59:27 -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 XAA20004 for <seamoby-web-archive@ietf.org>; Tue, 4 May 2004 23:59:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLDZ7-0007go-3V for seamoby-web-archive@ietf.org; Tue, 04 May 2004 23:59:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLDY8-0007Wp-00 for seamoby-web-archive@ietf.org; Tue, 04 May 2004 23:58:25 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLDXh-0007N7-00 for seamoby-web-archive@ietf.org; Tue, 04 May 2004 23:57:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLDR1-0004yR-3Q; Tue, 04 May 2004 23:51:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLDOM-0004Fg-KA for seamoby@optimus.ietf.org; Tue, 04 May 2004 23:48:18 -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 XAA19457 for <seamoby@ietf.org>; Tue, 4 May 2004 23:48:15 -0400 (EDT)
From: john.loughney@nokia.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLDOK-00064C-Bv for seamoby@ietf.org; Tue, 04 May 2004 23:48:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLDNQ-0005vA-00 for seamoby@ietf.org; Tue, 04 May 2004 23:47:21 -0400
Received: from mgw-x2.nokia.com ([131.228.20.22]) by ietf-mx with esmtp (Exim 4.12) id 1BLDMi-0005m7-00 for seamoby@ietf.org; Tue, 04 May 2004 23:46:36 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159]) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i453kaH14984; Wed, 5 May 2004 06:46:36 +0300 (EET DST)
X-Scanned: Wed, 5 May 2004 06:46:01 +0300 Nokia Message Protector V1.3.30 2004040916 - RELEASE
Received: (from root@localhost) by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i453k1hk017329; Wed, 5 May 2004 06:46:01 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks004.ntc.nokia.com 004D6iO4; Wed, 05 May 2004 06:45:59 EEST
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i453jxH02649; Wed, 5 May 2004 06:45:59 +0300 (EET DST)
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 5 May 2004 06:45:57 +0300
x-mimeole: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Seamoby] Review Period Reminder
Date: Wed, 05 May 2004 06:45:57 +0300
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360143BDAB@esebe023.ntc.nokia.com>
Thread-Topic: [Seamoby] Review Period Reminder
Thread-Index: AcQx9Sc0/xweaI3gSC6t/hPOPCGZ+gAXdaLg
To: kempf@docomolabs-usa.com, seamoby@ietf.org
X-OriginalArrivalTime: 05 May 2004 03:45:57.0506 (UTC) FILETIME=[797BFE20:01C43253]
Content-Transfer-Encoding: quoted-printable
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.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi James,

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

These are related to these RFCs:

3667 IETF Rights in Contributions. S. Bradner. February 2004. (Format:
     TXT=43297 bytes) (Updates RFC2026) (Also BCP0078) (Status: BEST
     CURRENT PRACTICE)

3668 Intellectual Property Rights in IETF Technology. S. Bradner.
     February 2004. (Format: TXT=41365 bytes) (Updates RFC2026, RFC2028)
     (Also BCP0079) (Status: BEST CURRENT PRACTICE)

3669 Guidelines for Working Groups on Intellectual Property Issues. S.
     Brim. February 2004. (Format: TXT=40946 bytes) (Status:
     INFORMATIONAL)


http://www.rfc-editor.org/copyright.html


> > 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.

I understood, but I could be wrong, that all RFCs should have this kind of text:

ftp://ftp.rfc-editor.org/in-notes/rfc-editor/boilerplate.txt
 
> > 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.

OK.
 
> > 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?

Nothing specific, just wondering.

John

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

v2.23.0 | Report a Bug | By Email