I think the third scenario is likely to be problematic.

My understanding is that your third scenario would
require that the customers' networks all be part of
the same site as the ISP network - at least as far in
as a DNS server somewhere. I imagine some ISPs
might want to draw a site boundary somewhere
between the ISP edge and the CPE; either in the
CPE or in the ISP edge device or by declaring the
CPE-PE link to be not in either site...

- Ralph

At 05:36 PM 4/4/2002 +0200, Hesham Soliman (ERA) wrote:
>Hi,
>
>During the last meeting a question was raised
>on whether the scenarios for which the stateless
>DNS discovery draft can be used, were clear to
>everyone.
>I think that on a very high level we could basically
>say that this draft is useful when a host desires
>to discover a DNS located in the same site for the
>purpose of address resolution.
>
>Examples of where this can be useful:
>
>- Corporate networks
>- Cellular networks: 3GPP is one case where this
>   would be useful for all those who complain
>   about how small the devices are and that the
>   less code the better ;)
>
>- ISPs which host a DNS server for customers
>   connected via DSL for example. Of course in
>   this case they would have to define a site
>   accordingly.
>
>Any other scenarios ? I think there is a reasonable
>case for this draft based on the scenarios
>above.
>
>Comments?
>
>Cheers,
>Hesham
>
>--------------------------------------------------------------------
>IETF IPng Working Group Mailing List
>IPng Home Page:                      http://playground.sun.com/ipng
>FTP archive:                      ftp://playground.sun.com/pub/ipng
>Direct all administrative requests to [EMAIL PROTECTED]
>--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to