Subject: Electronic Commerce Symposium CFP
From: Jorge Cobb <[email-masked]>
To: [email-masked]
Date: Thu, 22 Jun 2000 11:53:57 -0500 (CDT)

* please forgive us if you receive multiple copies of this message
* feel free to distribute to your colleagues.

                         ISADS 2001 CALL FOR PAPERS

                  The Fifth International Symposium on
                    Autonomous Decentralized Systems

		    with an emphasis on electronic commerce

                  Monday March 26 - Wednesday March 28, 2001
                         Dallas, Texas, USA

Sponsored by:

                         IEEE Computer Society 
              Information Processing Society of Japan 
        The Society of Instrument and Control Engineers of Japan 
    The Institute of Electronics, Infor. and Communication Engineers, Japan 

In Cooperation with:

             International Federation for Information Processing 
             International Federation of Automatic Control 
                             OMG 
                            TINA-C 
          Manufacturing Science and Technology Center, Japan 

Scope: 

Driven by the continuous growth in the power, intelligence and openness of
computer, communication and control technologies, possibilities and
opportunities for realizing highly efficient and dependable business and
control systems have been steadily increasing.  Dynamically changing
social and economic situations demand next-generation systems based on
emerging technologies and applications. Such systems are expected to have
the characteristics of living systems composed of largely autonomous and
decentralized components. Such systems are called Autonomous Decentralized
Systems (ADS).

After the successful first, second, third, and fourth International
Symposium on Autonomous Decentralized Systems (ISADS) held in 1993 in
Japan, in 1995 in the USA , in 1997 in Germany, and in 1999 in Japan, the
fifth ISADS will be held in Dallas, Texas, USA during March 26-28, 2001.
While ISADS 2001 will primarily focus on advancements and innovation in
ADS concept, technologies, and applications related to the increasingly
important topic of *Electronic Commerce*, other themes such as
telecommunications and heterogeneous system and application integration
will also be included.

The ISADS 2001 committee invites papers and panel proposals on the topics
of the symposium that will foster interactions among researchers and
practitioners in computer, communication, management, control as applied
to electronic commerce and other related fields from academia, industry,
and government.

The scope of discussions on ADS shall include, but not be limited 
to: 

* Computer and communication architectures / intelligent network /Internet; 
* Heterogeneous distributed information / control systems; 
* Mobile agent /computer-supported cooperative works;
* Distributed software development and maintenance;
* Assurance, fault tolerance and on-line expansion; 
* Object management architecture /design pattern / application frameworks; 
* Emergent control and robotic systems; 
* Novel applications: electronic commerce, telecommunications, 
  information service systems, manufacturing systems, 
  real-time event management, office automation, traffic and 
  transportation control, logistics systems. 

Plant tour is scheduled on March 29, 2001. Delegates are encour-
aged to participate. 

Information for Authors 

Papers should describe original work (not submitted or published
elsewhere) and be 20 double-spaced pages (5,000 words) or less in length.
Papers should include: title, authors, affiliations, 150-word abstract and
list of keywords.

Identify the author responsible for correspondence, including the author's
name, position, mailing address, telephone and fax numbers, and email
address. One of the authors of each accepted paper must present the paper
at ISADS 2001.

Information for Panel Organizers 

Panel proposals should include: title, organizer's affiliations, position,
mailing address, telephone and fax numbers, email address, and 150-word
statement on the scope, proposed chair and panelists.

Submission Address 

Authors and panel organizers are requested to submit their manuscripts
electrically in the Microsoft WORD document file format, the PDF format,
or the Postscript format, and also email the abstract and the full
addresses of the author(s) to the following address:

[email-masked]

Note The program committee of ISADS2001 highly encourage electronic
submissions. Otherwise, papers should be sent to the program chair:

Dr. Bhavani Thuraisingham
Mail Stop A270
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730
Phone: 781-271-8873
Fax: 781-271-8752
Email: [email-masked]

General Information 

For general information, see our World-Wide Web Page at: 

http://isads.utdallas.edu

The proceedings of the symposium will be published by IEEE Computer
Society Press.

Important Deadlines

August 15, 2000: All papers and panel proposals are due
November 15, 2000: Authors and panel organizers notified of acceptance. 
December 15, 2000: Camera-ready copies of accepted papers and 
panelists' position papers 

General Chair
William Osborne, U. of Texas, Dallas, USA

Program Committee

Chair: Bhavani Thuraisingham, The MITRE Corp., USA 

Co-Chair: Makoto Imase, NTT Labs, Japan
Co-Chair: Linda Strick, GMD Fokus, Berlin, Germany 
Co-Chair: Jeffrey Tsai, U. of Illinois, Chicago, USA 

