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

Elwyn Davies <elwynd@dial.pipex.com> Tue, 01 April 2014 23:38 UTC

Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7E801A0011 for <ietf@ietfa.amsl.com>; Tue, 1 Apr 2014 16:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 74KAxx_tZeUV for <ietf@ietfa.amsl.com>; Tue, 1 Apr 2014 16:38:03 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 868EC1A0028 for <ietf@ietf.org>; Tue, 1 Apr 2014 16:37:56 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1WV8FX-0002GG-Nn; Wed, 02 Apr 2014 00:37:51 +0100
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Elwyn Davies <elwynd@dial.pipex.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
In-Reply-To: <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
Content-Type: text/plain
Date: Wed, 02 Apr 2014 00:37:46 +0100
Message-Id: <1396395466.15324.6860.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/A1GGO-A7fmmC2DONnU9HB00SxX4
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Apr 2014 23:38:07 -0000

On Tue, 2014-04-01 at 18:48 -0400, Andrew G. Malis wrote:
> As a tea drinker, I'm very happy to see this extension to RFC 2324.
> However, many people drink their tea with lemon, and that doesn't
> really fit into any of the addition-types in section 2.2.1. Another
> addition-type may be required.
> 
> Cheers,
> Andy

+1

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

Tea 'up,
Elwyn

> 
> 
> On Tue, Apr 1, 2014 at 6:00 PM,  <rfc-editor@rfc-editor.org> wrote:
> > A new Request for Comments is now available in online RFC libraries.
> >
> >
> >         RFC 7168
> >
> >         Title:      The Hyper Text Coffee Pot
> >                     Control Protocol for Tea Efflux Appliances
> >                     (HTCPCP-TEA)
> >         Author:     I. Nazar
> >         Status:     Informational
> >         Stream:     Independent
> >         Date:       1 April 2014
> >         Mailbox:    inazar@deviantart.com
> >         Pages:      7
> >         Characters: 14490
> >         Updates:    RFC 2324
> >
> >         I-D Tag:    draft-nazar-htcpcp-tea-00.txt
> >
> >         URL:        http://www.rfc-editor.org/rfc/rfc7168.txt
> >
> > The Hyper Text Coffee Pot Control Protocol (HTCPCP) specification
> > does not allow for the brewing of tea, in all its variety and
> > complexity.  This paper outlines an extension to HTCPCP to allow
> > for pots to provide networked tea-brewing facilities.
> >
> >
> > INFORMATIONAL: This memo provides information for the Internet community.
> > It does not specify an Internet standard of any kind. Distribution of
> > this memo is unlimited.
> >
> > This announcement is sent to the IETF-Announce and rfc-dist lists.
> > To subscribe or unsubscribe, see
> >   http://www.ietf.org/mailman/listinfo/ietf-announce
> >   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> >
> > For searching the RFC series, see http://www.rfc-editor.org/search
> > For downloading RFCs, see http://www.rfc-editor.org/rfc.html
> >
> > Requests for special distribution should be addressed to either the
> > author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> > specifically noted otherwise on the RFC itself, all RFCs are for
> > unlimited distribution.
> >
> >
> > The RFC Editor Team
> > Association Management Solutions, LLC
> >
> >
>