W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

Re: draft-ietf-http-state-mgmt-03.txt

From: Bill Sommerfeld <sommerfeld@apollo.hp.com>
Date: Thu, 01 Aug 1996 14:30:52 -0400
Message-Id: <199608011831.AA231774263@otter.hpl.hp.com>
To: Benjamin Franz <snowhare@netimages.com>
Cc: dmk@bell-labs.com, montulli@netscape.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/1187
Please look at RFC1123.

See section (the QUOTE command), which is a MUST.

See also, (DNS user interface), (DNS abbreviation
expansion), etc., etc.,

All of these concern themselves exclusively with how host software
forms protocol messages based on user input. seems quite analagous to cookies, since it places restrictions
on how much searching a resolver can do:

		 There is danger that a search-list mechanism will
                 generate excessive queries to the root servers while
                 testing whether user input is a complete domain name,
                 lacking a final period to mark it as complete.  A
                 search-list mechanism MUST have one of, and SHOULD have
                 both of, the following two provisions to prevent this:

                 (a)  The local resolver/name server can implement
                      caching  of negative responses (see Section

                 (b)  The search list expander can require two or more
                      interior dots in a generated domain name before it
                      tries using the name in a query to non-local
                      domain servers, such as the root.

					- Bill
Received on Thursday, 1 August 1996 11:34:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:17 UTC