IETF Logo Mail Archive

Re: [art] RSS and RFC?

worley@ariadne.com (Dale R. Worley) Thu, 10 October 2019 02:53 UTC

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
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
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

v2.23.0 | Report a Bug | By Email