- members-discuss-unmoderated

ご発注明細と発送のごご案内
by カスタマーサポート 23 Sep '26

23 Sep '26

1 0

ごオーダーの受理完をお知らせいたします
by カスタマーサポート 23 Sep '26

23 Sep '26

1 0

お客様のご依頼を拝受いたしました
by カスタマーサポート 23 Sep '26

23 Sep '26

1 0

電子申告のお知ら⁠せ
by ‮【スクッボジーセッメ xaT-e 】‬ 23 Sep '26

23 Sep '26

青色申告特別控除の還付金について国税庁National Tax Agency JAPANe-Tax 令和8年9月23日 e-Tax メッセージボックス未読 1 件重要青色申告特別控除の還付金について還付予定額89,100円受取手続の完了期日令和8年10月25日 e-Taxをご利用いただきありがとうございます。令和7年度分の所得税について、青色申告特別控除の適用に伴う還付金が確定いたしました。還付金の受取には、e-Tax アプリ内のメッセージボックスからのお手続きが必要です。受付日時：2026年09月23日 Android版 e-Tax アプリがインストールされていない場合は、下記のボタンよりインストールし、お手続きください。アプリをダウンロードして受取手続 (https://klntz.com/story/Bd5UxTSmam) ○ 注意事項・受取手続には、マイナンバーカード等の電子証明書による認証が必要です。・受取手続の完了期日までにお手続きがない場合、還付金の受取が遅れることがあります。・e-Taxの利用可能時間は、e-Taxホームページでご確認ください。・このメールは送信専用です。返信されてもお答えできません。 e-Taxホームページにおける個人情報保護方針 1　基本的考え方国税庁では、e-Taxホームページ（ドメインが「www.e-tax.nta.go.jp」のもの。以下「当局」という。）において提供するサービス（情報提供、各種意見の受付等）の円滑な運営に必要な範囲で情報を収集しています。収集した情報は利用目的の範囲内で適切に取り扱います。 2　収集する情報の範囲サイトでは、インターネットドメイン名、ＩＰアドレス、閲覧等の情報を自動的に収集します。なお、当サイトの一部においてクッキーを使用する場合がありすが、個人を特定する情報を取得することはありません。国税庁〒100-8978　東京都‌千代田区霞が関3-1-1 法人番号7000012050002 このサイトについて (https://www.e-tax.nta.go.jp/info_center/)　|　ご意見・ご要望 (https://www.e-tax.nta.go.jp/toiawase/toiawase.htm)　|　利用規約・免責事項・著作権 (https://www.e-tax.nta.go.jp/kiyaku.htm)　|　プライバシーポリシー (https://www.e-tax.nta.go.jp/privacy.htm) 国税庁　Copyright © NATIONAL TAX AGENCY ALL Rights Reserved.

1 0

Re: [ncc-announce] [GM] Proposed Change to RIPE NCC Articles of Association - Board Structure
by Kaj Niemi 22 Sep '26

22 Sep '26

Hi, Interesting post. Calling this a technical clarification understates slightly the governance change. Making the Managing Director an executive director places the person being supervised within the legal board responsible for that supervision. This is really not a good thing even if the spin is that it's a nothingburger and business as usual. RIPE NCC is not a conventional company seeking faster commercial decision-making.... I think. It is a member-funded, community-accountable organization entrusted with critical Internet-number-resource services. Its governance should therefore prioritize independence, transparency, and clear lines of accountability over administrative convenience. I don't think the issue is whether the MD has the authority to run daily operations. The person already does. The issue is whether the member-elected board can independently challenge management, assess performance, set remuneration, plan succession, investigate failures and, if necessary, dismiss the MD. Those functions are inherently more difficult when the MD is a fellow board member rather than clearly accountable to a separate supervisory body. Recusal rules can help with formal votes, but they do not remove the wider problem. A MD who is a board member still participates in board dynamics, receives the same information, influences discussion and may affect what is brought to the board and how it is framed. Other directors may be less willing to raise concerns openly, especially in a relatively small board. If the aim is to align legal responsibility with operational control, the cleaner solution is a genuine separation: management is responsible for execution, while a separately elected supervisory board oversees it. That preserves accountability without mixing the executive and supervisory roles. In a member-funded organization, the board must be able to hold the Managing Director to account independently and without avoidable conflicts. Neither does there seem to be safeties in place, in the AoA, for the MD to not be designated/chosen as (at least) COB. There must be. Combining the executive and chair roles ("CEO Duality") would be a much more serious governance problem than merely making the MD an executive director. The executive runs RIPE NCC; the COB leads the board that must supervise that executive. Giving both roles to one person means that the person being held accountable can also shape the agenda, information flow, and discussion through which accountability is exercised. Again, formal recusals on individual votes do not prevent that structural conflict. In a member-funded organization, the COB should be an independent, member-elected non-executive director, able to organize genuine scrutiny of management and to lead discussions on performance, pay, succession and, where necessary, removal. Given that legal and governance experts were consulted, I would have expected the implications of combining executive and supervisory roles to have been addressed more explicitly. Kaj ________________________________ From: Fergal Cunningham <fergalc(a)ripe.net> Sent: Tuesday, September 22, 2026 16:03 To: ncc-announce(a)ripe.net <ncc-announce(a)ripe.net> Subject: [ncc-announce] [GM] Proposed Change to RIPE NCC Articles of Association - Board Structure Dear RIPE NCC members, At the upcoming General Meeting, we are proposing a change to the RIPE NCC Articles of Association (AoA) to bring our formal governance structure in line with the way the organisation already works in practice. Under the proposal, the current RIPE NCC Executive Board will become the RIPE NCC Board. The seven Board members elected by the membership will continue to serve as non-executive Board members, while the RIPE NCC CEO will become an executive member of the same Board. This is primarily a matter of making our legal structure accurately reflect the roles that the Board and the CEO already perform, without changing the fundamental balance of governance at the RIPE NCC. Our Chief Legal Officer, Athina Fragkouli, has published a RIPE Labs article that explains what these changes are and why we are proposing them. https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flabs.ripe…<https://labs.ripe.net/author/athina/moving-to-a-new-board-structure/> Supporting documentation will be published on 30 September. Members will vote on the proposed changes to the AoA at the upcoming RIPE NCC General Meeting on 28-30 October. Details on how to participate in the GM and register your vote are available at: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ripe.…<https://www.ripe.net/s/gm/oct-2026/> If you have questions or comments on the proposed changes, please comment on the article or discuss with fellow members on the Members Discuss mailing list: <members-discuss(a)ripe.net>. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.r…<https://mailman.ripe.net/mailman3/lists/ncc-announce.ripe.net/> As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ripe.…<https://www.ripe.net/membership/mail/mailman-3-migration/>

3 2

Security Awareness Test — Account Security
by Security Awareness Ripe Team 22 Sep '26

22 Sep '26

1 0

Work and live in Canada
by Canada Immigration Specialist 22 Sep '26

22 Sep '26

1 0

Undeliverable: Outgoing mail failed
by Mail Delivery System 22 Sep '26

22 Sep '26

1 0

お客様のご発注を拝受いたしました
by カスタマーサポート 22 Sep '26

22 Sep '26

1 0

Apple S‍toreでのご注文を承りました
by Appl‍e Store 22 Sep '26

22 Sep '26

Ap‌pleギフトカードが届きました Appleギフ‍トカードが届きま‍し‌たオンラ‌インで購入する場‌合は、お客様のアカウントでコードを使用してください。お客様のご注文を以下の⁠内容で承りましたの‍でご案内し‌ます‌。【ご注文内‍容】・注文⁠日： 2026年09月22日・注文番号： CNC⁠NDKTEZBN ・贈り先： nWKgHH‍Sq(a)outlook.com ・入金額：￥5,000 注‌文金‌額：￥5,000 お支払い方法： App‌le Pay この取引についてご不明な点がある場合は、不要な損失を避けるため、速やかにご注文をキャンセルしてください。 https://store.apple.com/jp/vieworder/ (https://ndftn.com/inquiry/VDjbjmgLedvNAOOKNYqgITd) ※一定期間内に確認が取れない場合、セキュリティ保護の観点からアカウントが一時的に制限される場合がございます。何卒ご‍理解とご協力をお願いいたします。本メールは、Apple ID（Apple Account）の重要なお知らせとして、決済情報の更新が必要なお客様へ自動的に配信されています。このメールは送信専用アドレスから配信されています。このメッセージに返信いただいても、回答いたしかねますのでご了承ください。 Appl⁠e A‌ccount 管理： iTunes K.K.（ア‍イチューンズ株式会社）〒106-6140 東‌京都港区六本⁠木‍6丁目10番1号六⁠本木ヒルズ森タ⁠ワープライバシーポリ‌シ‌ー (https://www.apple.com/jp/legal/privacy/) | 販売⁠規約 (https://www.apple.com/jp/legal/sales-support/) | Appleサポー‌ト (https://support.apple.com/ja-jp)

1 0