Re: [lisp] draft-ietf-lisp-introduction-05 - EID/RLOC Syntax

[Dino Farinacci <[e-mail]>]

> 1) Is it a requirement for LISP packets to be routable over the Internet?

Well yes if you want them to get to an ETR. 

>    - If so, doesn't the outer header have to be IP?

Not if you are trying to move packets from ITR to ETR via a layer-2 bridged network or  layer-2 MPLS network. 

>    - If so, doesn't the RLOC have to be an IP address?
> 
> 2) If the LISP payload is IPv4 or IPv6:
>    - Does the EID have to be 32 or 128 bits

Yes because it arrives at the ITR in either an IPv4 or IPv6 packet. 

>    - If so, how is it "syntactically different" from an IP address

It's not. But your line of questioning is both obvious and confusing. 

>    - If not, how can the outer header be either IPv4 or IPv6
> 
> 3) Does the LISP payload have to be IP?
>    - If not, what protocols are allowed
>    - If not, how does the ETR know what protocol the payload is? The LISP header doesn't contain a protocol id or ethertype

Can you ask a specific question please?

If two hosts are going to talk to each other they need to use the same protocol. So the EID is relative to that protocol's address format. 

When those packets are encapsulated by an ITR to the ETR over a core network the ITR, ETR, and the vote network use the same protocol. So the RLOC address is relative to that protocol's address format. 

The inner and outer header can be any packet format. So the LISP mapping database could support the transport of  AppleTalk packets between hosts over an IPX core network between xTRs. 

Dino