
From nobody Tue Oct  1 09:00:45 2019
Return-Path: <gsenopu@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F23B120992; Tue,  1 Oct 2019 09:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 mjbtqyegRpFc; Tue,  1 Oct 2019 09:00:32 -0700 (PDT)
Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com [IPv6:2607:f8b0:4864:20::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 80B9B120A28; Tue,  1 Oct 2019 08:51:21 -0700 (PDT)
Received: by mail-oi1-x236.google.com with SMTP id k20so14881808oih.3; Tue, 01 Oct 2019 08:51:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uQ5xFTiNLEriw8mK9KPnSSRyGpTtV3bxfUGCAFwDqvo=; b=hsp2JdM/y9LXaMgolE+zIrTiFrlin2dBFue0E68p1z5fDp4ZzLF6SC2X8Y913WXnOA IJJtkYT1pFd7wxuI07wJ0vCcjETebZUgfd3rlfmsP6xRPnli5I0mFVVEgp0PEi/ZkOn6 VWFLPh6LNzvESYfRAZU+XNlWFRnxcf0L0q5gEkqFl5B5ovpwGKqib+KvV8uPde8gE5I4 nkoX2iCD/2Ga9gqBRewWVxemDOJoYR9uZovNg8S4941TFq3J4Ng4JCdVc82Ev2s3x87K hoBxaGsEDpw2tYATpGiERvuHbRsSKahU3k5ut0dyFzU1dAOw0U1A0ECTTANCJBjNpotF mFgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uQ5xFTiNLEriw8mK9KPnSSRyGpTtV3bxfUGCAFwDqvo=; b=JcPh40Cwt75y8U38tMLfpucS7kvzD/ax86ks2lkSu0ZC+2HZU04TQJS/790jHGjal2 dRw5evHqniGKUAUkOCEFcOpaT84G8wZ2yuOzSkFQXvQWLpc9PYlaV18+4Vy5tgTHqi4W O5robzqQNxO2Q5WksUPWEsPVFT8eXCWx2BUXGZtYotUf5g8fB+isRqszedR8I77L6Z+7 9NBLaLxwC7HlnF3FCkdUS7t+XXAtqPUVP0oCs0ieFuK1GlssgA8FMKPC8I11Y8RvRZ0p AIO5m/EfzMq7ewwL0IwfJmw/ncDpKRypfZaVUvMypDDqTPLJzn6LCZjf1JXTPnU2jtjY 3hRA==
X-Gm-Message-State: APjAAAULgg2M84jiTSWV5w2MuzaIvQZc+34JK9NLI/SdSd4E6QhfHJx3 xDUjdOp35amHO/FUCDF+M7z9uo5ertI/cqKuHKU=
X-Google-Smtp-Source: APXvYqyixkRlj2b3BAlH2VR4F0/45pvMptUPQRhqTADvtonByBNuIxPwe0g+rBk1wM0k+Ygr/kO7DmsMywospuGrqsc=
X-Received: by 2002:a05:6808:b07:: with SMTP id s7mr4027169oij.134.1569945080760;  Tue, 01 Oct 2019 08:51:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:2f61:0:0:0:0:0 with HTTP; Tue, 1 Oct 2019 08:51:20 -0700 (PDT)
In-Reply-To: <CAKi_AEv=K_c73eRTOMjnVK-LOS9X7YydiFsJkW5XGPp7Wz+bRQ@mail.gmail.com>
References: <791b33b8-4696-f69c-aca3-8838b2caafd8@sectigo.com> <CAChr6SyYB9mHAx+AQSTVQvb2g5FvAD03KQ_Ta7=RH+6Pt8dKrw@mail.gmail.com> <77F8C1C2AAB5AE251285436F@172.20.2.211> <30deb3a8-c24f-1f38-2701-aa1d68b6adba@nostrum.com> <CAKi_AEuhiAEbHgQ15=KL2af5qL3ei-NQjHd6UCpxqbxoHCfqvQ@mail.gmail.com> <CAKi_AEuxuiPZ4=KoCcH_rVa1GEhgVBKeC3SOP3h4W1bUi6aq-g@mail.gmail.com> <CAKi_AEt2A3MbJOrxZvkqKtkFT8BSmQ_PpFRor0OpQ6gEbgfNnA@mail.gmail.com> <CAKi_AEtqPm79_HkFcURjekgbKvS6ZOuFhiEWqdMue8=kpOjGXg@mail.gmail.com> <CAKi_AEtSLVdQFv+R3mRM3AVHVeB+FOi+a5R6XQEcK3vqVA+pWA@mail.gmail.com> <CAKi_AEv=K_c73eRTOMjnVK-LOS9X7YydiFsJkW5XGPp7Wz+bRQ@mail.gmail.com>
From: Guntur Wiseno Putra <gsenopu@gmail.com>
Date: Tue, 1 Oct 2019 22:51:20 +0700
Message-ID: <CAKi_AEstdAtr=MteB18VC3pCSUDC6WPndY5ko0-bVPMTRgp6SQ@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: John C Klensin <john-ietf@jck.com>, "art@ietf.org" <art@ietf.org>,  "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, "tsoupi@uic.edu" <tsoupi@uic.edu>,  "info@playthemagic.com" <info@playthemagic.com>
Content-Type: multipart/alternative; boundary="000000000000db11a10593db527e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/BfnapKbgl9WZZ6-9-I3Bey9ntt8>
Subject: Re: [art] [arch-d] BCP 190, draft-nottingham-for-the-users, and a generalization
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Oct 2019 16:00:37 -0000

--000000000000db11a10593db527e
Content-Type: text/plain; charset="UTF-8"

Dear architecture-discuss,


To share what may be inspiring:

If there are society of networks and networks of societies may we say also
about pedagogy of networks and networks of pedagogies: thus we are
supposedly combining those notions on "society", "networks", "languages"
and "great operations of capital" (those of M. Castells', J.F. Lyotard's
and G. Deleuze and F. Guattari's)...


Regard,
Guntur Wiseno Putra

Pada Minggu, 11 Agustus 2019, Guntur Wiseno Putra <gsenopu@gmail.com>
menulis:

> Dear architecture-discuss,
>
> (There are things need to correct on * Note)
>
> To share what I have found out: if such public installations inspire/is
> about exploring musicality of diferent architectural features --as it was
> attempted by "Building Music" of Electronic Visual Laboratory UIC:
>
>
> https://www.evl.uic.edu/entry.php?id=1985
>
>
> *Note:
> - There is a correction for Daria Tsoupikova e-mail address of my previous
> messages on Marcos Novak'"Liquid Architecture in Cyberspace"
> - Should I add CC: info@playthemagic.com as it is of the "Building Music"
> page which may have importances.
>
>
> Regard,
> Guntur Wiseno Putra
>
>
>
>
>
> Dear architecture-discuss,
>
>
>
> To share what I have found out: if such public installations inspire/is
> about exploring musicality of diferent architectural features --as it was
> attempted by "Building Music" of Electronic Visual Laboratory UIC:
>
>
> https://www.evl.uic.edu/entry.php?id=1985
>
>
> *Note: There is a correction for Daria Tsoupikova e-mail address of my
> previous messages...
>
>
> Regard,
> Guntur Wiseno Putra
>
>
>
> Pada Minggu, 11 Agustus 2019, Guntur Wiseno Putra <gsenopu@gmail.com>
> menulis:
>
>> Dear architecture-discuss,
>>
>>
>>
>> To share what I have found out: if such public installations inspire/is
>> about exploring musicality of diferent architectural features --as it was
>> attempted by "Building Music" of Electronic Visual Laboratory UIC:
>>
>>
>> https://www.evl.uic.edu/entry.php?id=1985
>>
>>
>> *Note: There is a correction for Daria Tsoupikova e-mail address of my
>> previous messages...
>>
>>
>> Regard,
>> Guntur Wiseno Putra
>>
>> Pada Minggu, 11 Agustus 2019, Guntur Wiseno Putra <gsenopu@gmail.com>
>> menulis:
>>
>>> Dear architecture-discuss,
>>>
>>> Forgive me for typing errors in previous message...
>>>
>>> An alternative link to the posting on Marcos Novak's "Liquid
>>> Architecture in Cyberspace" at public@informationarchitecture@w3.org I
>>> mentioned earlier is
>>>
>>> https://lists.w3.org/Archives/Public/public-informationarchi
>>> tecture/2019May/0000.html
>>>
>>> (which was "403 Forbidden: Request forbidden by administrative rules"
>>> the last time I checked up minutes ago)
>>>
>>> Or, if going directly toward the text:
>>>
>>> https://www.evl.uic.edu/datsoupi/coding/readings/1991_Novak_Liquid.pdf
>>>
>>> Thank to Martin Dodge for suggesting Marcos Novak's architecture in
>>> www.cybergeography.org bringing me to Daria Tsoupukiva's lecture
>>> providing the reading...
>>>
>>>
>>>
>>> Regard,
>>> Guntur Wiseno Putra
>>>
>>> Pada Minggu, 11 Agustus 2019, Guntur Wiseno Putra <gsenopu@gmail.com>
>>> menulis:
>>>
>>>> Dear architecture-discuss,
>>>>
>>>> An alternative link to the posting on Marcos Nocak'S "Liquid
>>>> Architecture in Cyberspace" at public@informationarchitecture@w3.org
>>>> I mentioned earlier is
>>>>
>>>> https://lists.w3.org/Archives/Public/public-informationarchi
>>>> tecture/2019May/0000.html
>>>>
>>>> (which was "403 Forbidden: Request forbidden by administrative rules"
>>>> the last time I checked up minutes ago)
>>>>
>>>> Or, if going directly toward the text:
>>>>
>>>> https:///www.evl.uic.edu/datsoupi/coding/readings/Marcos_Novak_
>>>> Liquid.pdf
>>>>
>>>> Thank to Martin Dodge for suggesting Marcos Novak's architecture in
>>>> www.cybergeography.org bringing me to Daria Tsoupukiva's lecture
>>>> providing the reading...
>>>>
>>>> Regard,
>>>> Gubtur Wiseno Putra
>>>>
>>>> Pada Minggu, 11 Agustus 2019, Guntur Wiseno Putra <gsenopu@gmail.com>
>>>> menulis:
>>>>
>>>>> Dear architecture-discuss,
>>>>>
>>>>> Such co-presences of which architecture is part of: if we attempt to
>>>>> think of its relation with other human experiences on poetry, on poetics,
>>>>> on a spirit invoked to make comprehensible a poetic fact, to get toward an
>>>>> understanding of cyberspace architecture, of "Liquid Architecture in
>>>>> Cyberspace" (Marcos Novak, 1991)
>>>>>
>>>>> I suggested as a reading to public-informationarchitecture@w3.org at
>>>>> which there is the web-address to the Novak's work (posted at 12 May 2019):
>>>>>
>>>>> http://www.w3.org/mid/CAKi_AEu%252BK6XUb94zR7-9fQDq0Hy9JP0Zy
>>>>> T5em5Tg9gBMJh0Aiw@mail.gmail.com;list=public-informationarchitecture
>>>>> Regard,
>>>>>
>>>>> Guntur Wiseno Putra
>>>>>
>>>>> Pada Rabu, 24 Juli 2019, Guntur Wiseno Putra <gsenopu@gmail.com>
>>>>> menulis:
>>>>>
>>>>>> Dear architecture-discuss,
>>>>>> & John,
>>>>>>
>>>>>> To share what might be inspiring...
>>>>>>
>>>>>> In order to propose what should be understood as "concept", "percept"
>>>>>> & "affect", thus as "philosophy" & "art", Deleuze & Guattari ("What is
>>>>>> Philosophy?") mentioned architecture as the first art as art begins with
>>>>>> house: that of which "the most scientific architecture continually produces
>>>>>> and unifies planes and sections... it could be defined as "frame" with a
>>>>>> connection among various frames oriented differently, applied to other
>>>>>> arts...(There is) a composite system consisting of points and
>>>>>> counterpoints... (there is) a matter of sensations (percepts and affects)
>>>>>> combined... (While) the system still needs a composition plane run
>>>>>> "deframing" opening ways from house territory to city-cosmos, the system in
>>>>>> which there are cosmic forces to create new affects...".
>>>>>>
>>>>>> There is "asthetic composition" as the working of sensation which is,
>>>>>> so they said, the definition of art...
>>>>>>
>>>>>> Regard,
>>>>>> Guntur Wiseno Putra
>>>>>>
>>>>>> Pada Selasa, 23 Juli 2019, Adam Roach <adam@nostrum.com> menulis:
>>>>>>
>>>>>>> John --
>>>>>>>
>>>>>>> It's going to take a while for me to formulate my thoughts around
>>>>>>> what you say below. To make sure I understand the class of constraints
>>>>>>> you're concerned about below, can you clarify whether you think they apply
>>>>>>> to:
>>>>>>>
>>>>>>>    - Documents like BCP 200, RFC 2804, and BCP 188?
>>>>>>>    - Documents like BCP 9 and BCP 92?
>>>>>>>    - Documents like BCP 25, BCP 54, and BCP 83?
>>>>>>>
>>>>>>> You might see an unstated agenda in the categories of documents I
>>>>>>> list above, so I'll state it explicitly: in the general case, one person's
>>>>>>> important protections against a tragedy of the commons is another person's
>>>>>>> annoying impediment to be ignored and defeated. I get that not all of the
>>>>>>> above read on protocol design; but they do share the common feature that
>>>>>>> they've gone through the IETF consensus process (at least to the degree
>>>>>>> that such a process existed at the time of their respective publications).
>>>>>>> If we're going to carefully parse out the meanings of some of them as the
>>>>>>> will of the community while treating others as light guidelines to be
>>>>>>> ignored when they become cumbersome, we're going to need to agree on a
>>>>>>> pretty bright line that divides those categories.
>>>>>>>
>>>>>>> /a
>>>>>>>
>>>>>>> On 7/23/19 08:37, John C Klensin wrote:
>>>>>>>
>>>>>>> (copying architecture-discuss because the comment I'm about to
>>>>>>> make is an architectural issue and because
>>>>>>> draft-nottingham-for-the-users is under discussion there.)
>>>>>>>
>>>>>>>
>>>>>>> A late colleague, much loved by some of us, used to claim (much
>>>>>>> more elegantly than I can manage) that one of the reasons the
>>>>>>> ARPANET and then the Internet protocols had succeeded and much
>>>>>>> of what was seen as competitive alternatives had not, was that
>>>>>>> our efforts focused on pragmatic, working protocols and
>>>>>>> implementations.
>>>>>>>
>>>>>>> The other folks had developed a culture of formalisms, models,
>>>>>>> and stated design principles.  They then tried to develop
>>>>>>> protocols that fit into the boxes and categories of those
>>>>>>> formalisms, models, and design principles.    When they
>>>>>>> discovered that something didn't fit, they needed to either
>>>>>>> invent kludges or other ways of getting square pegs into round
>>>>>>> holes, go back and revise models and guidance before moving
>>>>>>> forward, or consider and make exceptions (which often required
>>>>>>> first figuring out how to make an exception and developing
>>>>>>> procedures for that).
>>>>>>>
>>>>>>> One difficulty is that the above can waste a lot of time.
>>>>>>> Another is that it can distort protocol design, if only because
>>>>>>> forcing square pegs into round holes tends to be hard on both
>>>>>>> the pegs and the holes.
>>>>>>>
>>>>>>> In many or most fields of application, the nature of engineering
>>>>>>> involves seeing and understanding a range of tradeoffs and then
>>>>>>> doing design work that reflects a carefully-chosen balance among
>>>>>>> them.  Give design elegance absolute priority over structural
>>>>>>> issues and buildings and bridges fall down.  IMO, we need to
>>>>>>> think, and keep thinking, about systems and tradeoffs.  That, in
>>>>>>> turn, means that statements like these that can be interpreted
>>>>>>> in absolute terms, even if we mostly agree with them, should be
>>>>>>> packaged as general guidelines and not BCPs to which everything
>>>>>>> done in the future is required to either conform or to try to
>>>>>>> figure out how to appeal to a higher authority.
>>>>>>>
>>>>>>> I'm not at all convinced that the proposal that was summarized
>>>>>>> an ARTAREA yesterday and that is seen as requiring an exception
>>>>>>> to BCP 190 is a good idea.  But I think our time would be better
>>>>>>> spent, and the Internet more efficiently made better, discussing
>>>>>>> the strengths, weaknesses, and alternatives to that idea rather
>>>>>>> than debating the reach and appropriateness of BCP 190 under
>>>>>>> various circumstances.   Long term and more generally, I think
>>>>>>> that suggests seeing BCP 190 not as a particular set of
>>>>>>> principles and rules but as an example of something we don't
>>>>>>> want to do to ourselves again as a BCP (or as something that
>>>>>>> gets enough of an IAB stamp of approval that people will later
>>>>>>> argue MUST (or SHOULD) be conformed to.  Again, restated as
>>>>>>> general guidance with the assumption that there will be
>>>>>>> exceptions and cases not considered, I don't have much of a
>>>>>>> problem.    If that shoe fits  draft-nottingham-for-the-users,
>>>>>>> so be it.
>>>>>>>
>>>>>>>    john
>>>>>>>
>>>>>>> p.s. I don't mean to pick on Mark here.   While these two
>>>>>>> documents coming up at the same time was handy, I think the
>>>>>>> problem is general and that there are far worse examples
>>>>>>> (examples of which he is not an author) than either of them.
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> art mailing listart@ietf.orghttps://www.ietf.org/mailman/listinfo/art
>>>>>>>
>>>>>>>
>>>>>>>

--000000000000db11a10593db527e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<span style=3D"color:rgb(34,34,34);font-size:14px;line-height:22.1200008392=
334px">Dear architecture-discuss,</span><div style=3D"color:rgb(34,34,34);f=
ont-size:14px;line-height:22.1200008392334px"><br></div><div style=3D"color=
:rgb(34,34,34);font-size:14px;line-height:22.1200008392334px"><br></div><di=
v style=3D"color:rgb(34,34,34);font-size:14px;line-height:22.1200008392334p=
x">To share what may be inspiring:<br><div><br></div><div>If there are soci=
ety of networks and networks of societies may we say also about pedagogy of=
 networks and networks of pedagogies: thus we are supposedly combining thos=
e notions on &quot;society&quot;, &quot;networks&quot;, &quot;languages&quo=
t; and &quot;great operations of capital&quot; (those of M. Castells&#39;, =
J.F. Lyotard&#39;s and G. Deleuze and F. Guattari&#39;s)...</div><div><br><=
/div><div><br></div><div>Regard,</div><div>Guntur Wiseno Putra</div><div><b=
r></div></div>Pada Minggu, 11 Agustus 2019, Guntur Wiseno Putra &lt;<a href=
=3D"mailto:gsenopu@gmail.com">gsenopu@gmail.com</a>&gt; menulis:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><div>Dear architecture-discuss,<br></div><div><div>=
<br></div><div>(There are things need to correct on * Note)</div><div><br><=
/div><div>To share what I have found out: if such public installations insp=
ire/is about exploring musicality of diferent architectural features --as i=
t was attempted by &quot;Building Music&quot; of Electronic Visual Laborato=
ry UIC:</div><div><br></div><div><br></div><div><a href=3D"https://www.evl.=
uic.edu/entry.php?id=3D1985" target=3D"_blank">https://www.evl.uic.edu/entr=
y.<wbr>php?id=3D1985</a><br></div><div><br></div><div><br></div><div>*Note:=
=C2=A0</div><div>- There is a correction for Daria Tsoupikova e-mail addres=
s of my previous messages on Marcos Novak&#39;&quot;Liquid Architecture in =
Cyberspace&quot;</div><div>- Should I add CC: <a href=3D"mailto:info@playth=
emagic.com" target=3D"_blank">info@playthemagic.com</a> as it is of the &qu=
ot;Building Music&quot; page which may have importances.</div><div><br></di=
v><div><br></div><div>Regard,</div><div>Guntur Wiseno Putra</div></div><div=
><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div=
>Dear architecture-discuss,<div><br></div><div><br></div><div><br></div><di=
v>To share what I have found out: if such public installations inspire/is a=
bout exploring musicality of diferent architectural features --as it was at=
tempted by &quot;Building Music&quot; of Electronic Visual Laboratory UIC:<=
/div><div><br></div><div><br></div><div><a href=3D"https://www.evl.uic.edu/=
entry.php?id=3D1985" target=3D"_blank">https://www.evl.uic.edu/entry.<wbr>p=
hp?id=3D1985</a><br></div><div><br></div><div><br></div><div>*Note: There i=
s a correction for Daria Tsoupikova e-mail address of my previous messages.=
..</div><div><br></div><div><br></div><div>Regard,</div><div>Guntur Wiseno =
Putra</div></div><div><br></div><br><br>Pada Minggu, 11 Agustus 2019, Guntu=
r Wiseno Putra &lt;<a href=3D"mailto:gsenopu@gmail.com" target=3D"_blank">g=
senopu@gmail.com</a>&gt; menulis:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear ar=
chitecture-discuss,<div><br></div><div><br></div><div><br></div><div>To sha=
re what I have found out: if such public installations inspire/is about exp=
loring musicality of diferent architectural features --as it was attempted =
by &quot;Building Music&quot; of Electronic Visual Laboratory UIC:</div><di=
v><br></div><div><br></div><div><a href=3D"https://www.evl.uic.edu/entry.ph=
p?id=3D1985" target=3D"_blank">https://www.evl.uic.edu/entry.<wbr>php?id=3D=
1985</a><br></div><div><br></div><div><br></div><div>*Note: There is a corr=
ection for Daria Tsoupikova e-mail address of my previous messages...</div>=
<div><br></div><div><br></div><div>Regard,</div><div>Guntur Wiseno Putra<br=
><br>Pada Minggu, 11 Agustus 2019, Guntur Wiseno Putra &lt;<a href=3D"mailt=
o:gsenopu@gmail.com" target=3D"_blank">gsenopu@gmail.com</a>&gt; menulis:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">Dear architecture-discuss,<div><br></div><=
div><span style=3D"color:rgb(34,34,34);font-size:14px;line-height:22.120000=
8392334px">Forgive me for typing errors in previous message...</span></div>=
<div><span style=3D"color:rgb(34,34,34);font-size:14px;line-height:22.12000=
08392334px"><br></span></div><div><span style=3D"color:rgb(34,34,34);font-s=
ize:14px;line-height:22.1200008392334px">An alternative link to the posting=
 on Marcos Novak&#39;s &quot;Liquid Architecture in Cyberspace&quot; at pub=
lic@informationarchitecture</span><span style=3D"color:rgb(34,34,34);font-s=
ize:14px;line-height:22.1200008392334px"><wbr>@</span><a href=3D"http://w3.=
org/" style=3D"font-size:14px;line-height:22.1200008392334px" target=3D"_bl=
ank">w3.org</a><span style=3D"color:rgb(34,34,34);font-size:14px;line-heigh=
t:22.1200008392334px">=C2=A0I mentioned earlier is</span></div><div><div st=
yle=3D"color:rgb(34,34,34);font-size:14px;line-height:22.1200008392334px"><=
br></div><div style=3D"color:rgb(34,34,34);font-size:14px;line-height:22.12=
00008392334px"><a href=3D"https://lists.w3.org/Archives/Public/public-infor=
mationarchitecture/2019May/0000.html" target=3D"_blank">https://lists.w3.or=
g/Archives/<wbr>Public/public-informationarchi<wbr>tecture/2019May/0000.htm=
l</a><br></div><div style=3D"color:rgb(34,34,34);font-size:14px;line-height=
:22.1200008392334px"><br></div><div style=3D"color:rgb(34,34,34);font-size:=
14px;line-height:22.1200008392334px">(which was &quot;403 Forbidden: Reques=
t forbidden by administrative rules&quot; the last time I checked up minute=
s ago)</div><div style=3D"color:rgb(34,34,34);font-size:14px;line-height:22=
.1200008392334px"><br></div><div style=3D"color:rgb(34,34,34);font-size:14p=
x;line-height:22.1200008392334px">Or, if going directly toward the text:</d=
iv><div style=3D"color:rgb(34,34,34);font-size:14px;line-height:22.12000083=
92334px"><br></div><div><font color=3D"#222222"><span style=3D"font-size:14=
px;line-height:22.1200008392334px"><a href=3D"https://www.evl.uic.edu/datso=
upi/coding/readings/1991_Novak_Liquid.pdf" target=3D"_blank">https://www.ev=
l.uic.edu/datsou<wbr>pi/coding/readings/1991_Novak_<wbr>Liquid.pdf</a></spa=
n></font><br></div><div><font color=3D"#222222"><span style=3D"font-size:14=
px;line-height:22.1200008392334px"><br></span></font></div><div style=3D"co=
lor:rgb(34,34,34);font-size:14px;line-height:22.1200008392334px">Thank to M=
artin Dodge for suggesting Marcos Novak&#39;s architecture in=C2=A0<a href=
=3D"http://www.cybergeography.org/" target=3D"_blank">www.cybergeography.or=
g</a>=C2=A0brin<wbr>ging me to Daria Tsoupukiva&#39;s lecture providing the=
 reading...</div></div><div><br></div><div><br></div><div><br></div><div>Re=
gard,</div><div>Guntur Wiseno Putra<br><br>Pada Minggu, 11 Agustus 2019, Gu=
ntur Wiseno Putra &lt;<a href=3D"mailto:gsenopu@gmail.com" target=3D"_blank=
">gsenopu@gmail.com</a>&gt; menulis:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear=
 architecture-discuss,<div><br></div><div>An alternative link to the postin=
g on Marcos Nocak&#39;S &quot;Liquid Architecture in Cyberspace&quot; at pu=
blic@informationarchitecture<wbr>@<a href=3D"http://w3.org" target=3D"_blan=
k">w3.org</a>=C2=A0 I mentioned earlier is</div><div><br></div><div><a href=
=3D"https://lists.w3.org/Archives/Public/public-informationarchitecture/201=
9May/0000.html" target=3D"_blank">https://lists.w3.org/Archives/<wbr>Public=
/public-informationarchi<wbr>tecture/2019May/0000.html</a><br></div><div><b=
r></div><div>(which was &quot;403 Forbidden: Request forbidden by administr=
ative rules&quot; the last time I checked up minutes ago)</div><div><br></d=
iv><div>Or, if going directly toward the text:<br></div><div><br></div><div=
>https:///<a href=3D"http://www.evl.uic.edu/datsoupi/coding/readings/Marcos=
_Novak_" target=3D"_blank">www.evl.uic.edu/datso<wbr>upi/coding/readings/Ma=
rcos_Nov<wbr>ak_</a> Liquid.pdf</div><div><br></div><div>Thank to Martin Do=
dge for suggesting Marcos Novak&#39;s architecture in <a href=3D"http://www=
.cybergeography.org" target=3D"_blank">www.cybergeography.org</a> bringing =
me to Daria Tsoupukiva&#39;s lecture providing the reading...</div><div><br=
></div><div>Regard,</div><div>Gubtur Wiseno Putra<br><br>Pada Minggu, 11 Ag=
ustus 2019, Guntur Wiseno Putra &lt;<a href=3D"mailto:gsenopu@gmail.com" ta=
rget=3D"_blank">gsenopu@gmail.com</a>&gt; menulis:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">Dear architecture-discuss,<div><br></div><div>Such co-presences o=
f which architecture is part of: if we attempt to think of its relation wit=
h other human experiences on poetry, on poetics, on a spirit invoked to mak=
e comprehensible a poetic fact, to get toward an understanding of cyberspac=
e architecture, of &quot;Liquid Architecture in Cyberspace&quot; (Marcos No=
vak, 1991)</div><div><br></div><div>I suggested as a reading to <a href=3D"=
mailto:public-informationarchitecture@w3.org" target=3D"_blank">public-info=
rmationarchitecture<wbr>@w3.org</a> at which there is the web-address to th=
e Novak&#39;s work (posted at 12 May 2019):</div><div><br></div><div><a hre=
f=3D"http://www.w3.org/mid/CAKi_AEu%252BK6XUb94zR7-9fQDq0Hy9JP0ZyT5em5Tg9gB=
MJh0Aiw@mail.gmail.com;list=3Dpublic-informationarchitecture" target=3D"_bl=
ank">http://www.w3.org/mid/CAKi_AEu<wbr>%252BK6XUb94zR7-9fQDq0Hy9JP0Zy<wbr>=
T5em5Tg9gBMJh0Aiw@mail.gmail.c<wbr>om;list=3Dpublic-informationarch<wbr>ite=
cture</a><br></div><div>Regard,</div><div><br></div><div>Guntur Wiseno Putr=
a<br><br>Pada Rabu, 24 Juli 2019, Guntur Wiseno Putra &lt;<a href=3D"mailto=
:gsenopu@gmail.com" target=3D"_blank">gsenopu@gmail.com</a>&gt; menulis:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">Dear architecture-discuss,<div>&amp; John,<=
br></div><div><br></div><div>To share what might be inspiring...<br><div><b=
r></div><div>In order to propose what should be understood as &quot;concept=
&quot;, &quot;percept&quot; &amp; &quot;affect&quot;, thus as &quot;philoso=
phy&quot; &amp; &quot;art&quot;, Deleuze &amp; Guattari (&quot;What is Phil=
osophy?&quot;) mentioned architecture as the first art as art begins with h=
ouse: that of which &quot;the most scientific architecture continually prod=
uces and unifies planes and sections... it could be defined as &quot;frame&=
quot; with a connection among various frames oriented differently, applied =
to other arts...(There is) a composite system consisting of points and coun=
terpoints... (there is) a matter of sensations (percepts and affects) combi=
ned... (While) the system still needs a composition plane run &quot;deframi=
ng&quot; opening ways from house territory to city-cosmos, the system in wh=
ich there are cosmic forces to create new affects...&quot;.</div><div><br><=
/div><div>There is &quot;asthetic composition&quot; as the working of sensa=
tion which is, so they said, the definition of art...</div><div><br></div><=
div>Regard,</div><div>Guntur Wiseno Putra<br><br>Pada Selasa, 23 Juli 2019,=
 Adam Roach &lt;<a href=3D"mailto:adam@nostrum.com" target=3D"_blank">adam@=
nostrum.com</a>&gt; menulis:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div>John --<br>
    </div>
    <div><br>
    </div>
    <div>It&#39;s going to take a while for me to
      formulate my thoughts around what you say below. To make sure I
      understand the class of constraints you&#39;re concerned about below,
      can you clarify whether you think they apply to: <br>
    </div>
    <div>
      <ul>
        <li>Documents like BCP 200, RFC 2804, and BCP 188?</li>
        <li> Documents like BCP 9 and BCP 92?</li>
        <li>Documents like BCP 25, BCP 54, and BCP 83?</li>
      </ul>
      <p>You might see an unstated agenda in the categories of documents
        I list above, so I&#39;ll state it explicitly: in the general case,
        one person&#39;s important protections against a tragedy of the
        commons is another person&#39;s annoying impediment to be ignored
        and defeated. I get that not all of the above read on protocol
        design; but they do share the common feature that they&#39;ve gone
        through the IETF consensus process (at least to the degree that
        such a process existed at the time of their respective
        publications). If we&#39;re going to carefully parse out the
        meanings of some of them as the will of the community while
        treating others as light guidelines to be ignored when they
        become cumbersome, we&#39;re going to need to agree on a pretty
        bright line that divides those categories.</p>
      <p>/a<br>
      </p>
    </div>
    <div><br>
    </div>
    <div>On 7/23/19 08:37, John C Klensin wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <pre>(copying architecture-discuss because the comment I&#39;m about =
to
make is an architectural issue and because
draft-nottingham-for-the-users is under discussion there.)


A late colleague, much loved by some of us, used to claim (much
more elegantly than I can manage) that one of the reasons the
ARPANET and then the Internet protocols had succeeded and much
of what was seen as competitive alternatives had not, was that
our efforts focused on pragmatic, working protocols and
implementations. =20

The other folks had developed a culture of formalisms, models,
and stated design principles.  They then tried to develop
protocols that fit into the boxes and categories of those
formalisms, models, and design principles.    When they
discovered that something didn&#39;t fit, they needed to either
invent kludges or other ways of getting square pegs into round
holes, go back and revise models and guidance before moving
forward, or consider and make exceptions (which often required
first figuring out how to make an exception and developing
procedures for that).

One difficulty is that the above can waste a lot of time.
Another is that it can distort protocol design, if only because
forcing square pegs into round holes tends to be hard on both
the pegs and the holes.

In many or most fields of application, the nature of engineering
involves seeing and understanding a range of tradeoffs and then
doing design work that reflects a carefully-chosen balance among
them.  Give design elegance absolute priority over structural
issues and buildings and bridges fall down.  IMO, we need to
think, and keep thinking, about systems and tradeoffs.  That, in
turn, means that statements like these that can be interpreted
in absolute terms, even if we mostly agree with them, should be
packaged as general guidelines and not BCPs to which everything
done in the future is required to either conform or to try to
figure out how to appeal to a higher authority.

I&#39;m not at all convinced that the proposal that was summarized
an ARTAREA yesterday and that is seen as requiring an exception
to BCP 190 is a good idea.  But I think our time would be better
spent, and the Internet more efficiently made better, discussing
the strengths, weaknesses, and alternatives to that idea rather
than debating the reach and appropriateness of BCP 190 under
various circumstances.   Long term and more generally, I think
that suggests seeing BCP 190 not as a particular set of
principles and rules but as an example of something we don&#39;t
want to do to ourselves again as a BCP (or as something that
gets enough of an IAB stamp of approval that people will later
argue MUST (or SHOULD) be conformed to.  Again, restated as
general guidance with the assumption that there will be
exceptions and cases not considered, I don&#39;t have much of a
problem.    If that shoe fits  draft-nottingham-for-the-users<wbr>,
so be it.

   john

p.s. I don&#39;t mean to pick on Mark here.   While these two
documents coming up at the same time was handy, I think the
problem is general and that there are far worse examples
(examples of which he is not an author) than either of them.

______________________________<wbr>_________________
art mailing list
<a href=3D"mailto:art@ietf.org" target=3D"_blank">art@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/art" target=3D"_blank">htt=
ps://www.ietf.org/mailman/l<wbr>istinfo/art</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </div>

</blockquote></div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote>
</blockquote>

--000000000000db11a10593db527e--


From nobody Tue Oct  1 13:19:55 2019
Return-Path: <roland@letsencrypt.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC067120059 for <art@ietfa.amsl.com>; Tue,  1 Oct 2019 13:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=letsencrypt.org
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 Uo17hMbIv3If for <art@ietfa.amsl.com>; Tue,  1 Oct 2019 13:19:35 -0700 (PDT)
Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (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 B809212001E for <art@ietf.org>; Tue,  1 Oct 2019 13:19:35 -0700 (PDT)
Received: by mail-oi1-x232.google.com with SMTP id w144so15643940oia.6 for <art@ietf.org>; Tue, 01 Oct 2019 13:19:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=letsencrypt.org; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=5HsBV60NrQ5J6D3n9hHCeeP8TYqkUPA6mKjNRj6+7cQ=; b=A7KqTA71+pljVzWS5hw6XAWCocmfrLVYc98GqeiqnrAb/l+gzhqS8F4LcJFN48rFIs a/JS1E6q9DY12mNbUhumQdKNxPLDBLtAdI02uNwE2kKbHCnO04hAPjnpJFwaVpBV7IZe PBIK6+hDNeMD2Y6bMFWP+BY7LiWI1fzRNb35g=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=5HsBV60NrQ5J6D3n9hHCeeP8TYqkUPA6mKjNRj6+7cQ=; b=lqIfxv3Emy22QH/68dD7kAUK9A6u03aohSDuqPBM4BIw1an+Vk8fmqpDKWp6oN9sdy /8VqPazv+e3+aDxRBzch1+ds+jCcXeGb1QQC8kCkm0m/OU5fb3yOddZtOLj2dl/5OvJu tzHgl3dxN4dsrdTRfb57QniuzFzNiXYp2PjBxg8ryhIZJ0xeSp5DiBqW69mkqhpOR7dZ K4apNbu3d8R0PAVhKSCRnxxi+MVC1pk8D3O3BeKfZxcmz2mRMVYss4I9/d+vybTuTEQ2 IMWTXWP5QsTI8UGk7WYD3Lbg0Xxyh1+2aO1mFxIOyQIP0+FkQL81+cMKcO1zg64oSVZl hiWA==
X-Gm-Message-State: APjAAAXNDJ0Dl+/GU9WVUlH0k4ou5XbMA4ENuJa5GhT+0svW1q8mZS0E rGDnVnZ+lZi+Xngz80koyabtkQ==
X-Google-Smtp-Source: APXvYqydLRmnLymjQPBNzo4aRg3rRFA0OJ/1hxdKbC4Jq+oGvvs2SVByLDjVRYVMcqnk+z8UP3P8MA==
X-Received: by 2002:aca:56ca:: with SMTP id k193mr5077575oib.155.1569961174834;  Tue, 01 Oct 2019 13:19:34 -0700 (PDT)
Received: from ?IPv6:2600:1700:bd50:a5b0:98b6:333c:5dd8:82ec? ([2600:1700:bd50:a5b0:98b6:333c:5dd8:82ec]) by smtp.gmail.com with ESMTPSA id n65sm5591996oib.35.2019.10.01.13.19.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Oct 2019 13:19:33 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Roland Shoemaker <roland@letsencrypt.org>
In-Reply-To: <156870601125.17470.11128908292563240208@ietfa.amsl.com>
Date: Tue, 1 Oct 2019 13:19:32 -0700
Cc: art@ietf.org, draft-ietf-acme-tls-alpn.all@ietf.org, acme@ietf.org, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <36445804-1B33-4949-88FA-71BB9107C443@letsencrypt.org>
References: <156870601125.17470.11128908292563240208@ietfa.amsl.com>
To: Martin Thomson <mt@lowentropy.net>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ZMTLGvGsRO60J9PlHJypLpQ0jSs>
Subject: Re: [art] Artart last call review of draft-ietf-acme-tls-alpn-06
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Oct 2019 20:19:39 -0000

Hey Martin,

Thanks for the thorough review, I agree with all of the suggestions and =
will be incorporating the changes into the next revision. Following up =
on one point about Section 7, I believe you may actually be thinking =
about another issue we had with the http-01 ACME challenge. The issue =
here was as described, if the ACME server was using HTTPS to validate a =
http-01 challenge and the expected domain name didn=E2=80=99t have a =
proper virtual host configuration many servers would redirect the =
request to a =E2=80=98default=E2=80=99 handler. This is called out in =
RFC 8555 Section 8.3.

Thanks,
Roland

> On Sep 17, 2019, at 12:40 AM, Martin Thomson via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Reviewer: Martin Thomson
> Review result: Ready with Nits
>=20
> This is a clear description of a simple protocol that addresses a =
well-defined
> problem.  I didn't find any real issues, though I have some =
suggestions that
> might improve the document a little.  My view is that publication =
without these
> would still produce a useful RFC.
>=20
> Suggestions:
>=20
> The document should probably talk about minimum TLS versions and =
expected
> algorithms.  I think that it would be enough to say TLS 1.2 minimum =
with the
> mandatory cipher suites from that spec.  You might also want to =
require
> certificates with a PKCS#1v1.5 RSASSA key (as much as those are =
terrible), but
> to permit use and negotiation of other alternatives.  If your CA =
supports
> ECDSA, I see no reason not to prepare an ECDSA certificate on that =
basis, but
> that would be based on extra-textual knowledge, it's no guarantee of
> interoperability.
>=20
> Section 4
> I have two suggestions here for making the properties you rely on with =
the
> protocol clearer to readers.
>=20
> You should explicitly say that the "acme-tls/1" protocol as negotiated =
here
> does not carry application data, it only requires that the server =
provide
> certificate-based authentication.  AND that the certificate-based
> authentication provided uses an alternative method than that described =
in RFC
> 5280, even though it uses X.509 certificates.  Both of these are =
already
> implicit in the text here, but I think that it would help to be very =
clear
> about these as they are a little surprising ways to use TLS.
>=20
> You might also want to explicitly point out that though the protocol =
does not
> depend on the server providing a valid signature, or even that it =
successfully
> complete the TLS handshake, these are both required by the protocol =
and a
> validator MAY withhold authorization if the TLS handshake does not =
complete
> successfully.  (This is implied in Step 4, but not explained.)
>=20
> Nits:
>=20
> Section 1
> The history lesson in the appendix is useful.  It helps to articulate =
why the
> design is this way.  However, I don't think that you need to spend a =
third of
> the introduction on a reference to that historical information.  I'd =
cut that
> paragraph entirely.
>=20
> Section 3
> =
https://www.quickanddirtytips.com/sites/default/files/styles/insert_large/=
public/images/937/use-utilize-pin.png?itok=3DBt7A6RQq
>=20
> Step 3: s/AMCE/ACME; this sentence is two with a comma-splice
>=20
> Section 4
> This is taste only, but I find the extra version decoration on these
> identifiers unnecessary.  Decorate v2 if you are unfortunate enough to =
need one.
>=20
> Section 5
>=20
> The parallel list construction in this sentence is a little awkward:
>=20
>   "This means that if User A registers Host A and User B registers =
Host B the
>   server should not allow a TLS request using a SNI value for Host A =
to be
>   served by User B or Host B to be served by User A."
>=20
> The first part of this sentence is fine, but the second part "or Host =
B to be
> served by User A" might be clearer if it said "or a TLS connection =
with a
> server_name extension identifying Host B to be answered by User A."  =
Or similar.
>=20
> Section 6.2
> Please don't use uppercase for an identifier when the actual protocol =
is
> identified using lowercase ASCII.  I know that RFC 7301 did this for =
HTTP/1.1,
> but that was a confusing mistake that doesn't need to be propagated.
>=20
> Section 7
> This is not an appendix.  You can make appendices using `<back>` in =
XML or by
> moving the section under `---back` in kramdown-rfc2629.
>=20
> The implication of this text is to say that this is a replacement for =
an
> important part of ACME.  I would instead say that this is an iteration =
on an
> earlier design that used the TLS server_name extension to carry the =
challenge.=20
> And that that earlier design was shown to have some serious issues in =
practice.
>=20
> My understanding of the problem differs from what is described here =
though: the
> problem - as I recall - was that this used high-entropy, generated =
values for
> the server_name extension and an HTTP or absent ALPN identifier.  =
These names
> might not have as strong a binding to the user that controlled the =
validated
> portion of that name (the suffix) as desired.  Some servers would =
route these
> SNI values to a "default" handler.  The "default" handler could be =
under the
> control of any user; in fact, users could in some cases choose a name =
that
> would greatly improve their chances of having their certificate used =
as a
> default (e.g., aaaaa.example.host or zzzzz.example.host.  As =
formulated here,
> particularly with the User A/Host B phrasing, you are almost implying =
that the
> security property you rely on in the ALPN design doesn't hold.  As far =
as I'm
> aware, that security property does hold because you are including =
exactly the
> validated name in the SNI.
>=20
>=20


From nobody Wed Oct  2 13:33:06 2019
Return-Path: <me@evertpot.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E97112002F for <art@ietfa.amsl.com>; Wed,  2 Oct 2019 13:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evertpot.com header.b=j6wuLwhz; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=BB6eeTSw
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 FI9nRbRnn3K2 for <art@ietfa.amsl.com>; Wed,  2 Oct 2019 13:33:02 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61173120018 for <art@ietf.org>; Wed,  2 Oct 2019 13:33:02 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id AC226539 for <art@ietf.org>; Wed,  2 Oct 2019 16:33:01 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 02 Oct 2019 16:33:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evertpot.com; h= subject:references:to:from:message-id:date:mime-version :in-reply-to:content-type; s=mesmtp; bh=aIb+FYNEZd4cMpATU5GhBMiQ lYSzfvTNUupsDbRkhhU=; b=j6wuLwhzsmiGfm3rowUE518cWcV8rTwOZNx8blYL i3nJg5zi66fgdcED2KuvENKRlwb21Y6Sg97hhZ4x9h5tNiZGoE1UL8iNFYflPSl3 AU5vOkSOu/VAuXYspLkN59WMgHRAwyzd1ROZ1QWUQ6GJ28gQaffQoZW6NXbMjQg+ aSc=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=aIb+FY NEZd4cMpATU5GhBMiQlYSzfvTNUupsDbRkhhU=; b=BB6eeTSwnl5Y02RmiYFcKp AJiFkx1BHsvHkfRyrplVW9JjTpAMYJQYiCpZZvNOe0UfDwbTB8VZUnuB3pjIp+Tx wNAebZcJfDnYYhN+G8njL4KrpeHvRFOisZ+K+UE+8yDPKIi1BSovRSqOb+KceKzJ hI5l8pq5+bo/YqDSG4jeuH4w1kTSnbY1iYQZNqnLa3y2dEK1tfb8bjwoyoBCysnn JPC09TUrXIcATNgNWM/RE1WkuBuDcn3dvFPPNr3+JlNC7OkcLm3IpdBesdEpZzSm CiuEWWjnQE/Umue15BQdA+E4Mb1KWarR0r61tSizi22DZBtFLpev97arevsIwvKQ ==
X-ME-Sender: <xms:fAmVXdTpT1L39AuKl1YYvzieTRODYu-LUEv2N3-tVbHTfhCZs0Wb0g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrgeeigdduhedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefufhfvhffkffgfgggjtgesrgdtre ertdefjeenucfhrhhomhepgfhvvghrthcurfhothcuoehmvgesvghvvghrthhpohhtrdgt ohhmqeenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppedugedvrdduuddvrdduke eirddvhedvnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmvgesvghvvghrthhpohhtrdgt ohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:fAmVXbD8r-CPBh6tG7jBcPYPGWk4hEkxiRJD99KDWndWu7sC4cUiCw> <xmx:fAmVXd2j3xveeGDl6wvgTZP7PQ5-TSGRWWnaD4oFbBjEdplN2KQdDA> <xmx:fAmVXZVcLJDeuW1YJM5zoO6miXWZN0U7-4xBF21YcKFoNFnGrH3anQ> <xmx:fQmVXWLhLzu5d9k7nZ2gPd81j7WzTAtCw9AZ2h4cxG-Ag3nCRUPeog>
Received: from [192.168.2.10] (toroon0954w-lp130-01-142-112-186-252.dsl.bell.ca [142.112.186.252]) by mail.messagingengine.com (Postfix) with ESMTPA id 9FB788005C for <art@ietf.org>; Wed,  2 Oct 2019 16:33:00 -0400 (EDT)
References: <157004748168.8945.4438822403486226680.idtracker@ietfa.amsl.com>
To: art@ietf.org
From: Evert Pot <me@evertpot.com>
Openpgp: preference=signencrypt
Autocrypt: addr=me@evertpot.com; keydata= mQINBFzZpTYBEACt3GNTWOSosId2/7G1EHYWfva4gF4kgOL+/pew0+I2wTCyFeDXti+CRE1o 5LoCpTSGHDWZokSELeA2PwNX1ls7c2sZ7AVKWKhBLBhPEVo6YzlTli/B747ryGfMikiWYCRa e/yBJtyRuWuS8ArxCpEROzcUqCGZu7Rqs9RzUfYS7WZ85ne3DeRxPCCBIIlhlRu2lasjByPs IpSI0YSIpq4M5fLqbVdTjfqbTBGw82pDwQwlxO3J0T07dnvpEEheYspkMj/EGXqVTrLuoRw0 D7yObXgr0bcjuf+km8cdfZktclqCg1YajiseBBObw9IQpWiIE0oIxA7mAti1wus3JLxAfqCI tgzBtwEPeg6tcfzeDI9gnSl904g2+ozS0uFI61YHA/j70IxgIwyzp8QDsj0nS83aqaZV8k2U FNCnbriMftMCD/+iudRxfzq4VThkhIgfR9ZsaTvdWGIsAxCZyjaUHFMOBafjCMNjePCg74yA JSwdHhi6mzIuIfVGqsKXmO4Khzgm+c2qVq7cym93yp6kqNXOge9ZjQ2q96HHa64wXoYlNYZU 0fkvjkANj9V7ZC4PnavRMQHeFsW+vqU38pIFSppsqpeBggvV4U2WRHt2NyrE3ta9h1XTs9w3 SWSTujpJ/XGqPm7YYnNPrKXn5uvjEJ+OKt4+trpP1juUc3LJ8wARAQABtBtFdmVydCBQb3Qg PG1lQGV2ZXJ0cG90LmNvbT6JAk4EEwEIADgWIQTLR9Vo8uufCXNz2gLxiYR6BK2dDwUCXNml NgIbIwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRDxiYR6BK2dDyHmD/0bufc/UhM76R8S NSpYAds83HKt3XgIGPl8CEMaz35bkvlNypVUvd0iLy1MFgDDyqdXuM840HWL0grCC+g1LA8K eeHSYBDYm+ATlEu09FCN6+TdDbWBA19vmLlJ98mEgCDrIo/B+pskap4Qxq20vuxssL0nIXyM 1FoPlrTu8SuZrkViUSWmEICSB6UfZntIJDPxv9NSEjLKSkTCwIXna744W4zQQ/tHohohw2qc epCudGv1AhJBJS+UE8W+Lpt3e1fsMZQl/UIFpF3EQ3+6DkIHqk+nVe7zstcGbB/RUkHqwUCb km9Iv2B9YURrDW6XIF2jp+vAVuI78kLjXCTEBd8bzlBjt2BOTVaj4JZcdilKfNNr57H8Go+A IyVqsjjJ0LqkCdmG96lgJLUCcMztiJnTxxzLFSF4rQHKV14G8EQ+xMkx5We3QOWKGFHkf4JF zPCFD8O1978FbPEZ6JjnSR8Goeb5RKpGe3AfjHR7brS6jpxQaC8pGnjVBQzY3bXc1LSKWJ8N LHEOnKN5xBnwWpQv7pygxslnrNCzWCUijsqSQOFcihUEcZwNr6IwHBXBoR56pEiGk1u9Y8cZ VcJbQkj9Ok/0fNF1wYDlJS7gl20pD3YwZ2GIBPHH8FI+COOQmSTqpkN655H1qL4nfakXwu27 giSFbm0HupM7IuGm7fjigrkCDQRc2aU2ARAAysa169s6wds+2mg9oJTz0kDusRXca3pRiMKV 9YfpztMX9KK8F799gRtvjz8ZHVQlhr6NYHJmtsH5Y0iGYOL/6kUE56laB/C3cSJ0FOZN5Ov2 fROUWmEJod7oyHJW0mcGKGfHiuGo0Xs7bAcspxF5s8iysFr50nLGEqJJ7G6/jzcMuFwqhQ5z B3/hctD09nI5YPzJJrJiPxtJ3OV4wEziIW7Ff9rOwSDvMLbSfX/iJA7QRM81IuTVWBBljlG9 YkbPcyczINtqYAXFaKGaUM+TE3YnUDFsHgvpEm2MFC4NCcKFDgsAy8IOEYRCDXtkS2eopQvd rafP5jJ9aLXP/zbXlslY7dQ+QxQjus1W+V0eR09NDp83uaJ/EdtnveETyQqjrF+z4svdlRYF Xd3kyV91OC2r3fXX2uKHDuAQVI2jbAS2apnCJbCQJMQfULyAYXKf8iCGk7nC1y0tGGpQ7HxQ GW0KC86GQP8hrXYNVvhkFGuxGjp814U7eFfZUZICq3Lqk8rxi830+9noFCHU4egkRynULhCN M1R/A/itwBZsrZ4+I6vYejKizDvzm3e9sb+5CMQeX4Y1uLkYKT163hshJCGsJEIobmvLlqUh qkY3UFI293h8xv/b0bEbeILUWJn2c6GNWR3flbb4wYW968DZg3uvKnFkomA6XECwsAKDegUA EQEAAYkCNgQYAQgAIBYhBMtH1Wjy658Jc3PaAvGJhHoErZ0PBQJc2aU2AhsMAAoJEPGJhHoE rZ0PYdEP/0K9Nc7khSfCqvuyLnoV6ONkaGHfbjgNcjGj7n46nx9FQJpp36fVBYItJdFXEfbt riY7OnqS5voTDlpmS922xfk9gfG1TKGQrsHCKSj63LyIPweYdCFGvy5F/Ijn0eNeVuxJU48D gE3nfAygrDdjfgDy3E+iFNEbb1YJLXCTavA4ciX5IZ7W7uzWLC4m2u/3N2/phuPtRcRdszB+ kwHPnmPNX1Jqw84jLD+Nn8ideM4G6H3fqFS55GktB0wfMOgsnVDSyrFKnXMF/077W8ZUU9k/ TveBbBtYLxcwJyrVnARh97xUi9PUABK/K8djp+z/kBQCU+Umwii4vFoubh/vTE/09BRaY8jg tvTetzzeMoqsnRiEgFHO+RCUFVFrzG8X48zji44+Vs/Ocq4Rz1auHPGpVT7ksB7/1C3wWOIg D+rOfkLt+zr1QG2V/BT1O0qrAaxOOm3pj76OyYks/tcdERkXWIQhCamn2Wc4h7tWuGnCJHny AGRF93EEPoMXoa5YxE7ai6WIUJBnR892vEVL+tOMDc0uaOAxk9xfMTM9FICqLVzfxo4GUDhJ tVV72OP0MkjyR1JTKZ6zAS7e5CviHutd8m/ILFDCKxgl46mERGW87eolJEO2aAjR8LycuwD2 PApJHMoXVaQKApGJYYaUeJrYDbqVYBNRMoVllUFOGRE6
X-Forwarded-Message-Id: <157004748168.8945.4438822403486226680.idtracker@ietfa.amsl.com>
Message-ID: <6987f70f-4f81-de99-fbad-e3529bceb422@evertpot.com>
Date: Wed, 2 Oct 2019 16:32:59 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <157004748168.8945.4438822403486226680.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------9895C912230929A5EDCBFF59"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/-A8FxwXNVhWr8MkhkI-sF-2AgJY>
Subject: [art] Fwd: New Version Notification for draft-pot-authentication-link-01.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Oct 2019 20:33:05 -0000

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

A new version of the authentication-link draft.

The changes are unsubstantial. Since I've published the original draft,
I've had several people reach out and implement these rels.

I am curious if there is interest in the ART Area to adopt this draft,
or if there is anything I can do to to get it to a state where it could.
My intuition is that this is a fairly uncontroversial proposal, but I've
been wrong before.

Regards,
Evert

-------- Forwarded Message --------
Subject: 	New Version Notification for draft-pot-authentication-link-01.txt
Date: 	Wed, 02 Oct 2019 13:18:01 -0700
From: 	internet-drafts@ietf.org
To: 	Evert Pot <me@evertpot.com>




A new version of I-D, draft-pot-authentication-link-01.txt
has been successfully submitted by Evert Pot and posted to the
IETF repository.

Name: draft-pot-authentication-link
Revision: 01
Title: Link relationship types for authentication
Document date: 2019-10-02
Group: Individual Submission
Pages: 4
URL:
https://www.ietf.org/internet-drafts/draft-pot-authentication-link-01.txt
Status: https://datatracker.ietf.org/doc/draft-pot-authentication-link/
Htmlized: https://tools.ietf.org/html/draft-pot-authentication-link-01
Htmlized:
https://datatracker.ietf.org/doc/html/draft-pot-authentication-link
Diff: https://www.ietf.org/rfcdiff?url2=draft-pot-authentication-link-01

Abstract:
This specification defines a set of relationships that may be used to
indicate where a user may authenticate, log out, register a new
account or find out who is currently authenticated.



Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


--------------9895C912230929A5EDCBFF59
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>A new version of the authentication-link draft.</p>
    <p>The changes are unsubstantial. Since I've published the original
      draft, I've had several people reach out and implement these rels.</p>
    <div class="moz-forward-container">I am curious if there is interest
      in the ART Area to adopt this draft, or if there is anything I can
      do to to get it to a state where it could. My intuition is that
      this is a fairly uncontroversial proposal, but I've been wrong
      before.</div>
    <div class="moz-forward-container"><br>
    </div>
    <div class="moz-forward-container">Regards,<br>
      Evert<br>
    </div>
    <div class="moz-forward-container"><br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
            </th>
            <td>New Version Notification for
              draft-pot-authentication-link-01.txt</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
            <td>Wed, 02 Oct 2019 13:18:01 -0700</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
            <td>Evert Pot <a class="moz-txt-link-rfc2396E" href="mailto:me@evertpot.com">&lt;me@evertpot.com&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <br>
      A new version of I-D, draft-pot-authentication-link-01.txt<br>
      has been successfully submitted by Evert Pot and posted to the<br>
      IETF repository.<br>
      <br>
      Name: draft-pot-authentication-link<br>
      Revision: 01<br>
      Title: Link relationship types for authentication<br>
      Document date: 2019-10-02<br>
      Group: Individual Submission<br>
      Pages: 4<br>
      URL:
<a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-pot-authentication-link-01.txt">https://www.ietf.org/internet-drafts/draft-pot-authentication-link-01.txt</a><br>
      Status:
      <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-pot-authentication-link/">https://datatracker.ietf.org/doc/draft-pot-authentication-link/</a><br>
      Htmlized:
      <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-pot-authentication-link-01">https://tools.ietf.org/html/draft-pot-authentication-link-01</a><br>
      Htmlized:
      <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-pot-authentication-link">https://datatracker.ietf.org/doc/html/draft-pot-authentication-link</a><br>
      Diff:
      <a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-pot-authentication-link-01">https://www.ietf.org/rfcdiff?url2=draft-pot-authentication-link-01</a><br>
      <br>
      Abstract:<br>
      This specification defines a set of relationships that may be used
      to<br>
      indicate where a user may authenticate, log out, register a new<br>
      account or find out who is currently authenticated.<br>
      <br>
      <br>
      <br>
      Please note that it may take a couple of minutes from the time of
      submission<br>
      until the htmlized version and diff are available at
      tools.ietf.org.<br>
      <br>
      The IETF Secretariat<br>
      <br>
    </div>
  </body>
</html>

--------------9895C912230929A5EDCBFF59--


From nobody Mon Oct  7 05:29:11 2019
Return-Path: <ggh@multi.fi>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23849120099 for <art@ietfa.amsl.com>; Mon,  7 Oct 2019 05:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 2ShECwdutj1l for <art@ietfa.amsl.com>; Mon,  7 Oct 2019 05:29:08 -0700 (PDT)
Received: from webmail.multi.fi (webmail.multi.fi [85.134.37.159]) (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 34F6412004E for <art@ietf.org>; Mon,  7 Oct 2019 05:29:07 -0700 (PDT)
Received: from webmail.multi.fi (localhost [IPv6:::1]) by webmail.multi.fi (Postfix) with ESMTPS id 707F718000A1 for <art@ietf.org>; Mon,  7 Oct 2019 15:29:05 +0300 (EEST)
Received: from [109.240.230.47] ([109.240.230.47]) by webmail.multi.fi (Horde Framework) with HTTPS; Mon, 07 Oct 2019 15:29:05 +0300
Date: Mon, 07 Oct 2019 15:29:05 +0300
Message-ID: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi>
From: Ggh <ggh@multi.fi>
To: art@ietf.org
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/rhalsAschqu3Hb5oj-IgwD0d-XY>
Subject: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Oct 2019 12:29:10 -0000

Hello,

My name is Greg, and would like to ask if this list is a good place to discuss
RSS and its possible use?

Thank you,
Greg

Tell me, and I forget. Ask me, and I discover...



From nobody Mon Oct  7 05:39:21 2019
Return-Path: <lef.mutualauth@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14DC6120099 for <art@ietfa.amsl.com>; Mon,  7 Oct 2019 05:39:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 BqD2voPJR2cN for <art@ietfa.amsl.com>; Mon,  7 Oct 2019 05:39:17 -0700 (PDT)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (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 1BDE41200B1 for <art@ietf.org>; Mon,  7 Oct 2019 05:39:17 -0700 (PDT)
Received: by mail-pl1-x631.google.com with SMTP id q15so6792677pll.11 for <art@ietf.org>; Mon, 07 Oct 2019 05:39:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=d4ZufZ3RXND/PLCh9rxS8MKfhqJdJlrrsr4nPguSycI=; b=KngkKAyz+/nVYAlKrmdGBZkLUOmEjw5qbGdDEUe9gmjlky7yIIoa8eGONRjKUTnxtc IHxOkjGCu4RnOYDMYO3ikomnnQxPHUxIzZUSxDV7cKJQuBjLpwl6a+Jp78VsatpqYQ+Y 1H7zawro0BzfKWBXRU/F8bNK0A+4hGAER5b/3J0vGg2QNT6lT0acv0ckvZbh+0JYnM/6 EorBqSIIzszpNx5f7u8K29P3ne0MksIYRGa0vYK3+cYSEXFHDV5zGOg4qcFz3mHq2RGa fGHur7QdtHsvMAAlcsGO1J3DUi3TSGycgHO/4qQ0lArYT9qcA5qou58xw6DVKkppypeJ FlTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=d4ZufZ3RXND/PLCh9rxS8MKfhqJdJlrrsr4nPguSycI=; b=b8TlkEHS47VTG4yb8tfDtk6WAfaPUG+Eeuz4wATqTxCDKNt89U0lCUdEerKr5m4YkE bZnMXRobN+jS3Swowl3d+Vm5wZYanwBKHalh5ql44b2viAV3ZjXmPSJtcoZz6/muMcqq IVU08pHjIikrDZWe+CGB64j4WpdcXBmfqawhIsU4eYz8qtyOtACw2L4qno4cXUWgctzR 4THElf4PE/psywJuJBPMk85qCvhHAkUYRACzaPkWsYO9KhVcm3LUDQlHqkov9Uwnzi28 dhBzDb1MFIac3iAQyLdVRMlZXycS0Se/q0FwvZVRbdLARQ+S2Qw2d2fGjoJwQJe0DT9A muEw==
X-Gm-Message-State: APjAAAXI6bhQqRu5U7pC3rB6vbJKk5gdSwxmEioe2PVpggihMIR7aclo nPMYh7ZaFh14BEjbycd4Jfc=
X-Google-Smtp-Source: APXvYqyEQjdVM5pnVrevCglHzqXGhfPp49zBDK/oFRkkhSMMgYW6qVmwkMTkNkg8o1yo0JaqjEaLaA==
X-Received: by 2002:a17:902:a588:: with SMTP id az8mr28894391plb.184.1570451956622;  Mon, 07 Oct 2019 05:39:16 -0700 (PDT)
Received: from [192.168.1.43] (43x235x73x247.ap43.ftth.ucom.ne.jp. [43.235.73.247]) by smtp.gmail.com with ESMTPSA id k8sm11974904pgm.14.2019.10.07.05.39.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 07 Oct 2019 05:39:15 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-6D1551B7-F9EC-4902-BD80-8856770AD6A6
Content-Transfer-Encoding: 7bit
From: lef mutualauth <lef.mutualauth@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 7 Oct 2019 21:39:12 +0900
Message-Id: <3E30D491-724C-42B3-9BD0-B62C7215BABC@gmail.com>
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi>
Cc: art@ietf.org
In-Reply-To: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi>
To: Ggh <ggh@multi.fi>
X-Mailer: iPhone Mail (17A861)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/yRbCzq13gyzegbs73RJT9oH3QoU>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Oct 2019 12:39:19 -0000

--Apple-Mail-6D1551B7-F9EC-4902-BD80-8856770AD6A6
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi,=20

I think your opinion is correct.

https://datatracker.ietf.org/wg/atompub/about/

--=20
HAYASHI, Tatsuya / from iPhone
<hayashi@lepidum.co.jp>
Lepidum Co. Ltd.

> 2019/10/07 21:29=E3=80=81Ggh <ggh@multi.fi>=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=
=AB:
>=20
> =EF=BB=BF
> Hello,
>=20
> My name is Greg, and would like to ask if this list is a good place to dis=
cuss
> RSS and its possible use?
>=20
> Thank you,
> Greg
>=20
> Tell me, and I forget. Ask me, and I discover...
>=20
>=20
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art

--Apple-Mail-6D1551B7-F9EC-4902-BD80-8856770AD6A6
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"><div><br></div><div>Hi,&nbsp;</div><div><br=
></div><div>I think your opinion is correct.</div><div><br></div><p style=3D=
"margin: 0px; font-stretch: normal; font-size: 12px; line-height: normal; fo=
nt-family: Helvetica;">https://datatracker.ietf.org/wg/atompub/about/</p><br=
><div dir=3D"ltr"><div>--&nbsp;</div><div>HAYASHI, Tatsuya /&nbsp;<span clas=
s=3D"Apple-style-span" style=3D"-webkit-tap-highlight-color: rgba(26, 26, 26=
, 0.294118);">from iPhone</span></div><div>&lt;hayashi@lepidum.co.jp&gt;</di=
v><div>Lepidum Co. Ltd.</div></div><div dir=3D"ltr"><br><blockquote type=3D"=
cite">2019/10/07 21:29=E3=80=81Ggh &lt;ggh@multi.fi&gt;=E3=81=AE=E3=83=A1=E3=
=83=BC=E3=83=AB:<br><br></blockquote></div><blockquote type=3D"cite"><div di=
r=3D"ltr">=EF=BB=BF<span></span><br><span>Hello,</span><br><span></span><br>=
<span>My name is Greg, and would like to ask if this list is a good place to=
 discuss</span><br><span>RSS and its possible use?</span><br><span></span><b=
r><span>Thank you,</span><br><span>Greg</span><br><span></span><br><span>Tel=
l me, and I forget. Ask me, and I discover...</span><br><span></span><br><sp=
an></span><br><span>_______________________________________________</span><b=
r><span>art mailing list</span><br><span>art@ietf.org</span><br><span>https:=
//www.ietf.org/mailman/listinfo/art</span><br></div></blockquote></body></ht=
ml>=

--Apple-Mail-6D1551B7-F9EC-4902-BD80-8856770AD6A6--


From nobody Mon Oct  7 05:40:15 2019
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAF76120018 for <art@ietfa.amsl.com>; Mon,  7 Oct 2019 05:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 n85jg9HG5bU1 for <art@ietfa.amsl.com>; Mon,  7 Oct 2019 05:40:11 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4: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 71B621200CC for <art@ietf.org>; Mon,  7 Oct 2019 05:40:11 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 638D1281150; Mon,  7 Oct 2019 14:40:09 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id 5D78928118D; Mon,  7 Oct 2019 14:40:09 +0200 (CEST)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 560D4281150; Mon,  7 Oct 2019 14:40:09 +0200 (CEST)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 52129642BE40; Mon,  7 Oct 2019 14:40:09 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 415CD4027B; Mon,  7 Oct 2019 14:39:44 +0200 (CEST)
Date: Mon, 7 Oct 2019 14:39:44 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Ggh <ggh@multi.fi>
Cc: art@ietf.org
Message-ID: <20191007123944.GA3893@nic.fr>
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi>
X-Operating-System: Debian GNU/Linux 10.1
X-Kernel: Linux 4.19.0-6-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Bogosity: No, tests=bogofilter, spamicity=0.000222, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2019.10.7.123017
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/brGHUo0tSh-zxA5adm5TT2cozjQ>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Oct 2019 12:40:14 -0000

On Mon, Oct 07, 2019 at 03:29:05PM +0300,
 Ggh <ggh@multi.fi> wrote 
 a message of 16 lines which said:

> if this list is a good place to discuss RSS and its possible use?

You may, but RSS is not an IETF format so people may be more
interested in discussions about Atom? (Hard to say more, since you did
not provide details.)


From nobody Tue Oct  8 02:12:10 2019
Return-Path: <ggh@multi.fi>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADE9D120132 for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 02:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 eIbKhrHpWuGd for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 02:12:05 -0700 (PDT)
Received: from webmail.multi.fi (webmail.multi.fi [85.134.37.159]) (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 30AD112006B for <art@ietf.org>; Tue,  8 Oct 2019 02:12:04 -0700 (PDT)
Received: from webmail.multi.fi (localhost [IPv6:::1]) by webmail.multi.fi (Postfix) with ESMTPS id 15B5D18000BC for <art@ietf.org>; Tue,  8 Oct 2019 12:12:02 +0300 (EEST)
Received: from [109.240.78.199] ([109.240.78.199]) by webmail.multi.fi (Horde Framework) with HTTPS; Tue, 08 Oct 2019 12:12:02 +0300
Date: Tue, 08 Oct 2019 12:12:02 +0300
Message-ID: <20191008121202.Horde.5L0ZpLmkJxbNcfmV2Jz8JWg@webmail.multi.fi>
From: Ggh <ggh@multi.fi>
To: art@ietf.org
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi> <20191007123944.GA3893@nic.fr>
In-Reply-To: <20191007123944.GA3893@nic.fr>
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/_uZyEZYvr4R5psV5EJwOsEgnhcM>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 09:12:08 -0000

Hi,

Well...,

I think it is a bit wicked that what is used is RSS2.0 (more or less)  
as far as I can tell.

Would it not be a better route to take to standardise RSS2(and similar) than
atom(which catches less attraction)?

My opinion,
Thank's,
Greg

> Quoting Stephane Bortzmeyer <bortzmeyer@nic.fr>:ta
> On Mon, Oct 07, 2019 at 03:29:05PM +0300,
>  Ggh <ggh@multi.fi> wrote
>  a message of 16 lines which said:
>> if this list is a good place to discuss RSS and its possible use?
> ?
> You may, but RSS is not an IETF format so people may be more
> interested in discussions about Atom? (Hard)  to say more, since you did
> not provide details.)
>
> __________________________) _____________________
> art mailing list
> art@ietf.orge https://www.ietf.org/mailman/listinfo/art



Tell me, and I forget. Ask me, and I discover...



From nobody Tue Oct  8 02:56:02 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75462120164 for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 02:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 YuEDwxccj0xe for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 02:55:51 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 5480A120271 for <art@ietf.org>; Tue,  8 Oct 2019 02:55:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1570528544; bh=xnfXp5PySAePgzXLWLubvvF+3qPy3/YwMPpRJCnkzIg=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=Y4HCwilLZYAxzMNWbqXBpzmYX8Pzngl5BVgFYkXhyoyMFfCH/jxXFx02cCq/twfRZ bVEDYdDYy+1+2fwWOW0w/TExT0D696Mm+sUaKb9nK5ZImggK2d03b2TonXPgXNWVJs lt9tCQALXEalw6p15m6lvOHYkrk6tIVmeVh6cCiU=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1Msq2E-1hy2TP3ggC-00tB7U; Tue, 08 Oct 2019 11:55:43 +0200
To: Ggh <ggh@multi.fi>, art@ietf.org
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi> <20191007123944.GA3893@nic.fr> <20191008121202.Horde.5L0ZpLmkJxbNcfmV2Jz8JWg@webmail.multi.fi>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <38b94eec-7934-12b7-f638-d4b69523192d@gmx.de>
Date: Tue, 8 Oct 2019 11:55:42 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <20191008121202.Horde.5L0ZpLmkJxbNcfmV2Jz8JWg@webmail.multi.fi>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:jpwZash7u2qzrcA45XE76h299/TMo8HW8UJIYXKSXcEgm+jvbNt 93r/PNzfPUK04wm+4WFgb/dV7UfSnfDxGfKtLhhanXHHkve329NRZn7NLy2q7UVy34Y31qx JP7eqwrJrE9WhhbLygMmKZm80rqTcZi4tiZGTdfhplgs8WPDpWEAthNIw4VEM5TeGU5rVcC gJyDHnt9wJLh7h2vDlbpw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:NubhcDGW6PU=:BGD0KspwH+iNPhUYs6Biyb nocI3SmdgpaoJGDd55I+ZE62czqNUPLCeehE2d0/1sj4+PO7w1cAqbxAMSHXX/MJDoVaZ55F4 aMbkXitIx9V5gLvWzLZN+QK0YLAtEah7YyOhX7DHmokD4F5K41jryoJPFVdHoS7uPV6/AQT/k kO+qcRSofoGgBwkoFj4oWIwuwrmBV9m6MLgOtjrmBTcrATgRwxT6ULGMW0iliCyLsG0v9Kp1w D+C9b9TuhHWm3w1Vr0DX0Y4sVaDzzaCD8OsA3NJIuNkr9xFFRELYLR+crnUdvRkxzVELGRiEu 9cWvC3i7cOaRBzrCIMFSNDKHzerJbgwfgn+N4KjITq5mUA+HrVs+G5TnTx97W3C0T0fu5QVaK hTbfs0HeklOzauokD6ik/q/oItu22T+JUdgq9vEqq0o9BVZVl/XjJjznLEhjBVdHk5sHmwYSc fA7N2bXtmODxNuL9NZryyZlBVrFDLvRPlsswnKTq4Ao/xOYaSeCQOribP3MMU6/4KxhfbW4eG EAhNBNxPqtkBZhlrzatQyMK91XNly5an6ppQtMHfJbOHKCOXEEUVfxBPo9hm5Kg8W0YsD47Px aHbj/UkzE5PMuz38+hRmcYyY+hptSHLzGp9mWFPjyY1RgRv1X3J4HjyTOBNdq8HSRr2Da0Jqe 9b10lO7TF/JaE6fpIo7V9evJF5qNuEd5m7DuaTDlFa3ownKvhXFy4evSaYZmL1tkm0ERbi4PP PUqEfHSM4xzZcrDawvfohvvLFBjEnX6InNrNtUogealxFPeGIufPkSqH/G/RuyeifassDv8T6 JoVXM9IXix0mP6/w1gKEyVW4IXaC3Oh0vLQJ8NbPyKoOdC1oXTDm9DT1agHrQtzFDaVrOPqLq +pAoelNCCwuH9J7NoyJIWNofdTDg2RhN1/knRLn1HdznC5CyKommx0/TCPyLwH+vIf5My7H0S qK+UgJ/LiEwCwTLulJab3JnLjC7YVYSW9FwPL78zhODH8oaGhmXSWQ8MzywGxbkHERTecrlNw An1h5ALHOLrjslVda8Zv4yAJ7hOG1N3TD1MwhTCqCPcRMkGkU3y577hWLtInYrL5n5MYr1EFh A7Gr+VuyoNI6D1qU3ZVTlecPSIV8/y+wVwCZm1w4m8GFrH+RmMdWLtFVvUqMS/lgSBd1OLaqX qrU/KWTWBIQrhGBW06/S7JoBDeTwbnD2RDQWE6K2h9tzwNO2RROEfhNpAXQ4Bwc9P6ODfYUUp 7ia2Zzt2eflkqIx8iMejjxauu9Fodn8jjr5MPZCfy7c/JkCrKKcaz6rO5xvs=
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/0EubSxMynwebmdv9mkeeo8ZsAOM>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 09:56:01 -0000

On 08.10.2019 11:12, Ggh wrote:
> Hi,
>
> Well...,
>
> I think it is a bit wicked that what is used is RSS2.0 (more or less) as
> far as I can tell.
>
> Would it not be a better route to take to standardise RSS2(and similar)
> than
> atom(which catches less attraction)?
>
> My opinion,
> Thank's,
> Greg

Uh.

There was a reason why the WG defined a new format instead of fixing the
existing ones. I was going to point you the the WG's mail archive, as
linked from <https://datatracker.ietf.org/wg/atompub/charter/>, but it
seems to be gone.

Does anybody know whether there's a copy of
<https://www.imc.org/atom-syntax/mail-archive/>?

Best regards, Julian


From nobody Tue Oct  8 04:47:17 2019
Return-Path: <edward.vielmetti@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D84791200FE for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 04:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 xtc-aMiaxiKG for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 04:47:12 -0700 (PDT)
Received: from mail-ua1-x930.google.com (mail-ua1-x930.google.com [IPv6:2607:f8b0:4864:20::930]) (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 8BC3612002E for <art@ietf.org>; Tue,  8 Oct 2019 04:47:12 -0700 (PDT)
Received: by mail-ua1-x930.google.com with SMTP id w7so5061209uag.4 for <art@ietf.org>; Tue, 08 Oct 2019 04:47:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1Ke3qcf9OQBiG5BR037dt+dkdJhPYE/xuxusaTQOr94=; b=H7hwLiHcS12b9Y9hlGLTIYBmInnHLyMyHOQ7awxSUe7PzvPw3NyaZvP/zXeiYCGTzg Y3j0T6uC5gEiM6P4qGEwKxlJjKycD3iRsvLatlglGr0gFOkfFYoDUAFplGsad3vjoe2Q vBwjhhN7HMQcLCT6cV7jsekpw/ihdbhPwKnHOZYgKFhr4Z72ClYSeyV3oFd730Sn0xuk bZ1XKFKAbGqfBuNAygyIri1m177M6WauRLvDvV6WFF2py6R6A06miLpVmbWjv8sk1m7n T+kylH0+S268hR4oeZS04tuJ4Fv5q1UF0CXfBEYgMH6TsuT4P4xEtHmuI7eqGue+joRC VBcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1Ke3qcf9OQBiG5BR037dt+dkdJhPYE/xuxusaTQOr94=; b=ZATFNSWG4tmQJXlCYpRtz4qxkYx0fWmqCN/tGaZFillN9/hbB3SQeM5Rlww8CdDkgA VhYVA+KmVlglpAEl0Pdm6hEspJAjIPixcjR2pVyoEauqTLAAJvVVDECPT51Tglc7kwMX q3erNXcPnGMyLo2Pt8nNX0ULJrXFRt35rI3+Ap4x+17LvX/1RcLDlRLkoJN30dihNAYb NbuoBhSJLgtoUBWzOsnV7hHmIhkt2fOrljfXXUI/RzZnaHcJ3ELm/ifeBsQ1BVJwILbJ nQvLIFuiqVjVHHWGknSj9nbK/PldpYEAJMbuFpP3uz5VMUCCyTPGq+Gm5YUsTb3yevUn WLJg==
X-Gm-Message-State: APjAAAU0bNRlPMmr73IG2TdhmXnXUhcJt9elaYwheoqHyp9Gs0e9kyH7 +t0NUtdihB4LqJhJg7U70R+WdMOn3/NGQOKXSw4=
X-Google-Smtp-Source: APXvYqwjIrEKiDMWr5tR2GFmtpALl+7unwBAKvZupHKn/c+HNNqSrbjE0L8Sk+p6yIRkCnA35h+ujIY+Z8SoZRFxL/s=
X-Received: by 2002:ab0:6691:: with SMTP id a17mr16709544uan.21.1570535231437;  Tue, 08 Oct 2019 04:47:11 -0700 (PDT)
MIME-Version: 1.0
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi> <20191007123944.GA3893@nic.fr> <20191008121202.Horde.5L0ZpLmkJxbNcfmV2Jz8JWg@webmail.multi.fi> <38b94eec-7934-12b7-f638-d4b69523192d@gmx.de>
In-Reply-To: <38b94eec-7934-12b7-f638-d4b69523192d@gmx.de>
From: Edward Vielmetti <edward.vielmetti@gmail.com>
Date: Tue, 8 Oct 2019 04:46:34 -0700
Message-ID: <CAPRZce0EQOedTtdFSvy81XCWJ4j6P=6GfPu8g7hVWH9RRnhCog@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Ggh <ggh@multi.fi>, art@ietf.org
Content-Type: multipart/alternative; boundary="00000000000093bef2059464ba22"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/8ueeiHn9M44UCQcryEQDG0AtLI0>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 11:47:15 -0000

--00000000000093bef2059464ba22
Content-Type: text/plain; charset="UTF-8"

Perhaps an informational, non-normative RFC describing in some loving
detail the RSS in actual use in the wild would be a service to the
community. I'm thinking something similar in scope and style to RFC 1436
(Gopher protocol).

On Tue, Oct 8, 2019 at 2:56 AM Julian Reschke <julian.reschke@gmx.de> wrote:

> On 08.10.2019 11:12, Ggh wrote:
> > Hi,
> >
> > Well...,
> >
> > I think it is a bit wicked that what is used is RSS2.0 (more or less) as
> > far as I can tell.
> >
> > Would it not be a better route to take to standardise RSS2(and similar)
> > than
> > atom(which catches less attraction)?
> >
> > My opinion,
> > Thank's,
> > Greg
>
> Uh.
>
> There was a reason why the WG defined a new format instead of fixing the
> existing ones. I was going to point you the the WG's mail archive, as
> linked from <https://datatracker.ietf.org/wg/atompub/charter/>, but it
> seems to be gone.
>
> Does anybody know whether there's a copy of
> <https://www.imc.org/atom-syntax/mail-archive/>?
>
> Best regards, Julian
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art
>


-- 
Edward Vielmetti +1 734 330 2465
edward.vielmetti@gmail.com

--00000000000093bef2059464ba22
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Perhaps an informational, non-normative RFC describing in =
some loving detail the RSS in actual use in the wild would be a service to =
the community. I&#39;m thinking something similar in scope and style to RFC=
 1436 (Gopher protocol).</div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Tue, Oct 8, 2019 at 2:56 AM Julian Reschke &lt;<=
a href=3D"mailto:julian.reschke@gmx.de">julian.reschke@gmx.de</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 08.10.2019 =
11:12, Ggh wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; Well...,<br>
&gt;<br>
&gt; I think it is a bit wicked that what is used is RSS2.0 (more or less) =
as<br>
&gt; far as I can tell.<br>
&gt;<br>
&gt; Would it not be a better route to take to standardise RSS2(and similar=
)<br>
&gt; than<br>
&gt; atom(which catches less attraction)?<br>
&gt;<br>
&gt; My opinion,<br>
&gt; Thank&#39;s,<br>
&gt; Greg<br>
<br>
Uh.<br>
<br>
There was a reason why the WG defined a new format instead of fixing the<br=
>
existing ones. I was going to point you the the WG&#39;s mail archive, as<b=
r>
linked from &lt;<a href=3D"https://datatracker.ietf.org/wg/atompub/charter/=
" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/wg/atom=
pub/charter/</a>&gt;, but it<br>
seems to be gone.<br>
<br>
Does anybody know whether there&#39;s a copy of<br>
&lt;<a href=3D"https://www.imc.org/atom-syntax/mail-archive/" rel=3D"norefe=
rrer" target=3D"_blank">https://www.imc.org/atom-syntax/mail-archive/</a>&g=
t;?<br>
<br>
Best regards, Julian<br>
<br>
_______________________________________________<br>
art mailing list<br>
<a href=3D"mailto:art@ietf.org" target=3D"_blank">art@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/art" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/art</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature">Edward Vielmetti=C2=A0+1 734 330 2465<div><a hre=
f=3D"mailto:edward.vielmetti@gmail.com" target=3D"_blank">edward.vielmetti@=
gmail.com</a></div><div><br></div></div>

--00000000000093bef2059464ba22--


From nobody Tue Oct  8 05:49:45 2019
Return-Path: <sm@elandsys.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16D9F120800 for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 05:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 GAouJyT4EFpC for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 05:49:43 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 66B651200F9 for <art@ietf.org>; Tue,  8 Oct 2019 05:49:43 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.168.90]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x98CnJtG009611 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Oct 2019 05:49:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1570538974; x=1570625374; i=@elandsys.com; bh=HFZW980jJtNaoucVFu4bclx1ps6Cgy7G5YfqZ2QRFo8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=XHV1+2N9vKruR4HCqR2KH1XlC1+GDYZOJo8FfkxoyR1Y2ODSa+hNIVxP5YycelcBC apC7i+aZP+ie1EP3AoLJuvftbtUuOkLJPeiP8jeRWXQfiPpEC0bfZ1N97+fC7gY0Xa 37zYIMzqDjRVhJ06zpfAXA2B9jU8XIZP+BapdAo4=
Message-Id: <6.2.5.6.2.20191008052000.0c9ae410@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 Oct 2019 05:48:41 -0700
To: Edward Vielmetti <edward.vielmetti@gmail.com>, Julian Reschke <julian.reschke@gmx.de>, art@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Ggh <ggh@multi.fi>
In-Reply-To: <CAPRZce0EQOedTtdFSvy81XCWJ4j6P=6GfPu8g7hVWH9RRnhCog@mail.g mail.com>
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi> <20191007123944.GA3893@nic.fr> <20191008121202.Horde.5L0ZpLmkJxbNcfmV2Jz8JWg@webmail.multi.fi> <38b94eec-7934-12b7-f638-d4b69523192d@gmx.de> <CAPRZce0EQOedTtdFSvy81XCWJ4j6P=6GfPu8g7hVWH9RRnhCog@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/OWzEsTR97KXywerbghZIu3nng4U>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 12:49:44 -0000

Hello,
At 04:46 AM 08-10-2019, Edward Vielmetti wrote:
>Perhaps an informational, non-normative RFC describing in some 
>loving detail the RSS in actual use in the wild would be a service 
>to the community. I'm thinking something similar in scope and style 
>to RFC 1436 (Gopher protocol).

The IPR for the RSS specification is owned by an organization which 
is unrelated to the IETF.  The persons volunteering to write the 
Internet-Draft may have to seek the relevant approval.

For what it is worth, there may be some confusion given that the term 
"RSS" is also used to refer to feeds formatted according to RFC 4287.

Regards,
S. Moonesamy  


From nobody Tue Oct  8 05:54:58 2019
Return-Path: <edward.vielmetti@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36D121207FD for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 05:54:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 uShv7dLvEU_K for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 05:54:55 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 44842120033 for <art@ietf.org>; Tue,  8 Oct 2019 05:54:55 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id v10so11199808vsc.7 for <art@ietf.org>; Tue, 08 Oct 2019 05:54:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/r0/aEagHhWdyRx9I6RXVbuP+cjPmMXmmr5ucLk+7yM=; b=L8iYmiwhqoamFJplXdRzHspe6cZjos1PybVY4MpAXE/XneVkROxLwN8CkZQN93u9fg rz3QTNojYHdzGD5RkBglZfdWDcPRmisQ6vNdWaC6EvkRGBKimv4xKjHKNVFXYnVEitpM GaWEITR1aQB0ZiMiZboUktng1xUK2pWTWWP3BMc4rpV4DXgZaQvWE07929XXKsIrJoNk xqpQxNVWGkUDt9ZWGNwAu2EGnRmhBxL9VSeygxtuitGT8u4+916ChcUC7Uxbz2tIsIJI MlIoPCvIrI6suBa/AFA7+zrxvQT99CgGYwcGlglzJA+FByYT5DABe8XoG5iKsk+mc4+i 3Zjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/r0/aEagHhWdyRx9I6RXVbuP+cjPmMXmmr5ucLk+7yM=; b=rTTifrBP226QEpwv1hIGxJwtfvoIcKUQu4ISKtl4VIoaD346W7sLUn3HcBBaDG1WuC /JWc3XZOpbtvICJm5/ub6RVkmDwK96u0g9dM98f+JOXWNJQA/1PwnhjUutzLXb7F6HGf pHCeWrpYIHmzlCAZ9hHMROphnOceecyhkUDa0XQQUK69uM2vDNiufGynqhpLQXrGCI2O fBuOvdosstAT1GCcNYdpo4CC56OblPjxef7cCPyz4owP+3rirKz8+wRm/GUQ5IrPqUTl ze7xR6qEJUq+LL+DHfjAZenDr6YD/05AccC08hwl6ZOIdVuemhfEzgaH5ZHaTH4Z4fB9 xrZQ==
X-Gm-Message-State: APjAAAX6T7m86Zw2J3bnlvPdlVJgmYVjsarV8bBa8rWoGu6B2doW/mxt jB/fVWjB8zaD4qMR5c5QvHDcgpijcILW7aIEGLY=
X-Google-Smtp-Source: APXvYqwuVYaNP4vIjL3hs7mSNVex/milBTn4fNAsnD08nJrBQLPRtbZCuvjkI7mxMVEVk5asIL/l7qPM3x3p0aok9rI=
X-Received: by 2002:a67:77ce:: with SMTP id s197mr17299851vsc.211.1570539294310;  Tue, 08 Oct 2019 05:54:54 -0700 (PDT)
MIME-Version: 1.0
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi> <20191007123944.GA3893@nic.fr> <20191008121202.Horde.5L0ZpLmkJxbNcfmV2Jz8JWg@webmail.multi.fi> <38b94eec-7934-12b7-f638-d4b69523192d@gmx.de> <CAPRZce0EQOedTtdFSvy81XCWJ4j6P=6GfPu8g7hVWH9RRnhCog@mail.gmail.com> <6.2.5.6.2.20191008052000.0c9ae410@elandnews.com>
In-Reply-To: <6.2.5.6.2.20191008052000.0c9ae410@elandnews.com>
From: Edward Vielmetti <edward.vielmetti@gmail.com>
Date: Tue, 8 Oct 2019 05:54:42 -0700
Message-ID: <CAPRZce2YQdvYUHYAhy7uEmwMAwO3Jdy_f79uneS4a_3zEanFvg@mail.gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, art@ietf.org, Ggh <ggh@multi.fi>
Content-Type: multipart/alternative; boundary="000000000000be4cc2059465ace4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/L29dqjyljdBY9bgdhJR25FGI24M>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 12:54:57 -0000

--000000000000be4cc2059465ace4
Content-Type: text/plain; charset="UTF-8"

Just to clarify, by IPR you mean Intellectual Property Rights? If so,
please cite a specific reference.

On Tue, Oct 8, 2019, 05:49 S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hello,
> At 04:46 AM 08-10-2019, Edward Vielmetti wrote:
> >Perhaps an informational, non-normative RFC describing in some
> >loving detail the RSS in actual use in the wild would be a service
> >to the community. I'm thinking something similar in scope and style
> >to RFC 1436 (Gopher protocol).
>
> The IPR for the RSS specification is owned by an organization which
> is unrelated to the IETF.  The persons volunteering to write the
> Internet-Draft may have to seek the relevant approval.
>
> For what it is worth, there may be some confusion given that the term
> "RSS" is also used to refer to feeds formatted according to RFC 4287.
>
> Regards,
> S. Moonesamy
>
>

--000000000000be4cc2059465ace4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Just to=C2=A0clarify, by IPR you mean Intellectual Proper=
ty Rights? If so, please cite a specific reference.</div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 8, 2019, 05:=
49 S Moonesamy &lt;<a href=3D"mailto:sm%2Bietf@elandsys.com">sm+ietf@elands=
ys.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
At 04:46 AM 08-10-2019, Edward Vielmetti wrote:<br>
&gt;Perhaps an informational, non-normative RFC describing in some <br>
&gt;loving detail the RSS in actual use in the wild would be a service <br>
&gt;to the community. I&#39;m thinking something similar in scope and style=
 <br>
&gt;to RFC 1436 (Gopher protocol).<br>
<br>
The IPR for the RSS specification is owned by an organization which <br>
is unrelated to the IETF.=C2=A0 The persons volunteering to write the <br>
Internet-Draft may have to seek the relevant approval.<br>
<br>
For what it is worth, there may be some confusion given that the term <br>
&quot;RSS&quot; is also used to refer to feeds formatted according to RFC 4=
287.<br>
<br>
Regards,<br>
S. Moonesamy=C2=A0 <br>
<br>
</blockquote></div>

--000000000000be4cc2059465ace4--


From nobody Tue Oct  8 06:10:22 2019
Return-Path: <edward.vielmetti@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A003120807 for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 06:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 FAVls9mwDEeS for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 06:10:18 -0700 (PDT)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (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 54F22120052 for <art@ietf.org>; Tue,  8 Oct 2019 06:10:18 -0700 (PDT)
Received: by mail-vs1-xe34.google.com with SMTP id m22so11228787vsl.9 for <art@ietf.org>; Tue, 08 Oct 2019 06:10:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VqDh58wLPyvXN3jUJRZez1mZzUqPmOnEdIX7kJFjeEs=; b=mOnbBfz5as9Pf09/eVHFitHlfmwLd8jrm33xqv1hJkqYrVYD9KDSnQUMpuB7m4ivV+ 5J4zB2+ARoOR1l/8kN6LmwCXJdF+ARtbfBJTePyD8l/xcSDmiIp6KEDu+p4THjzi+pX8 3h6XYsyxS5x+4JZ8IHeZkwHsNcSB8H0NLEtitchVG34IsGZx6TgdMOKBN2GFA54PE/a8 CBrAcVsujJn3tYKC9iPMlyIgcNBMURx7ChSOjZhqOu6MdZpOg8ih0NNh92oKCT7NxtLk LSpqMgK0Qtq1iGm6ITwmh0Q7FOFEcXXkIAWZY9ZzJQer/3gCJjyTZPIPlccBgdIkGrnV rSBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VqDh58wLPyvXN3jUJRZez1mZzUqPmOnEdIX7kJFjeEs=; b=eWM0sDiF/ueAE9T4EXJPAzywdKSGScaX5fx8EVY2/pgSxfvEYiimCk6jFaZJQKO95r EHUW1/nTMIFdhRSBoHYHS3bktEhw4gumjUq1fDkZKU5QlaU5Rlb89QPw7WBHdy9y/E2t u4NOqVzdnm8Q7HPAcMWZ9CXOWo7qr53KqePMsCjxYlfY9aqm0slhxtdXskQP9I71ZwQ1 NsbZ/R8jzX1yL3ouwFwoq1q+UkAiMs2OBadkm1lJFDqobXpPf1SYR7MddTPerRCOnnGV V0AuC+3scuyXpE21I+bMStLuxk6B1uCNMtHHhq8zUfR7+JWCwYlDlGL2ImQhJ9KO6ZwU NJSQ==
X-Gm-Message-State: APjAAAXtQy0U+qzISosHtHHlM6mrXSHqIHTxsCj9cKMPP2Dene2jtpZR 0nXXZX7j6c0bnpEzw+w3JiuvgFcUL6VJnsrbg3A=
X-Google-Smtp-Source: APXvYqy9F0KaCmresAt1dRELIVKBsi6nN1OZzTdAWveG7CWiXbh9E4b/VjhY7lqdF10VLOy/46h0abgjrRaurTq2ysU=
X-Received: by 2002:a67:2e01:: with SMTP id u1mr18928828vsu.44.1570540217143;  Tue, 08 Oct 2019 06:10:17 -0700 (PDT)
MIME-Version: 1.0
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi> <20191007123944.GA3893@nic.fr> <20191008121202.Horde.5L0ZpLmkJxbNcfmV2Jz8JWg@webmail.multi.fi> <38b94eec-7934-12b7-f638-d4b69523192d@gmx.de> <CAPRZce0EQOedTtdFSvy81XCWJ4j6P=6GfPu8g7hVWH9RRnhCog@mail.gmail.com> <6.2.5.6.2.20191008052000.0c9ae410@elandnews.com> <CAPRZce2YQdvYUHYAhy7uEmwMAwO3Jdy_f79uneS4a_3zEanFvg@mail.gmail.com>
In-Reply-To: <CAPRZce2YQdvYUHYAhy7uEmwMAwO3Jdy_f79uneS4a_3zEanFvg@mail.gmail.com>
From: Edward Vielmetti <edward.vielmetti@gmail.com>
Date: Tue, 8 Oct 2019 06:09:40 -0700
Message-ID: <CAPRZce1YOMR6_9M_0gXQQo7uP39d+Sxo-prp0ahHT5BJ8bOSWw@mail.gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, art@ietf.org, Ggh <ggh@multi.fi>
Content-Type: multipart/alternative; boundary="000000000000bf95c3059465e33f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/-3V92w21a_bORU79UOLECSnpTRU>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 13:10:21 -0000

--000000000000bf95c3059465e33f
Content-Type: text/plain; charset="UTF-8"

I do not see the string "RSS" anywhere in RFC 4287, so I don't consider
that RFC an impediment to any future work.

On Tue, Oct 8, 2019 at 5:54 AM Edward Vielmetti <edward.vielmetti@gmail.com>
wrote:

> Just to clarify, by IPR you mean Intellectual Property Rights? If so,
> please cite a specific reference.
>
> On Tue, Oct 8, 2019, 05:49 S Moonesamy <sm+ietf@elandsys.com> wrote:
>
>> Hello,
>> At 04:46 AM 08-10-2019, Edward Vielmetti wrote:
>> >Perhaps an informational, non-normative RFC describing in some
>> >loving detail the RSS in actual use in the wild would be a service
>> >to the community. I'm thinking something similar in scope and style
>> >to RFC 1436 (Gopher protocol).
>>
>> The IPR for the RSS specification is owned by an organization which
>> is unrelated to the IETF.  The persons volunteering to write the
>> Internet-Draft may have to seek the relevant approval.
>>
>> For what it is worth, there may be some confusion given that the term
>> "RSS" is also used to refer to feeds formatted according to RFC 4287.
>>
>> Regards,
>> S. Moonesamy
>>
>>

-- 
Edward Vielmetti +1 734 330 2465
edward.vielmetti@gmail.com

--000000000000bf95c3059465e33f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I do not see the string &quot;RSS&quot; anywhere in RFC 42=
87, so I don&#39;t consider that RFC an impediment to any future work.</div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tu=
e, Oct 8, 2019 at 5:54 AM Edward Vielmetti &lt;<a href=3D"mailto:edward.vie=
lmetti@gmail.com">edward.vielmetti@gmail.com</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">Just to=C2=A0=
clarify, by IPR you mean Intellectual Property Rights? If so, please cite a=
 specific reference.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Tue, Oct 8, 2019, 05:49 S Moonesamy &lt;<a href=3D"m=
ailto:sm%2Bietf@elandsys.com" target=3D"_blank">sm+ietf@elandsys.com</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<=
br>
At 04:46 AM 08-10-2019, Edward Vielmetti wrote:<br>
&gt;Perhaps an informational, non-normative RFC describing in some <br>
&gt;loving detail the RSS in actual use in the wild would be a service <br>
&gt;to the community. I&#39;m thinking something similar in scope and style=
 <br>
&gt;to RFC 1436 (Gopher protocol).<br>
<br>
The IPR for the RSS specification is owned by an organization which <br>
is unrelated to the IETF.=C2=A0 The persons volunteering to write the <br>
Internet-Draft may have to seek the relevant approval.<br>
<br>
For what it is worth, there may be some confusion given that the term <br>
&quot;RSS&quot; is also used to refer to feeds formatted according to RFC 4=
287.<br>
<br>
Regards,<br>
S. Moonesamy=C2=A0 <br>
<br>
</blockquote></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature">Edward Vielmetti=C2=A0+1 734 330 2465<div><a hre=
f=3D"mailto:edward.vielmetti@gmail.com" target=3D"_blank">edward.vielmetti@=
gmail.com</a></div><div><br></div></div>

--000000000000bf95c3059465e33f--


From nobody Tue Oct  8 06:15:54 2019
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD66120086 for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 06:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 TIJ_oM5XpqKg for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 06:15:51 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4: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 BA72B12004E for <art@ietf.org>; Tue,  8 Oct 2019 06:15:50 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id D675D280819; Tue,  8 Oct 2019 15:15:48 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id CF39628081C; Tue,  8 Oct 2019 15:15:48 +0200 (CEST)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id C7A52280819; Tue,  8 Oct 2019 15:15:48 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id C36EF642A7A5; Tue,  8 Oct 2019 15:15:48 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id AE1DB4024D; Tue,  8 Oct 2019 15:15:23 +0200 (CEST)
Date: Tue, 8 Oct 2019 15:15:23 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Edward Vielmetti <edward.vielmetti@gmail.com>
Cc: S Moonesamy <sm+ietf@elandsys.com>, Julian Reschke <julian.reschke@gmx.de>, art@ietf.org, Ggh <ggh@multi.fi>
Message-ID: <20191008131523.GA29645@nic.fr>
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi> <20191007123944.GA3893@nic.fr> <20191008121202.Horde.5L0ZpLmkJxbNcfmV2Jz8JWg@webmail.multi.fi> <38b94eec-7934-12b7-f638-d4b69523192d@gmx.de> <CAPRZce0EQOedTtdFSvy81XCWJ4j6P=6GfPu8g7hVWH9RRnhCog@mail.gmail.com> <6.2.5.6.2.20191008052000.0c9ae410@elandnews.com> <CAPRZce2YQdvYUHYAhy7uEmwMAwO3Jdy_f79uneS4a_3zEanFvg@mail.gmail.com> <CAPRZce1YOMR6_9M_0gXQQo7uP39d+Sxo-prp0ahHT5BJ8bOSWw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPRZce1YOMR6_9M_0gXQQo7uP39d+Sxo-prp0ahHT5BJ8bOSWw@mail.gmail.com>
X-Operating-System: Debian GNU/Linux 10.1
X-Kernel: Linux 4.19.0-6-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Bogosity: No, tests=bogofilter, spamicity=0.000291, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2019.10.8.130317
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/oXU_tS9kfhJmaS0sAD3fI3KEXfI>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 13:15:53 -0000

On Tue, Oct 08, 2019 at 06:09:40AM -0700,
 Edward Vielmetti <edward.vielmetti@gmail.com> wrote 
 a message of 97 lines which said:

> I do not see the string "RSS" anywhere in RFC 4287, so I don't consider
> that RFC an impediment to any future work.

S. Moonesamy's point was that many people call "RSS" any syndication
format (including Atom).


From nobody Tue Oct  8 06:16:14 2019
Return-Path: <sm@elandsys.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85A2C120882 for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 06:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level: 
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 bvxlqz5PdkaL for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 06:16:05 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 8FFBD1208AB for <art@ietf.org>; Tue,  8 Oct 2019 06:16:05 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.168.90]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x98DFkWm002195 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Oct 2019 06:15:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1570540558; x=1570626958; i=@elandsys.com; bh=ZGtDfP/P7zMplUbzFhh6jvCNXl588DmbpfRTMGNfweY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=aZ13qEYP9o6Yl0Dz/t9sj1YHwxpApwnli4cnKeXecaIJ1GECjp9BmPudbL/eInRQb hAuRFYoGus9alwybimse0CXsR2ItG51BGW94gM3BAm+nxqUHNRayqYOaFpUXEccYyM MUt7kH4CkeQaGP/RV3ZlVci+ZBDKaVBYuxOTY7w8=
Message-Id: <6.2.5.6.2.20191008055829.0a31a158@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 Oct 2019 06:00:28 -0700
To: Edward Vielmetti <edward.vielmetti@gmail.com>, art@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, Ggh <ggh@multi.fi>
In-Reply-To: <CAPRZce2YQdvYUHYAhy7uEmwMAwO3Jdy_f79uneS4a_3zEanFvg@mail.g mail.com>
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi> <20191007123944.GA3893@nic.fr> <20191008121202.Horde.5L0ZpLmkJxbNcfmV2Jz8JWg@webmail.multi.fi> <38b94eec-7934-12b7-f638-d4b69523192d@gmx.de> <CAPRZce0EQOedTtdFSvy81XCWJ4j6P=6GfPu8g7hVWH9RRnhCog@mail.gmail.com> <6.2.5.6.2.20191008052000.0c9ae410@elandnews.com> <CAPRZce2YQdvYUHYAhy7uEmwMAwO3Jdy_f79uneS4a_3zEanFvg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/nhR17nBfv5GQI0jUzYSYN81fp_c>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 13:16:12 -0000

Hi Edward,
At 05:54 AM 08-10-2019, Edward Vielmetti wrote:
>Just to clarify, by IPR you mean Intellectual Property Rights? If 
>so, please cite a specific reference.

Yes.  Please see http://www.rssboard.org/rss-specification

Regards,
S. Moonesamy 


From nobody Tue Oct  8 07:59:08 2019
Return-Path: <rjsparks@nostrum.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0F691200B9 for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 07:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 KQ0MDVlTYtWN for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 07:59:05 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 41DA9120013 for <art@ietf.org>; Tue,  8 Oct 2019 07:59:05 -0700 (PDT)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x98Ex4Ov034617 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <art@ietf.org>; Tue, 8 Oct 2019 09:59:04 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1570546744; bh=pDnd9VrGnn7DNmxwzOYgyiXKSGNgB+o6X9KhLgKDyas=; h=Subject:To:References:From:Date:In-Reply-To; b=Efb2jF1xGxSABpl5SftLjelOfH2xuHScViOCo6tcv8RteLlcc2VDaisJ6zYKMNPCe BpT/3kyn2p4OFze4beGF8UiHh6/fBy2I9Ghz/Yhwxt/dnFYcAPd4J47r1hSjTy4o/O 1LRN+MBsGYMfJSkbcIE5W4mK4yDx7WGrCLPHK4kQ=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: art@ietf.org
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi> <20191007123944.GA3893@nic.fr> <20191008121202.Horde.5L0ZpLmkJxbNcfmV2Jz8JWg@webmail.multi.fi> <38b94eec-7934-12b7-f638-d4b69523192d@gmx.de>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <c2a8cb73-b915-dff1-1703-c97d5c2b100f@nostrum.com>
Date: Tue, 8 Oct 2019 09:59:03 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <38b94eec-7934-12b7-f638-d4b69523192d@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/O2mL9FZtu8HjY4qGtEubdU_kges>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 14:59:07 -0000

Hi Julian -

Does <https://mailarchive.ietf.org/arch/browse/atompub/> contain what 
you're looking for?

RjS

On 10/8/19 4:55 AM, Julian Reschke wrote:
> On 08.10.2019 11:12, Ggh wrote:
>> Hi,
>>
>> Well...,
>>
>> I think it is a bit wicked that what is used is RSS2.0 (more or less) as
>> far as I can tell.
>>
>> Would it not be a better route to take to standardise RSS2(and similar)
>> than
>> atom(which catches less attraction)?
>>
>> My opinion,
>> Thank's,
>> Greg
>
> Uh.
>
> There was a reason why the WG defined a new format instead of fixing the
> existing ones. I was going to point you the the WG's mail archive, as
> linked from <https://datatracker.ietf.org/wg/atompub/charter/>, but it
> seems to be gone.
>
> Does anybody know whether there's a copy of
> <https://www.imc.org/atom-syntax/mail-archive/>?
>
> Best regards, Julian
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art


From nobody Tue Oct  8 08:26:05 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25CF2120086 for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 08:26:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 73OoHI3dM_kx for <art@ietfa.amsl.com>; Tue,  8 Oct 2019 08:26:00 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 ADE8F120026 for <art@ietf.org>; Tue,  8 Oct 2019 08:25:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1570548341; bh=UgAyp6oSa1NUFiNHWr3+2MrJxpnnK3ev0DVXLFLMS/A=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=W+g8XKMUBzaGE97g65LqQzF8EPTXqLzc3pMiZ7Hc/asOBEB+7v+2W9zB4dM4eNlMv kwHX6d/ETECECfq4oV3OXLTYS4YhfujDi8T8pKNH6xMpeZ6Y2RBREnqaiesBjU+R9j ky+p+lBU2XfobOrpHj9szVFgZCpICCN0to8IYOGU=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.81] ([217.91.35.233]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N33Ib-1i5vgG1yjV-013Mfg; Tue, 08 Oct 2019 17:25:41 +0200
To: Robert Sparks <rjsparks@nostrum.com>, art@ietf.org
References: <20191007152905.Horde.QlcAdmZkA3uesm2a0Fp5i79@webmail.multi.fi> <20191007123944.GA3893@nic.fr> <20191008121202.Horde.5L0ZpLmkJxbNcfmV2Jz8JWg@webmail.multi.fi> <38b94eec-7934-12b7-f638-d4b69523192d@gmx.de> <c2a8cb73-b915-dff1-1703-c97d5c2b100f@nostrum.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <ede9dbc5-d1c6-2daf-c23d-417822a9b251@gmx.de>
Date: Tue, 8 Oct 2019 17:25:36 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <c2a8cb73-b915-dff1-1703-c97d5c2b100f@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:IkAj7eB831BKVu6KPFUaskl5zdXWkKycb08ixud01nrU4MpE6X3 Ni7fzeYGREqKT9LLBVHkkFlIsVfezlt5LYpFbMFHbuC0HsUicYx5ZW3paxGqYQNKKtfqHA8 oJrSpQ3kVMk+/F08b59hm0c1xVrFUaMPDLUkg241I9z784aCkVLCK5LYb0RNEhhyqIy7TOT 8pAKPL3FGk6TrbrmaMibA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:t4vZ2jRtZy4=:3tdW/jNnR+iu80mj5feJFY p0/Kcb/rJrlZJ+jVG3IveltGXIlTGDxloj45/UQb15Yxd1LIooyiYkHmgjMwkFuZPRt+mp9nN fcYa35rZtTbVKQDdSL1mCUA0k1uVzYe+iBdcsSe0AkgNR2kNqHnKE8CQLz30fZAmivPFlOEZ2 hGdMyGOprQGg/35CeYa6kTwuoMMgFhcUHut/fp6pYV1YSSoLUFhk2qOX+s/0qNQdeobrUq+c3 LBLutw5jMXEdW+1sbEF276uiSPQC7ud8plJU/Hek0tjw6X2UPIjSSUDK8hIrc/CbafCJ+Sp7g vOcY+YJjnGznCCpO40lvTrnTTgyhslwihBaclpvteLI+g5PEutHJY+FoFM0y9hWMMT0PN9LAF 3hsS1xPounYaCkxq0J09iX04Zqc15cFbD6P3jLUNGRFFBjFiyoTTLtvZ3ExrTt6P93NCQNodV u+ok5sdYLjJ+OSjbVo998x3pbu5Vyu6XoH8s6FEq8g6ElT4CNOxuMGtuFBifX5KJedwZZy+P5 uYLkYyhyUi4hcLhbuVVSe8k/9lAfYlso3RXnlOZsZ9zfTRJ02AmXKW3IndpWuo0jnstUekF4o WTMgq9MGiBQsPH6kQMvp+IX5rnoMS+8miA1nXKZuVm0T/5+s7AGSa9xVyIi96EMx4joGRFTne 0uDBFR/p1IHn0xfe/DrRsMO3wGxMh8Awso763AjgmoPFNmV2WZhcPCjw+giSvfrg3rBww/vnZ 6CmHs7DzxHbbpyvDdC+lrKuUqXJA9y9E+b6rbnp/K2o9/chdATeVIccqAhcxOG/ACtTiP5w8F 9K/Cslp2nSlR6qRcz7oKLK7cEmCXmYZQXvhXJQubPV+e/QwohyCuKgA5EjexKEmurYqa3uUqw J5ipHMhLDoSwrR2d29pEvfbkTbxClDxIWGRLdtGWMxKIlVEMuhFsDi97DHi1Z/3/FBzl/HhIt 8ucr4FEe8UWT7eDH9SihH6VFUZygwF1fZtIaOiuz/o/AcdOOU869g8wiZkO18kdE4X9kY9K/1 W8iVW/5jwKsYrRsq1wTAMnHDkvGyJ655dG4Pb7klahRKWDI1pmj8rlrfaDOPgDTj/UlzP4Hkc fCMBPT60EzitS8n9Y0VkeidN44SCBGt4mqaAElE8QMPWSydwHv8+4Ho1DbZDWlZAmuWrSmsaz CE87GH2BDRB7yHVWWsMasxAms4njoimg7tw+2EGwqXHuFc2/uGYFnif/14bm0MvwP8MnR2JKF FCH7hzrjYHh8qPyNpVkfRAYvGAfSVKzBm6X2Nw4eYscUR/L66JfKKG9HwigE=
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/XF6AUvlN_hxxjM1LrhqsziJ00ck>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 15:26:03 -0000

On 08.10.2019 16:59, Robert Sparks wrote:
> Hi Julian -
>
> Does <https://mailarchive.ietf.org/arch/browse/atompub/> contain what
> you're looking for?
>
> RjS
> ...

Those do not seem to go back to the time when the WG as actually working
on the format and protocol specs (RFC 5023 was published in 2007).

Best regards, Julian


From nobody Wed Oct  9 19:53:31 2019
Return-Path: <worley@alum.mit.edu>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42D361200A1 for <art@ietfa.amsl.com>; Wed,  9 Oct 2019 19:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.683
X-Spam-Level: 
X-Spam-Status: No, score=-1.683 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 MNmxv7-ijFJb for <art@ietfa.amsl.com>; Wed,  9 Oct 2019 19:53:28 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (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 9ABBE120048 for <art@ietf.org>; Wed,  9 Oct 2019 19:53:28 -0700 (PDT)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-07v.sys.comcast.net with ESMTP id IOAcihZLYgoPqIOZzilL7f; Thu, 10 Oct 2019 02:53:27 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1570676007; bh=AeMODRdRG0dN+HCZO/XlG6ELW207fQ+oQwlPRy/UdlA=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=ZhEGSqW6Itatzt3dHSFXYOJvxglRGCZ6lutxsKoTF1YPkbX9og1MSvts7U0u+pSzl nhljl0TGtzb0K+mMdj7gWdhYoz3FX+yC4q/gfalUwrqQvSBua/hXYQropaxM1thEZw 5slLyvxf6quuVyGdVbHD6JQTqhjac7LU0RYNxZIysQpa5yNjzuMKs5JCUHC61XXkIV F1lPt/pHhKl6A0gMLcR42MJM1s3YNnobHYptccDbnSBAbnfUu++ZMqiRYohl0vC18X qWzqCS8W1yKH5BzvxMtZtYLaox8iOOos7sw6jYrXxbRJrtiF3B72IT+DGIdc47As8C gP/XIR1NJie0Q==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4600:1e00:222:fbff:fe91:d396]) by resomta-ch2-05v.sys.comcast.net with ESMTPA id IOZxi4jyLhzmhIOZyigdFv; Thu, 10 Oct 2019 02:53:27 +0000
X-Xfinity-VMeta: sc=0;st=legit
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 x9A2rOtV011334; Wed, 9 Oct 2019 22:53:24 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id x9A2rNnh011321; Wed, 9 Oct 2019 22:53:23 -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: S Moonesamy <sm+ietf@elandsys.com>
Cc: edward.vielmetti@gmail.com, julian.reschke@gmx.de, art@ietf.org, ggh@multi.fi
In-Reply-To: <6.2.5.6.2.20191008052000.0c9ae410@elandnews.com> (sm+ietf@elandsys.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Wed, 09 Oct 2019 22:53:23 -0400
Message-ID: <874l0hqpjw.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/B2SmJbhmVjaZd7j0W39RI23uO3Y>
Subject: Re: [art] RSS and RFC?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Oct 2019 02:53:30 -0000

S Moonesamy <sm+ietf@elandsys.com> writes:
> The IPR for the RSS specification is owned by an organization which 
> is unrelated to the IETF.  The persons volunteering to write the 
> Internet-Draft may have to seek the relevant approval.

As a general rule, you don't need permission of the IPR owners to *write
about* something, you need it to *implement* it.

Of course, to be maximally useful, there should be references to
documentation of any IPR claims that we can track down.

Dale


From nobody Tue Oct 15 16:55:15 2019
Return-Path: <adam@nostrum.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A28DF120825; Tue, 15 Oct 2019 16:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.28
X-Spam-Level: 
X-Spam-Status: No, score=-1.28 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.4, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 de8PJA8Cz8RM; Tue, 15 Oct 2019 16:55:06 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 7421C120019; Tue, 15 Oct 2019 16:55:06 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x9FNsw4s074238 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 15 Oct 2019 18:55:03 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1571183705; bh=qccM11TtOO5V+sfxM5S+aQ+EN+gBlDDZ07SuZdy1fpw=; h=To:Cc:Reply-To:From:Subject:Date; b=XjJ1UTDw8CJlX0xnQJ20k71NEl1wxsTILHlJX4zTkNyThJO08JKQcUtPwblCNzJoI 41Tu02lOfTyFy6hHUvgAVkDioBijQrS9+//KBNL5Xi6KWiNLm+cYHi0N7TfKwi8oB7 a8lVD3HNQ9JwiqxM29NZxy4QvaP8JQwTe+UAlWHM=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Applications and Real-Time Area Discussion <art@ietf.org>
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>, "art-ads@ietf.org" <art-ads@ietf.org>
Reply-To: Applications and Real-Time Area Discussion <art@ietf.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <cdeb0612-89bd-ae70-a7c3-a769d07e5f4c@nostrum.com>
Date: Tue, 15 Oct 2019 18:54:52 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/WNSUV38BdouBo9cY8bkqiZeeP4E>
Subject: [art] Last Call for Comments: draft-nottingham-rfc7320bis (BCP 190 update)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2019 23:55:08 -0000

ART community (cc DISPATCH and HTTPBIS, but please respond only to ART):

Based on conversations on the DISPATCH and ART mailing lists this past 
summer [1], and on in-person discussions that took place in Montreal, 
Mark Nottingham has produced a revision of BCP 190 that takes into 
account community input on several points. The changes are all intended 
to be relaxations of previously-enforced restrictions on how URI 
namespaces could be used.

The revised document is at:

https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/

And diffs from the current, in-force version of BCP 190 can be seen here:

https://www.ietf.org/rfcdiff?url1=rfc7320&url2=draft-nottingham-rfc7320bis-02


This message is intended to serve as a final, two-week last call for 
input from the ART community before the document is put forth for formal 
IETF consensus. The final consensus document will be published as a 
replacement of RFC 7320 (formally, it will obsolete it), and will become 
the new BCP 190.

Please provide input on the document on the ART mailing list 
(art@ietf.org) by Wednesday, October 30th. To prevent the conversation 
from becoming fragmented, please do not respond to the HTTPBIS or 
DISPATCH mailing lists on this topic.

Thanks!

/a

____
[1] 
https://mailarchive.ietf.org/arch/search/?q=bcp%20190&f_list=art%2Cdispatch


From nobody Wed Oct 16 05:44:49 2019
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 324FD120926 for <art@ietfa.amsl.com>; Wed, 16 Oct 2019 05:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 wPb-M8TcqIGp for <art@ietfa.amsl.com>; Wed, 16 Oct 2019 05:44:45 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDD111208DC for <art@ietf.org>; Wed, 16 Oct 2019 05:44:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 55D18BE2E for <art@ietf.org>; Wed, 16 Oct 2019 13:44:42 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0pG1Op6i68yl for <art@ietf.org>; Wed, 16 Oct 2019 13:44:40 +0100 (IST)
Received: from [172.16.22.50] (unknown [142.131.68.10]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id CDB59BDCF for <art@ietf.org>; Wed, 16 Oct 2019 13:44:39 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1571229880; bh=gn8jFDe0bO0sv3GdWkT+9ysXHoPCFdz2oy1tHTKavVk=; h=Subject:To:References:From:Date:In-Reply-To:From; b=lvdsi0VB8SDfeIKtTi6+u0YuWcD3L4PFOC7L38sKzSgvrSaUQdW52kAZuANExwX/d axdNWoq6F1D3YN1RvPBsYfQWW7oUrXbgI3LvrFsbfN9I2CZFBJS+G4MOPgi6OOvqAT SYPcZhF1Umm64Sp2A2MIDDInwuO3zfyfG4ZobtII=
To: Applications and Real-Time Area Discussion <art@ietf.org>
References: <cdeb0612-89bd-ae70-a7c3-a769d07e5f4c@nostrum.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=5BB5A6EA5765D2C5863CAE275AB2FAF17B172BEA; url=
Autocrypt: addr=stephen.farrell@cs.tcd.ie; prefer-encrypt=mutual; keydata= mQINBFo9UDIBEADUH4ZPcUnX5WWRWO4kEkHea5Y5eEvZjSwe/YA+G0nrTuOU9nemCP5PMvmh 5Cg8gBTyWyN4Z2+O25p9Tja5zUb+vPMWYvOtokRrp46yhFZOmiS5b6kTq0IqYzsEv5HI58S+ QtaFq978CRa4xH9Gi9u4yzUmT03QNIGDXE37honcAM4MOEtEgvw4fVhVWJuyy3w//0F2tzKr EMjmL5VGuD/Q9+G/7abuXiYNNd9ZFjv4625AUWwy+pAh4EKzS1FE7BOZp9daMu9MUQmDqtZU bUv0Q+DnQAB/4tNncejJPz0p2z3MWCp5iSwHiQvytYgatMp34a50l6CWqa13n6vY8VcPlIqO Vz+7L+WiVfxLbeVqBwV+4uL9to9zLF9IyUvl94lCxpscR2kgRgpM6A5LylRDkR6E0oudFnJg b097ZaNyuY1ETghVB5Uir1GCYChs8NUNumTHXiOkuzk+Gs4DAHx/a78YxBolKHi+esLH8r2k 4LyM2lp5FmBKjG7cGcpBGmWavACYEa7rwAadg4uBx9SHMV5i33vDXQUZcmW0vslQ2Is02NMK 7uB7E7HlVE1IM1zNkVTYYGkKreU8DVQu8qNOtPVE/CdaCJ/pbXoYeHz2B1Nvbl9tlyWxn5Xi HzFPJleXc0ksb9SkJokAfwTSZzTxeQPER8la5lsEEPbU/cDTcwARAQABtDJTdGVwaGVuIEZh cnJlbGwgKDIwMTcpIDxzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllPokCQAQTAQgAKgIbAwUJ CZQmAAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAUCWj6jdwIZAQAKCRBasvrxexcr6o7QD/9m x9DPJetmW794RXmNTrbTJ44zc/tJbcLdRBh0KBn9OW/EaAqjDmgNJeCMyJTKr1ywaps8HGUN hLEVkc14NUpgi4/Zkrbi3DmTp25OHj6wXBS5qVMyVynTMEIjOfeFFyxG+48od+Xn7qg6LT7G rHeNf+z/r0v9+8eZ1Ip63kshQDGhhpmRMKu4Ws9ZvTW2ACXkkTFaSGYJj3yIP4R6IgwBYGMz DXFX6nS4LA1s3pcPNxOgrvCyb60AiJZTLcOk/rRrpZtXB1XQc23ZZmrlTkl2HaThL6w3YKdi Ti1NbuMeOxZqtXcUshII45sANm4HuWNTiRh93Bn5bN6ddjgsaXEZBKUBuUaPBl7gQiQJcAlS 3MmGgVS4ZoX8+VaPGpXdQVFyBMRFlOKOC5XJESt7wY0RE2C8PFm+5eywSO/P1fkl9whkMgml 3OEuIQiP2ehRt/HVLMHkoM9CPQ7t6UwdrXrvX+vBZykav8x9U9M6KTgfsXytxUl6Vx5lPMLi 2/Jrsz6Mzh/IVZa3xjhq1OLFSI/tT2ji4FkJDQbO+yYUDhcuqfakDmtWLMxecZsY6O58A/95 8Qni6Xeq+Nh7zJ7wNcQOMoDGj+24di2TX1cKLzdDMWFaWzlNP5dB5VMwS9Wqj1Z6TzKjGjru q8soqohwb2CK9B3wzFg0Bs1iBI+2RuFnxLkCDQRaPVAyARAA+g3R0HzGr/Dl34Y07XqGqzq5 SU0nXIu9u8Ynsxj7gR5qb3HgUWYEWrHW2jHOByXnvkffucf5yzwrsvw8Q8iI8CFHiTYHPpey 4yPVn6R0w/FOMcY70eTIu/k6EEFDlDbs09DtKcrsT9bmN0XoRxITlXwWTufYqUnmS+YkAuk+ TLCtUin7OdaS2uU6Ata3PLQSeM2ZsUQMmYmHPwB9rmf+q2I005AJ9Q1SPQ2KNg/8xOGxo13S VuaSqYRQdpV93RuCOzg4vuXtR+gP0KQrus/P2ZCEPvU9cXF/2MIhXgOz207lv3iE2zGyNXld /n8spvWk+0bH5Zqd9Wcba/rGcBhmX9NKKDARZqjkv/zVEP1X97w1HsNYeUFNcg2lk9zQKb4v l1jx/Uz8ukzH2QNhU4R39dbF/4AwWuSVkGW6bTxHJqGs6YimbfdQqxTzmqFwz3JP0OtXX5q/ 6D4pHwcmJwEiDNzsBLl6skPSQ0Xyq3pua/qAP8MVm+YxCxJQITqZ8qjDLzoe7s9X6FLLC/DA L9kxl5saVSfDbuI3usH/emdtn0NA9/M7nfgih92zD92sl1yQXHT6BDa8xW1j+RU4P+E0wyd7 zgB2UeYgrp2IIcfG+xX2uFG5MJQ/nYfBoiALb0+dQHNHDtFnNGY3Oe8z1M9c5aDG3/s29QbJ +w7hEKKo9YMAEQEAAYkCJQQYAQgADwUCWj1QMgIbDAUJCZQmAAAKCRBasvrxexcr6qwvD/9b Rek3kfN8Q+jGrKl8qwY8HC5s4mhdDJZI/JP2FImf5J2+d5/e8UJ4fcsT79E0/FqX3Z9wZr6h sofPqLh1/YzDsYkZDHTYSGrlWGP/I5kXwUmFnBZHzM3WGrL3S7ZmCYMdudhykxXXjq7M6Do1 oxM8JofrXGtwBTLv5wfvvygJouVCVe87Ge7mCeY5vey1eUi4zSSF1zPpR6gg64w2g4TXM5qt SwkZVOv1g475LsGlYWRuJV8TA67yp1zJI7HkNqCo8KyHX0DPOh9c+Sd9ZX4aqKfqH9HIpnCL AYEgj7vofeix7gM3kQQmwynqq32bQGQBrKJEYp2vfeO30VsVx4dzuuiC5lyjUccVmw5D72J0 FlGrfEm0kw6D1qwyBg0SAMqamKN6XDdjhNAtXIaoA2UMZK/vZGGUKbqTgDdk0fnzOyb2zvXK CiPFKqIPAqKaDHg0JHdGI3KpQdRNLLzgx083EqEc6IAwWA6jSz+6lZDV6XDgF0lYqAYIkg3+ 6OUXUv6plMlwSHquiOc/MQXHfgUP5//Ra5JuiuyCj954FD+MBKIj8eWROfnzyEnBplVHGSDI ZLzL3pvV14dcsoajdeIH45i8DxnVm64BvEFHtLNlnliMrLOrk4shfmWyUqNlzilXN2BTFVFH 4MrnagFdcFnWYp1JPh96ZKjiqBwMv/H0kw==
Message-ID: <4921de47-86e7-22af-767c-fb2ec0c3cc1f@cs.tcd.ie>
Date: Wed, 16 Oct 2019 13:44:37 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <cdeb0612-89bd-ae70-a7c3-a769d07e5f4c@nostrum.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="vO18sghcuiJzf67MRCW7uWCeLjmkChmrn"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/oJuXggPuAyH05oltTHbzmCNDREQ>
Subject: Re: [art] Last Call for Comments: draft-nottingham-rfc7320bis (BCP 190 update)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2019 12:44:47 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--vO18sghcuiJzf67MRCW7uWCeLjmkChmrn
Content-Type: multipart/mixed; boundary="w88yCxxp1lY47dEf2QinnVHomyeF7ZoBv";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Applications and Real-Time Area Discussion <art@ietf.org>
Message-ID: <4921de47-86e7-22af-767c-fb2ec0c3cc1f@cs.tcd.ie>
Subject: Re: Last Call for Comments: draft-nottingham-rfc7320bis (BCP 190
 update)
References: <cdeb0612-89bd-ae70-a7c3-a769d07e5f4c@nostrum.com>
In-Reply-To: <cdeb0612-89bd-ae70-a7c3-a769d07e5f4c@nostrum.com>

--w88yCxxp1lY47dEf2QinnVHomyeF7ZoBv
Content-Type: multipart/mixed;
 boundary="------------4A6F725C4A5E6CDACE8CA2C4"
Content-Language: en-GB

This is a multi-part message in MIME format.
--------------4A6F725C4A5E6CDACE8CA2C4
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

On 16/10/2019 00:54, Adam Roach wrote:
>=20
> Please provide input on the document on the ART mailing list
> (art@ietf.org) by Wednesday, October 30th. To prevent the conversation
> from becoming fragmented, please do not respond to the HTTPBIS or
> DISPATCH mailing lists on this topic.

I only had time for a quick scan but that looks like a good
improvement, thanks.

One suggestion, if the Mark (or someone else) had the time
and inclination: it could be good to include a short paragraph
describing an example of when it was ok to diverge from the
general guidance and (briefly) why. Maybe trans would provide
that example. I don't think adding that is necessary, but
it'd help I think.

Cheers,
S.

--------------4A6F725C4A5E6CDACE8CA2C4
Content-Type: application/pgp-keys;
 name="0x5AB2FAF17B172BEA.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="0x5AB2FAF17B172BEA.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQINBFo9UDIBEADUH4ZPcUnX5WWRWO4kEkHea5Y5eEvZjSwe/YA+G0nrTuOU9nem
CP5PMvmh5Cg8gBTyWyN4Z2+O25p9Tja5zUb+vPMWYvOtokRrp46yhFZOmiS5b6kT
q0IqYzsEv5HI58S+QtaFq978CRa4xH9Gi9u4yzUmT03QNIGDXE37honcAM4MOEtE
gvw4fVhVWJuyy3w//0F2tzKrEMjmL5VGuD/Q9+G/7abuXiYNNd9ZFjv4625AUWwy
+pAh4EKzS1FE7BOZp9daMu9MUQmDqtZUbUv0Q+DnQAB/4tNncejJPz0p2z3MWCp5
iSwHiQvytYgatMp34a50l6CWqa13n6vY8VcPlIqOVz+7L+WiVfxLbeVqBwV+4uL9
to9zLF9IyUvl94lCxpscR2kgRgpM6A5LylRDkR6E0oudFnJgb097ZaNyuY1ETghV
B5Uir1GCYChs8NUNumTHXiOkuzk+Gs4DAHx/a78YxBolKHi+esLH8r2k4LyM2lp5
FmBKjG7cGcpBGmWavACYEa7rwAadg4uBx9SHMV5i33vDXQUZcmW0vslQ2Is02NMK
7uB7E7HlVE1IM1zNkVTYYGkKreU8DVQu8qNOtPVE/CdaCJ/pbXoYeHz2B1Nvbl9t
lyWxn5XiHzFPJleXc0ksb9SkJokAfwTSZzTxeQPER8la5lsEEPbU/cDTcwARAQAB
tCFTdGVwaGVuIEZhcnJlbGwgPHN0ZXBoZW5AamVsbC5pZT6JAj0EEwEIACcFAlo9
UYwCGwMFCQmUJgAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQWrL68XsXK+qG
CxAApYHWYgGOIL3G6/OpkejdAkQoCVQAK8LJUSf6vzwost4iVfxIKcKW/3RqKNKk
rRl8beJ7j1CWXAz9+VXAOsE9+zNxXIDgGA7HlvJnhffl+qwibVgiHgUcJFhCSbBr
sjC+1uULaTU8zYEyET//GOGPLF+X+degkE/sesh4zcEAjF7fGPnlncdCCH3tvPZZ
sdTcjwOCRVonKsDgQzBTCMz/RPBfEFX44HZx4g1UQAcCA4xlucY8QkJEyCrSNGpG
nvGK8DcGSmnstl1/a9fnlhpdFxieX3oY2phJ1WKkYTn6Advrek3UP71CKxpgtPmk
d3iUUz/VZa0Cv6YxQXskspRDVEvdCMYSQBtJPQ4y2+5UxVR9GIQXenwYp9AP2niv
Voh+ITsDWWeWnnvYMq07rSDjq0nGdj41MJkNX+Yb2PXVyXItcj5ybE3T2+y3pSBG
FEZYJGuaL4NwtBJFMOdOtBmUOPbetS2971EL3Izxb7ibOZWDwexv+8R6SWYfP1wV
N3p46RyBQuXqJV8ccE11m6vtZTGSYgnLUUFZMRQYH+0hwuYe0T3AA18xDdSYsa8v
ovCCd3l5S4UNzIM2PMChqGrEzKapUpZg7+8ACcxRU3b9Ihd7WYjJ+pQPCoWYKozv
tEvenbNpE/govO/ED3B14e+R2yevRPjRrsN7PJzSf15fQLuJARwEEAEIAAYFAlo9
UqAACgkQLzyHNoBfjaLrSwf+MIHbFRQ4O5cmLYR5sIByWelN3SuRN/gW8rpKo9Ok
Cz6An8uV/iCXy5tNMLzzi0BFl8f22DwBcC5qy9qnlIAdogWam1qWoTAoAD8veEqm
uKhYrqJsCcAyNrKYmK0hP3rpHxx1LySDmKYXmw/8qtBXKHTouMm+5tSsznhykRMT
AAr2p7PSaHgo+hIVaW/rKSspHjDhhZS+G9mtOZad1IH29M6G1Q1NCO0Ywe8krKLQ
IAQlFxtgvOqpPOZNzeKBa/+KbE8TGgMWrkOhC8OeEM5PVzdDhlhD9kPzB/pCKDF5
DofJ/ZRqnDpbKPQ0bsW38AOig3kOc0A27awiBEw3urqR1YkCMwQQAQgAHRYhBH4X
CgRchM9GDit5oBDvedn9g1MSBQJbtyScAAoJEBDvedn9g1MSI/oP/0A9J9nrnBMq
Zpm857lfYWw+rshLK+tyeP4OQeOqnDFvs9jePpcyJLG3DF2r6VbVKPQq+AE6Uf5h
cJBDEN6BjEhRPSbLcqG3A1cz/nNwm8rPmNp+oKhmaBBQGxwciMLmzgynsDydnjPp
MyEs04zvsbsl4vrp2095o105l8KcrrxQrioFjbwveGwHQK9bxJKhx9D+gIk+MouB
ur45UDKTZkMZrr9FGrtkyXCGAxvKdcNC5Oa8z9sj1rcUJfG/OpVAMWhArdlZbFUQ
yoX6pU2Zb1CR2qpWAVerGSfBhmfCyStjARqaKxlftjO+Bj3Jj73Cr5eqej3qB5+V
4BCsPjr4RLvVbYUCPsRdxWc+nBLlfVYkRURu21g1hFm5KFPjgUkyo1s4vjUOY8Dy
I+xLGF7f/IhUBG6l+Vswhpwu7ydalZkeFiPx5xna5NfbEYxvsIf71DvipGvIOaHv
X4egWoFgm8n/9c3rcMxJtpwHPSsUt5dgLsyu6VE0IbvOAc3dN7CWJ355DVFJq9Zg
2YVf0izSpyyzJeGsgkfjW6xpmdvZxuT2UcN4BTcm6vYqueASGrb3lfhzC5gpeVsc
/MoSjTS65vNWbpzONZWMZuLEFraxWJzC0JrDK3NCd0VN3kstqGkVbUIiYOnUm8Vu
4zoVMLlGWzHLIGoPRG2nRezn1YyNfyb5iQGcBBABCgAGBQJbxcflAAoJEGo7ETk8
pK1gE7QL/ApC5P68W5DrI1787WJVZv1u4t/g39vTr7Xer3UMTVQg10vpa7pmqOGh
jIDzDMg3Pe3K3M7fVzfAlUA1qw6ne4RCueVoRKpubeF4AlYbMr0K6hNCPjt5uAxm
bBVuejKTc6pru5rv5gKL0nDbr+Snft5xt7juBLSSimw0/41sZnkjCxo9rF/RA/v6
+uWyK171RKmsEYu8fFtw1eqUNt/Xj792TUixE3pxXheNtQtZGk/9P3W83ChhG4Fh
5EQsn0pIh9wZIAbMRLpgRKyW87fWHZC8/YH8h7afarvn9Thl5pFUldCe22mNJj6K
LChn2aEHQd+PdY1GBpZEcmNEUPuovwzatM0h64hCzTm41eDqRfihZVBT7TbfXQnv
8rywa42Mk756RGzzEZcQEhwQXZcMQUfxIQQ2VyJo0zG36VdZTQF7TF/4Lz7/3cJ5
6jOIm+dwPXtu+C2wAQuD4USOLt4JWPYpqzDfHYJIND/497P9Z9SuQeahr2ez3DRB
g3qsHEjBV7QyU3RlcGhlbiBGYXJyZWxsICgyMDE3KSA8c3RlcGhlbi5mYXJyZWxs
QGNzLnRjZC5pZT6JAkAEEwEIACoCGwMFCQmUJgAFCwkIBwIGFQgJCgsCBBYCAwEC
HgECF4AFAlo+o3cCGQEACgkQWrL68XsXK+qO0A//ZsfQzyXrZlu/eEV5jU620yeO
M3P7SW3C3UQYdCgZ/TlvxGgKow5oDSXgjMiUyq9csGqbPBxlDYSxFZHNeDVKYIuP
2ZK24tw5k6duTh4+sFwUualTMlcp0zBCIzn3hRcsRvuPKHfl5+6oOi0+xqx3jX/s
/69L/fvHmdSKet5LIUAxoYaZkTCruFrPWb01tgAl5JExWkhmCY98iD+EeiIMAWBj
Mw1xV+p0uCwNbN6XDzcToK7wsm+tAIiWUy3DpP60a6WbVwdV0HNt2WZq5U5Jdh2k
4S+sN2CnYk4tTW7jHjsWarV3FLISCOObADZuB7ljU4kYfdwZ+WzenXY4LGlxGQSl
AblGjwZe4EIkCXAJUtzJhoFUuGaF/PlWjxqV3UFRcgTERZTijguVyREre8GNERNg
vDxZvuXssEjvz9X5JfcIZDIJpdzhLiEIj9noUbfx1SzB5KDPQj0O7elMHa1671/r
wWcpGr/MfVPTOik4H7F8rcVJelceZTzC4tvya7M+jM4fyFWWt8Y4atTixUiP7U9o
4uBZCQ0GzvsmFA4XLqn2pA5rVizMXnGbGOjufAP/efEJ4ul3qvjYe8ye8DXEDjKA
xo/tuHYtk19XCi83QzFhWls5TT+XQeVTMEvVqo9Wek8yoxo67qvLKKqIcG9givQd
8MxYNAbNYgSPtkbhZ8SJARwEEAEIAAYFAlo9UqAACgkQLzyHNoBfjaLzHAgAlWT6
NXEGtw/r1miKNGcopzvzILQ9oB8rKI9U9EL6tOf/y2V5oYee/GyQDb3ZdoPxxYYc
Jf+RyiH1nMoqUIZiZJaf3bJXinDZ5+AdfE++UR2NBvqaNyC6u3r24jo1B/sagKbY
tWgsYtRqHLD4IWi37MZrVyjBuF7u14Q07+uhjq6mX2O/tHpCYw/Q82tbeTRPyUf1
WQOAfD1kfBpW9PvAva5Iw9FWeXpCXRzwxnCZhYfGfqtuSw6CPBYLdbikqML6FZ7E
DuTBb/8um1wK7Y9bgeIQC+CYjhYB5RXa1tDJRab2Js4luCvSR0w/CgHw26293tlv
e2Q6UTrmHxP5U22DlokCPQQTAQgAJwUCWj1QMgIbAwUJCZQmAAULCQgHAgYVCAkK
CwIEFgIDAQIeAQIXgAAKCRBasvrxexcr6tJpD/4rrILH+meP07vrx8wW5eYuqCiP
GYnh/CXxIF8eLrfbe5d4QRgtq+w6UeQPMyzKRIRiCoBXB2oJLBZHyxBPxZlg33dT
MrEGn8QWKx2iNuz9rZMXyOSWFetuO01d/aUPd5BnbLbIyK5of8xCQlXM6KH8bc+9
gQ7edR9mfLTdvBf2FR522hg8BRBM1imKc3vO8v39+qIHHRjuiwxBBCAOhHtHRsZX
ripS0uFA07dM46Oi/E8osjx6fQt/lH5z/PN+2adxYSrLSAXfr1oD3RxYNhuWgyGF
L64/VCQb1YGjf0Z5MBPnWm9jgUoOY5K9eNSS0L83WeJjlF5+Q/WOgB+rb49Prm2D
Feo9+S9f2V53Llz1WIspXJg6f+n9lmHE94MfQj1GAHCzI0FeL19lvM+LhD8jJSCb
hrC3+yobyy/AUOs5Z3E+njjX1FF/VCVAs6iOa6i+XG+Y1hh3ir2y1kckJ5auT10M
SU8GEZu9ayU4M3o3N9yxOjaoP0NuQ4MMLL/n/u4u94AeZaHPNBXn/hVfVRRmpRXt
GKvJtFAEppGEYezB+bLKIm6XlpPkhnwYzleLZ7AMEco2C6QM8QPB3g3JpS3sqRhA
5rEP4lL16BmijmF+CHoPE/zwgKZbKpyVDqvIW5IDgvfIC2X4pbZDRvGIUKaGSB4+
ksZgUUnNyvfQr2p7jokCMwQQAQgAHRYhBH4XCgRchM9GDit5oBDvedn9g1MSBQJb
tySbAAoJEBDvedn9g1MSeKkQAJm44jt1kwHgQgeDBKdjdvl0AjE0xVEQxriZ6lP/
l//34YT0auFfzsYIrChSpQXAEtobBAr4Ohw1Us+BZe+H5P8vm6LRuPwozC3SjwfX
4Iec8+9ot6tIVg4sbedDSgb/CCFVjsmIGcQ1P73JLJTBJ6mxYCV/gn3QC6bwDOFo
7kD9FDHCjRN8XfhHQ4Q9cYyt06uF31qG/aumgWYC9geCGgAwiHgwxNYb9GoJ0iZj
CROwbYvLTcQgsVUW2bTmsVR13UVKDsdl02sRV7qcVYW6R0a3Ra8KudX+nt25H5DR
Gd382KZ5W8pydsy/viTvD9z6v0ulChBYxAedIvGIClrhbxlLEPmIg4ImVOLGqsUg
Vm32J95WOjEkk4PEZ12xSDBtwhSJqmJNboWlfmw43KdIbY8zNhffIO3N6O7FsdGx
mqyHeLoTpqY+ySVUPpbuyW8ujnI/J//+6hdTZ9dQsEJQlWngKuWOQ5ma58MPSN88
zllsqhZAFQjNxqnkSzL6ZQ+v/jvuRRe16B80AeO55DsmbWsMv/YLLD1mSi7+Khy2
EtMBhgojWwrGMvdLN6X3mnzNJEscYyLxM9tSk+iySP2sLthK0BVgpAzBSdaf/ezI
z60P+neHDzteNFf8Mn7lmgYk1amvZoJ29s5+n2HwxyRL5dVMyMdyQmntubbctfqr
Z0tIiQGcBBABCgAGBQJbxcflAAoJEGo7ETk8pK1gnCYMAJY4FeIYjlIXGghFWzsB
4fYwK1+iaFpU3fSto5qcrqVtVPjXpwqczqBWeXGyQxiB0kan4OVAXydIeaP8EAuF
CA7paP3s9STLJBO3KurkwyRkPW5zo0X7xVqaVToRsX2Ul98KVJoHYQD1KdezEtwl
vpNwiiBr42AYR751Vm6JBVAbQXuFpB3c8bUV0OkkRxNFtL8/2PieHar58n5dntGk
bPlPkztahsFqktgacIgXHX5vaT+7YeeZ1DWLOYjGO0wNhkOSeroCmxwJUikU7joB
p823L7r5KfpqWTPpSCzVstQKZUGmmoE1qCswY/Ud5wvp9SccpIILkRXj0rZRtfnE
5MpL3hjmtNzfDd9qIsJtBJlSB2hZwAsVm1l+EWN9hG3tqyA43niUMy2n6q690of3
berSiQ+kvY/aC9Hx8I+bKzOV9/J2VUTqfaPZa4Uy2rVX5Q2p69n/PMj7mEer0rCL
3j9V16J9c+s0BSkXoKdtYdB0TWVhBgUybd9qtYcwHWvhP7QuU3RlcGhlbiBGYXJy
ZWxsIDxzdGVwaGVuQHRvbGVyYW50bmV0d29ya3MuY29tPokCPQQTAQgAJwUCWj1R
WgIbAwUJCZQmAAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBasvrxexcr6jsc
EADEcB0WQEZn2AkrzDs1RhL0Lp6cZi0BigofkbcGfdhJyMSs19C0dhvncrAFClVI
6/Udw3yFtDyYtOCf2W3M3A1K6/RfEizCLzTsdFIhni9gOJLlUpXViQtgrlstjk7h
qVV3Ooz4BlCqS4cG7rfqf4LQQPpTAuFUEV9I28FBUB2irqC+v4gTysIgpMw0bA1y
BU9sX5jE/tRkzqnuzZrkwiobDtRFJ9qp+7O2JtcY4EsVtLAsaodJKc5cF8R4OvB1
n66vxxcgg9Eh4JNWZ47xsaCmAGo1Bcb2jIY35OtgAL7gCGLRSMKTtAaPy1/fEgIq
hCljJ9x40Fkn/3r2BX21WC9HFSPFTBz2RluLRzxdgxOrkYK8EiHUPoE5b1AEzZKw
2AbeXfr57f5zYsN3IqfbQLUjMYtUN1wK3Pjb+idD972wyXMWt8uOzlI7b9Ocu+nY
m2whBfJv9Pmp3QYTmPz+LB9lH65VNVUSxSXVr5iWXO3qx1HtEiGEqkporMQCTh3T
5Ud3PvMSRBFFKNs9WhJ/Lxz+SV30WLwG6dr5mQqlzAhb4Phc/zekZyXRdS/oDKrB
LUucS36O//49JeyRi1QvOfxnfmIqRIAf/k3PoYJmTo5E82//r5Qj3YGlRu78ba0H
Arxs+ACD6AnEHHcbswpbtVEKYzlSu0Ar0Dc7vRWM/IyQdIkBHAQQAQgABgUCWj1S
oAAKCRAvPIc2gF+NosIsB/9f/29FNla3BJfGIEIDnhrqGD0i9bSa89SqBd++uG06
TQgW5wsqtNcrwn81yZTq6XE6i9VtD4GKfqC0d4KZJr9bnbeD81cI64VOdL8zJWJs
0vj5EIXCobKyX74Kb4uePUyZqwT2Q74I116u/HwA9/FXsPo5isbh4ZqD4t0VHpWk
mfq1FPT9a/JPyX46qKqB2Fce/7Qy+SQP1NfkuUlbhUH/JG9aSSYvk3lznNiH41x9
M+FDlL106itXOubrl3oi2fT3fsSedq7uzt+IV0DQEeNaoQAUuwEhdB8IWOMqN2wo
DjGVKJftfsSWY9ilZrnDBNDrp0vRqcx33LUMkIw4d7iBiQIzBBABCAAdFiEEfhcK
BFyEz0YOK3mgEO952f2DUxIFAlu3JJwACgkQEO952f2DUxJjuw/6ApHSsVTWD4a0
H6FJ23A9Ftpy+aXZ4vYlzkSrfsn2ECrEfK3lXQh/uzwjJUDYZeB1/BQsFZtcYNQO
JSSHbQ49BFRLwb1J/wBZG4bbmrkLxnNbKDKQvzxEpclkMW0Dj0J6o7kGrmzIGGrh
B+JJN99AcineHRug8ZSFIERRCmigxdhAKU0BFD7P+5HNHltSL3DF1c2fFOf2JrgB
KVoE+9RhMZjWNbYetFFLCkjXb5Rpay9zeMm1DxfSTGAnuOwUXW6qq4hnl5+VC/48
ceDZElLLfu7RQUZv44pkSTOWZs+iQoJiHMFHk9wPqyB2Vok1yJ2a2j27WhXrJlPw
nZbgJO5RyWDG3p/eVmpl5Uuc2dsfIpR17KnAuWpghK6V+cyFncDoGCl/YG2Mvool
sW08FiZh3Ej4dnJjj25TZkeFG74JJDXLvMYpJfSBGnmETv4Dhcm2xPqVMuFuL1qJ
lMbVLrMo2GXeo03OzNyvbs+u8WLIaGm5hC7N1CXY8wZs4jo6OJ/expvnc07dEuws
4zT3AiWv3nIouWReRStZy9QkavDocqbyPmilcdPCYk4BsOlzpwwO74hNG7iyl0Kd
AlwTxGQ7y0rJou6HYa1TmRhIEr3vKvlW+JfUUrqtjXgsuacTXo4+Ira2JUErL2cY
zQMq1j4r1ZyhFnuz93s7Rsx/Nw0+0YuJAZwEEAEKAAYFAlvFx+UACgkQajsROTyk
rWCJqwv+NLVPE4sD4sDA2/6Ek7UsRIUkg+S39fhqWsLc4rtw/mDunv8Un61I3K04
fZ2Ry4nF9hZM0a710UvXFbStvrzRJO3EAAcdJR9LTCd19e8UeruQbIee3YT91U4N
kC9JMpecfq62/teOAU2e5P3fWYaLs5ZX7zCLwWuBcW2l3SyoljQczM85HhJ3XHm+
FnwQ6D9xRle+lvWTcuC9d1yAyUb8IOospcL2lJTmy8e3r79R24hPlSB4LDe0wEN8
AXbagrcAQZjwyaHyWxjJbTwZ0b43WGdfIqZ1ElOeoffbketPGRmWvx5xUvb2ALFB
BdETzV270gs5XDJgJ1SIIKOyDADxwvroTe2jD8C/841eEql5QSow3s/U3zRqk3mt
tto8Qw/DN71aeh6dmYSsvd2UjsHw/vofOPRBGxZLEkKTEvMnhmMW9hiKPkPia+Qg
evYE020qpKSxLEdWA8nprHwxmGiDNesCfXSC6vm1qfyj5g8HzxSckq9ZaMhKMCo7
vxflUEDuuQINBFo9UDIBEAD6DdHQfMav8OXfhjTteoarOrlJTSdci727xiezGPuB
HmpvceBRZgRasdbaMc4HJee+R9+5x/nLPCuy/DxDyIjwIUeJNgc+l7LjI9WfpHTD
8U4xxjvR5Mi7+ToQQUOUNuzT0O0pyuxP1uY3RehHEhOVfBZO59ipSeZL5iQC6T5M
sK1SKfs51pLa5ToC1rc8tBJ4zZmxRAyZiYc/AH2uZ/6rYjTTkAn1DVI9DYo2D/zE
4bGjXdJW5pKphFB2lX3dG4I7ODi+5e1H6A/QpCu6z8/ZkIQ+9T1xcX/YwiFeA7Pb
TuW/eITbMbI1eV3+fyym9aT7Rsflmp31Zxtr+sZwGGZf00ooMBFmqOS//NUQ/Vf3
vDUew1h5QU1yDaWT3NApvi+XWPH9TPy6TMfZA2FThHf11sX/gDBa5JWQZbptPEcm
oazpiKZt91CrFPOaoXDPck/Q61dfmr/oPikfByYnASIM3OwEuXqyQ9JDRfKrem5r
+oA/wxWb5jELElAhOpnyqMMvOh7uz1foUssL8MAv2TGXmxpVJ8Nu4je6wf96Z22f
Q0D38zud+CKH3bMP3ayXXJBcdPoENrzFbWP5FTg/4TTDJ3vOAHZR5iCunYghx8b7
Ffa4UbkwlD+dh8GiIAtvT51Ac0cO0Wc0Zjc57zPUz1zloMbf+zb1Bsn7DuEQoqj1
gwARAQABiQIlBBgBCAAPBQJaPVAyAhsMBQkJlCYAAAoJEFqy+vF7FyvqrC8P/1tF
6TeR83xD6MasqXyrBjwcLmziaF0Mlkj8k/YUiZ/knb53n97xQnh9yxPv0TT8Wpfd
n3BmvqGyh8+ouHX9jMOxiRkMdNhIauVYY/8jmRfBSYWcFkfMzdYasvdLtmYJgx25
2HKTFdeOrszoOjWjEzwmh+tca3AFMu/nB++/KAmi5UJV7zsZ7uYJ5jm97LV5SLjN
JIXXM+lHqCDrjDaDhNczmq1LCRlU6/WDjvkuwaVhZG4lXxMDrvKnXMkjseQ2oKjw
rIdfQM86H1z5J31lfhqop+of0cimcIsBgSCPu+h96LHuAzeRBCbDKeqrfZtAZAGs
okRina9947fRWxXHh3O66ILmXKNRxxWbDkPvYnQWUat8SbSTDoPWrDIGDRIAypqY
o3pcN2OE0C1chqgDZQxkr+9kYZQpupOAN2TR+fM7JvbO9coKI8Uqog8CopoMeDQk
d0YjcqlB1E0svODHTzcSoRzogDBYDqNLP7qVkNXpcOAXSVioBgiSDf7o5RdS/qmU
yXBIeq6I5z8xBcd+BQ/n/9Frkm6K7IKP3ngUP4wEoiPx5ZE5+fPIScGmVUcZIMhk
vMvem9XXh1yyhqN14gfjmLwPGdWbrgG8QUe0s2WeWIyss6uTiyF+ZbJSo2XOKVc3
YFMVUUfgyudqAV1wWdZinUk+H3pkqOKoHAy/8fST
=3DYzQY
-----END PGP PUBLIC KEY BLOCK-----

--------------4A6F725C4A5E6CDACE8CA2C4--

--w88yCxxp1lY47dEf2QinnVHomyeF7ZoBv--

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

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

iQIzBAEBCgAdFiEEW7Wm6ldl0sWGPK4nWrL68XsXK+oFAl2nELUACgkQWrL68XsX
K+oZlQ//UnEjVxKjFz5b+A7ZwXp9fN07E5YovJgg+2g+XuN07aDtuvrvbWok1vaF
6Iw6sxltpFmrPpZv7ds7AEtMbRi8gYW86HbzXl5SNicxwum/iymQY4qptK0JLUEs
B6TnB6SIW2fl6Xa1nfLMP0LwkIsslTlJSd5WcV5QVvii+4Eo1A4r30iU7Z1ANNz3
i//EH40ydCQ9kBqxpb2FzO4JJPe5YB+qRSr+mVIiLjlpbwHRYYzoM+5zLJtLZ2an
VOWlvhTrVObGXmPYRr2PN5ln8nVnPsiuQ5VijNB8UT3XqNhK/7Le+Azg5FZEXK99
nMvvQig/O0RLixqRw+k3+x0qUr63AgUHJMkJODE7MQdhIG375y3W1rqTsU2qVM87
NfE+f2kTozvJl3GEL4bwHwkhI1Kzda64zpEF0cxooFZDc+0zqCKqiv9/ageYrAfJ
iyoP7i+HdS6VrdLZei4OMlN3cYxq3pes8VZwPc5utAt3vXgYZMlwN2dMlbCLqscR
+JNzOUnjxpML1LSZaf0mqJqsige3YAlIPOJ2D7yXNqDUMuj9+t3PSWQ8prGesdal
+xOQdA1b69VtmSNQ20r9Eoj4deztCQQyQvXmf9kfvvCKzOY0uylq5w19+hxmbhxD
UhTwCOiKaZ3egC3YvdPkRm2Jp5+jxF0TZ8qkRJtRt9sWmq2++fg=
=pCwV
-----END PGP SIGNATURE-----

--vO18sghcuiJzf67MRCW7uWCeLjmkChmrn--


From nobody Wed Oct 16 12:10:56 2019
Return-Path: <masinter@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89C90120957 for <art@ietfa.amsl.com>; Wed, 16 Oct 2019 12:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.476
X-Spam-Level: 
X-Spam-Status: No, score=-1.476 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.172, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 pTRgGDKzZ5hj for <art@ietfa.amsl.com>; Wed, 16 Oct 2019 12:10:52 -0700 (PDT)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (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 CFCAF120241 for <art@ietf.org>; Wed, 16 Oct 2019 12:10:46 -0700 (PDT)
Received: by mail-pl1-x631.google.com with SMTP id k7so11726986pll.1 for <art@ietf.org>; Wed, 16 Oct 2019 12:10:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:from:to:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=Zpaeo/LanLmg+T7xKZQOZVqj+DzS4QnNOU0j04yvaJo=; b=Hbhli7Ho1crE+21VpJnInxm3PjiHT6zjRDjf49z+ez99l6LzCTtzUjYuFvPNk3Ee3n SE9JhkubHWOfmvOG8ngb8ZXPmSCr0tAwa/qZRtWBT6rL31DVX2Nb3Do3wDLB1mYNploz UZMFumeLzfMLkxmDG8CCw7sZvSAjHzyQanaQYa5vbt2XkUw3lQysjdFW4I3Z/B4nmxLx iQdekdlUNk3r8GuqRGF6uCFZGrhkrbsKts4lTZB5dap3u42mV1xehoqtXX21+xu7jTy3 CTNapQndGnVxmAah9f3qwyUHSgYcf00xuZz/qZl/7xOLSHLL0g4syYwiRhz1dVpvQ+Zq S0SQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=Zpaeo/LanLmg+T7xKZQOZVqj+DzS4QnNOU0j04yvaJo=; b=OUKCKKGuRqUeBY3RnjioCYOR7pm7M2GzFAfHF47zs0hh+kHlyRaSw+GtodzS03FywQ wfKxrLx+DJ7ZACdIl3HHd3IJEGfOR4XlW2q5p6AH4GL3Lq+8caJmQgpfNoWtXbdFLabr dtTDjxorIjQg+KMYckxpW2raQDOzfSaViQuB5ffHszit/PQmw6ctjWHlPeWKV0/qFho9 z7nGyclNzDIPF9BVrZXMdwHJS1iclGUwkTeGfs/wClyHX0GqkcYTpYF6dtJOFqwHkghy BdBYZHqmBLEtXimaDxAjy6ln5js9ujs5YRAbZqHvZBzECZpxcSV3P6KqUWCHwaSgRap7 nT2Q==
X-Gm-Message-State: APjAAAX5yFnVsm8iqPNQdv/uwFur3scS8j8zpM81AE29uDwKkouYL17q KBLeeu/LInT3T1sF/evDZ8s9VtCU
X-Google-Smtp-Source: APXvYqzOIXRSuEHXaNokAHGxR4CG+n4Bn/aqUAWd+QRvqsU3AYNi6AQBCFpKn7AV7evgeUrNdIV43A==
X-Received: by 2002:a17:902:122:: with SMTP id 31mr40775922plb.274.1571253045379;  Wed, 16 Oct 2019 12:10:45 -0700 (PDT)
Received: from TVPC (c-67-169-101-78.hsd1.ca.comcast.net. [67.169.101.78]) by smtp.gmail.com with ESMTPSA id o60sm3557590pje.21.2019.10.16.12.10.44 for <art@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Oct 2019 12:10:44 -0700 (PDT)
Sender: Larry Masinter <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: "'Applications and Real-Time Area Discussion'" <art@ietf.org>
References: <cdeb0612-89bd-ae70-a7c3-a769d07e5f4c@nostrum.com> <4921de47-86e7-22af-767c-fb2ec0c3cc1f@cs.tcd.ie>
In-Reply-To: <4921de47-86e7-22af-767c-fb2ec0c3cc1f@cs.tcd.ie>
Date: Wed, 16 Oct 2019 12:10:44 -0700
Message-ID: <015301d58455$6931dde0$3b9599a0$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQDvf4+JJ/bJOFv8I8G83RI7mYy0aAIUjYeQqRj+MtA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/b7jOBzEF63JVrraS77zSFfCOasE>
Subject: Re: [art] Last Call for Comments: draft-nottingham-rfc7320bis (BCP 190 update)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2019 19:10:55 -0000

On 8/21/2019 at 7:50 AM I wrote

An update to BCP 190 should take into account the fact that there is not =
a consensus for the "best" of various "current practice" for avoiding =
the URL squatting identified (namely using a hypermedia format to let =
the server control the URL format completely rather than the API control =
the URL syntax and making the client do string processing.

But didn't see a reply. =20

If you want links, link to draft-hartke-t2trg-coral and =
draft-kelly-json-hal as two examples of current practice for which the =
"best" way hasn't shaken out.

Larry
--
https://LarryMasinter.net



-----Original Message-----
From: Larry Masinter <masinter@gmail.com> On Behalf Of Larry Masinter
Sent: Wednesday, August 21, 2019 7:50 AM
To: 'Adam Roach' <adam@nostrum.com>; 'John C Klensin' =
<john-ietf@jck.com>; 'Mark Nottingham' <mnot@mnot.net>
Cc: 'Jacob Hoffman-Andrews' <jsha@letsencrypt.org>; 'Devon O'Brien' =
<devon.obrien@gmail.com>; 'ART Area' <art@ietf.org>
Subject: RE: [art] Call for Consensus: Re: On BCP 190

Just back from an August vacation, apologies for brevity IMHO An update =
to BCP 190 should take into account the fact that there is not a =
consensus for the "best" of various "current practice" for avoiding the =
URL squatting identified (namely using a hypermedia format to let the =
server control the URL format completely rather than the API control the =
URL syntax and making the client do string processing.


As far as process goes, I think it's ok to drop the DISCUSS in
 question because it is Experimental and not Standards track.


As  Carsten Bormann <cabo@tzi.org> wrote  Sunday, July 28, 2019 1:43 AM
Re: [art] On BCP 190

>=20
> On Jul 28, 2019, at 08:26, Larry Masinter <LMM@acm.org> wrote:
> >
> > Now, why JSON-HAL is still an expired  Internet Draft is a puzzle.
>=20
> (Slightly, but not completely off-topic:)
>=20
> Probably because there are multiple ways to skin this cat and we never =

> tried to converge on one.
>=20
> As a data point, for the applications in the CoRE working group, we=20
> have mostly been able to avoid BCP190-style arguments by using=20
> /.well-known, mainly because simple devices only tend to have one=20
> service offered directly under / and because IoT device platforms tend =

> to provide the application developer full control over the URI space.  =

> /.well-known/core provides a discovery mechanism for the entry point =
URIs
actually offered by a server.
>=20
> For where this is not enough, the WG has just last week adopted CoRAL=20
> (not yet resubmitted as draft-ietf, so you can find it at=20
> draft-hartke-t2trg-coral) as our idea of a hypermedia format like HAL. =
=20
> Up to now, we tried to make everything work with RFC 6690 link format, =

> but that has too many idiosyncrasies that started to get in the way of =
a
long-term way forward.





From nobody Wed Oct 16 15:12:47 2019
Return-Path: <noreply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D9A6D120086; Wed, 16 Oct 2019 15:12:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller via Datatracker <noreply@ietf.org>
To: <art@ietf.org>
Cc: draft-ietf-httpbis-http2-tls13.all@ietf.org, ietf@ietf.org, ietf-http-wg@w3.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.105.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Matthew Miller <linuxwolf+ietf@outer-planes.net>
Message-ID: <157126396580.7872.17320060403551594228@ietfa.amsl.com>
Date: Wed, 16 Oct 2019 15:12:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/d7t_0jRyP1srvqmhEJygTrAABEQ>
Subject: [art] Artart last call review of draft-ietf-httpbis-http2-tls13-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2019 22:12:46 -0000

Reviewer: Matthew Miller
Review result: Ready

This document updates HTTP/2 (RFC 7540) to prohibit TLSv1.3 post-handshake
auth, matching the existing prohibition to TLSv1.2 renegotiation.

This document is ready for publication.  It clearly describes the problem and
what clients and servers need to do.


From nobody Wed Oct 16 16:33:51 2019
Return-Path: <adam@nostrum.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA961200F7 for <art@ietfa.amsl.com>; Wed, 16 Oct 2019 16:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level: 
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 3R8Te3U0QMIH for <art@ietfa.amsl.com>; Wed, 16 Oct 2019 16:33:48 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 60346120086 for <art@ietf.org>; Wed, 16 Oct 2019 16:33:48 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x9GNXYTm010281 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 16 Oct 2019 18:33:36 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1571268816; bh=+s8vEB/xvdROoyTIcxa5Yh9xFMX+PeD4LbenPQOULPE=; h=Subject:To:References:From:Date:In-Reply-To; b=A3jcZ6qdHQecZWWiHfvSioBH5eBDbeyn/rMswD/uN7DAwBGduVHpUL0ixHat0Y4n0 +Vyd6+3eN3ZdIGq8AigR22SKGVVItVBrULivgqS7b25kReJgb7hLtUdRHMSdvwW5nG llu+DWzb8U1iuNv8PGuT02nXHgkRr5rkaf68jhHQ=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Larry Masinter <LMM@acm.org>, "'Applications and Real-Time Area Discussion'" <art@ietf.org>
References: <cdeb0612-89bd-ae70-a7c3-a769d07e5f4c@nostrum.com> <4921de47-86e7-22af-767c-fb2ec0c3cc1f@cs.tcd.ie> <015301d58455$6931dde0$3b9599a0$@acm.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <422af97e-cf53-9e3c-84ab-0d2dd907bdfe@nostrum.com>
Date: Wed, 16 Oct 2019 18:33:28 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <015301d58455$6931dde0$3b9599a0$@acm.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/-6NWMWLaHVugUYkkNz5ubD_v7Ws>
Subject: Re: [art] Last Call for Comments: draft-nottingham-rfc7320bis (BCP 190 update)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2019 23:33:49 -0000

Thanks for bringing that up again, Larry! I recall seeing that message 
and having a hard time parsing out the point you were making or deducing 
what resultant changes you'd like to see to BCP 190. I meant to return 
to it later to puzzle out your exact meaning, but it got away from me. I 
apologize.

Thanks for adding concrete examples; looking to them for clarification...

It appears that draft-kelly-json-hal is using URIs exactly as expected 
(that is, the _thing_ being talked about is exactly the _thing_ the URI 
has been assigned to by the site administrator), albeit with some 
interesting HTTP-specific protocol stuff that uses Content-Type to 
change the response body from information to metainformation. There's 
certainly some HTTP-related discussion to be had here about the wisdom 
of overloading the semantics of Content-Type in this way, but it doesn't 
seem to bear on the naming question. Correct me if I've simply found the 
wrong part of this document.

I dug through draft-ietf-core-coral and couldn't quite find any 
mechanism that seems to align with the words in your statement below. 
But then again, it's a pretty big draft, and you didn't cite any 
particular behavior in particular, so I might have missed the section 
you have in mind. For what its worth, the URI handling that I see in 
that document is based on the provisioning of a (server-controlled) 
starting-point URI into clients, and then using a document at that 
endpoint as a roadmap for all the other URIs used by the application. 
This seems entirely compliant with both BCP 190 as currently written and 
with the proposed BCP 190 currently under discussion. I see nothing to 
"take into account" here, as the draft's approach is already in 
accordance with BCP 190 (and, in fact, it was one of the solutions that 
I encourage TRANS to pursue).

As before, I'm trying not to take a position on any given issue here, so 
I don't intend to argue for or against the point you're making -- I'm 
just looking for clarity on what you're trying to say, ideally in a way 
that is understandable to the community and (assuming the community 
agrees) actionable for the draft author.

I would propose that the easiest way to make progress is to send 
concrete suggestions to this mailing list detailing text that you would 
like to see added/revised/removed from the current draft. If you find it 
easier, you may wish to submit a PR against 
https://github.com/mnot/I-D/blob/gh-pages/rfc7320bis/draft.md and post a 
link to that PR to this mailing list. If not, email with OLD/NEW 
sections would serve the purpose just fine.

Thanks!

/a


On 10/16/19 2:10 PM, Larry Masinter wrote:
> On 8/21/2019 at 7:50 AM I wrote
>
> An update to BCP 190 should take into account the fact that there is not a consensus for the "best" of various "current practice" for avoiding the URL squatting identified (namely using a hypermedia format to let the server control the URL format completely rather than the API control the URL syntax and making the client do string processing.
>
> But didn't see a reply.
>
> If you want links, link to draft-hartke-t2trg-coral and draft-kelly-json-hal as two examples of current practice for which the "best" way hasn't shaken out.
>
> Larry
> --
> https://LarryMasinter.net
>
>
>
> -----Original Message-----
> From: Larry Masinter <masinter@gmail.com> On Behalf Of Larry Masinter
> Sent: Wednesday, August 21, 2019 7:50 AM
> To: 'Adam Roach' <adam@nostrum.com>; 'John C Klensin' <john-ietf@jck.com>; 'Mark Nottingham' <mnot@mnot.net>
> Cc: 'Jacob Hoffman-Andrews' <jsha@letsencrypt.org>; 'Devon O'Brien' <devon.obrien@gmail.com>; 'ART Area' <art@ietf.org>
> Subject: RE: [art] Call for Consensus: Re: On BCP 190
>
> Just back from an August vacation, apologies for brevity IMHO An update to BCP 190 should take into account the fact that there is not a consensus for the "best" of various "current practice" for avoiding the URL squatting identified (namely using a hypermedia format to let the server control the URL format completely rather than the API control the URL syntax and making the client do string processing.
>
>
> As far as process goes, I think it's ok to drop the DISCUSS in
>   question because it is Experimental and not Standards track.
>
>
> As  Carsten Bormann <cabo@tzi.org> wrote  Sunday, July 28, 2019 1:43 AM
> Re: [art] On BCP 190
>
>> On Jul 28, 2019, at 08:26, Larry Masinter <LMM@acm.org> wrote:
>>> Now, why JSON-HAL is still an expired  Internet Draft is a puzzle.
>> (Slightly, but not completely off-topic:)
>>
>> Probably because there are multiple ways to skin this cat and we never
>> tried to converge on one.
>>
>> As a data point, for the applications in the CoRE working group, we
>> have mostly been able to avoid BCP190-style arguments by using
>> /.well-known, mainly because simple devices only tend to have one
>> service offered directly under / and because IoT device platforms tend
>> to provide the application developer full control over the URI space.
>> /.well-known/core provides a discovery mechanism for the entry point URIs
> actually offered by a server.
>> For where this is not enough, the WG has just last week adopted CoRAL
>> (not yet resubmitted as draft-ietf, so you can find it at
>> draft-hartke-t2trg-coral) as our idea of a hypermedia format like HAL.
>> Up to now, we tried to make everything work with RFC 6690 link format,
>> but that has too many idiosyncrasies that started to get in the way of a
> long-term way forward.
>
>
>
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art



From nobody Wed Oct 16 17:16:50 2019
Return-Path: <masinter@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30B2C1200F7 for <art@ietfa.amsl.com>; Wed, 16 Oct 2019 17:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.476
X-Spam-Level: 
X-Spam-Status: No, score=-1.476 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.172, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 7OCyM3Lz38sf for <art@ietfa.amsl.com>; Wed, 16 Oct 2019 17:16:46 -0700 (PDT)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (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 596D412003E for <art@ietf.org>; Wed, 16 Oct 2019 17:16:46 -0700 (PDT)
Received: by mail-pf1-x42a.google.com with SMTP id 205so432654pfw.2 for <art@ietf.org>; Wed, 16 Oct 2019 17:16:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:from:to:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=e4EFdK4gPUT/BZ4cBbnFaH6dRrG11N31gOZDz+w4WYE=; b=uTJrvEPlI4pmg2hC+KjKlIifAEjnjDwO+5blpKMqxAYydPJYGma5jqBxzauuMvVYDn s2M6CfOj/6pyhaFZ2MUZ4bPDDCl3HhXoWNJqGGA7TU1NA5bPN/1Xidjs/Cy1fnsjOKWC ekofGAJSR2fKA9UNJcRu4zSL5f6WlH+i//mxiSRahstnXwdVFEGHxTkuOBiWWsSRaKhS Ir/NqqxkplaAHP4Rg8qkrPhxyw9l138n9y/C9iwgrStSgpToIahAwphTB6hDeEEi1va7 xqgdJWKUJBwi7frmx6WkUaDm5p6VfOYYCqk08NnQGR/7E59j5vkB4KZd/E4PXmldfSBv LAtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=e4EFdK4gPUT/BZ4cBbnFaH6dRrG11N31gOZDz+w4WYE=; b=oBheI22RA+ibRCRx3F2U0WmCcvO+RYUyzH4aUIFXySOBbSITk97hSyYirl6uKOXX6Q DSeR1N6ppevriwSDwlmzpOLo/FVVqQJMroQk9inKc44/j/Ilg/Flr5Cttd7r3hv+36Gq mJaxEDIr73LJ4CqSZ2zIoDqawGxJ2gyTlfPYKC2LBDbbnBNvCMcr5zxx71jm+62ZSkaX siPoliNejfJO4S3fpV4tgN1lRhqI8OI/sYjiuX543svw4oY4+CWUGIvy66Vdosn4EUSh 15twwQpZ/gMeZoSPiPv8kQH+GwHETLiSc57V+F/KKw2TLDaCv1nu1Gstl/5WAAHOzDNo HL4g==
X-Gm-Message-State: APjAAAV2vD991t4ChM9gCPxZdMJHaAtFYYcOBirtUbkYZvmH8TmR5KZk d19o6iituAImtrTiCV4A5/30dBU8
X-Google-Smtp-Source: APXvYqwy3oI5p1e+wEWCFhERkjrPglLGDWBI8Kntz+gM3+Pd6ERcWbal0ZQrJb2o4p1S1GZ2y/tm4Q==
X-Received: by 2002:a17:90a:f311:: with SMTP id ca17mr779292pjb.112.1571271405451;  Wed, 16 Oct 2019 17:16:45 -0700 (PDT)
Received: from TVPC (c-67-169-101-78.hsd1.ca.comcast.net. [67.169.101.78]) by smtp.gmail.com with ESMTPSA id ev20sm289623pjb.19.2019.10.16.17.16.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Oct 2019 17:16:44 -0700 (PDT)
Sender: Larry Masinter <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: "'Adam Roach'" <adam@nostrum.com>, "'Applications and Real-Time Area Discussion'" <art@ietf.org>
References: <cdeb0612-89bd-ae70-a7c3-a769d07e5f4c@nostrum.com> <4921de47-86e7-22af-767c-fb2ec0c3cc1f@cs.tcd.ie> <015301d58455$6931dde0$3b9599a0$@acm.org> <422af97e-cf53-9e3c-84ab-0d2dd907bdfe@nostrum.com>
In-Reply-To: <422af97e-cf53-9e3c-84ab-0d2dd907bdfe@nostrum.com>
Date: Wed, 16 Oct 2019 17:16:43 -0700
Message-ID: <027a01d58480$285495d0$78fdc170$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQDvf4+JJ/bJOFv8I8G83RI7mYy0aAIUjYeQAaTW988BsFjF6aj+qJLQ
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/yuMZTxuld9cf5lvNf14R58cmxzM>
Subject: Re: [art] Last Call for Comments: draft-nottingham-rfc7320bis (BCP 190 update)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2019 00:16:48 -0000

As I understand it, people wanting to do what used to be separate protocols
now define the network interface as a kind of REST API.


https://en.wikipedia.org/wiki/Hypertext_Application_Language


HAL is the name for a style of Interface where the relationship between one
resource and other resources that are related are not defined by asking the
client to do string manipulation on the URLs (like you might by defining a
base and doing relative relations) but rather explicitly returning
"hypermedia objects" that contain explicit URLs of the related resources.

JSON-HAL is just one such building block.  When I mentioned it on the ART
list, Carsten Bormann noted that the CoRE working group was going to adopt a
derivative called CoRAL.
 (draft-hartke-t2trg-coral-02 contained a note about JSON HAL that was
dropped in later versions.)

The reason for including any of this in rfc7320bis/BCP-190 is to point
people at this rather extensive body of work by people who were trying to
solve the problem that BCP-190 was set up to warn people away from. 
BCP-190 started as an internet draft "get off my lawn" but as is, it gives
scant advice for how to avoid the practice and still accomplish the goals.

It just seemed odd to update BCP 190 without giving more of a hint about
what seemed to be a widespread method of avoiding doing excessive and
unwieldy URL mangling in network protocols.


>> As a data point, for the applications in the CoRE working group, we 
>> have mostly been able to avoid BCP190-style arguments by using 
>> /.well-known, mainly because simple devices only tend to have one 
>> service offered directly under / and because IoT device platforms 
>> tend to provide the application developer full control over the URI
space.
>> /.well-known/core provides a discovery mechanism for the entry point 
>> URIs actually offered by a server.
>> For where this is not enough, the WG has just last week adopted CoRAL 
>> (not yet resubmitted as draft-ietf, so you can find it at
>> draft-hartke-t2trg-coral) as our idea of a hypermedia format like HAL.
>> Up to now, we tried to make everything work with RFC 6690 link 
>> format, but that has too many idiosyncrasies that started to get in 
>> the way of a long-term way forward.



https://it.toolbox.com/blogs/craigborysowich/overview-of-api-hypermedia-type
s-093018
https://www.fenews.co.uk/press-releases/33067-detailed-guide-api-technical-a
nd-data-standards-v2-2019 


From nobody Thu Oct 17 13:10:17 2019
Return-Path: <adam@nostrum.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B9D41200FA for <art@ietfa.amsl.com>; Thu, 17 Oct 2019 13:10:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.279
X-Spam-Level: 
X-Spam-Status: No, score=-1.279 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.4, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 tomC5Oz8eJ1M for <art@ietfa.amsl.com>; Thu, 17 Oct 2019 13:10:13 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 A9C80120241 for <art@ietf.org>; Thu, 17 Oct 2019 13:10:13 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x9HKA98h022454 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 17 Oct 2019 15:10:11 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1571343011; bh=eyZzA49mydw3GSVkN+IXJ08KcydBee7qIepIJJMAAEI=; h=Subject:To:References:From:Date:In-Reply-To; b=lVarovgLfPui3YXZpLIdwLEaSZyDSfZFnOBs3sQrdvxZaeGLW02CchmGrFDYBrthl Ot2UXEqlAe5VkvJNYGKTSPqltr2T1jX/it9ip6kLmQb9CKEZs1JZgZJtjTj+dLOsQn ouiiCAm8oBC/RSD8dkaaLBgPjljHwj9DBgsRBnW4=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Larry Masinter <LMM@acm.org>, "'Applications and Real-Time Area Discussion'" <art@ietf.org>
References: <cdeb0612-89bd-ae70-a7c3-a769d07e5f4c@nostrum.com> <4921de47-86e7-22af-767c-fb2ec0c3cc1f@cs.tcd.ie> <015301d58455$6931dde0$3b9599a0$@acm.org> <422af97e-cf53-9e3c-84ab-0d2dd907bdfe@nostrum.com> <027a01d58480$285495d0$78fdc170$@acm.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <3fd8fbc7-5cd2-a6e7-8dc6-69b0cf6608ed@nostrum.com>
Date: Thu, 17 Oct 2019 15:10:03 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <027a01d58480$285495d0$78fdc170$@acm.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ZDcq8URFgbfRK8IrosqGqfo1utA>
Subject: Re: [art] Last Call for Comments: draft-nottingham-rfc7320bis (BCP 190 update)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2019 20:10:16 -0000

Ah, okay. So it sounds like you're suggesting that Section 3 should add 
new content to talk about additional techniques, beyond the three it 
already describes.

Can you propose some text?

/a

On 10/16/19 7:16 PM, Larry Masinter wrote:
> As I understand it, people wanting to do what used to be separate protocols
> now define the network interface as a kind of REST API.
>
>
> https://en.wikipedia.org/wiki/Hypertext_Application_Language
>
>
> HAL is the name for a style of Interface where the relationship between one
> resource and other resources that are related are not defined by asking the
> client to do string manipulation on the URLs (like you might by defining a
> base and doing relative relations) but rather explicitly returning
> "hypermedia objects" that contain explicit URLs of the related resources.
>
> JSON-HAL is just one such building block.  When I mentioned it on the ART
> list, Carsten Bormann noted that the CoRE working group was going to adopt a
> derivative called CoRAL.
>   (draft-hartke-t2trg-coral-02 contained a note about JSON HAL that was
> dropped in later versions.)
>
> The reason for including any of this in rfc7320bis/BCP-190 is to point
> people at this rather extensive body of work by people who were trying to
> solve the problem that BCP-190 was set up to warn people away from.
> BCP-190 started as an internet draft "get off my lawn" but as is, it gives
> scant advice for how to avoid the practice and still accomplish the goals.
>
> It just seemed odd to update BCP 190 without giving more of a hint about
> what seemed to be a widespread method of avoiding doing excessive and
> unwieldy URL mangling in network protocols.
>
>
>>> As a data point, for the applications in the CoRE working group, we
>>> have mostly been able to avoid BCP190-style arguments by using
>>> /.well-known, mainly because simple devices only tend to have one
>>> service offered directly under / and because IoT device platforms
>>> tend to provide the application developer full control over the URI
> space.
>>> /.well-known/core provides a discovery mechanism for the entry point
>>> URIs actually offered by a server.
>>> For where this is not enough, the WG has just last week adopted CoRAL
>>> (not yet resubmitted as draft-ietf, so you can find it at
>>> draft-hartke-t2trg-coral) as our idea of a hypermedia format like HAL.
>>> Up to now, we tried to make everything work with RFC 6690 link
>>> format, but that has too many idiosyncrasies that started to get in
>>> the way of a long-term way forward.
>
>
> https://it.toolbox.com/blogs/craigborysowich/overview-of-api-hypermedia-type
> s-093018
> https://www.fenews.co.uk/press-releases/33067-detailed-guide-api-technical-a
> nd-data-standards-v2-2019
>


From nobody Tue Oct 29 12:05:08 2019
Return-Path: <antonio@gnu.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8333B120052 for <art@ietfa.amsl.com>; Thu, 24 Oct 2019 08:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 gl0ee9Poi2nT for <art@ietfa.amsl.com>; Thu, 24 Oct 2019 08:58:31 -0700 (PDT)
Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 947B61200CC for <art@ietf.org>; Thu, 24 Oct 2019 08:58:31 -0700 (PDT)
Received: from fencepost.gnu.org ([2001:470:142:3::e]:48219) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <antonio@gnu.org>) id 1iNfVO-0007K0-Cv; Thu, 24 Oct 2019 11:58:30 -0400
Received: from 181.red-88-3-73.dynamicip.rima-tde.net ([88.3.73.181]:58445 helo=[192.168.1.2]) by fencepost.gnu.org with esmtpa (Exim 4.82) (envelope-from <antonio@gnu.org>) id 1iNfVL-0001gq-SN; Thu, 24 Oct 2019 11:58:29 -0400
Message-ID: <5DB1CA45.10106@gnu.org>
Date: Thu, 24 Oct 2019 17:59:01 +0200
From: Antonio Diaz Diaz <antonio@gnu.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14
MIME-Version: 1.0
To: art@ietf.org
CC: Antonio Diaz Diaz <antonio@gnu.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ZuX1_G6rLsuoH04JNjJuD2rQ318>
X-Mailman-Approved-At: Tue, 29 Oct 2019 12:05:06 -0700
Subject: [art] Request for review of draft-diaz-lzip-00
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Oct 2019 15:58:34 -0000

Dear all,

During the latest GNU Hackers Meeting, the maintainers of GNU Wget suggested 
me to register the content encoding name "lzip" because they were 
implementing support for it in Wget2. We agreed that it would be a good idea 
to also register the media type "application/lzip". These registrations 
should help prevent the use of "x-lzip" as a content encoding, and prevent 
further deployment of the unregistered media type "application/x-lzip". I 
learned about the problems caused by the "x-" prefix at 
http://tools.ietf.org/html/rfc6648#appendix-B

After reading a good number of RFCs, I found in section 4.8 of RFC 8126 that 
making these registrations requires the publication of an AD-Sponsored RFC. 
Therefore, I submitted an Interned Draft[1] and am writing to this list in 
the hope that it is the right place to request review and sponsoring.

[1] https://datatracker.ietf.org/doc/draft-diaz-lzip/

Two weeks ago I sent the entry for the media type application/lzip to the 
media-types@iana.org mailing list for review. No answer yet.

Lzip is a compressed format designed, written, and tested with great care to 
replace most uses of gzip and bzip2. The reference implementation has been 
in stable status since 2009, and is widely deployed. Most archivers support 
the lzip format. Many browsers and package managers support the media type 
as application/x-lzip.

The IANA Time Zone Database[2] is distributed in lzip format (and the IANA 
server identifies the tar.lz files as application/x-lzip).

[2] http://www.iana.org/time-zones


Thanks in advance,
Antonio.