Members
G. Agha, U. of IL, Urbana, USA
R. Arai, U. of Tokyo, Japan
D. Bae, KAIST, Korea  
F. Bastani, U. of TX, Dallas, USA
E. Bertino,  U. of Milano, Italy
M. Ceruti, SPAWAR, USA
I. Chen, Virginia, Tech, USA
Y. Chen, U. of the Witwatersrand, South Africa
R. Chow, U. of FL, USA
J. Chung, IBM T.J. Watson Research Center, USA
P. Chuang, Tamkang U., Taiwan
P. Ciancarini, U. of Bologna.
B. Cukic, West Virginia U., USA
K. Eckert, GMD FOKUS Germany
S. Eisenbach, Imperial College, UK
D. Ferrari, U. of Catoloca, Italy
M. Fisher, Manchester Metropolitan U., UK
M. Fujita, Sony, Japan
A. Fukuda, Nara Inst. of Science and Technology, Japan
V. Garg, Univ. of TX, Austin, USA
S. Ghosh, Arizona State U., USA       
A. Ghafoor,  Purdue U., USA
A. Ghose, U. of Wollongong, Australia
M. Gien, Sun, France
V. Gobel, U. of Oslo, Norway
T. Higashino Osaka U., Japan   
D. Hislop, ARO, USA
I.  Iida, Fujitsu, Japan
Y. Ishiguro, NEC, Japan
K. Ito, TITECH, Japan
Y. Kakuda, Hiroshima City U., Japan
K. Kim, U.C. Irvine, USA 
H. Kopetz, TU Wien, Austria
J. Kramer, Imperial College, UK
L. LeLann, INRIA, France
C. Liu, Chung Yuan Christian U., Taiwan
M. Lyu, The Chinese U. of Hong Kong, Hong Kong
Y. Masunaga, Ochanomizu U., Japan 
W. Meng , State U. of New York at Binghamton, USA
R. Montanari, U. of Bologna, Italy
W. Ng, Nanyang Technological U., Singapore
A. Prakash, U. of Michigan, USA
J. Putman, MITRE, USA
Q. Qingquan, Southwest Jiatong U., China
N. Raynal, INRIA, France
W. Ruh, Concept-V, USA
D. Serpanos, Inst. of Comuter Science, Technology-Hellas, Greece
S. Shekhar, U. of MN, Mpls, USA
L. Simoncini, CNUCE-CNR, Italy
R. Stroud, U. of  New Castle, UK
V. Subrahmanian, U. of MD, College Park, USA
K. Tsuchiya, Kyoto Uv, Japan
B. Wah, U. of  IL, Urbana, USA
Y. Wakahara, U. of Tokyo, Japan
F.  Wang, National Chao Tung U., Taiwan
M. Wooldridge, U. of Liverpool, UK
H. Yokota, TITECH, Japan  
M. Yano, Tohoku U., Japan
S. Yongqiang, Shanghai Jiao Tong U, China
P. Yu, IBM T.J. Watson Research Center
S. Zubairy, Quaid-e-Azam U., Pakistan

Steering Committee

Chair: Stephen S. Yau, Arizona State U., USA 
Hiroshi Kuwahara, Hitachi, Japan
Kinji Mori, Tokyo Inst. of Technology, Japan
Radu Popescu-Zeletin, GMD, Germany

Publicity Chair

Jorge Cobb, U. of Texas, Dallas, USA

Date: Fri, 16 Jun 2000 14:07:39 -0400
From: The IESG <[email-masked]>
Subject: Last Call: Internet Open Trading Protocol (IOTP) HTTP	Supplement to Proposed Standard
Sender: [email-masked]
To: IETF-Announce: ;
Cc: [email-masked]
Reply-to: [email-masked]

The IESG has received a request from the Internet Open Trading Protocol
Working Group to consider Internet Open Trading Protocol (IOTP) HTTP
Supplement <draft-ietf-trade-iotp-http-07.txt> as a Proposed Standard.

The IESG will also consider publication of HTTP MIME Type Handler
Detection <draft-ietf-trade-mime-detector-03.txt> as an Informational
RFC.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
[email-masked] or [email-masked] mailing lists by June 29, 2000.

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-http-07.txt
http://www.ietf.org/internet-drafts/draft-ietf-trade-mime-detector-03.txt

Date: Thu, 15 Jun 2000 13:48:11 -0400
From: "Donald E. Eastlake 3rd" <[email-masked]>
Subject: FWD: Internet-Draft Cut-off for Pittsburgh IETF
To: [email-masked]
Cc: [email-masked]

For those not on the main IETF list, here is the draft cutoff
announcement:

Message-Id:  <[email-masked]>
From:  Internet-Draft Administrator <[email-masked]>
To:  IETF-Announce: ;
Subject:  Internet-Draft Cut-off for Pittsburgh IETF
Date:  Thu, 15 Jun 2000 06:41:24 -0400

--------

The cut-off for Interntet-Draft submissions prior to the
Pittsburgh, PA, USA IETF meeting is Friday, July 14, 2000
at 5 pm US-ET. Internet-Drafts received after this time will NOT
be announced nor made available in the Internet-Drafts
Directories.

We will begin accepting Internet-Draft submissions the week
of the meeting, though announcements will NOT be sent until
the IETF meeting is over.

Thank you for your understanding and cooperation. Please do
not hesitate to contact us if you have any questions or
concerns.

NOTE: All initial submissions (-00.txt) with a filename
      beginning with a draft-ietf MUST be approved by the
      appropriate WG Chair prior to processing and announcing.
      WG Chair approval must be received prior to the I-D cut-off
      date.

      As such, -00 submissions received the day of the cut-off
      will NOT be processed as WG documents. Do NOT wait until
      the last minute.

FYI:  These and other significant date can be found at 
      http://www.ietf.org/meetings/cutoff_dates_48.html

Date: Wed, 14 Jun 2000 15:33:15 -0400
From: "Donald E. Eastlake 3rd" <[email-masked]>
Subject: draft-ietf-trade-mime-detector-03.txt & draft-ietf-trade-iotp-http-07.txt
To: [email-masked]

Since the MIME detector draft has passed working group Last Call I
will forward it to the IESG requesting publication as Informational.

You may have noticed a second revision of the IOTP HTTP supplement.
This was to fix capitlaization of "must" in some cases and the like,
as requested by our Area Director.  I will again be requesting
approval for its publication.

Thanks,
Donald

Date:  Wed, 31 May 2000 15:14:35 -0400
From:  "Donald E. Eastlake 3rd" <[email-masked]>
Subject:  HTTP Supplement and MIME Type Detector drafts
To:  [email-masked]
Message-id:  <[email-masked]>

Hi,

This is the start of a two week Working Group last call on the
draft-ietf-trade-mime-detector-03.txt draft.  This is an informational
document on determining what sort of MIME types a browser supports.

Since there were no objections to the
draft-ietf-trade-iotp-http-05.txt draft as per below, I'm going to do
a quick update onit to replace draft references with RFC references
and forward it to the IESG for their approval for publication as a
Proposed Standard RFC.

Thanks,
Donald

Date:  Wed, 03 May 2000 15:35:35 -0400
From:  "Donald E. Eastlake 3rd" <[email-masked]>
Subject:  WG Last CAll draft-ietf-trade-iotp-http-05.txt
To:  [email-masked]
Message-id:  <[email-masked]>

