<?xml version='1.0' encoding='utf-8'?>

<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.17 (Ruby 3.0.2) -->

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-iab-bias-workshop-report-02" number="9707" updates="" obsoletes="" category="info" consensus="true" submissionType="IAB" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.21.0 --> version="3" xml:lang="en">

  <front>
    <title abbrev="BIAS Workshop Report">IAB Barriers to Internet Access of Services (BIAS) Workshop Report</title>

<!-- [rfced] We see that post-8073 IAB RFCs that discuss workshops
use a different title format - along the lines of either "Report from
the IAB Workshop on ..." (fairly common) or "IAB Workshop Report:
Measuring Network Quality for End-Users" (RFC 9318 only).  May we
update the document title as follows?

Original:
 IAB Barriers to Internet Access of Services (BIAS) Workshop Report

Suggested:
 Report from the IAB Workshop on Barriers to Internet Access of
                        Services (BIAS)
-->

    <seriesInfo name="Internet-Draft" value="draft-iab-bias-workshop-report-02"/> name="RFC" value="9707"/>
    <author fullname="Mirja Kühlewind">
      <organization/>
      <address>
        <email>ietf@kuehlewind.net</email>
      </address>
    </author>
    <author fullname="Dhruv Dhody">
      <organization/>
      <address>
        <email>dd@dhruvdhody.com</email>
      </address>
    </author>
    <author fullname="Mallory Knodel">
      <organization/>
      <address>
        <email>mknodel@cdt.org</email>
      </address>
    </author>
    <date year="2024" month="June" day="20"/> month="December"/>

    <keyword>Internet Access</keyword>
    <keyword>Censorship</keyword>
    <keyword>community networks</keyword>
    <keyword>Community Networks</keyword>
    <keyword>digital divide</keyword>

    <abstract>
      <?line 218?>
<t>The "Barriers for to Internet Access of Services (BIAS)" workshop was convened by the Internet Architecture Board (IAB) from January 15-17, 2024 as a three-day online meeting.  Based on the submitted position papers, the workshop covered three areas of interest: the role of community networks Community Networks in Internet Access of Services; Services, reports and comments on the observed digital divide; divide, and measurements of censorship and censorship circumvention. This report summarizes the workshop's discussion discussions and serves as a reference for reports on the current barriers to Internet Access.</t> Access.

<!-- [rfced] Abstract:  We changed "Barriers for" to "Barriers to"
per the document title and
<https://datatracker.ietf.org/group/biasws/about/>.  Please let us
know any concerns.

Original:
 The "Barriers for Internet Access of Services (BIAS)" workshop was
 convened by the Internet Architecture Board (IAB) from January 15-17,
 2024 as a three-day online meeting.

Currently:
 The "Barriers to Internet Access of Services (BIAS)" workshop was
 convened by the Internet Architecture Board (IAB) from January 15-17,
 2024 as a three-day online meeting. -->

</t>
      <t>Note that this document is a report on the proceedings of the workshop.  The views and positions documented in this report were expressed during the workshop by participants and do not necessarily reflect the IAB's views and positions.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://intarchboard.github.io/draft-iab-bias-workshop-report/draft-iab-bias-workshop-report.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-iab-bias-workshop-report/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/intarchboard/draft-iab-bias-workshop-report"/>.</t>
    </note>
  </front>
  <middle>
    <?line 224?>

<section anchor="introduction">
      <name>Introduction</name>

