Re: [Standards] [Members] IETF 89 and the XMPP WG meeting - are you going?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 *bump* please do add your name to the wiki page noted below so we can figure things out *before* the event. On 02/12/2014 12:39 PM, Mike Taylor wrote: IETF 89 is approaching and the XMPP Working Group is scheduled to meet - see http://wiki.xmpp.org/web/IETF_89 for details. The importance of the XMPP WG is that quite a few XMPP related technologies are now also IETF drafts and they need activity and discussion so they can move forward to be considered IETF documents. The Working Group is where all of this activity takes place and it really helps the process when XMPP folk are participating. The London WG meeting is a great opportunity for new (and old) members to come, help and participate - to that end I created the above wiki page to help get a feel for who can attend. The board is also considering helping defray some of the costs but we need a better feel for how many people are going (or would go) so we can decide. Please do list your name on the wiki page if you are going so we can start getting organized for this. thanks - -- bear xmpp agitator; ops curmudgeon; generalist http://bear.im/about http://bear.im/pubkey.txt 0A93 9BA7 8203 FCBC 58A9 E8B5 9D1E 0661 8EE5 B4D8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTBOb0AAoJEJ0eBmGO5bTY4jsP/R8hbN/WWFM42cl8TVtvP3gv Gb8PpFNjrUc3QOJeoHphOVMBuf4YfwVd3RgTy+0hfHmWwWYdb02ZOeeBXu5IfjhT JCp0WkhL6e2JHng3U8vaScCl9atH+1HbYyG3Gcoxeqdzyu3ekClGwyJNf11L+rKs wIKb0VIz6195wmAmDvTgrQ6rt/M9YrO7fzbNCr2ur7nM9mzDUqVq8Gu2Hiv0Ye+P UxUw0mn+xnnINBzKPyHaR+PN4vwcU5nNcQbln71kb/46MPtOZSK1PSQ86nQEQ/lp 4+giKpU0m+5zZIjFw4+JoiQAb8UtLtOW6/2jJu5NU83xH1CE9dqdFKCyXmF57hA8 TIVO2M1SrCs5QhlCjntLQh2zkqZFxhq3GDzWOod1vuwvnNnvYA9PqKoeWloxm1Qy y7HbYEzpWIc+9KukBeJskqHPsOXnZzwfqglTTPU+Ek++57zeMkpBMkb2NF+qII2S U+KmWPMBCKI5AZTYLPgEeyA40rzyRcTCrQR/aRIfN2RMx7BX0CfXW0o6fqifQoj1 0wWdzH5XJZngUPwoScx9ma4U5jf3wGr8Wv+yK8kZR2f4d+TuXReF5CDR9IXHS9F6 GygxfxtN/4w/fdHAn38mx+QWJiACRWr1wtXjp6s9qklDSMpqtWnu0UwQzxGnHnBY wwvliTXKwIMz3sjzXfxR =BMBJ -END PGP SIGNATURE-
[Standards] IETF 89 and the XMPP WG meeting - are you going?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 IETF 89 is approaching and the XMPP Working Group is scheduled to meet - - see http://wiki.xmpp.org/web/IETF_89 for details. The importance of the XMPP WG is that quite a few XMPP related technologies are now also IETF drafts and they need activity and discussion so they can move forward to be considered IETF documents. The Working Group is where all of this activity takes place and it really helps the process when XMPP folk are participating. The London WG meeting is a great opportunity for new (and old) members to come, help and participate - to that end I created the above wiki page to help get a feel for who can attend. The board is also considering helping defray some of the costs but we need a better feel for how many people are going (or would go) so we can decide. Please do list your name on the wiki page if you are going so we can start getting organized for this. thanks - -- bear xmpp agitator; ops curmudgeon; generalist http://bear.im/about http://bear.im/pubkey.txt 0A93 9BA7 8203 FCBC 58A9 E8B5 9D1E 0661 8EE5 B4D8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJS+7HPAAoJEJ0eBmGO5bTYfpwP/RtE0YvDyXKd5I98X3Hz/8rn RTneAyUUHdNLQ122p2dCDUCJNcsIcGJSp2ZRZw+3to2V5TsyOurKRIkt5AWpDFJn qKJ+oLp62dkQ0npfxHXWhRzgo3ZkJAHYl3HTXykOhYCW0QZEong6BU3mvsvAt4bw WLJPGQssG2lT/slFAfdfYuLBqSus8EWe1b0Gu/g8koUQ5lid/PYn0E1oJxDWe06u njpfsdXXzoicVfG0/g00NMr/do4+54jFXTMu85iTPipPneTmWDmFAnCl2GXB5WTP GG/96ogSojpi0u5033aONPUA5Cu9KKQ9Q1iF7KfAp5TlQKaZHr6xRbawg+IVkHJj kW4Tr6DJRp97P81YPyCNVpgkBVAAvGSPd/nEgdiMTYDkgMpiESQIm6MpBn6ZDGBa F1HKQvPeR5OgWomqkzP8p+F8xKiaPUNtTcOpfgAQ7ISv6IcXLlXmUSsm2kcIWB2i grFH/gLjqH4Cz71/IZVOp3awY2M7hh4hiEVR5UXPS9qxd5vrrJD0XOpOvb/c0ojt kdcngkZ0Gq0E/HoPD0bBnMla7ELdHr3NJpAUwHuemef32PvFHGNJVrzRTPxMzIxQ JBup9Eua9bIn8DVQhN7BA6JBDDB4RaxMQGHNf5fVZlV3Oa/T2+kJ4ufWfy/RjjXa BBOdNdbv3TpHrHH8yRkR =zQXa -END PGP SIGNATURE-
Re: [Standards] Event Logging over XMPP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/10/2013 09:34 AM, Markus Kohlhase wrote: Anybody objects if I write a XEP proposal about this? no, absolutely not! Markus Please do and count me in if you need help with this! - -- bear xmpp agitator; ops curmudgeon; generalist http://bear.im/about http://bear.im/pubkey.txt 0A93 9BA7 8203 FCBC 58A9 E8B5 9D1E 0661 8EE5 B4D8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSf79SAAoJEJ0eBmGO5bTYifsQAJ1wsnFwLlpcKrHfUZHhVI93 +M+rWc7yvIRlgfQm4ah+ExIZLI61iQAt7H+YYJMjBBUwn1vOwuMGrA3ctuLxc+Iw AikeMdhxP2bw6ubczGF8zfV1kQEcwTkYt99fLO5JV/hcR7EjtmbHFKpoiqE4q9v3 OHLTR9nT5c6cfjbOlz3USBBKXaxB5xrLGIuhPq8ytI8uuSmMF5Ll6A+xf7iHQ9Ou 3JIq9RfiS2PHXgpKWlrkHKWX8B+QVUeoEq+piSxZ0SZVrj/EDncLu8QX3PicKc49 gs+eg5fxUws5uZkGQBiRtLyhDoBTvB1srZLScEknP2JfSDYDxsV9mdZgIRQG1no8 LYLUCoIrPIIlGVSy13R4l9hsDs2sMkNL2WG/OUcPp2JF6Po+LxKrVu+t9xaBpbn/ l+TZXZaRRiQErImBTLBltNzQ8891G+jgD9Tp7fwQmDgZKDd7WfqLvyTx+MCixal6 /R7yvJuZ5e8t81Xi4AsPe53IcKEpWSBG7de2nwQ0yCDd4KvMs6okC9UpSvqu4hU+ Oj0ffkIKIYjxCEcP+7c4U1hOL+GrN74yv1yEEgucenj/TTomDk6SmelcGWy9TSFe hEbFTpGHTACOLo1HP3SAeE2lMMIokAOORjyWEYoN1/TmecVqYFOtbnNvezjMR6ul EEnj8L+T/gM5eY3rDnIw =aILm -END PGP SIGNATURE-
Re: [Standards] Event Logging over XMPP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/10/2013 11:26 AM, Yusuke DOI wrote: Peter, (2013-11-11 0:43), Peter Waher wrote: XML has many features that are very nice: Plugability and versioning using namespaces, validation (schema), swearch (xpath) and transformations/conversions (xslt). I don't think it's beneficial to start JSON vs. XMPP discussion here. If we want to hand logs to JSON-based systems, this doesn't mean we should use JSON as-is. For example, we can still use JSON-ish XML instead. In the case, if we use complex namespace and XML-ish versioning, XML-JSON binding may become broken. What I would like to clarify is use cases. fortunately I don't think we need to go down that dragon strewn path as we can now just put xmpp-ftw or stanza.io into the mix. 'logging' is a too broad word I think. What framework/logging facilities in your mind? I was thinking of network/admin logging, for instance like or based on Syslog semantics (also IETF). Could be used to log events of interest to system administrators, network architects, etc. Can also be used to find problems or learn how IoT networks based on XMPP work. Then, I guess netconf/netmod(YANG) and SNMP will be a first choices. FYI, as IoT-related disucussion there are proposal on CoAP-based management interface (not adopted by IETF yet). http://www.ietf.org/mail-archive/web/core/current/msg05102.html The realm of logging appears to be broadly divided into two camps; the folks who live in the structured realm of SNMP type log generation and the others who sling text and/or JSON at a receiving entity. I am mainly interested in using XMPP as a transport so am not to worried about maintaining a strict XML structure but I can see how that would be beneficial to have. This means we would need to identify a core set of elements as MUST with the rest being optional. - -- bear xmpp agitator; ops curmudgeon; generalist http://bear.im/about http://bear.im/pubkey.txt 0A93 9BA7 8203 FCBC 58A9 E8B5 9D1E 0661 8EE5 B4D8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSf8CyAAoJEJ0eBmGO5bTYCCIQAKLDIEmx/3WPLj7Cine3zr80 qUbUewnsaD5BcyItNQmpitDfeo/5ufZLqTcLx77LZnOTtxrN5IRDzcrQyuMHJw+h e1bypi6lRBfnwTK9myWhiHumI6rpT2j02RaLyuElSJ2CwjxOsVA21VxhoEhPjEya J2CL9nTIiB2e4moUmAxeceo71xUGjwDkEfv2zwfuuNfIyriXdWlfPO/J4O/Aw4Zx HUiyvaOt3TDOuN9pFMAHONYplraoBlSUjrCvyRyVvCONPKjD3xiR5CoM5iX84AAi Z408AU/Suh6z083faXSVsuE7GdcsOs5Q7cHmo0RCttnFyoMXoT8K9LTE6/Y495i/ x36Qh33vkjb48pSyS01w+ex64UQWujlwMY2SmLbBasDdB9lSWOLeDpPnqCfS0lkK 4l6sCfzm+HwK/BAlI+UqDVNTCGkp2CEpUc9JpyR9il5bvq/uIHFsu4q4iqrq4UR0 u3V3FfZ0rG+VxNHqXaJqbsajwuSA1pwXdhrn4NQqQtgANPD94t0VBT5odhF0Ovyv KH2V9qfx9ojIY821p/Fv5pPURhUYut6OFABOSVOZL1lR0LTlgbv8/j9XaI/K6vP1 52SGRfYtXcWRFw2J8JCXVmm7TtiF8zWGZLJqF6KkPsT5zG1fUoVkgaqiao+nehSG 0HbohQYYa/5MMqwpCYXH =j1Uc -END PGP SIGNATURE-
Re: [Standards] Proposal: Event logging over XMPP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/10/2013 02:58 PM, Steffen Larsen wrote: Hi Peter, First of all great work and perfect to bring this up.. I’ve done this a while now, but haven’t brought it to a broader audience. thumbs up! indeed, good job and +1 for this So here is my first 50 cent on the doc: Cool stuff with the tags.. This I can tel you will be valuable for many people. I use these kind of tags all the time to piggy back stuff, that could be valuable in the context. I don’t like the tag “event”. I think it should be log tag instead, no to confuse anybody. I have made several custom XMPP components and client where they have event tag embedded, which have a completely different meaning and context. I also think that event is a bit too broad of a term here and would prefer log or even eventlog Type and Level? I think its too complicated. Only level should be present and with fewer clases.. Debug, Info, Notice… is way too much. People tend to misuse and not think when they have a lot of choices. :-) I also think that this may be too many options and would prefer to see Level limited to a smaller set and have Type removed completely as it could be implemented as Tags. I do love that you've chosen to use words instead of numbers to represent the levels. Another item I wanted to bring up is can we just remove timezone worries completely and say use UTC and only UTC? IMO it is a best practice and would avoid the whole TZ issue (yea, yea, I know this one is going to be a long shot ;) thanks! -Cheers! /Steffen On 10 Nov 2013, at 20:31, Peter Waher peter.wa...@clayster.com mailto:peter.wa...@clayster.com wrote: Hello all First of all: Thank you to everybody providing both input and an interest. It is clear the need for an extension in this area is missing and both wanted and needed. So I took the opportunity to write a first proposal based on all your comments and on our past experience as well, on how such an event logging extension could look like (attached). I’ve made sure Syslog events can be mapped onto such event log messages (being a standard and all), but extended it a bit to provide for things lacking in Syslog as well as adapting it to the world of XML where new possibilities exist. The extension is made so that it can be used both by those who only want to send simple text events and by those who want to have a more controlled way of sending data (including data and types). Hopefully this is a good compromise. But as with all compromises, it has the possibility to offend people in both camps… What do you think? If you have any questions, comments or suggestions please don’t hesitate to mail them. Best regards, Peter Waher xep--EventLog.html - -- bear xmpp agitator; ops curmudgeon; generalist http://bear.im/about http://bear.im/pubkey.txt 0A93 9BA7 8203 FCBC 58A9 E8B5 9D1E 0661 8EE5 B4D8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSf/jwAAoJEJ0eBmGO5bTYSZQP/RU4RErKoT0I+5o9qNS8cu7q d5dh3oraLTZaKS+G9vB3qwjGHaeUYCzqzygZdekm6xmsh/X8OCd5sgHSqgwpCTuM reMicE7VW4xel/NVC9m7tyyEVeqepDB0AYQrlCSEMG7chpTuasqrf7Uv78M/ss04 swartJSGNAuLx0hDtvBFkHnyh/JtMOiyigE1fNgLArV2YUsiN8wbCef/Gflo6l0k tP8Y/s3ZrRLnmE4Ay9+FoHHm/FuYff8ALxkLU0dfY4whnecOdAQWMhbrh8SBDys6 4bvGvVG7tyg/LbGLD3Bv8BmfU1tbo5b5HR/WPMGdAoNs9ldtYuBoA3+rxpFDIaUz aiQP6O5F5W1eA7MRkMWOw+W2sixVzaIIlJ/GvmYNTM9rX5UtIIxAIxbZfjkg8hC6 cNRitUaPpZPDAnfNmSU1SXFg4dUS2U0Xf+HUTwKcFmcm5AN7lqQrVcG9Cw2K/61F 5cGUfETQue7f7W4Qrn9h9ixXux9u0UEvpivY2DgHWxOEnTv0W9tQziCQgn8n/Vto VpWqo2xzrxJv4epzI6K2HN1R+zdKlxbyuc2vLv6reTmL59ioEzOoQxk5fYwt9q6d 1TMDMMlJIgfG4w2E+FHPjdmJh8q8FCQMUClUVYX4t6kb2/nbwlKpFfN5bHnmiIIE zv0YlqAhtaGXFamqjSJM =kob/ -END PGP SIGNATURE-
Re: [Standards] Event Logging over XMPP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/09/2013 03:13 PM, Robert Kosten wrote: Hi, a Lurker here ;-) I've had the same thought about two years ago as well so I implemented a small Monolog (PHP Logging Library) Handler that sent log messages as both formatted message (for standard chat clients) and a custom stanza for our status board. At the time I thought that pub/sub might actually be better though, because I didn't really want the logger to know who would receive the message... Sadly that code belongs to a former company and I'm not certain I can remember everything about it (It was a quick'n'dirty solution), otherwise I'd attach it :-P Regards, Robert Kosten On 11/09/2013 09:08 PM, Steffen Larsen wrote: No haven’t seen such a XEP, but I’ve implemented something like it to be able to remote debug set-top boxes etc. I’ve just did a dumb implementation based on message stanzas, where the client can send the log to diff. implementations like console, remote (xmpp), file etc. with different levels. So I am interested as well. :-) I could see this happening by wrapping the protocol that Logstash uses. /Steffen On 09 Nov 2013, at 19:30, Matthew Wild mwi...@gmail.com wrote: On 9 November 2013 18:24, Peter Waher peter.wa...@clayster.com wrote: Hello Is anybody aware of event logging extensions for XMPP? XEP 0163, 207 and 316 all relate to publish/subscript (personal) events as I can see. What I’m looking for is system and network events for system administrators, like Syslog, for instance, but over XMPP. No, but I have wished for such a XEP before now. I'd love to see a simple one that primarily defines a way to transport log messages over XMPP (perhaps re-using syslog semantics). Regards, Matthew - -- bear xmpp agitator; ops curmudgeon; generalist http://bear.im/about http://bear.im/pubkey.txt 0A93 9BA7 8203 FCBC 58A9 E8B5 9D1E 0661 8EE5 B4D8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSfpkBAAoJEJ0eBmGO5bTY2n0P/jA+ty1Gusx0utAolJtdEeKh 9sr7uOcO/TKr9ZZPPj4XeZOFNF981XPHaaGEF0rmPZa/Y3zn1gIhMHM3hxWAUw6b agev8fN3SZ+R3XtE6hlbgE7mMlI94vfaGj7E3yieTx0My2ePNeXrGgFifJa+MKlm mJDrfKnshlPaXz71JbpRJTFeqadq65FGKWuAZZHRYtHWJnUO8eWFpjxO/YEE1QaE YSwNMjVAVjIMM8S2c4dpmNdPXu2lqv7EU6cd9n2/J9EDomjRokss6nDY5MUwyp0k bhJES91KVLzFgSf0HlAIsur0mcfwYGsorccNDG9rr3Q/aat695VdzQWdSuRrmz00 iiklx8zWA0d8DZvldVmguy+lSJfxgNZGGCdbbNHhyLzQH2tRp8w0QtHhVifLDWYa 9mvLCojpLB3fygwn5vsbC/aVi1VVVl+J5bwpRIx/vyd4dA08T7K2M2qHnD1U4w+g Vjc2QRjBNTwg4kTZCYV5DvLLK9E8ylcVRWCskd/ppSKGTWk/tUNslUCHYH+cDFMQ xpnLfto6bLEC7QMFP309HN+6g8VlCmnpLhRchAlpt4cd5tMm04I/MvfIhvtGJYtS +pHNbcVBgp5n8Hj7KNQWZV1Zbtr2Mp/8RWPeeYnLNtblOzR8Ot4iy4KL09l0JTIV kmlT9C19uTgl7tVT9PtM =FHXf -END PGP SIGNATURE-
Re: [Standards] jabber-id email header
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/19/2013 10:44 PM, Peter Saint-Andre wrote: Back in 2007 we defined an email header for advertising your Jabber ID in your email messages: http://tools.ietf.org/id/draft-saintandre-jabberid-08.txt For various reasons we never got this header registered with IANA, but on re-reading RFC 3864 I've concluded that we could add it to the provisional register through a XEP instead of an RFC. Is there still interest in registering this header? I'm +1 for this because it will make sense when we start using our JID as an identity marker. Peter - -- bear xmpp agitator; ops curmudgeon; generalist http://bear.im/about http://bear.im/pubkey.txt 0A93 9BA7 8203 FCBC 58A9 E8B5 9D1E 0661 8EE5 B4D8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSO8n3AAoJEJ0eBmGO5bTYPcAP/3iRndy23n5F3wffuyBui3N+ fhATlKplUWInsXJkNtZYVilckLy4QfdLJXo3wE2SeQfjM/6U92kZvXFPahxMnOEm Whv6vq2pf2LVYaXsHkdc2+I4bNpOsenWMrp99uyneQ7hdU58q/5PdbFu5o8IVezb 0Y33c6iEa3qw2jAYCUFvOBUeBe4UXIcgZh4AU9D/48h3tV5aQXEcQV7sMZA44eXO EhuphezJoPLBMq0DpqwyJhd63kVGtdXpMlI6g4z8q0C4FrqBCT0xkKbT444PBWdc qUWg4eAumb3CIs3/wxVF9SKfuUKkq7bFOphydbISWhGxuKexqyuD6RBwRb9MnACJ +gwMbA27FCIRPGX5VGVAhbGuNIXb3EGsuLRg06k5vxAWhTJ5o4S3kDGQPpqyJ812 Xajb+ptUft1l6o/gUhnroHCSMGvksStyeSq2kkMyg6PJoudBicpImoYb3+8aKT0k KF9U46oupwiqny4Irt3jcRT1R8HbGGT2EauuiM1hGgzEYIFw/TPOutlBT1XL3WSt BZz0IpUMmOsvRYY12PmXEfomMHCKHNJdN5o1mxQnv1QgP/S7GoaVIwx5YKdBGjox cYtBncChVtfg6O24fzsmU1dcYKdtF2vmjcFg65DStUpc22ZSjuzzqw0M1/KY1sb8 slsGrvQfUxYmPKygzSaJ =+cc6 -END PGP SIGNATURE-
Re: [Standards] Fwd: Re: [cryptography] Is it just me or is this fundamentally broken?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/05/2013 12:04 PM, Peter Saint-Andre wrote: I would like to suggest that we change XEP-0027 from Active to Deprecated (and then Obsolete). The technology is no longer in wide use, and it has so many problems that I don't think we want to actively suggest that people implement it. +1 for being proactive at clearing out older (and unwise) info Peter Original Message Subject: Re: [cryptography] Is it just me or is this fundamentally broken? Date: Mon, 04 Mar 2013 18:24:46 -0700 From: Peter Saint-Andre stpe...@stpeter.im To: Peter Gutmann pgut...@cs.auckland.ac.nz CC: cryptogra...@randombit.net On 3/4/13 4:42 PM, Peter Gutmann wrote: Quoting http://xmpp.org/extensions/xep-0027.html#signing: Signing enables a sender to verify that they sent a certain block of text. [...] The text that is signed MAY be the empty string. (There's no metadata or anything there, just a raw signature). No one uses XEP-0027 these days, they all use OTR. The PGP integration with XMPP clients was an early experiment in the Jabber community before we even called it XMPP. Think 13+ years ago. But clients never signed empty strings, although we never fixed the spec because no one was using the technology. I'll push to make the spec Obsolete. Peter ___ cryptography mailing list cryptogra...@randombit.net http://lists.randombit.net/mailman/listinfo/cryptography - -- bear xmpp agitator; ops curmudgeon; generalist http://bear.im/about http://bear.im/pubkey.txt 0A93 9BA7 8203 FCBC 58A9 E8B5 9D1E 0661 8EE5 B4D8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRNiY7AAoJEJ0eBmGO5bTYyOYP/2v6Tbtn1exoZjd+dE33T4Bj Qnk4HsNwfGyxJWbts2kHWqCHkfKD7xgUxekcKSz5Joh7LLAeMZXtonndwhiCyI/q /09oMbpozzcSei6nADZHk3ElYypDkzC45ti6UhfoTJdfkESu+7ELyRDjfpOWp2ga aoLo8K6ZFYYnNz56J34V+RggsQssQdA2cJt/lj+GjnJ3VUeI+S0JAC0XTvpdBI9E GqZH2uKSGKWaDztbe75wtKiEVXqxSMpJIIfJ7u+BGXkLr1rf01kxeO25pDHIH3yl dApFWI183dxWHUmjh0iVRkGwolNH3Ry5c+AnL3hyWwVTaRanCnsPRuXOQLoWM8y1 wHdrR6yEwFTA93Xxljr+o1LyBb4hf5Gpm3w7Kn8ZNlc4vA4w2Ou+5F7Upg8VAoYP MqapFKXqT3lNcR79zVXY2NXz1IHqZxwWQNHW/ytAxgJSTzaHihfOhIaImN0IU5/M Ajv36eW/kqXnX/VfOBRBRTr+SVFdD6A1iURL3emCkpzDpgSryJr5F32DGrKloA+x V9O9VbrwIi8xqGJcpiJU9ttxTnHD1j3J4MknT5z6b8O/725QsZCNXSU8rW+YJ2u/ htxBVWh1d248GXG+jkDG2dlP1GZKjjjsEOw3GCjwN/G8Aa/sjcel7rOV0YLxZ8Py c92JTNJcyh+cXkATF5lO =nyK4 -END PGP SIGNATURE-
