[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
From: "Liu, Hong" <Hong.Liu@neustar.biz>
Date: Mon, 8 Jul 2002 09:12:24 -0500
Sender: owner-ietf-provreg@cafax.se
Subject: RE: EPP PUSH: Session Setup Semantics

Scott,

Thanks for the comment. I agree with you on this. The upcoming draft will
take this approach, and also discuss the interactions between push and poll.


Cheers,

--Hong

-----Original Message-----
From: Hollenbeck, Scott [mailto:shollenbeck@verisign.com]
Sent: Monday, July 08, 2002 9:06 AM
To: 'Liu, Hong'; 'ietf-provreg@cafax.se'
Subject: RE: EPP PUSH: Session Setup Semantics


> Suppose both the server and the client agree on supporting 
> EPP PUSH in this
> session, there are two possible semantics:
> a. Push-only semantics. The session can only be used for server-pushed
> messages. The client cannot use <poll> in this session to 
> retrieve messages
> from the server.
> b. Mixed semantics. Both server-push and client-poll are allowed.
> In both cases, I think it is reasonable to assume that other 
> EPP commands
> and responses are allowed.
> 
> Which semantics should we pick, (a) or (b)? 
> Is this a registry policy issue or a standardization issue?

I believe that (b) is the proper approach.  Polling is a "standard" protocol
feature that you can't just eliminate, so I see it as a standardization (and
thus interoperability) issue.

-Scott-

Home | Date list | Subject list