<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.debry-http-usepost" target="https://datatracker.ietf.org/doc/html/draft-debry-http-usepost-00">
   <front>
      <title>The Use of Post:  A Response to draft-cohen-http-postal-00.txt</title>
      <author initials="T. N." surname="Hastings" fullname="Thomas N. Hastings">
         </author>
      <author initials="F. D." surname="Wright" fullname="F. Don Wright">
         <organization>Lexmark</organization>
      </author>
      <author initials="H." surname="Lewis" fullname="Harry Lewis">
         </author>
      <author initials="S. A." surname="Isaacson" fullname="Scott A. Isaacson">
         <organization>Noell</organization>
      </author>
      <author initials="R." surname="deBry" fullname="Roger deBry">
         </author>
      <author initials="C." surname="Kugler" fullname="Carl Kugler">
         <organization>IBM</organization>
      </author>
      <author initials="S." surname="Gebert" fullname="Stee Gebert">
         </author>
      <date month="February" day="24" year="1998" />
      <abstract>
	 <t>A recent Internet Draft [1] argues that the common use of POST to
     proide a uniform method of passing blocks of data to an application,
     is being misused in the definition of new application protocols, such
     as the Internet Printing Protocol. Cohen et. al. argue that a new
     PUSH method be defined for this purpose. This Internet Draft argues
     that the existing POST method proides all of the required
     functionality for back end applications, such as Print, without
     sacrificing the leels of security that customers expect. More
     importantly, from the customer\022s point of iew, it does this without
     any impact to existing, installed network components.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-debry-http-usepost-00" />
   
</reference>
