November 2018
Proposed changes to Ops-AnnounceA consultation on the maintenance of the Ops-Announce mailing list.
This document presents proposed changes to the LINX MoU for Ops-Announce.
- The goal is to allow members to subscribe to LAN specific announcements.
- The proposal is that the MoU section 4.6.1 will be changed to refer to a non-constitutional reference document that details the LAN announcement make up.
- See the LAN Announcements Reference Document which is now available.
The Change in Detail
| Current MoU | Proposed MoU |
| 4.6 You will make sure that at least one member of your staff is subscribed to the following mailing lists: | 4.6 You will make sure that at least one member of your staff is subscribed to the following mailing lists: |
| 4.6.1 ops-announce@wordpress-314780-2068383.cloudwaysapps.com mailing list, which is intended to carry announcements of an urgent operational nature; | 4.6.1 The LAN announcement(s) mailing lists, specific to your peering service or services, where the mailing list details can be found in the ‘LAN announcements reference document’. |
November 2018
Proposed changes to peering request response timesA consultation on peering request response times.
This document presents proposed changes to the LINX MoU for response times to peering requests.
- A large part of the membership do not meet the criteria as set out in Article 4.4 in the MoU.
- LINX currently would have +40% of its members in breach of the MoU and should proceed to sanction / disconnect them (this is clearly not in the interest of members).
- Having a clause in the MoU that states breach but is not enforceable is also not ideal.
- The proposal is to simply remove that clause from the MoU and, as it is no longer referenced, also remove the requirement to provide an email address to receive peering requests.
The Change in Detail
| Current MoU | Proposed MoU |
| 4.4 You will confirm receipt of a peering request made to the email address specified in 4.3.2 above by any LINX Member within two working days of the request. An auto-responder is considered acceptable. Failure to comply with this clause 4.4 shall be regarded as a material breach of this MoU. | 4.4. To remove clause 4.4 in its entirety. |
| 4.3.2 an email address for which requests for peering should be sent, | 4.3.2 To remove clause 4.3.2 in its entirety. As there is no longer reference to this in the MoU, it is not appropriate to refer to it. |
Next steps
These changes were presented in outline at LINX102, where no comments were raised. They will be presented as formal resolutions at the EGM to be held on 20th November 2018 as part of the LINX103 member conference.
If any LINX member wishes to comment on these changes, please contact the LINX member relations team.
