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.
*Chaitanya Dhareshwar*
Linkedin <http://in.linkedin.com/in/chaitanyabd> | Blog <http://cbd.vcio.in> |
Skype: chaitanyabd
Mobile: +91.9820760253
On Wed, Apr 2, 2014 at 8:46 AM, Ole Jacobsen <olejacobsen(_at_)me(_dot_)com>
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.
Ole
Ole J. Jacobsen
Editor & Publisher
Cell: +1 415 370-4628
docomo: (090) 3337 9311
UK Orange: +44 780 5977 889
Sent from my iPhone
On 1 Apr 2014, at 19:52, "Rgd.ietf" <rgd(_dot_)ietf(_at_)gmail(_dot_)com>
wrote:
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(_at_)gmail(_dot_)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(_at_)rfc-editor(_dot_)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(_at_)deviantart(_dot_)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(_at_)rfc-editor(_dot_)org.
Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC