Re: [rfc-i] rfc-interest Digest, Vol 189, Issue 10

BBMcoll <BBMcollections@bell.ca> Mon, 20 July 2020 19:01 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 153203A0F15; Mon, 20 Jul 2020 12:01:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=bell.ca
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 2BDkQ37nmbmY; Mon, 20 Jul 2020 12:01:20 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07A373A0E9B; Mon, 20 Jul 2020 12:01:07 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9E183F40721; Mon, 20 Jul 2020 12:00:54 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 7124CF40721 for <rfc-interest@rfc-editor.org>; Mon, 20 Jul 2020 12:00:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bell.ca
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nDnRuytdaMnq for <rfc-interest@rfc-editor.org>; Mon, 20 Jul 2020 12:00:48 -0700 (PDT)
Received: from ESA3-Dor.bell.ca (esa3-dor.bell.ca [204.101.223.60]) by rfc-editor.org (Postfix) with ESMTPS id 6A3D1F40720 for <rfc-interest@rfc-editor.org>; Mon, 20 Jul 2020 12:00:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bell.ca; i=@bell.ca; q=dns/txt; s=ESAcorp; t=1595271660; x=1626807660; h=from:to:date:message-id:mime-version:subject; bh=mGRB44hv2HEnYVr6sfKFchDY5madqXGhlyNEwm6rHJs=; b=UNsbkWmNTuGnQwLLMgBZaL4Dnkifi+rR4wRHpW1pfrBGdn4aFzwm8UKg zDKmqIKPa6Zbtb227zgW9oXFOlcoZdow4AUjMYUFXTIIWyk/6xssXZJZ6 KpnsClPfJehDwmivVShQoFDV0GoG3sr75XY3IyF/QNJVErlbxc0Grp4wN cBRD0TlMUrMB7xbhkrOL5oRjGqIXZ3yS6cxnXfe1/OzPMiOdeeQ2l4er+ o2KDAKc739BIPMNawhS6Fgzee5+5hvcYR/+DrxP8rJ3xpvtkPfYL/3Q2y pYdFMC6peyy3/plf3r9iDPomBbZ5ifyIQdsiQOuUlc926HRCamELpId3d A==;
IronPort-SDR: R6CXpkW8UvNFKyZ1kRjoG8IIg7PesMIFJgYjBVS9rvgeN3KgyYhwYSoTravQnUvQ5QwdfEzPjD ISK7Uz06R1Sg==
Received: from dc5cmz-d00.bellca.int.bell.ca (HELO DG1MBX03-WYN.bell.corp.bce.ca) ([198.235.121.231]) by esa03corp-dor.bell.corp.bce.ca with ESMTP; 20 Jul 2020 15:00:59 -0400
Received: from DG1MBX04-WYN.bell.corp.bce.ca (2002:8eb6:120e::8eb6:120e) by DG1MBX03-WYN.bell.corp.bce.ca (2002:8eb6:120d::8eb6:120d) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 20 Jul 2020 15:00:58 -0400
Received: from DG1MBX04-WYN.bell.corp.bce.ca ([fe80::18c0:101b:f25e:acdc]) by DG1MBX04-WYN.bell.corp.bce.ca ([fe80::18c0:101b:f25e:acdc%22]) with mapi id 15.00.1497.006; Mon, 20 Jul 2020 15:00:58 -0400
From: BBMcoll <BBMcollections@bell.ca>
To: "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Thread-Topic: [EXT]rfc-interest Digest, Vol 189, Issue 10
Thread-Index: AQHWXsgasyVM6R2yVU2XOopfHAS5Mg==
Date: Mon, 20 Jul 2020 19:00:58 +0000
Message-ID: <e9fb3a84a37c4e7884634f110c65777a@DG1MBX04-WYN.bell.corp.bce.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.24.25.3]
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [rfc-i] rfc-interest Digest, Vol 189, Issue 10
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============5809598393137229230=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Un message en français suivra
Thank you for your email.
A response to your inquiry will be provided as quickly as possible within the next 24 hours, during business hours (Eastern Time).
If this is an urgent matter, please contact our office at 1-866-350-7710 and select Option 1 for Telephone or Option 2 for Internet, High-speed, IP/Broadband.
Thank you for contacting BBM -Bell Business Markets Collections
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Merci de votre courriel.
Nous répondrons à votre demande dans les plus brefs délais à l’intérieur des prochaines 24 heures , durant les heures normales de bureau (heure de l’Est).
Pour toute question urgente, veuillez appeler notre bureau aux 1 866 350-7710 et sélectionner l’option 1 pour les services téléphoniques ou l’option 2 pour les services Internet (haute vitesse, IP et large bande).
Merci d’avoir communiqué avec l’équipe Recouvrement de Bell Marchés Affaires.