Since there have been no comments or suggestions on this draft for
some time and earlier comments and suggestions have generally been
incorporated, I'm calling a two week Working Group Last Call on this
draft.  I intend to forward the draft to the IESG as is or with minor
changes based on future comments sometime on or after 17 May.

Thanks,
Donald
=====================================================================
 Donald E. Eastlake 3rd                      [email-masked]
 140 Forest Avenue                                +1 914-276-2668(h)
 Hudson, MA 01749 USA                             +1 508-261-5434(w)

------- End of Forwarded Message

Date: Wed, 14 Jun 2000 15:16:38 -0400
From: "Donald E. Eastlake 3rd" <[email-masked]>
Subject: Chris Smith comments on draft-ioag-base-00.txt
To: [email-masked]

These are comments from Chris Smith:

>-----------------------------------------------------
>
>After a quick peek, I have initially noticed the
>following items. This is not a comprehensive
>review - some of these items may not be quite
>as I have seen them, so if you find that you
>disagree, please speak up. In addition, highly
>relevant items may have been missed. Again,
>if you see such, speak up.
>
>1) Inappropriateness of level
>
>   This protocol does cover what it indicates - that
>   is
>       "the data transfer between the subsystems of
>       a distributed billing and accounting system."
>
>   However, it covers much more as well. Based on the
>   overall role of a protocol such as this, I had
>   expected an application layer protocol. This goes
>   much lower. It includes topics that I would consider
>   out of scope, including such items as
>   'time synchronization' and 'message fragmentation
>   and reassembly'.
>
>   I expected that an application level protocol
>   would be designed to be transport independent.
>
>2) Incompleteness
>
>   In spite of pushing all the way down to link level
>   messages (see (1) above) this protocol does not
>   cover any aspects of encrypting or protecting its
>   content except for a single bitflag to indicate
>   'contents are encrypted'. However, since there appears
>   to be little flexibility in the message content structure,
>   this would require a significant volume of work to
>   add.
>
>   Furthermore, this protocol appears to depend on the
>   security of the network on which it is carried. This is
>   reinforced by the statement.
>
>     "10. Security Considerations
>          Authentication and crypting will be part of
>          the next version of BASE."
>
>   Given the low level to which this protocol pushes its
>   definitions, it may prove difficult to add the above
>   features using either standardized or commonly accepted
>   security mechanisms.
>
>3) Inappropriate definitions
>
>   This protocol assigns the authority for something called
>   'license keys' to the "BASE registration office of the
>   INTERNET ONLINE AG". (The 'license keys' appear to actually
>   be identifiers, not keys in the more common cryptographic
>   sense of the word.)
>
>   I would have expected this to reside elsewhere if this is to
>   fall under IETF governance. Other identifiers are simply specified
>   within the draft, with a policy of having new identifiers "announced
>   to the BASE registration office of the IOAG". This practice strikes
>   me as both inappropriate, and potentially a cause of conflicting
>   identifiers in actual use.
>
>   The actual 'load types' as listed in this document also seem to
>   be the bare minimum. In particular, quality of service issues
>   appear to be restricted to bandwidth. Given the value of low
>   latency to some types of communication, the listed set of load
>   types will likely not be sufficient.
>
>   Finally, the specifed URL, http://base.ioag.com, is not defined
>   as of this writing. This seems to be intended either for more
>   information, or as the registration point - this is not made clear.
>
>4) Exact role of IETF/IESG not clear
>
>   I find that the following statement contributes to some confusion
>   regarding the relationships between IOAG, the IETF and the IESG.
>
>      "BASE was defined by INTERNET ONLINE AG (IOAG) as a part of the 
>       development of their BillingWare product. It is, however, not 
>       restricted to a specific product, but allows a standardized 
>       communication within a distributed system of load data generators 
>       and load data analyzers."
>
>   As I understand it, the above statement is true, whether or not
>   this is a draft or accepted as an EFC.
>   
>   A much more useful statement (although possibly beyond the scope
>   of a draft) would have indicated how passing this protocol into
>   the governance of the IESG would help or make a difference.
>
>   Several statements throughout the document suggest that (1) this
>   protocol is in use and (2) a next version is expected. If the
>   goal here is NOT to involve the IESG and IETF in the work of the
>   next version, why is this even being posted as a draft? I speak
>   only for myself, but it would not surprise me to find that the
>   next version of the specification would be far more restricted
>   in its scope. However, I would have initial concerns about the
>   roles and reactions of the various parties if an in-use 
>   proprietary protocol was to be picked up and heavily modified
>   by the IETF.
>
>In summary - it is reasonable to assume that there is a role for a 
>protocol to relay 'load data' for billing purposes. I am certain
>that I do not have sufficient background to know if this is covered
>by any existing IESG RFCs or initiatives.
>
>However, I would prefer to see a substantial amount of focus and
>trimming of this specification to better focus on its core
>requirements, and to better enable it to work within the
>larger domain of standards that may better address non-core
>requirements.
>
>------------------------------------------------------------ 
> Chris Smith                                +1.416.348.6090 
> Royal Bank                       [email-masked] 

In response to the procedural parts above, the IETF has a long history
of publishing protocols and networking documents of general interest
even if they are not under IETF control.  The main thing we should be
looking for in review is problems with the protocol that are not
mentioned in the protocol or conflicts with on-going IETF work.  It's
not a question of whether, as a working gorup, we approve of this, but
whether there are serious problems we see which are not pointed out in
the document.

Thanks,
Donald

Date: Tue, 13 Jun 2000 07:04:00 -0400
From: [email-masked]
Subject: I-D ACTION:draft-ietf-trade-iotp-http-07.txt
Sender: [email-masked]
To: IETF-Announce: ;
Cc: [email-masked]
Reply-to: [email-masked]

