Puneet, that sounds perfect. Thanks for reconsidering this.
Barry
On Wed, Sep 18, 2019 at 8:14 AM Puneet Sood wrote:
>
> On Sat, Sep 14, 2019 at 8:46 AM Barry Leiba wrote:
> >
> > > > I wonder if it makes sense to be more explicit here that one isn’t
> > > > meant to keep using expired data fo
On Sat, Sep 14, 2019 at 8:46 AM Barry Leiba wrote:
>
> > > I wonder if it makes sense to be more explicit here that one isn’t
> > > meant to keep using expired data forever, but is expected to keep
> > > trying to refresh it. So, maybe?:
> > >
> > > NEW
> > > If the data is unable to be
> >
Barry,
Thanks for the detailed review. The editorial comments and security
considerations comment will be addressed in a new draft I will be
pushing.
On Wed, Sep 11, 2019 at 12:06 PM Barry Leiba wrote:
>
> I am handling this document as responsible AD, as Warren is a
> co-author and so must recu
> > I wonder if it makes sense to be more explicit here that one isn’t
> > meant to keep using expired data forever, but is expected to keep
> > trying to refresh it. So, maybe?:
> >
> > NEW
> > If the data is unable to be
> > authoritatively refreshed when the TTL expires, the record
On Wed, Sep 11, 2019 at 12:06:23PM -0400,
Barry Leiba wrote
a message of 75 lines which said:
> I wonder if it makes sense to be more explicit here that one isn’t
> meant to keep using expired data forever, but is expected to keep
> trying to refresh it. So, maybe?:
>
> NEW
> If the da
I am handling this document as responsible AD, as Warren is a
co-author and so must recuse himself. I’m not sure how I missed the
publication request, but miss it I did, and thanks to Warren for
pinging me.
Thanks for a very well-written and clear document. I have only some
minor editorial comme
