If LIR is pronounced “Elle-Eye-Are” (which is how I pronounce it) then “an LIR” is correct. It would only be “a LIR” if you pronounce it “Lear”.
http://blog.apastyle.org/apastyle/2012/04/using-a-or-an-with-acronyms-and-abbreviations.html Scott > On May 4, 2018, at 1:42 AM, Ian Dickinson <[email protected]> > wrote: > > There are a number of occurrences of "an LIR" (and also "An LIR") throughout > the document that should be changed to "a LIR". > Presumably only s/Organisation/LIR/ was done. > > Other than this grammar nit, I am happy the text matches the goal and I > support it. > > Ian > > -----Original Message----- > From: address-policy-wg <[email protected]> On Behalf Of > Marco Schmidt > Sent: 03 May 2018 16:08 > To: [email protected] > Subject: [address-policy-wg] 2018-01 Review Phase (Organisation-LIR > Clarification in IPv6 Policy) > > Dear colleagues, > > Policy proposal 2018-01, "Organisation-LIR Clarification in IPv6 Policy" is > now in the Review Phase. > > This proposal aims to clarify the wording used in ripe-699 regarding terms > such as "organisation" and "LIR". > > The proposal has been updated following the last round of discussion and is > now at version v2.0. Some of the differences from version v1.0 include: > - Clarifies when the subsequent allocation policy applies > - Fixing some typos > > The RIPE NCC has prepared an impact analysis on this latest proposal version > to support the community’s discussion. You can find the full proposal and > impact analysis at: > https://www.ripe.net/participate/policies/proposals/2018-01 > > And the draft documents at: > https://www.ripe.net/participate/policies/proposals/2018-01/draft > > As per the RIPE Policy Development Process (PDP), the purpose of this four > week Review Phase is to continue discussing the proposal, taking the impact > analysis into consideration, and to review the full draft RIPE Policy > Document. > > At the end of the Review Phase, the WG Chairs will determine whether the WG > has reached rough consensus. It is therefore important to provide your > opinion, even if it is simply a restatement of your input from the previous > phase. > > We encourage you to read the proposal, impact analysis and draft document and > send any comments to <[email protected]> before 1 June 2018. > > Kind regards, > > Marco Schmidt > Policy Officer > RIPE NCC > > Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum > > > Disclaimer > > This email is private and may be confidential and is intended for the > recipient only. If misdirected please notify us by telephone and return and > confirm that it has been deleted from your system and any copies destroyed. > If you are not the intended recipient you are strictly prohibited from using, > printing, copying, distributing or disseminating this email or any > information within it. We use reasonable endeavours to virus scan all emails > leaving our organisation but no warranty is given that this email and any > attachments are virus free. You should undertake your own virus checking. The > right to monitor email communication through our networks is reserved by us.
