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

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
> 