Re: [lisp] draft-ietf-lisp-introduction-05

Hi Joel

> Would it help if we said that EIDs or RLOCs may use syntaxes associated with
> other address families?
>

What about this (second paragraph section 2.4.1)?

Typical mappings in LISP bind EIDs in the form of IP prefixes with
a set of RLOCs, also in the form of IPs.  IPv4 and IPv6 addresses are
encoded using the appropriate Address Family Identifier (AFI)
[RFC3232]. However LISP also supports more general syntaxes associated
with other address families by means of LISP Canonical Address Format (LCAF)
[I-D.ietf-lisp-lcaf].

Albert

> Yours,
> Joel
>
>
> On 10/11/14, 10:15 PM, Ronald Bonica wrote:
>>
>> Dino,
>>
>> The very first page of the Intro document says that RLOCs and EIDs can be
>> syntactically different from IP addresses. However, it leaves the reader to
>> guess what this means. So, I need to ask 20 seemingly obvious questions to
>> ferret out the actually meaning. Believe me, it is as painful to me as it is
>> to you!
>>
>> What does it mean to be "syntactically different" from an IP address? If
>> you can explain that, we won't have to play 20 questions.
>>
>>
>> Ron
>>
>>
>>
>>> -----Original Message-----
>>> From: Dino Farinacci [mailto:farinacci@gmail.com]
>>> Sent: Saturday, October 11, 2014 9:42 PM
>>> To: Ronald Bonica
>>> Cc: Joel M. Halpern; lisp@ietf.org
>>> Subject: Re: [lisp] draft-ietf-lisp-introduction-05 - EID/RLOC Syntax
>>>
>>>> 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
>
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp