Re: Advancing IOTP-protocol, DSIG, and DOMHASH to Informational
Yoshiaki KAWATSURA <kawatura@bisd.hitachi.co.jp> Thu, 09 September 1999 05:48 UTC
Received: from one.eListX.com (one.elistx.com [209.116.252.130]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA13758 for <trade-archive@odin.ietf.org>; Thu, 9 Sep 1999 01:48:49 -0400 (EDT)
Received: from one.elistx.com by one.eListX.com id aa12281; 9 Sep 99 01:37 EDT
Received: from hitpro.hitachi.co.jp by one.eListX.com id aa12269; 9 Sep 99 01:37 EDT
Received: from bisdgw.bisd.hitachi.co.jp by hitpro.hitachi.co.jp (8.9.3/3.7W-hitpro) id OAA22443; Thu, 9 Sep 1999 14:38:59 +0900 (JST)
Received: from bisdmail.bisd.hitachi.co.jp by bisdgw.bisd.hitachi.co.jp (8.9.3+3.2W/3.7W-bisdgw) with ESMTP id OAA15281; Thu, 9 Sep 1999 14:38:59 +0900 (JST) (envelope-from kawatura@ecd.bisd.hitachi.co.jp)
Received: from localhost by bisdmail.bisd.hitachi.co.jp (8.9.3/3.7W-bisdmail) with ESMTP id OAA28709; Thu, 9 Sep 1999 14:38:58 +0900 (JST) (envelope-from kawatura@ecd.bisd.hitachi.co.jp)
Message-Id: <199909090538.OAA28709@bisdmail.bisd.hitachi.co.jp>
To: dee3@torque.pothole.com
Cc: ietf-trade@elistx.com
Cc: kawatura@bisd.hitachi.co.jp
Subject: Re: Advancing IOTP-protocol, DSIG, and DOMHASH to Informational
From: Yoshiaki KAWATSURA <kawatura@bisd.hitachi.co.jp>
In-Reply-To: Your message of "Thu, 09 Sep 1999 00:45:52 -0400" <199909090445.AAA10235@torque.pothole.com>
References: <199909090445.AAA10235@torque.pothole.com>
X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Thu, 09 Sep 1999 14:38:58 +0900
X-Dispatcher: imput version 980905(IM100)
Lines: 32
Sender: ietf-trade-owner@lists.eListX.com
Precedence: bulk
X-elistx: ietf-trade
Source-Info: From (or Sender) name not authenticated.
Content-Transfer-Encoding: 7bit
> Although there is still some discussion of minor details in the > iotp-v1.0-protocol-05 draft, there is a consensus to submit the IOTP > v1 protocol to the IESG for Informational along with the companion > IOTP DSIG draft. Since DSIG uses DOM HASH, that will need to be > advanced as well. There have been no recent comments on the DOM HASH > draft. I think that the level of changes being suggested for the > protocol draft can be handled in parallel with IESG consideration > (including IETF last call if the IESG thinks that is called for) > although, of course, the our AD might have a different . So, I have > requested their advancement. > > The exact drafts in question are > > draft-ietf-trade-iotp-v1.0-protocol-05.txt > draft-ietf-trade-iotp-v1.0-dsig-02.txt > draft-ietf-trade-hiroshi-dom-hash-02.txt Sounds good. I have some comment for DOMHASH to Kent Tamura-san, one of the author of DOMHASH. All of my comment is requests for clarification of the draft, there is no technical change request and he mentioned some points will be clarified sooner. ---- Yoshiaki Kawatsura : E-mail kawatura@bisd.hitachi.co.jp Business & Information Systems Development Division, Hitachi,Ltd. Voice: +81-44-549-1713(direct) Fax: +81-44-549-1721 ----------------------------------------------------------------------- Message addressed to: ietf-trade@lists.elistx.com Archive available at: http://www.elistx.com/archives/ietf-trade/ To (un)subscribe send a message with "subscribe" or "unsubscribe" in the body to: ietf-trade-request@lists.elistx.com
- Re: Advancing IOTP-protocol, DSIG, and DOMHASH to… Patrik Fältström
- Re: Advancing IOTP-protocol, DSIG, and DOMHASH to… Yoshiaki KAWATSURA
- Advancing IOTP-protocol, DSIG, and DOMHASH to Inf… Donald E. Eastlake 3rd