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

Re: [lisp] Consensus? EID and RLOC use of the same address = separate namespace

From: Dino Farinacci <dino at cisco.com>
To: Robin Whittle <rw at firstpr.com.au>
Cc: lisp at ietf.org
Date: Wed, 25 Mar 2009 19:09:59 -0700
In-reply-to: <49CAE11C.80802 at firstpr.com.au>
References: <c9e.4a4f53ae.36fbe0e4 at aol.com> <tsl63hx9o1s.fsf at mit.edu> <49CAE11C.80802 at firstpr.com.au>

           Dino, Vince, David and Darrel:  You wrote draft-
              farinacci-lisp.  Can you comment on this debate?


No, I won't. I would rather work on more important problems.

I will keep this simple:

An EID is a 32-bit address used for socket-id identification in hosts.It is also an interface ID since the host can be multi-homed andattached to the subnets the IGP is routing within the site. An EID isnot injected into BGP routing towards the core.

An RLOC is the PA IP address assigned to the CE/PE interface of theLISP router that resides at the site.


With all due respect, can we move on?

Dino

Follow-Ups:
- Re: [lisp] Consensus? EID and RLOC use of the same address = separate namespace
  - From: Robin Whittle

References:
- Re: [lisp] Consensus? EID and RLOC use of the same address = separate namespa...
  - From: HeinerHummel
- Re: [lisp] Consensus? EID and RLOC use of the same address = separate namespa...
  - From: Sam Hartman
- Re: [lisp] Consensus? EID and RLOC use of the same address = separate namespace
  - From: Robin Whittle

Prev by Date: Re: [lisp] Consensus? EID and RLOC use of the same address = separate namespace
Next by Date: Re: [lisp] Consensus? EID and RLOC use of the same address = separate namespace
Previous by thread: Re: [lisp] Consensus? EID and RLOC use of the same address = separate namespace
Next by thread: Re: [lisp] Consensus? EID and RLOC use of the same address = separate namespace
Index(es):
- Date
- Thread

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