Re: [Softwires] [Fwd: I-D Action:draft-carpenter-softwire-sample-00.txt]

Hi,

If more than one SIMPLE server deployed and anycast addresses
are not used, how do SIMPLE clients discover the suitable
SIMPLE server, i.e., how do SIMPLE clients get the listener
transport address of the suitable SIMPLE server?

THanks,
washam 

----- Original Message -----
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Wednesday, June 9, 2010 5:12 pm
Subject: Re: [Softwires] [Fwd: I-D Action:draft-carpenter-softwire-sample-00.txt]
To: WashamFan <Washam.Fan@huaweisymantec.com>
Cc: softwires@ietf.org, Sheng Jiang <shengjiang@huawei.com>

> Hi Washam,
>  
>  Thanks for your comments, see in line. These are my comments;
>  Sheng may want to comment too.
>  
>  On 2010-06-08 20:30, WashamFan wrote:
>  > Hi,
>  > 
>  > There are some concerns after I skimmed over the draft.
>  > How many SIMPLE servers should be deployed in a metro
>  > network? 
>  
>  Well, that (IMHO) would depend entirely on the load so I think
>  it is an engineering question.  Since /64 prefixes are abundant,
>  it would be trivial to have as many SAMPLE servers as you
>  need for the load.
>  
>  > If SIMPLE servers are stateless, would anycast
>  > address be used for avalability and load-balancing?
>  
>  Personally, I think that is complication with no value.
>  If the SIMPLE server is colocated with another single point
>  of failure such as the first hop router for a large group
>  of subscribers, I don't see why you would worry about
>  load balancing and availability.
>  
>  > How does the ISP provision the IP address and port of
>  > SIMPLE servers to the hosts behind the IPv4-only CPEs?
>  
>  That doesn't change; they are still provisioned for IPv4
>  exactly as they are today. The IPv4 service is not changed
>  in any way.
>  
>  > If SIMPLE servers are stateless, I assume the multicast
>  > capability would be absent, right?
>  
>  As described so far, SIMPLE is just the same as Teredo and
>  6to4 as far as multicast goes.
>  
>  Regards,
>       Brian
>  
>  > 
>  > Thanks,
>  > washam
>  > ----- Original Message -----
>  > From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>  > Date: Tuesday, June 8, 2010 0:26 am
>  > Subject: [Softwires] [Fwd: I-D Action:draft-carpenter-softwire-sample-00.txt]
>  > To: softwires@ietf.org
>  > 
>  > 
>  >> Hi,
>  >>  
>  >>  This is another approach to stateless tunnels across subscriber NATs.
>  >>  We've posted it in a preliminary form so that people can compare 
> it with
>  >>  the SAM-based proposal presented in Anaheim and with draft-lee-softwire-6rd-udp.
>  >>  
>  >>      Brian + Sheng
>  >>  
>  >>  -------- Original Message --------
>  >>  Subject: I-D Action:draft-carpenter-softwire-sample-00.txt
>  >>  Date: Mon,  7 Jun 2010 00:30:02 -0700 (PDT)
>  >>  From: Internet-Drafts@ietf.org
>  >>  Reply-To: internet-drafts@ietf.org
>  >>  To: i-d-announce@ietf.org
>  >>  
>  >>  A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
>  >>  
>  >>  	Title           : Legacy NAT Traversal for IPv6: Simple Address 
> 
>  >> Mapping for Premises Legacy Equipment (SAMPLE)
>  >>  	Author(s)       : B. Carpenter, S. Jiang
>  >>  	Filename        : draft-carpenter-softwire-sample-00.txt
>  >>  	Pages           : 9
>  >>  	Date            : 2010-06-07
>  >>  
>  >>  IPv6 deployment is delayed by the existence of millions of subscriber
>  >>  network address translators (NATs) that cannot be upgraded to support
>  >>  IPv6.  This document specifies a mechanism for traversal of such
>  >>  NATs.  It is based on an address mapping and on a mechanism whereby
>  >>  suitably upgraded hosts behind a NAT may obtain IPv6 connectivity 
> via
>  >>  a stateless server, known as a SAMPLE server, operated by their
>  >>  Internet Service Provider.  SAMPLE is an alternative to the Teredo
>  >>  protocol.
>  >>  
>  >>  A URL for this Internet-Draft is:
>  >>  http://www.ietf.org/internet-drafts/draft-carpenter-softwire-sample-00.txt
>  >>  
>  >>  
>  >>  
>  >>  _______________________________________________
>  >>  Softwires mailing list
>  >>  Softwires@ietf.org
>  >>  https://www.ietf.org/mailman/listinfo/softwires
>  >>  
>  > 
>  