<!-- [rfced] Please review the guidance for IAB documents
(https://www.rfc-editor.org/materials/iab-format.txt)
and let us know if any changes are needed. Specifically,
would you like to add this paragraph to the introduction?

"The following boilerplate paragraph SHOULD appear in the introduction:

      The Internet Architecture Board (IAB) holds occasional workshops
      designed to consider long-term issues and strategies for the
      Internet, and to suggest future directions for the Internet
      architecture.  This long-term planning function of the IAB is
      complementary to the ongoing engineering efforts performed by working
      groups of the Internet Engineering Task Force (IETF)."
-->

      <t>The Internet as part of the critical infrastructure affects many aspects of our society significantly, although it impacts different parts of society differently. The Internet is an important tool to reach for reaching the Sustainable Development Goals (SDG) (SDGs) listed in <xref target="SDG"/> target="SDGs"/> and to for globally support supporting human rights. Consequently, the lack of meaningful access to digital infrastructure and services is also a form of disenfranchisement.</t>
      <t>Solely having Internet access is not enough. At the same time as we work to connect the next billion people and reduce the digital divide, it is also important to understand persistent and novel inequalities in the digital age when accessing content and services. There are more and more barriers to meaningful access to the services and applications that run on the Internet. Even if Internet connectivity is available, information and service access may remain challenged and unequal.</t>
      <t>This IAB workshop has aimed</t> aimed to</t>
      <ul spacing="normal">
        <li>
          <t>to
          <t>collect reports about barriers to accessing content and services on the Internet, e.g., based on filtering, and blocking as well as due to general inequality of technological capabilities, like device or protocol limitations.

<!-- [rfced] Section 1:  We had trouble parsing this sentence.  To
what does "based on" refer?  Also, please clarify "as well as due to".

Original:
 This IAB workshop has aimed

 *  to collect reports about barriers to accessing content and
    services on the Internet, e.g. based on filtering, and blocking as
    well as due to general inequality of technological capabilities,
    like device or protocol limitations.</t> limitations.

Possibly (we changed "has aimed" to "aimed", as the workshop took
  place about a year ago):
 This IAB workshop aimed to collect reports about barriers to
 accessing content and services on the Internet.  For example,

 *  based on filtering

 *  based on blocking

 *  due to general inequality of technological capabilities, e.g.,
    device or protocol limitations. -->
</t>
        </li>
        <li>
          <t>to help
          <t>help the Internet community get a better understanding of how the Internet functions in different parts of the world and which technology or techniques need to be used to gain access to content.</t>
        </li>
        <li>
          <t>to build
          <t>build an understanding of what "being connected" to the Internet means: What is the Internet to users? What is needed to be meaningfully connected? What are the minimum requirements to be able to access certain parts of the content and services provided over the Internet?</t>
        </li>
      </ul>
      <section anchor="about-this-workshop-report-content">
        <name>About this workshop report content</name> the Content of This Workshop Report</name>
        <t>This document is a report on the proceedings of the workshop. The views and positions documented in this report are were expressed during the workshop by participants and do not necessarily reflect the IAB's views and positions.</t>
        <t>Furthermore, the content of the report comes from presentations given by workshop participants and notes taken during the discussions, without interpretation or validation.  Thus, the content of this report follows the flow and dialogue of the workshop but does not attempt to capture a consensus.</t>
      </section>
    </section>
    <section anchor="workshop-scope-and-discussion">
      <name>Workshop Scope and Discussion</name>
      <t>The workshop was organized across three days with all-group discussion slots, one per day. The following topic areas were identified identified, and the program committee organized paper submissions into three main themes for each of the three discussion slots. During each discussion, those papers were presented sequentially with open discussion held at the end of each day.</t>
      <section anchor="session-1-community-networks-their-role-in-internet-access-of-services">
        <name>Session 1: Community Networks - Their Role in Internet Access of Services</name>
        <t>The first day of the workshop focused on the role of Community Networks <xref target="RFC7962"/> as a way to overcome the barriers to Internet Access. Community Networks are self-organized networks wholly owned by the community and thus provide an alternative mechanism to bring connectivity and internet services to those places that lack commercial interest.</t>
        <t>Presentations ranged from highlighting the need for measuring Quality of Experience (QoE) for Community Networks, to the potential role the Content Delivery Network (CDN) can play in Community Networks, to the role of Satellite Networks, and finally, to the vital role of the spectrum in this space.</t>
        <section anchor="the-quality-of-community-networks">
          <name>The Quality of Community Networks</name>
          <t><xref target="MARTINEZ"/> highlighted the need to address Quality of Experience (QoE) QoE in discussions around Community Networks. As a community-driven deployment, the knowledge and involvement of individuals can vary; therefore, there are no guarantees of connectivity or quality of service. There is a need to focus on user expectations and how they translate to measurable performance indicators. Further, it asks for better documenting documentation of best practices in deploying community networks Community Networks as well as considering careful thought regarding manageability considerations for community networks Community Networks in protocol development. <xref target="GUIFI"/> as an example Community Network was discussed discussed, and some existing resources for Community Networks (<xref target="APC"/>, <xref target="ISOC"/>, and target="APC"/> <xref target="ISOC"/> <xref target="TBB"/>) target="TBB"/> were shared by the participants.</t>
          <t>The inconsistent quality and performance of Satellite Internet is result in a connectivity gap for community networks Community Networks that rely on non-terrestrial networks (NTNs) for internet access <xref target="HU"/>.</t>
        </section>
        <section anchor="strengthening-community-networks">
          <name>Strengthening Community Networks</name>
          <t><xref target="BENSON"/> focused on the prohibitive cost of the transit and Internet service services for Community Networks and argued for Content Delivery Networks (CDNs) CDNs to provide transit-like and Internet services services, at no more than at-cost at-cost, in a mutually beneficial way. Community networks Networks still need backhaul to and from the CDN's point of presence presence, and models for community-backhaul and open-source CDNs were highlighted. Discussion included the status of Project PANGEA <xref target="PANGEA"/> project status as well as legal and commercial considerations in related to such use of CDNs.</t>
          <t><xref target="HU"/> highlighted that Satellite Internet provided by advanced LEO low-Earth orbit (LEO) satellite constellations can play a pivotal role in closing the connectivity gap in the urban-rural digital divide via Satellite-dependent community networks. Community Networks. These existing known performance and management gaps need focus to be focused on, to enable Satellite Internet to resolve the divide. Further, research directions such as multi-layer satellite networking, autonomous maintenance, and integration between Terrestrial and Non-Terrestrial terrestrial networks and NTNs were suggested.</t> suggested.

<!-- [rfced] Section 2.1.2:  For ease of the reader, we expanded
"LEO" as "low-Earth orbit" here, per [HU].  Please let us know
any concerns.

Original:
 [HU] highlighted that Satellite Internet provided by advanced LEO
 satellite constellations can play a pivotal role in closing the
 connectivity gap in the urban-rural digital divide via Satellite-
 dependent community networks.

Currently:
 [HU] highlighted that Satellite Internet provided by advanced low-
 Earth orbit (LEO) satellite constellations can play a pivotal role in
 closing the connectivity gap in the urban-rural digital divide via
 Satellite-dependent Community Networks. -->

</t>
          <t><xref target="RENNO"/> called attention to the coveted 6GHz 6 GHz (part of the C-band with a desirable mix of coverage and capacity) as a prime choice for International Mobile Telecommunication (IMT) for 5G technology while it is in common unlicensed use in the community networks Community Networks (and small ISPs). Spectrum allocations directly impact industries and market access with ramifications for Community Networks. Further, there was a discussion on geopolitical tensions because of it.

<!-- [rfced] Section 2.1.2:  To what does "it" refer in this
sentence?

Original (the previous sentence is included for context):
 Spectrum allocations directly impact industries and market
 access with ramifications for community networks.  Further, there was
 a discussion on the geopolitical tension because of it.</t> it. -->

</t>
        </section>
        <section anchor="discussion">
          <name>Discussion</name>
          <t>How can the technical community address the management gap gaps and improve best practices for Community Networks? Is the increasing complexity of the Internet making it more challenging to establish secure connections, and should this be taken into account in the design of the Internet? What steps need to be taken to make sure Community Networks are secure? Should the manageability consideration considerations be expanded to explicitly consider Community Networks? The Global Access to the Internet for All (GAIA) Research Group <xref target="GAIA"/> research group could be a venue for further discussion and research. Further discussion highlighted the need for readily available knowledge and tools for community networks Community Networks as well as the tussle with market forces when commercial networks compete with community networks. Community Networks. Also, there is a lack of operational inputs from community network Community Network operators in the IETF/IRTF.</t>
        </section>
      </section>
      <section anchor="session-2-digital-divide-reports-and-comments">
        <name>Session 2: Digital Divide - Reports and Comments</name>
        <t>Critical internet infrastructure affects many aspects of our society significantly, although differently, the inequitable aspects of which are typically referred to as "digital inclusion" signifying that in efforts to digitalise digitalize society, there are those left out due to what is typically called the "digital divide", a related term specific to access to the Internet. These concepts together demonstrate that even if Internet connectivity is available, for some there will remain challenges towards achieving equality. This becomes especially significant as governments view the Internet as an important tool to help for helping them reach the Sustainable Development Goals (SDG) SDGs listed in <xref target="SDG"/> target="SDGs"/> and to for globally support supporting human rights.</t> rights.

<!-- [rfced] Section 2.2:  This sentence is a bit unwieldy and
difficult to follow.  May we update as suggested?

Original:
 Critical internet infrastructure affects many aspects of our society
 significantly, although differently, the inequitable aspects of which
 are typically referred to as "digital inclusion" signifying that in
 efforts to digitalise society, there are those left out due to what
 is typically called the "digital divide", a related term specific to
 access to the Internet.

Suggested:
 Critical Internet infrastructure affects many aspects of our society
 significantly, although it impacts different parts of society
 differently.  The inequitable aspects are typically referred to as
 "digital inclusion"; these aspects signify that in efforts to
 digitalize society, there are those left out due to what is
 typically called the "digital divide", a related term specific to
 access to the Internet. -->

</t>
        <t>The second day of workshops was essential to understanding the nature of the digital divide. Presentations of reports interrogated at least three key aspects of the digital divide, though it is recognized that there may be more technical aspects of the digital divide that were not present. Those were differences between population demographics in the provision of online resources by governments, inequality in the use of multilingualized domains and email addresses, and increased costs for end-user downloads of contemporary websites' sizes.

<!-- [rfced] Section 2.2:  We found "at least three" and "Those were"
a bit confusing, as only three aspects are listed.  Also, as written,
the third sentence indicates that sizes are downloaded.  May we
update as suggested?  If not, please clarify the text.

Original:
 Presentations of reports interrogated at
 least three key aspects of the digital divide, though there is
 recognition that there may be more technical aspects of the digital
 divide that were not present.  Those were: differences between
 population demographics in the provision of online resources by
 governments, inequality in the use of multilingualized domains and
 email addresses, and increased costs for end-user downloads of
 contemporary websites' sizes.</t> sizes.

Suggested:
 Presentations of reports interrogated at
 least three key aspects of the digital divide, though it is
 recognized that there may be more technical aspects of the digital
 divide that were not addressed.  Three of those aspects were:

 *  differences between population demographics in the provision
    of online resources by governments.

 *  inequality in the use of multilingualized domains and email
    addresses.

 *  increased costs for end-user downloads of websites of
    contemporary sizes.
-->

</t>
        <section anchor="disparities-in-service-provision">
          <name>Disparities in service provision</name> Service Provisioning</name>
<!-- DNE "evidence that ..." text below from [HOLZ]; verified and corrected -->
          <t>Ralph Holz presented research that exposes the more limited DNS-mediated access to government websites by Indigenous communities in Australia as compared to less disadvantaged users in the same population in "Evidence for a digital divide? Measuring DNS dependencies in the context of the Indigenous indigenous population of Australia". Australia" <xref target="HOLZ"/> target="HOLZ"/>. DNS dependency trends were analysed analyzed between two lists of domains serving Australian government sites for Indigenous users and the general population. Researchers found, found "evidence that dependencies for the Indigenous indigenous population are indeed differently configured," indicative of a difference in service provisioning. However However, qualitative follow-up research is needed to interrogate both the potential reasons for these differences and whether the differences contribute to a "digital divide" digital divide that is tangible for Indigenous users.</t>
        </section>
        <section anchor="lack-of-consistent-acceptance-of-language-scripts">
          <name>Lack of consistent acceptance Consistent Acceptance of language scripts</name> Language Scripts</name>
          <t>On the topic of availability of Internet services and content in multiple languages languages, "Universal Acceptance of Domain Names and Email Addresses: A Key to Digital Inclusion" was presented by Sarmad Hussain of ICANN. ICANN <xref target="HUSSAIN"/> target="HUSSAIN"/>. The ICANN community has increased the options for multilingual identifiers through the expansion of the Internet's DNS for use in domains and email addresses. However, while the work of technical specification specifications and policy recommendations is complete, much work remains to deploy a multiligualized multilingualized internet. Today Today, there are around 150 internationalised internationalized domain names (IDNs) (IDNs), but the barriers to
equal rollout of these scripts at the domain level are is hindered primarily by software and applications that do not yet recognise recognize these new scripts. "Universal Acceptance" is a programme program of action for the internet community at large that can ensure that IDNs are accepted and treated consistently.</t> consistently.

<!-- [rfced] Section 2.2.2:  This sentence as written indicated that
the barriers, as opposed to equal rollout, were hindered.  We updated
to indicate that the equal rollout is hindered.  Please review, and
let us know if anything is incorrect.

Original:
 Today there are around 150 internationalised domain names (IDNs) but
 the barriers to equal rollout of these scripts at the domain level
 are hindered primarily by software and applications that do not yet
 recognise these new scripts.

Currently:
 Today, there are around 150 internationalized domain names (IDNs),
 but equal rollout of these scripts at the domain level is hindered
 primarily by software and applications that do not yet recognize
 these new scripts. -->

</t>
        </section>
        <section anchor="web-affordability-and-inclusiveness">
          <name>Web Affordability and Inclusiveness</name>
<!-- [LB]  "geographic variations in ..." is quoted from [HABIB] (verified) -->
          <t>In "A Framework for Improving Web Affordability and Inclusiveness" Inclusiveness", Rumaisa Habib presented research on the connection between website size and cost to end users. users <xref target="HABIB"/> target="HABIB"/>. This critical inquiry presents access in terms of affordability and through measurement demonstrates that the material costs to end users who pay for their connection based on the volume of data they download and upload have risen as the complexity of the web Web grows. Their research provides a framework for optimisation optimization based on end-user affordability. This framework is anchored to in reality: it <xref target="HABIB"/> proposes a fairness metric and suggests systematic adaptations to Web complexity of the Web based on "geographic variations in mobile broadband prices and income levels."</t>
        </section>
        <section anchor="discussion-1">
          <name>Discussion</name>
          <t>These three reports discuss very different aspects of current inequalities in Internet access in various parts of the world: service provision, provisioning, availability, and economic costs. Notably, the reports discuss trends that exacerbate the digital divide beyond the question of connectivity or whether users have access to the Internet, potentially bringing yielding concrete ways that the IETF community can address digital inclusion within its remit.</t>
          <t>Discussants noted that while there are some interesting aspects to the problem of the digital divide, such as measurements and frameworks, most of the work is involves getting this work to the right appropriate people at the policy layer so there level; therefore, it is an importance of communicating important to communicate this technical evidence to the right appropriate people. The IETF's role could be to build consensus on the proper solutions presented to decision-makers that put research and measurement not only in context but also in a consensus-driven solution space. Another method to better communicate this research is by telling stories of end users in more relatable and relevant terms, which terms; this is often a challenge for at the technical level and a role for more diverse stakeholders at the more local level.</t>
        </section>
      </section>
      <section anchor="session-3-censorship-reports-and-circumvention">
        <name>Session 3: Censorship - Reports and Circumvention</name>
        <t>This session focused on reports of censorship as observed during in recent years in different parts of the world, as well as world; it also focused on the use of of, and expectation on expectations for, censorship circumvention tools, mainly the use of secure VPN services.</t>
        <t>The censorship reports, with a focus on Asia, and specifically India, as well as Russia, as an example where censorship has changed significantly recently, discussed the legal frameworks and court acts actions that put legal obligations on regional network providers to block traffic. Further, measurements to validate the blocking as well as analyses of how blocking is implemented were discussed, i.e. i.e., which protocols are used but also which kind kinds of devices are used to configure the blocking rules and where are they deployed.</t> are deployed.

<!-- [rfced] Section 2.3:  We cannot determine what "specifically"
and "example" refer to in this sentence.  If the suggested text is
not correct, please clarify the use of "specifically" and "example".

Original:
 The censorship reports, with a focus on Asia, and specifically India,
 as well as Russia, as an example where censorship has changed
 significantly recently, discussed the legal frameworks and court acts
 that put legal obligations on regional network providers to block
 traffic.

Suggested (assuming that "specifically" refers to India only and
  that "example" refers to Russia only):
 The censorship reports - with a focus on Asia and (specifically)
 India, as well as Russia (which provides an example of where
 censorship has changed significantly recently) - discussed the legal
 frameworks and court actions that put legal obligations on regional
 network providers to block traffic. -->

</t>
        <section anchor="censorship-orders-measurements-and-device-analysis">
          <name>Censorship Orders, Measurements, and Device Analysis</name>
          <t><xref target="SAMSUDIN"/> reported on confirmed blocking from 10 countries (Cambodia, Hong Kong (China), India, Indonesia, Malaysia, Myanmar, Philippines, Thailand, Timor-Leste, and Vietnam) in the period from 1 July 2022 to 30 June 2023. The blocking was either confirmed by OONI Open Observatory of
Network Interference (OONI) measurements for existing blocking fingerprints, heuristics, i.e. i.e., for new blocking fingerprints as well as news reports of blocking orders, or user experiences. Most of these countries block specific content such as porn, gambling, or certain news pages. Interestingly Interestingly, the blocking in Hong Kong and Myanmar is focused on the military and governmental pages of foreign countries. Blocking is often realized by either DNS tampering or HTTP tampering. For DNS, either a decided chosen IP address, a bogon IP address (127.0.0.1), or an empty domain (nxdomain) (NXDOMAIN) is used. In the case of DNS tampering using a decided chosen IP address or HTTP tampering tampering, some countries provide a block page that exposes the blocking, blocking; however, more transparency about related to blocking is requested by civil society organizations and the iMAP project.</t> Internet Monitoring Action Project (iMAP).

<!-- [rfced] Section 2.3.1:

a) It is not clear what "either" refers to in this sentence.  Also,
we defined "OONI" as "Open Observatory of Network Interference" per
<https://ooni.org/>.

If the suggested text regarding "either" and the definition of "OONI"
are not correct, please clarify the text.

Original:
 The blocking was either confirmed by OONI
 measurements for existing blocking fingerprints, heuristics, i.e. for
 new blocking fingerprints as well as news reports of blocking orders,
 or user experiences.

Suggested:
 The blocking was confirmed by either (1) Open
 Observatory of Network Interference (OONI) measurements for existing
 blocking fingerprints or heuristics (i.e., for new blocking
 fingerprints as well as news reports of blocking orders) or (2) user
 experiences.

b) Per Internet searches, a bogon address could be any one of a
number of inappropriate addresses and is not necessarily 127.0.0.1.
However, is 127.0.0.1 the only possible bogon address when discussing
DNS?  If not, should "(127.0.0.1)" be "(e.g., 127.0.0.1)"?

Original:
 For DNS, either a decided
 IP address, a bogon IP address (127.0.0.1), or an empty domain
 (nxdomain) is used. -->

</t>
          <t><xref target="GROVER"/> further focused the discussion on online censorship in India, Pakistan, and Indonesia. In India, where providers are responsible for implementing the blocking but no method is mandated, the six major ISPs (covering 98.82% of all subscribers) were tested on 4379 blocked websites (based on court orders, user reports, and publicly available or leaked government orders) on DNS poisoning/injection or HTTP/SNI-based censorship. Used The censorship techniques used and websites blocked were different across ISPs. Multiple ISPs used two different techniques (depending on the website), and all but one provided censorship notices. Providers blocked between 1892 to and 3721 (of 4379) pages with only 1115 (27.64%) of pages (27.64%) blocked by all ISPs. ISPs <xref target="Singh2020"/> target="Singh2020"/>. In contrast, in Pakistan, the government can also order the IPSs ISPs to perform blocking blocking, and blocking has even been observed in the past on at the IXP Internet Exchange Point (IXP) level. Since 2020, there has also been a central Web Monitoring System deployed at lines of international connectivity. In Indonesia, initially, the government guided ISPs in how to perform the blocking. The regulations were updated in 2020 to allow Indonesian ISPs to block websites at their discretion. In 2022, there was a proposal by internet service providers ISPs to centralise centralize DNS. In Indonesia, a partial block list blocklist is publicly available, but without any indication of why something is blocked. blocked <xref target="Grover2023"/></t> target="Grover2023"/>.