--Boundary_(ID_LtV/iYn8IPGPvUCFLOKkAw)

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Open Trading Protocol Working Group of the IETF.

	Title		: Internet Open Trading Protocol (IOTP) HTTP Supplement
	Author(s)	: D. Eastlake 3rd, C. Smith	 
        Filename	: draft-ietf-trade-iotp-http-07.txt
	Pages		: 9
	Date		: 12-Jun-00
	
Internet Open Trading Protocol (IOTP [RFC 2801]) messages will be
carried as XML documents. As such, the goal of mapping to the
transport layer is to ensure that the underlying XML documents are
carried successfully between the various parties.
This documents describes that mapping for the Hyper Text Transport
Protocol (HTTP), Versions 1.0 and 1.1.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-http-07.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-trade-iotp-http-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-trade-iotp-http-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_LtV/iYn8IPGPvUCFLOKkAw)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_jVpfthQNmNNzIc5lG4bMYA)"

--Boundary_(ID_jVpfthQNmNNzIc5lG4bMYA)
Content-type: Message/External-body; access-type="mail-server";
 server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-trade-iotp-http-07.txt

--Boundary_(ID_jVpfthQNmNNzIc5lG4bMYA)
Content-type: Message/External-body; name="draft-ietf-trade-iotp-http-07.txt";
 site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--Boundary_(ID_jVpfthQNmNNzIc5lG4bMYA)--

--Boundary_(ID_LtV/iYn8IPGPvUCFLOKkAw)--

Date: Fri, 09 Jun 2000 18:09:11 -0400
From: "Donald E. Eastlake 3rd" <[email-masked]>
Subject: IOTP Book Published
To: [email-masked]

I hope you will excuse my posting this to the list bu McGraw Hill has
published : "Internet Open Trading Protocol" by David Burdett, Donald
E. Eastlake III, & Marcus Goncalves.  ISBN 0-07-135501-4.

Thanks,
Donald
=====================================================================
 Donald E. Eastlake 3rd                      [email-masked]
 140 Forest Avenue                                +1 978-562-2827(h)
 Hudson, MA 01749 USA                             +1 508-261-5434(w)

Date: Fri, 02 Jun 2000 06:42:39 -0400
From: [email-masked]
Subject: I-D ACTION:draft-ietf-trade-iotp-http-06.txt
Sender: [email-masked]
To: IETF-Announce: ;
Cc: [email-masked]
Reply-to: [email-masked]

--Boundary_(ID_SqQvgRp/2wKIgpAzHcjHAA)

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Open Trading Protocol Working Group of the IETF.

	Title		: Internet Open Trading Protocol (IOTP) HTTP Supplement
	Author(s)	: D. Eastlake 3rd, C. Smith 
 	Filename	: draft-ietf-trade-iotp-http-06.txt
	Pages		: 9
	Date		: 01-Jun-00
	
Internet Open Trading Protocol (IOTP [RFC 2801]) messages will be
carried as XML documents. As such, the goal of mapping to the
transport layer is to ensure that the underlying XML documents are
carried successfully between the various parties.
This documents describes that mapping for the Hyper Text Transport
Protocol (HTTP), Versions 1.0 and 1.1.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-http-06.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-trade-iotp-http-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-trade-iotp-http-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_SqQvgRp/2wKIgpAzHcjHAA)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_vQNeZ8wsZ5bPGOluZUd96w)"

--Boundary_(ID_vQNeZ8wsZ5bPGOluZUd96w)
Content-type: Message/External-body; access-type="mail-server";
 server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-trade-iotp-http-06.txt

--Boundary_(ID_vQNeZ8wsZ5bPGOluZUd96w)
Content-type: Message/External-body; name="draft-ietf-trade-iotp-http-06.txt";
 site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--Boundary_(ID_vQNeZ8wsZ5bPGOluZUd96w)--

--Boundary_(ID_SqQvgRp/2wKIgpAzHcjHAA)--

Date: Fri, 02 Jun 2000 06:42:39 -0400
From: [email-masked]
Subject: I-D ACTION:draft-ietf-trade-iotp-http-06.txt
Sender: [email-masked]
To: IETF-Announce: ;
Cc: [email-masked]
Reply-to: [email-masked]

--Boundary_(ID_tTOb4/We8DStNzeQLeO8PQ)

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Open Trading Protocol Working Group of the IETF.

	Title		: Internet Open Trading Protocol (IOTP) HTTP Supplement
	Author(s)	: D. Eastlake 3rd, C. Smith 
 	Filename	: draft-ietf-trade-iotp-http-06.txt
	Pages		: 9
	Date		: 01-Jun-00
	
Internet Open Trading Protocol (IOTP [RFC 2801]) messages will be
carried as XML documents. As such, the goal of mapping to the
transport layer is to ensure that the underlying XML documents are
carried successfully between the various parties.
This documents describes that mapping for the Hyper Text Transport
Protocol (HTTP), Versions 1.0 and 1.1.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-http-06.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-trade-iotp-http-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-trade-iotp-http-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_tTOb4/We8DStNzeQLeO8PQ)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_OIYL+NNOA5UHfdgPIdT/TQ)"

--Boundary_(ID_OIYL+NNOA5UHfdgPIdT/TQ)
Content-type: Message/External-body; access-type="mail-server";
 server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-trade-iotp-http-06.txt

--Boundary_(ID_OIYL+NNOA5UHfdgPIdT/TQ)
Content-type: Message/External-body; name="draft-ietf-trade-iotp-http-06.txt";
 site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--Boundary_(ID_OIYL+NNOA5UHfdgPIdT/TQ)--

--Boundary_(ID_tTOb4/We8DStNzeQLeO8PQ)--

Date: Thu, 01 Jun 2000 18:21:19 +0200
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <[email-masked]>
Subject: draft-ioag-base-00.txt
To: Donald Eastlake 3rd <[email-masked]>
Cc: iesg <[email-masked]>, [email-masked]

Would TRADE please take a peek at this and advise the IESG if it is reasonable?

    Patrik
    Area Director, Applications Area

