[Seamoby] Resolution of Issues with draft-ietf-seamoby-iana-00.txt
"James Kempf" <kempf@docomolabs-usa.com> Thu, 06 May 2004 22:05 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 SAA22718 for <seamoby-archive@odin.ietf.org>; Thu, 6 May 2004 18:05:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLqv5-0000V1-40 for seamoby-archive@odin.ietf.org; Thu, 06 May 2004 18:00:43 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46M0hG3001912 for seamoby-archive@odin.ietf.org; Thu, 6 May 2004 18:00:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLqsv-0007bl-3m for seamoby-web-archive@optimus.ietf.org; Thu, 06 May 2004 17:58:29 -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 RAA22006 for <seamoby-web-archive@ietf.org>; Thu, 6 May 2004 17:58:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLqss-0004dA-GF for seamoby-web-archive@ietf.org; Thu, 06 May 2004 17:58:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLqrq-0004CX-00 for seamoby-web-archive@ietf.org; Thu, 06 May 2004 17:57:23 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLqrF-0003kz-00 for seamoby-web-archive@ietf.org; Thu, 06 May 2004 17:56:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLqkj-00053z-3J; Thu, 06 May 2004 17:50:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLqgE-0003RE-PA for seamoby@optimus.ietf.org; Thu, 06 May 2004 17:45:22 -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 RAA21400 for <seamoby@ietf.org>; Thu, 6 May 2004 17:45:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLqgC-0006sk-8o for seamoby@ietf.org; Thu, 06 May 2004 17:45:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLqfG-0006S6-00 for seamoby@ietf.org; Thu, 06 May 2004 17:44:22 -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 1BLqeQ-000611-00 for seamoby@ietf.org; Thu, 06 May 2004 17:43:30 -0400
Message-ID: <019301c433b3$434192f0$366115ac@dcml.docomolabsusa.com>
From: James Kempf <kempf@docomolabs-usa.com>
To: seamoby@ietf.org
Date: Thu, 06 May 2004 14:44:07 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] Resolution of Issues with draft-ietf-seamoby-iana-00.txt
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
Folks,
I tried to create an issues page for draft-ietf-seamoby-iana-00.txt on Dan
Forsberg's Web site where the CTP issues page is, but all I got was a long
Python stack dump. :-(
Anyway, there aren't that many issues, and I hope we can resolve them
without an issues page. In addition to the editorial issues John Loughney
raised, there were three other issues that received some amount of comment:
1) Use of MUST, MAY, and SHOULD in the document
Suggested resolution: According to Allison, this is OK in an experimental
document, and she would like us to submit the IANA allocations document as
experimental, not informationl, along with the other two documents (CTP and
CARD). So the suggestion is that we keep it in.
2) Allocation of a context identifier for ROHC.
Suggested resolution: I have not received a reply from Allison on this, but
considering there is currently no RFC track document, either individual or
working group, to which one could point if someone actually wanted to
implement a ROHC context, I think we should wait. When such a document is
available, the authors can ask Allison for a Designated Expert to review the
request for a context identifier and have one assigned. If Allison feels
that assigning a context idenifier is OK in the absence of a specification,
she can recommend it during AD Review.
3) Sunset clause on IANA allocations is unusual.
Suggested resolution: This was in response to Ted Hardie and Thomas Narten's
Discuss comment on CARD, about using scarce IANA resources. If CTP and CARD
never achieve PS status, IANA must maintain the port and ICMP type
allocations even though the protocols never are widely used. The Sunset
clause allows IANA to widthdraw the allocation if CARD and CTP don't become
Proposed Standards within a 3 year time frame.
Unless there are any further commments, I will modify the IANA allocations
draft to reflect the comments as reflected on the list and the resolutions
suggested in this email.
jak
_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby