update list location

Author: brong

last-call-templates/PR-message-to-list.txt

@@ -1,11 +1,11 @@
 Hi all,
 
-We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3]. Their posting rights to the last-call@ietf.org mailing list have been restricted for the next 14 days.  We encourage everyone to review the IETF discussion list charter [4] and avoid postings that include uncivil commentary [5]. 
+We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3]. Their posting rights to the last-call@ietf.org mailing list have been restricted for the next 14 days.  We encourage everyone to review the IETF list charter [4] and avoid postings that include uncivil commentary [5]. 
 
 Thanks,
 [NAME] on behalf of the Team for last-call@ietf.org
 
-[1] https://www.ietf.org/how/lists/discussion/
+[1] https://www.ietf.org/how/lists/last-call/
 [2] [LINK to specific message 1]
 [3] [LINK to specific message 2]
 [4] https://www.rfc-editor.org/rfc/rfc9245.html

last-call-templates/PR-moderation-message-to-list.txt

@@ -1,11 +1,11 @@
 Hi all,
 
-We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3] under a new subject line but on the same topic against the direction from the IETF chair to bar posting on the thread [4]. Their posting rights to the last-call@ietf.org mailing list have been restricted for the next 14 days.  We encourage everyone to review the IETF discussion list charter [5] and our SOP [6]. 
+We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has determined that [NAME] has engaged in a pattern of abuse based on their recent messages to this list [2][3] under a new subject line but on the same topic against the direction from the IETF chair to bar posting on the thread [4]. Their posting rights to the last-call@ietf.org mailing list have been restricted for the next 14 days.  We encourage everyone to review the IETF list charter [5] and our SOP [6]. 
 
 Thanks,
 [NAME] on behalf of the Team for last-call@ietf.org
 
-[1] https://www.ietf.org/how/lists/discussion/
+[1] https://www.ietf.org/how/lists/last-call/
 [2] [LINK to specific message 1]
 [3] [LINK to specific message 2]
 [4] [LINK to the IETF chair message to the list]

last-call-templates/announcements-to-list.txt

@@ -1,10 +1,10 @@
 Hi all,
 
-We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF discussion list charter [3] and avoid postings that includes announcements of conferences, events, or activities that are not sponsored or endorsed by the IETF, IRTF, IAB, or the Internet Society as per [3]. 
+We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2]. We encourage everyone to review the IETF list charter [3] and avoid postings that includes announcements of conferences, events, or activities that are not sponsored or endorsed by the IETF, IRTF, IAB, or the Internet Society as per [3]. 
 
 Thanks,
 [NAME] on behalf of the Team for last-call@ietf.org
 
-[1] https://www.ietf.org/how/lists/discussion/
+[1] https://www.ietf.org/how/lists/last-call/
 [2] [LINK to specific message 1]
 [3] https://www.rfc-editor.org/rfc/rfc9245.html

last-call-templates/announcements.txt

@@ -9,6 +9,6 @@ We consider this an initial suggestion. We do not believe your message is part o
 Thanks,
 [NAME] on behalf of the Team for last-call@ietf.org
 
-[1] https://www.ietf.org/how/lists/discussion/
+[1] https://www.ietf.org/how/lists/last-call/
 [2] [LINK to specific message]
 [3] https://www.rfc-editor.org/rfc/rfc9245.html

last-call-templates/first-message-to-list.txt

@@ -1,11 +1,11 @@
 Hi all,
 
-We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent messages [2][3] with a request to take a voluntary cooling-off break. We encourage everyone to review the IETF discussion list charter [4] and avoid postings that include uncivil commentary [5]. 
+We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent messages [2][3] with a request to take a voluntary cooling-off break. We encourage everyone to review the IETF list charter [4] and avoid postings that include uncivil commentary [5]. 
 
 Thanks,
 [NAME] on behalf of the Team for last-call@ietf.org
 
-[1] https://www.ietf.org/how/lists/discussion/
+[1] https://www.ietf.org/how/lists/last-call/
 [2] [LINK to specific message 1]
 [3] [LINK to specific message 2]
 [4] https://www.rfc-editor.org/rfc/rfc9245.html

last-call-templates/first-message.txt

@@ -15,7 +15,7 @@ If you wish for us to make this message public, please let us know and we will r
 Thanks,
 [NAME] on behalf of the Team for last-call@ietf.org
 
