RE: TCP Mapping

["Liu, Hong" <Hong.Liu@neustar.biz>]

Rick,

Most (if not all) EPP implementations today use TCP and will stay that way
for a long time. For this matter, we want to make PUSH work using TCP. It is
not a requirement, it is an extension with which we can use PUSH for EPP
over TCP.

I don't think EPP PUSH should be exclusively tied to BEEP. BEEP makes EPP
PUSH easier, and that is it.

I am not sure about smtp since I have not seen the draft yet...

Two questions need to be addressed separately in the discussion:
1. Can EPP PUSH be used for EPP over TCP?
2. How to do the EPP PUSH extension properly for EPP over TCP (or over any
transport)?

I hope we can agree on 1 and focus on 2.  

--Hong

-----Original Message-----
From: Rick Wesson [mailto:wessorh@ar.com]
Sent: Saturday, June 29, 2002 7:40 PM
To: Hollenbeck, Scott
Cc: 'Eric Brunner-Williams in Portland Maine'; Liu, Hong;
'ietf-provreg@cafax.se'
Subject: RE: TCP Mapping 

I understand how push can work with beep, but why is it a requirement to
work with the tcp transport? also isn't push with smtp only require a
corrdinated mbox?

I'd prefer we not muck with the tcp transport and find a method to get
push to work with all transports or settle on using beep because it is
already prepaired for push style messaging.

-rick