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


To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Date: Thu, 21 Jun 2001 13:48:13 -0400
Sender: owner-ietf-provreg@cafax.se
Subject: RE: Poll response data

>-----Original Message-----
>From: Sheer El-Showk [mailto:sheer@saraf.com]
>Sent: Thursday, June 21, 2001 12:33 PM
>To: Klaus Malorny
>Cc: Rick H Wesson; Hollenbeck, Scott; 'ietf-provreg@cafax.se'
>Subject: Re: Poll response data

[snip]

>That implementation detail aside, I think its still possible to address
>this concern within the protocol.  I may have missed it, but I didn't see
>any reference to a message timestamp in the EPP-03 discussion of <poll>.
>I think each poll resposne should include two new timestamps.  The first
>will be the time that the queue was most recently updated; the second will
>be the time that particular queued message was placed in the queue.  That
>way, the registrar has all the information it requires about the queued
>messages and can descide in a more informed manner whether or not it has
>to make further queries.

This could be done pretty easily by adding two child elements to the
existing <msgQ> element: <qHead> to note when the message being retrieved
was enqueued, and <qTail> to note when the last message was enqueued.

<Scott/>

Home | Date list | Subject list