Opened 8 years ago

Last modified 8 years ago

#214 new defect

Should gateways figure things out completely or just punt endpoints to a closer gateway?

Reported by: yaronf.ietf@… Owned by: draft-ietf-ipsecme-p2p-vpn-problem@…
Priority: normal Milestone:
Component: p2p-vpn-problem Severity: -
Keywords: Cc:

Description

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.

Change History (2)

comment:1 Changed 8 years ago by yaronf.ietf@…

  • Component changed from draft-ietf-ipsecme-ikev2bis to p2p-vpn-problem
  • Owner changed from paul.hoffman@… to draft-ietf-ipsecme-p2p-vpn-problem@…

comment:2 Changed 8 years ago by mcr@…

  A                                                        B
   \                                                      /
    \                                                    /
     \                                                  /
      +----+    trunk1    +------+    trunk2     +-----+
      | H1 |==============|  H2  |===============|  H3 |
      +----+              +------+               +-----+
     /                            \
    /                              \
   C                                D


Leaf A has traffic of leaf B.  It would otherwise go via Hub1(H1), Hub2,
and Hub3.

Thanks to our new Private Elastic Cloud On-Demand (PECOD) protocol,
magic will happen.  The question, *AT THE REQUIREMENTS* phase, is
whether a solution such as:

step1, H1 tells A that H2 is closer:

  A                                                        B
   \                                                      /
    \.....................                               /
     \                    \                             /
      +----+    trunk1    +------+    trunk2     +-----+
      | H1 |==============|  H2  |===============|  H3 |
      +----+              +------+               +-----+
     /                            \
    /                              \
   C                                D


step2, H2 tells A where H3 is:

  A                                                        B
   \............................................          /
    \.....................                      \        /
     \                    \                      \      /
      +----+    trunk1    +------+    trunk2     +-----+
      | H1 |==============|  H2  |===============|  H3 |
      +----+              +------+               +-----+
     /                            \
    /                              \
   C                                D

step3, H3 tells A where B is:

  A........................................................B
   \............................................          /
    \.....................                      \        /
     \                    \                      \      /
      +----+    trunk1    +------+    trunk2     +-----+
      | H1 |==============|  H2  |===============|  H3 |
      +----+              +------+               +-----+
     /                            \
    /                              \
   C                                D


Version 1, edited 8 years ago by mcr@… (previous) (next) (diff)
Note: See TracTickets for help on using tickets.