From nobody Fri Oct 13 01:57:11 2017
Return-Path: <lists@digitaldissidents.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71FB513306C for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 01:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level: 
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wC0UoLdkQvqS for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 01:57:08 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78CDF133052 for <xml2rfc@ietf.org>; Fri, 13 Oct 2017 01:57:07 -0700 (PDT)
Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <lists@digitaldissidents.org>) id 1e2vmD-0000rn-E3 for xml2rfc@ietf.org; Fri, 13 Oct 2017 10:57:05 +0200
To: xml2rfc@ietf.org
From: Niels ten Oever <lists@digitaldissidents.org>
Message-ID: <873da473-9a22-9465-84f9-66ded9a738e7@digitaldissidents.org>
Date: Fri, 13 Oct 2017 10:57:04 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Authenticated-As-Hash: 29cc722430e8f1f6ed904119444c0d49b0f3ee91
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 1f72ff50073f138f9668c095d6f579a1
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/9EUthieDdviTdbwKAei4UH24p_o>
Subject: [xml2rfc] dependency error
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Oct 2017 08:57:10 -0000

Hi all,

Not sure whether I should file this bug here or in the debian
bugtracker, but I thought I'd first try it here.

Am running make on my Debian Testing instance and getting the following:


$ make
kramdown-rfc2629 draft-association.md > association.staging.xml
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not
find 'kramdown' (~> 1.14.0) - did find: [kramdown-1.15.0] (Gem::LoadError)
Checked in
'GEM_PATH=/home/lem/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
execute `gem env` for more information
	from /usr/lib/ruby/2.3.0/rubygems/dependency.rb:328:in `to_spec'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:65:in `gem'
	from /usr/lib/ruby/vendor_ruby/kramdown-rfc2629.rb:14:in `<top (required)>'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in
`require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in
`rescue in require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:40:in
`require'
	from /usr/bin/kramdown-rfc2629:3:in `<main>'
Makefile:14: recipe for target 'draft-association.xml' failed
make: *** [draft-association.xml] Error 1

Seems like kramdown-rfc2629 is dependent on kramdown 1.14.0 whereas the
newest version is 1.15.0. I think that is something that should be fixed
in the kramdown-rfc2629 and then pushed downstream.

But happy to be told otherwise!

Cheers,

Niels


-- 
Niels ten Oever
Head of Digital

Article 19
www.article19.org

PGP fingerprint    8D9F C567 BEE4 A431 56C4
                     678B 08B5 A0F2 636D 68E9


From nobody Fri Oct 13 05:17:35 2017
Return-Path: <lists@digitaldissidents.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13C7E13239C for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 05:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HbbU_-V1vcgB for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 05:17:27 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78E24132705 for <xml2rfc@ietf.org>; Fri, 13 Oct 2017 05:17:26 -0700 (PDT)
Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <lists@digitaldissidents.org>) id 1e2yu0-0000Y4-NX for xml2rfc@ietf.org; Fri, 13 Oct 2017 14:17:24 +0200
To: xml2rfc@ietf.org
References: <873da473-9a22-9465-84f9-66ded9a738e7@digitaldissidents.org>
From: Niels ten Oever <lists@digitaldissidents.org>
Message-ID: <2768c8d6-dd7f-36a9-8cc8-920a943c49cb@digitaldissidents.org>
Date: Fri, 13 Oct 2017 14:17:19 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <873da473-9a22-9465-84f9-66ded9a738e7@digitaldissidents.org>
Content-Type: multipart/mixed; boundary="------------F6E5B592470291DAE44A5F33"
Content-Language: en-US
X-Authenticated-As-Hash: 29cc722430e8f1f6ed904119444c0d49b0f3ee91
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: eb2d2b8108261ba9a4ab915a0067ef44
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/wRnQZr01No9M5LG23lEcHJbn7UA>
Subject: Re: [xml2rfc] dependency error
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Oct 2017 12:17:33 -0000

This is a multi-part message in MIME format.
--------------F6E5B592470291DAE44A5F33
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hmmm, just changing :


gem 'kramdown', '~> 1.14.0'

to:

gem 'kramdown', '~> 1.15.0'

in kramdown-rfc2629.rb did also not really yield the result I was hoping
for:

$ make
kramdown-rfc2629 draft-association.md > association.staging.xml
*** Input contains HT ("tab") characters. Undefined behavior will ensue.
** Configuration problem with OpenSSL certificate store at
/usr/lib/ssl/cert.pem.
**   workaround using 'certified' gem disabled on Debian.
/usr/lib/ruby/2.3.0/psych.rb:379:in `parse': (<unknown>): could not find
expected ':' while scanning a simple key at line 268 column 6
(Psych::SyntaxError)
	from /usr/lib/ruby/2.3.0/psych.rb:379:in `parse_stream'
	from /usr/lib/ruby/2.3.0/psych.rb:327:in `parse'
	from /usr/lib/ruby/2.3.0/psych.rb:293:in `safe_load'
	from /usr/bin/kramdown-rfc2629:44:in `xml_from_sections'
	from /usr/bin/kramdown-rfc2629:264:in `<main>'
Makefile:14: recipe for target 'draft-association.xml' failed
make: *** [draft-association.xml] Error 1

:((

Cheers,

Niels

PS Attached the markdown file I am trying to convert.

On 10/13/2017 10:57 AM, Niels ten Oever wrote:
> Hi all,
> 
> Not sure whether I should file this bug here or in the debian
> bugtracker, but I thought I'd first try it here.
> 
> Am running make on my Debian Testing instance and getting the following:
> 
> 
> $ make
> kramdown-rfc2629 draft-association.md > association.staging.xml
> /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not
> find 'kramdown' (~> 1.14.0) - did find: [kramdown-1.15.0] (Gem::LoadError)
> Checked in
> 'GEM_PATH=/home/lem/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
> execute `gem env` for more information
> 	from /usr/lib/ruby/2.3.0/rubygems/dependency.rb:328:in `to_spec'
> 	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:65:in `gem'
> 	from /usr/lib/ruby/vendor_ruby/kramdown-rfc2629.rb:14:in `<top (required)>'
> 	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in
> `require'
> 	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in
> `rescue in require'
> 	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:40:in
> `require'
> 	from /usr/bin/kramdown-rfc2629:3:in `<main>'
> Makefile:14: recipe for target 'draft-association.xml' failed
> make: *** [draft-association.xml] Error 1
> 
> Seems like kramdown-rfc2629 is dependent on kramdown 1.14.0 whereas the
> newest version is 1.15.0. I think that is something that should be fixed
> in the kramdown-rfc2629 and then pushed downstream.
> 
> But happy to be told otherwise!
> 
> Cheers,
> 
> Niels
> 
> 

-- 
Niels ten Oever
Head of Digital

Article 19
www.article19.org

PGP fingerprint    8D9F C567 BEE4 A431 56C4
                     678B 08B5 A0F2 636D 68E9

--------------F6E5B592470291DAE44A5F33
Content-Type: text/markdown;
 name="draft-association.md"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="draft-association.md"

---=20
title: Freedom of Association on the Internet
abbrev: FoA
docname: draft-tenoever-hrpc-association-02
category: info

ipr: trust200902
area: IRTF
workgroup: Human Rights Protocol Considerations Research Group
keyword: Internet-Draft
stand_alone: yes
pi:
  rfcedstyle: yes
  toc: yes
  tocindent: yes
  sortrefs: yes
  symrefs: yes
  strict: yes
  comments: yes
  inline: yes
  text-list-symbols: -o*+
 =20
author:

-
       ins: N. ten Oever
       name: Niels ten Oever
       organization: ARTICLE 19
       email: niels@article19.org

-
       ins: G. Perez de Acha
       name: Gisela Perez de Acha
       organization: Derechos Digitales
       email: gisela@derechosdigitales.org

normative:

informative:=20
   RFC0001:
   RFC0155:=20
   RFC1211:
   RFC1287:
   RFC3233:
   RFC1958:
   RFC4084:
   RFC4949:
   RFC5694:
   RFC6176:
   RFC6973:
   RFC7118:
   RFC7858:

   UDHR:
     title: The Universal Declaration of Human Rights
     date: 1948
     author:
        - org: United Nations General Assembly
     target:  http://www.un.org/en/documents/udhr/

   ICCPR:
     title: International Covenant on Civil and Political Rights
     date: 1966
     author:
        - org: United Nations General Assembly
     target: http://www.ohchr.org/EN/ProfessionalInterest/Pages/CCPR.aspx=


   Tocqueville:
     title: Democracy in America
     author:
        - ins: A. de Tocqueville
     target: http://classiques.uqac.ca/classiques/De_tocqueville_alexis/d=
emocracy_in_america_historical_critical_ed/democracy_in_america_vol_2.pdf=
 p. 304

   Abibil:
     title: Dissecting 'Operation Ababil' - an OSINT Analysis
     date: 2012
     author:
        - ins: D. Danchev
     target: http://ddanchev.blogspot.be/2012/09/dissecting-operation-aba=
bil-osint.html

   GreenMovement:
     title: Iran DDoS
     date: 2009
     author:
        - ins: N. Villeneuve
     target: https://www.nartv.org/2009/06/16/iran-ddos/

   BCP72:
     title: Guidelines for Writing RFC Text on Security Considerations
     date: 2003
     author:=20
        - org: IETF
     target: https://datatracker.ietf.org/doc/bcp72/

   HussainHoward:
     title: "What Best Explains Successful Protest Cascades? ICTs and the=
 Fuzzy Causes of the Arab Spring"
     date: 2013
     author:
        - ins: M.M. Hussain
        - ins: P.N. Howard
     target: https://doi.org/10.1111/misr.12020
     seriesinfo: "Int Stud Rev (2013) 15 (1): 48-66."

   UNHRC:
     title: Report of the Special Rapporteur on the rights to freedom of =
peaceful assembly and of association=20
     date: 2012
     author:
        - ins: Maina Kiai
     target: http://freeassembly.net/wp-content/uploads/2013/10/A-HRC-20-=
27_en-annual-report-May-2012.pdf
     seriesinfo: A/HRC/20/27
     =20
   APC:
     title: Freedom of assembly and association online in India, Malaysia=
  and Pakistan. Trends, challenges and recommendations.
     date: 2016
     author:
        - org: Association for Progressive Communications
        - ins: Gayathry Venkiteswaran=20
     target: https://www.apc.org/es/system/files/FOAA_online_IndiaMalaysi=
aPakistan.pdf

   Swire:
     title: "Social Networks, Privacy, and Freedom of Association: Data E=
mpowerment vs. Data Protection"
     date: 2012
     author:
        - ins: Peter Swire
     target: https://ssrn.com/abstract=3D1989516 or http://dx.doi.org/10.=
2139/ssrn.1989516
     seriesinfo: "North Carolina Law Review (2012) 90 (1): 104."

   ARTICLE19:
     title: "The Right to Protest Principles: Background Paper"
     date: 2016
     author:
        - org: ARTICLE 19
     target: https://www.article19.org/data/files/medialibrary/38581/Prot=
est-Background-paper-Final-April-2016.pdf page 7

   UNGA:
     title: Human rights defenders
     date: 2004
     author:
        - ins: Hina Jilani
     target: http://www.un.org/en/ga/search/view_doc.asp?symbol=3DA/59/40=
1 para. 46
     seriesinfo: A/59/401
    =20
   HafnerandLyon:
     title: Where Wizards Stay Up Late. The Origins of the Internet
     date: 1998
     author:
        - ins: K. Hafnerand
        - ins: M. Lyon
     target: https://doi.org/10.1111/misr.12020
     seriesinfo: "First Touchstone Edition (1998): 93."
  =20
   Pensado:
     title: Student Activism. Utopian Dreams.
     date: 2012
     author:
        - ins: Jaime Pensado
     target: http://revista.drclas.harvard.edu/book/student-activism
     seriesinfo: "ReVista. Harvard Review of Latin America (2012)."
    =20
   Abbate:
     title: Inventing the Internet
     date: 2013
     author:
        - ins: Janet Abbate
     target: https://mitpress.mit.edu/books/inventing-internet
     seriesinfo: "Cambridge: MIT Press (2013): 11."

   Pariser:
      title: "The Filter Bubble: How the New Personalized Web Is Changing=
 What We Read and How We Think"
      date: 2012
      author:=20
        - ins: E. Pariser
      seriesinfo: Peguin Books, London.

   Melucci:
      title: The Process of Collective Identity
      date: 1995
      author:
        - ins: A. Melucci
      seriesinfo: Temple University Press, Philadelphia

   AckermannKargerZhang:
      title: "Mailing Lists: Why Are They Still Here, What=E2=80=99s Wron=
g With Them, and How Can We Fix Them?"=20
      date: 2017
      author:
        - ins: M. S. Ackerman
        - ins: D. R. Karger
        - ins: A. X. Zhang
      target: https://people.csail.mit.edu/axz/papers/mailinglists.pdf
      seriesinfo: "Mit. edu (2017): 1."

   Marcus:
      title: "Commercial Speech on the Internet: Spam and the first amend=
ment"
      date: 1998
      author:=20
        - ins: J. A. Marcus
      target: http://www.cardozoaelj.com/wp-content/uploads/2013/02/Marcu=
s.pdf
#      seriesinfo: "Cardozo Arts & Entertainment"

   Benkler:
      title: Peer Production and Cooperation
      date: 2009
      author:
        - ins: Y. Benkler
      target: http://www.benkler.org/Peer%20production%20and%20cooperatio=