<!-- [rfced] Section 2.3.1:  We had trouble following these
sentences, in part because the text related to the citation for
[Singh2020]* has some issues.

* We consulted <https://arxiv.org/pdf/1912.08590>, which provides the
full [Singh2020] paper, and found that "27.64%" in the current text
seems to be out of "4379", which is not correct. (The full paper
mentions "only 1115 websites out of the 4033 (just 27.64%)").

(We have an item later in our list of questions for you, where we ask
if we can update the URL for the reference listing so that readers
can access the full Singh paper at no cost.)

May we update the text as suggested?  If not, please

* clarify what "tested on" refers to

* provide the correct definitions of "SNI", "IPSs" (noting that for
  now we changed "IPSs" to "ISPs"), and "IXP"

* review the numbers provided in [Singh2020] and correct the
  numbers as needed.  For example, because 1115 is 27.64% of 4033, we
  added "4033" to the suggested text below, per
  <https://arxiv.org/pdf/1912.08590>.

Original:
 [GROVER] further focused the discussion on online censorship in
 India, Pakistan, and Indonesia.  In India, where providers are
 responsible for implementing the blocking but no method is mandated,
 the six major ISPs (covering 98.82% of all subscribers) were tested
 on 4379 blocked websites (based on court orders, user reports, and
 publicly available or leaked government orders) on DNS poisoning/
 injection or HTTP/SNI-based censorship.  Used censorship techniques
 and websites blocked were different across ISPs.  Multiple ISPs used
 two different techniques (depending on the website), and all but one
 provided censorship notices.  Providers blocked between 1892 to 3721
 (of 4379) pages with only 1115 (27.64%) of pages blocked by all ISPs.
 [Singh2020] In contrast, in Pakistan, the government can also order
 the IPSs to perform blocking and blocking has even been observed in
 the past on the IXP level.

Suggested (also assuming that "tested on" refers to DNS
  poisoning/injection or on censorship using HTTP or SNI):
 [GROVER] further focused the discussion on online censorship in
 India, Pakistan, and Indonesia.

 As discussed in [Singh2020], in India, where providers are
 responsible for implementing the blocking but no method is
 mandated, the six major ISPs (covering 98.82% of all subscribers)
 were tested on a total of 4379 blocked websites (based on court
 orders, user reports, and publicly available or leaked government
 orders) by using DNS poisoning/injection or using censorship based
 on HTTP or the Server Name Indication (SNI).  The censorship
 techniques used and websites blocked were different across ISPs.
 Multiple ISPs used two different techniques (depending on the
 website), and all but one provided censorship notices.  A list of
 4379 potentially blocked websites was tested; 4033 of those websites
 appeared in at least one ISP's blocklist.  Providers blocked between
 1892 and 3721 of the 4033 websites, with only 1115 websites (27.64%)
 blocked by all six ISPs.

 In contrast, in Pakistan, the government can also order the ISPs to
 perform blocking, and blocking has even been observed in the past at
 the Internet Exchange Point (IXP) level. -->

</t>
          <t><xref target="BASSO"/> reported that for Russia a high large increase in additions to the Roskomnadzor's block list blocklist was observed in March 2022 as well as in December 2022, foremost covering news pages but also covering human rights organizations and social media, where more than 3500 blocking orders were added to the list by an "Unknown body". Further, blocking of domains that are not in the official Roskomnadzor's list Roskomnadzor blocklist has been observed as well.</t>
          <t>An invited talk presented included a presentation of the work in <xref target="WANG"/> on locating censorship devices by using HTTP and TLS traceroutes, identifying device vendors through fingerprinting, and reverse-engineering censorship triggers by the use of fuzzing. E.g. for For example, in the case of Azerbaijan and Kazakhstan, they showed that a significant portion of measurements from remote countries are is blocked at the endpoint, indicating local policies policies, but showed that connection resets are also happening in Belarus and Russia. Further, they could identify a set of commercial network devices (with filtering techniques such as firewalls) that are used in these countries for censorship and show how fuzzing can be used to fingerprint and cluster behaviours behaviors as well as potentially circumvent the deployed methods.</t>
          <t>All speakers called for more transparency by requiring blocking messages as well as publication and auditing of blocklists. Potentially Potentially, even standardization could help.</t>
        </section>
        <section anchor="use-of-vpns-for-censorship-circumvents-and-user-expectations">
          <name>Use of VPNs for Censorship Circumvents and User Expectations</name>
          <t>Further on in the session, the possibility and prevalence of using VPNs for circumvention has been discussed were discussed, including user expectations and an analysis of security shortcomings of commercial VPN services. The analysis presented in <xref target="RAMESH"/> has shown various problems that lead to data leaks such as leakage of IPv6 traffic, non-browser traffic, or tunnel failure, not upholding user expectations, especially when used in authoritarian regimes for censorship circumvention or private communication.</t> communication.

<!-- [rfced] Section 2.3.2:  In this sentence as written, it is not
clear what "not upholding user expectations" refers to.  It appears
that in [RAMESH], "user expectations" is treated as a separate
concept.  May we update this sentence as suggested?

Original:
 The analysis presented in [RAMESH] has shown various problems that
 lead to data leaks such as leakage of IPv6 traffic, non-browser
 traffic, or tunnel failure, not upholding user expectations,
 especially when used in authoritarian regimes for censorship
 circumvention or private communication.

Suggested:
 The analysis presented in [RAMESH] has shown various problems that
 lead to data leaks, such as (1) leakage of IPv6 traffic,
 (2) non-browser traffic, or (3) tunnel failure, in addition to
 failing to uphold user expectations, especially when used in
 authoritarian regimes for censorship circumvention or private
 communication. -->

</t>
          <t>The question of how common the use of VPNs for circumvention is and its legal implications, as VPNs are illegal in a few countries, has been was discussed. E.g. For example, VPNs are not officially banned in India India, but VPN providers need to store log data and those, those who haven't complied, complied stopped serving India. However, more data on VPN use and blocking might be needed.</t>
        </section>
        <section anchor="discussion-2">
          <name>Discussion</name>
          <t>After all, there is a cat-and-mouse game between censors and circumvents, circumvents; however, continued work on protocol enhancements that protect user privacy is essential.</t>
        </section>
      </section>
      <section anchor="key-take-aways">
        <name>Key Take Aways</name> Takeaways</name>
        <t>Some key takeaways from the workshop are -</t> as follows:</t>
        <ul spacing="normal">
          <li>
            <t>There is a need for the technical community to address the management gaps in operating Community Networks.</t>
          </li>
          <li>
            <t>Work should be done in documenting to document best practices for operating Community Networks.</t>
          </li>
          <li>
            <t>During the development of protocols, explicit manageability considerations related to Community Networks should be considered.</t> carefully thought out.</t>
          </li>
          <li>
            <t>Build consensus on solutions that have the most significant impact in fostering digital inclusion. Further, promoting these solutions ensures that efforts to bridge the digital divide are effective and inclusive.</t>
          </li>
          <li>
            <t>Further work should be done to enhance protocols protocols, ensuring that user privacy should continue.</t> is preserved.</t>
          </li>
          <li>
            <t>Develop further protocols (or extensions to existing protocols) that enable more transparency on filtering filtering, and promote their use and deployment.</t>
          </li>
          <li>
            <t>Develop new VPN-like services and potentially support measurements to understand their deployment and use.</t>
          </li>
          <li>
            <t>Further discussion of these topics could happen in GAIA, HRPC, PEARG, the GAIA Research Group, the Human Rights Protocol Considerations (HRPC) Research Group, the Privacy Enhancements and Assessments Research Group (PEARG), and MAPRG the Measurement and Analysis for Protocols Research Group (MAPRG), based on the relevance to the research group. The management Management-related and operations-related discussion discussions can be taken to OPSAWG. the IETF Operations and Management Area Working Group (OPSAWG). The community could also explore if whether a group focused on censorship (and its circumvention) focused group could be created.</t>
          </li>
        </ul>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-informative-references">
      <name>Informative References</name>
      <reference anchor="RFC7962">
        <front>
          <title>Alternative Network Deployments: Taxonomy, Characterization, Technologies, and Architectures</title>
          <author fullname="J. Saldana" initials="J." role="editor" surname="Saldana"/>
          <author fullname="A. Arcia-Moret" initials="A." surname="Arcia-Moret"/>
          <author fullname="B. Braem" initials="B." surname="Braem"/>
          <author fullname="E. Pietrosemoli" initials="E." surname="Pietrosemoli"/>
          <author fullname="A. Sathiaseelan" initials="A." surname="Sathiaseelan"/>
          <author fullname="M. Zennaro" initials="M." surname="Zennaro"/>
          <date month="August" year="2016"/>
          <abstract>

  <section><name>IANA Considerations</name>
   <t>This document presents a taxonomy of a set of "Alternative Network Deployments" has no IANA actions.</t>
  </section>

<!-- [rfced] [Document Shepherd]  We see that emerged in the last decade with the aim of bringing Internet connectivity to people or providing this document does not
contain a local communication infrastructure Security Considerations section.  Please see Section 4.8.5
of RFC 7322 (https://www.rfc-editor.org/info/rfc7322).  Also, please
provide appropriate text for this document.  For example, should
"security shortcomings" in Section 2.3.2 be mentioned/addressed?

If you verify that security considerations do not apply to serve various complementary needs and objectives. They employ architectures and topologies different from those of mainstream networks and rely on alternative governance and business models.</t>
            <t>The document also surveys this
document, we could add something like the technologies deployed following (as done in these networks, and their differing architectural characteristics, including a set
IAB RFCs 8700 ("Fifty Years of definitions RFCs") and shared properties.</t>
            <t>The classification considers models such as Community Networks, Wireless Internet Service Providers (WISPs), networks owned by individuals but leased out to network operators who use them as a low-cost medium to reach the underserved population, networks that provide connectivity by sharing wireless resources of the users, 9419 ("Considerations on
Application - Network Collaboration Using Path Signals")):

 4.  Security Considerations

    This document has no security considerations.

Please review and rural utility cooperatives.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="7962"/>
        <seriesInfo name="DOI" value="10.17487/RFC7962"/>
      </reference> advise. -->

  </middle>
  <back>
    <references anchor="sec-informative-references">
      <name>Informative References</name>

      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7962.xml"/>

      <reference anchor="SDG" anchor="SDGs" target="https://sdgs.un.org/goals">
        <front>
          <title>Sustainable Development
          <title>The 17 Goals</title>
          <author>
            <organization/>
            <organization>United Nations Department of Economic and Social Affairs - Sustainable Development</organization>
          </author>
          <date>n.d.</date>
        </front>
      </reference>

      <reference anchor="MARTINEZ" target="https://www.ietf.org/slides/slides-biasws-community-networks-and-the-quest-for-quality-00.pdf">
        <front>
          <title>Community Networks and the Quest for Quality</title>
          <author initials="L. M." surname="Martínez-Cervantes" fullname="Luis Miguel Martínez Cervantes">
            <organization/>
          </author>
          <author initials="R." surname="Guevara-Martínez" fullname="Rolando Guevara Martínez">
            <organization/>
          </author>
          <date year="2024" month="January"/>
        </front>
      </reference>

      <reference anchor="GUIFI" target="https://guifi.net/en">
        <front>
          <title>Guifi.net</title>
          <title>guifi.net</title>
          <author>
            <organization/>
          </author>
          <date>n.d.</date>
        </front>
      </reference>

      <reference anchor="APC" target="https://www.apc.org/">
        <front>
          <title>The Association for Progressive Communications (APC)</title>
          <author>
            <organization/>
          </author>
          <date>n.d.</date>
        </front>
      </reference>

      <reference anchor="ISOC" target="https://www.internetsociety.org/action-plan/community-networks/">
        <front>
          <title>Community
          <title>Connecting the Unconnected: Community networks help bridge the connectivity gap</title>
          <author>
            <organization/>
            <organization>Internet Society</organization>
          </author>
          <date>n.d.</date>
        </front>
      </reference>

      <reference anchor="TBB" target="https://tribalbroadbandbootcamp.org/">
        <front>
          <title>Tribal Broadband Bootcamp</title>
          <author>
            <organization/>
          </author>
          <date>n.d.</date>
        </front>
      </reference>

      <reference anchor="BENSON" target="https://www.ietf.org/slides/slides-biasws-a-c-in-cdn-access-service-to-and-from-the-internet-at-cost-for-community-networks-00.pdf">
        <front>
          <title>A 'C' in CDN - CDN: Access service to and from the Internet at cost for community networks</title>
          <author initials="T. A." surname="Benson" fullname="Theophilus A. Benson">
            <organization/>
          </author>
          <author initials="M." surname="Fayed" fullname="Marwan Fayed">
            <organization/>
          </author>
          <date year="2024" month="January"/>
        </front>
      </reference>

      <reference anchor="PANGEA" target="https://www.cloudflare.com/en-gb/pangea/">
        <front>
          <title>Project Pangea from Cloudflare</title> Pangea: Helping underserved communities expand access to the Internet for free</title>
          <author>
            <organization/>
            <organization>Cloudflare</organization>
          </author>
          <date>n.d.</date>
        </front>
      </reference>

      <reference anchor="HU" target="https://www.ietf.org/slides/slides-biasws-closing-the-performance-and-management-gaps-with-satellite-internet-challenges-approaches-and-future-directions-01.pdf">
        <front>
          <title>Closing the Performance and Management Gaps with Satellite Internet - Internet: Challenges, Approaches, and Future Directions</title>
          <author initials="P." surname="Hu" fullname="Peng Hu">
            <organization/>
          </author>
          <date year="2024" month="January"/>
        </front>
      </reference>

      <reference anchor="RENNO" target="https://www.ietf.org/slides/slides-biasws-position-paper-by-raquel-renno-01.pdf">
        <front>
          <title>Maximising Connectivity - Connectivity: The Spectrum's Vital Role in Technology Access</title>
          <author initials="R." surname="Rennó" fullname="Raquel Rennó">
            <organization/>
          </author>
          <date year="2024" month="January"/>
        </front>
      </reference>

      <reference anchor="GAIA" target="https://www.irtf.org/gaia.html">
        <front>
          <title>Global Access to the Internet for All Research Group</title> Group (GAIA)</title>
          <author>
            <organization/>
          </author>
          <date>n.d.</date>
        </front>
      </reference>

      <reference anchor="SAMSUDIN" target="https://www.ietf.org/slides/slides-biasws-position-paper-by-raquel-renno-01.pdf"> target="https://www.ietf.org/slides/slides-biasws-imap-internet-monitoring-action-project-internet-censorship-report-02.pdf">
        <front>
          <title>iMAP (Internet Monitoring Action Project) 2023 Internet Censorship Report</title>
          <author initials="S." surname="Samsudin" fullname="Siti Nurliza Samsudin">
            <organization/>
          </author>
          <date year="2024" month="January"/>
        </front>
      </reference>

      <reference anchor="GROVER" target="https://datatracker.ietf.org/meeting/interim-2024-biasws-03/materials/slides-interim-2024-biasws-03-sessa-online-censorship-in-india-pakistan-and-indonesia-00">
        <front>
          <title>Online censorship in India, Pakistan and Indonesia</title>
          <author initials="G." surname="Grover" fullname="Gurshabad Grover">
            <organization/>
          </author>
          <date year="2024" month="January"/>
        </front>
      </reference>

      <reference anchor="Grover2023" target="https://archive.org/details/eaten-by-the-internet/">
        <front>
          <title>The infrastructure of censorship in Asia</title>
          <author initials="G." surname="Grover" fullname="Gurshabad Grover">
            <organization/>
          </author>
          <author initials="C." surname="Cath" fullname="Corinne Cath (ed.)">
            <organization/>
          </author>
          <date year="2023" month="October"/>
        </front>
        <refcontent>in &quot;Eaten by the Internet&quot;, ed. Corinne Cath, pp. 75-81</refcontent>
        <refcontent>Internet Archive, Meatspace Press</refcontent>
      </reference>

      <reference anchor="Singh2020" target="https://dl.acm.org/doi/abs/10.1145/3394231.3397891">
        <front>
          <title>How India Censors the Web</title>
          <author initials="K." surname="Singh" fullname="Kushagra Singh">
            <organization/>
          </author>
          <author initials="G." surname="Grover" fullname="Gurshabad Grover">
            <organization/>
          </author>
          <author initials="V." surname="Bansal" fullname="Varun Bansal">
            <organization/>
          </author>
          <date year="2020" month="July"/>
        </front>
        <refcontent>WebSci '20: Proceedings of the 12th ACM Conference on Web Science, pp. 21-28</refcontent>
        <seriesInfo name="DOI" value="10.1145/3394231.3397891"/>
      </reference>

<!-- [rfced] References:  The provided URL for [Singh2020] only
provides the Abstract.  May we update this listing as follows, so
that readers may access the full article at no cost?

Original:
 [Singh2020]
            Singh, K., Grover, G., and V. Bansal, "How India Censors
            the Web", July 2020,
            <https://dl.acm.org/doi/abs/10.1145/3394231.3397891>.

Suggested:
 [Singh2020]
            Singh, K., Grover, G., and V. Bansal, "How India Censors
            the Web", WebSci '20: Proceedings of the 12th ACM
            Conference on Web Science, DOI 10.1145/3394231.3397891,
            July 2020,
            <https://arxiv.org/pdf/1912.08590>. -->

      <reference anchor="BASSO" target="https://datatracker.ietf.org/meeting/interim-2024-biasws-03/materials/slides-interim-2024-biasws-03-sessa-online-censorship-in-india-pakistan-and-indonesia-00"> target="https://datatracker.ietf.org/meeting/interim-2024-biasws-03/materials/slides-interim-2024-biasws-03-sessa-slide-how-internet-censorship-changed-in-russia-during-the-1st-year-of-military-conflict-in-ukraine-00.pdf">
        <front>
          <title>How Internet censorship changed in Russia during the 1st year of military conflict in Ukraine</title>
          <author initials="S." surname="Basso" fullname="Simone Basso">
            <organization/>
          </author>
          <date year="2024" month="January"/>
        </front>
      </reference>

      <reference anchor="WANG" target="https://datatracker.ietf.org/meeting/interim-2024-biasws-03/materials/slides-interim-2024-biasws-03-sessa-online-censorship-in-india-pakistan-and-indonesia-00"> target="https://datatracker.ietf.org/meeting/interim-2024-biasws-03/materials/slides-interim-2024-biasws-03-sessa-network-measurement-methods-for-locating-and-examining-censorship-devices-00.pdf">
        <front>
          <title>Network Measurement Methods for Locating and Examining Censorship Devices</title>
          <author initials="R. S." surname="Raman" fullname="Ram Sundara Raman">
            <organization/>
          </author>
          <author initials="M." surname="Wang" fullname="Mona Wang">
            <organization/>
          </author>
          <author initials="J." surname="Dalek" fullname="Jakub Dalek">
            <organization/>
          </author>
          <author initials="J." surname="Mayer" fullname="Jonathan Mayer">
            <organization/>
          </author>
          <author initials="R." surname="Ensafi" fullname="Roya Ensafi">
            <organization/>
          </author>
          <date year="2023" month="November"/>
        </front>
      </reference>

      <reference anchor="RAMESH" target="https://datatracker.ietf.org/meeting/interim-2024-biasws-03/materials/slides-interim-2024-biasws-03-sessa-investigating-the-vpn-ecosystem-through-the-lens-of-security-privacy-and-usability-00">
        <front>
          <title>Investigating the VPN Ecosystem through the lens of Security, Privacy, and Usability</title>
          <author initials="R." surname="Ramesh" fullname="Reethika Ramesh">
            <organization/>
          </author>
          <date year="2024" month="January"/>
        </front>
      </reference>

      <reference anchor="HOLZ" target="https://www.ietf.org/slides/slides-biasws-evidence-for-a-digital-divide-measuring-dns-dependencies-in-the-context-of-the-indigenous-population-of-australia-00.pdf">
        <front>
          <title>Evidence for a digital divide? Measuring DNS dependencies in the context of the indigenous population of Australia</title>
          <author initials="R." surname="Holz" fullname="Ralph Holz">
            <organization/>
          </author>
          <author initials="N." surname="Nazemi" fullname="Niousha Nazemi">
            <organization/>
          </author>
          <author initials="O." surname="Tavallaie" fullname="Omid Tavallaie">
            <organization/>
          </author>
          <author initials="A. Y." surname="Zomaya" fullname="Albert Y. Zomaya">
            <organization/>
          </author>
          <date year="2023"/>
        </front>
      </reference>

      <reference anchor="HUSSAIN" target="https://www.ietf.org/slides/slides-biasws-universal-acceptance-of-domain-names-and-email-addresses-a-key-to-digital-inclusion-01.pdf">
        <front>
          <title>Universal Acceptance of Domain Names and Email Addresses - Addresses: A Key to Digital Inclusion</title>
          <author initials="S." surname="Hussain" fullname="Sarmad Husain"> Hussain">
            <organization/>
          </author>
          <date year="2023"/>
        </front>
      </reference>

<!-- Used <https://dl.acm.org/doi/10.1145/3603269.3604872> to verify
     the author list -->
      <reference anchor="HABIB" target="https://www.ietf.org/slides/slides-biasws-a-framework-for-improving-web-affordability-and-inclusiveness-00.pdf">
        <front>
          <title>A Framework for Improving Web Affordability and Inclusiveness</title>
          <author initials="R." surname="Habib" fullname="Rumaisa Habib">
            <organization/>
          </author>
          <author initials="S." surname="Tanveer" fullname="Sarah Tanveer">
            <organization/>
          </author>
          <author initials="A." surname="Inam" fullname="Aimen Inam">
            <organization/>
          </author>
          <author initials="H." surname="Ahmed" fullname="Haseeb Ahmed">
            <organization/>
          </author>
          <author initials="A." surname="Ali" fullname="Ayesha Ali">
            <organization/>
          </author>
          <author initials="Z. A." surname="Uzmi" fullname="Zartash Afzal Uzmi">
            <organization/>
          </author>
          <author initials="Z. A." surname="Qazi" fullname="Zafar Ayyub Qazi">
            <organization/>
          </author>
          <author initials="I. A." surname="Qazi" fullname="Ihsan Ayyub Qazi">
            <organization/>
          </author>
          <date year="2023" month="September"/>
        </front>
        <refcontent>ACM SIGCOMM '23, pp. 592-607</refcontent>
        <seriesInfo name="DOI" value="10.1145/3603269.3604872"/>
      </reference>
    </references>
    <?line 336?>

<section anchor="position-papers">
      <name>Position Papers</name>
      <t>19
      <t>Nineteen position papers were submitted to the workshop call for papers. Eleven were selected for publication. Papers that were not published either (1)&nbsp;only provided a very prelimited analysis of an idea that was felt to be incomprehensive for discussion at the workshop or (2)&nbsp;addressed problems that were considered "beyond scope" as dedicated for the workshop discussion, e.g., discussing cybersecurity threats as a barrier to participation or implication of technology in a regulation that imposes blocking. Both of these topics pose a potentially severe risk for the open Internet; however, these risks might pose a high risk for all Internet users but do not necessarily imply an unbalance.

<!-- [rfced] Appendix A:  We see a list of twelve published papers
under "This is the list of all published papers", but this sentence
indicates eleven.  Should we update to "twelve"?  If not, should the
M-Lab paper be placed in a separate category even though it's
included in the list of accepted papers?

Looking at <https://datatracker.ietf.org/group/biasws/materials/>,
we see 26 (twenty-six) papers listed with "interim-2024-biasws-<##>",
so "19 position papers" in the current text is also unclear to us.

Please review, and let us know if any updates are needed.

Original:
 19 position papers were submitted to the workshop call for papers. 11
 were selected for publication. -->

<!-- [rfced] Appendix A:  We had trouble following this sentence
and updated it as noted below.  Please review, and let us know if
anything is incorrect.

Also, please note that we changed "threads" to "threats" here.  Please
let us know if this is incorrect.

In addition, please confirm that "prelimited"* is the correct word
here and that "scope as dedicated for the workshop discussion" will
be clear to readers; we do not understand the meaning of "dedicated
for ..."

* Please see <https://www.merriam-webster.com/dictionary/prelimited>.

Original:
 Papers that were not published either
 (1) only provided a very prelimited analysis of an idea that was felt
 to be incomprehensive for discussion at the workshop, or (2)
 addressed problems that were beyond the scope as dedicated for the
 workshop discussion e.g. discussing cyber security threads as a
 barrier for participation or implication of technology in regulation
 that imposes blocking.

Currently:
 Papers that were not
 published either (1) only provided a very prelimited analysis of an
 idea that was felt to be incomprehensive for discussion at the
 workshop or (2) addressed problems that were considered "beyond
 scope" as dedicated for the workshop discussion, e.g., discussing
 cybersecurity threats as a barrier to participation or implication
 of technology in a regulation that imposes blocking.

Possibly:
 Papers that were not
 published either (1) only provided a very prelimited analysis of an
 idea that was felt to be incomprehensive for discussion at the
 workshop or (2) addressed problems that were considered beyond the
 scope of the workshop discussions, e.g., discussing cybersecurity
 threats as a barrier to participation or implication of technology
 in a regulation that imposes blocking. -->

<!-- [rfced] Appendix A:  "risks might provide a high risk" reads
oddly.  May we update as suggested (assuming that "these risks"
means "these scenarios")?

Original:
 Both of these topics pose a potentially
 severe risk on the open Internet, however, these risks might provide
 a high risk for all Internet users but do not necessarily imply an unbalance.</t>
 unbalance.

Suggested:
 Both of these
 scenarios pose a potentially severe risk for the open Internet;
 however, they might pose a high risk for all Internet users but do
 not necessarily imply an unbalance. -->

</t>
      <t>All accepted papers are available at: https://datatracker.ietf.org/group/biasws/materials/</t> at <eref target="https://datatracker.ietf.org/group/biasws/materials/" brackets="angle"/>.</t>
      <t>This is the list of all published papers:</t>
      <t>Community Networks:</t>
      <ul spacing="normal">
        <li>
          <t>L. M. Martínez-Cervantes, R. Guevara-Martínez:
          <t>Martínez-Cervantes, L.&nbsp;M. and R.&nbsp;Guevara-Martínez: Community Networks and the Quest for
Quality <xref target="MARTINEZ"/></t>
        </li>
        <li>
          <t>T. Benson, M. Fayed:
          <t>Benson, T.&nbsp;A. and M.&nbsp;Fayed: A ‘C’ 'C' in CDN: Access service to and from the Internet at cost for community networks at-cost <xref target="BENSON"/></t>
        </li>
        <li>
          <t>P. Hu:
          <t>Hu, P.: Closing the Performance and Management Gaps with Satellite Internet:
Challenges, Approaches, and Future Directions <xref target="HU"/></t>
        </li>
        <li>
          <t>R. Rennó:
          <t>Rennó, R.: Maximising Connectivity: The Spectrum's Vital Role in Technology Access <xref
target="RENNO"/></t>
        </li>
      </ul>
      <t>Digital Divide:</t>
      <ul spacing="normal">
        <li>
          <t>R. Holz, N.
          <t>Holz, R., Nazemi, O. N., Tavallaie, A.Y. Zomaya: O., and A.&nbsp;Y.&nbsp;Zomaya: Evidence for a digital divide?
Measuring DNS dependencies in the context of the indigenous population of Australia <xref
target="HOLZ"/></t>
        </li>
        <li>
          <t>S. Hussain:
          <t>Hussain, S.: Universal Acceptance of Domain Names and Email Addresses: A Key to
Digital Inclusion <xref target="HUSSAIN"/></t>
        </li>
        <li>
          <t>R. Habib, S.
          <t>Habib, R., Tanveer, A. S., Inam, H. A., Ahmed, A. H., Ali, Z.A. A., Uzmi, Z.A. Z.&nbsp;A., Qazi, I.A. Qazi: Z.&nbsp;A., and I.&nbsp;A.&nbsp;Qazi: A Framework for Improving Web Affordability and Inclusiveness <xref target="HABIB"/></t>
        </li>
        <li>
          <t>J. Ott, G.
          <t>Ott, J., Bartolomeo, M.M. G., Bese, R. M.M., Bose, M. R., Bosk, D. M., Guzman, L. D., Kärkkäinen, M. L., Kosek, N. Mohan: M., and N.&nbsp;Mohan: The Internet: Only for the Fast (and Furious)?</t>
        </li>
        <li>
          <t>L.Y. Ohlsen:
          <t>Ohlsen, L.Y.: BIAS workshop - M-Lab Position Paper submission</t> submission

<!-- [rfced] Appendix A: Would you like to add references for these
two papers? We note other papers in this section have corresponding
references.

Current:
   *  Ott, J., Bartolomeo, G., Bese, M.M., Bose, R., Bosk, M., Guzman,
      D., Kärkkäinen, L., Kosek, M., and N. Mohan: The Internet: Only
      for the Fast (and Furious)?

   *  Ohlsen, L.Y.: BIAS workshop - M-Lab Position Paper submission

Perhaps:
   *  Ott, J., Bartolomeo, G., Bese, M.M., Bose, R., Bosk, M., Guzman,
      D., Kärkkäinen, L., Kosek, M., and N. Mohan: The Internet: Only
      for the Fast (and Furious)? [OTT]

   *  Ohlsen, L.Y.: BIAS workshop - M-Lab Position Paper submission
      [OHLSEN]

where in the References section:

[OTT] Ott, J., Bartolomeo, G., Bese, M.M., Bose, R., Bosk, M., Guzman,
      D., Kärkkäinen, L., Kosek, M., and N. Mohan, "The Internet: Only
      for the Fast (and Furious)?", January 2024,
      <https://www.ietf.org/slides/slides-biasws-the-internet-only-for-the-fast-00.pdf>.

[OHLSEN] Ohlsen, L.Y., "BIAS workshop - M-Lab Position Paper submission",
         [Date], <https://www.ietf.org/slides/slides-biasws-m-lab-position-paper-00.pdf>.
NOTE: The PDF at that URL is errored and needs to be replaced. This has been reported
to support@ietf.org.
-->

</t>
        </li>
      </ul>
      <t>Censorship:</t>
      <ul spacing="normal">
        <li>
          <t>S. Nurliza Samsudin:
          <t>Samsudin, S.: iMAP (Internet Monitoring Action Project) 2023 Internet
Censorship Report <xref target="SAMSUDIN"/></t>
        </li>
        <li>
          <t>G. Grover:
          <t>Grover, G.: The infrastructure of censorship in Asia <xref target="Grover2023"/></t>
        </li>
        <li>
          <t>S. Basso:
          <t>Basso, S.: How Internet censorship changed in Russia during the 1st year of military
conflict in Ukraine <xref target="BASSO"/></t>
        </li>
      </ul>
      <t>In addition to the submitted paper papers, two invited talks were presented included, based on published papers:</t>
      <ul spacing="normal">
        <li>
          <t>R. Sundara Raman, M.
          <li>Raman, R.&nbsp;S., Wang, J. M., Dalek, J. J., Mayer, R. Ensafi: J., and R.&nbsp;Ensafi: Network Measurement Methods for Locating and Examining Censorship Devices <xref target="WANG"/></t>
        </li>
        <li>
          <t>R. target="WANG"/></li>
          <li>Ramesh, R., Vyas, A., and R.&nbsp;Ensafi: "All of them claim to be the best": Multi-perspective study of VPN users and VPN providers</li>

<!-- [rfced] Appendix A:  We found this URL for this additional
Ramesh paper:  <https://www.usenix.org/conference/usenixsecurity23/
presentation/ramesh-vpn>.
We suggest that it be cited here and included in the References
section.

Would it be acceptable to change [RAMESH] to [RAMESH-1] and use
[RAMESH-2] for this paper?

Original:
 *  R.  Ramesh, A.  Vyas, R.  Ensafi:    “All "All of them claim to be the best”:
    best": A multi-perspective study of VPN users and VPN providers</t>
        </li> providers

Suggested:
 *  Ramesh, R., Vyas, A., and R. Ensafi: "All of them claim to be the
    best: Multi-perspective study of VPN users and VPN providers"
    [RAMESH-2]

In the References section:
 [RAMESH-2]   Ramesh, R., Vyas, A., and R. Ensafi, "'All of them
              claim to be the best': Multi-perspective study of VPN
              users and VPN providers", 32nd USENIX Security
              Symposium (USENIX Security '23), 2023,
              <https://www.usenix.org/conference/usenixsecurity23/
              presentation/ramesh-vpn>. -->

      </ul>
    </section>
    <section anchor="workshop-participants">
      <name>Workshop Participants</name>
      <t>The workshop participants were Arnaud Taddei, Carlos Pignataro, Carsten Bormann, Cindy Morgan, Colin Perkins, Cory Myers, Dan Sexton, David Guzman, David Millman, David Schinazi, Dhruv Dhody, Gurshabad Grover, Hanna Kreitem, Jane Coffin, Jiankang Yao, Jörg Ott, Juan Peirano, Lai <contact fullname="Arnaud Taddei"/>,
      <contact fullname="Carlos Pignataro"/>, <contact fullname="Carsten
      Bormann"/>, <contact fullname="Cindy Morgan"/>, <contact fullname="Colin
      Perkins"/>, <contact fullname="Cory Myers"/>, <contact fullname="Dan
      Sexton"/>, <contact fullname="David Guzman"/>, <contact fullname="David
      Millman"/>, <contact fullname="David Schinazi"/>, <contact
      fullname="Dhruv Dhody"/>, <contact fullname="Gurshabad Grover"/>,
      <contact fullname="Hanna Kreitem"/>, <contact fullname="Jane Coffin"/>,
      <contact fullname="Jiankang Yao"/>, <contact fullname="Jörg Ott"/>,
      <contact fullname="Juan Peirano"/>, <contact fullname="Lai Yi Ohlsen, Luis Martinez, Mallory Knodel, Marwan Fayed, Matthew Bocci, Michael Welzl, Michuki Mwangi, Mirja Kühlewind, Mona Wang, Peng Hu, Ralph Holz, Raquel Renno, Reethika Ramesh, Rumaisa Habib, Sarmad Hussain, Simone Basso, Siti Ohlsen"/>,
      <contact fullname="Luis Martinez"/>, <contact fullname="Mallory
      Knodel"/>, <contact fullname="Marwan Fayed"/>, <contact
      fullname="Matthew Bocci"/>, <contact fullname="Michael Welzl"/>,
      <contact fullname="Michuki Mwangi"/>, <contact fullname="Mirja
      Kühlewind"/>, <contact fullname="Mona Wang"/>, <contact fullname="Peng
      Hu"/>, <contact fullname="Ralph Holz"/>, <contact fullname="Raquel
      Rennó"/>, <contact fullname="Reethika Ramesh"/>, <contact
      fullname="Rumaisa Habib"/>, <contact fullname="Sarmad Hussain"/>,
      <contact fullname="Simone Basso"/>, <contact fullname="Siti Nurliza Samsudin, Suresh Krishnan, Theophilus Benson, Tirumaleswar Reddy, Tommy Pauly, Vesna Manojlovic, and Wes Hardaker.</t>
      Samsudin"/>, <contact fullname="Suresh Krishnan"/>, <contact
      fullname="Theophilus Benson"/>, <contact fullname="Tirumaleswar
      Reddy.K"/>, <contact fullname="Tommy Pauly"/>, <contact fullname="Vesna
      Manojlovic"/>, and <contact fullname="Wes Hardaker"/>.</t>
    </section>
    <section anchor="workshop-program-committee">
      <name>Workshop Program Committee</name>
      <t>The workshop program committee members were Christopher Wood <contact fullname="Christopher Wood"/> (IAB, Cloudflare), Dhruv Dhody <contact fullname="Dhruv Dhody"/> (IAB, Huawei), Mallory Knodel <contact fullname="Mallory Knodel"/> (IAB, Center for Democracy and Technology), Mirja Kühlewind <contact fullname="Mirja Kühlewind"/> (IAB, Ericsson), and Tommy Pauly <contact fullname="Tommy Pauly"/> (IAB, Apple).</t>
    </section>
    <section numbered="false" anchor="iab-members-at-the-time-of-approval">
      <name>IAB Members at the Time of Approval</name>
      <t>Internet Architecture Board members at the time this document was approved for publication were: TODO</t> TODO

<!-- [rfced] IAB Members at the Time of Approval:  Please provide the
list of IAB members at the time this document was approved for
publication.

Original:
 Internet Architecture Board members at the time this document was
 approved for publication were: TODO -->

</t>
    </section>
    <section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>Thanks to Arnaud Taddei <contact fullname="Arnaud Taddei"/> for helpful suggestions to improve this report.</t>
    </section>
  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA9V9W3NbR3buO35FF6dSQ6YASJTs8ZhTpzwgKUu0xMuQlJ2Z
twZ2A2hzXzD7QghSqco/I6lK3vKap1TlKW/+J/4lWd9a3b17b4CS7PHknDOZ
jEDs3bfV6/KtSzdGo9GgtnVqjtTe2eRYHeuytKasVF2os7w2ZW5qNZnNTFWp
Yq5uTHlv6Q+1f3w2uTlQ3xXlXbUsVurarIqy3hvo6bQ099QZnm8/nunaLIpy
c6RsPi8Gg6SY5TqjwZNSz+uR1dPR1OpqtHYNRyU3HD1+MqiaaWaryhZ5vVlR
C5rtIG+yqSmPBgl1ezSYFXll8qqpjlRdNmZA03g6uDMb6iw5GqhRf0H46oQa
FGW1tCv8NSuyrMltvVH0Fs8B3yZ2YWud0r/3NqFuTd7QaErRt8tmSmu1ea3L
2XJa6DJ59OGV7FG7lGZb1dRuWder6ujRo7j9WHod2+IjPX3k8XhZZ+neYKCb
elmUWD6NrNS8SVOh+N65Lb/X6uWP/71MzdrmyR6/YDJtU6zJ1PM/3jXGPRwT
QfZ2dHK6LJt7dboskk23fZL8McGzBI/GRNhdrc91mhI3qJd5kZi020F2x1/+
cZbU46Jc0FLyosx0be+J+AOwT/hLqeuvT7748ndP8PHm9PkRd0Q0XRgis6dy
lSyqcZOjs0eLQqeVvCXMf9NUtba5nqZGnZp7kxarzOS1eu5ePJ9c355dPPvL
7q7X6/UYBOO+q5S4pHL/8N6sq1HgrJHnrJHOk1G9NKO/NsQNI1oOfdIpXnn8
eLxK5vH0TgJjXrjmiporaq7+hOaKmtMnbs7twrbzf0buX0ViR9KhXo3VOf1X
l/WP/5Gbt6MTEmtNwlGF92SDXjW2Uud20Zi0fVv13+73fj1Wzxtzr0s9Co16
HV8XKc2/8O+p7nsszuobnTeamOPJ4yef0dfPX599fbab/IvGzi049JHJY6o9
99/Tl5Ork4f3Tq9mvHVx41ui7aSqipklLitypvBVWSxK0hzEdX5LZvyUFCIN
cEDtz24uPzCQdRoI3Zp6w4PqGXoYrYgij7bZ5NFuNvCP1dKkKzUtbbIwzA6k
BHNDPd7jrYUmtaZuj493z6gu7VSn07LQyZS2Y1oU9Uxnq21S8Hvq2L+ojt2b
9NLxs4uby4tfKhZ6NBvZfDRL8pFmnTyqxMKM6oIFZF4WGUuJp9xI1yRMTmB2
SNW27EzUTz/888lPP/wLsac6Ob0gje4MmhsLtg6rwlhMw2AndK0wFu/9Ltvw
UUG7HavJWB3DyOQ9ESD+KlZLmzbV1iv9XkhWv9Ybk/R6IKFZ6zx6tFNuriYX
z59NHt6gWVo0yTzVpYGWJgkaLaaPVjpfGN1hAuL974mx1BU/EmKdhLb05ovX
v1g5pkVl8wXv88qUrNlz4gEwAH3SCwNdPCJuJjNH5nFU0UJT0nURW8yWZEsM
TY2YarUiTp0tjejYeVM3pRkltjQsacQjh1v6VWbAu3/VzoDZ4jzMQD2nGSjM
QN34GbTMQmAizGGoJmESQ+7la56FOg2z+ATuuRqrF01v06+of//tzv2+fnZx
cflLd2JFZBBtpGkjRtPNqNRkn1ICFXle7CDcuX5jCZaBdiex5hmx/rxZ0Rdl
k/22Ut8yhCK9byCGt2a2zIu0WGwCFvsoNcisXNMsfvzPvi3hGcbPdtuPydkH
pMCWjiwLbTVjp44hSQsoQKc2SF10tAS0wyTFDCoDHKeel0UD3XgzOb95fXr2
i7Xjz94Nez65UvthYucF6auixOZMmOm8EB+AKE/bFbQo2CH1T9iOmzH9v86q
JrF91XZDs1YXTZnat7r7zu6dub789tn1biJRA12XenZnypZYmTE1LeoRC7/N
RujH0+zx00cEC+lrwm2enLvfI1NTVXpU5KnNzWgWSACDRIjXaiL7nSVYmLMa
oa+K3FT09ePHMc0vub1q24O/z9B+SLpSOmANcOY7+ATiPh+Die5N2aPs84aG
0FOdxI93E5WfY5t3ExaMSjCG6ZkYwr5ELkMd5WCz2OBugSKC3qWuSKxnrNHI
K+yuffJ3WOJ285OxOtH1stf4BNxOu4FHat8k44OIQpezuiB3kXkf0kkstKTP
jx/gvHSsZ5nQp7CP9LR6dPh4fHj42eePnj798rMnTw/H9O8Xv//yMCbQi2It
m+9lilXFd2b6CRR5OZY59db0siF6LAgkxw9/ZWp+SwhE55VOe82/1WWTx48c
rzUpMxoE4Xhyc/OAvfl/X3hlu5wWjNiY0ASZ8QTsfN0Q3tcqaUoPEA4JEW5I
04P1M0sgAGJHuHueWsJH1OT1XUm+pPk0JXqsycnYUqAZTTd6tFPEvyNk9/8r
4Z0bq86NrkiLMLo6N0SqpGJ7+qqAY0UEh+Z89kZnNmeM0W4ReemIRH0acCA6
X2uCdFvQISPPP0/ggsbPdwDw74gh+vi7yHX8fb/VN2N1qlNz12v2jb5rpp0n
OxqeE6jvy/I3NF5NjNl5uGOxz0ha53bL497o+Ilw1AXphCzSideT82c3L/5v
MZXN701V2wXvPBuh+1U+MuSCbarawA8kYLVY8hPC2dWomFPLGUkmeYCr0t7r
2Ya5rqn01LpQSsx1Z/EALMvfXl2oZ34A5QbgJxhAQp4yAFlzGUHw/Gs/xCci
V9qEqq/Zr4l4S3un46c7Jf3F5atfHHkyCFrCm4LDrEcumDmSYOYoY/kDuROi
Z2JWJsfblreKCU2KrTZvatBaYAH1YPKiATxdNSmHP/BQN4QJdMqS3selz9wc
WLR1L6D6lVMC2JLTixsVTwLa1EU1MAnsR80QxE9CtZPAw4mfxMd3hTblRZFu
BaZ0ulrGD3qtLsbqQr81WV+8LmwBM9192Gt7OVa3+p5cRG1Nr/llZpOth73m
k7H681j9pcj0RveaT1KS4br3WDjJCfaL1zc3k1/uiTQ5YcWSQACHaVY1u+e0
6QkNR3yCWYizzdHbkU4ShMnw3ejObBDM8Xxn81naIIq/w3157UdhT0tGwa6e
8ihEWxpFDAJGURM/CiI66qXZwDM7dbx15sf5OCfcwM0m/bPtx+gyI+RED3XH
f/E0nRyfPRBZ+5TIF6HozMAIsmTabEUADYK4NtORntN3iVdiYkh5PfcmR5Rs
V5Tra98fS9mZ7w/gU03i/pw3EvX3adJCzad9cWloJyrdebZN3VtNenfLnBF1
9bL3bJvlz+jlPrdbggvxg16rF2M1WWZb4bIXujIgRfSoPxwJUl+wJxsDufYP
hAFuiDkjuzkYjUaKHARYx3owgJO0FxJpvBkfzaTtKZ+/UWtdQd9hZxI13XRj
DRO4bbUR1+sYCSPy9yfHBxKP82bj8PPR4RdDth6KetMwbMaMEr1RAtyUs9vk
wxPIpHEK0bOcZKtr+sLHHhTHHqohPw5znMGXMIn0q3RJChyLYuvOuS28XSLY
A/dwO2rNLvKDNPmDkhyWCDuaEzys/ByLKeK2NHjXjPyBX85aPFn1XFPuK4L4
tpw1GVEZqyQeXdrKDUtUyDJd2rem6qz6txUNVc0aTkJydzyRSkhcmjmt3Rs5
vwA3Z4IQJSDu9OH06ngwuChqBPF1Tf9Ds0kKmiBaWemf5+Y6JOGeGZPQFlbe
KPpp0p6CA++tWQsB/Va2PYpnU0dLXtPclXmzYoWaxN5O2HNixZUuazuzK527
vUkKlRc17StWQCQjt5DokCJOTFxJBNsxi7HIC1m8JDWDwW9AiLJIGo5QifS0
AfiKx/RLnBEQszPa8l4MgtQlDVkpQvCk3aoV/0FtiqZULtWiKrvI7Zxa53UK
DJeStgPWs0TfbKXRIrFz3sOaB+UefOvwKN2MVWeK2JwcXRAZqW/a2SLF9pJM
zARJfjC3qPZvTp8fqHfv6J/37yWrV6gFBxyJmlWz4v1ZkqLNVWkXy7oaI9Ra
mb82RpbCaJVwOfujRsNRmjep0iFa6QWlTzXHwayGsIy0KojREPxGV8TrBg1y
0jgVSxTt3A3JNE1rqdm0tPskY1EnYAcgs8WStHAtSoUUKZkp+h/azrVwFKbl
UlX8Tg50R+YpZZVjilUq8yMl08wks9UV9yFvnJt0TH1F/hxJWM08Rx/IFwWx
8WdOWgtUMJJojfCl71svaHpLsi6yIKyRoafrwFOLWaBkxaeywpGSP8QCvnMv
mCCe6GimV6s0ZBFZ+BFycWLuCUxOHWkqZedRtCIOt4MQ94SJwGNDFZLjkZpC
nsvNghAi0ZUhVciaJPxiI6QZQwqpSxSEBPFfQstZ2M7BP8rupSznQVVPi6ar
4D5Mw/4Sh8qMyR5NvTma2xSuYr4Qf2uaFrM7DgiAh9IU/yYN5+7IEzCljjZ2
w/rCpxhYYcz0StCPRUImtXe05xxAUKSsSZnWBa2Hvifrp72W4mVyfrVjgltz
tgDnq6khg1lGbIdZ0gSWxbqXJ2hySf2A63boGqdtU9mL9dJCf7SJEpoo/2VR
MEACY1hTTI1qKvm4wI62nOaI7hcybSz3vD3RNZjupx/+dWrcXoGvTPLTD/+2
leoASxNQ+g4tbNV9BtGjza2+Co8xxzDLVhrSTTuIexmChM4Q5smajJjqr431
Zlzas/oMXEWWvIRS7VJvJ58xDsY8gFk6U/6KrM9v1IQZl41hYHZnFV1/Thx+
sT3++eZY/29a46+bkrouob+GHTK6hQRiwP1inImJ0QtOaS3gRWBCYXJbM6Np
AUzpO3oxWk0Lp0gokVfFTjCIpBFq59WXitxim2jBaUTMptoxzZZ2c1JMxVqY
c06fhDRWkxA1pr85JBY10c2I4dIkydmKWZkUhhhJFcrKxgAroaTtZlasRPGf
hlUIeukgeXIAie/fQsHOygKSyZCZoLjLJJMCHi2QMIzBZZUWNa0SQWCyYXhb
uEjWxuQrVnbmkDeDN0RYagI4TpU7plyQU8gaC6jeRLNhWK/aojooJZZ2zI5t
A/XAG04bwFDGUc7NvzfXsTqVbeVX26fYqaIyzouQmTruMZBRBjGWoQ5Tg2ia
x52T+k2UFoxgaFk0CRmBKMLSe2PkxcOdRVKchrZlyDt/wOmQvZtbUo2KHaUe
o8xJWCNPyTs3OwZ9986VowHPQVWsNYcmoH8gRNz+Q57AznKvErghnY/aLQze
1HpZgIDFOvIYWysl3NAERQgboGFbcy6fI8WMbIetMla0ZWQDBFugvU8GtlqV
eYV3lqCncciFUSj7a+XMskUWf5C26qqjMkpJr7AyWRKoTQFsvVZg0wa2C8FJ
X9oGgj97Q5xk2dHa/1Px7IDf3CbY0NuuVVELi8mW4asTpzhOTYqAU2ik9k9O
Lw5I9HOsasP1Qg937DmgLQVpX+FyIoL8KeNzef+eEaZvxTjQlUcE7V+RH2KY
r3/D4h4te3sig8G7d74skTgtkNEkLRVhLyVK9kES2ljmwGsFgYQdQxKkr1gj
+rKrpGTdn5hVWmxgykQz3+XFOjUoSRPmuS/Se8nxcJCAEXwD5wekvtfl5g9o
RrbKmyCHrXMCNY0uUWxoxJ2PGZP2PcJ7jjM9NGcb7WnAsgvJBUCBYaU+HCdi
gg6pkeDQUBXKcx18J+5j2BEVJfH0Ca4XJVHDWU72RXR1J8rS4UFv3MG+U5Ro
rhAdEl/LU0xkbSs6EkFcGB+SWRYCKYXyQTz/xK1jd4kahgroNml9zzEpKS6o
dCoqJ6LoDE7X1qazFXPc4WxLBSVm3pBnhWkRd5GfPXOmYofq2n/3bnJ18v79
kAZFeSQ+oZt3726Pj9+/PxCrUC112aqvGEGMRTXbnJcs7pzfeOflhd3pyGPH
R0cx5ENUErcLji3xSF7kI2oHvYXUVfvW/sXtRSX6xvYc33fvXrx+/95J7k1N
uH5Bq5CU5U7BlbJJon7PrNBmLe3UsmLm0kNvdcGZtnah264yfoju7F2WBHoS
98ZurVex2qOFEc97E+GGG7GjtGvMCkaZxJOdXk5KurpMcJxWWVM3bNSn5JvN
LRuDNUDMjgpW4qI0FVGdkv1Y6ibdqsikCf70w78g22NFiQiGmHnPOzFpTwRG
oS+8AVgxEjZFXw6IRCpzHKE4xbF2eAzv3kn1JO3TypU/kuNUNx0RTc1Cp22k
UixfTzqJKFVDsIW2mpU5TWEMNgDX9DQ30XUHBwcnhuRDJ/fg9US9enapQikk
D4nPbshgxbRa2fsi2B54/VG1Y79e2EdEmnKq81HZlBxxiSMvZMh0O8WQM6x3
CBYr4yrSFTAMeUdgef/aCkvUeHoAAJ1NjGAkcraDKBxlq2BbnDeB6UVaufQF
eW3tp2wD7VrWpLUdpcikRzR0E5eoQ1MXeZEhyQg8TLKDCQ8DHlrI5kLfr41B
TWOrM/DOBemR2116RNRds1jQE+I88AEXbRIrzBCOSdgP4bi0xw6It4M9fvf8
xVu1H4dET0ZckS2uBKn4yorJyuwbMZgk6toZYgRBZrQ/BwJLVyVicrNl4XWI
EJZXRfM9L8jSGFoWOZBxrbvaPzu/FTX4+fM4QLFe4n0Jy4HLqBFMbp5ahN1p
9uD+kNDd0gP7bFoyooA6u7mqDsahfBQ+UuFDZLKXpFokagt7jKSvdeG0TJd3
rV5mspALxIHfDxnKiGsEfqyZRJEn4hT0whSrInVhaNqlSlhgpp1o29pZgdgr
RJkR5JE1OcdwOCbVQnSH0TgE0hEG4TbO5Zk+jNit9r9SZ5VLks/gHTqMQbb9
jY+MdSI6mqNqtGusyn1AUFxMRQMSN9lqqbjOolUX7LHzhpHPniYCX6fGufjs
StIWEIysQ4jVIALfH9/Ff0gQVp2YlvQDFEYfFFI6DztFmNhX6sZPxHwIKKFv
wn80cxmKPhN72jpt39tJ00+rAN5HkTGC+fiXxDkoIHHwZzxDxLIUHyLjdnPh
u35qyTcNjNnxindhfUk76QRhnxAM7kFxJCcexIqRTWNGpcGoAxYhJ1XUEIzH
EfLI2IUewGekp6TNLiGbpFXhJYxBmc9bkIEuveKx+aqpXaRpqxP3JiorHWOd
Pbv9+tHZ9e3X3YDAk6NQC3AqdmvkiptFUZy4tOJgcNJmlTxe/PXSS1HiaOjE
ErHNmjcn6kvCvRwH3awwGwnewX6IG1epvTaP42ob9tywG7HmmoXNINdfx4kf
S6rJzTP2rsR/T82cjAmiYBJNX/vYbpiGM0qY/F4XCuwNORAKj4memzJjlxZk
iCK1PWHxmIDEDTUeeL4wwuAmA4Qptc+Cmp+R8wBPVy64AvUNTNlPcmCstS4T
ajhbWsMpLJ8ycBngqZEwp+GFSAqu3VnswgIWNZfINOKpvRNDD2QDfRoh+3vm
BcVPIoVYIOIpMSwfv6rYoiGeLMGQTqIsRF60L+neTriNVTeEQy/51A/LTVks
mA0QBiKzU7tA4Z3piMyuRJ6TlKAVyL4XRHLBP5INxxOkraYu39Ya0Q/2Lc0Z
byG86wKP2GpwPr4/CgIKxeahXFRUBqYkpLci8Qwah8F45UrOXEFF6wUTQo94
ZBinpTy2FqjAEJQaL/AUAT2pphL1xIVUKhRSedjJJt0k7Bu62CzXO3LAYZ2n
hU58oASh7KJEOcjaTMmZM9VviZffmqoFKAQkQxrUO5NhcYO2Fi4K2QaTJhL6
ZlVUrkyCN4YzaPTa6cXNKDOJFZYIiqAlTJgU6HXW1vN5he9mFQr6JBhCkM/p
wxQ9kklkZ6jWC4GXrVXgpHO0j/T13q9dhnj20TLEPQRaUL1JItzpFLEm+uSc
AcIr6Qbb6hmQTB2RshK+9mzBO4SzPL73PKanEFNgfJiWkMTnA3yitJ3sOBxa
klIlUglDtedLRmWPO4RA/w8vHVaF8Ljh4pxg97g23i5IsyTDPR8/Q4CD1qYj
+dvJhVykRPjZIHknciSNJRUyalYtS3ZSjpFSUtOiXvaDwbTZ3h2o2SDFikAS
sGKWRK20z8AEpZ02EiXUWzbRGWKkuwhHQ7nv2hQnhK8c/olCW7pT+5hq6AeC
b9WstGQuB5fOjeD8DygoNtD6OOiOSA2HJiT4QyRmtYNQn++akMUvrbw8+kDh
5R5bnFZzkJy3BZWoqOTZnkwuLlhIpECV5ISra/B1BP5QfNAqP64CW7XuXKxI
2zwYn71p67kZ9XulHdtsDixBONGVc1E/oIkDNw6dw+uzRKHogO2SB0JtFQbc
xtmGrRuQZ+JDQ5Vzz2oyhRmiE9yZYBdBcRwr5qgarzPYC9tCqgLmvoV2LoJ/
+Plj95LD1rYKZobrGwlmnHHsb9rUW2kpNlsIGqWAh0K1KjCiz8q53lIAGB57
CQ0ALY34gmShaeurYl6vtSuV2a55canrjam9+a+MGy8njOXGHO/m1D3xJVy6
MxPFMgun9gV1b1VvcL6qXDgtB/ccWV6aISgiVOQRfEK1NGzMWklNN06IP6XC
9ozsz99Uo7vXLbbdZZKLYKWcjx7siTO2bP+dPqhqCa45u8kyiIJmlkAwZesV
oRZj4wesQrFXzpCfTZTemrsXvaggMwb4VUB2yp8RcZgmnhQym2pFnO220Zad
xcWVq/dF2sjO45yKpHM8IpLaphV/XGqyHSVK27yfux0cIWrBY19L/NKWLYVd
GBbcNu9sJdRRRpvTnVjAZh36OFej7YBLCGfLwkEbYjS8doSgDA0oCIsG1LbM
uX7LkP2ZSfRFooiEDfgACw1P3yd65UE69QbWipYY5ra3MB7YIgVn20h1JoG/
cC8EBNnbESRhMiPSXo33tkNd4twJ9vf+gYtcKM46tIVPEXT39bH92rytAkNO
F1qGHVtlU0fb6GHYMY8CouEeFRmtmvltrC4KOOPOO+9P2aE0B3b1zJRTcU+3
XI2p2RQOZ/GNLs7S9DOWHlUIfzM37vaThy1YgQYFLnWpeTKDiLGggiQIEYIg
kW6DNvNBxa2oAYdniJK2hq+VccTSbSEX7KBYx2UigoVzdoU9bJ/Vl2o82UOf
bC8LAjzZQ55eCL7HVdqS6HGyQI5OFqW9vHgsTO3KA1yVVkjCw/MNBaO1A3ls
aF1sv4jCTa1nPosr02e67by14C0K3h7K1QAT0X9bSVolxPZCqV2oG4pye1xz
Q5pKZK1V4WzlZ8yyI0Q8S7e1q6ZulU+vvp0NJnmfGwm2i2cCOy4lsXlcuuQT
9X5sV2mgJtQHuDHjo5cSe+XsdUsZo1xxVQuykaNFwoRoVuF+AcnNt1qbdUhp
JDIkgS6OaJLW4JgIrMbQRbws2taGZ+vjNMFqt5vh4AWwg9CbcR8GSRgPGCTm
7syySBP2eOrIJS1CB90I4dOj+DxpLzoYnw5w9X+VaxelbEOZf/ekQRUdUhCP
kkANtgzHhj9a/jmMI7FFJ2TA+qstX8DTh440SKx3yLmrdBN34kL5OPoYCpol
dBT15VY29JmlUEKB4/0u9O8hLhSUu/EgmrkcnB726gvWLIzRQID2/rh1J4jq
aAbN3JYfYBmScG1VhgM0DeomWRd5yZEXSSPxiU8OWmHLFhJm9gFlZ9MF83KZ
MdLfc5pGlBTqaCx6z5UkulquHbXJzqWvfCVweAfJMVDCFX6y/x/WN1R2TGIp
ouELNwSMMssF8ZY3qEMuiZNS5ug9Kf8Vp7s7xbJJW/82BIIBltjL4HwkbHok
GZdlwieAorPaLh4lZ7BJi2Ctlgsb/J0nnP0AC4mg8GzKzESF3BzfP3ysOEvE
SmT/RGfTgvnoRUFvvMT/7J+QrdIHQ89h4RoNmpAmHS+fNjonX2Oorshg2dWK
cARN8XYJ24+Qxq0lVTB6hYTrUH1rTU3Oz0EI5xH8LFyxwWG42+AJiPj0Mf2d
Gz7mJTo/TJ/DqZa1Z7S4jbq8vDjrsgtH6XwGvF0+/Q/qXC1Tc2lIT9Abs8qx
ABrB89n5fsxoOUp6Iz0UGhRu28SrlbInqfoi0HPeGlmOxfstEP4PUXwfNvCG
m0YhTLWgbUo5R45EkivE5nmsEE4YC4YRhOBUT8v+ebS3fL2SbB3kolcLE+5W
wGttpAsBLI5a0PRRMIasYljAWB1HgiaWhfH0W9kdt2Nw92tSSFJYRat4cXt7
1X5Dgl/wS0PfQLN9Rmjp7MojKyQ/psWCZtt+p/YPn3wxfkz/d3jA5IHqy1Y4
QSR+8n7+Rj4dYIJYLshFgE10c3diDWdvd429PWfBZu1OhmpPt6eg2XbQ1u/L
EEpKohoSYEcBEIKtCFW6ox0RYVGfz9ULoOmM0F0aEmGuPjUqr2P/GzcTuRoa
rniQS39QAOXSm37z605duOL/fvyGnWH3ih2mqXtF9Fyr5TUjk2oFP95H54JG
9pmQsFhoXNQ5CUCynASE4k/EX6jsG/rmezjzN1e0+1xvgXZf/n78+yf/wDab
5LRqpghhTGl8V+5WC/loeZ89/eJLGY/NgYuK7wdHTSybl2YW5WCc2TtrSBhn
naQvTSc1Gv1FAWLp4QBdgstWha04vPrI5t87j9ox1aObi7ORjN8Sfaxed7+I
T6OwPQkB/bCW0sTuntS/g06kf3wQkskmG78uorejzvclAs2SmnsHHUMdCAFA
YGwTV8v7OqlonoRx5dDWVeABP0UfHzn8/Zei7794cqj2adOwKQdOz0hhOkDU
4eHh52qfBPx3n/3DAZeh8Quht43y1SsIp4QLhojLzwSiI6uMjFDEtxyYb3eJ
PTdYeN4u8e2ubhhzuLKpCG7E56KAozhhOsWCAv70Ng4ZOX/i6p+uHBzGlUIz
tm6PfWKYj3lhfO5Gg45INnAYIbpP7EYuzPCggYNpMLrhFHAoI4odYC+W3oBb
JHpckXSXDItGFB64g5bAFbotBWIJFbNMqK7xlW/Md82KpRSNsTwO1SNh0A6f
S+8B9AX+FefBSsUF+dqcJznjfp50y4MkOkOLnG62SuS7uNKREVFNEr4+HbTU
u6IjngpSP9A126I9ZE73R2VQj+DzKRJuWC83bAjg4LOmdrzJBb/hSrD377kG
FTc3xTiNrQPUobvzSHOhSQi8s0+ZJDaElrAN10V1V2S5Tt4WJUfSoxWsY0fI
4t4aOJCMrSIAQw9OCen74/RPOJdvOAoQtGkLLloIHB7GOfAd5oevcE0VZyO9
NWjLVp9+/vhxHzO5pFziMknsc2A9kO8cIWgpY5zi0uPIR2h7aXN2tT/dBmfd
yWIxdxWxW7TjUSCBXRl2xCK7OUEi854zrISD7uIIQoiW5LTVuBqKdpZ4IvUX
KUUK0bsLtB5BGIwkQKvbVzcw/YTpiL0AoV02hQtM3IFJ0jFJESVXImAaTmuW
hp3yEVeSGdmm2HLQZi1YD3cc03nz9i1L9DOcBPVBAA+NJm8RfLPfu+v0Xuq3
+m4ZdOgGlWhrz8S6U7UB9nby0QXmQPxgtToGTtgtr9Hbk0dceTwM0kbrkbgC
B5us48soOI2NqV0aAdy61KuVFITTBh2bVJeNsKfIWrf+cOPCSZ76WI+pfcSq
W3UVdnOf7VQ4NhtbUA/fyUsxa1KDKPb2jMm2Vziz4wlwkVj39gRQmFWx2yg2
VtEB1IgTxCdPmwrBpKnBeXGCMR3HJQ5vtpELwX/erAjsQngC5XXklkhszFUk
hRhQB61ON+74aMfdynAkcmG6M2D12mbodAPlJgLMDTkFT7ghmimbWC6a0WXi
9IzbLdT4OO/5tbDst1cXrkyzJWQbWarcRVJEoWfRkZRwIFNJ2QLDTBNO0yG+
SX9EqRZSAvc6NS6mKRIdRu7GhIJuaSMqUuwu3sauwzEsbuLfh+ARRiZmKGti
R3/kNeLMTmSJzXPooVVYrKfkvjHUwNPEwF5RfF9Cyf5kmdESJUVyB9i2ZWr8
Bd8G2eSr+9/54M2QD3JMkcYBjvJfQqk0JKUp8ilpg/NGUM3NCqHDnVQYxsVg
XProRUZuzIGPCjSBwFK2LTjdDeDT5vZe10Z1iqpdAC7OHEDQXA11pCMf2Fjr
0jO1P48Aj8anWDkGxw25QCN1bwDezc26lfnhDv5wyji05qCzM2DIS+g8F2LI
rZfQgtj+Fvz4ol5EihGMXcgeimNIfuiQk3xIhORkA2vJVVn4V9SCdGYS6l54
hCj9LuFfdEYEwKAgUQcTZxyynxpXFrKjMnsyh4KipXSqUolucvl0gS4XKCXy
noLbWdFvrShH/jNwvs1x6kaqAqITWCZfIvXgoogcpqRHOFbCXOeusMMcQqGe
hKxRY3GLSugJ0j64hiOT0joEvTWngsJZmXBiFds1GgxGWyfitsPrbeYoOjFY
b1WjM1hzpbo7jzaNaTSckPZl4VPUB+SupOLB83CSQP1wr6fRqfGoVpKPArkw
6TBUc3/4qFwoWC121ZS3M/fNwDgjdbyd1GkzObyXnMyTtENVdwBIOKpAS62c
ed5Ky0UQgJZEoMStl4t3/UBSouATkm2lb/QLAL28JF8lwAXMqJpyOVwpK8Cy
vK3xSTXHolHwmYcMmtHzqCOTZ3beItmXENFpu9jnCKg7LSEpfh8PDS85SOJO
+2yb9fhKEGf2ikwuTIKv5mW/PYoaTwmRVNIQcp6tUxgVoxBfVNsP9kc3yjjH
MAwipQVVh5Rx9MpHWLlcq/JAgbEg2AHnBIbqxfXVyVBdPZtcPxf4fD65un7e
rW9w2bMoHdk5WyBmNpJWd+rN8fzI83w0NwfewkmLy6ubyXfPpaMok8wzZggL
6cK22LnEBbyF2/eWp2OSDkJEr3f4YSaFNO4aKBzTw70KV/6+sSu+KWAwOPyy
fweZPzjlryhzhGgvJUPwBbpEXh+rw0PXBEeYaqf4ItA3doOpXplww0de6H0X
/N0/PJD4T4guaallIDTjC15jjIQ8c2K06xa426S1O9jCBRTUbglhuJfoY3z0
o+6sifHK/pODUH6W9HARTzoqPajkVoqKWJQdlUjbBzpFw/GVO/5vAPoNvPCA
8VDGgYJiDna40jBHYXc814OaCG50Lt/h5HQbnHG1kZkEoNsQzjEKNPvCgpcQ
GoklFCaW63fuwnVwK5NHRRPBDEtXeLNyOKCNiHNYgzvhSmDE7Hz0RjLYcivI
1m0qWOVG7tCZ6hTS6DyTUCnmOJXdvhCO1R+7RZcl5JHcDBndmevyzu6iHQ4O
uHhyy6Iy4NFgsG3KjnDzz4M/9TPc+Ts9R7jk8Of82pCKLyGg8W79b5kMw8+W
UJ/932A5+uSfYHnorJI7bdyepKax+fcyZAV/++95HP28n/NwR8BpFuF3Kh78
dYyjn/njGCocEEWhTnymibfY3WQ7bC+nHXbumqXZj8PVsEye//37eEMZPM23
vW8Vk/l7lB7H9cSOQKiZHEaXkQ795aLDcF8ofzVJiXp/GdOn128z//FP+i19
PPMf/8bbVttKS5rbN2N1WZPeeo6b4Muatj0zBWTnHIIE9+ga6hEfzvnD3VCd
QnDfZoh8kXi//PHfy7u7H//d5kaE7iW9fcfccF4QmDvq3FfIP1gRCipJQEmI
9oWj2e8++IqVBvHL5TIlqEtbxD/lF6zHSJ2PXulpz2BHNwmRKgrYgPmTiN7/
MRDq9Vf7rRIVFx3QcOGnEJjVb5ef9osV/fj4P4a7+f/OvxKgQiB+gCJhH2AP
dwW2N7IynZEli0PAW3cqBdS4w0awKHQuvB/6u+2H4br6Ybh/ftjeJv8r3tgf
wtNOV/Ld5yx732501RmT/vPTD/8KAyuKJlMzUmiZPyO8lCPRP/3wb5BIOdGP
la6cs1PVTbJxQZPoKEwnPtG50+squnWkd5dX50ozJvmkzHWDW7uTxJB2ONEl
GR11RW4fmfiy4G9QJ05CC+tDpD4hPbkhTkeKgv4qUiQCDa4bqPAn8cf5hpO8
pwQxbki/woqeappokHf569ymafTnzQwlMlBR0c8xDrd++4M0HU1Dq5cl4VpD
iu8bjZ9KQTSHuvrG6vyOGEH9WdPcv/nxv8qFaKZvGo1pWnLG6MErbdWfrVMO
Q/cLgaANgQeuyIl+0HHY+Yky/FXTnq2JILMZTfbckgAZpBbTt6n82dxZdb7G
uRn83f19ymH7gwtD/zNYw+jC9mH8S1A0097t+sNu/fywdxhl2PnRjeHu3zCi
r+F9L4mEJFk5duC2/Rk3j3tuLVl1kqRqTdJ/bRLsxS1BmA3xV4Nc57emyvGb
h3nxfUpsOBNI8R2JxgtNdgPQsMuW7h63E3+PW583t+55yzid5hj1ZInSIpol
qY/vikJujB5GP9520GEc9/hFo9fGHvT31DeGshFf4NRkxaxETIAzSAG8HGxv
oWv8rCR4T6Ry+fuINu4FQlupOWAi4A7Sc7ca5xzdWin0Z0xGGGfw7kh+CNYk
/2dvTsDZ7LEuffjK7KzbId9N271ymfO73P+22+gOjt5enl5ihpOZP2Mv58l3
zuaWTMUdBxM6aoO7Rt4Al8S6Yn4fIvG3PkR3G44H/wMeXMhYsHcAAA== [rfced] Although this document discusses inclusiveness
extensively, as part of our process we still need to ask you to
review the "Inclusive Language" portion of the online Style Guide at
<https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
and let us know if any changes are needed.  Updates of this nature
typically result in more precise language, which is helpful for
readers.

Note that our script did not flag any words in particular, but this
should still be reviewed as a best practice. -->

<!-- [rfced] Please let us know if any changes are needed for the
following:

a) The following terms were used inconsistently in this document.
We chose to use the latter forms.  Please let us know any objections.

 block list / blocklist (Section 2.3.1)

 community network(s) (12 instances in text) /
   Community Network(s) (14 instances in text) (per RFC 7962)

 (Non-)Terrestrial / (non-)terrestrial

b) The following terms appear to be used inconsistently in this
document.  Please let us know which form is preferred.

 internet / Internet (used generally, e.g., "the Internet community",
   "the internet community")

 internet access (1 instance) / Internet Access (2 instances) /
   Internet access (2 instances) (in text; used generally)
   (We also see "in Internet Access of Services" in the Abstract.)

 satellite / Satellite (e.g., "satellite constellations",
   "via Satellite-dependent community networks")

c) Please let us know how/if the following should be made consistent
(asking because "circumvents" is normally a verb; please see
<https://www.merriam-webster.com/dictionary/circumvents>):

 circumvents (noun) / circumvention (noun) -->

</rfc>