- WG-RIUP - mailman.kantarainitiative.org

Fwd: W3C Workshop Report: Secure the Web Forward
by Tom Jones 01 Feb '24

01 Feb '24

an effort is underway to secure the web https://www.w3.org/2023/03/secure-the-web-forward/report.html their first priorities are "start by documenting threat models on the web and* formulating end-user stories related to security to inform standardization groups*, developers, and policy makers." I would like to add this effort as one of the targets of the RIUP use cases that are now under development in RIUP ..tom ---------- Forwarded message --------- From: Ian Jacobs <ij(a)w3.org> Date: Thu, Feb 1, 2024 at 11:24 AM Subject: Fwd: W3C Workshop Report: Secure the Web Forward To: <public-payments-wg(a)w3.org> Dear Web Payments WG, For those interested in security, W3C published today a report from the September 2023 Workshop "Secure the Web Forward”: https://www.w3.org/2023/03/secure-the-web-forward/report.html Ian Begin forwarded message: *From: *xueyuan <xueyuan(a)w3.org> *Subject: **W3C Workshop Report: Secure the Web Forward* *Date: *February 1, 2024 at 12:59:05 AM CST *To: *chairs(a)w3.org *Resent-From: *chairs(a)w3.org Dear Chairs, The report from the W3C Secure the Web Forward Workshop [1], held online in September 2023 in coordination with OpenSSF, OWASP and OpenJS, is now available: https://www.w3.org/2023/03/secure-the-web-forward/report.html This report contains a brief summary, collects highlights from the live sessions, links to the presentation videos, and details next steps. The workshop was organized to review the state of technologies (existing, in development, or proposed), guidelines, tools, and documentation available to developers to secure applications deployed on the web, and coordinate relevant activities. About 30 people attended the live sessions to discuss the 9 selected position papers along 3 different themes: supply chain security (including Software Bills of Materials, also known as SBOMs), JavaScript security, and developer awareness. Participants acknowledged the growing complexity of web applications and of security related web technologies (e.g., CORS, Content Security Policy), which together makes it challenging for developers to secure applications. The main outcomes are that: - The use of SBOMs, which some regulations may require, could help developers keep track of security vulnerabilities. - A verification mechanism, such as the Source Code Transparency proposal, would allow browsers to validate that the application resources received match the resources advertised by the application developer in a web bundle or an SBOM and possibly analyzed by security researchers. - In parallel, JavaScript execution could be split in Compartments to isolate third party code and keep their power under control. Making this foolproof with the design of the DOM API remains a challenge. - Additionally, same origin realms can be manipulated by an attacker against the web application itself when they are not properly handled. Web applications should have the ability to control, at load time, how the potentially untrusted code they contain can create or access same origin realms. - Cookies are another source of security vulnerabilities. The deprecation of third party cookies creates a unique opportunity to revise the defaults of the cookies model for the web for increased security. - Regardless of technical solutions, a documentation effort is warranted: tutorials, how-tos, references, guides and best practices, targeted at developers as well as policy makers. On top of progressing technical topics mentioned above, one of the suggested next steps is to initiate an activity, possibly hosted within a W3C Community Group, set to take a holistic approach to security and coordinate collaborations with other organizations (OpenSSF, OWASP, OpenJS, Open Web Docs, MDN, IETF, etc.). This activity could start by documenting threat models on the web and formulating end-user stories related to security to inform standardization groups, developers, and policy makers. Progress on this proposal is tracked in a GitHub issue [2]. Interested parties can contact Francois Daoust <fd(a)w3.org>. W3C thanks those who helped with the organization and execution of the workshop, including members of the Program Committee, speakers, the MDN team, the WebDX Community Group and workshop participants. For Philippe le Hégaret, Strategy Lead; Xueyuan Jia, W3C Marketing & Communications [1] https://www.w3.org/2023/03/secure-the-web-forward/ [2] https://github.com/w3c/secure-the-web-forward-workshop/issues/42 -- Ian Jacobs <ij(a)w3.org> https://www.w3.org/People/Jacobs/ Tel: +1 917 450 8783

2 1

For anyone interested in biometric privacy issues
by Tom Jones 30 Jan '24

30 Jan '24

https://www.nextgov.com/emerging-tech/2024/01/tsa-uses-minimum-data-fine-tu… thx ..Tom (mobile)

1 0

Article
by Salvatore D'Agostino 19 Jan '24

19 Jan '24

https://www.nytimes.com/2024/01/17/nyregion/migrants-shelter-snow-nyc.html?… Free read I think Get Outlook for iOS<https://aka.ms/o0ukef>

5 6

Fwd: 2024 Webinars! We've Got A Great Lineup!
by Noreen Whysel 18 Jan '24

18 Jan '24

1 0

My need for IDs
by Salvatore D'Agostino 18 Jan '24

18 Jan '24

https://www.nytimes.com/2024/01/17/nyregion/migrants-shelter-snow-nyc.html?… I don't think this email address post to the list Can you please share Best Sal Get Outlook for iOS<https://aka.ms/o0ukef>

1 0

Fwd: [Speculative F(r)iction in Generative AI] More details
by Noreen Whysel 18 Jan '24

18 Jan '24

The Mozilla foundation is hosting a "Speculative Friction in Generative AI" event on Friday that will focus on AI in Healthcare. Should prove interesting if anyone else can join. Noreen ---------- Forwarded message --------- From: Bogdana Rakova <bogdana(a)mozillafoundation.org> Date: Wed, Jan 17, 2024 at 3:13 PM Subject: [Speculative F(r)iction in Generative AI] More details To: Hi everyone, I'm thrilled to welcome you to the *Speculative F(r)iction in Generative AI* <https://speculativefriction.org/events> event coming up this Friday. Together with Tyler (T) Munyua we will facilitate an interactive and experimental session together with our panelists (see their bios below). To make the discussion more concrete and tangible we'll focus on the use of AI in healthcare and engage with a science fiction approach to interrogating the present state of *governing* such AI systems and how they might change the interactions between patients and clinicians. To allow ourselves to imagine and experience the consequences and implications of possible futures, we will play with a design fiction world where *every AI agent needs to have a social license <https://bobi-rakova.medium.com/the-ai-social-license-9d5ed4dc1815> in order to operate*. Excited to explore this speculative fiction artifact together on Friday and in the meantime ... I'm sending you this quick email to share an invitation for you to bring a wellness artifact to the event. Please think of any kind of physical object that you might interact with to boost your wellness. Panelists bios: - Gemma Petrie - Principal Researcher at Mozilla focused on the intersection of people, competition, and policy. Her research explores the dynamics of the internet ecosystem in order to advocate for technology that puts people first. Recent projects have explored how design frictions like browser choice screens can improve transparency, give people meaningful agency, and help them make choices that better align with their preferences. - Sophia Bazile - Futures Literacy and Foresight practitioner interested in capacity-building for transformative inner, organizational, and wider sociocultural change. Her approaches are multi-/trans-/interdisciplinary, rooted in decolonial praxis, and commitment to collective un/learning through perpetual experimentation. She has designed, curated, and convened inquiries around how technologies* facilitate reciprocal relationships between planetary beings—and the kinds of imagined and imposed relationships they amplify, disrupt, or inhibit. - Richmond Y. Wong - an Assistant Professor of Digital Media at Georgia Tech's School of Literature, Media, and Communication. He directs the Creating Ethics Infrastructures Lab where his research seeks to create social, cultural, and organizational environments that can support technologists and designers in ethical decision-making. This includes creating design approaches that propose alternate ways to consider human values, supporting worker and community-led actions, improving organizational ethics review practices, and understanding the role of law and policy. Recent projects include studying the technology workers’ organizational practices related to ethics, and creating design activities to help people talk through issues related to privacy and surveillance. Thank you! We are all thrilled and excited to connect during the panel and workshop on Friday. Please feel free to reach out to me if you have any questions. With kind regards, Bogdana (Bobi) -- Bogdana Rakova <https://bobirakova.com/> / *Senior Trustworthy AI Fellow, Mozilla Foundation* Experiments: terms-we-serve-with <https://termsweservewith.org/> / speculative f(r)iction <https://speculativefriction.org/> / ecosystemic AI <https://noteforms.com/forms/ecosystemic-ai-working-group-2ttywq?notionforms…> -- Noreen Whysel nwhysel(a)gmail.com http://www.whysel.com

