[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers



>>>>> "Darrel" == Darrel Lewis (darlewis) <darlewis at cisco.com> writes:

    >> 
    >> I am not saying there isn't a viable business model for PETRs.
    >> I am just saying that I don't know what the business model is
    >> for PETRs and that I think that at least one seemingly viable
    >> model should be proposed before the whole PETR concept is
    >> accepted.
    >> 
    >> 
    >> 

Here is a simple one.  A provider wants to advertise that it allows for
    Darrel> IPv6 connectivity, but it does not have equipment in the
    Darrel> access network that supports v6 natively.  So it offers a
    Darrel> v6 service that includes a CPE device that runs LISP, and
    Darrel> some PETRs for those CPE's to use when accessing non-LISP
    Darrel> sites.  IPv6 packets sent from the hosts at the site are
    Darrel> encapsulated in v4 and sent over the access network that
    Darrel> does not support v6.

Speaking as an individual, I'd like to find deployment models f
Speaking as an individual, this deployment model has two problems:

1) The IETF already has other solutinos in that space with a lot more
successful deployment than LISP (6to4, Teredo, probably even 6rd).

2) This deployment model does not actually get to the deployment we
need.

As I understand it, for interworking to be useful, we need to get to a
point where everyone using LISP either

A) Is on a link that can loosen URPF

or
B)  has a PETR they can use.

So, you need to show that there are sufficient insentives to make
PETRs available to all lisp sites on access networks that are going to
enforce URPF.  Combining with v6 deployment doesn't really seem to
help this much.

I can see insentives for whomever is selling you your EID to make a
PETR available to you, but unless you are going to end up tied to a
single ISP, I don't see why they will be in a position to make a PETR
available close to you.

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.