rfc8890xml2.original.xml   rfc8890.xml 
<?xml version="1.0" encoding="UTF-8"?> <?xml version='1.0' encoding='utf-8'?>
<!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.13 --> <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.13 -->
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent"> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902"
docName="draft-iab-for-the-users-04" number="0000" submissionType="IAB" docName="draft-iab-for-the-users-04" number="8890" submissionType="IAB"
category="info" consensus="true" obsoletes="" updates="" xml:lang="en" category="info" consensus="true" obsoletes="" updates="" xml:lang="en"
tocInclude="true" sortRefs="true" symRefs="true" version="3"> tocInclude="true" sortRefs="true" symRefs="true" version="3">
<!-- xml2rfc v2v3 conversion 2.34.0 --> <!-- xml2rfc v2v3 conversion 2.34.0 -->
<front> <front>
<title>The Internet is for End Users</title> <title>The Internet is for End Users</title>
<seriesInfo name="RFC" value="0000"/> <seriesInfo name="RFC" value="8890"/>
<author initials="M." surname="Nottingham" fullname="Mark Nottingham"> <author initials="M." surname="Nottingham" fullname="Mark Nottingham">
<organization/> <organization/>
<address> <address>
<postal>
<city>Prahran</city><region>VIC</region>
<country>Australia</country>
</postal>
<email>mnot@mnot.net</email> <email>mnot@mnot.net</email>
<uri>https://www.mnot.net/</uri> <uri>https://www.mnot.net/</uri>
</address> </address>
</author> </author>
<date year="2020" month="May"/>
<workgroup>Internet Architecture Board (IAB)</workgroup> <date year="2020" month="August"/>
<keyword>stakeholder</keyword> <keyword>stakeholder</keyword>
<abstract> <abstract>
<t>This document explains why the IAB believes that, when there is a <t>This document explains why the IAB believes that, when there is a
conflict between the interests of end users of the Internet and other conflict between the interests of end users of the Internet and other
parties, IETF decisions should favour end users. It also explores how parties, IETF decisions should favor end users. It also explores how
this can more effectively be achieved.</t> the IETF can more effectively achieve this.</t>
</abstract> </abstract>
<note>
<name>Note to Readers</name>
<t>The issues list for this draft can be found at <eref
target="https://github.com/intarchboard/for-the-users/issues">https://gith
ub.com/intarchboard/for-the-users/issues</eref>.</t>
<t>The most recent (often, unpublished) draft is at <eref
target="https://intarchboard.github.io/for-the-users/">https://intarchboar
d.github.io/for-the-users/</eref>.</t>
<t>Recent changes are listed at <eref
target="https://github.com/intarchboard/for-the-users/commits/master">http
s://github.com/intarchboard/for-the-users/commits/master</eref>.</t>
<t>See also the draft's current status in the IETF datatracker, at
<eref
target="https://datatracker.ietf.org/doc/draft-iab-for-the-users/">https://d
atatracker.ietf.org/doc/draft-iab-for-the-users/</eref>.</t>
</note>
</front> </front>
<middle> <middle>
<section anchor="introduction" numbered="true" toc="default"> <section anchor="introduction" numbered="true" toc="default">
<name>Introduction</name> <name>Introduction</name>
<t>Many who participate in the IETF are most comfortable making what we <t>Many who participate in the IETF are most comfortable making what we
believe to be purely technical decisions; our process is defined to believe to be purely technical decisions; our process
favor technical merit, through our well-known mantra of "rough consensus favors technical merit through our well-known mantra of "rough consensus
and running code."</t> and running code."</t>
<t>Nevertheless, the running code that results from our process (when <t>Nevertheless, the running code that results from our process (when
things work well) inevitably has an impact beyond technical things work well) inevitably has an impact beyond technical
considerations, because the underlying decisions afford some uses while considerations, because the underlying decisions afford some uses while
discouraging others. While we believe we are making only technical discouraging others. While we believe we are making only technical
decisions, in reality, we are defining (in some degree) what is possible decisions, in reality, we are defining (in some degree) what is possible
on the Internet itself.</t> on the Internet itself.</t>
<t>This impact has become significant. As the Internet increasingly <t>This impact has become significant. As the Internet increasingly
mediates essential functions in societies, it has unavoidably become mediates essential functions in societies, it has unavoidably become
profoundly political; it has helped people overthrow governments and profoundly political; it has helped people overthrow governments,
revolutionize social orders, swing elections, control populations, revolutionize social orders, swing elections, control populations,
collect data about individuals, and reveal secrets. It has created collect data about individuals, and reveal secrets. It has created
wealth for some individuals and companies while destroying others'.</t> wealth for some individuals and companies while destroying that of others. </t>
<t>All of this raises the question: For whom do we go through the pain <t>All of this raises the question: For whom do we go through the pain
of gathering rough consensus and writing running code?</t> of gathering rough consensus and writing running code?</t>
<t>After all, there are a variety of parties that standards can benefit, s <t>After all, there are a variety of parties that standards can benefit,
uch as (but not limited to) end users, network operators, schools, equipment ven such as (but not limited to) end users, network operators, schools,
dors, specification authors, specification implementers, content owners, governm equipment vendors, specification authors, specification implementers,
ents, non-governmental organisations, social movements, employers, and parents.< content owners, governments, nongovernmental organizations, social
/t> movements, employers, and parents.</t>
<t>Successful specifications will provide some benefit to all of the relev <t>Successful specifications will provide some benefit to all the
ant parties because standards do not represent a zero-sum game. However, there a relevant parties because standards do not represent a zero-sum
re sometimes situations where there is a conflict between the needs of two (or m game. However, there are sometimes situations where there is a conflict
ore) parties.</t> between the needs of two (or more) parties.</t>
<t>In these situations, when one of those parties is an "end user" of the <t>In these situations, when one of those parties is an "end user" of
Internet - for example, a person using a Web browser, mail client, or another ag the Internet -- for example, a person using a web browser, mail client,
ent that connects to the Internet - the Internet Architecture Board argues that or another agent that connects to the Internet -- the Internet
the IETF should favor their interests over those of other parties.</t> Architecture Board argues that the IETF should favor their interests
<t><xref target="who" format="default"/> explains what is meant by "end us over those of other parties.</t>
ers"; <xref target="why" format="default"/> outlines why IETF work should priori <t><xref target="who" format="default"/> explains what is meant by "end
tise them, and <xref target="how" format="default"/> describes how we can do tha users", <xref target="why" format="default"/> outlines why IETF work
t.</t> should prioritize them, and <xref target="how" format="default"/>
describes how we can do that.</t>
</section> </section>
<section anchor="who" numbered="true" toc="default"> <section anchor="who" numbered="true" toc="default">
<name>Who Are "End Users"?</name> <name>Who Are "End Users"?</name>
<t>In this document, "end users," means human users whose activities IETF <t>In this document, "end users" means human users whose activities
standards as a whole are designed to support, sometimes indirectly. Thus, the en IETF standards support, sometimes
d user of a protocol to manage routers is not a router administrator; it is the indirectly. Thus, the end user of a protocol to manage routers is not a
people using the network that the router operates within.</t> router administrator; it is the people using the network that the router
<t>End users are not necessarily a homogenous group; they might have diffe operates within.</t>
rent views of how the Internet should work, and might occupy several roles, such <t>End users are not necessarily a homogenous group; they might have
as a seller, buyer, publisher, reader, service provider and consumer. An end us different views of how the Internet should work and might occupy
er might be browsing the Web, monitoring remote equipment, playing a game, video several roles, such as a seller, buyer, publisher, reader, service
conferencing with colleagues, sending messages to friends, or performing an ope provider, and consumer. An end user might browse the Web, monitor
ration in a remote surgery theatre. They might be "at the keyboard", or represen remote equipment, play a game, videoconference with colleagues,
ted by software indirectly (e.g., as a daemon).</t> send messages to friends, or perform an operation in a remote
<t>Likewise, an individual end user might have many interests (e.g., priva surgery theater. They might be "at the keyboard" or represented by
cy, security, flexibility, reachability) that are sometimes in tension.</t> software indirectly (e.g., as a daemon).</t>
<t>A person whose interests we need to consider might not directly be usin <t>Likewise, an individual end user might have many interests (e.g.,
g a specific system connected to the Internet. For example, if a child is using privacy, security, flexibility, reachability) that are sometimes in
a browser, the interests of that child's parents or guardians may be relevant. A tension.</t>
person pictured in a photograph may have an interest in systems that process th <t>A person whose interests we need to consider might not directly be
at photograph; a person entering a room with sensors that send data to the Inter using a specific system connected to the Internet. For example, if a
net has interests that may be involved in our deliberations about how those sens child is using a browser, the interests of that child's parents or
or readings are handled.</t> guardians may be relevant. A person pictured in a photograph may have an
<t>While such less-direct interactions between people and the Internet may interest in systems that process that photograph; a person entering a
be harder to evaluate, this document's concept of end-user nonetheless includes room with sensors that send data to the Internet may have interests that m
such people.</t> ay
be involved in our deliberations about how those sensor readings are
handled.</t>
<t>While such less-direct interactions between people and the Internet
may be harder to evaluate, this document's concept of "end user"
nonetheless includes such people.</t>
</section> </section>
<section anchor="why" numbered="true" toc="default"> <section anchor="why" numbered="true" toc="default">
<name>Why The IETF Should Prioritise End Users</name> <name>Why the IETF Should Prioritize End Users</name>
<t>Even before the IETF was established, the Internet technical community <t>Even before the IETF was established, the Internet technical
has focused on user needs since at least <xref target="RFC0001" format="default" community has focused on user needs since at least <xref
/>, which stated that "One of our goals must be to stimulate the immediate and e target="RFC0001" format="default"/>, which stated that "One of our goals
asy use by a wide class of users."</t> must be to stimulate the immediate and easy use by a wide class of
<t>And, while we specialise in technical matters, the IETF is not users."</t>
<t>And, while we specialize in technical matters, the IETF is not
neutral about the purpose of its work in developing the Internet; in "A neutral about the purpose of its work in developing the Internet; in "A
Mission Statement for the IETF" <xref target="RFC3935" Mission Statement for the IETF" <xref target="RFC3935"
format="default"/>, the definitions include:</t> format="default"/>, the definitions include:</t>
<blockquote>The IETF community wants the Internet to succeed because we <blockquote>The IETF community wants the Internet to succeed because we
believe that the existence of the Internet, and its influence on economics, believe that the existence of the Internet, and its influence on economics,
communication, and education, will help us to build a better human communication, and education, will help us to build a better human
society.</blockquote> society.</blockquote>
<t>Later in <xref target="RFC3935" sectionFormat="of" section="2.1"/>, <t>Later, in "The Scope of the Internet" (<xref target="RFC3935" sectionFo
"The Scope of the Internet" it says:</t> rmat="of" section="4.1"/>),
it says:</t>
<blockquote>The Internet isn't value-neutral, and neither is the IETF. We want <blockquote>The Internet isn't value-neutral, and neither is the IETF. We want
the Internet to be useful for communities that share our commitment to the Internet to be useful for communities that share our commitment to
openness and fairness. We embrace technical concepts such as decentralized openness and fairness. We embrace technical concepts such as decentralized
control, edge-user empowerment and sharing of resources, because those control, edge-user empowerment and sharing of resources, because those
concepts resonate with the core values of the IETF community. These concepts concepts resonate with the core values of the IETF community. These concepts
have little to do with the technology that's possible, and much to do with the have little to do with the technology that's possible, and much to do with the
technology that we choose to create.</blockquote> technology that we choose to create.</blockquote>
<t>In other words, the IETF develops and maintains
<t>In other words, the IETF is concerned with developing and maintaining t the Internet to promote the social good. The society that the IETF
he Internet to promote the social good, and the society that the IETF is attempt is attempting to enhance is composed of end users, along with groups of
ing to enhance is composed of end users, along with groups of them forming busin them forming businesses, governments, clubs, civil society
esses, governments, clubs, civil society organizations, and other institutions.< organizations, and other institutions.</t>
/t> <t>Merely advancing the measurable success of the Internet (e.g.,
<t>Merely advancing the measurable success of the Internet (e.g., deployme deployment size, bandwidth, latency, number of users) is not an adequate
nt size, bandwidth, latency, number of users) is not an adequate goal; doing so goal; doing so ignores how technology is so often used as a lever to
ignores how technology is so often used as a lever to assert power over users, r assert power over users, rather than empower them.</t>
ather than empower them.</t> <t>Beyond fulfilling the IETF's mission, prioritizing end users can also
<t>Beyond fulfilling the IETF's mission, prioritising end users can also h help to ensure the long-term health of the Internet and the IETF's
elp to ensure the long-term health of the Internet and the IETF's relevance to i relevance to it. Perceptions of capture by vendors or other providers
t. Perceptions of capture by vendors or other providers harm both; the IETF's wo harm both; the IETF's work will (deservedly) lose end users' trust if it
rk will (deservedly) lose end users' trust if it prioritises (or is perceived to prioritizes (or is perceived to prioritize) others' interests over
prioritise) others' interests over them.</t> them.</t>
<t>Ultimately, the Internet will succeed or fail based upon the actions of <t>Ultimately, the Internet will succeed or fail based upon the actions
its end users, because they are the driving force behind its growth to date. No of its end users, because they are the driving force behind its growth
t prioritising them jeopardizes the network effect which the Internet relies upo to date. Not prioritizing them jeopardizes the network effect that the
n to provide so much value.</t> Internet relies upon to provide so much value.</t>
</section> </section>
<section anchor="how" numbered="true" toc="default"> <section anchor="how" numbered="true" toc="default">
<name>How The IETF Can Prioritise End Users</name> <name>How the IETF Can Prioritize End Users</name>
<t>There are a few ways that the IAB believes the IETF community can prior <t>There are a few ways that the IAB believes the IETF community can
itise end users, based upon our observations. By its nature, this is not a compl prioritize end users, based upon our observations. This
ete list.</t> is not a complete list.</t>
<section anchor="engaging-the-internet-community" numbered="true" toc="def ault"> <section anchor="engaging-the-internet-community" numbered="true" toc="def ault">
<name>Engaging the Internet Community</name> <name>Engaging the Internet Community</name>
<t>The IETF community does not have any unique insight into what is "goo <t>The IETF community does not have any unique insight into what is
d for end users," and it is not uncommon for us to be at a further disadvantage "good for end users", and it is not uncommon for us to be at a further
because of our close understanding of some - but not all - aspects of the Intern disadvantage because of our close understanding of some -- but not all
et.</t> -- aspects of the Internet.</t>
<t>At the same time, we do have a culture of considerable deference to a <t>At the same time, we have a culture of considerable deference to
broader "Internet community" - roughly, what this document calls end users - in a broader "Internet community" -- roughly what this document calls end
our decision-making processes. Mere deference, however, is not adequate; even w users -- in our decision-making processes. Mere deference, however, is
ith the best intentions, we cannot assume that our experiences of the Internet a not adequate; even with the best intentions, we cannot assume that our
re those of all of its end users, or that our decisions have a positive impact u experiences of the Internet are those of all of its end users or that
pon them.</t> our decisions have a positive impact upon them.</t>
<t>Therefore, we have not only a responsibility to analyse and consider <t>Therefore, we have not only a responsibility to analyze and
the impacts of the IETF's work, but also a responsibility to consult with that g consider the impacts of the IETF's work, but also a responsibility to
reater Internet community. In particular, we should do so when one of our decisi consult with that greater Internet community. In particular, we should
ons has potential impact upon end users.</t> do so when one of our decisions has a potential impact upon end
<t>The IETF community faces significant hurdles in doing so. Our work is users.</t>
specialised and often esoteric, and processes for developing standards often in <t>The IETF community faces significant hurdles in doing so. Our work
volve very long timescales. Affected parties are rarely technical experts, and t is specialized and often esoteric, and processes for developing
heir experience of the Internet is often based upon incomplete (and sometimes in standards often involve very long timescales. Affected parties are
accurate) models. Often, even when we try to engage a broader audience, their pa rarely technical experts, and they often base their understanding of the
rticipation is minimal - until a change affects someone in a way they don't like Internet
. Surprising the Internet community is rarely a good outcome.</t> upon incomplete (and sometimes inaccurate) models. Often,
<t>Government-sponsored individuals sometimes participate in the IETF co even when we try to engage a broader audience, their participation is
mmunity. While this is welcome, it should not be taken as automatically represen minimal -- until a change affects someone in a way they don't
tative of end users elsewhere, or even all end users in the relevant jurisdictio like. Surprising the Internet community is rarely a good outcome.</t>
n. Furthermore, what is desirable in one jurisdiction (or at least to its admini <t>Government-sponsored individuals sometimes participate in the IETF
strators) might be detrimental in others (see <xref target="conflict" format="de community. While this is welcome, it should not be taken as
fault"/>).</t> automatically representative of end users elsewhere, or even all end
<t>While some civil society organisations specialise in technology and I users in the relevant jurisdiction. Furthermore, what is desirable in
nternet policy, they typically do not have the capacity to participate broadly, one jurisdiction (or at least to its administrators) might be
nor are they necessarily representative of the larger Internet community. Nevert detrimental in others (see <xref target="conflict"
heless, their understanding of end user needs is often profound, and they are in format="default"/>).</t>
many ways the best informed advocates for end user concerns; they should be con <t>While some civil society organizations specialize in technology and
sidered a primary channel for engaging the broader Internet community.</t> Internet policy, they rarely can
<t>A promising approach to help fill these gaps is to identify and engag participate broadly, nor are they necessarily representative of the
e with specifically affected communities when making decisions that might affect larger Internet community. Nevertheless, their understanding of
them; for example, one or more industry associations, user groups, or a set of end-user needs is often profound, and they are in many ways the
individuals, though we can't of course formally ensure that they are appropriate best-informed advocates for end-user concerns; they should be
ly representative.</t> considered a primary channel for engaging the broader Internet
<t>In doing so, we should not require them to "come to us"; unless a st community.</t>
akeholder community is already engaged in the IETF process effectively, the IETF <t>A promising approach to help fill these gaps is to identify and
community should explore how to meet with them on their terms - taking the init engage with specifically affected communities when making decisions
iative to contact them, explain our work, and solicit their feedback.</t> that might affect them, for example, one or more industry
<t>In particular, while IAB workshops, BoFs and Bar BoFs can be an effec associations, user groups, or a set of individuals, though we can't
tive mechanism to gather input within our community, they often do not have the formally ensure that they are appropriately representative.</t>
visibility in other communities that is required to solicit input, much less eff <t>In doing so, we should not require them to "come to us"; unless a
ective participation.</t> stakeholder community is already engaged in the IETF process
<t>Instead, an event like a workshop may be more effective if co-located effectively, the IETF community should explore how to meet with them
with - and ideally hosted or co-hosted by - a forum that's familiar to that sta on their terms -- take the initiative to contact them, explain our
keholder community. We should also take the opportunity to raise the visibility work, and solicit their feedback.</t>
of IETF work (or potential IETF work) in such fora through conference talks, pan <t>In particular, while IAB workshops, BOFs, and Bar BOFs can be an
els, newsletter articles, etc.</t> effective mechanism to gather input within our community, they rarely
<t>For example, the IAB held the ESCAPE workshop <xref target="RFC8752" have the visibility into other communities that is required to
format="default"/> to solicit input from Internet publishers and advertisers tha solicit input, much less effective participation.</t>
t might be affected by a proposal for new work in the IETF. While the workshop w <t>Instead, an event like a workshop may be more effective if
as considered successful, participation might have been improved by identifying co-located with -- and ideally hosted or co-hosted by -- a forum that's
an appropriate industry forum and working with them to host the event.</t> familiar to that stakeholder community. We should also
<t>When we engage with the Internet community, we should also clearly id raise the visibility of IETF work (or potential IETF
entify tailored feedback mechanisms (e.g., subscribing to a mailing list may not work) in such fora through conference talks, panels, newsletter
be appropriate), and assure that they are well-known in those communities.</t> articles, etc.</t>
<t>The Internet Society can be an invaluable partner in these efforts; t <t>For example, the IAB ESCAPE workshop <xref
heir focus on the Internet community, policy expertise and resources can help to target="RFC8752" format="default"/> solicited input from Internet
facilitate discussions with the appropriate parties.</t> publishers and advertisers about a proposal that might affect them.
<t>Finally, we should remember that the RFC series are Requests For Comm While the workshop was considered successful,
ents; if there are serious implications of our work, we should document them and participation might have been improved by identifying an appropriate
ask for feedback from the Internet Community.</t> industry forum and working with them to host the event.</t>
<t>When we engage with the Internet community, we should also clearly
identify tailored feedback mechanisms (e.g., subscribing to a mailing
list may not be appropriate) and assure that they are well known in
those communities.</t>
<t>The Internet Society can be an invaluable partner in these efforts;
their focus on the Internet community, policy expertise, and resources
can help to facilitate discussions with the appropriate parties.</t>
<t>Finally, we should remember that the RFC Series contains Requests For
Comments; if there are serious implications of our work, we should
document them and ask for feedback from the Internet community.</t>
</section> </section>
<section anchor="creating-user-focused-systems" numbered="true" toc="defau lt"> <section anchor="creating-user-focused-systems" numbered="true" toc="defau lt">
<name>Creating User-Focused Systems</name> <name>Creating User-Focused Systems</name>
<t>We should pay particular attention to the kinds of architectures we c <t>We should pay particular attention to the kinds of architectures we
reate, and whether they encourage or discourage an Internet that works for end u create and whether they encourage or discourage an Internet that
sers.</t> works for end users.</t>
<t>For example, one of the most successful Internet applications is the <t>For example, one of the most successful Internet applications is
Web, which uses the HTTP application protocol. One of HTTP's key implementation the Web, which uses the HTTP application protocol. One of HTTP's key
roles is that of the Web browser - called the "user agent" in <xref target="RFC7 implementation roles is that of the web browser -- called the "user
230" format="default"/> and other specifications.</t> agent" in <xref target="RFC7230" format="default"/> and other
<t>User agents act as intermediaries between a service and the end user; specifications.</t>
rather than downloading an executable program from a service that has arbitrary <t>User agents act as intermediaries between a service and the end
access into the users' system, the user agent only allows limited access to dis user; rather than downloading an executable program from a service
play content and run code in a sandboxed environment. Of course, end users are d that has arbitrary access into the users' system, the user agent only
iverse and the ability of a limited number of user agents to properly represent allows limited access to display content and run code in a sandboxed
individual interests is imperfect, but this arrangement is an improvement over t environment. End users are diverse and the ability of a few user
he alternative - the need to completely trust a Web site with all information on agents to represent individual interests properly is imperfect, but
your system to browse it.</t> this arrangement is an improvement over the alternative -- the need to
<t>Defining the user agent role in standards also creates a virtuous cyc trust a website completely with all information on your system to
le; it allows multiple implementations, thereby allowing end users to switch bet browse it.</t>
ween them with relatively low costs (although there are concerns about the compl <t>Defining the user agent role in standards also creates a virtuous
exity of the Web creating barriers to entry for new implementations). This creat cycle; it allows multiple implementations, allowing end users
es an incentive for implementers to carefully consider the users' needs, which o to switch between them with relatively low costs (although there are
ften are reflected back into the defining standards. The resulting ecosystem has concerns about the complexity of the Web creating barriers to entry
many remaining problems, but a distinguished user agent role provides an opport for new implementations). This creates an incentive for implementers
unity to improve it.</t> to consider the users' needs carefully, which are often reflected into
<t>In contrast, the Internet of Things (IoT) has not yet seen the broad the defining standards. The resulting ecosystem has many
adoption of a similar role; many current systems require opaque, vendor-specific remaining problems, but a distinguished user agent role provides an
software or hardware for the user-facing component. Perhaps as a result of this opportunity to improve it.</t>
, that ecosystem and its end users face serious challenges.</t> <t>In contrast, the Internet of Things (IoT) has not yet seen the
broad adoption of a similar role; many current systems require opaque,
vendor-specific software or hardware for the user-facing
component. Perhaps as a result of this, that ecosystem and its end
users face serious challenges.</t>
</section> </section>
<section anchor="identifying-negative-end-user-impact" numbered="true" toc ="default"> <section anchor="identifying-negative-end-user-impact" numbered="true" toc ="default">
<name>Identifying Negative End User Impact</name> <name>Identifying Negative End-User Impact</name>
<t>At its best, our work will unambiguously build a better human society <t>At its best, our work will unambiguously build a better human
. In some cases, we will consciously decide to be neutral and open-ended, allowi society. Sometimes, we will consciously be neutral and
ng the "tussle" among stakeholders to produce a range of results (see <xref targ open-ended, allowing the "tussle" among stakeholders to produce a
et="TUSSLE" format="default"/> for further discussion).</t> range of results (see <xref target="TUSSLE" format="default"/> for
<t>At the very least, however, we must examine our work for negative imp further discussion).</t>
act on end users, and take steps to mitigate it where encountered. In particular <t>At the very least, however, we must examine our work for negative
, when we've identified a conflict between the interests of end users and other impact on end users and take steps to mitigate it where
stakeholders, we should err on the side of protecting end users.</t> encountered. In particular, when we've identified a conflict between
<t>Note that "negative impact on end users" is not defined in this docum the interests of end users and other stakeholders, we should err on
ent; that is something that the relevant body (e.g., Working Group) needs to dis the side of protecting end users.</t>
cuss and come to consensus on. Merely asserting that something is harmful is not <t>Note that "negative impact on end users" is not defined in this
adequate. The converse is also true, though; it's not good practice to avoid id document; that is something that the relevant body (e.g., working
entifying harms, nor is it acceptable to ignore them when brought to our attenti group) needs to discuss and come to consensus on. Merely asserting
on.</t> that something is harmful is not adequate. The converse is also true,
<t>The IAB and IETF have already established a body of guidance for situ though; it's not good practice to avoid identifying harms, nor is it
ations where this sort of conflict is common, including (but not limited to) <xr acceptable to ignore them when brought to our attention.</t>
ef target="RFC7754" format="default"/> on filtering, <xref target="RFC7258" form <t>The IAB and IETF have already established a body of guidance for
at="default"/> and <xref target="RFC7624" format="default"/> on pervasive survei situations where this conflict is common, including (but not
llance, <xref target="RFC7288" format="default"/> on host firewalls, and <xref t limited to) <xref target="RFC7754" format="default"/> on filtering,
arget="RFC6973" format="default"/> regarding privacy considerations.</t> <xref target="RFC7258" format="default"/> and <xref target="RFC7624"
<t>Much of that advice has focused on maintaining the end-to-end propert format="default"/> on pervasive surveillance, <xref target="RFC7288"
ies of a connection <xref target="RFC3724" format="default"/>. This does not mea format="default"/> on host firewalls, and <xref target="RFC6973"
n that our responsibility to end users stops there; decisions might affect them format="default"/> regarding privacy considerations.</t>
in other ways. For example, data collection by various applications even inside <t>Much of that advice has focused on maintaining the end-to-end
otherwise secure connections is a major problem on the Internet today. Also, ina properties of a connection <xref target="RFC3724"
ppropriate concentration of power on the Internet has become a concerning phenom format="default"/>. This does not mean that our responsibility to end
enon - one that protocol design might have some influence upon.</t> users stops there; decisions might affect them in other ways. For
example, data collection by various applications even inside otherwise
secure connections is a major problem on the Internet today. Also,
inappropriate concentration of power on the Internet has become a
concerning phenomenon -- one that protocol design might have some
influence upon.</t>
</section> </section>
<section anchor="conflict" numbered="true" toc="default"> <section anchor="conflict" numbered="true" toc="default">
<name>Handling Conflicting End User Needs</name> <name>Handling Conflicting End-User Needs</name>
<t>When the needs of different end users conflict (for example, two sets <t>When the needs of different end users conflict (for example, two
of end users both have reasonable desires) we again should try to minimise nega sets of end users both have reasonable desires), we again should try to
tive impact.</t> minimize negative impact.</t>
<t>For example, when a decision improves the Internet for end users in o <t>For example, when a decision improves the Internet for end users in
ne jurisdiction, but at the cost of potential harm to others elsewhere, that is one jurisdiction, but at the cost of potential harm to others
not a good tradeoff. As such, we effectively design the Internet for the pessima elsewhere, that is not a good trade-off. As such, we design
l environment; if a user can be harmed, they probably will be, somewhere.</t> the Internet for the pessimal environment; if a user can be harmed,
<t>There may be cases where genuine technical need requires compromise. they probably will be, somewhere.</t>
However, such tradeoffs are carefully examined and avoided when there are altern <t>There may be cases where genuine technical need requires
ate means of achieving the desired goals. If they cannot be, these choices and r compromise. However, such trade-offs are carefully examined and avoided
easoning ought to be thoroughly documented.</t> when there are alternate means of achieving the desired goals. If they
cannot be, these choices and reasoning ought to be thoroughly
documented.</t>
</section> </section>
<section anchor="deprioritising-internal-needs" numbered="true" toc="defau lt"> <section anchor="deprioritising-internal-needs" numbered="true" toc="defau lt">
<name>Deprioritising Internal Needs</name> <name>Deprioritizing Internal Needs</name>
<t>There are a number of needs that are very visible to us as specificat <t>There are several needs that are very visible to us as
ion authors, but should explicitly not be prioritised over the needs of end user specification authors but should explicitly not be prioritized over
s.</t> the needs of end users.</t>
<t>These include: convenience for document editors, IETF process matters <t>These include convenience for document editors, IETF process
, and "architectural purity" for its own sake.</t> matters, and "architectural purity" for its own sake.</t>
</section> </section>
</section> </section>
<section anchor="iana-considerations" numbered="true" toc="default"> <section anchor="iana-considerations" numbered="true" toc="default">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<t>This document does not require action by IANA.</t> <t>This document has no IANA actions.</t>
</section> </section>
<section anchor="security-considerations" numbered="true" toc="default"> <section anchor="security-considerations" numbered="true" toc="default">
<name>Security Considerations</name> <name>Security Considerations</name>
<t>This document does not have any direct security impact; however, failin <t>This document does not have any direct security impact; however,
g to prioritise end users might well affect their security negatively in the lon failing to prioritize end users might well affect their security
g term.</t> negatively in the long term.</t>
</section> </section>
</middle> </middle>
<back> <back>
<references> <references>
<name>Informative References</name> <name>Informative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.0001. xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.0001. xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3724. xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3724. xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3935. xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3935. xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6973. xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6973. xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7230. xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7230. xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7258. xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7258. xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7288. xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7288. xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7624. xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7624. xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7754. xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7754. xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8752. xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8752. xml"/>
<!-- [rfced] [TUSSLE] The URL below is correct --> <reference anchor="TUSSLE" target="https://groups.csail.mit.edu/ana/Public
ations/PubPDFs/Tussle2002.pdf">
<reference anchor="TUSSLE" target="http://groups.csail.mit.edu/ana/Publica
tions/PubPDFs/Tussle2002.pdf">
<front> <front>
<title>Tussle in Cyberspace: Defining Tomorrow's Internet</title> <title>Tussle in Cyberspace: Defining Tomorrow's Internet</title>
<author initials="D." surname="Clark" fullname="David D. Clark"> <author initials="D." surname="Clark" fullname="David D. Clark">
<organization>MIT Lab for Computer Science</organization> <organization>MIT Lab for Computer Science</organization>
</author> </author>
<author initials="K." surname="Sollins" fullname="Karen R. Sollins"> <author initials="K." surname="Sollins" fullname="Karen R. Sollins">
<organization>MIT Lab for Computer Science</organization> <organization>MIT Lab for Computer Science</organization>
</author> </author>
<author initials="J." surname="Wroclawski" fullname="John Wroclawski"> <author initials="J." surname="Wroclawski" fullname="John Wroclawski">
<organization>MIT Lab for Computer Science</organization> <organization>MIT Lab for Computer Science</organization>
</author> </author>
<author initials="R." surname="Braden" fullname="Robert Braden"> <author initials="R." surname="Braden" fullname="Robert Braden">
<organization>USC Information Sciences Institute</organization> <organization>USC Information Sciences Institute</organization>
</author> </author>
<date year="2002"/> <date month="August" year="2002"/>
</front> </front>
<seriesInfo name="DOI" value="10.1145/633025.633059"/>
</reference> </reference>
</references> </references>
<section numbered="false" toc="default">
<name>IAB Members at the Time of Approval</name>
<t>Internet Architecture Board members at the time this document was approved
for publication were:</t>
<ul empty="true" spacing="compact">
<li><t><contact fullname="Jari Arkko"/></t></li>
<li><t><contact fullname="Alissa Cooper"/></t></li>
<li><t><contact fullname="Stephen Farrell"/></t></li>
<li><t><contact fullname="Wes Hardaker"/></t></li>
<li><t><contact fullname="Ted Hardie"/></t></li>
<li><t><contact fullname="Christian Huitema"/></t></li>
<li><t><contact fullname="Zhenbin Li"/></t></li>
<li><t><contact fullname="Erik Nordmark"/></t></li>
<li><t><contact fullname="Mark Nottingham"/></t></li>
<li><t><contact fullname="Melinda Shore"/></t></li>
<li><t><contact fullname="Jeff Tantsura"/></t></li>
<li><t><contact fullname="Martin Thomson"/></t></li>
<li><t><contact fullname="Brian Trammell"/></t></li>
</ul>
</section>
<section numbered="false" anchor="acknowledgements" toc="default"> <section numbered="false" anchor="acknowledgements" toc="default">
<name>Acknowledgements</name> <name>Acknowledgements</name>
<t>This document was influenced by many discussions, both inside and <t>Many discussions influenced this document, both inside and
outside of the IETF and IAB. In particular, <contact fullname="Edward outside of the IETF and IAB. In particular, <contact fullname="Edward
Snowden"/>'s comments regarding the priority of end users at IETF 93 and Snowden"/>'s comments regarding the priority of end users at IETF 93 and
the HTML5 Priority of Constituencies were both influential.</t> the HTML5 Priority of Constituencies were both influential.</t>
<t>Many people gave feedback and input, including <contact <t>Many people gave feedback and input, including <contact
fullname="Harald Alvestrand"/>, <contact fullname="Mohamed Boucadair"/>, fullname="Harald Alvestrand"/>, <contact fullname="Mohamed Boucadair"/>,
<contact fullname="Stephen Farrell"/>, <contact fullname="Joe <contact fullname="Joe
Hildebrand"/>, <contact fullname="Lee Howard"/>, <contact fullname="Russ Hildebrand"/>, <contact fullname="Lee Howard"/>, <contact fullname="Russ
Housley"/>, <contact fullname="Niels ten Oever"/>, <contact Housley"/>, <contact fullname="Niels ten Oever"/>, <contact
fullname="Mando Rachovitsa"/>, <contact fullname="Martin Thomson"/>, fullname="Mando Rachovitsa"/>, <contact fullname="John
<contact fullname="Brian Trammell"/>, <contact fullname="John Klensin"/>, and <contact fullname="Eliot Lear"/>.</t>
Klensin"/>, <contact fullname="Eliot Lear"/>, <contact fullname="Ted
Hardie"/>, and <contact fullname="Jari Arkko"/>.</t>
</section> </section>
</back> </back>
<!-- ##markdown-source:
H4sIABnEZl4AA6Vca5PbxpX9zl+BGn+QpoqkFDuOY81uvKNXJMeSXZpx+cPW
VqoJNMnOAGgaDQxFq/Tf95x7uxsgOc4+kkrZQxJAd9/Huec+4MViMetdX9tn
xe3WFm/b3nat7QsXirXvildtVfwcbBdmlS9b0+CyqjPrfuHMaoELFv3WLgZe
sHj6x1llelzw6eX17avPsxIfNr47PCtcu/azve/uNp0fds/GRa67cut6W/ZD
Z4vn3nRV8fjt9fPL2cztumdF3w2h//Lp02+ffjkLw6pxITjf3h52WASXze7s
AU+tnhWlbwMOMdi2f+jL8jB+29na3pu2L3am650N4y8WR5WTHH2182760NCb
O7v1dWW72Qwf2urvpvYtNnTAs3buWfGfvS/nBf7h2gr7mRfBd31n1wF/HZr4
R9+5Ej+VvtmZ+EeDi/GTa2vX2v+azczQb333bFYsZgX+59rwrHi3LN77vnft
Zmsa+VpV8s50d6e/+G5jWveb6SGyZ/KNbYyrnxVN6/v/4D+WUIH8MHTY97bv
d+HZkyf7/X6Zfn0CRUB3XYOn3Fs+5fbnm5sfXunzetNtbK934kZRbliWAass
G9cvbTU8Ma158tOwql0pGwn88NPL1+HJ7RBCbaHcL5e7aq3PUzO80J9w4uLF
YQV9QET4+qVduxbnK25947vO7x+FbEgXcn+WmPxvEf8dRfdyWbyoIab8rUru
pbl31fmPR8Ir3r29LX4wK3GIF1DZgFWLm9LBsuzDq/1tWdz4GpoMJ+v9zXS2
LT6c//yvrvj9svil82Vt9uHOnSz6vd+2D/36r66JYzzvDKz8ZL0PHmrrT387
Xu3nmxdQX7Qt36aFqFPx2l7XVEShmcxms8ViUZgVnAc+M5vdboFRQKWBnlPY
j7vaYFfFfnsoeiLZ9fNiZWtn7/HQfmvgZfstZI/fADa41RAh1rDMHtf1e6u/
4WQ4tw19KPx6xAR+6Kf4CM8vPJ+VgGRevH11+7qobOmIUqEIWz/UVbE2937o
xicti7e4uw5etuyxVLH1ezwcWypNW8C4bWHXa6AifK4+YHOFAUziHNUyCgHu
af/+nv/o/d8/WIgZqDUjfgMiBzyxdqEXRcpjBbHl4XjW2g/YiumLf0sev3H9
dlgtgUFPcHgDTF4Rip8cwfsTffJflrpO47FAZ0uK/rFf97adF0O7o6eHra0u
45oU82Sl6eOXcVnnTxbiEh/0yeXWtBscB04jR7L/n40TW10fnjQGD+j49Btr
VQPUqGwUWFIOXcc1Aer9EIg+om/RqcF3MLo7282xgVnewOSHpbP9egkbfwKT
fPI7MVLORgU2rqpqO5t9QYPqfDWUdILZ7J1pDzBTr0ZVuh3M/2grlITIHqfC
o3uzAlI25o7AuIeRF3ubrB4xiPreIbbCihBlty1QuB4t9KqgYe6ACzYEqqoi
xELGuJFW201uamzn4EH9FiC/2cqNe1vXi7vW72GzCKidoY9c6O+MvbYNkCP9
pBtaQe7SV3Z5MZu9x+46HKnGunM52/QKcVbYVhhqOOG6883RPh9HL8blcHaQ
CtnIJaRk7x3lcSi2husWToIrZHDw2MR4Fm7OwWU0Is1xQWmgHtkIfMN29YF7
GT3ZrCHqCoG8sfRhYoyD2CsXSuzMbHi1YAGc+xf5aaIF/ClKUx359mFdMPDj
zKZ2/WGe7qlSyHuMH2X1ym46ay9V1dDYzoMS0QR8ewxPMHhbr5cRJaMkKBcc
lg8KbtO6NfbQ9sviOpzc3JbYSsDK2GxjKwcrDAWED/9w2PV6aMVexUsCmI5V
AHS6xNDCeFwlqojLQXmCO/hm53FGHv4qXQ9D2MHqdtbveBKxDcT3YsM/W+FF
akb23tcDF3a/WVkXe4FiIHdQqj0FBZMqo1ahZXhWjfV2Q23ylzWvEI9GKPED
D1s5cIABgDBPy0APRbAQQq9wzV1SJASgPX7stwKuopLJ/XK7cLrWjVaCWNL5
w2gjj6CV67rWiALldMYFqxr4FQir4fE1Hg8caBDgaA0bn12P1+0Q6Xj/xvCJ
fPRDbreHy8pvE+f6DmuvGdhNXc9jLKSpmeLedNDjgY+NEU0dUUguUDXEANLC
KMlqh3JbQCyPV5Ah4hHwGSgr4HE5Brt5AXsSJ/U7OpwXVZVb7ylt++vgdhK9
73GH/raDR6wjW4yM7uxrmHNteZ+sQEXzGQAi+TwxGyzv28X4hdgLWUhIBhGt
qMEl8Q6Lh/uDPIlC3JGwwQwQNYaSALQe6uPtQNEO6oSJwwysGkUUE5HUJFXb
s9wjI88oY6ibwuzsDgDIU5niN9v5RRgaaLuxy+KN3xM+p8rjkr1r8MAA5pQ2
JT//T2yntbZScrP3COSd0I/LtEGc+q1cxz3mR0cihaxHD+aDzSdygrwXyQAu
zngTgh9dx340VCJkDL/vApQ6EG/w8Re7KlZw/8AzMmMpSgApEyncZlrlXGZD
2Yh94lgtXDpQ1qcrHX1+INlEAjMkO88hdsLbyJ+s66acEKKPR8bJjggghPXp
E3z28+cpGVWcbizVvjqMkgkXVwUvP+BywBCTPuWusgdxmbiRXec8PVkjVKNm
+ekTSCNuBbqUnVtFEgmkoJNWXo5EtvgFApLH0W1xkVP5i++KT19wo1G7Exo9
n2xwfiHbxpMHxPdIg/dydENu6kThKrJsv4y8vKhOEYyBRilFGHY7MJb5xFyJ
nSCRfX1YFrfbIZKBtANK2NCvkEwDyPEI7AOaJ9jR9SlYOouJXxSmahAvmR8A
aCS8OMXVGFrUxNTsFZWy5uMTFKWoCUeGAQm+yhkAz8PlYG2AAaAlgpmB2BsP
Y/TAXEmAr/g4RE232TJu3JMmgMwLtbx3di/OpoR/YptR1dyT6lfv92U57A4I
RbA6oBTCGcNsgl6DHxDO4Car4cB/JfqNPztJCnCt7e5daRM6dTFEIUaA0SHy
t6O0dUkwRvG+JCm4I9wQIRcilWBiG+QdI3Rj1doc1HUJUPOC63hBG566FGYK
aWrsNXQ4bguaxw8NJUmGT8qJ+NNWQfwcamBqKI9to1YE+VtqW7cQhm5jO0n2
QMItLSgLHqe4iJq9swfJCi7kwRlYYZNwx4DUZU/FjpZYPLbLzXKuAq4M1mov
YQc/uDu7hw/OhVnmmH8qPtF4QxY/YkZ8IPz43pQHHh65hvC8dW0/upVT0geV
Id/RT5dqmcfgzjwA0R1yIINIuKkeOa62V1CnRBPRjXuj8eZTrmxG3BTNinBA
htQkRNVnTM10KbQkQ7ejewJTYbjws/S0jN1nybTCNa9HuhXjKnWyGaAeR6Rp
jGwsxUnYZzrlzgluV2oBuy0wYdOZ3VZuEaGLWnQ1oaVylojtKXfQD/nmqzH6
CJnQA3QetEssllwK9CPyIGpaeONpoCE7HA8qF8eDuBaM9V53zRymQk6wSolH
5J+KBdShLieuK8kNtY8EGIkiE39NLMT3mTctVJO6sIl0PEX2iHf09aOdxm1t
DUkzzwEx14jqdn4cBpgO+7a0uz4WQSR9JZmyMW1jjlAPFSkHd6QLpoBz0FIy
I8ONAttPYwzLYUiC0AFB6BXYH7a19spXYgQ0zDiYz0lBYX58kGky1zQD0Emz
vjUOECBvr/Eq0htYJiAQagH+wDo+ffruw+sXT58+/cPnz+QyDgdg1k+Dp/Iu
flRmQ41tPHl9MwTBFEYx+CLzCd2qa2J6JLLG0w9cl8iCKEg2WNYmiPFr7QfJ
73VbzWNqAFcV30PWFzTNH/Nt0yu7zQKJwa61Q89YoMYjwW3odpGPuD6mxHhW
haBR+13C8SS6K/52cV2802J6ccODCwfXcpGudhGF9NW3X31NIUmhRLLRlPeJ
9p/NZn8ZdT2qYm/a/iSnFAIAAk3cjax3WqpIcRh4CL+luk6Io4ZFHtCBxg56
CfwWduobV4Z5Wl5JuV5uqyF9FI7OTBOakMrIQNwydBkGfuU4msseCPeG30JU
N5pQFl8u/wByxLPelIhHp9u7INsI5hBGkYydlPYRYj8czS6i9nR3rXXCHyNJ
oQyXiLcivTPhCV5bJh/UUxL1mKVtiRa0WC13iUZxG7YKMA+aEK6N6/hBVrHN
Crhhj+sidPmQCUYlVTjsF/l2lRJqZEjVRutZzJWQjXSyGBfgLiTRXbN+g92U
9qi+QjPNq/CKlq4jWMvzlkQAEdRYbz0yLInx02cI8iNg9rU4J5Pl9DA5l6/9
5iASejQWSyLD4iH/+T3Cp5GrBnm4FgA0JVLiz5bQiYvKzjoyXnnoxAllTcM6
pdZ0ThWMGCW0ht/HrHTjfTXPKB6N8yRbkQorPHgnqT4hvUXMKK1upiEyVEeV
bDyw9omTac8mCrspEudaMZiz3nOaTsPrV/wX2E+dNzQt7MesWeXjYimf30Nu
76xUIk2F2F4mESDFAJGTMmbQBPssZYz8qbJMzMXWAgwSdoWVALL9dl4QkFty
q3ZoVpo5yGEvc44A2lCBtNLeiOlX0Du3EHyBBGWswo8GgBvxo5S2C4kpQghr
e6+RE7DOHofYv2aFUbqd1GSopTb5hwgXAniulUg48dqx+7PJaoR1xu7mfMz3
pKCV0w8mdlK0FhATRYchRkwqdAFpNfhRqlMPdSsma0WCVYpdO/Csn2xHhxJs
x72l2UmWjDgWKzPkaTHbjZkEnQ8LrvDt1fTZWpIl2j4GPUD6YasafLamF+XT
PNLeLimk6ycZbpAaBAub3JC7Vw46/n6ZamjnKblI+Oca4Rk6rg8nhEE2lAIQ
llizsLAy1Ouwi8XTxKJiIJ14zKRCfBBapo0DeAFUBKcpGcmQL2qAglPte8UW
AgYbs8dKFV/7BygTee9vsfaXUlJt/URacnSGjsEyxP36ScFJsUyAUynYG5hy
DssvYDi/w79YQ5B+Tq4Cru0e8ecwrYkc99HOYj3tclKimEptFC8Dk1/RGhQl
lsXzg8gKAQCGFulnzucJXLXttemDI33xBba90UL7kUhepG1oV+pka5W3+sSY
IICcte7XgVQrSEYEI/K5RnNBuNXi1KQEoqwjbW1o+XQciJdFIiHMEpIbOvGP
ygVBuJ6VimQ4kU2W4gXSY5CSSYyVUjJcLIpUSmXJkK1OksP+DA+Z/KlqAvLt
grmhdAwQyPScRTnU4r705NTrWEkpWlNycXvJ1FgkKC6yOLPoLri+1JTpSXu1
hWm7FXyhnrgIL885jrY0FrHjEXMvC50zAIybmBNxtZSZFB8R+gp5CVA3h+WV
5nSs8sb6o9S55JbASoZaq7RZPwI5Yif5DAS7xEFYWNKy7ImjCwWOjxr7P1Gs
iKWOPdnUTknA0SyjDzGDkc3JDdyetHtYsQg7KkKTe5F+a+pDsLkcI2m6ZhR8
9hH/iaA6F/uQEPDQE6WoU/dJajjERghLV5yrd4nvYosRuUwne44lKFhR8EcF
3lNZkEj1sRM0lcTY4X7QGdemlAJ17juBc3fIbaWukYLxsvhx6GIKEybJUaWs
QoIxaCNz9TLW55N5iUtO+NZYk9TbYi6OgNYdJGCK5wQYMk3zWlDXVrmQTWPp
zEnrVKyrD5mTuanBndmbS0tPgNC1GdseC2OeVHdMWQ6sPl4Wja9sjV39qI11
9QaqBHrqu4NG/w0BZvRiM1RO3Uo3NnaQpXBGgtEiNgqyDNBeLcUb9tfZ3xSg
4WaodKmxIApovKs885fa3SGU3SDX7HIQe8CyCmloKc8T/sriNluAMIq/Zia5
EOP1Ws8Z22ejMH6v/T2xYK2HpLixtzVXkR5ktGT6H3N2cwfBkbwNveewCaHr
MBYCZbTpeNYDsrfSPhFAEOkTLsYL4pZyP+cfA4RSOeEPy+K1RoJG0SBGF1bC
FYWdetb0HmE9uT4hnCwcV7PBZHNls7J952I7y8VcBMQpWIusPXV5Pn++HItG
jC8PcfbYBnuoCqEkmCaalczObanECqZx2EVJxpaVYJ5kcQaYEEFpqkcxVIaT
loftIpuaVtPPdSLklmNmD6PY2SAB7P4suuYKrRaDslemnnT2ZqV2rtX6bWRB
OfowNyIOVfe+lBbBlCmkvC/E8n80wZXN4M5byZMaA/+l37W2jo+YEJvkzA8c
Vkq+yBHV+8wOfxvNYCUhYEYRO3Ubs5Nj0o44gujWqsgIGVraTB1MatAk8JuW
FQRvYgwf4V+rm2KJepcEwKvjnp4EDm0l0r9B9HFmRGpmtTGCi9A0+9TGXhGs
FBuP2vGI1mxra7h/1CuhGbpgJVOVvecsSOmq6lCkA2FLJnBiVprAp4AzDX3a
eP11cGqbDQVYXMj8Av4a2LEbWil+mukc6DH4mZr120MUdnWEXqkMPZnumj+A
bWk/cT5ME1OQfGtzdMfmlHs4Dul0jRCwXpWldXcoUb1IqUFvoqrmqTmpMzy5
4RTo3K6Pz1zDVVamvFNhHTEFQRQmBbwXO6UCn/vXWmF6bjr9EIfNmAOnw+IA
tHsXRLA6uoCN7oY+dtty+UqkEHFGffUUY+5dpj4JAc9rYgxFqk7tP8YTypJz
zZnqI3Ucx0w5e+ihTen5MAxoGGRwjGdPFfXjoT2mtaVf1AIUsRJEPs9UorJi
tqChvWaiuDB+QLbNq2jbQ5OKVmvT4Jym066DzmOcW55U9KLZ6GQbLhJJeWm6
ql3hETJscipCuNXYdWYoGgle/v5SmiqUGbZnijSNktt8DLT1HWxhZ4BsMvix
D7UWV0Wq0rq0fQmxHnWRUo4JFNMaxaubF9c/vRpF/OnTd28XL5ccpiNd29kF
HBpn+vz5TKs6LTYGrNQPVeMEdCNaOIngExxb2REApXBP7PDBKDy3TIhjSX1S
pY3kw47bZMNiAvYhT4vMT6jYpFG4YrMGHBqZvC6e8Do2Pic4NgKpmocM+GDt
3F5NiEVj0lI6DVY4gBLHKfw/TN6mYChWBKWZrh63BR27WmhbAojRqXOfMwwr
mUmI9UgjQxz8IEOpdJjIzCanu1QQYjZ3BuaTOUPRgRaRs6+nbCOd5iYynBGB
wPzZ5SL3oiZaLexrrLQc7es1bBP32D86G6abCEg5UEwEXEzgcq1bFk31OSQ8
dC/qjpOCQwhxWCjKf6rccYTkNfKAuj5SRWcbK1XNXJP58PoFO/spT/lgZXAs
SHv2RXyV4Ioo1I8zQricQwqcncqDSzG70ygwzQFjli82pYq5E2/IahdHe7gU
IyWoL4oXzD6pdhabFq9jY+5G27KwyrzaDhYxRhipZkuen/qsMHEdUTKTAR7p
c2tFXk0HdCXWXS2Drw5mCg3JY5piDGPJXQr89N7jms8pPuUxpzh4Ozr2pLKw
mwg1tnNkcEKreEOa73tze/vT9OI83IJUT5fhFUD9OxwiT7nppTL8oQ83fdrR
ZFiKsYN0ziqKXgjDkjmpC5q79vO++fKrp8DNsUR/PMnGCmq+LbAgWqTetvQ5
Ox1a0yazycMlqbqcZHh1VASv4Lm1l562xNGPthx0bhmn33SmUWMaHycHlBne
buWQ/pA8amdA6nVcKRaRtck/z1/FuTCtutQ15JLHEuMTWJR1gSMreW4wTijr
7LGkvgFfrfxHS8p87zovOSuz8cg+55NUUKacEPO7MMrBjHHV5A0cdyaSiLWO
u+PM8WTobzJfMta5dY7XdgxVWguS5Nd0HZN48VeX5p67OM+Yi+MQB21VKWGc
jBvHRLQiwVKHVOV1CC+41Jtj8usm72rg/wfiRpwXYRFUbJCthNksv6hzohUa
sJCIcVhMYow4MTk1RN0PxKjygMAj81tRic1Q944TDcc+EeIQ5Cpq+7hhQnKA
7cP/JgOPcbIDmbuJr1fgPkhA5nTYOkkzthE2U1436beruD5GBScvLBPcraAQ
F9dn9/SQacTJ5i/ZzXRhFIBUh4h995LfHI25ip6wIcBOfTiuGEZfkOw2IY6y
Zqlh2XUduQ1xO3tQni3P6pDmapy7F0lCKqpg+qLkxB1fIWtjVRce3IRYlKRT
8aZBhjXOtB5bFUGHuY4IaTRWNZ23rXaZTehP+jeQ9K2O/D9+628vZUukEQcO
z6VhVsmeQfP8Ts2U7hfgfgwr3MeVniK/6RFHhFLO53cGcXQeW16LcSwqDYlB
Jxydkb/TtASPumColwHrZodw0WpDbcs0XJqGKtM08D1XgBvFmwYbRtNlrTRH
bPAroDrfg4mR9e2EJL63G/Xp1NYp3kpJVnoEfCirF/Mc5bUPNrSmWbkNfY2T
YP9sEoKFYi0fGekG760+ghZYOn0AqwNVet0kz6cwxOxsu8CpOL6THVSCUy+v
+F0UpvFqgimlSYhYDYwrhUBbHCeQ10FilUtfQ0QkE1Iydl4iy7oceyRa7rVi
UbnfgFPISA+DvGvtKB511SjSWNyelrZjrYjJFVS3k90C3t1GGHofh66Ffghu
V+eVdmXjj/h81aOT0tD/5V20SfieSG7K4GzXJRZLoJChflANpqdTjISY3uvM
Acee/tnBL1KPJr0j5E4mh69yzi1V3K2qOk3XpkLpyld5wPKXmL38lVWgy1id
0/hMNaaXKVIFI77YwAJrGiSQFnxeaFzXaW+aFO2ks6QYh6dpwHYxBiHs2VRt
Ytx5pHdJ/Xon03WxZ8b3Wo6SNK4TtKTJ+NwLz9gpvenTbEEMPNT8StJmHc0Z
JmQ3ZTFIhKXmyrRb206pnjTOwtFXKUe+ADK4Svr48jrK+fC/qKOLhbNoYDoY
0nDUQMe45A2jh17jiJzxm6//yCH1ljVGnZKcZzr59Z8jnYxf/OnLeO2Ovd5A
a0JKd2+BGUaaE+nGP/9Zr5N0dQ343bOjOJ8860/ffvMVrulglV2lMUcGaE/e
3+JgyVBu84Apsnxq62Qa8HTyhjONvSc4Rf4lZSOJGHH8lREkDsF9w0PFaJ17
ypyNH5uF5/240V1D73dBOcXVpJR6VkUdS1msPZ8M28rkaXx9iVvjaIbRAHGU
fUi3wrXq9XwYh5Z15NhOjqZvakAs//BdCuZneW/vK4MQcF2zToq8dJKwCi9i
pE6RNg7CnDxh8saZSVxKVAlfwJctrgcZZYqV5nR11l/fG5iWSuK7Vmn0j820
GA7fcESWD30RLZx/53D4XmDl0xe5LxILIokAi9LHEf3JvE3yl8dHtW2+JxPs
KSJzCkb3yRfnfBvb7QF2HS7ldb4NS64RnWMLTxpy1M4J8J5moAIcJltOokwn
A5ZHSexDTaZI1RKJDb2qLVX6ZJqHsKTtpEkPLAG7zmYIKPZ8tduv1/LuIKuC
Enymby1HDZ5tsZfXMRClGxmez+nVlY6TazNFSzfcUZz8PYiNyhuFQj9WVl8j
kR2m9nsqxgpViRAIDjowwo89XMl6IuXTETlpqkzfrJIyZzqipngj946cQTvS
EhBsNX2zXPoPMdmy8Q0a4oq8wp3gR02j0vFicIS1HjIONay0LBpk+tCVNr3+
SMuSplYKISsZaIhzGjkU63vi8IyX9mjsSPUAEYhPHM/9jNlpjMPp9QPhT1Ir
rmMbhJz2d17To4FNmhcszNa53DcOCVVjWppd8GR6QDqROmOs4brVHrs0+fM7
/5XTNwqPuit5dJpCu5gUjXDynbx4caHpFZ14D6cEhdKxqbfX76+JIpPocvqf
Gcjwn5IGk+GYd3NWiSPDssz/9lF5OimO9Kf3QyIcXI28dR0rqUczcROvV7xk
wXQSV1w3PjEhTX1I9WydhLBdk/7bAkwTeYrrkjXXmsO+Uk+cfXqmRmKrf79Y
w2ztxefTI+3NZDxbCtqNniuXP+cKlTFACZEd+kRRcytMKND18zPy/Iq5V1Xc
YGPgYI9C/u+mTFiCAIwK53BCm3t9+rdf5UrNm9t3P3ydpuPk8hfjfzVGuqB0
kbhlORexchlf1I+vWWyov1wZlWxOW0wjvXpjYH0VIuk93wY2bDq/81vDhvJz
P5SmMg7Hu0FKQSB5bZCg8v3c7z22iOzMrvSeH5D8AKVw0nnxgRz5DTMwe5gX
7x0Am68HFT+qqWCDlS8+AHaQevfB8BuSZbAY3wRGg+eI5PjYGYhQF9u2xd9q
vmGEX1/VDqb5g6XYb7HNNxRvrLV+D+JRXHd3d345+2//Y85KQEgAAA==
</rfc> </rfc>
 End of changes. 32 change blocks. 
421 lines changed or deleted 286 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/