rfc9707v3.txt | rfc9707.txt | |||
---|---|---|---|---|
Internet Architecture Board (IAB) M. Kühlewind | Internet Architecture Board (IAB) M. Kühlewind | |||
Request for Comments: 9707 | Request for Comments: 9707 | |||
Category: Informational D. Dhody | Category: Informational D. Dhody | |||
ISSN: 2070-1721 | ISSN: 2070-1721 | |||
M. Knodel | M. Knodel | |||
December 2024 | January 2025 | |||
Report from the IAB Workshop on Barriers to Internet Access of Services | Report from the IAB Workshop on Barriers to Internet Access of Services | |||
(BIAS) | (BIAS) | |||
Abstract | Abstract | |||
The "Barriers to Internet Access of Services (BIAS)" workshop was | The "Barriers to Internet Access of Services (BIAS)" workshop was | |||
convened by the Internet Architecture Board (IAB) from January 15-17, | convened by the Internet Architecture Board (IAB) from January 15-17, | |||
2024 as a three-day online meeting. Based on the submitted position | 2024 as a three-day online meeting. Based on the submitted position | |||
papers, the workshop covered three areas of interest: the role of | papers, the workshop covered three areas of interest: the role of | |||
skipping to change at line 47 ¶ | skipping to change at line 47 ¶ | |||
Internet Architecture Board (IAB). Documents approved for | Internet Architecture Board (IAB). Documents approved for | |||
publication by the IAB are not candidates for any level of Internet | publication by the IAB are not candidates for any level of Internet | |||
Standard; see Section 2 of RFC 7841. | Standard; see Section 2 of RFC 7841. | |||
Information about the current status of this document, any errata, | Information about the current status of this document, any errata, | |||
and how to provide feedback on it may be obtained at | and how to provide feedback on it may be obtained at | |||
https://www.rfc-editor.org/info/rfc9707. | https://www.rfc-editor.org/info/rfc9707. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2024 IETF Trust and the persons identified as the | Copyright (c) 2025 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
to this document. | to this document. | |||
Table of Contents | Table of Contents | |||
skipping to change at line 117 ¶ | skipping to change at line 117 ¶ | |||
divide, it is also important to understand persistent and novel | divide, it is also important to understand persistent and novel | |||
inequalities in the digital age when accessing content and services. | inequalities in the digital age when accessing content and services. | |||
There are more and more barriers to meaningful access to the services | There are more and more barriers to meaningful access to the services | |||
and applications that run on the Internet. Even if Internet | and applications that run on the Internet. Even if Internet | |||
connectivity is available, information and service access may remain | connectivity is available, information and service access may remain | |||
challenged and unequal. | challenged and unequal. | |||
This IAB workshop aimed to | This IAB workshop aimed to | |||
* collect reports about barriers to accessing content and services | * collect reports about barriers to accessing content and services | |||
on the Internet. For example: | on the Internet -- for example, based on filtering or on blocking, | |||
or due to general inequality of technological capabilities, e.g., | ||||
- based on filtering. | device or protocol limitations. | |||
- based on blocking. | ||||
- due to general inequality of technological capabilities, e.g., | ||||
device or protocol limitations. | ||||
* help the Internet community get a better understanding of how the | * help the Internet community get a better understanding of how the | |||
Internet functions in different parts of the world and which | Internet functions in different parts of the world and which | |||
technology or techniques need to be used to gain access to | technology or techniques need to be used to gain access to | |||
content. | content. | |||
* build an understanding of what "being connected" to the Internet | * build an understanding of what "being connected" to the Internet | |||
means: What is the Internet to users? What is needed to be | means: What is the Internet to users? What is needed to be | |||
meaningfully connected? What are the minimum requirements to be | meaningfully connected? What are the minimum requirements to be | |||
able to access certain parts of the content and services provided | able to access certain parts of the content and services provided | |||
skipping to change at line 172 ¶ | skipping to change at line 167 ¶ | |||
The first day of the workshop focused on the role of Community | The first day of the workshop focused on the role of Community | |||
Networks [RFC7962] as a way to overcome the barriers to Internet | Networks [RFC7962] as a way to overcome the barriers to Internet | |||
access. Community Networks are self-organized networks wholly owned | access. Community Networks are self-organized networks wholly owned | |||
by the community and thus provide an alternative mechanism to bring | by the community and thus provide an alternative mechanism to bring | |||
connectivity and Internet services to those places that lack | connectivity and Internet services to those places that lack | |||
commercial interest. | commercial interest. | |||
Presentations ranged from highlighting the need for measuring Quality | Presentations ranged from highlighting the need for measuring Quality | |||
of Experience (QoE) for Community Networks, to the potential role the | of Experience (QoE) for Community Networks, to the potential role the | |||
Content Delivery Network (CDN) can play in Community Networks, to the | Content Delivery Network (CDN) can play in Community Networks, to the | |||
role of Satellite Networks, and finally, to the vital role of the | role of satellite networks, and finally, to the vital role of the | |||
spectrum in this space. | spectrum in this space. | |||
2.1.1. The Quality of Community Networks | 2.1.1. The Quality of Community Networks | |||
[MARTINEZ] highlighted the need to address QoE in discussions around | [MARTINEZ] highlighted the need to address QoE in discussions around | |||
Community Networks. As a community-driven deployment, the knowledge | Community Networks. As a community-driven deployment, the knowledge | |||
and involvement of individuals can vary; therefore, there are no | and involvement of individuals can vary; therefore, there are no | |||
guarantees of connectivity or quality of service. There is a need to | guarantees of connectivity or quality of service. There is a need to | |||
focus on user expectations and how they translate to measurable | focus on user expectations and how they translate to measurable | |||
performance indicators. Further, it asks for better documentation of | performance indicators. Further, it asks for better documentation of | |||
best practices in deploying Community Networks as well as careful | best practices in deploying Community Networks as well as careful | |||
thought regarding manageability considerations for Community Networks | thought regarding manageability considerations for Community Networks | |||
in protocol development. [GUIFI] as an example Community Network was | in protocol development. [GUIFI] as an example Community Network was | |||
discussed, and some existing resources for Community Networks [APC] | discussed, and some existing resources for Community Networks [APC] | |||
[ISOC] [TBB] were shared by the participants. | [ISOC] [TBB] were shared by the participants. | |||
The inconsistent quality and performance of Satellite Internet result | The inconsistent quality and performance of satellite Internet result | |||
in a connectivity gap for Community Networks that rely on non- | in a connectivity gap for Community Networks that rely on non- | |||
terrestrial networks (NTNs) for Internet access [HU]. | terrestrial networks (NTNs) for Internet access [HU]. | |||
2.1.2. Strengthening Community Networks | 2.1.2. Strengthening Community Networks | |||
[BENSON] focused on the prohibitive cost of transit and Internet | [BENSON] focused on the prohibitive cost of transit and Internet | |||
services for Community Networks and argued for CDNs to provide | services for Community Networks and argued for CDNs to provide | |||
transit-like and Internet services, at no more than at-cost, in a | transit-like and Internet services, at no more than at-cost, in a | |||
mutually beneficial way. Community Networks still need backhaul to | mutually beneficial way. Community Networks still need backhaul to | |||
and from the CDN's point of presence, and models for community- | and from the CDN's point of presence, and models for community- | |||
backhaul and open-source CDNs were highlighted. Discussion included | backhaul and open-source CDNs were highlighted. Discussion included | |||
the status of Project PANGEA [PANGEA] as well as legal and commercial | the status of Project PANGEA [PANGEA] as well as legal and commercial | |||
considerations related to such use of CDNs. | considerations related to such use of CDNs. | |||
[HU] highlighted that Satellite Internet provided by advanced low- | [HU] highlighted that satellite Internet provided by advanced low- | |||
Earth orbit (LEO) Satellite constellations can play a pivotal role in | Earth orbit (LEO) satellite constellations can play a pivotal role in | |||
closing the connectivity gap in the urban-rural digital divide via | closing the connectivity gap in the urban-rural digital divide via | |||
Satellite-dependent Community Networks. These existing known | satellite-dependent Community Networks. These existing known | |||
performance and management gaps need to be focused on, to enable | performance and management gaps need to be focused on, to enable | |||
Satellite Internet to resolve the divide. Further, research | satellite Internet to resolve the divide. Further, research | |||
directions such as multi-layer Satellite networking, autonomous | directions such as multi-layer satellite networking, autonomous | |||
maintenance, and integration between terrestrial networks and NTNs | maintenance, and integration between terrestrial networks and NTNs | |||
were suggested. | were suggested. | |||
[RENNO] called attention to the coveted 6 GHz (part of the C-band | [RENNO] called attention to the coveted 6 GHz (part of the C-band | |||
with a desirable mix of coverage and capacity) as a prime choice for | with a desirable mix of coverage and capacity) as a prime choice for | |||
International Mobile Telecommunication (IMT) for 5G technology while | International Mobile Telecommunication (IMT) for 5G technology while | |||
it is in common unlicensed use in Community Networks (and small | it is in common unlicensed use in Community Networks (and small | |||
ISPs). Spectrum allocations directly impact industries and market | ISPs). Spectrum allocations directly impact industries and market | |||
access with ramifications for Community Networks. Further, there was | access with ramifications for Community Networks. Further, there was | |||
a discussion on geopolitical tensions because of these allocations. | a discussion on geopolitical tensions regarding the use of unlicensed | |||
spectrum and commercial interest in new spectrum usage. | ||||
2.1.3. Discussion | 2.1.3. Discussion | |||
How can the technical community address the management gaps and | How can the technical community address the management gaps and | |||
improve best practices for Community Networks? Is the increasing | improve best practices for Community Networks? Is the increasing | |||
complexity of the Internet making it more challenging to establish | complexity of the Internet making it more challenging to establish | |||
secure connections, and should this be taken into account in the | secure connections, and should this be taken into account in the | |||
design of the Internet? What steps need to be taken to make sure | design of the Internet? What steps need to be taken to make sure | |||
Community Networks are secure? Should manageability considerations | Community Networks are secure? Should manageability considerations | |||
be expanded to explicitly consider Community Networks? The Global | be expanded to explicitly consider Community Networks? The Global | |||
skipping to change at line 258 ¶ | skipping to change at line 254 ¶ | |||
connectivity is available, for some there will remain challenges | connectivity is available, for some there will remain challenges | |||
towards achieving equality. This becomes especially significant as | towards achieving equality. This becomes especially significant as | |||
governments view the Internet as an important tool for helping them | governments view the Internet as an important tool for helping them | |||
reach the SDGs listed in [SDGs] and for globally supporting human | reach the SDGs listed in [SDGs] and for globally supporting human | |||
rights. | rights. | |||
The second day of workshops was essential to understanding the nature | The second day of workshops was essential to understanding the nature | |||
of the digital divide. Presentations of reports interrogated at | of the digital divide. Presentations of reports interrogated at | |||
least three key aspects of the digital divide, though it is | least three key aspects of the digital divide, though it is | |||
recognized that there may be more technical aspects of the digital | recognized that there may be more technical aspects of the digital | |||
divide that were not addressed. Three of those aspects were: | divide that were not addressed. The three aspects presented and | |||
discussed were differences between population demographics in the | ||||
* differences between population demographics in the provision of | provision of online resources by governments, inequality in the use | |||
online resources by governments. | of multilingualized domains and email addresses, and increased costs | |||
for end-user downloads from websites of contemporary sizes. | ||||
* inequality in the use of multilingualized domains and email | ||||
addresses. | ||||
* increased costs for end-user downloads from websites of | ||||
contemporary sizes. | ||||
2.2.1. Disparities in Service Provisioning | 2.2.1. Disparities in Service Provisioning | |||
Ralph Holz presented research that exposes the more limited DNS- | Ralph Holz presented research that exposes the more limited DNS- | |||
mediated access to government websites by Indigenous communities in | mediated access to government websites by Indigenous communities in | |||
Australia as compared to less disadvantaged users in the same | Australia as compared to less disadvantaged users in the same | |||
population in "Evidence for a digital divide? Measuring DNS | population in "Evidence for a digital divide? Measuring DNS | |||
dependencies in the context of the indigenous population of | dependencies in the context of the indigenous population of | |||
Australia" [HOLZ]. DNS dependency trends were analyzed between two | Australia" [HOLZ]. DNS dependency trends were analyzed between two | |||
lists of domains serving Australian government sites for Indigenous | lists of domains serving Australian government sites for Indigenous | |||
skipping to change at line 362 ¶ | skipping to change at line 353 ¶ | |||
validate the blocking as well as analyses of how blocking is | validate the blocking as well as analyses of how blocking is | |||
implemented were discussed, i.e., which protocols are used but also | implemented were discussed, i.e., which protocols are used but also | |||
which kinds of devices are used to configure the blocking rules and | which kinds of devices are used to configure the blocking rules and | |||
where they are deployed. | where they are deployed. | |||
2.3.1. Censorship Orders, Measurements, and Device Analysis | 2.3.1. Censorship Orders, Measurements, and Device Analysis | |||
[SAMSUDIN] reported on confirmed blocking from 10 countries | [SAMSUDIN] reported on confirmed blocking from 10 countries | |||
(Cambodia, Hong Kong (China), India, Indonesia, Malaysia, Myanmar, | (Cambodia, Hong Kong (China), India, Indonesia, Malaysia, Myanmar, | |||
Philippines, Thailand, Timor-Leste, and Vietnam) in the period from 1 | Philippines, Thailand, Timor-Leste, and Vietnam) in the period from 1 | |||
July 2022 to 30 June 2023. The blocking was confirmed by either | July 2022 to 30 June 2023. The blocking was confirmed by (1) Open | |||
(1) Open Observatory of Network Interference (OONI) measurements for | Observatory of Network Interference (OONI) measurements for existing | |||
existing blocking fingerprints or heuristics (i.e., for new blocking | blocking fingerprints, (2) heuristics (i.e., for new blocking | |||
fingerprints as well as news reports of blocking orders) or (2) user | fingerprints as well as news reports of blocking orders), or (3) user | |||
experiences. Most of these countries block specific content such as | experiences. Most of these countries block specific content such as | |||
porn, gambling, or certain news pages. Interestingly, the blocking | porn, gambling, or certain news pages. Interestingly, the blocking | |||
in Hong Kong and Myanmar is focused on the military and governmental | in Hong Kong and Myanmar is focused on the military and governmental | |||
pages of foreign countries. Blocking is often realized by either DNS | pages of foreign countries. Blocking is often realized by either DNS | |||
tampering or HTTP tampering. For DNS, either a chosen IP address, a | tampering or HTTP tampering. For DNS, either a chosen IP address, a | |||
bogon IP address (e.g., 127.0.0.1), or an empty domain (NXDOMAIN) is | bogon IP address (e.g., 127.0.0.1), or an empty domain (NXDOMAIN) is | |||
used. In the case of DNS tampering using a chosen IP address or HTTP | used. In the case of DNS tampering using a chosen IP address or HTTP | |||
tampering, some countries provide a block page that exposes the | tampering, some countries provide a block page that exposes the | |||
blocking; however, more transparency related to blocking is requested | blocking; however, more transparency related to blocking is requested | |||
by civil society organizations and the Internet Monitoring Action | by civil society organizations and the Internet Monitoring Action | |||
Project (iMAP). | Project (iMAP). | |||
[GROVER] further focused the discussion on online censorship in | [GROVER] further focused the discussion on online censorship in | |||
India, Pakistan, and Indonesia. | India, Pakistan, and Indonesia. In India, where providers are | |||
As discussed in [Singh2020], in India, where providers are | ||||
responsible for implementing the blocking but no method is mandated, | responsible for implementing the blocking but no method is mandated, | |||
the six major ISPs (covering 98.82% of all subscribers) were tested | the six major ISPs (covering 98.82% of all subscribers) were tested | |||
on a total of 4379 blocked websites (based on court orders, user | on 4379 blocked websites (based on court orders, user reports, and | |||
reports, and publicly available or leaked government orders) by using | publicly available or leaked government orders) by using DNS | |||
DNS poisoning/injection or using censorship based on HTTP or the | poisoning/injection or using censorship based on HTTP or the Server | |||
Server Name Indication (SNI). The censorship techniques used and | Name Indication (SNI). The censorship techniques used and websites | |||
websites blocked were different across ISPs. Multiple ISPs used two | blocked were different across ISPs. Multiple ISPs used two different | |||
different techniques (depending on the website), and all but one | techniques (depending on the website), and all but one provided | |||
provided censorship notices. A list of 4379 potentially blocked | censorship notices. Providers blocked between 1892 and 3721 (of | |||
websites was tested; 4033 of those websites appeared in at least one | 4379) pages with only 1115 pages (27.64%) blocked by all ISPs | |||
ISP's blocklist. Providers blocked between 1892 and 3721 of the 4033 | [Singh2020]. | |||
websites, with only 1115 websites (27.64%) blocked by all six ISPs. | ||||
In contrast, in Pakistan, the government can also order the ISPs to | In contrast, in Pakistan, the government can also order the ISPs to | |||
perform blocking, and blocking has even been observed in the past at | perform blocking, and blocking has even been observed in the past at | |||
the Internet Exchange Point (IXP) level. Since 2020, there has also | the Internet Exchange Point (IXP) level. Since 2020, there has also | |||
been a central Web Monitoring System deployed at lines of | been a central Web Monitoring System deployed at lines of | |||
international connectivity. In Indonesia, initially, the government | international connectivity. In Indonesia, initially, the government | |||
guided ISPs in how to perform the blocking. The regulations were | guided ISPs in how to perform the blocking. The regulations were | |||
updated in 2020 to allow Indonesian ISPs to block websites at their | updated in 2020 to allow Indonesian ISPs to block websites at their | |||
discretion. In 2022, there was a proposal by ISPs to centralize DNS. | discretion. In 2022, there was a proposal by ISPs to centralize DNS. | |||
In Indonesia, a partial blocklist is publicly available, but without | In Indonesia, a partial blocklist is publicly available, but without | |||
skipping to change at line 438 ¶ | skipping to change at line 426 ¶ | |||
All speakers called for more transparency by requiring blocking | All speakers called for more transparency by requiring blocking | |||
messages as well as publication and auditing of blocklists. | messages as well as publication and auditing of blocklists. | |||
Potentially, even standardization could help. | Potentially, even standardization could help. | |||
2.3.2. Use of VPNs for Censorship Circumventions and User Expectations | 2.3.2. Use of VPNs for Censorship Circumventions and User Expectations | |||
Further on in the session, the possibility and prevalence of using | Further on in the session, the possibility and prevalence of using | |||
VPNs for circumvention were discussed, including user expectations | VPNs for circumvention were discussed, including user expectations | |||
and an analysis of security shortcomings of commercial VPN services. | and an analysis of security shortcomings of commercial VPN services. | |||
The analysis presented in [RAMESH-1] has shown various problems that | The analysis presented in [RAMESH-1] has shown various problems that | |||
lead to data leaks, such as (1) leakage of IPv6 traffic, (2) non- | lead to data leaks, such as leakage of IPv6 traffic, non-browser | |||
browser traffic, or (3) tunnel failure, in addition to failing to | traffic, or tunnel failure, not upholding user expectations, | |||
uphold user expectations, especially when used in authoritarian | especially when used in authoritarian regimes for censorship | |||
regimes for censorship circumvention or private communication. | circumvention or private communication. | |||
The question of how common the use of VPNs for circumvention is and | The question of how common the use of VPNs for circumvention is and | |||
its legal implications, as VPNs are illegal in a few countries, was | its legal implications, as VPNs are illegal in a few countries, was | |||
discussed. For example, VPNs are not officially banned in India, but | discussed. For example, VPNs are not officially banned in India, but | |||
VPN providers need to store log data and those who haven't complied | VPN providers need to store log data and those who haven't complied | |||
stopped serving India. However, more data on VPN use and blocking | stopped serving India. However, more data on VPN use and blocking | |||
might be needed. | might be needed. | |||
2.3.3. Discussion | 2.3.3. Discussion | |||
skipping to change at line 652 ¶ | skipping to change at line 640 ¶ | |||
measurement-methods-for-locating-and-examining-censorship- | measurement-methods-for-locating-and-examining-censorship- | |||
devices-00.pdf>. | devices-00.pdf>. | |||
Appendix A. Position Papers | Appendix A. Position Papers | |||
Nineteen position papers were submitted to the workshop call for | Nineteen position papers were submitted to the workshop call for | |||
papers. Twelve were selected for publication. Papers that were not | papers. Twelve were selected for publication. Papers that were not | |||
published either (1) only provided a very prelimited analysis of an | published either (1) only provided a very prelimited analysis of an | |||
idea that was felt to be incomprehensive for discussion at the | idea that was felt to be incomprehensive for discussion at the | |||
workshop or (2) addressed problems that were considered beyond the | workshop or (2) addressed problems that were considered beyond the | |||
scope of the workshop discussions, e.g., discussing cybersecurity | scope as dedicated for the workshop discussion, e.g., discussing | |||
threats as a barrier to participation or implication of technology in | cybersecurity threats as a barrier to participation or implication of | |||
a regulation that imposes blocking. Both of these scenarios pose a | technology in a regulation that imposes blocking. Both of these | |||
potentially severe risk for the open Internet; however, they might | topics pose a potentially severe risk for the open Internet; however, | |||
pose a high risk for all Internet users but do not necessarily imply | they might pose a high risk for all Internet users but do not | |||
an unbalance. | necessarily imply an unbalance. | |||
All accepted papers are available at | All accepted papers are available at | |||
<https://datatracker.ietf.org/group/biasws/materials/>. | <https://datatracker.ietf.org/group/biasws/materials/>. | |||
This is the list of all published papers: | This is the list of all published papers: | |||
Community Networks: | Community Networks: | |||
* Martínez-Cervantes, L. M. and R. Guevara-Martínez: Community | * Martínez-Cervantes, L. M. and R. Guevara-Martínez: Community | |||
Networks and the Quest for Quality [MARTINEZ] | Networks and the Quest for Quality [MARTINEZ] | |||
skipping to change at line 735 ¶ | skipping to change at line 723 ¶ | |||
Peirano, Lai Yi Ohlsen, Luis Martinez, Mallory Knodel, Marwan Fayed, | Peirano, Lai Yi Ohlsen, Luis Martinez, Mallory Knodel, Marwan Fayed, | |||
Matthew Bocci, Michael Welzl, Michuki Mwangi, Mirja Kühlewind, Mona | Matthew Bocci, Michael Welzl, Michuki Mwangi, Mirja Kühlewind, Mona | |||
Wang, Peng Hu, Ralph Holz, Raquel Rennó, Reethika Ramesh, Rumaisa | Wang, Peng Hu, Ralph Holz, Raquel Rennó, Reethika Ramesh, Rumaisa | |||
Habib, Sarmad Hussain, Simone Basso, Siti Nurliza Samsudin, Suresh | Habib, Sarmad Hussain, Simone Basso, Siti Nurliza Samsudin, Suresh | |||
Krishnan, Theophilus Benson, Tirumaleswar Reddy.K, Tommy Pauly, Vesna | Krishnan, Theophilus Benson, Tirumaleswar Reddy.K, Tommy Pauly, Vesna | |||
Manojlovic, and Wes Hardaker. | Manojlovic, and Wes Hardaker. | |||
Appendix C. Workshop Program Committee | Appendix C. Workshop Program Committee | |||
The workshop program committee members were Christopher Wood (IAB, | The workshop program committee members were Christopher Wood (IAB, | |||
Cloudflare), Dhruv Dhody (IAB, Huawei), Mallory Knodel (IAB, NYU), | Cloudflare), Dhruv Dhody (IAB, Huawei), Mallory Knodel (IAB, Center | |||
Mirja Kühlewind (IAB, Ericsson), and Tommy Pauly (IAB, Apple). | for Democracy and Technology), Mirja Kühlewind (IAB, Ericsson), and | |||
Tommy Pauly (IAB, Apple). | ||||
IAB Members at the Time of Approval | IAB Members at the Time of Approval | |||
Internet Architecture Board members at the time this document was | Internet Architecture Board members at the time this document was | |||
approved for publication were: | approved for publication were: | |||
Matthew Bocci | Matthew Bocci | |||
Alissa Cooper | Alissa Cooper | |||
Roman Danyliw | Roman Danyliw | |||
Dhruv Dhody | Dhruv Dhody | |||
End of changes. 16 change blocks. | ||||
57 lines changed or deleted | 46 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |