RE: IESG commet on draft-ietf-trade-iotp-v1.0-papi-05/06

Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com> Wed, 24 March 2004 21:34 UTC

Return-Path: <ietf-trade-errors@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856) id <0HV300G02NY4OK@elistx.com> (original mail from Donald.Eastlake@motorola.com); Wed, 24 Mar 2004 16:34:52 -0500 (EST)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856) id <0HV300G01NY4OJ@elistx.com> for ietf-trade@lists.elistx.com; Wed, 24 Mar 2004 16:34:52 -0500 (EST)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100]) by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0HV300F47NY3O1@elistx.com> for ietf-trade@lists.elistx.com; Wed, 24 Mar 2004 16:34:51 -0500 (EST)
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by motgate.mot.com (Motorola/Motgate) with ESMTP id i2OLYfj8020788 for <ietf-trade@lists.elistx.com>; Wed, 24 Mar 2004 14:34:41 -0700 (MST)
Received: from ma19exm01.e6.bcs.mot.com (ma19exm01.e6.bcs.mot.com [10.14.33.5]) by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id i2OLYEdl030294 for <ietf-trade@lists.elistx.com>; Wed, 24 Mar 2004 15:34:18 -0600
Received: by ma19exm01.e6.bcs.mot.com with Internet Mail Service (5.5.2657.2) id <F561Y6XQ>; Wed, 24 Mar 2004 16:34:21 -0500
Content-return: allowed
Date: Wed, 24 Mar 2004 16:34:21 -0500
From: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
Subject: RE: IESG commet on draft-ietf-trade-iotp-v1.0-papi-05/06
To: 'Masaaki Hiroya' <hiroya@st.rim.or.jp>
Cc: ykawatsu@itg.hitachi.co.jp, ietf-trade@lists.elistx.com
Message-id: <62173B970AE0A044AED8723C3BCF23810408B34A@ma19exm01.e6.bcs.mot.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.2)
Content-type: text/plain
List-Owner: <mailto:ietf-trade-help@lists.elistx.com>
List-Post: <mailto:ietf-trade@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>, <mailto:ietf-trade-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>, <mailto:ietf-trade-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-trade/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-trade-request@lists.elistx.com?body=help>
List-Id: <ietf-trade.lists.elistx.com>

Hi,

Yes, those looks like exactly the right changes. I will post the draft and notify our new area director, Scott Hollenbeck. We will see if there are any other objections but I hope that with this change it can be approved quickly.

Thanks,
Donald
===========================================================
 Donald E. Eastlake III       Donald.Eastlake@Motorola.com
 Motorola Laboratories               1-508-786-7554 (work)
 111 Locke Drive                     1-508-634-2066 (home)
 Marlboro, MA 01752 USA

-----Original Message-----
From: Masaaki Hiroya [mailto:hiroya@st.rim.or.jp] 
Sent: Tuesday, March 23, 2004 9:23 PM
To: Eastlake III Donald-LDE008
Cc: ykawatsu@itg.hitachi.co.jp; hiroya@st.rim.or.jp
Subject: Re: IESG commet on draft-ietf-trade-iotp-v1.0-papi-05

Hello Mr. Eastlake

I'm not sure how I should respond to the IESG comment on I-D draft,
but I attached the updated version of I-D draft.

The updated parts are as follows:

(OLD)(draft-ietf-trade-iotp-v1.0-papi-05)
    MerchantData        Any merchant related data that might be
                        used by the IOTP Payment Bridge for
                        different purposes, e.g., it might
                        contain access keys to some mall keys.
                                       ~~~~~~~~~~~~~~~~~~~~~~~
                        Its declaration coincides with the
                        Packaged Content's declaration (cf. IOTP
                        Specification).

(NEW)(draft-ietf-trade-iotp-v1.0-papi-06)
    MerchantData        Any merchant related data that might be
                        used by the IOTP Payment Bridge for
                        different purposes, e.g., it might
                        contain IDs to access some mall data,
                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                        but not cryptographic keys. Its Packaged
                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                        declaration coincides with the Content's
                        declaration (cf. IOTP Specification).

I think this correction covers the IESG comment.

Besides, I updated the Author's Address section as follows:

(OLD)
         Yoshiaki Kawatsura
         Hitachi, Ltd.
         890 Kashimada Saiwai-ku Kawasaki-shi
         Kanagawa, Japan 212-8567
         E-mail: kawatura@bisd.hitachi.co.jp
(NEW)
         Yoshiaki Kawatsura
         Hitachi, Ltd.
         890 Kashimada Saiwai-ku Kawasaki-shi
         Kanagawa, Japan 212-8567
         E-mail: ykawatsu@itg.hitachi.co.jp
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~

(OLD)
         Masaaki Hiroya
         Technoinfo Service, Inc.
         1155-6-206 Ichigao-cho
         Aoba-ku, Yokohama
         Kanagawa 225-0024 JAPAN
         Phone: +81-45-978-4522
         Email: hiroya@st.rim.or.jp
(NEW)
         Masaaki Hiroya
         Technoinfo Service, Inc.
         333-2-718 Uchikoshi-machi
         ~~~~~~~~~~~~~~~~~~~~~~~~~~
         Hachioji-shi
         ~~~~~~~~~~~~
         Tokyo 192-0911 JAPAN
         ~~~~~~~~~~~~~~~~~~~~
         Email: hiroya@st.rim.or.jp


If there is something else I should do, please let me know.

Best Regards
Masaaki


At 04/03/16 14:06, Eastlake III Donald-LDE008 wrote:
 >The IESG has provided the following comment on
 >       draft-ietf-trade-iotp-v1.0-papi-05
 >
 >"The use of MerchantData makes me nervous.  The level of abstraction makes
 >it difficult to tell, but I think that MerchantData can contain plaintext
 >cryptographic keys, which would be very poor design."
 >
 >We need to respond to this comment.


-----
Masaaki Hiroya
hiroya@st.rim.or.jp