RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)

<> Sun, 06 April 2014 00:41 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id EF57A1A01E8 for <>; Sat, 5 Apr 2014 17:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Xob5z29nHvB3 for <>; Sat, 5 Apr 2014 17:41:50 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 85E161A01DD for <>; Sat, 5 Apr 2014 17:41:49 -0700 (PDT)
Received: from [] by id CB/31-16341-7C2A0435; Sun, 06 Apr 2014 00:41:43 +0000
X-Originating-IP: []
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28075 invoked from network); 6 Apr 2014 00:41:43 -0000
Received: from (HELO ( by with AES128-SHA encrypted SMTP; 6 Apr 2014 00:41:43 -0000
Received: from ([]) by ([]) with mapi; Sun, 6 Apr 2014 01:41:42 +0100
Date: Sun, 06 Apr 2014 01:41:41 +0100
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Topic: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Index: Ac9PlRli6HVAjPTbShSk3czARFusbABmUumu
Message-ID: <>
References: <> <> <1396395466.15324.6860.camel@mightyatom>, <p06240603cf639ebf8c0d@[]>
In-Reply-To: <p06240603cf639ebf8c0d@[]>
Accept-Language: en-US, en-GB
Content-Language: en-GB
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 06 Apr 2014 00:41:54 -0000

Look, if the water is not boiling, it may contain more bacteria,
with adverse effects on health. Boiling water properly
is most likely to kill that bacteria and prevent infection.

Boiling the water is best practice, and you should use that
best practice even though you clearly don't understand why.
Trust us, you'll come to love it. It's for your own good.

This is clearly another security threat to be prevented, and
the IETF's core work and primary focus is on mitigating
security threats that the IETF created in the first place.

Boiling could have been mentioned in the security considerations
section. I see there's no mention of TLS or SHA or authenticating
commands either - so the IETF needs to set up a security group to
fix and properly secure HTCPCP-TEA immediately.
Documenting how everyone must always make tea will also be
a useful outcome of this group.

get to it, Stephen!

Lloyd Wood
From: ietf [] On Behalf Of Randall Gellens []
Sent: 04 April 2014 00:29
To: Elwyn Davies; Andrew G. Malis
Cc: IETF Discussion
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea  Efflux Appliances (HTCPCP-TEA)

At 12:37 AM +0100 4/2/14, Elwyn Davies wrote:

>  We also need the internationalized version to cater for all those
>  excellent varieties of China Tea.  A nice drop of pu-erh perhaps?

I stopped reading when I saw that there was no provision for handling
more delicate teas, just as Japanese sencha or gyokuro, which require
significantly cooler water and shorter brewing times.  I'm not sure
I'd characterize this as a question of internationalization, since it
involves fundamental protocol elements and operation rather than user
display text.

Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
The single biggest problem in communication is the illusion that it
has taken place.                                       --G. B. Shaw