Re: [Seamoby] Review Period Reminder

"James Kempf" <kempf@docomolabs-usa.com> Tue, 04 May 2004 18:15 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 OAA17132 for <seamoby-archive@odin.ietf.org>; Tue, 4 May 2004 14:15:07 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL4Nu-0002bq-Ta for seamoby-archive@odin.ietf.org; Tue, 04 May 2004 14:11:15 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i44IBEuY010026 for seamoby-archive@odin.ietf.org; Tue, 4 May 2004 14:11:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL4Bn-0006pr-Nf for seamoby-web-archive@optimus.ietf.org; Tue, 04 May 2004 13:58:43 -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 NAA16000 for <seamoby-web-archive@ietf.org>; Tue, 4 May 2004 13:58:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL4Bl-0001Kt-E8 for seamoby-web-archive@ietf.org; Tue, 04 May 2004 13:58:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL4Ap-0001Ep-00 for seamoby-web-archive@ietf.org; Tue, 04 May 2004 13:57:44 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BL49u-000191-00 for seamoby-web-archive@ietf.org; Tue, 04 May 2004 13:56:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL3zW-0001CO-R7; Tue, 04 May 2004 13:46:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL3xV-0000hb-2B for seamoby@optimus.ietf.org; Tue, 04 May 2004 13:43:57 -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 NAA15286 for <seamoby@ietf.org>; Tue, 4 May 2004 13:43:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL3xS-0007ek-RF for seamoby@ietf.org; Tue, 04 May 2004 13:43:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL3wl-0007Y6-00 for seamoby@ietf.org; Tue, 04 May 2004 13:43:11 -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 1BL3vj-0007Qk-00 for seamoby@ietf.org; Tue, 04 May 2004 13:42:07 -0400
Message-ID: <010201c431ff$356d3ef0$366115ac@dcml.docomolabsusa.com>
From: James Kempf <kempf@docomolabs-usa.com>
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
Cc: seamoby@ietf.org
References: <DADF50F5EC506B41A0F375ABEB320636D44D2A@esebe023.ntc.nokia.com> <004601c431f5$3379def0$366115ac@dcml.docomolabsusa.com> <4097D035.1E16C02E@iprg.nokia.com>
Subject: Re: [Seamoby] Review Period Reminder
Date: Tue, 04 May 2004 10:42:43 -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

Hi Charlie,

> > 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.
>
> I was under the very strong impression that the document was
> intended for publication as Experimental, and in that case
> it seems clear that the 2119 keywords SHOULD be used.
>

Well, I tend to agree, but I just want to confirm it with Allison.

> >      The Seamoby Working Group requests that IANA maintain allocations
for the
> >      port number and ICMP message type number for a minimum of 3 years
after
> >      which the allocations SHOULD be released, unless the Seamoby
protocols
> >      are advanced in some form to Proposed Standard.
>
> Is it a new policy that IANA would deallocate such assigned
> numbers?
>

Ted Hardie and Thomas Narten have a Discuss on CARD regarding the assignment
of permanent IANA resources (port numbers and ICMP types) to a protocol that
is experimental and may never get much market uptake. Using SCTP partially
addresses the comment (since SCTP ports are not as resource constrained and
we can utilize the PPIs to multiplex a single port for both protocols).
Having IANA maintain the allocations for a limited period of time addresses
the comment even further. I don't know if this has been done before, but I
passed the IANA draft by Allison and she seemed to think it was OK.

BTW, FMIP is considered to be in the same boat, according to my
conversations with Ted and Thomas about this, so those of us who are
involved in mipshop might want to be thinking about how to address this
problem there as well.

>
>
> I'll try to make further comments before Thursday, but
> I guess only small comments are requested.
>

Comments about replacement of text, including the suggested replacement, are
what is requested and indeed welcome.


            jak



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