SKREDDY@us.oraclec.om

------=_NextPart_000_003D_01BD5CF3.D830B140-- ----------------------------------------------------------------------- Message addressed to: ietf-iotp@lists.elistx.com Archive available at: http://www.elistx.com/archives/ietf-iotp/ Return-Path: ietf-iotp-owner@one.eListX.com Received: from one.eListX.com (one.elistx.com [209.116.252.130]) by ietf.org (8.8.5/8.8.7a) with SMTP id AAA07957 for ; Tue, 31 Mar 1998 21:53:54 -0800 (PST) Received: from renown.concentric.net by one.eListX.com id aa07004; 1 Apr 98 00:51 EST Received: from memphis (ts016d32.cup-ca.concentric.net [209.31.13.44]) by renown.concentric.net (8.8.5/) id AAA13185; Wed, 1 Apr 1998 00:51:19 -0500 (EST) [ConcentricHost SMTP Relay] Message-ID: <001201bd5d32$8f199b90$97ec1990@memphis.us.oracle.com> From: "S.Reddy Virtual Office" To: ietf-iotp@one.eListX.com MMDF-Warning: Parse error in original version of preceding line at one.eListX.com Cc: Donald Eastlake , skreddy@us.oracle.com, Steve Fabes MMDF-Warning: Parse error in original version of preceding line at one.eListX.com Subject: Minutes of Internet Open Trading Protocol BOF Date: Tue, 31 Mar 1998 21:53:54 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000F_01BD5CEF.7F8DCAE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: ietf-iotp-owner@lists.eListX.com Precedence: bulk X-elistx: ietf-iotp Source-Info: From (or Sender) name not authenticated. This is a multi-part message in MIME format. ------=_NextPart_000_000F_01BD5CEF.7F8DCAE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Don, Here is the minutes of the Internet Open Trading Protocol BOF. I have = retained the flow of the discussions in the same order.Let me know if I missed anything. Surendra --- Surendra K Reddy Oracle Corp., (650) 506 5441 skreddy@us.oracle.com Internet Open Trading Protocol BOF (iotp) Tuesday, March 31 at 1545-1645 Minutes of the Meeting Compiled By : Surendra Reddy ( skreddy@us.oracle.com ) Members Present: See IETF IOTF BOF Attendees List Chair: Donald E. Eastlake 3rd (1). Don started the BOF meeting explaining the main intent as to assess = the interest of participants=20 in forming a working group to develop an internet based trading = protocol based on exisiting OTP specification which is being developed by OTP consortium. (2). Then he made a presentation on overview of existing OTP standard (3). Following issues were raised during Don's OTP overview = presentation: (a). What is the scope of the IOTP working Group? Is this = working group is going to mandate in defining the business problem, requirements document? (b). Existing payment systems and its interoperability - Scope = of the payment protocol? How does it differ from EDI?Are there any overlap among = OFX(Open Financila Exchange), EDI (c). How does it relate to SET? (d). Does a concept of auctioneer is required or not? (e). Mechanisms for transporting trading objects - mandate at = least web and email mechanisms? (f). Some of the participants expressed their concern on the = scope and work items of this group? (g). OTP should at least support Electronic Funds Transfer, = Checks and Credit Cards? This throws the question of what need to be there in OTP and what need not be should = be clearly defined upfront. Otherwise, we land up in rate holes. Participants repeatedly indicated the need for = Requirements document. (h). Participants expressed confusion about whether the OTP is a = transport protocol or XML schema. If it is just XML schema representations, participants felt that IETF is not = the right forum to address schema. Don Clarified that OTP is protocol and XML schema. Hence putting under IETF = makes more sense. (i). Participants raised questions on why OTP consortium wanted = to transfer it to IETF, which doesnot have domain expertise in trading related issues? Various participants = discussed this issue and explained that combining the trading expertise of OTP consortium and protocol design expertise = of IETF, we can design a high quality protocol. 3. Then Don presented working group charter as follows: The Internet Open Trading Protocol provides an interoperable framework = for Internet commerce. It is payment system=20 independent and able tohandle cases where such roles as the merchant, = the payment received,the deliverer of goods=20 or services, and the provider of customer support are performed by = different parties or the party. The Internet Open Trading Protocol working group will republish the = existing Baseline Internet OTP (version 1.0) protocol=20 specification as an Informational RFC and develope IOTP version 2.0. Selection of items for inclusion in v2.0 is expected to be from the = following and others suggested by the Working Group: - Dynamic Definition of Trading Sequences - Multiple Protocol Options - Offer Request Block - Public Key Signatures (v1.0 uses secret key signatures) - Signatures on the Delivery Response - Improved Problem Resolution (extend to cover presentation of signed = receipt to customer support party, etc.) - Selection of Additional Options - Shorter Element and Attribute Names - Transaction Status Inquiry - OTP Architecture (informational development of standard interfaces to = software components). - Mapping OTP Messages to other Transport Layers Following issues are raised on the Working Group Charter: (a). Requirements document should be part of the working group work = items (b). Participants expressed concerns about OTP releasing current = document as informational RFC - confuse it will create among the current users of this protocol? 4. Finally, Don presented the Working Group goals and milestones as = follows: Goals and Milestones: 1.A Publication of IOTP v1.0 as an internet draft, WG formation + 2 = months. 1.B Publication of IOTP v1.0 as an Informational RFC, 1.A + 1 month. 2.A IOTP v2.0 requirements document initial release as an internet = draft, WG formation + 2 months. 2.B IOTP v2.0 requirements document as an Informational RFC. 2.A + 2 = months. 3.A IOTP v2.0 specification initial release as an internet draft, WG = formation + 4 months. 3.B IOTP v2.0 specification as a Proposed Standard RFC, 3.A + 3 months. Following comments are made on the milestones and goals: (a). Overall schedule looks acceptable. 5. Following are the Open Issues that need to be addressed? 1. Why IETF is choosen a place for reviewing the OTP protocol against = consortium. Trading experts from=20 consortium and draw experts from IETF.?It is appropriate for IETF to = get involve in it? 2. Interleaving financial technology and networking -- commitment from = consortium members and their commitment to make this working group successful. 3. Expressed concerns on scope of the working group - infinitely = expanding charters - not having requirement documents=20 will throw working group into rat holes. 4. Does the corsortium has agreed to hand over to IETF and whether = members are committed to participate in this effort?=20 Whether or not issuing informational RFC confuse the market? 5. Whether to publish some documents as informational or continue = working on taking to the standards? 6. define and agreed on goals for 2.0 and start working on them. 7. Are there any current reference implementations of OTP? Finally, Applications AD(Harald Alvestrand) asked the participants = whether they felt the need for such a working group or not? Majority of = the aparticipants supported forming Working Group. Application AD also asked = participants commitment in working on this working group. Reasonably good number of people expressed their intent = to work on this working group. ------=_NextPart_000_000F_01BD5CEF.7F8DCAE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Don,

