[TF-AIDN] Fwd: [Ext] Re: minutes of the call (11-06-2020)

Nabil Benamar benamar73 at gmail.com
Thu Jul 30 10:51:33 CEST 2020

Dear Ali,

Yes, it seems that we need to follow the terminology used by Unicode to
avoid confusion!

Are you ok with the final documents? Do you have further comments?

Eïd Mubarak!

On Thu, Jul 30, 2020, 09:07 Ali M. AlHoshaiyan <ahoshaiyan at citc.gov.sa>

> Thank you Dr. Nabil,
> I am not actually sure why they are called that, but you are right they
> should be called Arabic Digits instead, but for the sake of not confusing
> people using the LGR file, especially who are foreign to the Arabic script,
> in my humble opinion, I prefer to keep them as Common.
> In Saudi Arabia, and in most gulf countries, we use them interchangeably
> (Arabic and Arabic-Indic) so in software we write we have to accept both
> and then convert Arabic-Indic at the backend to Arabic Digits to keep data
> consistent. This issue arise with macOS and iOS users as apple let them
> enter Arabic-Indic digits when using the Arabic (Saudi Arabia) keyboard
> Sincerely,
> Ali
> From: Nabil Benamar <benamar73 at gmail.com>
> Date: Monday, July 27, 2020 at 11:14 AM
> To: "Ali M. AlHoshaiyan" <ahoshaiyan at citc.gov.sa>
> Cc: Sarmad Hussain <sarmad.hussain at icann.org>, "TF-AIDN (tf-aidn at meswg.org)"
> <tf-aidn at meswg.org>
> Subject: Re: [TF-AIDN] Fwd: [Ext] Re: minutes of the call (11-06-2020)
> Thank you Dr. ALi for your detailed feedback!
> I'm wondering why we call the Arabic digits(numbers) by common digits ??
> The "true" name of the following digits 0 1 2 3 is the Arabic numbers.
> Please note that in north-western african countries (Morocco, Algeria,
> Tunisia, Libya and Mauritania) we are using these digits and not the
> Arabic-indic ones.
> Best regards
> Nabil Benamar
> -------------------
> نبيل بنعمرو
> On Thu, Jul 23, 2020 at 2:15 PM Ali M. AlHoshaiyan <ahoshaiyan at citc.gov.sa
> <mailto:ahoshaiyan at citc.gov.sa>> wrote:
> Thank you Dr. Sarmad,
> Thank you Dr. Nabil,
> I have incorporated the last changes added to the Arabic language LGR (new
> dispositions) and updated references. These changes hopefully will allow
> optional activation of some rules
> Thank you taking this into consideration,
> Kind regards,
> Ali
> From: <tf-aidn-bounces at meswg.org<mailto:tf-aidn-bounces at meswg.org>> on
> behalf of Nabil Benamar <benamar73 at gmail.com<mailto:benamar73 at gmail.com>>
> Date: Thursday, July 16, 2020 at 10:28 AM
> To: "TF-AIDN (tf-aidn at meswg.org<mailto:tf-aidn at meswg.org>)" <
> tf-aidn at meswg.org<mailto:tf-aidn at meswg.org>>
> Subject: [TF-AIDN] Fwd: [Ext] Re: minutes of the call (11-06-2020)
> Dear TF-AIDN members,
> We have a new update sent by Dr. Sarmad.
> Please see below.
> ---------- Forwarded message ---------
> From: Sarmad Hussain <sarmad.hussain at icann.org<mailto:
> sarmad.hussain at icann.org><mailto:sarmad.hussain at icann.org<mailto:
> sarmad.hussain at icann.org>>>
> Date: Mon, Jul 13, 2020, 08:52
> Subject: Re: [Ext] Re: [TF-AIDN] minutes of the call (11-06-2020)
> To: Nabil Benamar <benamar73 at gmail.com<mailto:benamar73 at gmail.com><mailto:
> benamar73 at gmail.com<mailto:benamar73 at gmail.com>>>
> Cc: Fahd Batayneh <fahd.batayneh at icann.org<mailto:fahd.batayneh at icann.org
> ><mailto:fahd.batayneh at icann.org<mailto:fahd.batayneh at icann.org>>>
> Thank you Nabil.
> We have also updated the Arabic script LGR, in addition to the Arabic
> language LGR.  That is the same as RZ-LGR, with the addition of digits and
> hyphen.  I am attaching this for review by TF-AIDN as well.
> We look forward to working with TF-AIDN to finalize the Arabic script LGR
> and the Arabic language LGR before taking it to public comment.  We look
> forward to the feedback by 31 July.
> Regards,
> Sarmad
> 3 2020-07-23 und-Arab 6.3.0 Reference Label Generation Rules for the
> Arabic Script
> Overview
> This document specifies a reference set of Label Generation Rules (LGR)
> for the Arabic script for the second level. The starting point for the
> development of this LGR can be found in the related Root Zone LGR
> [RZ-LGR-3-Arab]. For details and additional background on the script, see
> TF-AIDN, "Proposal for Arabic Script Root Zone LGR", Version 3.4, 18
> November 2015 [Proposal-Arabic]. The format of this file follows [RFC 7940].
> This is a DRAFT document released for public comments and not final.
> Please see the announcement on the ICANN website for public comments on the
> Second Level Reference LGRs for details on how to submit comments.
> Repertoire
> The repertoire includes the 128 code points for letters used by languages
> that are actively written in the Arabic script as described in Section 3.2
> of [Proposal-Arabic]. For the second level, the repertoire has been
> augmented with the HYPHEN-MINUS, and three sets of decimal digits:
>   *   European (common) digits
>   *   Arabic-Indic digits
>   *   Extended Arabic-Indic digits
> for a total of 159 repertoire elements.
> The repertoire excludes code points for which TF-AIDN was unable to find
> sufficient evidence of use (see Appendix F in [Proposal-Arabic]). The
> repertoire is described in Section 3.2 of [Proposal-Arabic] and a subset of
> [Unicode 6.3].
> This LGR does not include combining marks or code point sequences. All
> combining marks have been excluded for these reasons:
>   *   First, they can significantly overproduce and would require
> additional rules to contain them effectively, complicating the design.
>   *   Second, even where they are required for some languages, they are
> optional for others.
>   *   Third, this also circumvents the issue regarding duplication between
> some precomposed code points and combining sequences raised by [IAB].
> For further details, see Section 3.2, "Code point repertoire included" in
> [Proposal-Arabic]. (The proposal cited has been adopted for the Arabic
> script portion of the Root Zone LGR.)
> Each code point or range is tagged with the script or scripts that the
> code point is used with, and one or more references documenting sufficient
> justification for inclusion in the repertoire, see "References" below.
> Comments identify the languages using the code point.
> Variants
> This reference LGR is designed for use in zones shared by more than one
> script. Where appropriate, cross-script variants have been defined to
> mutually exclude labels from different scripts that could otherwise be
> substituted by the users. Once a label has been delegated for one script,
> any variant labels from other scripts consisting of cross-script variants
> would be blocked. Any label containing at least one code point that is not
> a cross-script variant would be considered distinct. Because of that, even
> large numbers of defined cross-script variants generally do not lead to a
> high percentage of labels experiencing a collision.
> Digit Variants: The two sets of Arabic-specific digits are treated as
> semantic variants of each other and of the corresponding common (ASCII)
> digits. By transitivity, they are also semantic variants of any native
> digits in scripts that also include the common digits. Because of the
> restriction on leading digits, most labels would contain a unique code
> point in addition to any digits, thus no variant labels would actually
> result from any pro-forma cross-script variants. To keep digit variant sets
> manageable in zones where multiple scripts are present, no attempt has been
> made at identifying cross-script variants among digits of different numeric
> value or between a digit in one script and a letter in another, such as
> between digit zero and Latin letter 'o'.
> Variant Disposition: This LGR includes "blocked" and "allocatable"
> variants, assigned according to Section 4, "Final recommendation of
> variants for Top Level Domains (TLDs)" in [Proposal-Arabic]. These
> recommendations balance the desire to minimize the number of possible
> allocatable variants with the need to keep the definition of variants
> simple. See also the comments given in the listing.
> For the second level, an additional variant type "activated" is defined,
> so that certain variant labels are automatically delegated to improve user
> experience.
> The specification of variants in this reference LGR follows the guidelines
> in [RFC 8228].
> Character Classes
> This proposal defines the following named character classes:
>   *   common-digits — ASCII digits: U+0030 to U+0039
>   *   arabic-indic-digits — Arabic-Indic digits used with Arabic: U+0660
> to U+0669
>   *   extended arabic-indic-digits — Arabic-Indic digits used with other
> languages: U+06F0 to U+06F9
> Whole Label Evaluation (WLE) and Context Rules
> Common Rules
>   *   Hyphen Restrictions — restrictions on the allowable placement of
> hyphens (no leading/ending hyphen and no hyphen in positions 3 and 4).
> These restrictions are described in section of RFC 5891 [150]. They
> are implemented here as context rule on U+002D (-) HYPHEN-MINUS.
>   *   Leading Combining Marks — restrictions on the allowable placement of
> combining marks (no leading combining mark). This rule is described in
> section of RFC 5891 [150].
>   *   One non-ASCII code point — An IDN label must contain one non-ASCII
> code point, as described in Section 4.2.4 of RFC 5891 [150].
> Right-To-Left Rules
>   *   leading-digit— RFC 5893 restrictions on the allowable placement of
> digits (no leading digit), see section 2.1 of [160]; implemented here as a
> context rule on each digit.
>   *   digit-mixing — no mixing between different digit sets (European,
> Arabic-Indic, and Extended-Arabic-Indic digits) is allowed (see section 2.4
> of RFC 5893 [160]); implemented here as a WLE rule with associated action.
> Default Actions
> Actions include the default actions for LGRs as well as that needed to
> invalidate labels with misplaced combining marks. They are marked with ⍟.
> For a description see [RFC 7940].
> Arabic-specific Rules and Actions
> This LGR includes WLE rules and actions specific to the Arabic script. See
> Section 5, "Whole Label Evaluation (WLE) rules" in [Proposal-Arabic]. As
> specified, the rules and actions serve to prevent the mixing of two
> variants of the same code point within the same label. This reduces
> overproduction of variant labels. The rules are listed here with the
> numbers given in Table 17 in [Proposal-Arabic]. See also the comments given
> for each rule or action.
>   *   no-mix-kaf-keheh — WLE Rule 1: do not mix Arabic letters KAF and
> KEHEH in the same label
>   *   no-mix-kaf-swash — WLE Rule 2: do not mix Arabic letters KAF and
> SWASH KAF in the same label
>   *   no-mix-alef-maksura-farsi-yeh — WLE Rule 3: do not mix Arabic
> letters ALEF MAKSURA and FARSI YEH in the same label
>   *   no-mix-heh-goal — WLE Rule 4: do not mix Arabic letters HEH and HEH
> GOAL in the same label
>   *   no-mix-heh-goal-ae — WLE Rule 5: do not mix Arabic letters HEH GOAL
> and AE in the same label
>   *   no-mix-heh-ae — WLE Rule 6: do not mix Arabic letters HEH and AE in
> the same label
>   *   no-mix-heh-doachashmee — WLE Rule 7: do not mix Arabic letters HEH
> and HEH DOACHASHMEE in the same label
>   *   no-mix-teh-marbuta-goal — WLE Rule 8: do not mix Arabic letters TEH
> MARBUTA and FEH WITH DOT MOVED BELOW in the same label
>   *   no-mix-noon-with-three-dots-above-yeh-with-three-dots-below — WLE
> Rule 9: do not mix Arabic letters NOON WITH THREE DOTS ABOVE and YEH WITH
> THREE DOTS BELOW in the same label
>   *   no-mix-peh-noon-with-three-dots-above — WLE Rule 10: do not mix
> Arabic letters PEH and NOON WITH THREE DOTS ABOVE in the same label
>   *   no-mix-feh-with-dot-moved-below — WLE Rule 11:do not mix Arabic
> letters FEH and FEH WITH DOT MOVED BELOW in the same label
>   *   no-mix-qaf-with-dot-above — WLE Rule 12: do not mix Arabic letters
> QAF and QAF WITH DOT ABOVE in the same label
>   *   no-mix-feh-qaf-with-dot-above — WLE Rule 13: do not mix Arabic
> letters FEH and QAF WITH DOT ABOVE in the same label
>   *   no-mix-kaf-with-ring-gaf — WLE Rule 14: do not mix Arabic letters
> KAF WITH RING and GAF in the same label
>   *   no-mix-kaf-with-ring-keheh-with-three-dots-above — WLE Rule 15: do
> not mix Arabic letters KAF WITH RING and KEHEH WITH THREE DOTS ABOVE
>   *   no-mix-gaf-keheh-with-three-dots-above — WLE Rule 16: do not mix
> Arabic letters GAF and KEHEH WITH THREE DOTS ABOVE in the same label
> Arabic Script-specific Actions
> One action is specific to a non-default variant mapping type used in this
> LGR:
>   *   if at least one variant is in {activated}, force delegation for
> certain in-repertoire variants
> The disposition for this action is "activated" which implies mandatory
> delegation of the variant label. This variant type applies to the variant
> mappings between the three sets of digits.
> Methodology and Contributors
> This reference LGR for Arabic for the 2nd Level has been developed by
> Michel Suignard and Asmus Freytag, based on the Root Zone LGR for Arabic
> and information contained or referenced therein, see [RZ-LGR-3-Arab].
> Suitable extensions for the second level have been applied according to the
> [Guidelines]. The original proposal for an Arabic Script Root Zone LGR
> [Proposal-Arabic] that this LGR is based on, was developed by the Task
> Force for Arabic Script IDNs [TF-AIDN].
> For more information on methodology and contributors to the underlying
> Root Zone LGR, see [Proposal-Arabic], as well as [RZ-LGR-Overview].
> References
> The following general references are cited in this document:
> [Guidelines]
> ICANN, "Guidelines for Developing Reference LGRs for the Second Level,
> (Los Angeles, California: ICANN, 27 May 2020),
> https://www.icann.org/en/system/files/files/lgr-guidelines-second-level-06jan16-en.pdf
> [IAB]
> Internet Architecture Board (IAB), "IAB Statement on Identifiers and
> Unicode 7.0.0"
> https://www.iab.org/documents/correspondence-reports-documents/2015-2/iab-statement-on-identifiers-and-unicode-7-0-0/
> [MSR-4
> <https://www.iab.org/documents/correspondence-reports-documents/2015-2/iab-statement-on-identifiers-and-unicode-7-0-0/%5BMSR-4>
> ]
> Integration Panel, "Maximal Starting Repertoire — MSR-4 Overview and
> Rationale", 7 February 2019,
> https://www.icann.org/en/system/files/files/msr-4-overview-25jan19-en.pdf
> [Proposal-Arabic]
> TF-AIDN, "Proposal for Arabic Script Root Zone LGR", Version 3.4, 18
> November 2015
> https://www.icann.org/en/system/files/files/arabic-lgr-proposal-18nov15-en.pdf
> [RFC 6365]
> Hoffman, P. and J. Klensin, "Terminology Used in Internationalization in
> the IETF", BCP 166, RFC 6365, DOI 10.17487/RFC6365, September 2011,
> http://www.rfc-editor.org/info/rfc6365
> [RFC 7940]
> Davies, K. and A. Freytag, "Representing Label Generation Rulesets Using
> XML", RFC 7940, August 2016, http://www.rfc-editor.org/info/rfc7940
> [RFC 8228]
> A. Freytag, "Guidance on Designing Label Generation Rulesets (LGRs)
> Supporting Variant Labels", RFC 8228, August 2017,
> https://www.rfc-editor.org/info/rfc8228
> [RZ-LGR-Overview
> <https://www.rfc-editor.org/info/rfc8228%5BRZ-LGR-Overview>]
> Integration Panel, "Root Zone Label Generation Rules - LGR-3: Overview and
> Summary", 01 March 2020 (PDF),
> https://www.icann.org/sites/default/files/lgr/lgr-3-overview-10jul19-en.pdf
> [RZ-LGR-3-Arab]
> ICANN, Root Zone Label Generation Rules for the Arabic Script (und-Arab) ,
> 10 July 2019 (XML)
> https://www.icann.org/sites/default/files/lgr/lgr-3-arabic-script-10jul19-en.xml
> [Unicode 6.3]
> The Unicode Consortium. The Unicode Standard, Version 6.3.0, (Mountain
> View, CA: The Unicode Consortium, 2013. ISBN 978-1-936213-08-5)
> http://www.unicode.org/versions/Unicode6.3.0/
> [TF-AIDN <http://www.unicode.org/versions/Unicode6.3.0/%5BTF-AIDN>]
> Blog, "Task Force for Arabic Script IDNs"
> https://www.icann.org/news/blog/what-is-the-task-force-on-arabic-script-idns-tf-aidn-up-to
> For references consulted particularly in designing the repertoire for the
> Arabic script for the second level. please see details in the Table of
> References below. References [0] to [12] refer to the Unicode Standard
> versions in which the corresponding code points were initially encoded.
> References [100] and above correspond to sources justifying the inclusion
> of the corresponding code points. Entries in the table may have multiple
> source reference values.
> ]]> The Unicode Standard 1.1 The Unicode Standard 3.0 The Unicode Standard
> 4.1 The Unicode Standard 5.1 The Unicode Standard 6.0 The Unicode Standard
> 6.1 RFC 5564 Linguistic Guidelines for the Use of the Arabic Language in
> Internet Domains https://tools.ietf.org/html/rfc5564 Omniglot Hausa
> http://omniglot.com/writing/hausa.htm Omniglot Kashmiri
> http://omniglot.com/writing/kashmiri.htm Omniglot Kazakh
> http://omniglot.com/writing/kazakh.htm Omniglot Khowar
> http://omniglot.com/writing/khowar.htm Omniglot Kirghiz
> http://omniglot.com/writing/kirghiz.htm Omniglot Kurdish
> http://omniglot.com/writing/kurdish.htm Omniglot Malay
> http://omniglot.com/writing/malay.htm Omniglot Pashto
> http://omniglot.com/writing/pashto.htm Omniglot Persian(Farsi)
> http://omniglot.com/writing/persian.htm Omniglot Saraiki
> http://omniglot.com/writing/saraiki.htm Omniglot Sindhi
> http://omniglot.com/writing/sindhi.htm Omniglot Urdu
> http://omniglot.com/writing/urdu.htm Omniglot Wolof
> http://omniglot.com/writing/wolof.htm Omniglot Uyghur
> https://omniglot.com/writing/uyghur.htm Unicode, Kashmiri, Yeh
> http://www.unicode.org/L2/L2009/09215-kashmiri.pdf Unicode, Chad ANT, pp.
> 19-20 http://www.unicode.org/L2/L2010/10288r-arabic-proposal.pdf Unicode,
> DPLN, p.21 http://www.unicode.org/L2/L2010/10288r-arabic-proposal.pdf
> Unicode, Jawi and Moroccan Arabic GAF,
> http://www.unicode.org/L2/L2003/03176-gafs.pdf Unicode, Chadian, p.5
> http://www.unicode.org/L2/L2010/10288r-arabic-proposal.pdf Wolof, Paul
> Timothy
> http://paul-timothy.net/pages/ajamisenegal/primers/je_sais_le_wolofal_harmattan_20-oct-2015_a4.pdf
> Hausa, pp. 261-289 Warren-Rothlin, Andy (2014): West African scripts and
> Arabic-script orthographies in socio-political context. Meikal Mumin, Kees
> (C.) H. Versteegh (Eds.): The Arabic script in Africa. Studies in the use
> of a writing system. Leiden, Boston: Brill (Studies in Semitic Languages
> and Linguistics, 71) Mandika, Bamana, pp. 225-260 Vydrin, Valentin
> Feodos'evich; Dumestre, Gérard (2014): Manding Ajami samples. In Meikal
> Mumin, Kees (C.) H. Versteegh (Eds.): The Arabic script in Africa. Studies
> in the use of a writing system. Leiden, Boston: Brill (Studies in Semitic
> Languages and Linguistics, 71) Ethiopian, Wetter, Andreas (2006): Arabic in
> Ethiopia. In Kees (C.) H. Versteegh (Ed.): Encyclopedia of Arabic Language
> and Linguistics. Volume I. A-Ed, vol. 2. With assistance of Mushira Eid,
> Alaa Elgibali, Manfred Woidich, Andrzej Zaborski. Leiden: E. J. Brill, pp.
> 51-56. Western Arabic, Qaf with three dots above, city of Gabes, Tunisia
> Urdu, Heh goal with hamza above, Section 3 in
> http://www.columbia.edu/~mk2580/urdu_section/handouts/izafat.pdf Urdu,
> Teh marbuta goal, Code point UZT 76 of Urdu Zabta Takhti 1.01, the official
> code page standard for Govt. of Pakistan, approved in 2001; see
> http://cle.org.pk/Publication/papers/2001/uzt1.01.pdf Kurdish-Sorani, p.7
> in http://www.fas.harvard.edu/~iranian/Sorani/sorani_1_grammar.pdf Wolof,
> Beh with dot below and three dots above, &quot;Wolofal Orthography&quot; by
> Galen Currah, revised 20 May 2011 Malay, Jawi Keyboard standard by
> Department of Standards Malaysia
> https://en.wikipedia.org/wiki/Jawi_keyboard (Accessed on 13 November
> 2015) Ajami usage, &quot;Language planning in West Africa - who writes the
> script?&quot; by Friederike Lüpke;
> http://www.elpublishing.org/docs/1/02/ldd02_08.pdf Scott Clark,
> &quot;Alphabet and Orthography Statement For Fulfulde [FUB] Ajamiya&quot;,
> SIL, Yaoundé, Cameroon, 2007,
> https://www.sil.org/system/files/reapdata/11/59/46/115946668959791144133440092187534320035/AlphabetandOrthographyStatementforFulfuldeFUBAjamiyafortheinternet.pdf
> (Accessed on June 17 2019) Hausa, Newspapers and books published in Hausa
> using Arabic script,
> http://aflang.humanities.ucla.edu/language-materials/chadic-languages/hausa/hausa-online-grammar/pronunciation-writing/hausa-writing/
> Kyrgyz, http://www.ethnologue.com/language/kir Kyrgyz,
> http://www.ethnologue.com/country/CN/languages Urdu,
> https://www.bbc.com/urdu Wikipedia: &quot;Kyrgyz alphabets&quot;, http:s//
> en.wikipedia.org/wiki/Kazakh_alphabets<
> http://en.wikipedia.org/wiki/Kazakh_alphabets> (accessed on 13 November
> 2015) Malay, Information technology - Jawi Coded Character Set for
> Information Interchange MS 2443:2012, Department of Standards, Malaysia.
> http://www.jsm.gov.my Pashto Academy Peshawar University Kurdish,
> https://kurdpress.com/ Internet Architecture Board (IAB), &quot;IAB
> Statement on Identifiers and Unicode 7.0.0&quot;
> https://www.iab.org/documents/correspondence-reports-documents/2015-2/iab-statement-on-identifiers-and-unicode-7-0-0/
> An introduction to Latin-Script Uyghur: by Waris Abdukerim Janbaz ,State
> Library of Victoria, 2006,
> http://docplayer.net/42224797-An-introduction-to-latin-script-uyghur.html
> Torwali online and printed dictionaries Wikipedia: &quot;Jawi
> keyboard&quot; https://en.wikipedia.org/wiki/Jawi_keyboard (Accessed on
> 13 November 2015) Wikipedia: &quot;Saraiki alphabet&quot;
> https://en.wikipedia.org/wiki/Saraiki_alphabet (Accessed on 13 November
> 2015) ANT (Alphabet National du Tchad) is the national standard for
> Chad/Tchad; See Figures in L2/10-288R (used for “tr” sound as given in the
> table in Section 6.1.2):
> http://www.unicode.org/L2/L2010/10288r-arabic-proposal.pdf and Appendix B
> Wolof,
> https://www.openbookpublishers.com/htmlreader/978-1-78374-062-8/11.Ngom.xhtml
> RFC 5891, Internationalized Domain Names in Applications (IDNA): Protocol
> http://tools.ietf.org/html/rfc5891 RFC 5893, Right-to-Left Scripts for
> Internationalized Domain Names for Applications (IDNA)
> http://tools.ietf.org/html/rfc5893 Omniglot Arabic
> https://www.omniglot.com/writing/arabic.htm The Unicode Consortium,
> Common Locale Data Repository.- CLDR Version 28 (2015-09-16)- Locale Data
> Summary for Arabic (ar)-
> http://www.unicode.org/cldr/charts/28/summary/ar.html Wikipedia Arabic
> alphabet https://en.wikipedia.org/wiki/Arabic_alphabet accessed
> 2015-10-31 Saudi Network Information Center (.sa, Saudi Arabia ccTLD)
> http://www.iana.org/domains/idn-tables/tables/sa_ar_2.0.pdf 0030-0039
> 0660-0669 06F0-06F9 0020-007F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.meswg.org/pipermail/tf-aidn/attachments/20200730/f1c976c5/attachment-0001.html>

More information about the TF-AIDN mailing list