From nobody Mon Jul 3 13:23:54 2017 Return-Path: X-Original-To: usefor@ietfa.amsl.com Delivered-To: usefor@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC2AD13179F for ; Mon, 3 Jul 2017 13:23:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.42 X-Spam-Level: X-Spam-Status: No, score=-3.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g7KY4E6yyY9j for ; Mon, 3 Jul 2017 13:23:50 -0700 (PDT) Received: from smtp.smtpout.orange.fr (smtp08.smtpout.orange.fr [80.12.242.130]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54A84131799 for ; Mon, 3 Jul 2017 13:23:49 -0700 (PDT) Received: from mbpdejulienelie.home ([86.252.120.177]) by mwinf5d68 with ME id gLPm1v0033pkiFq03LPmUk; Mon, 03 Jul 2017 22:23:47 +0200 X-ME-Helo: mbpdejulienelie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Mon, 03 Jul 2017 22:23:47 +0200 X-ME-IP: 86.252.120.177 To: usefor@ietf.org From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Cc: pkyzivat@alum.mit.edu Message-ID: <15001f4b-477e-1900-6d3b-d0635b9dad94@trigofacile.com> Date: Mon, 3 Jul 2017 22:23:45 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Archived-At: Subject: [usefor] Issue with ABNF grammar in RFC 5536 X-BeenThere: usefor@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Ongoing discussion of usefor issues." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2017 20:23:52 -0000 Hi all, Paul Kyzivat noticed in the IETF Gen-ART mailing-list https://www.ietf.org/mail-archive/web/gen-art/current/msg14921.html that there is an issue in the ABNF of RFC 5536 (USEFOR). RFC 5536 defines the following extension: fields =/ *( approved / archive / control / distribution / expires / followup-to / injection-date / injection-info / lines / newsgroups / organization / path / summary / supersedes / user-agent / xref ) to the following element in RFC 5322: fields = *(trace *optional-field / *(resent-date / resent-from / resent-sender / resent-to / resent-cc / resent-bcc / resent-msg-id)) *(orig-date / from / sender / reply-to / to / cc / bcc / message-id / in-reply-to / references / subject / comments / keywords / optional-field) and a message is defined this way: message = (fields / obs-fields) [CRLF body] It appears that the extension done in RFC 5536 is wrong because of how "fields" is constructed in RFC 5322; as a matter of fact, (*a *b) in RFC 5322 is extended to (*a *b) / *c in RFC 5536 whereas (*a *b *c) was wanted. I believe an erratum should be filled to RFC 5536. Maybe by just changing the wording in Section 3: The following news header fields extend those defined in Section 3.6 of [RFC5322]: fields =/ *( approved / archive / control / distribution / expires / followup-to / injection-date / injection-info / lines / newsgroups / organization / path / summary / supersedes / user-agent / xref ) to: The following news header fields are defined by this document: news-fields = approved / archive / control / distribution / expires / followup-to / injection-date / injection-info / lines / newsgroups / organization / path / summary / supersedes / user-agent / xref The definition of message in Section 3.5 of [RFC5322] is changed to: message = *(fields / obs-fields / news-fields) [CRLF body] Any better idea of fix in RFC 5536? -- Julien ÉLIE « You know what I did before I married? Anything I wanted to. » From nobody Fri Jul 7 09:59:28 2017 Return-Path: X-Original-To: usefor@ietfa.amsl.com Delivered-To: usefor@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74298131789 for ; Fri, 7 Jul 2017 09:59:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n-6e-m7Shfvd for ; Fri, 7 Jul 2017 09:59:25 -0700 (PDT) Received: from hardbaer.com (mail.hardbaer.com [91.250.101.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74FE213173B for ; Fri, 7 Jul 2017 09:59:25 -0700 (PDT) X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from WStation4 (business-092-079-177-146.static.arcor-ip.net [92.79.177.146]) by hardbaer.com (Postfix) with ESMTPSA id EEE2428004B; Fri, 7 Jul 2017 18:59:23 +0200 (CEST) Date: Fri, 7 Jul 2017 18:59:14 +0200 From: Michael =?ISO-8859-15?B?QuR1ZXJsZQ==?= To: Julien =?ISO-8859-15?B?yUxJRQ==?= Cc: usefor@ietf.org, pkyzivat@alum.mit.edu Message-ID: <20170707185914.06cfa0ac@WStation4> In-Reply-To: <15001f4b-477e-1900-6d3b-d0635b9dad94@trigofacile.com> References: <15001f4b-477e-1900-6d3b-d0635b9dad94@trigofacile.com> Organization: STZ Elektronik User-Agent: Claws-Mail/3.13.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/BD0kenCxDXaWuQHILzTiCgw"; protocol="application/pgp-signature" Archived-At: Subject: Re: [usefor] Issue with ABNF grammar in RFC 5536 X-BeenThere: usefor@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Ongoing discussion of usefor issues." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2017 16:59:27 -0000 --Sig_/BD0kenCxDXaWuQHILzTiCgw Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Julien =C9LIE wrote: >=20 > Hi all, >=20 > Paul Kyzivat noticed in the IETF Gen-ART mailing-list > https://www.ietf.org/mail-archive/web/gen-art/current/msg14921.html > that there is an issue in the ABNF of RFC 5536 (USEFOR). >=20 > RFC 5536 defines the following extension: >=20 > fields =3D/ *( approved / > archive / > control / > distribution / > expires / > followup-to / > injection-date / > injection-info / > lines / > newsgroups / > organization / > path / > summary / > supersedes / > user-agent / > xref ) >=20 > to the following element in RFC 5322: >=20 > fields =3D *(trace > *optional-field / > *(resent-date / > resent-from / > resent-sender / > resent-to / > resent-cc / > resent-bcc / > resent-msg-id)) > *(orig-date / > from / > sender / > reply-to / > to / > cc / > bcc / > message-id / > in-reply-to / > references / > subject / > comments / > keywords / > optional-field) Hi Julien, there is Erratum 2950 (Status: Held for Document Update) that specify it like this: fields =3D *(trace *optional-field / 1*(resent-date / resent-from / resent-sender / resent-to / resent-cc / resent-bcc / resent-msg-id)) *(orig-date / from / sender / reply-to / to / cc / bcc / message-id / in-reply-to / references / subject / comments / keywords / optional-field) > and a message is defined this way: >=20 > message =3D (fields / obs-fields) > [CRLF body] >=20 >=20 >=20 > It appears that the extension done in RFC 5536 is wrong because of how=20 > "fields" is constructed in RFC 5322; as a matter of fact, (*a *b) in RFC= =20 > 5322 is extended to (*a *b) / *c in RFC 5536 whereas (*a *b *c) was wante= d. >=20 > I believe an erratum should be filled to RFC 5536. Maybe by just=20 > changing the wording in Section 3: >=20 > The following news header fields extend those defined in Section 3.6 > of [RFC5322]: >=20 > fields =3D/ *( approved / > archive / > control / > distribution / > expires / > followup-to / > injection-date / > injection-info / > lines / > newsgroups / > organization / > path / > summary / > supersedes / > user-agent / > xref ) >=20 > to: >=20 > The following news header fields are defined by this document: >=20 > news-fields =3D approved / > archive / > control / > distribution / > expires / > followup-to / > injection-date / > injection-info / > lines / > newsgroups / > organization / > path / > summary / > supersedes / > user-agent / > xref >=20 > The definition of message in Section 3.5 of [RFC5322] is changed to: >=20 > message =3D *(fields / obs-fields / news-fields) ^ > [CRLF body] Wouldn't this asterisk introduce the same "infinite loop of empty strings" situation as in the erratum noted above? --=20 Michael B=E4uerle --Sig_/BD0kenCxDXaWuQHILzTiCgw Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZX73iAAoJECo3xlduIVC7SdMQAIJ8wSivi4n9KF3wdgPn6Dir hlycqX+GdcvbRlD9oaSFpCcp0gZ071t3ZHPqf92ITFtE1/tgD5MXlP9hZrxF7JVk E5enuWkl/mpv1LGz5qMf/ZNgvPnyNx7Kdf02ZBd7Dv79tDU8/1rurpbsoXx8Qy5C McYwXwVhRBL6IPKW4unEVuuJ/0kD9VgSg1fwL/MEhD0xdK9J3ST0Eu3+rBa/y67k HEdDJYidlR0GYfhjsih8TVFTdFMfs8s79Pp74wTH2A36KH601naZt10MjbJwJISZ NzSC8Oz150jAqwM7u3IWPDl834wtqlAT3l8uFm/9ItVJCXWFStOmQfVACYi/Ujf1 KpjqqEVvXZHD7AFy5HFBHzgc0KOrBVqd1w/0sx7m8dvA8kYYpF49YUPQOslnR1L9 HnfJChqtkLOugvUuTm7phOCNYSS0mbN/nFpB4nHKBCQxgau/ZqfHVYAzA6BdrUCN PtCtDnwDSEj7mNH42mSNkd/vGKLfofX72DvVGVPLLfz4VFe8tXSzdM4BohmOPY3n sXvH6aQwC41V3jlYgzAN4lyGD+O2NkbddexAYxZSjsZFyVCqhyGh3jXqTcwCRJF7 ufHxT1sLDSPAohXsg1m+qi3nmxF8/zAU0wjfaH7nxzePQCXkIhtl/5KhTK0j4059 QnZ+XcFNhLJwJSocipS1 =L3c9 -----END PGP SIGNATURE----- --Sig_/BD0kenCxDXaWuQHILzTiCgw-- From nobody Mon Jul 10 12:47:05 2017 Return-Path: X-Original-To: usefor@ietfa.amsl.com Delivered-To: usefor@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF6C1318A0 for ; Mon, 10 Jul 2017 12:46:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.421 X-Spam-Level: X-Spam-Status: No, score=-3.421 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ofsqRL_Qip_1 for ; Mon, 10 Jul 2017 12:46:52 -0700 (PDT) Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B4881318A3 for ; Mon, 10 Jul 2017 12:46:51 -0700 (PDT) Received: from mbpdejulienelie.home ([86.252.120.177]) by mwinf5d81 with ME id j7mp1v0093pkiFq037mpj8; Mon, 10 Jul 2017 21:46:49 +0200 X-ME-Helo: mbpdejulienelie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Mon, 10 Jul 2017 21:46:49 +0200 X-ME-IP: 86.252.120.177 To: usefor@ietf.org Cc: =?UTF-8?Q?Michael_B=c3=a4uerle?= , pkyzivat@alum.mit.edu References: <15001f4b-477e-1900-6d3b-d0635b9dad94@trigofacile.com> <20170707185914.06cfa0ac@WStation4> From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Message-ID: <69036829-918f-2b31-7145-45b8629ef341@trigofacile.com> Date: Mon, 10 Jul 2017 21:46:49 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170707185914.06cfa0ac@WStation4> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [usefor] Issue with ABNF grammar in RFC 5536 X-BeenThere: usefor@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Ongoing discussion of usefor issues." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 19:46:54 -0000 Hi Michael, >> Paul Kyzivat noticed in the IETF Gen-ART mailing-list >> https://www.ietf.org/mail-archive/web/gen-art/current/msg14921.html >> that there is an issue in the ABNF of RFC 5536 (USEFOR). >> >> The following news header fields extend those defined in Section 3.6 >> of [RFC5322]: >> >> fields =/ *( approved / >> archive / >> control / >> distribution / >> expires / >> followup-to / >> injection-date / >> injection-info / >> lines / >> newsgroups / >> organization / >> path / >> summary / >> supersedes / >> user-agent / >> xref ) >> >> to: >> >> The following news header fields are defined by this document: >> >> news-fields = approved / >> archive / >> control / >> distribution / >> expires / >> followup-to / >> injection-date / >> injection-info / >> lines / >> newsgroups / >> organization / >> path / >> summary / >> supersedes / >> user-agent / >> xref >> >> The definition of message in Section 3.5 of [RFC5322] is changed to: >> >> message = *(fields / obs-fields / news-fields) > ^ >> [CRLF body] > > Wouldn't this asterisk introduce the same "infinite loop of empty > strings" situation as in the erratum noted above? As "fields" in RFC 5322 amended with erratum 2950 no longer has an infinite loop of empty strings, *(fields / obs-fields / news-fields) also do not have, don't it? Note that using 1*(fields / obs-fields / news-fields) is also fine because headers are not empty. I once thought about something like original (fields / obs-fields) extended with *news-fields. The issue is that "fields" and "news-fields" are a/ mixed and b/ Netnews specific header fields do not appear after all mail header fields. -- Julien ÉLIE « – Chef ! On vient ! – On se met en carré ? – Non ! En bosquet ! » (Astérix) From nobody Thu Jul 13 09:55:08 2017 Return-Path: X-Original-To: usefor@ietfa.amsl.com Delivered-To: usefor@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86694128B8F for ; Thu, 13 Jul 2017 09:55:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aQ7WSszFhIjo for ; Thu, 13 Jul 2017 09:55:04 -0700 (PDT) Received: from hardbaer.com (mail.hardbaer.com [91.250.101.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4E151270A3 for ; Thu, 13 Jul 2017 09:55:03 -0700 (PDT) X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from WStation4 (business-092-079-177-146.static.arcor-ip.net [92.79.177.146]) by hardbaer.com (Postfix) with ESMTPSA id 59D5C28002A; Thu, 13 Jul 2017 18:55:01 +0200 (CEST) Date: Thu, 13 Jul 2017 18:54:49 +0200 From: Michael =?UTF-8?B?QsOkdWVybGU=?= To: Julien =?UTF-8?B?w4lMSUU=?= Cc: usefor@ietf.org, pkyzivat@alum.mit.edu Message-ID: <20170713185449.09e33b08@WStation4> In-Reply-To: <69036829-918f-2b31-7145-45b8629ef341@trigofacile.com> References: <15001f4b-477e-1900-6d3b-d0635b9dad94@trigofacile.com> <20170707185914.06cfa0ac@WStation4> <69036829-918f-2b31-7145-45b8629ef341@trigofacile.com> Organization: STZ Elektronik User-Agent: Claws-Mail/3.13.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/qv9Y7DmWkJjkZyP1fqY.1H="; protocol="application/pgp-signature" Archived-At: Subject: Re: [usefor] Issue with ABNF grammar in RFC 5536 X-BeenThere: usefor@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Ongoing discussion of usefor issues." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 16:55:06 -0000 --Sig_/qv9Y7DmWkJjkZyP1fqY.1H= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Julien =C3=89LIE wrote: > Michael B=C3=A4uerle wrote: > > Julien =C3=89LIE wrote: > > >=20 > > > Paul Kyzivat noticed in the IETF Gen-ART mailing-list > > > https://www.ietf.org/mail-archive/web/gen-art/current/msg14921.ht= ml > > > that there is an issue in the ABNF of RFC 5536 (USEFOR). > > > > > > The following news header fields extend those defined in Section= 3.6 > > > of [RFC5322]: > > > > > > fields =3D/ *( approved / > > > archive / > > > control / > > > distribution / > > > expires / > > > followup-to / > > > injection-date / > > > injection-info / > > > lines / > > > newsgroups / > > > organization / > > > path / > > > summary / > > > supersedes / > > > user-agent / > > > xref ) > > > > > > to: > > > > > > The following news header fields are defined by this document: > > > > > > news-fields =3D approved / > > > archive / > > > control / > > > distribution / > > > expires / > > > followup-to / > > > injection-date / > > > injection-info / > > > lines / > > > newsgroups / > > > organization / > > > path / > > > summary / > > > supersedes / > > > user-agent / > > > xref > > > > > > The definition of message in Section 3.5 of [RFC5322] is changed= to: > > > > > > message =3D *(fields / obs-fields / news-fields) =20 > > ^ =20 > > > [CRLF body] =20 > >=20 > > Wouldn't this asterisk introduce the same "infinite loop of empty > > strings" situation as in the erratum noted above? =20 >=20 > As "fields" in RFC 5322 amended with erratum 2950 no longer has an=20 > infinite loop of empty strings, *(fields / obs-fields / news-fields)=20 > also do not have, don't it? Agreed. Looking at RFC 5322 again I'm no longer sure that there really was an infinite loop even without erratum 2950 applied. For an infinite loop of empty strings something like this is required: *(*a) ; Can result in =E2=88=9E(0a) Looking at: *(trace *optional-field / *(resent-date / resent-from / resent-sender / resent-to / resent-cc / resent-bcc / resent-msg-id)) The second and third repetition operators are not nested (alternatives) but the result can reduce to: *(trace) if both of them use zero repetitions. Note that there is no slash after trace and trace must contain at least one "Received" header field: trace =3D [return] 1*received Therefore the content in the outer parenthesis can not be empty. Have I overlooked/misunderstood something? Can somebody show an example how to create an infinite loop of empty strings from the original syntax? --=20 Michael B=C3=A4uerle --Sig_/qv9Y7DmWkJjkZyP1fqY.1H= Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZZ6XZAAoJECo3xlduIVC7GlsP/RP8h4/Vn3pPUtIaw0QwYarx GwzIjvrIdDoHmadU/7dQXeQ36VGt8+boC6SXy+0LuIMYy5ecTu7uCREtyH4j9cns jZIYbLKRN167UzvJV93qhaLWDcfmuwAxe+rP9GJdaU1ZQssCk9RpFEvvFFwxJjMs fk9uYKKmAr6DGSfRZJ22XHC83bxnItb8aq8fpLMxSahAo2vt3KBqQAI2pgbNP6HA +ZYlaAwtLaZumtpuM3ErBOOL8gDEeA6EWoEFpyHoNcJyBd+UiRcD56epBBVPsyrM iJw/PYqKXnkcfcwUu8N2A+nZtB5IAQE/rkdBT6KW6EdTDluTPvCWmxRo9+WixKAj rX/PfQFRhC4eLH+aewKR2YobV9//saUP8PxmZKXfsPwQGslPWdj1Rj9j+uE1O/lA AkQIEkUz1ii03ViF1HPkiTiC2wk/v88e0PcCMPPrRDqbqDDoPL61vYeKIVAHbWhD 3iOdOUPdn1mdA2IAFnqac3o4/BceaNOvkzjtDcuTbCQVlWJpc3LSMpVFXhUkl/j2 wjVSV5WIA2U/M4Py2SOoPriEmWJlJVHIIzWiTy7G4McO+pUH81qVySya2z2ll+nO dsk0IXh9osQVUBmbnMz2dAtbaOSNYz972QJ/qEeZuG1j8wVVUNQ97aUDE1l/6DfG sGViX2nKTyviB5Iji+Pu =scxU -----END PGP SIGNATURE----- --Sig_/qv9Y7DmWkJjkZyP1fqY.1H=--