n%2009.pdf
#      seriesinfo: "M. Bauer & M. Latzer (eds.), Handbook on the Economic=
s of the Internet, Cheltenham and Northampton, Edward Elgar."

   AndersonGuarnieri:
      title: "Fictitious Profiles and WebRTC's Privacy Leaks Used to Iden=
tify Iranian Activists"
      date: 2016
      author:
        - ins: C. Anderson
        - ins: C. Guarnieri
      target: https://iranthreats.github.io/resources/webrtc-deanonymizat=
ion/

   OSCE:
      title: Guidelines on Freedom of Peaceful Assembly=20
      date: 2010
      author:
         - org: OSCE Office for Democratic Institutions and Human Rights
      target: https://www.osce.org/odihr/73405?download=3Dtrue
      seriesinfo: page 24

   Abibil:
     title: Dissecting 'Operation Ababil' - an OSINT Analysis
     date: 2012
     author:
        - ins: D. Danchev
     target: http://ddanchev.blogspot.be/2012/09/dissecting-operation-aba=
bil-osint.html

   GreenMovement:
     title: Iran DDoS
     date: 2009
     author:
        - ins: N. Villeneuve
     target: https://www.nartv.org/2009/06/16/iran-ddos/

   NelsonHedlun:
     title: "A Network of Peers: Models Through the History of the Intern=
et"
     date: 2001
     author:
        - ins: N. Minar
        - ins: M. Hedlun
     target: "http://library.uniteddiversity.coop/REconomy_Resource_Pack/=
More_Inspirational_Videos_and_Useful_Info/Peer_to_Peer-Harnessing_the_Pow=
er_of_Disruptive_Technologies.pdf"
     seriesinfo: "Peer to Peer: Harnessing the Power of Disruptive Techno=
logies, ed: Andy Oram"

   Vu:
     title: "Peer-to-Peer Computing: Principles and Applications"
     date: 2010
     author:
        - ins: Vu, Quang Hieu
        - ins: Lupu, Mihai
        - ins: Ooi, Beng Chin=20
     target: "https://www.springer.com/cn/book/9783642035135"

   Star:
     title: The Ethnography of Infrastructure
     date: 1999
     author:
        - ins: S.L. Star
     target: http://journals.sagepub.com/doi/abs/10.1177/0002764992195532=
6
     seriesinfo: American Behavioral Scientist, Volume 43 (3), 377-391.

   Schleuder:
     title: Schleuder - A gpg-enabled mailinglist with remailing-capabili=
ties.
     author:
        - org: Nadir
     date 2017
     target: https://schleuder.nadir.org/

   Crawford:
     title: "The WebRTC VPN =E2=80=9CBug=E2=80=9D and How to Fix"
     date: 2015
     author:=20
        - ins: D. Crawford
    target: https://www.bestvpn.com/the-webrtc-vpn-bug-and-how-to-fix-it/=


   RPZ:
     title: DNS Response Policy Zones (RPZ)
     date: 2017
     author:
        - ins: P. Vixie
        - ins: V. Schyver
     target: https://tools.ietf.org/html/draft-ietf-dnsop-dns-rpz-00

--- abstract

This document aims to scope the relation between Internet protocols and t=
he right to freedom of assembly and association. The Internet increasingl=
y mediates our lives and our ability to excercise human rights. Since Int=
ernet protocols play a central role in the management, development and us=
e of the Internet, the relation between protocols and the aforementioned =
rights should be documented and adverse impacts should be mitigated. As t=
here have been methods of protest on the Internet -a form of freedom of a=
ssembly- that have proven to be harmful to connectivity and infrastructur=
e, such as DDoS attacks, this text aims to document forms of protest, ass=
ociation and assembly that do not have a negative impact on the Internet =
infrastructure.

--- middle


Introduction
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The right to freedom of assembly and association protects collective expr=
ession, in turn, systems and protocols than enable communal communication=
 between people and servers allow these rights to prosper. The Internet i=
tself was originally designed as "a medium of communication for machines =
that share resources with each other as equals" {{NelsonHedlun}}, the Int=
ernet thus forms a basic infrastructure for the right freedom of assembly=
 and association.=20

The manner in which communication is designed and implemented impacts the=
 ways in which rights can be excercised. For instance a decentralized and=
 resilient architecture that protects anonimity and privacy, offers a str=
ong protection for the exercise of such freedoms in the online environmen=
t. At the same time, centralized solutions have enabled people to group t=
ogether in recognizable places and helped the visbility of groups.=20

draft-irtf-hrpc-research established the relationship between human right=
s and Internet protocols, and it provides guidelines for considerations o=
n the human rights impact of protocols.=20

This draft aims to take continue the work started in draft-irtf-hrpc-rese=
arch by investigating the exact impact of Internet protocols on a specifi=
c human rights, namely the right to freedom of assembly and association g=
iven their importance for the Internet, in order to mitigate (potential) =
negative impacts.=20


Vocabulary used=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Anonymity
: The condition of an identity being unknown or concealed. {{RFC4949}}

Censorship resistance
: Methods and measures to mitigate Internet censorship.

Connectivity
: The extent to which a device or network is able to reach other devices =
or networks to exchange data. The Internet is the tool for providing glob=
al connectivity {{RFC1958}}. Different types of connectivity are further =
specified in {{RFC4084}}. The combination of the end-to-end principle, in=
teroperability, distributed architecture, resilience, reliability and rob=
ustness are the enabling factors that result in connectivity to and on th=
e Internet.
=09
Decentralization
: Implementation or deployment of standards, protocols or systems without=
 one single point of control.

Pseudonymity=20
: The ability to disguise one's identity online with a different name tha=
n the "real" one, allowing for diverse degrees of disguised identity and =
privacy. It is strengthened when less personal data can be linked to the =
pseudonym; when the same pseudonym is used less often and across fewer co=
ntexts; and when independently chosen pseudonyms are more frequently used=
 for new actions (making them, from an observer's or attacker's perspecti=
ve, unlinkable)."  {{RFC6973}}


Research questions
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

1. How does the internet architecture enable and/or inhibit freedom of as=
sociation and assembly?

2. Is the Internet an assembly or association? Should it be protected as =
such?=20


Methodology
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

In order to answer the research questions, first a number of cases have b=
een collected to analyze where Internet infrastructure and protocols have=
 either enabled or inhibited groups of people to collaborate, cooperate o=
r communicate. This overview does not aim to cover all possible ways in w=
hich people can collectively organize or reach out to each other using In=
ternet infrastructure and Internet protocols, but rather cover typical us=
es in an effort of doing an ethnography of infrastructure {{Star}}. Subse=
quently we analyze the cases with the theoretical framework provided in t=
he literature review and provide recommendations based on the findings.

The scope of this research is open protocols and architectures developed =
in the IETF, thus closed and centralized Internet platforms such as Faceb=
ook do not fall within the scope of this research.

Literature Review
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The right to freedom of assembly and association protects and enables col=
lective action and expression {{UDHR}} {{ICCPR}}. These rights ensures ev=
eryone in a society has the opportunity to express the opinions they hold=
 in common with others, which in turn facilitates dialogue among citizens=
, as well as with political leaders or governments {{OSCE}}. This is rele=
vant because in the process of democratic delibration, causes and opinion=
s are more widely heard when a group of people come together behind the s=
ame cause or issue {{Tocqueville}}.=20

In international law, the right to freedom of assembly and association pr=
otects any collective, gathered either permanently or temporarily for "pe=
aceful" purposes. We will later expand on the definitions and limits of "=
peacefulness" within these rights. For now it is important to underline t=
he propery of "freedom" because the rights to freedom of association and =
assembly is voluntary and uncoerced: anyone can join or leave a group of =
choice, which in turn means on should not be forced to either join, stay =
or leave.

The difference between freedom of assembly and freedom of association is =
merely gradual one: the former tends to have an informal and ephemeral na=
ture, whereas the latter refers to established and permanent bodies with =
specific objectives. Nonetheless, one and the other are protected to the =
same degree.

An assembly is an intentional and temporary gathering of a collective in =
a private or public space for a specific purpose: demonstrations, indoor =
meetings, strikes, processions, rallies or even sits-in {{UNHRC}}. The ri=
ght to protest is a conglomerate of various rights, and the right to asse=
mbly is one of them. Nonetheless protest, unlike assembly, involves an el=
ement of dissent that can be exercised individually whereas assembly alwa=
ys has a collective component {{ARTICLE19}}. Association on the other han=
d has a more formal and established nature. It refers to a group of indiv=
iduals or legal entities brought together in order to collectively act, e=
xpress, pursue or defend a field of common interests {{UNGA}}. Within thi=
s category we can think about civil society organizations, clubs, coopera=
tives, NGOs, religious associations, political parties, trade unions or f=
oundations.

The right to freedom of assembly and association is crucial for the Inter=
net, even if privacy and freedom of expression are the most discussed hum=
an rights when it comes to the online world. The IETF itself, defined as =
a 'open global community' of network designers, operators, vendors, and r=
esearchers, is also protected by freedom of assembly and association {{RF=
C3233}}. Discussions, comments and consensus around RFCs are possible bec=
ause of the collective expression that freedom of association and assembl=
y allow. The very word =E2=80=9Cprotocol=E2=80=9D found its way into the =
language of computer networking based on the need for collective agreemen=
t among network users {{HafnerandLyon}}.=20

The Internet is increasingly being used as a platform for protest. Digita=
l technologies play an important role "by helping individuals and groups =
to organise and plan effectively and quickly, respond to certain events, =
or document and report on protests "{{ARTICLE19}}. According to Hussain a=
nd Howard the Internet helped to "build solidarity networks and identific=
ation of collective identities and goals", facilitate protest, "extend th=
e range of local coverage to international broadcast networks" and as pla=
tform for contestation for the future of "the future of civil society and=
 information infrastructure" {{HussainHoward}}.=20

Protests are no longer limited to public physical spaces: squares, street=
s or parks. Technology "makes it possible for people to 'gather' in onlin=
e spaces and engage in new forms of 'virtual' protest" {{AARTICLE19}}. On=
line association and assembly are crucial to mobilise groups and people w=
here physical gatherings have been impossible or dangerous {{APC}}. Throu=
ghout the world -from the Arab Spring to Latin American student movements=
- the Internet has also played a crucial role by providing a means for th=
e fast dissemination of information that was otherwise mediated by broadc=
ast media, or even forbidden by the government {{Pensado}}.=20

We are aware that some of these examples go beyond the use of Internet pr=
otocols and flow over into the applications layer or examples in the offl=
ine world whereas the purpose of the following document is to break down =
the relationship between Internet protocols and the right to freedom of a=
ssembly and association. Nonetheless, given that protocols are a part of =
the socio-technical ordering of the world, we do recognize that in some c=
ases the line between them and applications, implementations, policies an=
d offline realities are often blurried and hard (if not impossible) to di=
fferentiate.


Cases and examples
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The Internet has become a central mediator for collective action and coll=
aboration. This means the Internet has become a strong enabler of the rig=
hts to freedom of association and assembly.=20

Here we will discuss different cases to bring out the characteristics and=
 consequences of different protocols, technologies and architectural feat=
ures. This issue is particularly timely since an increasing trend of cent=
ralization and consolidation on the Internet can be observed. This trend =
can be parallely observed on the application level, among Content Distrib=
ution Networks, hosting providers, as well as Internet access providers. =
Through the discussion of specific case we will try to further understand=
 how this impact freedom of assembly, freedom of association as well as t=
he distributed nature of the Internet {{RFC1287}}.

## Communicating

The ability to produce, receive and spread information is an essential pr=
e-requisite for discussing and organizing. Protocols that enable private,=
 open, collaborative and non-excluding communication models are the best =
fitted to foster and enable assembly and association rights.=20

### Mailing Lists

Since the beginning of the Internet mailing lists have been a key site of=
 assembly and association {{RFC0155}} {{RFC1211}}. In fact, mailing lists=
 were one of the Internet's first functionalities {{HafnerandLyon}}.

In 1971, four years after the invention of email, the first mailing list =
was created to talk about the idea of using Arpanet for discussion. By th=
is time, what had initially propelled the Arpanet project forward as a re=
source sharing platform was gradually replaced by the idea of a network a=
s a means of bringing people together {{Abbate}}. More than 45 years afte=
r, mailing lists are pervasive and help communities to engage, have discu=
ssion, share  information, ask questions, and build ties. Even as social =
media and discussion forums grew, mailing lists continue to be widely use=
d {{AckermannKargerZhang}}. They are a crucial tool to organise groups an=
d individuals around themes and causes {{APC}}.

Mailinglist are still in wide use, also in the IETF because they allow fo=
r easy association and allow people to subscribe (join) and unsubscribe (=
leave) as they please. They also allow for association of specific groups=
 on closed lists. Finally the archival function allows for accountabilty.=
 The downsides of mailinglists are similar to the ones generally associat=
ed with e-mail, except that end-to-end encryption such as OpenPGP {{RFC48=
80}} and S/MIME {{RFC5751}} is not possible because the final recipients =
are not known. There have been expirimental solutions to address this iss=
ues such as Schleuder {{Schleuder}}, but this has not been standardized o=
r widely deployed.

### Multi-party video conferencing and risks

