typo in historic (RFC 2026 10.4) boilerplate

[hassanakbar4]

resolution_fixed type_defect | by julian.reschke@gmx.de

---

We currently have

"The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees."

This should be:

"The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns."

see http://tools.ietf.org/html/rfc2026#section-10.4

---

Issue migrated from trac:1 at 2021-10-20 19:18:59 +0500

[hassanakbar4]

@tom111.taylor@bell.net changed status from new to assigned

[hassanakbar4]

@tom111.taylor@bell.net changed owner from ` totom111.taylor@bell.net`

[hassanakbar4]

@lars.eggert@nokia.com commented

---

I actually believe that this may be an error in RFC2026 rather than the tool. At least "assignee" is the correct term that should be used. Check with mtr and the trust first before making this change?

(If we make this change, someone will also have to rev idnits.)

[hassanakbar4]

@julian.reschke@gmx.de commented

---

Replying to hassanakbar4/ttest#1 (comment:2):

I actually believe that this may be an error in RFC2026 rather than the tool. At least "assignee" is the correct term that should be used. Check with mtr and the trust first before making this change?

(If we make this change, someone will also have to rev idnits.)

I checked historic RFCs (for example, 2567), and they say "assigns".

This only affects historic documents (thus not today's idnits), so I'll proceed with this.

[hassanakbar4]

@julian.reschke@gmx.de changed status from assigned to closed

[hassanakbar4]

@julian.reschke@gmx.de set resolution to fixed

[hassanakbar4]

@julian.reschke@gmx.de commented

---

Fixed with [44].

[hassanakbar4]

@julian.reschke@gmx.de changed milestone from ` to1.35`