I would beg to differ, I love my Iced Tea (ref: http://en.wikipedia.org/wiki/Iced_tea)
Further as the Internet Engineering Tea Force we must ensure all possibilities are covered... Even if its not common within a region/culture doesn't mean its not used elsewhere.
On Wed, Apr 2, 2014 at 8:46 AM, Ole Jacobsen <olejacobsen@xxxxxx> wrote:
As any Brit will tell you: ice has absolutely NOTHING to do with tea, so it would be out of scope.Sat-too-long-and-is-still-hot is, if I recall, known as "stewed" and anyone responsible faces possible deportation from the UK. A very serious matter indeed, almost as serious as refusing to obey the rules of a queue.OleOle J. JacobsenEditor & PublisherCell: +1 415 370-4628docomo: (090) 3337 9311UK Orange: +44 780 5977 889Sent from my iPhoneReview 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?
-rgdOn Apr 1, 2014, at 3:49 PM, "Andrew G. Malis" <agmalis@xxxxxxxxx> 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. Anotheraddition-type may be required.Cheers,AndyOn Tue, Apr 1, 2014 at 6:00 PM, <rfc-editor@xxxxxxxxxxxxxx> wrote:
A new Request for Comments is now available in online RFC libraries.RFC 7168Title: The Hyper Text Coffee PotControl Protocol for Tea Efflux Appliances(HTCPCP-TEA)
Author: I. NazarStatus: Informational
Stream: IndependentDate: 1 April 2014
Mailbox: inazar@xxxxxxxxxxxxxxPages: 7Characters: 14490Updates: RFC 2324I-D Tag: draft-nazar-htcpcp-tea-00.txtURL: http://www.rfc-editor.org/rfc/rfc7168.txtThe Hyper Text Coffee Pot Control Protocol (HTCPCP) specificationdoes not allow for the brewing of tea, in all its variety andcomplexity. 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 ofthis memo is unlimited.This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, seehttp://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.htmlRequests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@xxxxxxxxxxxxxx. Unless
specifically noted otherwise on the RFC itself, all RFCs are forunlimited distribution.
The RFC Editor TeamAssociation Management Solutions, LLC