Here = is the=20 minutes of the Internet Open Trading Protocol BOF. I have retained the = flow of=20 the discussions in the
same order.Let me know if I missed = anything.

Surendra
---

Surendra K Reddy
Oracle Corp.,
(650) 506 5441
skreddy@us.oracle.com

Internet = Open Trading=20 Protocol BOF (iotp)
Tuesday, March 31 at 1545-1645

Minutes of = the=20 Meeting

Compiled By = : Surendra=20 Reddy ( skreddy@us.oracle.com=20 )

Members = Present: See IETF=20 IOTF BOF Attendees List

Chair: = Donald E. Eastlake=20 3rd <dee@cybercash.com>

(1). Don = started the BOF=20 meeting explaining the main intent as to assess the interest of = participants=20
in forming a working group to develop = an=20 internet based trading protocol based on exisiting OTP specification = which is=20 being
developed by OTP = consortium.

(2). Then = he made a=20 presentation on overview of existing OTP standard

(3). = Following issues=20 were raised during Don's OTP overview presentation:

(a). What is = the scope=20 of the IOTP working Group? Is this working group is going to mandate in = defining=20 the business=20 problem,
&= nbsp; =20 requirements document?

(b). Existing = payment=20 systems and its interoperability - Scope of the payment=20 protocol?
= =20 How does it differ from EDI?Are there any overlap among OFX(Open = Financila=20 Exchange), EDI

(c). How does = it relate=20 to SET?

(d). Does a = concept=20 of auctioneer is required or not?