Multi-party video conferencing protocols such as WebRTC {{RFC6176}} {{RFC=
7118}} allow for robust, bandwidth-adaptive, wideband and super-wideband =
video and audio discussions in groups. 'The WebRTC protocol was designed =
to enable responsive real-time communications over the Internet, and is i=
nstrumental in allowing streaming video and conferencing applications to =
run in the browser. In order to easily facilitate direct connections betw=
een computers (bypassing the need for a central server to act as a gateke=
eper), WebRTC provides functionality to automatically collect the local a=
nd public IP addresses of Internet users (ICE or STUN). These functions d=
o not require consent from the user, and can be instantiated by sites tha=
t a user visits without their awareness. The potential privacy implicatio=
ns of this aspect of WebRTC are well documented, and certain browsers hav=
e provided options to limit its behavior.' {{AndersonGuarnieri}}.

'The disclosure of network addresses presents a specific risk to individu=
als that use privacy tools to conceal their real IP address to sites that=
 they visit. Typically, when a user browses the Internet over a VPN, the =
only address that should be recorded by sites they visit would be that of=
 the VPN provider itself. Using the WebRTC STUN function allows a site to=
 additionally enumerate the addresses that are associated with the comput=
er that the visitor is using =E2=80=93 rather than those of intermediarie=
s. This means that if a user is browsing the Internet on an ADSL connecti=
on over a VPN, a malicious site they visit could potentially surreptitiou=
s record the home address of the user.' {{AndersonGuarnieri}}.

While facilitating freedom of assembly and association multi-party video =
conferencing tools might pose concrete risks for those who use them. One =
the one hand WebRTC is providing a resilient channels of communications, =
but on the other hand it also exposes information about those who are usi=
ng the tool which might lead to increased surveillance, identification an=
d the consequences that might be derived from that. This is especially co=
ncerning because the usage of a VPN does not protect against the exposure=
 of IP addresses {{Crawford}}.=20

The risk of surveillance is also true in an offline space, but this is ge=
nerally easy to analyze for the end-user. Security and privacy expectatio=
ns of the end-user could be made more clear to the user (or improved) whi=
ch would result in a more secure and/or private excercise or the right to=
 freedom of assembly or association.


## Peer-to-peer networks and systems

At the organizational level, peer production is one of the most relevant =
innovations from Internet mediated social practices. According to {{Benkl=
er}}, it implies 'open collaborative innovation and creation, performed b=
y diverse, decentralized groups organized principally by neither price si=
gnals nor organizational hierarchy, harnessing heterogeneous motivations,=
 and governed and managed based on principles other than the residual aut=
hority of ownership implemented through contract.' {{Benkler}}.=20

In his book The Wealth of Networks, Benkler significantly expands on his =
definition of commons-based peer production. According to Benkler, what d=
istinguishes commons-based production is that it doesn't rely upon or pro=
pagate proprietary knowledge: "The inputs and outputs of the process are =
shared, freely or conditionally, in an institutional form that leaves the=
m equally available for all to use as they choose at their individual dis=
cretion." {{Benkler}} To ensure that the knowledge generated is available=
 for free use, commons-based projects are often shared under an open lice=
nse.

### Peer-to-peer system achitectures

Peer-to-peer (P2P) is esentially a model of how people interact in real l=
ife because "we deal directly with one another whenever we wish to" {{Vu}=
}. Usually if we need something we ask our peers, who in turn refer us to=
 other peers. In this sense, the ideal definition of P2P is that "nodes a=
re able to directly exchange resources and services between themselves wi=
thout the need for centralized servers" and where each participating node=
 typically acts both as a server and as a client {{Vu}}. In RFC 5694 P2P =
has been defined as peers or nodes that should be able to communicate dir=
ectly between themselves without passing intermediaries, and that the sys=
tem should be self-organizing and have decentralized control {{RFC5694}}.=
 With this in mind, the ultimate model of P2P is a completely decentraliz=
ed system, which is more resistant to speech regulation, immune to single=
 points of failure and have a higher performance and scalability. Nonethe=
less, in practice some P2P systems are supported by centralized servers a=
nd some others have hybrid models where nodes are organized into two laye=
rs: the upper tier servers and the lower tier common nodes {{Vu}}.

Since the ARPANET project, the original idea behind the Internet was conc=
eived as what we would now call a peer-to-peer system {{RFC0001}}. Over t=
ime it has increasingly shifted towards a client/server model with "milli=
ons of consumer clients communicating with a relatively priviledged set o=
f servers" {{NelsonHedlun}}. Whether for resource sharing or data sharing=
, P2P systems are a form of enabling freedom of assembly and association.=
 Not only they allow for effective dissemination of information, but they=
 also because leverage computing resources by diminishing costs allowing =
for the formation of open collectives at the network level. At the same t=
ime, in completely descentralized systems the nodes are autonomous and ca=
n join or leave the network as they want also makes the system unpredicab=
le: a resource might be only sometimes available, and some others it migh=
t be missing or incomplete {{Vu}}. Lack of information might in turn make=
 association or assembly more difficult.=20

Additionally, when one architecturally asseses the role of P2P systems on=
 can say that: "The main advantage of centralized P2P systems is that the=
y are able to provide a quick and reliable resource locating. Their limit=
ation, however, is that the scalability of the systems is affected by the=
 use of servers. While decentralized P2P systems are better than centrali=
zed P2P systems in this aspect, they require a longer time in resource lo=
cating. As a result, hybrid P2P systems have been introduced to take ad- =
vantages of both centralized and decentralized architectures. Basically, =
to maintain the scalability, similar to decentralized P2P systems, there =
are no servers in hybrid P2P systems. However, peer nodes that are more p=
owerful than others can be se- lected to act as servers to serve others. =
These nodes are often called super peers. In this way, resource locating =
can be done by both decentralized search techniques and centralized searc=
h techniques (asking super peers), and hence the systems benefit from the=
 search techniques of centralized P2P systems." {{Vu}}

### Version control

Ever since developers needed to collaboratively write, maintain and discu=
ss large code basis for the Internet there have been different approaches=
 of doing so. One approach is discussing code through mailing lists, but =
this has proven to be hard in case of maintaining the most recent version=
s. There are many different versions and characteristics of version contr=
ol systems.=20

A version control system is a piece of software that enables developers o=
n a software team to work together and also archive a complete history of=
 their work {{Sink}}. This allows teams to be working simultaneously on u=
pdated. According to Sink, broadly speaking, the history of version contr=
ol tools can be dividied into three generations. In the first one, concur=
rent development meant that only one person could be working on a file at=
 a time. The second generation tools permit simultaneous modifications as=
 long as users merge the current revisions into their work before they ar=
e allowed to commit. The hird generation tools allow merge and commit to =
be separated {{Sink}}.

Interestingly no version control system has ever been standardized in the=
 IETF whereas the version control systems like Subversion and Git have ar=
e widely used within the community, as well as by working groups. There h=
as been a spirited discussion on whether working groups should use centra=
lized forms of the Git protocol, such as those offered by Gitlab or Githu=
b. Proponents argue that this simplifies the workflow and allows for a mo=
re transparent workflow. Opponents argue that the relience on a centraliz=
ed service which is not merely using the Git protocol, but also used non-=
standardize options like an Issue-Tracker, makes the process less transpa=
rent and reliant on a third party.=20

The IETF has not made a decision on the use of centralized instances of g=
it, such as Github or Gitlab. There have been two efforts to standardize =
the workflow vis a vis these third party services, but these haven't come=
 to fruition:
https://www.ietf.org/archive/id/draft-nottingham-wugh-services-00.txt
https://www.ietf.org/archive/id/draft-thomson-github-bcp-00.txt

## Reaching out

In meatspace, handing out pamphlets and reaching out to unknown people is=
 the most common way for growing a cause and seeking collective support. =
The characteristics of the Internet infrastructure and online space make =
reaching out more difficult.

### Spam, filter bubbles, and unrequested messaging

In the 1990s as the internet became more and more commercial, spam came t=
o be defined as irrelevant or unsolicited messages that were porsted many=
 times to multiple news groups or mailing lists {{Marcus}}. Here the ques=
tion of consent is crucial. In the 2000s a large part of the discussion r=
evolved around the fact that certain corporations -protected by the right=
 to freedom of association- considered spam to be a form of "comercial sp=
eech", thus encompassed by free expression rights {{Marcus}}. Nonetheless=
, if we consider that the rights to assembly and association also mean th=
at "no one may be compelled to belong to an association" {{UDHR}}, spam i=
nfringes both rights if an op-out mechanism is not provided and people ar=
e obliged to receive unwanted information, or be reached by people they d=
o not know.

This leaves us with an interesting case: spam is currently handled mostly=
 by mailproviders on behalf of the user, next to that countries are incre=
asingly adopting opt-in regimes for mailinglists and commercial e-mail, w=
ith a possibility of serious fines in case of violation.

While this protects the user from being confronted with unwanted messages=
, it also makes it legally and technically very difficult to communicate =
a message to someone who did not explicitly ask for this. In public offli=
ne spaces we regularly get exposed to flyers, invitations or demonstratio=
ns where our opinions get challenged, or we are invited to consider diffe=
rent viewpoints. There is no equivalent on the Internet with the technica=
l and legal regime that currently operates in it. In other words, it is n=
early impossible  to provide information, in a proportionate manner, that=
 someone is not explicility expecting or asking for. This reinforces a co=
ncept that is regularly discussed on the application level, called =E2=80=
=98filter bubble=E2=80=99: =E2=80=9CThe proponents of personalization off=
er a vision of a custom-tailored world, every facet of which fits us perf=
ectly. It=E2=80=99s a cozy place, populated by our favorite people and th=
ings and ideas.=E2=80=9D {{Pariser}}. =E2=80=9CThe filter bubble=E2=80=99=
s costs are both personal and cultural. There are direct consequences for=
 those of us who use personalized filters. And then there are societal co=
nsequences, which emerge when masses of people begin to live a filter bub=
bled-life (=E2=80=A6). Left to their own devices, personalization filters=
 serve up a kind of invisible autopropaganda, indoctrinating us with our =
own ideas, amplifying our desire for things that are familiar and leaving=
 us oblivious to the dangers lurking in the dark territory of the uknown.=
=E2=80=9D {{Pariser}}.

It seems that the =E2=80=98filter bubble=E2=80=99-effect can also be obse=
rved at the infrastructure level, which actually strenghtens the impact a=
nd thus hampers the effect of collective expression. This could be interp=
retated as an argument for the injection of unrequested messages, spam or=
 other unrequested notifications. But the big difference between the prol=
iferation of such messages offline and online is the investment that is n=
eeded. It is not hard for a single person to message a lot of people, whe=
reas if that person needed to go house by house the scale and impact of t=
heir actions would be much smaller. Inversely if it were a common practic=
e to expose people to unwanted messages online, users would be drowned in=
 such messages, and no expression would be possible anymore.  Allowing il=
limited sending of unsolicited messages would be a blow against freedom o=
f speech: when everyone talks, nobody listens.=20

Here the argument is very similar to DDoS attacks: whereas one could argu=
e for legitimate uses in limited specific cases, these would be drowned o=
ut by a malicious use which constitutes an attack on the internet infrast=
ructure and thus the assembly or association itself.

### Distributed Denial of Service Attacks

One of the most common examples of an association at the infrastructure l=
evel are the Distributed Denial of Service Attacks (DDoS) in which the in=
frastructure of the Internet is used to express discontent with a specifi=
c cause {{Abibil}} {{GreenMovement}}. Unfortunately DDoS are often used t=
o stifle freedom of expression as they complicate the ability of independ=
ent media and human rights organizations to exercise their right to (onli=
ne) freedom of association, while facilitating the ability of governments=
 to censor dissent. This is one of the reasons protocols should seek to m=
itigate DDoS attacks {{BCP72}}.=20

As described in draft-irtf-hrpc-research: "Uses of DDoS might or might no=
t be legitimate for political reasons, but the IETF has no means or metho=
ds to assess this, and in general enabling DDoS would mean a deterioratio=
n of the network and thus freedom of expression". This is argued from the=
 vector of freedom of expression, but if we would analyze it from the per=
spective of freedom of association the argument could be as follows: If t=
he Internet is an association, any attack should be prevented and mitigat=
ed because it prevents the possibility of exercising a right to collectiv=
e expression, which is consistent with {{BCP72}}. More will be said on th=
is topic in the last section of the present text.

 On the other hand, it must be taken into consideration that DDoS attacks=
 are a form of forced assembly when done without the agreement -or even k=
nowledge- of the involved parts. This point was also described in draft-i=
rtf-hrpc-research: "When it comes to comparing DDoS attacks to protests i=
n offline life, it is important to remember that only a limited number of=
 DDoS attacks involved solely willing participants.  In most cases, the c=
lients are hacked computers of unrelated parties that have not consented =
to being part of a DDoS (for exceptions see Operation Abibil {{Abibil}} o=
r the Iranian Green Movement DDoS {{GreenMovement}}).


## Grouping together (identities)

Collective identities are also protected by freedom of association and as=
sembly. Acording to Melucci these are 'shared definitions produced by sev=
eral interacting individuals who are concerned with the orientation of th=
eir action as well as the field of opportunities and constraints in which=
 their action takes place.' {{Melucci}} In this sense, assemblies and ass=
ociations are an important base in the maintenance and development of cul=
ture, as well as preservation of minority identities {{OSCE}}.=20

### DNS

