Re: [Seamoby] Mobility Terminology Draft Ships!

Allison Mankin <mankin@psg.com> Thu, 12 February 2004 20:58 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 PAA15002 for <seamoby-archive@odin.ietf.org>; Thu, 12 Feb 2004 15:58:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArNu8-00051j-G0 for seamoby-archive@odin.ietf.org; Thu, 12 Feb 2004 15:57:48 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CKvmnd019317 for seamoby-archive@odin.ietf.org; Thu, 12 Feb 2004 15:57:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArNu8-00051U-BB for seamoby-web-archive@optimus.ietf.org; Thu, 12 Feb 2004 15:57:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14991 for <seamoby-web-archive@ietf.org>; Thu, 12 Feb 2004 15:57:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArNu4-0003Dj-00 for seamoby-web-archive@ietf.org; Thu, 12 Feb 2004 15:57:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArNt8-00035z-00 for seamoby-web-archive@ietf.org; Thu, 12 Feb 2004 15:56:47 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ArNsO-0002yL-00 for seamoby-web-archive@ietf.org; Thu, 12 Feb 2004 15:56:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArNsR-0004mJ-8j; Thu, 12 Feb 2004 15:56:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArNrs-0004Xv-E8 for seamoby@optimus.ietf.org; Thu, 12 Feb 2004 15:55:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14765 for <seamoby@ietf.org>; Thu, 12 Feb 2004 15:55:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArNrp-0002vw-00 for seamoby@ietf.org; Thu, 12 Feb 2004 15:55:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArNqv-0002pl-00 for seamoby@ietf.org; Thu, 12 Feb 2004 15:54:29 -0500
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1ArNq4-0002jz-00 for seamoby@ietf.org; Thu, 12 Feb 2004 15:53:36 -0500
Received: from localhost ([127.0.0.1] helo=psg.com) by psg.com with esmtp (Exim 4.30; FreeBSD) id 1ArNq3-000PeP-F9; Thu, 12 Feb 2004 20:53:35 +0000
To: Rajeev Koodli <rajeev@iprg.nokia.com>
cc: Jukka MJ Manner <jmanner@cs.Helsinki.FI>, James Kempf <kempf@docomolabs-usa.com>, Seamoby Working Group <seamoby@ietf.org>
Subject: Re: [Seamoby] Mobility Terminology Draft Ships!
In-Reply-To: Message from Rajeev Koodli <rajeev@iprg.nokia.com> of "Thu, 12 Feb 2004 12:04:32 PST." <402BDC50.E6C1B0CF@iprg.nokia.com>
Date: Thu, 12 Feb 2004 12:53:35 -0800
From: Allison Mankin <mankin@psg.com>
Message-Id: <E1ArNq4-0002jz-00@ietf-mx>
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.0 required=5.0 tests=AWL autolearn=no version=2.60

Rajeev and Jukka,

It's a great idea for anyone who has updates to the references
to send them to Jukka, as the Editor.  Jukka should save them
up, and when he does final edits with the RFC Editor later,
these fixes will be put in.  

It's not ok to do any revision on the i-d till then, so
one just hands on to the changes needed..  

About the expired i-ds, folks can suggest a related published 
paper, or take out the ref (with regrets), or revive it, if it's
actually a working group doc which shouldn't stay expired.

The reason WG i-ds are cited as Work in Progress is
that they're headed on to RFCs, so later they're going to
be findable as RFCs by their title, as long as all goes well.

Allison
Seamoby's Area Director

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