Split "Issuance and Renwal" into Policy and Technical categories

[riking]

Continuing the discussion from Internationalized Domain Names:

@eih

What about internationalized domain names under sensible ccTLDs which do not allow homoglyphs?

Like it is not possible to register аbc.de or аbc.fi (аbc.de or аbc.fi) containing a Cyrillic a as these ccTLDs accept only a limited set of accented letters and such but not symbols, other scripts or anything like that.

For this kind of ccTLDs there are no need for extra homoglyph tests, as registry authorities have prevented them altogether.

I think that the Issuance & Renewal category is a bit broad, and should be split into two categories.

One category for technical & client problems with issuance/renewal, the second category for policy decisions: the above topic, and things like "how often do certificates last", "when should a certificate be renewed".

Examples:

• Implementation
  Re-run Letsencrypt Client installs on existing installations? - #3 by eva2000
  Manual authenticator - way to automate the ACME Challenge file creation? - #3 by eva2000
  LE replacing a current certificate - #22 by schoen
  Preventing a attacker with DNS control from issueing certificates - #6 by schoen
  Letsencrypt & FreeBSD

• Issuance Policy
  Internationalized Domain Names - #20 by eih
  Are they limitations on who can use Let's Encrypt? - #5 by josh
  How do you confirm the person asking for the certificate actually owns the domain? - #20 by schoen
  Client auto renewals and failure notifications? - #5 by schoen
  Shouldn't verification via DNS record be a priority? - #7 by shred

I think 5 examples of each type is enough

Would like suggestions on the names.

@jsha what say you?

[jsha]

@riking: The split sounds good to me. How about “Issuance policies” and “Issuance: Technical Questions?”

[NOYB]

Think I’d leave off the “questions” and just go with Issuance Technical.

[riking]

Done, I just split the categories.