Domain names allow hosts to be identified by human parsable information. =
Whereas an IP address might not be the expression of an identity, a domai=
n name can be, and often is. On the other hand the grouping of a certain =
identity under a specific domain or even a Top Level Domain brings about =
risks because connecting an identity to a hierarchically structured ident=
ifier systems creates a central attack surface. Some of these risks are t=
he surveillance of the services running on the domain, domain based censo=
rship {{RFC7754}}, or impersonation of the domain through DNS cache poiso=
ning. Several technologies have been developed in the IETF to mitigated t=
hese risks such as DNS over TLS {{RFC7858}}, DNSSEC {{RFC4033}}, and TLS =
{{RFC5246}}. These mitigations would, when implemented, not make censorsh=
ip impossible, but rather make it visible. The use of a centralized autho=
rity always makes censorship through a registry or registrar possible, as=
 well as by using a fake resolver or using proposed standards such as DNS=
 Response Policy Zones {{RPZ}}.

The structuring of DNS as a hierarchical authority structure also brings =
about specific characteristic, namely the possibility of centralized poli=
cy making on the management and operation of domain names, which is what =
(in part) happens at ICANN. The impact of ICANN processes on human rights=
 will not be discussed here.=20
=20
### ASes

In order for edge-users to connect to the Internet, a user needs to be co=
nnected to an Automous System (AS) which, in turn, has peering or transit=
 relations with other AS'es. This means that in the process of accessing =
the Internet the edge-user needs to accept the policies and practices of =
the intermediary that provides them access to the other networks. In othe=
r words, for users to be able to join the 'network of networks', they alw=
ays need to connect through an intermediary.=20

While accessing the Internet through an intermediary, the user is forced =
to accept the policies, practices and principles of a network. This could=
 impede the rights of the edge-user, depending on the implemented policie=
s and practices on the network and how (if at all) they are communicated =
to them. For example: filtering, blocking, extensive logging or other inv=
asive practices that are not clearly communicated to the user.

In some cases it also means that there is no other way for the edge-user =
to connect to the network of networks, and is thus forced into accepting =
the policies of a specific network, because it is not trivial for an edge=
-user to operate an AS and engage in peering relation with other ASes. Th=
is design, combined with the increased importance of the Internet to make=
 use of basic services, forces edge-user to engage in association with a =
specific network eventhough the user does not consent with the policies o=
f the network.=20


Discussion: The Internet as an association
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

It is undeniable that communities, collaboration and joint action lie at =
the heart of the Internet. Even at at linguistical level, the words "netw=
orks=E2=80=9D and =E2=80=9Cassociations=E2=80=9D are close synonyms. Both=
 interconnected groups and assemblies of people depend on =E2=80=9Clinks=E2=