2 1

EU - US Mapping
by Salvatore D'Agostino 17 Jan '24

17 Jan '24

https://www.nist.gov/identity-access-management/eu-us-ttc-wg-1-digital-iden… EU-US TTC WG-1 Digital Identity Mapping Exercise Report<https://www.nist.gov/identity-access-management/eu-us-ttc-wg-1-digital-iden…> Save the Dates! www.nist.gov

1 0

Fw: Request for Comment & IPR Review: PCTF Authentication Final Recommendation V1.1 / Demande de commentaires et d’examen des droits de propriété intellectuelle : Recommandation finale pour la composante « Authentification » V1.1 du CCP
by Salvatore D'Agostino 16 Jan '24

16 Jan '24

fyi ________________________________ From: review(a)diacc.ca <review(a)diacc.ca> Sent: Tuesday, January 16, 2024 9:16 AM To: Salvatore D'Agostino <sal(a)idmachines.com> Subject: Request for Comment & IPR Review: PCTF Authentication Final Recommendation V1.1 / Demande de commentaires et d’examen des droits de propriété intellectuelle : Recommandation finale pour la composante « Authentification » V1.1 du CCP Français à suivre Notice of Intent: DIACC is collaborating to develop and publish the Authentication component of the Pan-Canadian Trust Framework (PCTF) to set a baseline of public and private sector interoperability of identity services and solutions. During this public review period, DIACC is looking for community feedback to ensure that the conformance criteria is clear and auditable. To learn more about the Pan-Canadian vision and benefits-for-all value proposition please review the Pan-Canadian Trust Framework Overview<https://diacc-dot-yamm-track.appspot.com/28zd0TGbiQXtMGiyCf0-eBSKmMAaDA7Pap…>. Document Status: These review documents have been developed by members of the DIACC’s Trust Framework Expert Committee<https://diacc-dot-yamm-track.appspot.com/2JVjj0zymk3OgdDAlfKJ2df4-8B1J0E6aq…> (TFEC) who operate under the DIACC controlling policies and consist of representatives from both the private and public sectors. These documents have been approved by the TFEC as Draft Recommendations V1.0. Summary: The PCTF Authentication Component defines: 1. A set of processes that enable access to digital systems. 2. A set of Conformance Criteria for each process that, when a process is shown to be compliant, enable the process to be trusted. Invitation: • All interested parties are invited to comment. Period: • Opens: January 16, 2024 at 23:59 PT | Closes: February 15, 2024 at 23:59 PT When reviewing the components Conformance Criteria, please consider the following and note that responses to this question are non-binding and serve to improve the PCTF. 1. Would you consider the Conformance Criteria as auditable or not? That is, could you objectively evaluate if an organization was compliant with that criteria and what evidence would be used to justify that? Review Documents: Authentication • Conformance Profile Final Recommendation V1.1<https://diacc-dot-yamm-track.appspot.com/2M8Z3V12SLp8MUG3QHMqeh-FebLTFCXSh2…> • Component Overview Final Recommendation V1.1<https://diacc-dot-yamm-track.appspot.com/2_UrwuzjJv36fkGGUpRMBqldzknvg447mi…> • DIACC Comment Submission Spreadsheet<https://diacc-dot-yamm-track.appspot.com/2zzrG69USxQDWkhLFlf-SlkUz3mc27Q4ZJ…> Intellectual Property Rights: Comments must be received within the 30-day comment period noted above. All comments are subject to the DIACC contributor agreement<https://diacc-dot-yamm-track.appspot.com/2wUO4oqQbPYiwiD7TeT3zluSDz2BPmB3wZ…>; by submitting a comment you agree to be bound by the terms and conditions therein. DIACC Members are also subject to the Intellectual Property Rights Policy<https://diacc-dot-yamm-track.appspot.com/2sXAQWdjzzJN-O9kkyv4ht3zlG_JuCX9zg…>. Any notice of an intent not to license under either the Contributor Agreement and/or the Intellectual Property Rights Policy with respect to the review documents or any comments must be made at the Contributor’s and/or Member’s earliest opportunity, and in any event, within the 30-day comment period. IPR claims may be sent to review(a)diacc.ca<mailto:review@diacc.ca>. Please include “IPR Claim” as the subject. Process: • All comments are subject to the DIACC contributor agreement.<https://diacc-dot-yamm-track.appspot.com/2xPVELHmtVpGVq7KPHbf-yykBn453MTDA1…> • Submit comments using the provided DIACC Comment Submission Spreadsheet<https://diacc-dot-yamm-track.appspot.com/2BCNYzUMyQo19ji6dHLiHF5mhKNKM8hQpb…>. • Reference the draft and corresponding line number for each comment submitted. • Email completed DIACC Comment Submission Spreadsheet to review(a)diacc.ca<mailto:review@diacc.ca>. • Questions may be sent to review(a)diacc.ca<mailto:review@diacc.ca>. Value to Canadians: The purpose of the PCTF Authentication Component is to assure the on-going integrity of login and authentication processes by certifying, through a process of assessment, that they comply with standardized Conformance Criteria. The Conformance Criteria for this component may be used to provide assurances: • That Trusted Processes result in the representation of a unique Subject at a Level of Assurance that it is the same Subject with each successful login to an Authentication Service Provider. • Concerning the predictability and continuity in the login processes that they offer or on which they depend. All participants will benefit from: • Login and authentication processes that are repeatable and consistent (whether they offer these processes, depend on them, or both). • Assurance that identified Users can engage in authorized interactions with remote systems. Relying Parties benefit from: • The ability to build on the assurance that Authentication Trusted Processes uniquely identify, at an acceptable level of risk, a Subject in their application or program space. Context: The purpose of this review is to ensure transparency in the development and diversity of a truly Pan-Canadian, and international, input. In alignment with our Principles for an Identity Ecosystem<https://diacc-dot-yamm-track.appspot.com/2ksQhMCqNZdn6rnZ9QzKU29MFfDmfnXdTS…>, processes to respect and enhance privacy are being prioritized through every step of the PCTF development process. DIACC expects to modify and improve these Draft Recommendations based upon public comments. Comments made during the review will be considered for incorporation into the next iteration and DIACC will prepare a Disposition of Comments to provide transparency with regard to how each comment was handled. Demande de commentaires et d’examen des droits de propriété intellectuelle : Recommandation finale pour la composante « Authentification » V1.1 du CCP Déclaration d’intention : Le CCIAN collabore pour développer et publier la composante « Authentification » du Cadre de confiance pancanadien (CCP) afin d’établir une base d’interopérabilité des services et solutions d’identité dans les secteurs public et privé. Pendant cette période d’examen public, le CCIAN cherche à obtenir la rétroaction de la communauté afin de s’assurer que les critères de conformité sont clairs et vérifiables. Pour en savoir plus sur la vision pancanadienne et la proposition de valeur présentant des avantages pour tous, veuillez passer en revue l’aperçu du Cadre de confiance pancanadien<https://diacc-dot-yamm-track.appspot.com/27MmefMLXId_ALqTYKoxYoZzoCqfqY2v25…>. État des documents : Ces documents à examiner ont été développés par les membres du Comité d’experts du Cadre de confiance<https://diacc-dot-yamm-track.appspot.com/2N0Yr90YBrPviuqPy36nxrqZtVh_lGxCwm…> (TFEC) du CCIAN, qui sont régis par les politiques qui contrôlent le CCIAN et comprennent des représentants des secteurs privé et public. Ces documents ont été approuvés par le TFEC en tant que recommandations préliminaires V1.0. Résumé La composante « Authentification » du CCP définit : 1. Un ensemble de processus donnant accès à des systèmes numériques. 2. Un ensemble de critères de conformité pour chaque processus qui, lorsqu’un processus s’avère conforme, permettent de faire confiance au processus. Invitation • Toutes les parties intéressées sont invitées à faire des commentaires. Période • Début : 16 janvier 2024 à 23 h 59 HP | Fin : 15 février 2024 à 23 h 59 HP En examinant les critères de conformité de la composante, veuillez tenir compte de la question qui suit et noter que les réponses ne sont pas contraignantes et visent à améliorer le CCP. 1. Considéreriez-vous que les critères de conformité sont vérifiables ou non? Autrement dit, pourriez-vous évaluer objectivement si une organisation était conforme à ces critères et quelles preuves seraient utilisées pour justifier cela? Documents à examiner : Authentification • Recommandation finale pour le profil de conformité V1.1<https://diacc-dot-yamm-track.appspot.com/2ctYL1VKYGuy6_IFd-oB8J6Q7hC9ZzyO7D…> • Recommandation finale pour l’aperçu de la composante V1.1<https://diacc-dot-yamm-track.appspot.com/2sXJn5gCX1gdfN1siuDcak3ymelufC6wAj…> • Formulaire pour soumettre les commentaires au CCIAN<https://diacc-dot-yamm-track.appspot.com/2Gy7LT9i7f3j200ngGQpekpUhfVCmvFfwc…> Droits de propriété intellectuelle Les commentaires doivent être reçus pendant la période de 30 jours indiquée ci-dessus. Tous les commentaires sont assujettis à l’entente de contributeur du CCIAN<https://diacc-dot-yamm-track.appspot.com/2Lw9MP8jccVK9cCLDyCEqLHOwQa1X9yjVh…>; en soumettant un commentaire, vous acceptez d’être lié par les conditions qu’elle renferme. Les membres du CCIAN sont également assujettis à la politique sur les droits de propriété intellectuelle<https://diacc-dot-yamm-track.appspot.com/2HwME7dSShmy58bj59XfaupLZJkKjicW0I…>. Tout avis d’intention de ne pas octroyer une licence en vertu de l’entente de contributeur et/ou de la politique sur les droits de propriété intellectuelle relativement aux documents à examiner ou à des commentaires doit être donné dès que le contributeur et/ou le membre en ont la possibilité, et en toute circonstance, pendant la période de commentaires de 30 jours. Les revendications au titre des droits de propriété intellectuelle peuvent être adressées à review(a)diacc.ca<mailto:review@diacc.ca>. Veuillez indiquer « Revendication en matière de propriété intellectuelle » dans l’objet. Processus • Tous les commentaires sont assujettis à l’entente de contributeur du CCIAN.<https://diacc-dot-yamm-track.appspot.com/2kl7ImnTN3w4K_6XsCd3-TGi_hl2w0prNp…> • Veuillez utiliser le formulaire prévu à cet effet pour soumettre vos commentaires au CCIAN<https://diacc-dot-yamm-track.appspot.com/2z-tuDYuVY1IjHZdJ6rStPmg0BczQ0CZ3i…>. • Assurez-vous d’indiquer le numéro de version et de ligne correspondant à chaque commentaire soumis. • Le formulaire de soumission de commentaires au CCIAN doit être envoyé par courriel, dûment rempli, à review(a)diacc.ca<mailto:review@diacc.ca>. • Questions : review(a)diacc.ca<mailto:review@diacc.ca>. Valeur pour les Canadiens La composante « Authentification » du CCP vise à assurer l’intégrité continue des processus de connexion et d’authentification en certifiant, au moyen d’un processus d’évaluation, qu’ils sont conformes aux critères de conformité uniformisés. Les critères de conformité pour cette composante peuvent être utilisés pour fournir des assurances : • Comme quoi les processus de confiance donnent la représentation d’un sujet unique à un niveau assurant qu’il s’agit du même sujet à chaque connexion réussie auprès d’un fournisseur de services d’authentification. • En ce qui concerne la prévisibilité et la continuité des processus de connexion qu’ils offrent ou dont ils dépendent. Tous les participants bénéficieront de : • Processus de connexion et d’authentification qui sont répétitifs et uniformes (qu’ils offrent ces processus, dépendent d’eux ou les deux). • L’assurance que les utilisateurs identifiés peuvent prendre part à des interactions autorisées avec des systèmes à distance. Les parties dépendantes bénéficieront de : • La capacité de tirer parti de l’assurance comme quoi les processus de confiance de l’authentification identifient d’une manière unique, à un niveau de risque acceptable, un sujet dans la sphère de leur application ou programme. Contexte Cet examen a pour but d’assurer la transparence de l’élaboration et de la diversité d’un apport véritablement pancanadien et international. Conformément à nos principes pour un écosystème de l’identité<https://diacc-dot-yamm-track.appspot.com/2UMztnwll9w8ucFCqy6LOFfMh82fYc8j7u…>, la priorité est accordée aux processus visant à respecter et à renforcer la vie privée à chaque étape du processus de développement du Cadre de confiance pancanadien. Le CCIAN s’attend à modifier et à améliorer ces recommandations finales en fonction des commentaires du public. Les commentaires faits pendant l’examen seront pris en compte pour être intégrés dans la prochaine itération et le CCIAN préparera un document expliquant d’une façon transparente comment chaque commentaire a été traité.