(e). = Mechanisms for=20 transporting trading objects - mandate at least web and email=20 mechanisms?

(f). Some of = the=20 participants expressed their concern on the scope and work items of this = group?

        (g). OTP should at = least=20 support Electronic Funds Transfer, Checks and Credit Cards? This throws = the=20 question=20 of
           &= nbsp; =20 what need to be there in OTP and what need not be should be clearly = defined=20 upfront. Otherwise, we land up=20 in
           &= nbsp; =20 rate holes. Participants repeatedly indicated the need for Requirements=20 document.

        (h). Participants = expressed=20 confusion about whether the OTP is a transport protocol or XML schema. = If it is=20 just=20 XML
           =   =20 schema representations, participants felt that IETF is not the right = forum to=20 address schema. Don Clarified=20 that
           = ;  =20 OTP is protocol and XML schema. Hence putting under IETF makes more=20 sense.

        (i). Participants = raised=20 questions on why OTP consortium wanted to transfer it to IETF, which = doesnot=20 have=20 domain
          &nb= sp; =20 expertise in trading related issues? Various participants discussed this = issue=20 and explained that combining the=20 trading
          &n= bsp; =20 expertise of OTP consortium and protocol design expertise of IETF, we = can design=20 a high quality protocol.

3. Then Don = presented=20 working group charter as follows:

The = Internet Open Trading=20 Protocol provides an interoperable framework for Internet commerce. It = is=20 payment system
independent and able tohandle cases where such roles = as the=20 merchant, the payment received,the deliverer of goods
or services, = and the=20 provider of customer support are performed by different parties or the=20 party.

The = Internet Open Trading=20 Protocol working group will republish the existing Baseline Internet OTP = (version 1.0) protocol
specification as an Informational RFC and = develope=20 IOTP version 2.0.

Selection = of items for=20 inclusion in v2.0 is expected to be from the following and others = suggested by=20 the Working Group:

- Dynamic = Definition of=20 Trading Sequences
- Multiple Protocol Options
- Offer Request = Block
-=20 Public Key Signatures (v1.0 uses secret key signatures)
- Signatures = on the=20 Delivery Response
- Improved Problem Resolution (extend to cover = presentation=20 of signed receipt to customer support party, etc.)
- Selection of = Additional=20 Options
- Shorter Element and Attribute Names
- Transaction Status = Inquiry
- OTP Architecture (informational development of standard = interfaces=20 to software components).
- Mapping OTP Messages to other Transport=20 Layers

Following = issues are=20 raised on the Working Group Charter:

(a). =20 Requirements document should be part of the working group work = items

(b). =20 Participants expressed concerns about OTP releasing current document as=20 informational RFC - confuse it will=20 create
among the current = users of=20 this protocol?

4. Finally, = Don presented=20 the Working Group goals and milestones as follows:

Goals and=20 Milestones:

1.A = Publication of IOTP=20 v1.0 as an internet draft, WG formation + 2 months.

1.B = Publication of IOTP=20 v1.0 as an Informational RFC, 1.A + 1 month.

2.A IOTP = v2.0=20 requirements document initial release as an internet draft, WG formation = + 2=20 months.

2.B IOTP = v2.0=20 requirements document as an Informational RFC. 2.A + 2 = months.

3.A IOTP = v2.0=20 specification initial release as an internet draft, WG formation + 4=20 months.

3.B IOTP = v2.0=20 specification as a Proposed Standard RFC, 3.A + 3 months.

Following = comments are=20 made on the milestones and goals:

(a). = Overall schedule=20 looks acceptable.

5. = Following are the Open=20 Issues that need to be addressed?

1. Why IETF = is choosen a=20 place for reviewing the OTP protocol against consortium. Trading experts = from=20
consortium and draw experts from IETF.?It is = appropriate=20 for IETF to get involve in it?

2. = Interleaving financial=20 technology and networking -- commitment from consortium members and = their=20 commitment
to make this working group=20 successful.

3. = Expressed concerns on=20 scope of the working group - infinitely expanding charters - not having=20 requirement documents
will throw working group = into rat=20 holes.

4. Does the = corsortium=20 has agreed to hand over to IETF and whether members are committed = to=20 participate in this effort?
Whether or not = issuing=20 informational RFC confuse the market?

5. Whether = to publish=20 some documents as informational or continue working on taking to the=20 standards?

6. define = and agreed on=20 goals for 2.0 and start working on them.

7. Are = there any current=20 reference implementations of OTP?

Finally, = Applications=20 AD(Harald = Alvestrand) =20 asked the participants whether they felt the need for such a working = group or=20 not? Majority of the
aparticipants supported forming Working Group.=20 Application AD also asked participants commitment in working on = this
working=20 group. Reasonably good number of people expressed their intent to work = on this=20 working group.

------=_NextPart_000_000F_01BD5CEF.7F8DCAE0-- ----------------------------------------------------------------------- Message addressed to: ietf-iotp@lists.elistx.com Archive available at: http://www.elistx.com/archives/ietf-iotp/ Return-Path: ietf-iotp-owner@one.eListX.com Received: from one.eListX.com (one.elistx.com [209.116.252.130]) by ietf.org (8.8.5/8.8.7a) with SMTP id AAA07957 for ; Fri, 27 Mar 1998 17:36:37 -0500 (EST) Received: from callandor.cybercash.com by one.eListX.com id aa03365; 27 Mar 98 17:33 EST Received: by callandor.cybercash.com; id RAA12786; Fri, 27 Mar 1998 17:36:24 -0500 Received: from cybercash.com(204.149.68.52) by callandor.cybercash.com via smap (3.2) id xma012753; Fri, 27 Mar 98 17:36:10 -0500 Received: (from dee@localhost) by cybercash.com (SMTP GateWay 2.0) id RAA08610; Fri, 27 Mar 1998 17:36:38 -0500 (EST) Date: Fri, 27 Mar 1998 17:36:37 -0500 (EST) From: "Donald E. Eastlake 3rd" To: Scott Huddle cc: ietf@ns.ietf.org, ietf-iotp@lists.eListX.com Subject: Re: Internet Open Trading Protocol BoF In-Reply-To: <199803272122.QAA00563@new6.Reston.mci.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ietf-iotp-owner@lists.eListX.com Precedence: bulk X-elistx: ietf-iotp Source-Info: From (or Sender) name not authenticated. Your message is misleading in giving the impression that the current version of the protocol is not freely down loadable by anyone. It is. For a variety of reasons from the accidents of their history to a perceived need to meet a tight schedule, it is not uncommon for a protocol to be initially developed in a more closed group and later transfered to a more open one. In some ways, that is what a design team does in an IETF working group. The Open Trading Protocol Consortium could be considered a design team writ large. What is being considered is to transfer change control and any right in the protocol to the IETF and place the further development of the protocol under the IETF standards process. I think this would be a good thing but it remains to be decided. Perhaps you can come to the BoF or read the available material and contribute to that decision. Donald On Fri, 27 Mar 1998, Scott Huddle wrote: > Date: Fri, 27 Mar 1998 16:22:26 -0500 > From: Scott Huddle > To: ietf@ns.ietf.org, dee@Cybercash.COM > Cc: ietf-iotp@lists.eListX.com > Subject: Re: Internet Open Trading Protocol BoF > > OK, I'll bite. Why is an open trading protocol forum (documents > and email) limited to members of the OTP consortium? > > -scott > > > From cclark@ns.ietf.org Fri Mar 27 14:17 EST 1998 > > Date: Fri, 27 Mar 1998 13:58:08 -0500 (EST) > > From: "Donald E. Eastlake 3rd" > > To: ietf@ns.ietf.org > > cc: ietf-iotp@lists.eListX.com > > Subject: Internet Open Trading Protocol BoF > > MIME-Version: 1.0 > > Content-Type> : > TEXT/PLAIN> ; > charset=US-ASCII> > > Content-Length: 774 > > > > There will be a BoF Tuesday afternoon 15:45-16:45 at the IETF meeting next > > week to discuss the possibility of forming a working group to continue > > development of the Internet Open Trading Protocol. For draft agenda, see > > , for draft charter, see > > , for the current > > state of the protocol, see . > > > > Donald > > ===================================================================== > > Donald E. Eastlake 3rd +1 978-287-4877(tel) dee@cybercash.com > > 318 Acton Street +1 978-371-7148(fax) dee@world.std.com > > Carlisle, MA 01741 USA +1 703-620-4200(main office, Reston, VA) > > http://www.cybercash.com http://www.privacy.org/ipc > > > > > > ===================================================================== Donald E. Eastlake 3rd +1 978-287-4877(tel) dee@cybercash.com 318 Acton Street +1 978-371-7148(fax) dee@world.std.com Carlisle, MA 01741 USA +1 703-620-4200(main office, Reston, VA) http://www.cybercash.com http://www.privacy.org/ipc ----------------------------------------------------------------------- Message addressed to: ietf-iotp@lists.elistx.com Archive available at: http://www.elistx.com/archives/ietf-iotp/ Return-Path: ietf-iotp-owner@one.eListX.com Received: from one.eListX.com (one.elistx.com [209.116.252.130]) by ietf.org (8.8.5/8.8.7a) with SMTP id AAA07957 for ; Fri, 27 Mar 1998 16:22:26 -0500 (EST) Received: from new6.reston.mci.net by one.eListX.com id aa02416; 27 Mar 98 16:23 EST Received: (from huddle@localhost) by new6.Reston.mci.net (8.6.12/8.6.6) id QAA00563; Fri, 27 Mar 1998 16:22:26 -0500 Date: Fri, 27 Mar 1998 16:22:26 -0500 From: Scott Huddle Message-Id: <199803272122.QAA00563@new6.Reston.mci.net> To: ietf@ns.ietf.org, dee@cybercash.com Subject: Re: Internet Open Trading Protocol BoF Cc: ietf-iotp@lists.eListX.com Sender: ietf-iotp-owner@lists.eListX.com Precedence: bulk X-elistx: ietf-iotp Source-Info: From (or Sender) name not authenticated. OK, I'll bite. Why is an open trading protocol forum (documents and email) limited to members of the OTP consortium? -scott > From cclark@ns.ietf.org Fri Mar 27 14:17 EST 1998 > Date: Fri, 27 Mar 1998 13:58:08 -0500 (EST) > From: "Donald E. Eastlake 3rd" > To: ietf@ns.ietf.org > cc: ietf-iotp@lists.eListX.com > Subject: Internet Open Trading Protocol BoF > MIME-Version: 1.0 > Content-Type> : > TEXT/PLAIN> ; > charset=US-ASCII> > Content-Length: 774 > > There will be a BoF Tuesday afternoon 15:45-16:45 at the IETF meeting next > week to discuss the possibility of forming a working group to continue > development of the Internet Open Trading Protocol. For draft agenda, see > , for draft charter, see > , for the current > state of the protocol, see . > > Donald > ===================================================================== > Donald E. Eastlake 3rd +1 978-287-4877(tel) dee@cybercash.com > 318 Acton Street +1 978-371-7148(fax) dee@world.std.com > Carlisle, MA 01741 USA +1 703-620-4200(main office, Reston, VA) > http://www.cybercash.com http://www.privacy.org/ipc > > ----------------------------------------------------------------------- Message addressed to: ietf-iotp@lists.elistx.com Archive available at: http://www.elistx.com/archives/ietf-iotp/ Return-Path: ietf-iotp-owner@one.eListX.com Received: from one.eListX.com (one.elistx.com [209.116.252.130]) by ietf.org (8.8.5/8.8.7a) with SMTP id AAA07957 for ; Fri, 27 Mar 1998 14:21:00 -0500 (EST) Received: from callandor.cybercash.com by one.eListX.com id aa00640; 27 Mar 98 14:17 EST Received: by callandor.cybercash.com; id OAA22296; Fri, 27 Mar 1998 14:20:36 -0500 Received: from cybercash.com(204.149.68.52) by callandor.cybercash.com via smap (3.2) id xma022282; Fri, 27 Mar 98 14:20:34 -0500 Received: (from dee@localhost) by cybercash.com (SMTP GateWay 2.0) id OAA02159; Fri, 27 Mar 1998 14:21:01 -0500 (EST) Date: Fri, 27 Mar 1998 14:21:00 -0500 (EST) From: "Donald E. Eastlake 3rd" To: Terry Allen cc: ietf-iotp@lists.eListX.com Subject: Re: Internet Open Trading Protocol BoF In-Reply-To: <199803271904.LAA18603@bolt.sonic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ietf-iotp-owner@lists.eListX.com Precedence: bulk X-elistx: ietf-iotp Source-Info: From (or Sender) name not authenticated. OK, Thanks for your support. Donald On Fri, 27 Mar 1998, Terry Allen wrote: > Date: Fri, 27 Mar 1998 11:04:56 -0800 > From: Terry Allen > To: ietf-iotp@lists.eListX.com > Subject: Re: Internet Open Trading Protocol BoF > > > I regret I won't be able to attend the BOF, but I am very > interested in seeing a working group formed for the purpose > described. > > Regards, > > > Terry Allen Veo Systems, Inc. > Business Language Designer 4005 Miranda Ave., no. 150 > (Common Business Language - CBL) Palo Alto, 94034 > terry.allen[at]veosystems.com http://www.veosystems.com/ > > ----------------------------------------------------------------------- > Message addressed to: ietf-iotp@lists.elistx.com > Archive available at: http://www.elistx.com/archives/ietf-iotp/ > ===================================================================== Donald E. Eastlake 3rd +1 978-287-4877(tel) dee@cybercash.com 318 Acton Street +1 978-371-7148(fax) dee@world.std.com Carlisle, MA 01741 USA +1 703-620-4200(main office, Reston, VA) http://www.cybercash.com http://www.privacy.org/ipc ----------------------------------------------------------------------- Message addressed to: ietf-iotp@lists.elistx.com Archive available at: http://www.elistx.com/archives/ietf-iotp/ Return-Path: ietf-iotp-owner@one.eListX.com Received: from one.eListX.com (one.elistx.com [209.116.252.130]) by ietf.org (8.8.5/8.8.7a) with SMTP id AAA07957 for ; Fri, 27 Mar 1998 13:58:08 -0500 (EST) Received: from callandor.cybercash.com by one.eListX.com id aa00522; 27 Mar 98 13:54 EST Received: by callandor.cybercash.com; id NAA19566; Fri, 27 Mar 1998 13:57:51 -0500 Received: from cybercash.com(204.149.68.52) by callandor.cybercash.com via smap (3.2) id xma019549; Fri, 27 Mar 98 13:57:42 -0500 Received: (from dee@localhost) by cybercash.com (SMTP GateWay 2.0) id NAA01257; Fri, 27 Mar 1998 13:58:09 -0500 (EST) Date: Fri, 27 Mar 1998 13:58:08 -0500 (EST) From: "Donald E. Eastlake 3rd" To: ietf@ietf.org cc: ietf-iotp@lists.eListX.com Subject: Internet Open Trading Protocol BoF Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ietf-iotp-owner@lists.eListX.com Precedence: bulk X-elistx: ietf-iotp Source-Info: From (or Sender) name not authenticated. There will be a BoF Tuesday afternoon 15:45-16:45 at the IETF meeting next week to discuss the possibility of forming a working group to continue development of the Internet Open Trading Protocol. For draft agenda, see , for draft charter, see , for the current state of the protocol, see . Donald ===================================================================== Donald E. Eastlake 3rd +1 978-287-4877(tel) dee@cybercash.com 318 Acton Street +1 978-371-7148(fax) dee@world.std.com Carlisle, MA 01741 USA +1 703-620-4200(main office, Reston, VA) http://www.cybercash.com http://www.privacy.org/ipc ----------------------------------------------------------------------- Message addressed to: ietf-iotp@lists.elistx.com Archive available at: http://www.elistx.com/archives/ietf-iotp/ Return-Path: ietf-iotp-owner@one.eListX.com Received: from one.eListX.com (one.elistx.com [209.116.252.130]) by ietf.org (8.8.5/8.8.7a) with SMTP id AAA07957 for ; Fri, 27 Mar 1998 11:08:15 -0500 (EST) Received: from europe.std.com by one.eListX.com id aa28942; 27 Mar 98 11:07 EST Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id LAA16868; Fri, 27 Mar 1998 11:08:09 -0500 (EST) Received: by world.std.com (TheWorld/Spike-2.0) id AA14966; Fri, 27 Mar 1998 11:08:15 -0500 Message-Id: <199803271608.AA14966@world.std.com> To: ietf-iotp@lists.eListX.com Cc: dee@world.std.com Subject: test Date: Fri, 27 Mar 1998 11:08:15 -0500 From: "Donald E. Eastlake 3rd" Sender: ietf-iotp-owner@lists.eListX.com Precedence: bulk X-elistx: ietf-iotp Source-Info: From (or Sender) name not authenticated. subscribe end ===================================================================== Donald E. Eastlake, III 1-978-287-4877(w&h) dee@cybercash.com 318 Acton Street 1-978-371-7148(fax) dee@world.std.com Carlisle, MA 01741 USA ----------------------------------------------------------------------- Message addressed to: ietf-iotp@lists.elistx.com Archive available at: http://www.elistx.com/archives/ietf-iotp/ Return-Path: ietf-iotp-owner@one.eListX.com Received: from one.eListX.com (one.elistx.com [209.116.252.130]) by ietf.org (8.8.5/8.8.7a) with SMTP id AAA07957 for ; Fri, 27 Mar 1998 11:04:56 -0800 (PST) Received: from marine.sonic.net by one.eListX.com id aa00576; 27 Mar 98 14:02 EST Received: (qmail 2174 invoked from network); 27 Mar 1998 19:05:16 -0000 Received: from unknown (HELO sub.sonic.net) (root@208.201.224.8) by marine.sonic.net with SMTP; 27 Mar 1998 19:05:16 -0000 Received: from bolt.sonic.net (tallen@bolt [208.201.224.36]) by sub.sonic.net (8.8.8/8.8.5) with ESMTP id LAA02633 for ; Fri, 27 Mar 1998 11:02:56 -0800 X-envelope-info: Received: (from tallen@localhost) by bolt.sonic.net (8.8.8/8.7.3) id LAA18603 for ietf-iotp@lists.eListX.com; Fri, 27 Mar 1998 11:04:56 -0800 Date: Fri, 27 Mar 1998 11:04:56 -0800 From: Terry Allen Message-Id: <199803271904.LAA18603@bolt.sonic.net> To: ietf-iotp@lists.eListX.com Subject: Re: Internet Open Trading Protocol BoF Sender: ietf-iotp-owner@lists.eListX.com Precedence: bulk X-elistx: ietf-iotp Source-Info: From (or Sender) name not authenticated. I regret I won't be able to attend the BOF, but I am very interested in seeing a working group formed for the purpose described. Regards, Terry Allen Veo Systems, Inc. Business Language Designer 4005 Miranda Ave., no. 150 (Common Business Language - CBL) Palo Alto, 94034 terry.allen[at]veosystems.com http://www.veosystems.com/ ----------------------------------------------------------------------- Message addressed to: ietf-iotp@lists.elistx.com Archive available at: http://www.elistx.com/archives/ietf-iotp/ Return-Path: ietf-iotp-owner@one.eListX.com Received: from one.eListX.com (one.elistx.com [209.116.252.130]) by ietf.org (8.8.5/8.8.7a) with SMTP id AAA07957 for ; Fri, 27 Mar 1998 09:28:27 -0500 (EST) Received: from callandor.cybercash.com by one.eListX.com id aa28294; 27 Mar 98 09:25 EST Received: by callandor.cybercash.com; id JAA21673; Fri, 27 Mar 1998 09:28:24 -0500 Received: from cybercash.com(204.149.68.52) by callandor.cybercash.com via smap (3.2) id xma021656; Fri, 27 Mar 98 09:28:01 -0500 Received: (from dee@localhost) by cybercash.com (SMTP GateWay 2.0) id JAA21882; Fri, 27 Mar 1998 09:28:28 -0500 (EST) Date: Fri, 27 Mar 1998 09:28:27 -0500 (EST) From: "Donald E. Eastlake 3rd" To: ietf-iotp@elistx.com Subject: test Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ietf-iotp-owner@lists.eListX.com Precedence: bulk X-elistx: ietf-iotp Source-Info: From (or Sender) name not authenticated. test ===================================================================== Donald E. Eastlake 3rd +1 978-287-4877(tel) dee@cybercash.com 318 Acton Street +1 978-371-7148(fax) dee@world.std.com Carlisle, MA 01741 USA +1 703-620-4200(main office, Reston, VA) http://www.cybercash.com http://www.privacy.org/ipc ----------------------------------------------------------------------- Message addressed to: ietf-iotp@lists.elistx.com Archive available at: http://www.elistx.com/archives/ietf-iotp/