Original text:
the ULA link prefix. A failure to renew the DHCPv6-PD-provided OSNR prefix could be <del> because the SNAC network has been disconnected from one AIL and moved </del>  to a different AIL.  In this situation, if the new AIL also has IPv6 service and DHCPv6-PD service, the DHCPv6 client will get a clear indication that the old prefix is no longer valid.  However, it may be that no DHCPv6-PD service is available on the new link, either because it is an IPv4-only link or because it's an IPv6-capable link <del> that doesn't provide DHCPv6 service.  In this situation, if the SNAC </del>  network remains connected to the link and no DHCPv6 service appears, the DHCPv6-PD-provided OSNR prefix will eventually time out and be replaced.  The SNAC router SHOULD NOT attempt to replace it prior to this normal timeout process, because there is no benefit to changing <del> the OSNR prefix on the SNAC network in such a situation, and it's </del>  possible that the SNAC router will return to the other link before the OSNR prefix expires.

Reviewer comments:
As Esko pointed out, the term "SNAC network" crept in during editing a few weeks ago, and doesn't add value. This pull request changes all instances of "SNAC network" to "stub network".
In -05, the term "SNAC network" is now used but not defined. Could we use the more generic term "stub network" instead? I.e. a SNAC router is able to automatically connect a stub network to an infrastructure network. So the stub network served by this SNAC router is still a "stub network". Or we could use the term "SNAC network" for any stub network that gets automatically connected via a SNAC router. But doing this adds an extra term throughout the document: it's not possible to mass-replace all occurrences of "stub network".
See also which overlaps with this issue, but targets a specific definition paragraph.
Right, this happened when we added a bunch of text in the last interim, and I think was a mistake. I think we just want to use the term "stub network" and not invent a new term. The thing that's new here is the "SNAC router", not the stub network.
I agree - "stub network" makes more sense here.
removed

Revised text:
the ULA link prefix. A failure to renew the DHCPv6-PD-provided OSNR prefix could be  <ins> because the stub network has been disconnected from one AIL and moved </ins> to a different AIL.  In this situation, if the new AIL also has IPv6 service and DHCPv6-PD service, the DHCPv6 client will get a clear indication that the old prefix is no longer valid.  However, it may be that no DHCPv6-PD service is available on the new link, either because it is an IPv4-only link or because it's an IPv6-capable link  <ins> that doesn't provide DHCPv6 service.  In this situation, if the stub </ins> network remains connected to the link and no DHCPv6 service appears, the DHCPv6-PD-provided OSNR prefix will eventually time out and be replaced.  The SNAC router SHOULD NOT attempt to replace it prior to this normal timeout process, because there is no benefit to changing  <ins> the OSNR prefix on the stub network in such a situation, and it's </ins> possible that the SNAC router will return to the other link before the OSNR prefix expires.