2 1

RIUP WG meeting tomorrow, Jan 16, 2024 at 1 PM ET
by jim kragh 15 Jan '24

15 Jan '24

*RIUP's 1st/3rd Tuesday Meeting Link:* https://us06web.zoom.us/j/87499194761?pwd=cmhDTHBXV2VTbFBMZzllMlZVbnFoZz09 Meeting ID: 874 9919 4761 *Passcode: 837815* Dial by your location +1 346 248 7799 US (Houston) +1 646 558 8656 US (New York) +1 669 900 9128 US (San Jose) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Washington DC) +1 312 626 6799 US (Chicago) Meeting ID: 874 9919 4761 Passcode: 837815 *Good afternoon! * *Agenda:* The RIUP Digital Identifier Inclusion document is in the hands of the Kantara Leadership Council for review and acceptance. Our next step involves the *RIUP Use Cases URL *link (content below if link fails) . https://docs.google.com/document/d/1-amM1fVtVKEILrXFbLBnVZ9S_BfpZW3s/edit?u… *Before we will tackle* *USE CASES* *with Tom*, we will start with a follow up session from two weeks ago with Jorge Flores, with ENTIDAD. Jorge will be joining RIUP WG, and today he will be sharing with us how he and his colleagues have reached out and engaged rural communities, farmworkers and their ecosystems. I envision we will hear some proven and basic take-away themes regarding ground level engagement; first steps in building trust using core technology. May all have a good afternoon and evening, enjoy family and friends, JIm =====================================================================================================================================================================================================================================================================================================------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This is a copy of the RUIP USE CASE content if the link above fails Farmworker in a Foreign Country Moderator: Tom Jones The details will vary from country to country but the barriers remain to be resolved wherever they arise. Each Subject Needs - Right to Work legally (H2A, Green Card, etc) - Medical Care (eg access to Medicaid or other tax supported programs) - Farm and Food Workers relief grantFood and Farmworkers relief program (FFWR) <https://www.ams.usda.gov/services/grants/ffwr> (created during Pandemic) some documentation not including immigration status (etc) - Proof of work status to get service (when person is not documented) (photo of paystub, letter) - Credentials to include scanned documents (See Tom’s youtube video <https://www.youtube.com/watch?v=Tq4hw7X5SW0>) - Cannot receive USPS mail - Support self, wife, children (delegated authority) - Send payments home - Receiving cash distributions (virtual debit card) May arrive after the farmworker has move on - Use someone else’s phone to access personal records or apply for a benefit - Paying taxes and unscrupulous attacks, including online attacks (e.g. example FFWR fraud incident <https://bakersfieldnow.com/news/local/delano-pd-scammers-attempt-to-defraud…> ) Solution - Identifier - user created is a possibility, but enterprise created email address is common - Notifications of changes of breaches from enterprises that hold user data - Can there be a back-up data store in the cloud to restore after loss of phone - Verifiable Credentials and decentralized Identifiers. - Account with consulate - Nonprofits like the Centro Cultural Mexicano Redmond Washington https://www.centroculturalmexicano.org/ - Rent Assistance | Asistencia Para la Renta <https://www.centroculturalmexicano.org/rent-assistance> - Events | Eventos <https://www.centroculturalmexicano.org/events> - Radio ¡Ya Es Tiempo! <https://www.centroculturalmexicano.org/listen-to-radio> - Resources | Recursos <https://www.centroculturalmexicano.org/new-folder> - Programs | Programas <https://www.centroculturalmexicano.org/programs-programas> - Scholarship | Beca <https://www.centroculturalmexicano.org/scholarship> - Small Businesses | Pequeños Negocios <https://www.centroculturalmexicano.org/sbrn> - Seattle Domestic Workers Ordinance <https://www.centroculturalmexicano.org/dseattle-domestic-workers-ordinance> - Mi Casa | Maker Space <https://www.centroculturalmexicano.org/79457969> - Makerspace | Espacio de Creación <https://www.centroculturalmexicano.org/makerspace> - The Time is Now! | ¡Ya Es Tiempo! <https://www.centroculturalmexicano.org/ya-es-tiempo-2> - Employment Opportunities I Oportunidades de Empleo <https://www.centroculturalmexicano.org/employment> - Mobile Wallet including older models - Is a smart phone enough - offline access - no phone home requirement - get older phones from telcos and manufacturers - Low cost smart phones are often issued to migrants under federal programs (e.g llifeline-program-low-income-consumers <https://www.fcc.gov/general/lifeline-program-low-income-consumers>) - Walmart has a phone for $30, but connectivity is costly and comes and goes. - Biometrics or any scanned artifact - Liveness detection (proof of presence, etc) - will help with back-up and restore - Interoperability - Third-party validation and support programs - often with non-profits (unions, medical) - Audit (ledgers, receipts, log, etc.) - deduplication - Education - Preparese <https://www.preparese.info/> - Western Union or other funds transfer capabilities - https://blackhawknetwork.com/ - Can we help non-profits address and fund these issues - Direct engagement with usda https://www.usda.gov/topics/farming/grants-and-loans Immigrant waiting to Cross the border Note that the details here are taken from the US Customs and Border Patrol (CBP) but would equally apply to any controlled border with a surplus of immigrant applicants but with some difference in the details. Each Subject Needs - Approved access to asylum - To understand a set of rules in a language that they do not understand well, if at all - To follow an existing set of asylum rules which have little to do with current events - Some proof that the meet the existing set of rules - A translator that can make it clear to them what else they need to do or to provide - Regular check-ins with Immigration and Customs Enforcement ( border-migrants-cell-phones-cec <https://www.cnn.com/2022/06/05/us/border-migrants-cell-phones-cec/index.html> ) SolutionSeparated Communities There are many reasons why some people choose, or are forced, to live separated from the dominant social order. These include historical, language, religion, economic, family or other social structures that are more congenial or accepting of their own identity. Since the dominant social order typically has the political and economic power to structure society to their own best interests, those living apart are seldom able to exercise their own rights as they choose. Specifically excluded from this category are those people rich enough to travel where and when they desire. Separated communities are found in all nations large enough to give them the space to form. Some such communities include: - indigenous where a foreign people have taken their land in the Americas and elsewhere, - homeless or street people who do have have a safe place to call home, - Roma of Europe and Travelers of Ireland, among others that chose to roam, - Uyghurs of China, Rohingya of Burma, Catalans of Spain and other stateless nations <https://en.wikipedia.org/wiki/Stateless_nation>, - any rural population in an industrialized country that chose a quiet, familiar location. Each Subject Needs - Privacy, meaning the right to be let alone, as they often do not want to be assimilated - Access to the same rights and privileges as the bulk of the nation’s people where they live

