Re: FW: AS#2 - Internet Draft Proposal - 0/3

[rsedc@xxxxxxxxxxxxxxxxxxxxxxx (David Chia)]

Bill Jacky wrote:

> 2).	Based on the initial requirements of this task force, it appears to
> me non-repudiation is a
> 	required topic; the standard must enforce non-repudiation.

Yes. At the server level as well as the application level. The server might
be running outside the firewall.

> 3).	The protocol should be between the application layer and the network
> layer.  Many of
> 	the comments here seem to forget that.  

No, that was exactly the point I raised. Is the ECTP server a single
application server or a front to many applications ? If it is a front
to many applications then how are they co-ordinated ?

> >Will the ECTP server able to write to any users' directories (i.e. root
> >priviledge) ? Will it trigger execution of application programs similar
> >to the email filter or the HTTP CGI ?

<snip>

> >Is the ECTP server suppose to be a single application server (like
> >the NNTP server) ? If not how do the ECTP server know what NEXT means
> >without referring to the appropriate applications ? The next item
> >in the catalog or the next cargo shipment ? If the NEXTs are meant
> >for the applications then why direct them towards the ECTP server ?

<snip>

> >On the other hand if the 'ECTP' servers are built into the
> >many diff bussiness applications, then how many ports need
> >to be registered as standard ports ? Otherwise how do the
> >originating clinets know where to go ?

<snip>


David Chia,
RMIT University