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

"Rgd.ietf" <rgd.ietf@gmail.com> Wed, 02 April 2014 02:53 UTC

Return-Path: <rgd.ietf@gmail.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 CFD0D1A00AA for <ietf@ietfa.amsl.com>; Tue, 1 Apr 2014 19:53:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 YA4ph1aMt6ai for <ietf@ietfa.amsl.com>; Tue, 1 Apr 2014 19:52:59 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id A82E91A00B4 for <ietf@ietf.org>; Tue, 1 Apr 2014 19:52:59 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id rd3so10794633pab.39 for <ietf@ietf.org>; Tue, 01 Apr 2014 19:52:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:from:subject:date:to; bh=lZYgzEITnt+ClcUVv4bbfSFv4cZvg+Dq13q/8qb0JCw=; b=JiFo7hfVSvE+Jx2ms7yUk6cbykrOPqKUKEbetFqkK3uBv0LFVOjp9Ot03q/VoSy7SS pN0HxYTozr17TH0TgIRWGJ1XEgCHxBzBZDStspYeBf57K5GtmEB9ujghQO7ZLhAmuMgf 4Nr13ebvWskezfyz5iQYPCl7yzsEdM4pIt2+J8xhYmcK7+jxKKVga/G1IFe9vVDBa0Wn QOVZdRhn1pBglmGzsmW7H7Fs03Z29oMG+2tYrOa3aRq2UYiRyDXfJJEqnbcuZdy6+kuj ymsvb0Djls2GcBpIFTdgv0VJ7gOBcxhshK63L4Btk9fdsqkKbziq8g8GqvTu8Pw6OuyC XXOw==
X-Received: by 10.66.141.144 with SMTP id ro16mr13656560pab.131.1396407176060; Tue, 01 Apr 2014 19:52:56 -0700 (PDT)
Received: from [10.0.1.7] (cpe-142-136-145-221.socal.res.rr.com. [142.136.145.221]) by mx.google.com with ESMTPSA id iu10sm869542pbd.71.2014.04.01.19.52.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 01 Apr 2014 19:52:54 -0700 (PDT)
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
In-Reply-To: <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com>
X-Mailer: iPad Mail (11B651)
From: "Rgd.ietf" <rgd.ietf@gmail.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Date: Tue, 1 Apr 2014 19:52:53 -0700
To: "Andrew G. Malis" <agmalis@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TMljSg6jabFVGtOD4SlP1tCV7p0
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: Wed, 02 Apr 2014 02:53:06 -0000

Review comments:

Section 2.2.1 There are also additional modes of sugar than cane sugar.  It should support sugar beet sugar. So section 2.2.1 sugar-beet and sugar-cane should be included in the options.

Tea has state(s) - it is either brewed or unbrewed , as well as cold or hot. There needs to be an optional state monitor reporting {brewed | unbrewed } and { hot | cold }.  

 I'm undecided if there should be a  { sat-too-long-and-is-cold | fresh } message. Perhaps a wider review would be helpful.

Finally is there any requirement for a parameter to specify ice?

-rgd

> On Apr 1, 2014, at 3:49 PM, "Andrew G. Malis" <agmalis@gmail.com> 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
> 
> 
>> 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
>