Ted, 

Thanks for the comments and reply. 

Again, the draft is not about building one large Layer 2.

The proposed proxy gateway is to enable subnets not to be restricted physically 
together, i.e. allowing the gateway nodes in one access domain to be the "proxy 
gateway" for all the hosts attached regardless those hosts' subnets. 

The draft is allow all the hosts attached to one "gateway" to be represented by 
this gateway, very much like today's router represent all the hosts attached.   
 


As for L2 NAT mentioned in the draft, there are issues and the benefits. The 
benefits have been documented in the draft and many of our emails. The issues 
need to be addressed. That is why we would like the WG to contribute. 

There are a lot of issues with L3 NAT too, but L3 NAT is one of the key 
components that make today's internet scale. 



Linda

> -----Original Message-----
> From: int-area-boun...@ietf.org [mailto:int-area-boun...@ietf.org] On
> Behalf Of Ted Lemon
> Sent: Friday, September 27, 2013 3:45 PM
> To: David Allan I
> Cc: int-area@ietf.org
> Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.txt
> 
> On Sep 27, 2013, at 4:40 PM, David Allan I <david.i.al...@ericsson.com>
> wrote:
> > Although the list discussion around my comments was an interesting
> and informative one, I did not consider my concerns addressed. An L3
> ARP proxy driving a 1:N MAC-NAT breaks a lot of stuff. IMO that is
> rather fundamental and more discussion would not change the facts. In
> that regard I cannot see how my concerns can be addressed by SARP as it
> stands...
> 
> I realize that for the people presenting these points it is obvious why
> a L2 nat is a bad idea, and I think I know at least one reason why they
> feel this way, but it would help to actually walk the working group
> through it rather than just pointing out that it is so, because I
> suspect that there are plenty of working group participants who are not
> experts on the topic, but would understand readily if the concerns were
> explained in more detail.
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area

Reply via email to