=80=9D and =E2=80=9Crelationships=E2=80=9D {{Swire}}. Taking this definit=
ion and the previous analysis into consideration, we argue that the Inter=
net constitutes a an assembly and an association. What are the implicatio=
ns of this? Does it mean that every network is an assembly and has absolu=
te freedom to implement its own rules? Or does the importance of a functi=
oning 'larger' assembly (the Internet) has prevails over the preferences =
of the smaller ones (individual AS'es)?=20
The demands that have been set for ASes is very limited and are based on =
routing principles: an AS must be used for exchanging external routing in=
formation with other ASes through BGP, should therefore use BGP and IP an=
d have a routing policy {{RFC1930}}. So in order to be able to connect to=
 the Internet as an AS, which means to engage in peering or transit relat=
ions, there are basic rules one needs to adhere to.  But theses rules do =
not say anything on how the AS will or should treat traffic on its networ=
k. In this regard, we must take into consideration that even things that =
are private, need to live up to standards because they have public conseq=
uences. If we take the example of ASes, we could say they are private inf=
rastructure (therefore souvereign with the ability to set their own polic=
ies), but jointly they form a type of public infrastructure, from the mom=
ent the receive an Autonomous Systems Number.=20

The Internet is made of up interconnected ASes (one would argue that this=
 doesn't include IXPs, but most modern IXPs will have an ASN for their ro=
ute server (and possibly a separate ASN for their management infrastructu=
re), which jointly form an assembly and an association. This assembly and=
 association should be protected. This means that rights and obligations =
that sterm from this organizational form, should also be protected and re=
spected.
=20
Conclusions
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The Internet has an impact on the ability for people to excercise their r=
ight to freedom of association and assembly. The Internet, since its ince=
ption has enabled people to jointly communicate, collaborate and collabor=
ate. The same could also be argued with relation to freedom of expression=
, some have argued that the text in article 19 of the {{UDHR}} reads like=
 a description of the Internet:

    [the] freedom to hold opinions without interference and to seek, rece=
ive and impart information and ideas through any media and regardless of =
frontiers. {{UDHR}}

The difference between freedom of expression and freedom of association a=
nd assembly is that the Internet itself takes the form on an association =
and assembly; it reproduces its features of collaboration. Recognizing th=
is is a crucial step in determining architectural features of the Interne=
t and its usage.=20


Security Considerations
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

As this draft concerns a research document, there are no security conside=
rations.


IANA Considerations
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

This document has no actions for IANA.

Research Group Information
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
The discussion list for the IRTF Human Rights Protocol Considerations Res=
earch Group is located at the e-mail address <hrpc@ietf.org>. Information=
 on the group and information on how to subscribe to the list is at
<https://www.irtf.org/mailman/listinfo/hrpc>

Archives of the list can be found at:
<https://www.irtf.org/mail-archive/web/hrpc/current/index.html>



--------------F6E5B592470291DAE44A5F33--


From nobody Fri Oct 13 05:23:08 2017
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADBBD13293A for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 05:22:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qXK7Pl4WxouK for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 05:22:52 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 920C0133064 for <xml2rfc@ietf.org>; Fri, 13 Oct 2017 05:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v9DCMmqb018951; Fri, 13 Oct 2017 14:22:48 +0200 (CEST)
Received: from [192.168.217.119] (p5DC7FC78.dip0.t-ipconnect.de [93.199.252.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3yD6LJ2KdbzDM1M; Fri, 13 Oct 2017 14:22:48 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <2768c8d6-dd7f-36a9-8cc8-920a943c49cb@digitaldissidents.org>
Date: Fri, 13 Oct 2017 14:22:45 +0200
Cc: xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 529590165.268334-725f4047ec29e817ed9f8b398cc6d2c9
Content-Transfer-Encoding: quoted-printable
Message-Id: <EBDABC50-7EF8-4901-8A45-A077D9AE539A@tzi.org>
References: <873da473-9a22-9465-84f9-66ded9a738e7@digitaldissidents.org> <2768c8d6-dd7f-36a9-8cc8-920a943c49cb@digitaldissidents.org>
To: Niels ten Oever <lists@digitaldissidents.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/5beftLJQ9p9Yba-kLcUEYXz9Ffw>
Subject: Re: [xml2rfc] dependency error
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Oct 2017 12:22:56 -0000

On Oct 13, 2017, at 14:17, Niels ten Oever <lists@digitaldissidents.org> =
wrote:
>=20
> expected ':' while scanning a simple key at line 268 column 6

You have

     date 2017

Where you probably intended a

     date: 2017

Gr=C3=BC=C3=9Fe, Carsten


From nobody Fri Oct 13 05:34:52 2017
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B148E13293A for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 05:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0GVKmws4vU34 for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 05:34:48 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33864132F7D for <xml2rfc@ietf.org>; Fri, 13 Oct 2017 05:34:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v9DCYinf028444; Fri, 13 Oct 2017 14:34:44 +0200 (CEST)
Received: from [192.168.217.119] (p5DC7FC78.dip0.t-ipconnect.de [93.199.252.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3yD6c42C6DzDM1Y; Fri, 13 Oct 2017 14:34:44 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <873da473-9a22-9465-84f9-66ded9a738e7@digitaldissidents.org>
Date: Fri, 13 Oct 2017 14:34:41 +0200
Cc: xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 529590881.67797-0eb55bd1b15a412ad9151aa409b45122
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1988AC9-A282-40A2-8515-15EBEE2CFB89@tzi.org>
References: <873da473-9a22-9465-84f9-66ded9a738e7@digitaldissidents.org>
To: Niels ten Oever <lists@digitaldissidents.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Jsa8AbHzIXhiIpJlQv2_210CVuM>
Subject: Re: [xml2rfc] dependency error
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Oct 2017 12:34:50 -0000

On Oct 13, 2017, at 10:57, Niels ten Oever <lists@digitaldissidents.org> =
wrote:
>=20
> find 'kramdown' (~> 1.14.0) - did find: [kramdown-1.15.0] =
(Gem::LoadError)

Hmm, that is a =E2=80=9Ccannot happen=E2=80=9D =E2=80=94 you cannot =
install (a recent version of) kramdown-rfc2629 without also installing =
kramdown 1.14.0.

Obviously, it did happen, so I=E2=80=99m curious:
How did you install kramdown-rfc2629?
(And what is the output of "gem search -l kramdown=E2=80=9D?)

Background on the versions involved:
Kramdown-rfc2629 depends on kramdown, a commonly used implementation of =
the markdown languages.
Kramdown-rfc2629 always specifies the minor version (semantic =
versioning) of kramdown that it uses.  So, here kramdown-rfc2629 wants =
to use 1.14.  But only 1.15 seems to be installed on the system, which =
cannot happen, because =E2=80=9Cgem install=E2=80=9D-ing =
kramdown-rfc2629 also installs the right version of kramdown (along =
other versions that may be installed).

Why is kramdown-rfc2629 using an older version of kramdown?  Kramdown =
turned off support for ancient Ruby 1.9 in 1.15.0 (A current Ruby would =
be 2.4.2 or 2.4.1).  Requiring kramdown 1.15 would therefore also remove =
support for ancient Ruby 1.9 in kramdown-rfc2629. This shouldn=E2=80=99t =
be a problem, as Ruby 1.9 really is obsolete.  Unfortunately, some older =
versions of Linux distributions such as Debian include just that =
obsolete version and provide no easy way to upgrade into the present.  =
(As a datapoint, until a few weeks ago the tools.ietf.org servers were =
running 1.9!).  So I saw a slightly greater downside in upgrading to =
1.15 than in sticking to a slightly older version of the markdown base =
=E2=80=94 that inequality may move to the other side quite soon, though.

The problem you ran into seems to add another downside, so let=E2=80=99s =
diagnose it.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Fri Oct 13 05:54:53 2017
Return-Path: <lists@digitaldissidents.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9A52133075 for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 05:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r2OHXlS9jmyo for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 05:54:51 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7417213306F for <xml2rfc@ietf.org>; Fri, 13 Oct 2017 05:54:51 -0700 (PDT)
Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <lists@digitaldissidents.org>) id 1e2zUH-0002IK-L0; Fri, 13 Oct 2017 14:54:49 +0200
To: Carsten Bormann <cabo@tzi.org>
Cc: xml2rfc@ietf.org
References: <873da473-9a22-9465-84f9-66ded9a738e7@digitaldissidents.org> <A1988AC9-A282-40A2-8515-15EBEE2CFB89@tzi.org>
From: Niels ten Oever <lists@digitaldissidents.org>
Message-ID: <4b59d84d-de1f-1210-7edd-58c2dcee9c81@digitaldissidents.org>
Date: Fri, 13 Oct 2017 14:54:49 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <A1988AC9-A282-40A2-8515-15EBEE2CFB89@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Authenticated-As-Hash: 29cc722430e8f1f6ed904119444c0d49b0f3ee91
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 353bb18b0f14186cd389c275975c39f5
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Ou55aQt4R5_poaWSI8ohk_1x3rk>
Subject: Re: [xml2rfc] dependency error
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Oct 2017 12:54:53 -0000

Hi Carsten,

On 10/13/2017 02:34 PM, Carsten Bormann wrote:
> On Oct 13, 2017, at 10:57, Niels ten Oever <lists@digitaldissidents.org> wrote:
>>
>> find 'kramdown' (~> 1.14.0) - did find: [kramdown-1.15.0] (Gem::LoadError)
> 
> Hmm, that is a “cannot happen” — you cannot install (a recent version of) kramdown-rfc2629 without also installing kramdown 1.14.0.
> 
> Obviously, it did happen, so I’m curious:
> How did you install kramdown-rfc2629?

I installed both kramdown and kramdown-rfc2629 with:

# apt install kramdown kramdown-rfc2629

What I think happened is that kramdown got upgraded after install.


> (And what is the output of "gem search -l kramdown”?)
> 

$ gem search -l kramdown

*** LOCAL GEMS ***

kramdown (1.15.0)
kramdown-rfc2629 (1.2.6)


> Background on the versions involved:
> Kramdown-rfc2629 depends on kramdown, a commonly used implementation of the markdown languages.
> Kramdown-rfc2629 always specifies the minor version (semantic versioning) of kramdown that it uses.  So, here kramdown-rfc2629 wants to use 1.14.  But only 1.15 seems to be installed on the system, which cannot happen, because “gem install”-ing kramdown-rfc2629 also installs the right version of kramdown (along other versions that may be installed).
> 
> Why is kramdown-rfc2629 using an older version of kramdown?  Kramdown turned off support for ancient Ruby 1.9 in 1.15.0 (A current Ruby would be 2.4.2 or 2.4.1).  Requiring kramdown 1.15 would therefore also remove support for ancient Ruby 1.9 in kramdown-rfc2629. This shouldn’t be a problem, as Ruby 1.9 really is obsolete.  Unfortunately, some older versions of Linux distributions such as Debian include just that obsolete version and provide no easy way to upgrade into the present.  (As a datapoint, until a few weeks ago the tools.ietf.org servers were running 1.9!).  So I saw a slightly greater downside in upgrading to 1.15 than in sticking to a slightly older version of the markdown base — that inequality may move to the other side quite soon, though.
> 
> The problem you ran into seems to add another downside, so let’s diagnose it.

Happy to help. Maybe things will change with the new Debian Stable,
which I think is the standard reference, no?

Thanks for the support for this piece of software!

Cheers,

Niels
> 
> Grüße, Carsten
> 

-- 
Niels ten Oever
Head of Digital

Article 19
www.article19.org

PGP fingerprint    8D9F C567 BEE4 A431 56C4
                     678B 08B5 A0F2 636D 68E9


From nobody Fri Oct 13 05:55:26 2017
Return-Path: <lists@digitaldissidents.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF46C13306F for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 05:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level: 
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QY0gU7249ePQ for <xml2rfc@ietfa.amsl.com>; Fri, 13 Oct 2017 05:55:23 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B498213207A for <xml2rfc@ietf.org>; Fri, 13 Oct 2017 05:55:23 -0700 (PDT)
Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <lists@digitaldissidents.org>) id 1e2zUo-0002Qu-1n; Fri, 13 Oct 2017 14:55:22 +0200
To: Carsten Bormann <cabo@tzi.org>
Cc: xml2rfc@ietf.org
References: <873da473-9a22-9465-84f9-66ded9a738e7@digitaldissidents.org> <2768c8d6-dd7f-36a9-8cc8-920a943c49cb@digitaldissidents.org> <EBDABC50-7EF8-4901-8A45-A077D9AE539A@tzi.org>
From: Niels ten Oever <lists@digitaldissidents.org>
Message-ID: <7940faad-1fa5-60cb-e785-e804799a6125@digitaldissidents.org>
Date: Fri, 13 Oct 2017 14:55:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <EBDABC50-7EF8-4901-8A45-A077D9AE539A@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Authenticated-As-Hash: 29cc722430e8f1f6ed904119444c0d49b0f3ee91
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 739ba1b2be5fabc1cc6069058737919f
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/TN7JGSEgYcisX4E7aLTKh4rKlGg>
Subject: Re: [xml2rfc] dependency error
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Oct 2017 12:55:25 -0000

On 10/13/2017 02:22 PM, Carsten Bormann wrote:
> On Oct 13, 2017, at 14:17, Niels ten Oever <lists@digitaldissidents.org> wrote:
>>
>> expected ':' while scanning a simple key at line 268 column 6
> 
> You have
> 
>      date 2017
> 
> Where you probably intended a
> 
>      date: 2017
> 

Oops, I should have caught that, thanks!

Regards,

Niels


From nobody Tue Oct 24 15:39:05 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3B4138BD2 for <xml2rfc@ietfa.amsl.com>; Tue, 24 Oct 2017 15:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZXSuqAN95GGu for <xml2rfc@ietfa.amsl.com>; Tue, 24 Oct 2017 15:39:02 -0700 (PDT)
Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18C3B138B5E for <xml2rfc@ietf.org>; Tue, 24 Oct 2017 15:39:02 -0700 (PDT)
Received: by mail-pg0-x22f.google.com with SMTP id b192so15702473pga.2 for <xml2rfc@ietf.org>; Tue, 24 Oct 2017 15:39:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:organization:to:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=xBEdXWHO+A7JEKIgPUvq1SrE5V/T2VE391bzkHoZAA8=; b=djQ9PBl6D6uHTVsfdt2U0uza6GHsur1lj6VMJpgv2HPRgpEgrPJqkPr2JCmF5KhB27 8gPOjPRP8dQnL0tQMbLA1fd5Dx419+o+wqeVZJyw3oSbLJgTjxWmUCWbjErsWJtKR65D Og1IxIWEPRpLiRHyLjk2jJ708NSnvXWJJeiE4CHJZXjfk2c2A/LWsM/9lMZiajpw1/Q/ nPD/om3ZX8x7QTC8up45VhYCbt+Wj7l3bdoke+vVbQznvPwsDtakCANFsC5RwxAgh2xL /3a77rXgYfmgPgVxLfUYOt9+sp0PSpiT7PPTybf3Byv/oAjpqdvHXoAuatHbD7z/z8Ln oTAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:organization:to:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=xBEdXWHO+A7JEKIgPUvq1SrE5V/T2VE391bzkHoZAA8=; b=dCpjQymuL/zhiFo0mt8gzKfcfvk+5tynVhZUSHic0PJbGZ29y14+MI52FNDmzoF3co S1dXTbiYS8QhEyxjzhtenNDYG1gtCnUpgS9XZo/0qvuBhSZ8IyzkhZoT0xi4QygqpbSj 6Twv+7pd/x7gQdAwUxoyIHm4Bw6zfhQg6Ls2P8+luRXAptEnMUdFuPlazEjlyKL/gEpF dom2f1DovfppQt1FsriEcAEBNEpRDf3NolO/g0JnXAHMp/jeFvkuO9u2KLHC0X306x7U FEZWeD0RjlNnlA14v/D0ddnQWEkkDEh9f78tSDUhg/YIeXtzoQzJcc7BbIK1yhhKCLIf VntQ==
X-Gm-Message-State: AMCzsaWGWA7FOnqvPCcYlbxJrpZ6OArNg4BOHdWRbd/jVbMeWC9J4oAZ J6EENYuZU15qu7sGHNnd7mi11w==
X-Google-Smtp-Source: ABhQp+R32O8k6Gc+kkRa5vRu2tYctfss6jV/sY946cV3IAAePEKtGlLnjG0fIuZHRE7iKZ1Wuyus8Q==
X-Received: by 10.98.74.206 with SMTP id c75mr192659pfj.100.1508884741204; Tue, 24 Oct 2017 15:39:01 -0700 (PDT)
Received: from ?IPv6:2406:e001:3d21:1:28cc:dc4c:9703:6781? ([2406:e001:3d21:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id d15sm1999166pfj.163.2017.10.24.15.38.59 for <xml2rfc@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Oct 2017 15:39:00 -0700 (PDT)
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
To: xml2rfc <xml2rfc@ietf.org>
Message-ID: <acaf347e-1882-43f2-da80-0a980002e9e7@gmail.com>
Date: Wed, 25 Oct 2017 11:39:02 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/xi-1xuCjULYasx4fIYlo1O7jg3Y>
Subject: [xml2rfc] Hangtext spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Oct 2017 22:39:03 -0000

Hi,

I just hit a case where xml2rfc outputs text that idnits doesn't like:

<t>There are 3 properties applicable to the installation of ASAs:
 <list style="hanging">
  <t hangText="The dynamic installation property">allows installing an ASA on demand, on any	hosts compatible with the ASA.</t>
  <t hangText="The decoupling property">allows controlling resources of a NE from a remote ASA, i.e. an ASA installed on a host machine different from the resources' NE.</t>
  <t hangText="The multiplicity property">allows controlling multiple sets of resources from a single ASA.</t>
 </list>
</t>

The output looks like this:
   The dynamic installation property  allows installing an ASA on
      demand, on any hosts compatible with the ASA.

   The decoupling property  allows controlling resources of a NE from a
      remote ASA, i.e. an ASA installed on a host machine different from
      the resources' NE.

   The multiplicity property  allows controlling multiple sets of
      resources from a single ASA.

Note the two spaces after the hangtext in each case. Idnits issues
warnings:

  == Line 361 has weird spacing: '...roperty  allow...'

  == Line 364 has weird spacing: '...roperty  allow...'

  == Line 368 has weird spacing: '...roperty  allow...'

Why two spaces?

     Brian

-- 
Regards
   Brian Carpenter



From nobody Wed Oct 25 04:54:26 2017
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 587AE13ACA2 for <xml2rfc@ietfa.amsl.com>; Wed, 25 Oct 2017 04:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GXWGISeOycoj for <xml2rfc@ietfa.amsl.com>; Wed, 25 Oct 2017 04:54:24 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D99C113B110 for <xml2rfc@ietf.org>; Wed, 25 Oct 2017 04:54:22 -0700 (PDT)
Received: from h-99-61.a357.priv.bahnhof.se ([82.196.99.61]:55986 helo=[192.168.1.120]) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1e7KGL-0005vg-QE; Wed, 25 Oct 2017 04:54:22 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, xml2rfc <xml2rfc@ietf.org>
References: <acaf347e-1882-43f2-da80-0a980002e9e7@gmail.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <b3275915-16eb-e21a-7cfc-6d306677296b@levkowetz.com>
Date: Wed, 25 Oct 2017 13:54:06 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <acaf347e-1882-43f2-da80-0a980002e9e7@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rvjI2VsxUv4AmeutD6cs3oTbrI6IcPH7h"
X-SA-Exim-Connect-IP: 82.196.99.61
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, brian.e.carpenter@gmail.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/EbZ-bbqH1cFDKXn16wx5MTaFiVI>
Subject: Re: [xml2rfc] Hangtext spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Oct 2017 11:54:25 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--rvjI2VsxUv4AmeutD6cs3oTbrI6IcPH7h
Content-Type: multipart/mixed; boundary="9dn8BohnPgLUJlxoWIPloiTTsD8DPSqTV";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,
 xml2rfc <xml2rfc@ietf.org>
Message-ID: <b3275915-16eb-e21a-7cfc-6d306677296b@levkowetz.com>
Subject: Re: [xml2rfc] Hangtext spacing
References: <acaf347e-1882-43f2-da80-0a980002e9e7@gmail.com>
In-Reply-To: <acaf347e-1882-43f2-da80-0a980002e9e7@gmail.com>

--9dn8BohnPgLUJlxoWIPloiTTsD8DPSqTV
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Brian,

On 2017-10-25 00:39, Brian E Carpenter wrote:
> Hi,
>=20
> I just hit a case where xml2rfc outputs text that idnits doesn't like:
>=20
> <t>There are 3 properties applicable to the installation of ASAs:
>  <list style=3D"hanging">
>   <t hangText=3D"The dynamic installation property">allows installing a=
n ASA on demand, on any	hosts compatible with the ASA.</t>
>   <t hangText=3D"The decoupling property">allows controlling resources =
of a NE from a remote ASA, i.e. an ASA installed on a host machine differ=
ent from the resources' NE.</t>
>   <t hangText=3D"The multiplicity property">allows controlling multiple=
 sets of resources from a single ASA.</t>
>  </list>
> </t>
>=20
> The output looks like this:
>    The dynamic installation property  allows installing an ASA on
>       demand, on any hosts compatible with the ASA.
>=20
>    The decoupling property  allows controlling resources of a NE from a=

>       remote ASA, i.e. an ASA installed on a host machine different fro=
m
>       the resources' NE.
>=20
>    The multiplicity property  allows controlling multiple sets of
>       resources from a single ASA.
>=20
> Note the two spaces after the hangtext in each case. Idnits issues
> warnings:
>=20
>   =3D=3D Line 361 has weird spacing: '...roperty  allow...'
>=20
>   =3D=3D Line 364 has weird spacing: '...roperty  allow...'
>=20
>   =3D=3D Line 368 has weird spacing: '...roperty  allow...'
>=20
> Why two spaces?

That's the convention xml2rfc uses to separate the list item identifier
from the item text in a list with hanging indentation.  In your use case,=

you don't have a very clear item identifier; I'm not sure how to best
approach this.  Maybe:

 <t>There are 3 properties applicable to the installation of ASAs:
  <list style=3D"hanging">
   <t hangText=3D"The dynamic installation property:"><vspace blankLines=3D=
"0"/>
    allows installing an ASA on demand, on any hosts compatible with the
    ASA.</t>
   <t hangText=3D"The decoupling property:"><vspace blankLines=3D"0"/>
    allows controlling resources of a NE from a remote ASA, i.e. an ASA
    installed on a host machine different from the resources' NE.</t>
   <t hangText=3D"The multiplicity property:"><vspace blankLines=3D"0"/>
    allows controlling multiple sets of resources from a single ASA.</t>
  </list>
 </t>

which produces:

   There are 3 properties applicable to the installation of ASAs:

   The dynamic installation property:
      allows installing an ASA on demand, on any hosts compatible with
      the ASA.

   The decoupling property:
      allows controlling resources of a NE from a remote ASA, i.e. an
      ASA installed on a host machine different from the resources' NE.

   The multiplicity property:
      allows controlling multiple sets of resources from a single ASA.



Best regards,

	Henrik


--9dn8BohnPgLUJlxoWIPloiTTsD8DPSqTV--

--rvjI2VsxUv4AmeutD6cs3oTbrI6IcPH7h
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJZ8HtmAAoJEE6bV0uPuxcaDwMP/2go0ImdQ0Qf6xjzb+ASeIOy
xn++fEZz6zRRIMTOR2UQMB0uGLlC4J/sf1+8hr6JLYFg2FiHin++ZmJexYLzNtlt
Y16mb5B8vwd9SP3bkt69IbW00vWS/BRyt/Fp9ra3Buv13qQn7X6TvfDLBrrmKPL4
dzTL2n2ZWj5bBnhtVp5QwGUHzUzhBkTjqouQNzHMRIkk0DScEm/55VwojSjSZlkJ
qFfhfNmH52bQPEidlviT4BPaQVrHdtCWSzYNk7iamx3AfIAM9G7wNb5xvkXBPQZS
/+c7Km+uoxkW6fcnu0QFY/J6BmSdjHW6LMm2o2H/RQyOSmbtbil8uRu/hA6P7wz3
nvcwVxtzaBvngzGL5flf9s6raGvItBungdenvOV/mK0x4L1Wp/jkU9NCInzNtcHA
+4b0u+j8qxAw/uCxmaoDYOWSNzQznOuxoopeumWUQ4rjj3shv6PHhcLtNmDiJqkk
SbmXjLrTIm7B3etsUOSbASvWoaRz2aLQdQtSTeqAV8Zn6mOWeK3Zq7OBExdKNBrD
5Cia4S6u+Z/gawH/ksXKwPHFTxErfkiUslpSjDUSkAneOsy0T6mzYrAb6CdaT8eo
2pcL5eqvwaus9XpPb3UzYh+PFruK0c31txhLnxfQaLJQVGp0upg8mwiTA5PJhVbP
YOWZctvEFgBsMdBialAs
=utXr
-----END PGP SIGNATURE-----

--rvjI2VsxUv4AmeutD6cs3oTbrI6IcPH7h--


From nobody Wed Oct 25 17:47:36 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B53113B144 for <xml2rfc@ietfa.amsl.com>; Wed, 25 Oct 2017 17:47:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5oPZBaIFiG4L for <xml2rfc@ietfa.amsl.com>; Wed, 25 Oct 2017 17:47:33 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E22913ACE5 for <xml2rfc@ietf.org>; Wed, 25 Oct 2017 17:47:33 -0700 (PDT)
Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-10v.sys.comcast.net with ESMTP id 7WKbeSS0mydAy7WKbeISbu; Thu, 26 Oct 2017 00:47:33 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-10v.sys.comcast.net with SMTP id 7WKZeED4iVigW7WKaenBNj; Thu, 26 Oct 2017 00:47:32 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v9Q0lVjw001966; Wed, 25 Oct 2017 20:47:31 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v9Q0lVXA001963; Wed, 25 Oct 2017 20:47:31 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: xml2rfc@ietf.org
In-Reply-To: <acaf347e-1882-43f2-da80-0a980002e9e7@gmail.com> (brian.e.carpenter@gmail.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Wed, 25 Oct 2017 20:47:31 -0400
Message-ID: <87a80eohuk.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfGmAZDUIgKu9I2jouGZTKoStICn6sFEcO9U+R4hWxbz905H4uAC6z3H+bWbpqXoZPkviXIP5tcYL3ewpYsa4xob0r9xyhur/69jQs1r0kv1kVDa/EF/m 2TFqlrnO+Z63C6tgIWKn1q8WCKFytGQdoYrXwH4Xh5Ck0Dwe/t4cv1ZQ3doFg2O8C+m3mWpYP5+tWqD4RQhok8U8G9YFLZpOfXI=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/RBrXR5rvxoHR0uelPbIcCdU8R90>
Subject: Re: [xml2rfc] Hangtext spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Oct 2017 00:47:35 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> writes:
> The output looks like this:
>    The dynamic installation property  allows installing an ASA on
>       demand, on any hosts compatible with the ASA.
>
>    The decoupling property  allows controlling resources of a NE from a
>       remote ASA, i.e. an ASA installed on a host machine different from
>       the resources' NE.
>
>    The multiplicity property  allows controlling multiple sets of
>       resources from a single ASA.
>
> Note the two spaces after the hangtext in each case. Idnits issues
> warnings:

Might the problem be that the hangtext doesn't end in a punctuation
mark?

Dale


From nobody Wed Oct 25 18:39:23 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55203139D0B for <xml2rfc@ietfa.amsl.com>; Wed, 25 Oct 2017 18:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7vfVdX666fbB for <xml2rfc@ietfa.amsl.com>; Wed, 25 Oct 2017 18:39:20 -0700 (PDT)
Received: from mail-pg0-x22d.google.com (mail-pg0-x22d.google.com [IPv6:2607:f8b0:400e:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7D3913B144 for <xml2rfc@ietf.org>; Wed, 25 Oct 2017 18:39:20 -0700 (PDT)
Received: by mail-pg0-x22d.google.com with SMTP id p9so1414071pgc.8 for <xml2rfc@ietf.org>; Wed, 25 Oct 2017 18:39:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=kTUjhzJK1r3ygFOLy+W2rL9e5pFdSU26ufojFZZqXqo=; b=n4ylpNleVQmYHurm/WhbwPbYEQVGLF0xqd1lymSyrlvg64mXM1MBf6thEsuzGJKVed +S0gyAXT5G02nl/h4u+r5VzhpCYbwxvpp4bbXN8gUUZXdGeUOjenTD7t3B3WXR0Y3a5q 0wCb1BsXWTeFSy1EEdieAx0Er7+jJ4wTbVvDxuhtcJUnT6z7CJ8n0R8VJBPBxU/0keYA 26y1OmKPoV2rDbB2xeplrQYD3+ZeN0D1myXwcUCRUMDoI4OR9ACqCJlYLKXxEXHJd0Du jqzBgcmFmq3ldWNtIIpJuRG8lFipAw31XhTwoiGedQDxkcFWP8PAKzxPrF8X87ObZUS4 P9Rg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=kTUjhzJK1r3ygFOLy+W2rL9e5pFdSU26ufojFZZqXqo=; b=drTPD0jKK8O0ddIlj+ZbpEpEyu0HS19MQ3dd+3My4XXZGa74aUdKHCXS8L+qf8U0KA 8tovV2HZvLtZ8DTOv+JVM082rkgMK+4EPK+3BBaOmvukYjZZas2TpdkhJr6kRghBKVwP 0goqi4lGnjZPkl3q4JJtExkHlxa+A178Jwmiy94+aecmYk7WKhhd4jhhIcOvRnXl16qR FqyDc1HgaYs+UPxiP08Tqd1Hzp2xm7wMCN1TxslhVGdRaQ8X828xAIFq57AwxWSLgMjH dAgqtY4scMSvRiys/OK5zKhc0rVZgYmwsaxqats1myWUTPqFoFH9HxrIxu9frj0D066O hk5w==
X-Gm-Message-State: AMCzsaVSZKFbsB1uJ63mi+eXxFT0rrEtFeYPCG1D97CKSNgQBTa4fYsu qOsAQeFw2+FUys6LszDIfr7ZUQ==
X-Google-Smtp-Source: ABhQp+Q+LUVI1Knn0j9TIKMNbpouGyzlBv5kc7GRWEzZ8WsggRRDUvOXHg8XPaPxE6DA6zNzM6+6bQ==
X-Received: by 10.98.211.203 with SMTP id z72mr3913803pfk.328.1508981959868; Wed, 25 Oct 2017 18:39:19 -0700 (PDT)
Received: from ?IPv6:2406:e001:3d21:1:28cc:dc4c:9703:6781? ([2406:e001:3d21:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id w69sm6733364pfd.22.2017.10.25.18.39.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Oct 2017 18:39:19 -0700 (PDT)
To: "Dale R. Worley" <worley@ariadne.com>
Cc: xml2rfc@ietf.org
References: <87a80eohuk.fsf@hobgoblin.ariadne.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6807ddb1-5d0a-b303-90e6-55fac12384e4@gmail.com>
Date: Thu, 26 Oct 2017 14:39:22 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <87a80eohuk.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Ap-6sc8iS_RDGJHHDANWRRVga5g>
Subject: Re: [xml2rfc] Hangtext spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Oct 2017 01:39:22 -0000

On 26/10/2017 13:47, Dale R. Worley wrote:
> Brian E Carpenter <brian.e.carpenter@gmail.com> writes:
>> The output looks like this:
>>    The dynamic installation property  allows installing an ASA on
>>       demand, on any hosts compatible with the ASA.
>>
>>    The decoupling property  allows controlling resources of a NE from a
>>       remote ASA, i.e. an ASA installed on a host machine different from
>>       the resources' NE.
>>
>>    The multiplicity property  allows controlling multiple sets of
>>       resources from a single ASA.
>>
>> Note the two spaces after the hangtext in each case. Idnits issues
>> warnings:
> 
> Might the problem be that the hangtext doesn't end in a punctuation
> mark?

Well, yes and no. As Henrik pointed out (thanks!) the hangtext is
a bit unusual by being purely alphanumeric. Of course the workaround
is obvious. However, shortly afterwards in the document we have

   Inputs are:

   [ASA class of type_x]  that specifies which classes ASAs to install,

Another hangtext that doesn't end in a punctuation mark, does generate
a double space, but *doesn't* upset idnits.

So what upset me is one tool producing output that upset another tool.
If there's a rule that hangtext must not end in an alphanumeric, fine,
but that doesn't seem to be in the DTD.

    Brian


From nobody Thu Oct 26 00:15:02 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1DFE13A441 for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 00:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2_qNeyT2IvGo for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 00:14:59 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EA461394E4 for <xml2rfc@ietf.org>; Thu, 26 Oct 2017 00:14:59 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.73.78]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MNIAz-1e59OR1Fn7-006yCI; Thu, 26 Oct 2017 09:14:38 +0200
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Dale R. Worley" <worley@ariadne.com>
Cc: xml2rfc@ietf.org
References: <87a80eohuk.fsf@hobgoblin.ariadne.com> <6807ddb1-5d0a-b303-90e6-55fac12384e4@gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <e74f3277-cc44-7629-316b-a0ce322a4c18@gmx.de>
Date: Thu, 26 Oct 2017 09:14:37 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <6807ddb1-5d0a-b303-90e6-55fac12384e4@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:lSO6EBOJEr1eSLfJwCi98IGKjBcq+Izjuq+mfl9dhj/R7Xudk77 tWiXf943XfUzee5jTmvWnVYZbFVO4Y1vzTC0NnCYkQbIfAmB3SJ1WUBRnfYM7VhXbJ53aWp AomzCe+4pUoEVvHvg6dBBm885Czb8cdb0BiJc9TiwJRzkN+TUdWxTZAj0sh+u0EhdRbgqZN zs01iNNmTil+DogQ4/MRg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:ho3Vcqd1Vlk=:pY1H6DeHS+wNiT3nO9QrBG zXOuo2LuahrfCKG/g8IHrOmf7xhjZ7sYPkdbnayuhlGZA+KBg8XlI1zy5Z0GW5806LnnFKpyN JKutvu4O4HjMCpi89IJn88szKh2289JNag3nwCQORL4r+ps9qIAY688UOcJLijdVBYcIwhgMe G6NWFbypUlOs33UnXDKGE6HSI0Cyr0Yg0XIwl/H18kp5IIBqgSZO3e7xhmxXLJakFZRcEBV0u fDYXVNslLA28VewfK7qJLnhEIH70xSQ7hyBEWoFQW00eDNFy9l6xsZ2cEHP7rcpedumIgb9Yi Rn10QJaa7k+MY2gqSpQnjAHTeyJz9yBuvNLFqedUi1WSyBIUtzxj/PQOr0Ii4N7/9bZ6q4ULR anrupkKASgG3rNYMNxaf5PCzAkY/qoP0LtEuK9zrQuwNDnajL2/3FsEA1Kn9jLbpM5tCrBnBI mDGIW+3xn1Gjt4VC7o9N6++HqsRBKa2bV8YFk3iW73y4R9No+LOW4nieS+gasU1trEjyNvMfb sJ64PyJOxZ/9NnyPeggzZgKVoYjCi9Lty1HBILvOP8qVmWH0dewi0J7alCETTwhtbBAAPHjkp WUIbctFO3ZwM84IfyLhfyeWGazy/jHaMCg942y61/EtT5kQc3b3XLHBTPomE+6TY5z2E+kkOT 3LGCPtGMKSAQ0wQherGRvYofBcgfJyv30l6GvaA/jHzJLNOZOPu+lPIL2PoPAYu1+qWbjWYBM zO0iAIxTh2zgZEVhEttsQoAtQSjDGpVbMaFaufbuuGCGiYg0/N7eyC+0fXUUoaf4HrC1+/GAD 87jF7jeZYSPB2bUR4x2zq6nuWPzu3r9WRf1sNtsiUTAaUykj5o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/s4UaGq011UxkGcLQM9yZ79fH9UE>
Subject: Re: [xml2rfc] Hangtext spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Oct 2017 07:15:01 -0000

On 2017-10-26 03:39, Brian E Carpenter wrote:
> ...
> So what upset me is one tool producing output that upset another tool.
> If there's a rule that hangtext must not end in an alphanumeric, fine,
> but that doesn't seem to be in the DTD.
> ...

By definition of what DTDs can do and can not.

That said: hangText doesn't need to end with punctuation.

Given that we're approaching V3, it would make sense to think about how 
your text would actually be written using the new V3 list elements, and 
how it would display then.

Best regards, Julian


From nobody Thu Oct 26 01:32:11 2017
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F33213F43E for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 01:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CL6058T9ge3j for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 01:32:09 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6874913AB34 for <xml2rfc@ietf.org>; Thu, 26 Oct 2017 01:32:09 -0700 (PDT)
Received: from h-99-61.a357.priv.bahnhof.se ([82.196.99.61]:57351 helo=[192.168.1.120]) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1e7daA-0000f8-1X; Thu, 26 Oct 2017 01:32:06 -0700
To: "Dale R. Worley" <worley@ariadne.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <87a80eohuk.fsf@hobgoblin.ariadne.com>
Cc: xml2rfc@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <4861d9e0-d0f6-e40c-95f9-359f0360c65f@levkowetz.com>
Date: Thu, 26 Oct 2017 10:31:58 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <87a80eohuk.fsf@hobgoblin.ariadne.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1DngwE60R5hVSmfrilotU0xGV7nRqGE4b"
X-SA-Exim-Connect-IP: 82.196.99.61
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, brian.e.carpenter@gmail.com, worley@ariadne.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/q9YJdTe2limhiTH0VlIaMhZ1T8I>
Subject: Re: [xml2rfc] Hangtext spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Oct 2017 08:32:10 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--1DngwE60R5hVSmfrilotU0xGV7nRqGE4b
Content-Type: multipart/mixed; boundary="o3hBBUwq3jIXjtdaxLg816M6pDah4FIed";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: "Dale R. Worley" <worley@ariadne.com>,
 Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: xml2rfc@ietf.org
Message-ID: <4861d9e0-d0f6-e40c-95f9-359f0360c65f@levkowetz.com>
Subject: Re: [xml2rfc] Hangtext spacing
References: <87a80eohuk.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87a80eohuk.fsf@hobgoblin.ariadne.com>

--o3hBBUwq3jIXjtdaxLg816M6pDah4FIed
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


On 2017-10-26 02:47, Dale R. Worley wrote:
> Brian E Carpenter <brian.e.carpenter@gmail.com> writes:
>> The output looks like this:
>>    The dynamic installation property  allows installing an ASA on
>>       demand, on any hosts compatible with the ASA.
>>
>>    The decoupling property  allows controlling resources of a NE from =
a
>>       remote ASA, i.e. an ASA installed on a host machine different fr=
om
>>       the resources' NE.
>>
>>    The multiplicity property  allows controlling multiple sets of
>>       resources from a single ASA.
>>
>> Note the two spaces after the hangtext in each case. Idnits issues
>> warnings:
>=20
> Might the problem be that the hangtext doesn't end in a punctuation
> mark?

idnits would probably not complain if there was a punctuation mark.  But
the idnits warning is just a warning, to be disregard it if the spacing
is intentional.


	Henrik


--o3hBBUwq3jIXjtdaxLg816M6pDah4FIed--

--1DngwE60R5hVSmfrilotU0xGV7nRqGE4b
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJZ8Z1+AAoJEE6bV0uPuxcanb4P/j04rOa5eUcV1Y8FT5x5EsJe
eu0aMGVOaAMB5nfoUXbilmGUtE9sxnoErYDrPNfhBDYFkVDB4xqqsCelU9gV/+O2
rXc1GH7XI3EQMU3YrHBrW0ev3tKW4IJ1BGs5DdyHAu054vgSKZN5ARRN6/AAktVY
e4Ec7FLhoSpY4iHgDiHw9fxMxk3UmcxObWDEgIQs4IOlUpThNGcbJdnHGTuZd/vB
0NCpi2T2jrzp6/hGoqt6GH+BhLO8PY8tMUVmf+ZBPzwr7yKAaeBMldPTtnUe28Jq
keaqg6v5R8G1kyadab2GJjWY8ZfFmEnN19meSy3sg17s7QFAUvGSo7FnKUT08q7t
c+JGfcx4kVhdri3CO3nk4fFL3/6s22+yhQ41xhuMtJoT+DsGh4P50mcjd5BrL250
SeiCn6Y4258JoGdbHqDouYp1oa6XGuPQDwi6XXKChIV1dhoAG614UiKfHty9l+PF
pfxIeXxZWT4PtOc7JQjRUAEsWw8ML3A28bD08lAtXViXyKW9pCSo85jplchM17dB
iiutsqseBzmOuRm1jdP/vivYPR2dasjs26Pp64IP4WGhkTylKfzzPEOd8eATEPZL
SpM8Pgdk9LazMrOxGRVjsLUksWYIGJy8qqGrskTQhtI9PjyS0lcjUQNE+MxeHE2K
IemgMazxD2vs3qlSfLnf
=tmr+
-----END PGP SIGNATURE-----

--1DngwE60R5hVSmfrilotU0xGV7nRqGE4b--


From nobody Thu Oct 26 12:50:15 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F338813946F for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 12:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MJp0CgbIp9RQ for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 12:50:13 -0700 (PDT)
Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AEBE13836A for <xml2rfc@ietf.org>; Thu, 26 Oct 2017 12:50:13 -0700 (PDT)
Received: by mail-pg0-x230.google.com with SMTP id p9so3503452pgc.8 for <xml2rfc@ietf.org>; Thu, 26 Oct 2017 12:50:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=O8taISerkRobKCfQ7ChReFqn4Ihcy483RurWsVXGo4I=; b=GVvA6a2Ec4vrNq16OlG0yfKRf5zLnpWEQpEj9JfveFdEqpaQn82KZnvnMs5caHRVcp RI2G/xGMbmYp7dDWVNoW0Bk8i7hJEBF8CuhHwm7V7D92nxyK6E6L0O6VLx80qlHPqfgA i9/QEc5U8xNQUiWKg+pRyF3+rG2lwJJdHciuFW2hcv9rdzSXyi5wPzMoNH1v57+HTAwy 5jKk4tY6Pn1+FnXurRrnC87NTRF+mDazSEAxCRmyGcze5OirZJDxsaw5O14S3JubVr/S alYFPCK0SgmcP9LlDu777QJoL0W22VUwAAiFOnJ1TtDX0O8TMv3o2dWjN6UV4Xqxyk7t lU3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=O8taISerkRobKCfQ7ChReFqn4Ihcy483RurWsVXGo4I=; b=Ez6YbGIup9de7z1cYxe9RwHASTMVSzWOLTWEDkX39ezx89215O+Rqn7RRYm14aVZgo JqocoHIGqa7N155inxQRxPKG+G+nyZVS/VWqgncy4xQqBlpZYmpk7/GnjzYKpjH6zqdU iRTTF1TVrugHzXS/d0zsLcgVV2iUeRWZD90Wyxi0AMQABqLj62RW7SjKMHFI9Fu92E9L Wf0l7irLY1ruLpvTS+50Y4zlEqU1drEoXbnV9BqqpwGaA0gkc7hOMHYAniigZXia+R7C CR4SdlWA+abfJlYG8o8hzHtaPurMY/1zfjAOthqFZ0VCNZn9xiJWrhrI9dmvdvpJ8I+t lYvw==
X-Gm-Message-State: AMCzsaXCUp7SCP/eP/OpWZBhoOJ9QYhmp5zkIjQhgqJZjntHqb5gVZxA U0pQbI1sB31v3eS9xF70EvHjgA==
X-Google-Smtp-Source: ABhQp+TzEpWP0c0MdjZ4u5mtHXG1eyL23jm/IQOK9wZOZAm3KyfKdz9UzpI4oMj7+f5Oh5Fmb5P7zA==
X-Received: by 10.99.121.201 with SMTP id u192mr5841232pgc.69.1509047412677; Thu, 26 Oct 2017 12:50:12 -0700 (PDT)
Received: from ?IPv6:2406:e001:3d21:1:28cc:dc4c:9703:6781? ([2406:e001:3d21:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id i62sm10895969pfe.73.2017.10.26.12.50.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Oct 2017 12:50:11 -0700 (PDT)
To: Henrik Levkowetz <henrik@levkowetz.com>, "Dale R. Worley" <worley@ariadne.com>
Cc: xml2rfc@ietf.org
References: <87a80eohuk.fsf@hobgoblin.ariadne.com> <4861d9e0-d0f6-e40c-95f9-359f0360c65f@levkowetz.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <fce3819e-4b49-ba4f-d990-87c5b10c09ee@gmail.com>
Date: Fri, 27 Oct 2017 08:50:16 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <4861d9e0-d0f6-e40c-95f9-359f0360c65f@levkowetz.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/qHxnYzIQ_174h2jQ3RtXO2kcqXc>
Subject: Re: [xml2rfc] Hangtext spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Oct 2017 19:50:15 -0000

On 26/10/2017 21:31, Henrik Levkowetz wrote:
> 
> On 2017-10-26 02:47, Dale R. Worley wrote:
>> Brian E Carpenter <brian.e.carpenter@gmail.com> writes:
>>> The output looks like this:
>>>    The dynamic installation property  allows installing an ASA on
>>>       demand, on any hosts compatible with the ASA.
>>>
>>>    The decoupling property  allows controlling resources of a NE from a
>>>       remote ASA, i.e. an ASA installed on a host machine different from
>>>       the resources' NE.
>>>
>>>    The multiplicity property  allows controlling multiple sets of
>>>       resources from a single ASA.
>>>
>>> Note the two spaces after the hangtext in each case. Idnits issues
>>> warnings:
>>
>> Might the problem be that the hangtext doesn't end in a punctuation
>> mark?
> 
> idnits would probably not complain if there was a punctuation mark.  But
> the idnits warning is just a warning, to be disregard it if the spacing
> is intentional.

Correct. The visual effect is a bit  ugly though. Clearly we will work
around it for this particular draft; and I agree with Julian that
if anything should change, it should be in the context of v3.

    Brian


From nobody Thu Oct 26 21:19:33 2017
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E179813F63C for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 21:19:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F445AYnA90rx for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 21:19:30 -0700 (PDT)
Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7301F1375C9 for <xml2rfc@ietf.org>; Thu, 26 Oct 2017 21:19:30 -0700 (PDT)
Received: by mail-wr0-x236.google.com with SMTP id 15so5000303wrb.5 for <xml2rfc@ietf.org>; Thu, 26 Oct 2017 21:19:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=3nDGGzBptj7igwP9JcQJaIgemX5ovCCZNlIG+RZQaCs=; b=dbyjH3zxgUCcjCRHi1P8v8qB+Yu5Qu7nHaHkR4z33jLSIIyZqhyrQkSVl6fAOgoh7J y9IsDmfKiIKPCmpraIG4AF2tYsjoQJ7MrwW/mXenf7tfWH4oD9/vdYgv0KtVu5AGwquF AyQjMBX31bL17pgtNs9QMaHAbq48HSL+CQGWna+6I3UrRqX/AWSRaysqOycuD2wW+VkV pgDnAzr8ZSHHUIWyptM8uDEIx9K27YSqMbOwE51roqBZj9OSXZn21O3QKSTktBQUgGAv K6npkIMPbQf0S559QklUXTwEZUs4C+iGfN01GGaoKEor6mQZPsASC++a2XBC6op8ebOI 0WZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=3nDGGzBptj7igwP9JcQJaIgemX5ovCCZNlIG+RZQaCs=; b=beCE32QgbfzoKhd5f/QBX0Gg96p71yNgnV6YCncCqwSQ+VoLInDiChBMnMrwk00AOK sCK7he/ZVHL7XwOc6GEThAmdgplKG+PQzhxdFTN8kDgMGhFAwyDFpIpk5sJsnZUlNmAA 1sY84b5DdsR0htWPXMqypVdZzpIy2Zc9awQB5453VveTEhMNGzEgFs4DIViDoKCITb+P DG+tx9UMrAfO85ACAxGRB95igTQFIUjKLD927nI1CJzp14m4fpAlMi87pbgKrSlnGvoc X7VAhRmfnU1CESndaf9JoPk+JV6Vzo4TI1MTUiIe9QQlubkAsPwaezxHZSCRJV8T4O5V o6Qg==
X-Gm-Message-State: AMCzsaUT6Gq8SDVhGiPOjrhNnLde7nLHa/h1J6uvLaZrd/jv3A+5/zdk CXdoIaRnpgJvpzPVA0WLSlQ=
X-Google-Smtp-Source: ABhQp+TOeLpJQSJI6rBTu8q7vosOjt8lBr70euaYYFfgj7/ruWm5F+NrIjkuarsAQUDYqwp49/iUBg==
X-Received: by 10.223.199.9 with SMTP id k9mr7436158wrg.145.1509077968998; Thu, 26 Oct 2017 21:19:28 -0700 (PDT)
Received: from [172.20.3.182] ([94.56.205.4]) by smtp.gmail.com with ESMTPSA id c67sm598414wmd.25.2017.10.26.21.19.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Oct 2017 21:19:27 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <EBB95B6A-50CA-4781-8039-8E52A0E11511@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_940DDB47-E631-4833-B689-0806165A0203"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Date: Fri, 27 Oct 2017 08:19:24 +0400
In-Reply-To: <4861d9e0-d0f6-e40c-95f9-359f0360c65f@levkowetz.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, xml2rfc@ietf.org
To: Henrik Levkowetz <henrik@levkowetz.com>
References: <87a80eohuk.fsf@hobgoblin.ariadne.com> <4861d9e0-d0f6-e40c-95f9-359f0360c65f@levkowetz.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/amb6OB9HFrF4GvXocKqqnTQkDOQ>
Subject: Re: [xml2rfc] Hangtext spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2017 04:19:32 -0000

--Apple-Mail=_940DDB47-E631-4833-B689-0806165A0203
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> On Oct 26, 2017, at 12:31 PM, Henrik Levkowetz <henrik@levkowetz.com> =
wrote:
>=20
> idnits would probably not complain if there was a punctuation mark.  =
But
> the idnits warning is just a warning, to be disregard it if the =
spacing
> is intentional.

Except that reviewers request that drafts be "idnits clean" (produce no =
idnits comments), in which case an error that the author ignored becomes =
mandatory to fix.

--Apple-Mail=_940DDB47-E631-4833-B689-0806165A0203
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAlnys8wACgkQEhdRnd2G
P+A2MA/+J+VgyPPlu/6mqx0na4TaTyqJd/lwyXQqgIMoUWg3jbo1sIhQ5aRMICXu
6fStVi9z6J5Uw3joHzxpXzvTt9nA4hrzjHm+pYmzCk1C7mKHbhslZWd5IOIFa1kQ
9B1gVycZ/4AHT8ag1DBY2nhGMyfjUowkWiavjxg66SpCXFTkOyuv6u12Lq1kpnWo
SLnO3ljUKRIZ5MN8OU0xgfnKzmGJqT5OfkGdmOBJ0kmjgpzW2QCtK8Cid/MgNxDR
HjukV2lD86Ladsjpr5e6QdaJgUNG5yCBBpEnkhP2XipbvvSHGnhkMMjGnkjlBpw3
hQz6lVNYhD0JKZ2vyAysqJQd00qoXQ1X7h0L1XpuAc1R95aPlJIx0xk9aaYjtgib
+bqUfDQeSXzjS65AdMxFC1nWMZ/1E0oHdDjuF5Nu4JUYzyqVKlb9Aso6s5t8P1oa
UqouMYXlye2+bm/b5PwOw/l7epl8laAIsJfDFmymTqbFIq1tQmdiYEN9zJlFeez3
KIvwYWGF7/mFRj48Hl1geeict1xuhBQcRZKEhS/6tDWBUMMkbV0DpCp7ypCsedDV
Kh7CaDXS+h8Hy01dt/0a9Q4vxYJgf5ho0j76l+KlIAFiRnKP627OF4M6Tngl4efC
wM5LX5nV3YRYCu47kSUcr7RYPkDyEy9JLzil2KN5f7EN9gUoAvU=
=Ra32
-----END PGP SIGNATURE-----

--Apple-Mail=_940DDB47-E631-4833-B689-0806165A0203--


From nobody Thu Oct 26 22:38:54 2017
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1070013A41F for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 22:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Rgd1JoM1VAB for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 22:38:52 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC2E21389BC for <xml2rfc@ietf.org>; Thu, 26 Oct 2017 22:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v9R5clUa028862; Fri, 27 Oct 2017 07:38:47 +0200 (CEST)
Received: from client-0013.vpn.uni-bremen.de (client-0013.vpn.uni-bremen.de [134.102.107.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3yNXjg2BDDzDWkk; Fri, 27 Oct 2017 07:38:47 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <EBB95B6A-50CA-4781-8039-8E52A0E11511@gmail.com>
Date: Fri, 27 Oct 2017 07:38:46 +0200
Cc: Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 530775526.3985-c530ec361db2ba04dcf33c348acda29d
Content-Transfer-Encoding: quoted-printable
Message-Id: <1156366F-42B8-458A-B758-7F63E5D32B1C@tzi.org>
References: <87a80eohuk.fsf@hobgoblin.ariadne.com> <4861d9e0-d0f6-e40c-95f9-359f0360c65f@levkowetz.com> <EBB95B6A-50CA-4781-8039-8E52A0E11511@gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/YaD0RTFehZic9sJLtnzza6KjOI8>
Subject: Re: [xml2rfc] Hangtext spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2017 05:38:53 -0000

On Oct 27, 2017, at 06:19, Fred Baker <fredbaker.ietf@gmail.com> wrote:
>=20
> Except that reviewers request that drafts be "idnits clean" (produce =
no idnits comments), in which case an error that the author ignored =
becomes mandatory to fix.

Well, then it might be time to explain the purpose of this tool to them.
(Is there a convenient place to link to that explains this?)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Oct 26 23:26:37 2017
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B4F913B10F for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 23:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBN9FAr5reEn for <xml2rfc@ietfa.amsl.com>; Thu, 26 Oct 2017 23:26:34 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EFC113B105 for <xml2rfc@ietf.org>; Thu, 26 Oct 2017 23:26:34 -0700 (PDT)
Received: from h-99-61.a357.priv.bahnhof.se ([82.196.99.61]:60039 helo=[192.168.1.120]) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1e7y6D-0002m9-9G; Thu, 26 Oct 2017 23:26:33 -0700
To: Carsten Bormann <cabo@tzi.org>, Fred Baker <fredbaker.ietf@gmail.com>
References: <87a80eohuk.fsf@hobgoblin.ariadne.com> <4861d9e0-d0f6-e40c-95f9-359f0360c65f@levkowetz.com> <EBB95B6A-50CA-4781-8039-8E52A0E11511@gmail.com> <1156366F-42B8-458A-B758-7F63E5D32B1C@tzi.org>
Cc: xml2rfc@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <b60e4bed-e5ec-049f-a35c-dcba6c4a8578@levkowetz.com>
Date: Fri, 27 Oct 2017 08:26:16 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <1156366F-42B8-458A-B758-7F63E5D32B1C@tzi.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="M1j5M2vT5VJLnpLVRHvipnksAE3uuo9UU"
X-SA-Exim-Connect-IP: 82.196.99.61
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, fredbaker.ietf@gmail.com, cabo@tzi.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/-vow131yAAEHqvJsc-tYFUO45J8>
Subject: Re: [xml2rfc] Hangtext spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2017 06:26:36 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--M1j5M2vT5VJLnpLVRHvipnksAE3uuo9UU
Content-Type: multipart/mixed; boundary="WD0dBdHKMi2KBveQJIwI1JcALQLrqph40";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: Carsten Bormann <cabo@tzi.org>, Fred Baker <fredbaker.ietf@gmail.com>
Cc: xml2rfc@ietf.org
Message-ID: <b60e4bed-e5ec-049f-a35c-dcba6c4a8578@levkowetz.com>
Subject: Re: [xml2rfc] Hangtext spacing
References: <87a80eohuk.fsf@hobgoblin.ariadne.com>
 <4861d9e0-d0f6-e40c-95f9-359f0360c65f@levkowetz.com>
 <EBB95B6A-50CA-4781-8039-8E52A0E11511@gmail.com>
 <1156366F-42B8-458A-B758-7F63E5D32B1C@tzi.org>
In-Reply-To: <1156366F-42B8-458A-B758-7F63E5D32B1C@tzi.org>

--WD0dBdHKMi2KBveQJIwI1JcALQLrqph40
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


On 2017-10-27 07:38, Carsten Bormann wrote:
> On Oct 27, 2017, at 06:19, Fred Baker <fredbaker.ietf@gmail.com> wrote:=

>>=20
>> Except that reviewers request that drafts be "idnits clean" (produce n=
o idnits comments), in which case an error that the author ignored become=
s mandatory to fix.
>=20
> Well, then it might be time to explain the purpose of this tool to them=
=2E
> (Is there a convenient place to link to that explains this?)

I added some text to the idnits about page.  I'll also include this in
the help text and manpage when I do the idnits rewrite for the RFC format=

tools at the beginning of next year.

See https://tools.ietf.org/tools/idnits/about


Best regards,

	Henrik



--WD0dBdHKMi2KBveQJIwI1JcALQLrqph40--

--M1j5M2vT5VJLnpLVRHvipnksAE3uuo9UU
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJZ8tGRAAoJEE6bV0uPuxcaQykP/RK3R7WgpsRfp1trRUX0Cv/h
tDKnnMjAYNcTr8rl5KsaAmnQk5w9qYeEvhZmWHL4c4qcqUU/Cb0UWPDSX+5E5/2l
zHMKnovXCM2ebXBBezLu2B1NVvwE+2xGtkTzr0HL94fZZDI1UNDZJeObi8zdVv9h
vqYO/tP7LoPzBjR7I4Rb8EtdATfIFPfpImVnWY7XULkuJ85OX6Owr0v2rxp0HVok
w8reYl9F6UA6xHwEllvRCwk5+7D0xLr1aMl4jU1wz//AaAEAd2TJMVxicSaiMnq+
aUFE62koeQMeoCVC4cdW4SCxSIq9ysWiVNmB0BR0FKQx43jM8mHDN1M/hTA8v2EY
SmATY+3SwV5KyYdhXxd36xO5k38NFv7UAGVYtfje5g864zLkh/Fads7+lLA4mOEc
xdBJRH6PeHGMnj+f5syp+VBK93N9uWEBwGHghZtLYGahT4SuPtwNy+rcVUvCvH42
97KE52Ln3QTDhM/bxuWnBz1ry1Ky40H1GyvqFI5GicrXAI30+cyJtWkoEmd2y/Vy
nXDIDPTZrm53XWzN9FRheUJGKNNg5EmHWzzKkAtSr2wfk3wkBjapieALZblk1vfq
9qt17K4ssjjepSa6oEPR9LibKYf71cA0AoWi7KW6ZMUGBnXWHKV64wjs+fXpYet9
fPog8YN0Xpt3pgHaGbCL
=aaIQ
-----END PGP SIGNATURE-----

--M1j5M2vT5VJLnpLVRHvipnksAE3uuo9UU--


From nobody Fri Oct 27 04:15:30 2017
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9AB213B109 for <xml2rfc@ietfa.amsl.com>; Fri, 27 Oct 2017 04:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UGcGHr2sWWDc for <xml2rfc@ietfa.amsl.com>; Fri, 27 Oct 2017 04:15:26 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 562D313F4D3 for <xml2rfc@ietf.org>; Fri, 27 Oct 2017 04:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v9RBFMJm000845; Fri, 27 Oct 2017 13:15:22 +0200 (CEST)
Received: from [100.72.192.11] (ip-109-47-1-11.web.vodafone.de [109.47.1.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3yNhB21vhwzDWsG; Fri, 27 Oct 2017 13:15:22 +0200 (CEST)
Content-Type: multipart/alternative; boundary=Apple-Mail-9A3F1F6D-AAED-4324-9D91-92E88F91FE13
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPhone Mail (15A432)
In-Reply-To: <b60e4bed-e5ec-049f-a35c-dcba6c4a8578@levkowetz.com>
Date: Fri, 27 Oct 2017 13:15:20 +0200
Cc: Fred Baker <fredbaker.ietf@gmail.com>, xml2rfc@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <1F072E9D-B40F-4B11-8E32-FD9BE1BE9653@tzi.org>
References: <87a80eohuk.fsf@hobgoblin.ariadne.com> <4861d9e0-d0f6-e40c-95f9-359f0360c65f@levkowetz.com> <EBB95B6A-50CA-4781-8039-8E52A0E11511@gmail.com> <1156366F-42B8-458A-B758-7F63E5D32B1C@tzi.org> <b60e4bed-e5ec-049f-a35c-dcba6c4a8578@levkowetz.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/6RExPC0ATRSqDhV6ngZEGfkUVZ4>
Subject: Re: [xml2rfc] Hangtext spacing
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2017 11:15:29 -0000

--Apple-Mail-9A3F1F6D-AAED-4324-9D91-92E88F91FE13
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Nice!  Thank you.=20

Sent from mobile

> On 27. Oct 2017, at 08:26, Henrik Levkowetz <henrik@levkowetz.com> wrote:
>=20
>=20
>> On 2017-10-27 07:38, Carsten Bormann wrote:
>>> On Oct 27, 2017, at 06:19, Fred Baker <fredbaker.ietf@gmail.com> wrote:
>>>=20
>>> Except that reviewers request that drafts be "idnits clean" (produce no i=
dnits comments), in which case an error that the author ignored becomes mand=
atory to fix.
>>=20
>> Well, then it might be time to explain the purpose of this tool to them.
>> (Is there a convenient place to link to that explains this?)
>=20
> I added some text to the idnits about page.  I'll also include this in
> the help text and manpage when I do the idnits rewrite for the RFC format
> tools at the beginning of next year.
>=20
> See https://tools.ietf.org/tools/idnits/about
>=20
>=20
> Best regards,
>=20
>    Henrik
>=20
>=20

--Apple-Mail-9A3F1F6D-AAED-4324-9D91-92E88F91FE13
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">Nice! &nbsp;Thank you.&nbsp;<br><br><div id=
=3D"AppleMailSignature">Sent from&nbsp;<span style=3D"font-size: 13pt;">mobi=
le</span></div><div><br>On 27. Oct 2017, at 08:26, Henrik Levkowetz &lt;<a h=
ref=3D"mailto:henrik@levkowetz.com">henrik@levkowetz.com</a>&gt; wrote:<br><=
br></div><blockquote type=3D"cite"><div><span></span><br><span>On 2017-10-27=
 07:38, Carsten Bormann wrote:</span><br><blockquote type=3D"cite"><span>On O=
ct 27, 2017, at 06:19, Fred Baker &lt;<a href=3D"mailto:fredbaker.ietf@gmail=
.com">fredbaker.ietf@gmail.com</a>&gt; wrote:</span><br></blockquote><blockq=
uote type=3D"cite"><blockquote type=3D"cite"><span></span><br></blockquote><=
/blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>Except=
 that reviewers request that drafts be "idnits clean" (produce no idnits com=
ments), in which case an error that the author ignored becomes mandatory to f=
ix.</span><br></blockquote></blockquote><blockquote type=3D"cite"><span></sp=
an><br></blockquote><blockquote type=3D"cite"><span>Well, then it might be t=
ime to explain the purpose of this tool to them.</span><br></blockquote><blo=
ckquote type=3D"cite"><span>(Is there a convenient place to link to that exp=
lains this?)</span><br></blockquote><span></span><br><span>I added some text=
 to the idnits about page. &nbsp;I'll also include this in</span><br><span>t=
he help text and manpage when I do the idnits rewrite for the RFC format</sp=
an><br><span>tools at the beginning of next year.</span><br><span></span><br=
><span>See <a href=3D"https://tools.ietf.org/tools/idnits/about">https://too=
ls.ietf.org/tools/idnits/about</a></span><br><span></span><br><span></span><=
br><span>Best regards,</span><br><span></span><br><span> &nbsp; &nbsp;Henrik=
</span><br><span></span><br><span></span><br></div></blockquote></body></htm=
l>=

--Apple-Mail-9A3F1F6D-AAED-4324-9D91-92E88F91FE13--