1 0

Canceled event: RIUP WG @ Tue Dec 31, 2024 1pm - 2pm (EST) (wg-riup@kantarainitiative.org)
by Kantara Initiative 11 Jan '24

11 Jan '24

This event has been canceled. RIUP WG Tuesday Dec 31, 2024 ⋅ 1pm – 2pm Eastern Time - New York Location Join Zoom Meeting https://us06web.zoom.us/j/87499194761?pwd=cmhDTHBXV2VTbFBMZzllMlZVbnFoZz09 https://www.google.com/maps/search/+Join+Zoom+Meeting+https:%2F%2Fus06web.z… Resilient Identifiers for Underserved Populations (RIUP) Work Group - Meeting weekly on the first and third Tuesday's at 1PM ESTTopic: RIUPKantara Initiative is inviting you to a scheduled Zoom meeting.Join Zoom Meetinghttps://us06web.zoom.us/j/87499194761?pwd=cmhDTHBXV2VTbFBMZzllMlZVbnFoZz09Meeting ID: 874 9919 4761Passcode: 837815Topic: RIUP Working GroupTime: Sep 19, 2023 01:00 PM Eastern Time (US and Canada) Every 2 weeks on Tue, until Nov 28, 2023, 6 occurrence(s) Sep 19, 2023 01:00 PM Oct 3, 2023 01:00 PM Oct 17, 2023 01:00 PM Oct 31, 2023 01:00 PM Nov 14, 2023 01:00 PM Nov 28, 2023 01:00 PMPlease download and import the following iCalendar (.ics) files to your calendar system.Weekly: https://us06web.zoom.us/meeting/tZMpfuCppz8tHNVQbiIRnAIOWuTndZJ8mbJV/ics?ic… tap mobile+13052241968,,87499194761#,,,,*837815# US+13092053325,,87499194761#,,,,*837815# US---Dial by your location• +1 305 224 1968 US• +1 309 205 3325 US• +1 312 626 6799 US (Chicago)• +1 646 558 8656 US (New York)• +1 646 931 3860 US• +1 301 715 8592 US (Washington DC)• +1 253 205 0468 US• +1 253 215 8782 US (Tacoma)• +1 346 248 7799 US (Houston)• +1 360 209 5623 US• +1 386 347 5053 US• +1 507 473 4847 US• +1 564 217 2000 US• +1 669 444 9171 US• +1 689 278 1000 US• +1 719 359 4580 US• +1 720 707 2699 US (Denver)• +353 1 536 9320 Ireland• +353 1 653 3895 Ireland• +353 1 653 3897 Ireland• +353 1 653 3898 Ireland• +353 6 163 9031 Ireland• +353 1 240 8941 Ireland• +39 021 241 28 823 Italy• +39 069 480 6488 Italy• +39 020 066 7245 Italy• +1 438 809 7799 Canada• +1 587 328 1099 Canada• +1 647 374 4685 Canada• +1 647 558 0588 Canada• +1 778 907 2071 Canada• +1 780 666 0144 Canada• +1 204 272 7920 Canada• +61 8 7150 1149 Australia• +61 2 8015 6011 Australia• +61 3 7018 2005 Australia• +61 7 3185 3730 Australia• +61 8 6119 3900 Australia• +43 72 011 5988 Austria• +43 120 609 3072 Austria• +43 12 535 501 Austria• +43 12 535 502 Austria• +43 670 309 0165 Austria• +44 203 481 5237 United Kingdom• +44 203 481 5240 United Kingdom• +44 203 901 7895 United Kingdom• +44 208 080 6591 United Kingdom• +44 208 080 6592 United Kingdom• +44 330 088 5830 United Kingdom• +44 131 460 1196 United KingdomMeeting ID: 874 9919 4761Passcode: 837815Find your local number: https://us06web.zoom.us/u/kc6npe25Uy Guests nwhysel(a)gmail.com kragh65(a)gmail.com Kantara Staff armin(a)kantarainitiative.org thomasclinganjones(a)gmail.com Kay Chopard ichhatwa(a)gmail.com amanda(a)kantarainitiative.org wg-riup(a)kantarainitiative.org Salvatore D'Agostino ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 0