[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [sitefinder-tech-discuss Home]
Subject: Re: [sitefinder-tech-discuss] followup from 15oct secsac
> > > > Other services as something to be addressed? Yes -- that's > > why TCP resets > > > and ICMP errors are used to reject connection attempts for > > other services. > > > > > > -Scott- > > > > that then opens the question of service rollout. hindsight often > > being considered better than foresight, it would have been > > interesing to see the impact of a wildcard "A" will > > TCP resets and ICMP errors generated for all services... :) > > > > presuming that wildcard entries are an acceptable delivery > > vector for service delivery, what would be the plan for > > coordinating w/ the zone consitutents on new service > > deployment? > > > > say putting up valid services on port 123? > > or, being more inovative, ports 88, 210, 546-7, 11371 and 26000 > > All TBD. As far as a plan goes, that's still being discussed in various > forums. All I can say is that we're currently thinking about many different > options and we're willing to listen to ideas. > > ...and before anyone else says it, we've already heard the "don't do > wildcards" idea. > > -Scott- to be sure... but I'm less concerned about the specific service and more about the ways and means to be used to inform the community that such service(s) are being contemplated, methods for gaining consensus, testing and verifcation suites, EIS reports to the community (EIS == environmental impact statements :) et.al... --bill ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.elistx.com/unsubscribe>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [sitefinder-tech-discuss Home]
Powered by eList eXpress LLC