Date: Thu, 22 Jun 2000 11:53:57 -0500 (CDT)
From: Jorge Cobb <[email-masked]>
Subject: Electronic Commerce Symposium CFP
To: [email-masked]

* please forgive us if you receive multiple copies of this message
* feel free to distribute to your colleagues.

                         ISADS 2001 CALL FOR PAPERS

                  The Fifth International Symposium on
                    Autonomous Decentralized Systems

		    with an emphasis on electronic commerce

                  Monday March 26 - Wednesday March 28, 2001
                         Dallas, Texas, USA

Sponsored by:

                         IEEE Computer Society 
              Information Processing Society of Japan 
        The Society of Instrument and Control Engineers of Japan 
    The Institute of Electronics, Infor. and Communication Engineers, Japan 

In Cooperation with:

             International Federation for Information Processing 
             International Federation of Automatic Control 
                             OMG 
                            TINA-C 
          Manufacturing Science and Technology Center, Japan 

Scope: 

Driven by the continuous growth in the power, intelligence and openness of
computer, communication and control technologies, possibilities and
opportunities for realizing highly efficient and dependable business and
control systems have been steadily increasing.  Dynamically changing
social and economic situations demand next-generation systems based on
emerging technologies and applications. Such systems are expected to have
the characteristics of living systems composed of largely autonomous and
decentralized components. Such systems are called Autonomous Decentralized
Systems (ADS).

After the successful first, second, third, and fourth International
Symposium on Autonomous Decentralized Systems (ISADS) held in 1993 in
Japan, in 1995 in the USA , in 1997 in Germany, and in 1999 in Japan, the
fifth ISADS will be held in Dallas, Texas, USA during March 26-28, 2001.
While ISADS 2001 will primarily focus on advancements and innovation in
ADS concept, technologies, and applications related to the increasingly
important topic of *Electronic Commerce*, other themes such as
telecommunications and heterogeneous system and application integration
will also be included.

The ISADS 2001 committee invites papers and panel proposals on the topics
of the symposium that will foster interactions among researchers and
practitioners in computer, communication, management, control as applied
to electronic commerce and other related fields from academia, industry,
and government.

The scope of discussions on ADS shall include, but not be limited 
to: 

* Computer and communication architectures / intelligent network /Internet; 
* Heterogeneous distributed information / control systems; 
* Mobile agent /computer-supported cooperative works;
* Distributed software development and maintenance;
* Assurance, fault tolerance and on-line expansion; 
* Object management architecture /design pattern / application frameworks; 
* Emergent control and robotic systems; 
* Novel applications: electronic commerce, telecommunications, 
  information service systems, manufacturing systems, 
  real-time event management, office automation, traffic and 
  transportation control, logistics systems. 

Plant tour is scheduled on March 29, 2001. Delegates are encour-
aged to participate. 

Information for Authors 

Papers should describe original work (not submitted or published
elsewhere) and be 20 double-spaced pages (5,000 words) or less in length.
Papers should include: title, authors, affiliations, 150-word abstract and
list of keywords.

Identify the author responsible for correspondence, including the author's
name, position, mailing address, telephone and fax numbers, and email
address. One of the authors of each accepted paper must present the paper
at ISADS 2001.

Information for Panel Organizers 

Panel proposals should include: title, organizer's affiliations, position,
mailing address, telephone and fax numbers, email address, and 150-word
statement on the scope, proposed chair and panelists.

Submission Address 

Authors and panel organizers are requested to submit their manuscripts
electrically in the Microsoft WORD document file format, the PDF format,
or the Postscript format, and also email the abstract and the full
addresses of the author(s) to the following address:

[email-masked]

Note The program committee of ISADS2001 highly encourage electronic
submissions. Otherwise, papers should be sent to the program chair:

Dr. Bhavani Thuraisingham
Mail Stop A270
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730
Phone: 781-271-8873
Fax: 781-271-8752
Email: [email-masked]

General Information 

For general information, see our World-Wide Web Page at: 

http://isads.utdallas.edu

The proceedings of the symposium will be published by IEEE Computer
Society Press.

Important Deadlines

August 15, 2000: All papers and panel proposals are due
November 15, 2000: Authors and panel organizers notified of acceptance. 
December 15, 2000: Camera-ready copies of accepted papers and 
panelists' position papers 

General Chair
William Osborne, U. of Texas, Dallas, USA

Program Committee

Chair: Bhavani Thuraisingham, The MITRE Corp., USA 

Co-Chair: Makoto Imase, NTT Labs, Japan
Co-Chair: Linda Strick, GMD Fokus, Berlin, Germany 
Co-Chair: Jeffrey Tsai, U. of Illinois, Chicago, USA 

