[Tools-discuss] Re: Datatracker question

[Bob Hinden <[e-mail]>]

Robert,

> On Aug 22, 2025, at 1:03 PM, Robert Sparks <[e-mail]> wrote:
> 
> Hi Bob - this was introduced in this week's release at the IESG's request at https://github.com/ietf-tools/datatracker/issues/9142.
> 
> The PR that brought it in was https://github.com/ietf-tools/datatracker/pull/9322.

I wasn’t aware of any of this.   Was this discussed on the w.g. chairs list, or did I miss it.   Assuming I didn’t miss it, seems odd that it was discussed on w.g. chairs list to see if this was desired.

I can think of chases where the automatic notification is going to be wrong.   Like what I did, or where the chairs want a different length of time for the adoption call.

Was there any announcement to the w.g. chairs that this change had been made?   Are there any other changes like this?

> 
> You can't currently cause it to not be sent.

I think that is a bug.

> 
> You have an interesting use case for changing the state after the fact that we should figure out, but in your case, why did you bother to set the call for adoption state if you were at the end of the period?

It happened because we are about to close the adoption call and I noticed we had not set the state earlier.    

Bob


> 
> RjS
> 
> On 8/22/25 2:02 PM, Bob Hinden wrote:
>> Hi,
>> 
>> I belatedly went to the datatracker to change the state of a draft to “Call for Adoption by WG”.  The call for adoption had been done two weeks earlier.
>> 
>> Much to my surprise the datatracker, besides changing the state as expected, sent a new adoption call to the list.  See below.
>> 
>> Why did the happen?  It didn’t give me any indication that it was going to do this.   How do I turn it off?  When was this introduced?
>> 
>> Bob
>> 
>> 
>>> Begin forwarded message:
>>> 
>>> From: Bob Hinden via Datatracker <[e-mail]>
>>> Subject: Call for adoption: draft-zhang-6man-ipv6-address-resolution-yang-00 (Ends 2025-09-05)
>>> Date: August 22, 2025 at 11:38:44 AM PDT
>>> To: <[e-mail]>, <[e-mail]>, <[e-mail]>
>>> Resent-From: <[e-mail]>
>>> Resent-To: [e-mail], [e-mail]
>>> Reply-To: Bob Hinden <[e-mail]>
>>> 
>>> 
>>> Subject: Call for adoption: draft-zhang-6man-ipv6-address-resolution-yang-00
>>> (Ends 2025-09-05)
>>> 
>>> This message starts a 2-week Call for Adoption for this document.
>>> 
>>> Abstract:
>>>   This document defines a YANG data model to configure and manage IPv6
>>>   Neighbor Discovery (ND) and related functions, including IPv6 address
>>>   resolution, redirect function, proxy Neighbor Advertisement, Neighbor
>>>   Unreachability Detection (NUD), Duplicate Address Detection (DAD),
>>>   SEcure Neighbor Discovery (SEND), and Secure ND Proxy.
>>> 
>>> File can be retrieved from:
>>> https://datatracker.ietf.org/doc/draft-zhang-6man-ipv6-address-resolution-yang/
>>> 
>>> Please reply to this message keeping [e-mail] in copy by indicating
>>> whether you support or not the adoption of this draft as a WG document.
>>> Comments to motivate your preference are highly appreciated.
>>> 
>>> Authors, and WG participants in general, are reminded of the Intellectual
>>> Property Rights (IPR) disclosure obligations described in BCP 79 [2].
>>> Appropriate IPR disclosures required for full conformance with the provisions
>>> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
>>> Sanctions available for application to violators of IETF IPR Policy can be
>>> found at [3].
>>> 
>>> Thank you.
>>> [1] https://datatracker.ietf.org/doc/bcp78/
>>> [2] https://datatracker.ietf.org/doc/bcp79/
>>> [3] https://datatracker.ietf.org/doc/rfc6701/
>>> 
>>> 
>> 
>> -----------------------------------------------
>> Tools-discuss mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>> https://mailarchive.ietf.org/arch/browse/tools-discuss/