[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: DNS based Destination Selection

To: multi6@ops.ietf.org
Subject: Re: DNS based Destination Selection
From: Brian E Carpenter <brian@hursley.ibm.com>
Date: Thu, 19 Jun 2003 17:59:52 +0200
Organization: IBM
References: <1055952500.30027.12.camel@trigger.highway.co.uk> <Pine.LNX.4.55.0306181153000.25748@seatpost.its.uiowa.edu> <1056003888.19105.22.camel@descartes> <1056012605.30027.39.camel@trigger.highway.co.uk>

A couple of comments

1. Forget A6 records. They are deprecated and pretty much dead and buried.

2. I agree with the comments suggesting that DNS cannot be the primary
mechanism for address selection. However, that doesn't exclude a DNS
based solution for address mapping. Applications that don't use DNS
to initiate a transaction might just have to use DNS if they want to
benefit from a mapping style of multihoming.

  Brian

References:
- DNS based Destination Selection
  - From: David Gethings <davidg@pipex.net>
- Re: DNS based Destination Selection
  - From: Jay Ford <jay-ford@uiowa.edu>
- Re: DNS based Destination Selection
  - From: Cedric de Launois <delaunois@info.ucl.ac.be>
- Re: DNS based Destination Selection
  - From: David Gethings <davidg@pipex.net>

Prev by Date: RE: draft-ietf-multi6-multihoming-requirements-06.txt
Next by Date: Re: DNS based Destination Selection
Previous by thread: Re: DNS based Destination Selection
Next by thread: Re: DNS based Destination Selection
Index(es):
- Date
- Thread