Members
G. Agha, U. of IL, Urbana, USA
R. Arai, U. of Tokyo, Japan
D. Bae, KAIST, Korea  
F. Bastani, U. of TX, Dallas, USA
E. Bertino,  U. of Milano, Italy
M. Ceruti, SPAWAR, USA
I. Chen, Virginia, Tech, USA
Y. Chen, U. of the Witwatersrand, South Africa
R. Chow, U. of FL, USA
J. Chung, IBM T.J. Watson Research Center, USA
P. Chuang, Tamkang U., Taiwan
P. Ciancarini, U. of Bologna.
B. Cukic, West Virginia U., USA
K. Eckert, GMD FOKUS Germany
S. Eisenbach, Imperial College, UK
D. Ferrari, U. of Catoloca, Italy
M. Fisher, Manchester Metropolitan U., UK
M. Fujita, Sony, Japan
A. Fukuda, Nara Inst. of Science and Technology, Japan
V. Garg, Univ. of TX, Austin, USA
S. Ghosh, Arizona State U., USA       
A. Ghafoor,  Purdue U., USA
A. Ghose, U. of Wollongong, Australia
M. Gien, Sun, France
V. Gobel, U. of Oslo, Norway
T. Higashino Osaka U., Japan   
D. Hislop, ARO, USA
I.  Iida, Fujitsu, Japan
Y. Ishiguro, NEC, Japan
K. Ito, TITECH, Japan
Y. Kakuda, Hiroshima City U., Japan
K. Kim, U.C. Irvine, USA 
H. Kopetz, TU Wien, Austria
J. Kramer, Imperial College, UK
L. LeLann, INRIA, France
C. Liu, Chung Yuan Christian U., Taiwan
M. Lyu, The Chinese U. of Hong Kong, Hong Kong
Y. Masunaga, Ochanomizu U., Japan 
W. Meng , State U. of New York at Binghamton, USA
R. Montanari, U. of Bologna, Italy
W. Ng, Nanyang Technological U., Singapore
A. Prakash, U. of Michigan, USA
J. Putman, MITRE, USA
Q. Qingquan, Southwest Jiatong U., China
N. Raynal, INRIA, France
W. Ruh, Concept-V, USA
D. Serpanos, Inst. of Comuter Science, Technology-Hellas, Greece
S. Shekhar, U. of MN, Mpls, USA
L. Simoncini, CNUCE-CNR, Italy
R. Stroud, U. of  New Castle, UK
V. Subrahmanian, U. of MD, College Park, USA
K. Tsuchiya, Kyoto Uv, Japan
B. Wah, U. of  IL, Urbana, USA
Y. Wakahara, U. of Tokyo, Japan
F.  Wang, National Chao Tung U., Taiwan
M. Wooldridge, U. of Liverpool, UK
H. Yokota, TITECH, Japan  
M. Yano, Tohoku U., Japan
S. Yongqiang, Shanghai Jiao Tong U, China
P. Yu, IBM T.J. Watson Research Center
S. Zubairy, Quaid-e-Azam U., Pakistan

Steering Committee

Chair: Stephen S. Yau, Arizona State U., USA 
Hiroshi Kuwahara, Hitachi, Japan
Kinji Mori, Tokyo Inst. of Technology, Japan
Radu Popescu-Zeletin, GMD, Germany

Publicity Chair

Jorge Cobb, U. of Texas, Dallas, USA

Date: Fri, 16 Jun 2000 14:07:39 -0400
From: The IESG <[email-masked]>
Subject: Last Call: Internet Open Trading Protocol (IOTP) HTTP	Supplement to Proposed Standard
Sender: [email-masked]
To: IETF-Announce: ;
Cc: [email-masked]
Reply-to: [email-masked]

The IESG has received a request from the Internet Open Trading Protocol
Working Group to consider Internet Open Trading Protocol (IOTP) HTTP
Supplement <draft-ietf-trade-iotp-http-07.txt> as a Proposed Standard.

The IESG will also consider publication of HTTP MIME Type Handler
Detection <draft-ietf-trade-mime-detector-03.txt> as an Informational
RFC.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
[email-masked] or [email-masked] mailing lists by June 29, 2000.

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-http-07.txt
http://www.ietf.org/internet-drafts/draft-ietf-trade-mime-detector-03.txt

Date: Thu, 15 Jun 2000 13:48:11 -0400
From: "Donald E. Eastlake 3rd" <[email-masked]>
Subject: FWD: Internet-Draft Cut-off for Pittsburgh IETF
To: [email-masked]
Cc: [email-masked]

For those not on the main IETF list, here is the draft cutoff
announcement:

Message-Id:  <[email-masked]>
From:  Internet-Draft Administrator <[email-masked]>
To:  IETF-Announce: ;
Subject:  Internet-Draft Cut-off for Pittsburgh IETF
Date:  Thu, 15 Jun 2000 06:41:24 -0400

--------

The cut-off for Interntet-Draft submissions prior to the
Pittsburgh, PA, USA IETF meeting is Friday, July 14, 2000
at 5 pm US-ET. Internet-Drafts received after this time will NOT
be announced nor made available in the Internet-Drafts
Directories.

We will begin accepting Internet-Draft submissions the week
of the meeting, though announcements will NOT be sent until
the IETF meeting is over.

Thank you for your understanding and cooperation. Please do
not hesitate to contact us if you have any questions or
concerns.

NOTE: All initial submissions (-00.txt) with a filename
      beginning with a draft-ietf MUST be approved by the
      appropriate WG Chair prior to processing and announcing.
      WG Chair approval must be received prior to the I-D cut-off
      date.

      As such, -00 submissions received the day of the cut-off
      will NOT be processed as WG documents. Do NOT wait until
      the last minute.

FYI:  These and other significant date can be found at 
      http://www.ietf.org/meetings/cutoff_dates_48.html

Date: Wed, 14 Jun 2000 15:33:15 -0400
From: "Donald E. Eastlake 3rd" <[email-masked]>
Subject: draft-ietf-trade-mime-detector-03.txt & draft-ietf-trade-iotp-http-07.txt
To: [email-masked]

Since the MIME detector draft has passed working group Last Call I
will forward it to the IESG requesting publication as Informational.

You may have noticed a second revision of the IOTP HTTP supplement.
This was to fix capitlaization of "must" in some cases and the like,
as requested by our Area Director.  I will again be requesting
approval for its publication.

Thanks,
Donald

Date:  Wed, 31 May 2000 15:14:35 -0400
From:  "Donald E. Eastlake 3rd" <[email-masked]>
Subject:  HTTP Supplement and MIME Type Detector drafts
To:  [email-masked]
Message-id:  <[email-masked]>

Hi,

This is the start of a two week Working Group last call on the
draft-ietf-trade-mime-detector-03.txt draft.  This is an informational
document on determining what sort of MIME types a browser supports.

Since there were no objections to the
draft-ietf-trade-iotp-http-05.txt draft as per below, I'm going to do
a quick update onit to replace draft references with RFC references
and forward it to the IESG for their approval for publication as a
Proposed Standard RFC.

Thanks,
Donald

Date:  Wed, 03 May 2000 15:35:35 -0400
From:  "Donald E. Eastlake 3rd" <[email-masked]>
Subject:  WG Last CAll draft-ietf-trade-iotp-http-05.txt
To:  [email-masked]
Message-id:  <[email-masked]>

