rfc9245.original   rfc9245.txt 
Network Working Group L. Eggert Network Working Group L. Eggert
Internet-Draft NetApp Internet-Draft NetApp
Obsoletes: 3005 (if approved) 24 February 2022 Obsoletes: 3005 (if approved) 7 April 2022
Updates: 3683 (if approved) Updates: 3683 (if approved)
Intended status: Best Current Practice Intended status: Best Current Practice
Expires: 28 August 2022 Expires: 9 October 2022
IETF Discussion List Charter IETF Discussion List Charter
draft-eggert-bcp45bis-08 draft-eggert-bcp45bis-08
Abstract Abstract
The Internet Engineering Task Force (IETF) discussion mailing list The Internet Engineering Task Force (IETF) discussion mailing list
furthers the development and specification of Internet technology furthers the development and specification of Internet technology
through the general discussion of technical, procedural, operational through the general discussion of technical, procedural, operational,
and other topics for which no dedicated mailing lists exists. As and other topics for which no dedicated mailing lists exist. As this
this is the most general IETF mailing list, considerable latitude in is the most general IETF mailing list, considerable latitude in terms
terms of topics is allowed, but there are posts and topics that are of topics is allowed, but there are posts and topics that are
unsuitable for this mailing list. This document defines the charter unsuitable for this mailing list. This document defines the charter
for the IETF discussion list and explains its scope. for the IETF discussion list and explains its scope.
This document obsoletes RFC3005 and updates RFC3683. This document obsoletes RFC 3005 and updates RFC 3683.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 28 August 2022. This Internet-Draft will expire on 9 October 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 28 skipping to change at page 2, line 28
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Charter for the IETF Discussion List . . . . . . . . . . . . 3 2. Charter for the IETF Discussion List . . . . . . . . . . . . 3
3. Moderation . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Moderation . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 6 6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 6 6.2. Informative References . . . . . . . . . . . . . . . . . 5
Appendix A. Changes . . . . . . . . . . . . . . . . . . . . . . 7 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 7
A.1. Since draft-eggert-bcp45bis-08 . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
A.2. Since draft-eggert-bcp45bis-07 . . . . . . . . . . . . . 8
A.3. Since draft-eggert-bcp45bis-06 . . . . . . . . . . . . . 8
A.4. Since draft-eggert-bcp45bis-05 . . . . . . . . . . . . . 8
A.5. Since draft-eggert-bcp45bis-04 . . . . . . . . . . . . . 8
A.6. Since draft-eggert-bcp45bis-03 . . . . . . . . . . . . . 9
A.7. Since draft-eggert-bcp45bis-02 . . . . . . . . . . . . . 9
A.8. Since draft-eggert-bcp45bis-01 . . . . . . . . . . . . . 9
A.9. Since draft-eggert-bcp45bis-00 . . . . . . . . . . . . . 9
A.10. Since RFC3005 . . . . . . . . . . . . . . . . . . . . . . 9
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
The IETF discussion list [IETF-DISCUSS] furthers the development and The IETF discussion list [IETF-DISCUSS] furthers the development and
specification of Internet technology through the general discussion specification of Internet technology through the general discussion
of technical, procedural, operational and other topics for which no of technical, procedural, operational and other topics for which no
dedicated mailing lists exists. As this is the most general IETF dedicated mailing lists exist. As this is the most general IETF
mailing list, considerable latitude in terms of topics is allowed. mailing list, considerable latitude in terms of topics is allowed.
However, there are posts and topics that are unsuitable for this However, there are posts and topics that are unsuitable for this
mailing list. This document defines the charter for the IETF mailing list. This document defines the charter for the IETF
discussion list and explains its scope. discussion list and explains its scope.
The IETF Note Well [NOTE-WELL] applies to discussions on the IETF The IETF Note Well [NOTE-WELL] applies to discussions on the IETF
discussion list and all other IETF mailing lists, and requires discussion list and all other IETF mailing lists, and requires
conformance with the IETF Guidelines for Conduct [RFC7154] and the conformance with the IETF Guidelines for Conduct [RFC7154] and the
Anti-Harassment Policy [RFC7776], among others. Anti-Harassment Policy [RFC7776], among others.
This document obsoletes [RFC3005], documenting the use of other This document obsoletes [RFC3005], as it documents the use of other
mailing lists for discussions that used to be in scope for the IETF mailing lists for discussions that were previously in scope for the
discussion list, referring to applicable policies such as the IETF discussion list, refers to applicable policies such as the
Guidelines for Conduct [RFC7154] and the Anti-Harassment Policy Guidelines for Conduct [RFC7154] and the Anti-Harassment Policy
[RFC7776], and clarifying moderation procedures. It also updates [RFC7776], and clarifies moderation procedures. It also updates part
part of Section 1 of [RFC3683], which copies the list of of Section 1 of [RFC3683], which copies the list of "inappropriate
"inappropriate postings" from [RFC3005]. This list in [RFC3683] is postings" from [RFC3005]. The list in [RFC3683] is hence updated by
hence updated by the new list in Section 2 below. the new list in Section 2.
2. Charter for the IETF Discussion List 2. Charter for the IETF Discussion List
The IETF discussion list is meant for discussions for which a more The IETF discussion list is meant for discussions for which a more
appropriate list does not exist, such as discussions that do not fall appropriate list does not exist, such as discussions that do not fall
within the scope of any working group, area, or other established within the scope of any working group, area, or other established
list. When discussions are started on the IETF discussion list for list. When discussions are started on the IETF discussion list for
which such a venue does exist, they should be continued at that other which such a venue does exist, they should be continued at that other
venue as soon as this is pointed out. venue as soon as this is pointed out.
When no dedicated mailing list exists for a topic, it may be When no dedicated mailing list exists for a topic, it may be
preferable to request the creation of one [NON-WG-LISTS] and announce preferable to request that one be created [NON-WG-LISTS] and announce
the availability of the new list on the IETF discussion list and on the availability of the new list on the IETF discussion list and
other related lists, such as area lists, rather than discussing that other related lists, such as area lists, rather than discussing that
topic on the IETF discussion list. topic on the IETF discussion list.
Appropriate postings to the IETF discussion list include: Appropriate postings to the IETF discussion list include:
* Initial discussion of technical issues that are candidates for * Initial discussion of technical issues that are candidates for
IETF work, but have not yet identified appropriate mailing lists. IETF work, but appropriate mailing lists have not yet been
identified.
* Questions and clarifications concerning practical aspects of IETF * Questions and clarifications concerning practical aspects of IETF
meetings, although most of these topics are better brought up on meetings, although most of these topics are better brought up on
the discussion list for IETF LLC administrative issues the discussion list for IETF LLC administrative issues
[ADMIN-DISCUSS] or the attendee discussion list for a given IETF [ADMIN-DISCUSS] or the attendee discussion list for a given IETF
meeting. meeting.
* Announcements of conferences, events, or activities that are * Announcements of conferences, events, or activities that are
sponsored or endorsed by the IETF, IRTF, IAB or the Internet sponsored or endorsed by the IETF, IRTF, IAB or the Internet
Society, although the IETF announcement list [IETF-ANNOUNCE] is Society, although the IETF announcement list [IETF-ANNOUNCE] is
skipping to change at page 5, line 12 skipping to change at page 4, line 42
* Announcements of conferences, events, or activities that are not * Announcements of conferences, events, or activities that are not
sponsored or endorsed by the Internet Society or the IETF. sponsored or endorsed by the Internet Society or the IETF.
3. Moderation 3. Moderation
The IETF Chair appoints _Moderators_ (previously known as the The IETF Chair appoints _Moderators_ (previously known as the
"sergeant-at-arms") for the IETF discussion list that are empowered "sergeant-at-arms") for the IETF discussion list that are empowered
to restrict posting by a person, or to an email thread, when the to restrict posting by a person, or to an email thread, when the
content is inappropriate and represents a pattern of abuse. They are content is inappropriate and represents a pattern of abuse. They are
encouraged to take into account the overall nature of the postings by encouraged to take into account the overall nature of the postings by
an individual and whether particular postings are an aberration or an individual and whether particular postings are typical or an
typical. aberration.
Moderation of the IETF discussion list, including the handling of any Moderation of the IETF discussion list, including the handling of any
appeals, is to be guided by the IETF discussion list charter appeals, is guided by the IETF discussion list charter specified in
specified in Section 2, and the related guidance from Section 1 that Section 2, and the related guidance from Section 1 that applies to
applies to all mailing lists. The moderators are intended to all mailing lists. The moderators are intended to establish a self-
establish a self-moderation function on the community, by the moderation function on the community, by the community. Because the
community. Because the IESG and IAB are in the appeals chain for IESG and IAB are in the appeals chain for moderator decisions (see
moderator decisions (see below), the IETF Chair therefore should not below), the IETF Chair therefore should not appoint a moderator who
appoint a moderator who is serving in such a role. If a moderator is is serving in such a role. If a moderator is selected for the IESG
selected for the IESG or IAB, they will step down from the moderator or IAB, they will step down from the moderator team.
team.
Apart from appointing moderators, the IETF Chair should refrain from Apart from appointing moderators, the IETF Chair should refrain from
the day-to-day operation and management of the moderator team. The the day-to-day operation and management of the moderator team. The
moderator team will independently define, publish, and execute their moderator team will independently define, publish, and execute their
role; see the current set of operating procedures [MOD-SOP] and abuse role; see the current set of operating procedures [MOD-SOP] and abuse
patterns [MOD-UPC]. The moderator team should reach out to the IETF patterns [MOD-UPC]. The moderator team should reach out to the IETF
Chair for any conflict resolution in a timely manner. Chair for any conflict resolution in a timely manner.
Because a moderator serves at the discretion of the IETF Chair - even Because a moderator serves at the discretion of the IETF Chair --
if the IETF Chair is not otherwise involved in the operation of the even if the IETF Chair is not otherwise involved in the operation of
moderator team - any moderator decision can be appealed to the IETF the moderator team -- any moderator decision can be appealed to the
Chair, per [RFC2026]. Decisions by the IETF Chair can be appealed to IETF Chair, per [RFC2026]. Decisions by the IETF Chair can be
the IESG as whole, again per [RFC2026]. appealed to the IESG as whole, again per [RFC2026].
4. Security Considerations 4. Security Considerations
The usual security considerations [RFC3552] do not apply to this The usual security considerations [RFC3552] do not apply to this
document. document.
Potential abuse of the moderation process for the suppression of Potential abuse of the moderation process for the suppression of
undesired opinions is counteracted by the availability of an appeals undesired opinions is counteracted by the availability of an appeals
process, per Section 3. process, per Section 3.
skipping to change at page 6, line 4 skipping to change at page 5, line 42
Potential abuse of the moderation process for the suppression of Potential abuse of the moderation process for the suppression of
undesired opinions is counteracted by the availability of an appeals undesired opinions is counteracted by the availability of an appeals
process, per Section 3. process, per Section 3.
5. IANA Considerations 5. IANA Considerations
This document does not request any IANA actions. This document does not request any IANA actions.
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
<https://www.rfc-editor.org/rfc/rfc2026>. <https://www.rfc-editor.org/info/rfc2026>.
6.2. Informative References 6.2. Informative References
[ADMIN-DISCUSS] [ADMIN-DISCUSS]
IETF, "Discussion List for IETF LLC Administrative IETF, "admin-discuss -- Discussion list for IETF LLC
Issues", 20 October 2021, administrative issues", n.d.,
<https://ietf.org/mailman/listinfo/admin-discuss>. <https://ietf.org/mailman/listinfo/admin-discuss>.
[ARCH-DISCUSS] [ARCH-DISCUSS]
IAB, "Open Discussion Forum For Long/Wide-Range IAB, "Architecture-discuss -- open discussion forum for
Architectural Issues", 20 October 2021, long/wide-range architectural issues", n.d.,
<https://ietf.org/mailman/listinfo/architecture-discuss>. <https://ietf.org/mailman/listinfo/architecture-discuss>.
[IETF-ANNOUNCE] [IETF-ANNOUNCE]
IETF, "IETF Announcement List", 20 October 2021, IETF, "IETF-Announce -- IETF announcement list. No
discussions.", n.d.,
<https://ietf.org/mailman/listinfo/ietf-announce>. <https://ietf.org/mailman/listinfo/ietf-announce>.
[IETF-DISCUSS] [IETF-DISCUSS]
IETF, "IETF Discussion List", 20 October 2021, IETF, "ietf -- IETF-Discussion", n.d.,
<https://ietf.org/mailman/listinfo/ietf>. <https://ietf.org/mailman/listinfo/ietf>.
[LAST-CALLS] [LAST-CALLS]
IETF, "IETF Last Calls", 20 October 2021, IETF, "last-call -- IETF Last Calls", n.d.,
<https://ietf.org/mailman/listinfo/last-call>. <https://ietf.org/mailman/listinfo/last-call>.
[MOD-SOP] IETF Discussion List Moderator Team, "IETF Discussion List [MOD-SOP] IETF, "Sergeant-at-Arms Standard Operating Procedures",
Moderator Team Standard Operating Procedures", 20 October commit c1abcb0 , 9 October 2019,
2021, <https://github.com/ietf/saa/blob/main/sop.md>. <https://github.com/ietf/saa/blob/main/sop.md>.
[MOD-UPC] IETF Discussion List Moderator Team, "Unprofessional [MOD-UPC] IETF, "Unprofessional commentary", commit e120305 , 8
Commentary", 20 October 2021, October 2019, <https://github.com/ietf/saa/blob/main/
<https://github.com/ietf/saa/blob/main/unprofessional- unprofessional-commentary.md>.
commentary.md>.
[NON-WG-LISTS] [NON-WG-LISTS]
IETF, "Non-Working Group Email List Guidelines", 20 IETF, "Non-Working Group Email List Guidelines", n.d.,
October 2021,
<https://ietf.org/how/lists/nonwglist-guidelines/>. <https://ietf.org/how/lists/nonwglist-guidelines/>.
[NOTE-WELL] [NOTE-WELL]
IETF, "Note Well", 20 October 2021, IETF, "Note Well", n.d.,
<https://ietf.org/about/note-well/>. <https://ietf.org/about/note-well/>.
[RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45, [RFC3005] Harris, S., "IETF Discussion List Charter", BCP 45,
RFC 3005, DOI 10.17487/RFC3005, November 2000, RFC 3005, DOI 10.17487/RFC3005, November 2000,
<https://www.rfc-editor.org/rfc/rfc3005>. <https://www.rfc-editor.org/info/rfc3005>.
[RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC
Text on Security Considerations", BCP 72, RFC 3552, Text on Security Considerations", BCP 72, RFC 3552,
DOI 10.17487/RFC3552, July 2003, DOI 10.17487/RFC3552, July 2003,
<https://www.rfc-editor.org/rfc/rfc3552>. <https://www.rfc-editor.org/info/rfc3552>.
[RFC3683] Rose, M., "A Practice for Revoking Posting Rights to IETF [RFC3683] Rose, M., "A Practice for Revoking Posting Rights to IETF
Mailing Lists", BCP 83, RFC 3683, DOI 10.17487/RFC3683, Mailing Lists", BCP 83, RFC 3683, DOI 10.17487/RFC3683,
March 2004, <https://www.rfc-editor.org/rfc/rfc3683>. March 2004, <https://www.rfc-editor.org/info/rfc3683>.
[RFC7154] Moonesamy, S., Ed., "IETF Guidelines for Conduct", BCP 54, [RFC7154] Moonesamy, S., Ed., "IETF Guidelines for Conduct", BCP 54,
RFC 7154, DOI 10.17487/RFC7154, March 2014, RFC 7154, DOI 10.17487/RFC7154, March 2014,
<https://www.rfc-editor.org/rfc/rfc7154>. <https://www.rfc-editor.org/info/rfc7154>.
[RFC7776] Resnick, P. and A. Farrel, "IETF Anti-Harassment [RFC7776] Resnick, P. and A. Farrel, "IETF Anti-Harassment
Procedures", BCP 25, RFC 7776, DOI 10.17487/RFC7776, March Procedures", BCP 25, RFC 7776, DOI 10.17487/RFC7776, March
2016, <https://www.rfc-editor.org/rfc/rfc7776>. 2016, <https://www.rfc-editor.org/info/rfc7776>.
Appendix A. Changes
| RFC Editor: Please remove this appendix before publication.
A.1. Since draft-eggert-bcp45bis-08
* Update [RFC3683], because it copies text from [RFC3005] that this
document updates. See this issue
(https://github.com/larseggert/bcp45bis/issues/11).
* addressed Eric Vyncke's IESG review
(https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/
ballot/#draft-eggert-bcp45bis_eric-vyncke)
* addressed Francesca Palombini's IESG review
(https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/
ballot/#draft-eggert-bcp45bis_francesca-palombini) and Carsten
Bormann's ART ART review
(https://mailarchive.ietf.org/arch/msg/art/ZnkYEl-
9mRWfKXtzHVUu7u92QB0/)
* addressed John Scudder's IESG review
(https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/
ballot/#draft-eggert-bcp45bis_john-scudder)
* addressed Roman Danyliw's IESG review
(https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/
ballot/#draft-eggert-bcp45bis_roman-danyliw)
* addressed Ben Kaduk's IESG review
(https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/
ballot/#draft-eggert-bcp45bis_benjamin-kaduk)
A.2. Since draft-eggert-bcp45bis-07
* incorporated suggestions from Adrian Farrel
(https://mailarchive.ietf.org/arch/msg/last-call/
bt79VpEeM4iAiFVD5vtxHAa_kdc)
* incorporated some suggestions from S Moonesamy
(https://mailarchive.ietf.org/arch/msg/last-call/
xQoWLovElvnS80ZPgHquAwJs3Mw)
* applied suggestions from Robert Wilton
(https://mailarchive.ietf.org/arch/msg/last-call/
qCC0p5Yow7AOQLo8T3862jPl4i0)
A.3. Since draft-eggert-bcp45bis-06
* applied a suggestion from Lloyd Wood
(https://mailarchive.ietf.org/arch/msg/ietf/
jVF496BFjekl9eVx1q9sqDIqOCs) to add access dates to cited URLs
* fixes to this change log
* applied a suggestion from Brian Carpenter to change
"unprofessional" to "uncivil"
A.4. Since draft-eggert-bcp45bis-05
* clarification of list scope as suggested by Brian Carpenter
(https://github.com/larseggert/bcp45bis/pull/10)
A.5. Since draft-eggert-bcp45bis-04
* use RFC2026 appeals process
(https://github.com/larseggert/bcp45bis/pull/7)
* addressed comments from Barry Leiba
(https://github.com/larseggert/bcp45bis/pull/6)
* quote cited text from Wikipedia
A.6. Since draft-eggert-bcp45bis-03
* addressed Robert Wilton's AD review
(https://github.com/larseggert/bcp45bis/pull/5)
A.7. Since draft-eggert-bcp45bis-02
* additional details about and guidelines for the SAA team, based on
a suggestion from Dhruv Dhody
(https://github.com/larseggert/bcp45bis/pull/1)
* remove reference to the IETF 110 attendees list, since those lists
are being removed by the secretariat shortly after each meeting
A.8. Since draft-eggert-bcp45bis-01
* applied a suggestion from Brian Carpenter
(https://mailarchive.ietf.org/arch/msg/gendispatch/-
U2LWKf0VonKnQXs4jPEqIg_L_A)
* rephrased beginning of Section 2, as suggested by Stephen Farrell
(https://mailarchive.ietf.org/arch/msg/gendispatch/p73lu-
D-WvQrbKBZ80c2T7bbBlQ/)
* incorporated a suggestion from Christian Huitema
(https://mailarchive.ietf.org/arch/msg/
gendispatch/64LgqlIk0h62mAK09Muqn1ccqRE/)
A.9. Since draft-eggert-bcp45bis-00
* added introduction, security considerations and IANA
considerations sections
* added "note to readers" with pointers to the discussion list and
the repo
* added references to IETF Sergeants-at-Arms procedures
* added references to various mailing lists for topics that used to
be in scope for the IETF discussion list but no longer are
* added references to the Note Well and relevant other policies that
apply
A.10. Since RFC3005
* converted to Markdown and xml2rfc v3
* updated references (as part of the conversion)
* updated author information
* various formatting changes
Acknowledgements Acknowledgements
The following people have made contributions to this document: The following people have made contributions to this document:
* Adrian Farrel * Adrian Farrel
* Barry Leiba * Barry Leiba
* Ben Kaduk * Ben Kaduk
 End of changes. 32 change blocks. 
201 lines changed or deleted 64 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/

mirror server hosted at Truenetwork, Russian Federation.