IETF Logo Mail Archive

Re: [apps-discuss] Stewart Bryant's Discuss on draft-ietf-appsawg-rfc5451bis-09: (with DISCUSS)

"John Levine" <johnl@taugh.com> Wed, 03 July 2013 15:56 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1061611E81D2 for <apps-discuss@ietfa.amsl.com>; Wed, 3 Jul 2013 08:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.697
X-Spam-Level:
X-Spam-Status: No, score=-110.697 tagged_above=-999 required=5 tests=[AWL=0.502, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sMEquwBgr6Ch for <apps-discuss@ietfa.amsl.com>; Wed, 3 Jul 2013 08:56:15 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id A57AF11E81CB for <apps-discuss@ietf.org>; Wed, 3 Jul 2013 08:56:12 -0700 (PDT)
Received: (qmail 89279 invoked from network); 3 Jul 2013 15:56:09 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 3 Jul 2013 15:56:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51d44999.xn--9vv.k1307; i=johnl@user.iecc.com; bh=Lehd4pl4y+MA/ei5bH+ajPlUv1m4pG5uW6u25f3EyzE=; b=R9HbssqZXDovW4C0GSuO7AfRJtPeVMbu8uaTYnX97ozbskFvQpYCxSAUO9Yq4aLZFj/0MYxkIe4eWiKdcsQycsFTHpyuwoAimYvE9WzBzve+88Yw6tZvp2Ac6Upy4NBeP+yHd3TkzXJedU2YqsZphnOMOHmB9fAQOQXS7AOhrvIgW04y2p/EjrHlFYGQhFv49PiOW7x2LwJneELZX5S6xundh1zX95z1TKZzpoTV2epdAl3Lqo88QxFy2mUOxs91
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51d44999.xn--9vv.k1307; olt=johnl@user.iecc.com; bh=Lehd4pl4y+MA/ei5bH+ajPlUv1m4pG5uW6u25f3EyzE=; b=mgU8qqP0ORmFJgRa8o4dJYr2RVairRXZwZQfTD87ksodXO5a4T5g7IAIkNCmiWB7dG5VTao7MJpd/IuHSTjDmi946TQQWIepR+hvCOJk5jJksdb0rO3oi8neHmdQalRhzgzRj9tvO0wVFgTIjQx23Q991OmVzZ6JvQFHXN+rL/6dBxmj3v3+blilvbEICWfQ2QcnzBaHFRYSuwmetywycY8sOiZWa7IF0mhPw6eIXLWPPLdxA44V64uoVPJUdYZj
Date: Wed, 03 Jul 2013 15:55:47 -0000
Message-ID: <20130703155547.33166.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: apps-discuss@ietf.org
In-Reply-To: <20130703141513.9256.44126.idtracker@ietfa.amsl.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Cc: stbryant@cisco.com
Subject: Re: [apps-discuss] Stewart Bryant's Discuss on draft-ietf-appsawg-rfc5451bis-09: (with DISCUSS)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jul 2013 15:56:21 -0000

>This update to RFC5451 introduces text containing what are almost
>certainly the trade marked names of a number of products. This does not
>seem to be called out in the text, which may be a problem for the trade
>mark owners.
>
>My question (to the IESG) is whether this is something that we need to
>worry about, or something that we just leave for the RFC Editor to deal
>with.

The IETF is under no duty to acknowledge or otherwise defend
trademarks of third parties (despite the legend about the Unix
trademark.)

This sounds like a question that would better be directed to Jorge.

R's,
John

v2.23.0 | Report a Bug | By Email