Since there have been no comments or suggestions on this draft for
some time and earlier comments and suggestions have generally been
incorporated, I'm calling a two week Working Group Last Call on this
draft.  I intend to forward the draft to the IESG as is or with minor
changes based on future comments sometime on or after 17 May.

Thanks,
Donald
=====================================================================
 Donald E. Eastlake 3rd                      [email-masked]
 140 Forest Avenue                                +1 914-276-2668(h)
 Hudson, MA 01749 USA                             +1 508-261-5434(w)

------- End of Forwarded Message

Date: Wed, 14 Jun 2000 15:16:38 -0400
From: "Donald E. Eastlake 3rd" <[email-masked]>
Subject: Chris Smith comments on draft-ioag-base-00.txt
To: [email-masked]

These are comments from Chris Smith:

>-----------------------------------------------------
>
>After a quick peek, I have initially noticed the
>following items. This is not a comprehensive
>review - some of these items may not be quite
>as I have seen them, so if you find that you
>disagree, please speak up. In addition, highly
>relevant items may have been missed. Again,
>if you see such, speak up.
>
>1) Inappropriateness of level
>
>   This protocol does cover what it indicates - that
>   is
>       "the data transfer between the subsystems of
>       a distributed billing and accounting system."
>
>   However, it covers much more as well. Based on the
>   overall role of a protocol such as this, I had
>   expected an application layer protocol. This goes
>   much lower. It includes topics that I would consider
>   out of scope, including such items as
>   'time synchronization' and 'message fragmentation
>   and reassembly'.
>
>   I expected that an application level protocol
>   would be designed to be transport independent.
>
>2) Incompleteness
>
>   In spite of pushing all the way down to link level
>   messages (see (1) above) this protocol does not
>   cover any aspects of encrypting or protecting its
>   content except for a single bitflag to indicate
>   'contents are encrypted'. However, since there appears
>   to be little flexibility in the message content structure,
>   this would require a significant volume of work to
>   add.
>
>   Furthermore, this protocol appears to depend on the
>   security of the network on which it is carried. This is
>   reinforced by the statement.
>
>     "10. Security Considerations
>          Authentication and crypting will be part of
>          the next version of BASE."
>
>   Given the low level to which this protocol pushes its
>   definitions, it may prove difficult to add the above
>   features using either standardized or commonly accepted
>   security mechanisms.
>
>3) Inappropriate definitions
>
>   This protocol assigns the authority for something called
>   'license keys' to the "BASE registration office of the
>   INTERNET ONLINE AG". (The 'license keys' appear to actually
>   be identifiers, not keys in the more common cryptographic
>   sense of the word.)
>
>   I would have expected this to reside elsewhere if this is to
>   fall under IETF governance. Other identifiers are simply specified
>   within the draft, with a policy of having new identifiers "announced
>   to the BASE registration office of the IOAG". This practice strikes
>   me as both inappropriate, and potentially a cause of conflicting
>   identifiers in actual use.
>
>   The actual 'load types' as listed in this document also seem to
>   be the bare minimum. In particular, quality of service issues
>   appear to be restricted to bandwidth. Given the value of low
>   latency to some types of communication, the listed set of load
>   types will likely not be sufficient.
>
>   Finally, the specifed URL, http://base.ioag.com, is not defined
>   as of this writing. This seems to be intended either for more
>   information, or as the registration point - this is not made clear.
>
>4) Exact role of IETF/IESG not clear
>
>   I find that the following statement contributes to some confusion
>   regarding the relationships between IOAG, the IETF and the IESG.
>
>      "BASE was defined by INTERNET ONLINE AG (IOAG) as a part of the 
>       development of their BillingWare product. It is, however, not 
>       restricted to a specific product, but allows a standardized 
>       communication within a distributed system of load data generators 
>       and load data analyzers."
>
>   As I understand it, the above statement is true, whether or not
>   this is a draft or accepted as an EFC.
>   
>   A much more useful statement (although possibly beyond the scope
>   of a draft) would have indicated how passing this protocol into
>   the governance of the IESG would help or make a difference.
>
>   Several statements throughout the document suggest that (1) this
>   protocol is in use and (2) a next version is expected. If the
>   goal here is NOT to involve the IESG and IETF in the work of the
>   next version, why is this even being posted as a draft? I speak
>   only for myself, but it would not surprise me to find that the
>   next version of the specification would be far more restricted
>   in its scope. However, I would have initial concerns about the
>   roles and reactions of the various parties if an in-use 
>   proprietary protocol was to be picked up and heavily modified
>   by the IETF.
>
>In summary - it is reasonable to assume that there is a role for a 
>protocol to relay 'load data' for billing purposes. I am certain
>that I do not have sufficient background to know if this is covered
>by any existing IESG RFCs or initiatives.
>
>However, I would prefer to see a substantial amount of focus and
>trimming of this specification to better focus on its core
>requirements, and to better enable it to work within the
>larger domain of standards that may better address non-core
>requirements.
>
>------------------------------------------------------------ 
> Chris Smith                                +1.416.348.6090 
> Royal Bank                       [email-masked] 

In response to the procedural parts above, the IETF has a long history
of publishing protocols and networking documents of general interest
even if they are not under IETF control.  The main thing we should be
looking for in review is problems with the protocol that are not
mentioned in the protocol or conflicts with on-going IETF work.  It's
not a question of whether, as a working gorup, we approve of this, but
whether there are serious problems we see which are not pointed out in
the document.

Thanks,
Donald

Date: Tue, 13 Jun 2000 07:04:00 -0400
From: [email-masked]
Subject: I-D ACTION:draft-ietf-trade-iotp-http-07.txt
Sender: [email-masked]
To: IETF-Announce: ;
Cc: [email-masked]
Reply-to: [email-masked]

--Boundary_(ID_LtV/iYn8IPGPvUCFLOKkAw)

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Open Trading Protocol Working Group of the IETF.

	Title		: Internet Open Trading Protocol (IOTP) HTTP Supplement
	Author(s)	: D. Eastlake 3rd, C. Smith	 
        Filename	: draft-ietf-trade-iotp-http-07.txt
	Pages		: 9
	Date		: 12-Jun-00
	
Internet Open Trading Protocol (IOTP [RFC 2801]) messages will be
carried as XML documents. As such, the goal of mapping to the
transport layer is to ensure that the underlying XML documents are
carried successfully between the various parties.
This documents describes that mapping for the Hyper Text Transport
Protocol (HTTP), Versions 1.0 and 1.1.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-http-07.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-trade-iotp-http-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-trade-iotp-http-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_LtV/iYn8IPGPvUCFLOKkAw)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_jVpfthQNmNNzIc5lG4bMYA)"

--Boundary_(ID_jVpfthQNmNNzIc5lG4bMYA)
Content-type: Message/External-body; access-type="mail-server";
 server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-trade-iotp-http-07.txt

--Boundary_(ID_jVpfthQNmNNzIc5lG4bMYA)
Content-type: Message/External-body; name="draft-ietf-trade-iotp-http-07.txt";
 site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--Boundary_(ID_jVpfthQNmNNzIc5lG4bMYA)--

--Boundary_(ID_LtV/iYn8IPGPvUCFLOKkAw)--

Date: Fri, 09 Jun 2000 18:09:11 -0400
From: "Donald E. Eastlake 3rd" <[email-masked]>
Subject: IOTP Book Published
To: [email-masked]

I hope you will excuse my posting this to the list bu McGraw Hill has
published : "Internet Open Trading Protocol" by David Burdett, Donald
E. Eastlake III, & Marcus Goncalves.  ISBN 0-07-135501-4.

Thanks,
Donald
=====================================================================
 Donald E. Eastlake 3rd                      [email-masked]
 140 Forest Avenue                                +1 978-562-2827(h)
 Hudson, MA 01749 USA                             +1 508-261-5434(w)

Date: Fri, 02 Jun 2000 06:42:39 -0400
From: [email-masked]
Subject: I-D ACTION:draft-ietf-trade-iotp-http-06.txt
Sender: [email-masked]
To: IETF-Announce: ;
Cc: [email-masked]
Reply-to: [email-masked]

--Boundary_(ID_SqQvgRp/2wKIgpAzHcjHAA)

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Open Trading Protocol Working Group of the IETF.

	Title		: Internet Open Trading Protocol (IOTP) HTTP Supplement
	Author(s)	: D. Eastlake 3rd, C. Smith 
 	Filename	: draft-ietf-trade-iotp-http-06.txt
	Pages		: 9
	Date		: 01-Jun-00
	
Internet Open Trading Protocol (IOTP [RFC 2801]) messages will be
carried as XML documents. As such, the goal of mapping to the
transport layer is to ensure that the underlying XML documents are
carried successfully between the various parties.
This documents describes that mapping for the Hyper Text Transport
Protocol (HTTP), Versions 1.0 and 1.1.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-http-06.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-trade-iotp-http-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-trade-iotp-http-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_SqQvgRp/2wKIgpAzHcjHAA)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_vQNeZ8wsZ5bPGOluZUd96w)"

--Boundary_(ID_vQNeZ8wsZ5bPGOluZUd96w)
Content-type: Message/External-body; access-type="mail-server";
 server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-trade-iotp-http-06.txt

--Boundary_(ID_vQNeZ8wsZ5bPGOluZUd96w)
Content-type: Message/External-body; name="draft-ietf-trade-iotp-http-06.txt";
 site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--Boundary_(ID_vQNeZ8wsZ5bPGOluZUd96w)--

--Boundary_(ID_SqQvgRp/2wKIgpAzHcjHAA)--

Date: Fri, 02 Jun 2000 06:42:39 -0400
From: [email-masked]
Subject: I-D ACTION:draft-ietf-trade-iotp-http-06.txt
Sender: [email-masked]
To: IETF-Announce: ;
Cc: [email-masked]
Reply-to: [email-masked]

--Boundary_(ID_tTOb4/We8DStNzeQLeO8PQ)

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Open Trading Protocol Working Group of the IETF.

	Title		: Internet Open Trading Protocol (IOTP) HTTP Supplement
	Author(s)	: D. Eastlake 3rd, C. Smith 
 	Filename	: draft-ietf-trade-iotp-http-06.txt
	Pages		: 9
	Date		: 01-Jun-00
	
Internet Open Trading Protocol (IOTP [RFC 2801]) messages will be
carried as XML documents. As such, the goal of mapping to the
transport layer is to ensure that the underlying XML documents are
carried successfully between the various parties.
This documents describes that mapping for the Hyper Text Transport
Protocol (HTTP), Versions 1.0 and 1.1.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-http-06.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-trade-iotp-http-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-trade-iotp-http-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_tTOb4/We8DStNzeQLeO8PQ)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_OIYL+NNOA5UHfdgPIdT/TQ)"

--Boundary_(ID_OIYL+NNOA5UHfdgPIdT/TQ)
Content-type: Message/External-body; access-type="mail-server";
 server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-trade-iotp-http-06.txt

--Boundary_(ID_OIYL+NNOA5UHfdgPIdT/TQ)
Content-type: Message/External-body; name="draft-ietf-trade-iotp-http-06.txt";
 site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--Boundary_(ID_OIYL+NNOA5UHfdgPIdT/TQ)--

--Boundary_(ID_tTOb4/We8DStNzeQLeO8PQ)--

Date: Thu, 01 Jun 2000 18:21:19 +0200
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <[email-masked]>
Subject: draft-ioag-base-00.txt
To: Donald Eastlake 3rd <[email-masked]>
Cc: iesg <[email-masked]>, [email-masked]

Would TRADE please take a peek at this and advise the IESG if it is reasonable?

    Patrik
    Area Director, Applications Area