[comp.protocols.tcp-ip.ibmpc] New Stanford PC/IP stuff

davidc@TERMINUS.UMD.EDU (01/28/88)

>I am planning to release version 3.0 of SU-PC/IP next month.

    Just a few questions...

>2) Code has now been ported to Microsoft C (version 5.0) and MASM 

    What version of MASM are you using?

>4) Changes in SMTP client to make it more secure

    What kind of changes?  How are you doing authentication?  Are you
still using the MHish interface with MH-POP?

>   We are currently working on tn3270 and SLIP driver

    Are you aware of the RFC that Jacob Rekhter of IBM has submitted to
Jon Postel proposing a new way of doing tn3270 option negotiation?  
If yes, did you implement the proposed 3270-Regime (what a name) stuff?  
If no, are you planning to?

Thanks...

-drc

khanna@JESSICA.STANFORD.EDU (Raman Khanna) (01/29/88)

>     What version of MASM are you using?
      
      4.0

>     What kind of changes?  How are you doing authentication?  Are you
>    still using the MHish interface with MH-POP?

      For authentication we are using subscriber-id & password
combination for receiving as well as sending messages.  Authentication
is done only once per session, so you don't have to enter password 10 
times if you plan to send 10 messages in one session.

      Yes, the user-interface continues to be MHish.  However, in our 
implementation for Macs, we are trying a more user-friendly Mac-like
interface.  In case people like it, we plan to provide a menu-driven
interface in addition to the current interface.  No commitments as yet, 
but any suggestions are most welcome.


>     Are you aware of the RFC that Jacob Rekhter of IBM has submitted to
>    Jon Postel proposing a new way of doing tn3270 option negotiation?  
>    If yes, did you implement the proposed 3270-Regime (what a name) stuff?  
>    If no, are you planning to?

     Yes, I have looked at the draft RFC.  We are waiting for RFC to be
released officially.  Right now my feeling is that we will implement
whatever the RFC says.  I haven't talked to Jacob as yet to find out
about the status of the RFC.


raman