Hi Steve, This is unclear to me. Isn't it routing that we send a packet across to a closer gateway/ router? What does everything mean in the question below?
If we are talking about say security and routing, I think that is true. The "logical" gateway (could be multiple interactions and devices) should be able to provide the functionality. Thanks, Vishwas On Tue, Mar 20, 2012 at 6:33 PM, Stephen Hanna <sha...@juniper.net> wrote: > Please comment on Suggested Resolution. Note that Yaron has > already supplied his comment below. > > Steve > > -----Original Message----- > From: ipsecme issue tracker [mailto:t...@tools.ietf.org] > Sent: Tuesday, March 20, 2012 6:59 PM > To: yaronf.i...@gmail.com; > draft-ietf-ipsecme-p2p-vpn-prob...@tools.ietf.org > Subject: [ipsecme] #214: Should gateways figure things out completely or > just punt endpoints to a closer gateway? > > #214: Should gateways figure things out completely or just punt endpoints > to a > closer gateway? > > Suggested Resolution: We should not specify this in the problem statement. > It should be specified in the solution. > > YS: sounds like a requirements-level question to me. > > -- > -------------------------+------------------------------------------------- > Reporter: | Owner: draft-ietf-ipsecme-p2p-vpn- > yaronf.ietf@… | problem@… > Type: defect | Status: new > Priority: normal | Milestone: > Component: p2p-vpn- | Severity: - > problem | Keywords: > Resolution: | > -------------------------+------------------------------------------------- > > Ticket URL: < > http://trac.tools.ietf.org/wg/ipsecme/trac/ticket/214#comment:1> > ipsecme <http://tools.ietf.org/ipsecme/> > > _______________________________________________ > IPsec mailing list > IPsec@ietf.org > https://www.ietf.org/mailman/listinfo/ipsec >
_______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