-[1] https://www.ietf.org/how/lists/discussion/
+[1] https://www.ietf.org/how/lists/last-call/
 [2] https://www.rfc-editor.org/rfc/rfc9245.html
 [3] [LINK to specific message]
 [4] https://github.com/ietf/Moderators/blob/main/unprofessional-commentary.md

last-call-templates/first-moderation-message-to-list.txt

@@ -1,11 +1,11 @@
 Hi all,
 
-We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2] to last-call@ietf.org under a new subject line but on the same topic against the direction from the IETF Chair [3]. We encourage everyone to review the IETF discussion list charter [4] and our SOP [5]. 
+We wanted to let the list know that the Team for last-call@ietf.org (described in more detail at [1]) has been in touch with [NAME] off-list concerning their recent message [2] to last-call@ietf.org under a new subject line but on the same topic against the direction from the IETF Chair [3]. We encourage everyone to review the IETF list charter [4] and our SOP [5]. 
 
 Thanks,
 [NAME] on behalf of the Team for last-call@ietf.org
 
-[1] https://www.ietf.org/how/lists/discussion/
+[1] https://www.ietf.org/how/lists/last-call/
 [2] [LINK to specific message]
 [3] [LINK to the IETF chair message to the list]
 [4] https://www.rfc-editor.org/rfc/rfc9245.html

last-call-templates/first-moderation-thread-message.txt

@@ -4,14 +4,14 @@ I am writing to you on behalf of the Team for last-call@ietf.org. This message h
 
 We are reaching out to you because of your recent message to last-call@ietf.org [3] under a new subject line but on the same topic against the direction from the IETF Chair [4]. 
 
-We are concerned that this message is part of an emerging pattern of abuse, given our previous attempts to close the discussion on this topic for the time being. As such, we request that you take a voluntary 5-day break from posting to last-call@ietf.org as per our SOP [5]. We will be notifying last-call@ietf.org that we have been in touch with you. If we continue to see this pattern, we will temporarily restrict your posting rights to last-call@ietf.org for 14 days.
+We are concerned that this message is part of an emerging pattern of abuse, given our previous attempts to close the last-call on this topic for the time being. As such, we request that you take a voluntary 5-day break from posting to last-call@ietf.org as per our SOP [5]. We will be notifying last-call@ietf.org that we have been in touch with you. If we continue to see this pattern, we will temporarily restrict your posting rights to last-call@ietf.org for 14 days.
 
 If you wish for us to make this message public, please let us know and we will re-send it with last-call@ietf.org on cc.
 
 Thanks,
 [NAME] on behalf of the Team for last-call@ietf.org
 
-[1] https://www.ietf.org/how/lists/discussion/
+[1] https://www.ietf.org/how/lists/last-call/
 [2] https://www.rfc-editor.org/rfc/rfc9245.html
 [3] [LINK to specific message]
 [4] [LINK to the IETF chair message to the list]

last-call-templates/first-pattern-of-abuse-message.txt

@@ -15,7 +15,7 @@ If you wish for us to make this message public, please let us know and we will r
 Thanks,
 [NAME] on behalf of the Team for last-call@ietf.org
 
-[1] https://www.ietf.org/how/lists/discussion/
+[1] https://www.ietf.org/how/lists/last-call/
 [2] https://www.rfc-editor.org/rfc/rfc9245.html
 [3] [LINK to specific message]
 [4] https://github.com/ietf/Moderators/blob/main/unprofessional-commentary.md

last-call-templates/forum-to-list.txt

@@ -1,13 +1,13 @@
 Hi all,
 
-We wanted to let the list know that the Last Call team (described in more detail at [1]) consider this thread [2] to be more appropriate for this [LIST][3]. And as per the IETF discussion list charter [4], we suggest that the discussions should be moved to the more specific forum identified. 
+We wanted to let the list know that the Last Call team (described in more detail at [1]) consider this thread [2] to be more appropriate for this [LIST][3]. And as per the IETF list charter [4], we suggest that the last-calls should be moved to the more specific forum identified. 
 
 [The Last Call team has been in touch with the [LIST] administers off-list.] (if required)
 
 Thanks,
 [NAME] on behalf of the Team for last-call@ietf.org
 
-[1] https://www.ietf.org/how/lists/discussion/
+[1] https://www.ietf.org/how/lists/last-call/
 [2] [LINK to thread]
 [3] [LINK to join LIST]
 [4] https://www.rfc-editor.org/rfc/rfc9245.html