Re: RFC 2782: SRV weight evaluation
Stuart Cheshire <cheshire@apple.com> Thu, 12 July 2001 05:02 UTC
Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA07171 for <dnsext-archive@lists.ietf.org>; Thu, 12 Jul 2001 01:02:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1) id 15KXvI-0006Gg-00 for namedroppers-data@psg.com; Wed, 11 Jul 2001 21:17:56 -0700
Received: from rip.psg.com ([147.28.0.39] ident=exim) by psg.com with esmtp (Exim 3.31 #1) id 15KXvI-0006Ga-00 for namedroppers@ops.ietf.org; Wed, 11 Jul 2001 21:17:56 -0700
Received: from randy by rip.psg.com with local (Exim 3.30 #1) id 15KXvI-000Br7-00 for namedroppers@ops.ietf.org; Wed, 11 Jul 2001 21:17:56 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
From: Stuart Cheshire <cheshire@apple.com>
To: Andrew Brown <atatat@atatdot.net>
cc: namedroppers@ops.ietf.org
Subject: Re: RFC 2782: SRV weight evaluation
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Message-Id: <E15KXvI-0006Gg-00@psg.com>
Date: Wed, 11 Jul 2001 21:17:56 -0700
Content-Transfer-Encoding: 7bit
>>If weights are to have a sensible intuitive meaning, then >>(in the presence of records containing weights greater than 0) >>records with weight 0 should *never* be selected. > >as a guess, i'd say that "records with a weight of zero in a record >set with some non-zero weights will end up being selected last in no >particular order". that is to say, all non-zero weighted records will >be picked first, and then the zero weight ones will be picked. Yes, you are right. That was what I meant. My unstated assumption was that after trying to contact a server and failing, that record is removed from the list and the process is repeated. After all the non-zero weight records have been tried and failed and removed, the zero-weight records are no longer "in the presence of records containing weights greater than 0", so they are now eligible for selection. Perhaps this wording is better: --- In the presence of records containing weights greater than zero, records with weight zero should *never* be selected. When there are no more records remaining present in the list with weights greater than zero (because all servers with non-zero weights, if any, have been tried already, and failed, and therefore removed from the list) any records still remaining (i.e. those with weight zero) should then be tried in random order. --- Stuart Cheshire <cheshire@apple.com> * Wizard Without Portfolio, Apple Computer * Chairman, IETF ZEROCONF * www.stuartcheshire.org to unsubscribe send a message to namedroppers-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body.
- Re: RFC 2782: SRV weight evaluation Stuart Cheshire
- RE: RFC 2782: SRV weight evaluation Levon Esibov
- RE: RFC 2782: SRV weight evaluation Stuart Cheshire