From: rfc-interest-request@rfc-editor.org
Sent: Monday, July 20, 2020 03:00 PM
To: rfc-interest@rfc-editor.org
Subject: [EXT]rfc-interest Digest, Vol 189, Issue 10

Send rfc-interest mailing list submissions to
        rfc-interest@rfc-editor.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://www.rfc-editor.org/mailman/listinfo/rfc-interest
or, via email, send a message with subject or body 'help' to
        rfc-interest-request@rfc-editor.org

You can reach the person managing the list at
        rfc-interest-owner@rfc-editor.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of rfc-interest digest..."


Today's Topics:

   1. Re: contributors section & tools & YANG (tom petch)
   2. Re: posting to this list (Brian E Carpenter)
   3. Re: [BULK] Re:  posting to this list (Ggh)
   4. RSS feeds and technology (Ggh)
   5. Re: RSS feeds and technology (Julian Reschke)


----------------------------------------------------------------------

Message: 1
Date: Sun, 19 Jul 2020 21:22:45 +0100
From: tom petch <daedulus@btconnect.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: RFC Interest <rfc-interest@rfc-editor.org>, tools-discuss@ietf.org
Subject: Re: [rfc-i] contributors section & tools & YANG
Message-ID: <5F14AB95.9030302@btconnect.com>
Content-Type: text/plain; charset=utf-8; format=flowed



On 17/07/2020 19:23, Carsten Bormann wrote:
> On 2020-07-17, at 11:33, tom petch <daedulus@btconnect.com> wrote:
>>
>> what about all those editors who appear in YANG modules
>
> Yeah, what about them?
>
> Er, this is a bit undirected for a question.
>
> I believe you should avoid sugared carbonated drinks before editing YANG modules, but maybe that wasn?t your question.

The question I had in mind was

 > Is there any tool from e.g.: the IETF or Arkko publishing houses that
actually deparses names
 > in a contributors section and does something with that information ?

and was asking whether by default or by option the names that are listed
in a YANG module in an IETF I-D are treated in the same way as
contributors section names are bearing in mind that YANG modules must be
plain text?

Tom Petch

>
> Gr??e, Carsten
>
> .
>


------------------------------

Message: 2
Date: Mon, 20 Jul 2020 10:45:16 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
To: John Levine <johnl@taugh.com>, ggh@multi.fi
Cc: rfc-interest@rfc-editor.org
Subject: Re: [rfc-i] posting to this list
Message-ID: <f2b12f54-d039-5363-00c1-e3cc8d05ea03@gmail.com>
Content-Type: text/plain; charset=utf-8

John, this actually isn't an IETF list. What you say about IETF lists is true, of course.

https://www.rfc-editor.org/mailman/listinfo/rfc-interest says:
"It will not be used for discussion of the IETF standards process, general IETF organizational issues, or issues for which the NOTE WELL admonition is needed for IPR reasons."

And Greg... welcome. Tell us.

Regards
   Brian Carpenter

On 20-Jul-20 04:08, John Levine wrote:
> In article <20200719135411.Horde.xsCwNsoxCPdmuFF8sAU3GSN@webmail.multi.fi> you write:
>> Sorry, I am new to this list, but I need to ask:is anyone (and
>> everyone) allowed to post to this list? Do you need to be a member of
>> some kind/sort?
>
> The IETF doesn't have members, you just show up.
>
> Messages to IETF mailing lists are considered contributions
> as described in the Note Well here:
>
> https://www.ietf.org/about/note-well/
>
> R's,
> John
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
> .
>


------------------------------

Message: 3
Date: Mon, 20 Jul 2020 09:35:46 +0300
From: Ggh <ggh@multi.fi>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: John Levine <johnl@taugh.com>, rfc-interest@rfc-editor.org
Subject: Re: [rfc-i] [BULK] Re:  posting to this list
Message-ID:
        <20200720093546.Horde.UTp7Qstvam4QyhxaKta0jYR@webmail.multi.fi>
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes

Hi All,

I have been dealing RSS for quite some time, and would like to discuss
ideas forth and back. I a few years ago wrote an RSS reader, which can
read and display RSS contents.

RSS is nice in many ways, I like the way of dealing with RSS sources
to display RSS contents to the reader.

In the the most general sense I think that RSS is important and a nice
technology. I have some thoughts creating an RSS publisher,
too.(attached)

So, I would like to bounce ideas forth and back.

Feel free to post on RSS technology and bounce ideas.

My RSS publisher:
https://www.multi.fi/~ghaga/rp.php

Thank's for your attention,

Best Regards,
Greg

Citerar Brian E Carpenter <brian.e.carpenter@gmail.com>:

> John, this actually isn't an IETF list. What you say about IETF
> lists is true, of course.
>
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest says:
> "It will not be used for discussion of the IETF standards process,
> general IETF organizational issues, or issues for which the NOTE
> WELL admonition is needed for IPR reasons."
>
> And Greg... welcome. Tell us.
>
> Regards
>    Brian Carpenter
>
> On 20-Jul-20 04:08, John Levine wrote:
>> In article
>> <20200719135411.Horde.xsCwNsoxCPdmuFF8sAU3GSN@webmail.multi.fi> you
>> write:
>>> Sorry, I am new to this list, but I need to ask:is anyone (and
>>> everyone) allowed to post to this list? Do you need to be a member of
>>> some kind/sort?
>>
>> The IETF doesn't have members, you just show up.
>>
>> Messages to IETF mailing lists are considered contributions
>> as described in the Note Well here:
>>
>> https://www.ietf.org/about/note-well/
>>
>> R's,
>> John
>> _______________________________________________
>> rfc-interest mailing list
>> rfc-interest@rfc-editor.org
>> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>> .
>>



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




------------------------------

Message: 4
Date: Mon, 20 Jul 2020 09:37:06 +0300
From: Ggh <ggh@multi.fi>
To: rfc-interest@rfc-editor.org
Subject: [rfc-i] RSS feeds and technology
Message-ID:
        <20200720093706.Horde.S76Bn2Rj_2BR5aYcOnG1lDA@webmail.multi.fi>
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes


Hi All,

I have been dealing RSS for quite some time, and would like to discuss
ideas forth and back. I a few years ago wrote an RSS reader, which can
read and display RSS contents.

RSS is nice in many ways, I like the way of dealing with RSS sources
to display RSS contents to the reader.

In the the most general sense I think that RSS is important and a nice
technology. I have some thoughts creating an RSS publisher,
too.(attached)

So, I would like to bounce ideas forth and back.

Feel free to post on RSS technology and bounce ideas.

My RSS publisher:
https://www.multi.fi/~ghaga/rp.php

Thank's for your attention,

Best Regards,
Greg


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




------------------------------

Message: 5
Date: Mon, 20 Jul 2020 08:52:06 +0200
From: Julian Reschke <julian.reschke@gmx.de>
To: Ggh <ggh@multi.fi>, rfc-interest@rfc-editor.org
Subject: Re: [rfc-i] RSS feeds and technology
Message-ID: <b6907f87-9d33-d46d-2d37-d2c442e08653@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed

On 20.07.2020 08:37, Ggh wrote:
>
> Hi All,
>
> I have been dealing RSS for quite some time, and would like to discuss
> ideas forth and back. I a few years ago wrote an RSS reader, which can
> read and display RSS contents.
>
> RSS is nice in many ways, I like the way of dealing with RSS sources to
> display RSS contents to the reader.
>
> In the the most general sense I think that RSS is important and a nice
> technology. I have some thoughts creating an RSS publisher, too.(attached)
>
> So, I would like to bounce ideas forth and back.
>
> Feel free to post on RSS technology and bounce ideas.
>
> My RSS publisher:
> https://www.multi.fi/~ghaga/rp.php
>
> Thank's for your attention,
>
> Best Regards,
> Greg
> ...

Greg,

see <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>:

"The rfc-interest@rfc-editor.org mailing list has been created by the
RFC Editor to facilitate community discussion on the RFC series and to
make suggestions about RFC Editor functions. The RFC Editor hopes that
this mailing list will provide a focal point for input, information, and
discussion about the details of the RFC process, as well as an archive
to avoid the continual re-hashing of some issues. Topics appropriate to
this list may include formatting, tools, style, content, and indexing
aspects of the RFC series. It will not be used for discussion of the
IETF standards process, general IETF organizational issues, or issues
for which the NOTE WELL admonition is needed for IPR reasons."

For discussion of RSS, the best match I can think of would be the ART
mailing list <https://www.ietf.org/mailman/listinfo/art>.

Best regards, Julian


------------------------------

Subject: Digest Footer

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest


------------------------------

End of rfc-interest Digest, Vol 189, Issue 10
*********************************************
------------------------------------------------------------------------------
External Email: Please use caution when opening links and attachments / Courriel externe: Soyez prudent avec les liens et documents joints

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest