Opened 9 years ago

Closed 8 years ago

#95 closed editorial (fixed)

On eliminating vs. deferring mapping lookup (comment 15 reported by Y. Rekhter)

Reported by: wmhaddad@… Owned by:
Priority: minor Component: draft-ietf-lisp
Severity: - Keywords:


Section 4.1:

In order to eliminate the need for a mapping lookup in the reverse
direction, an ETR MAY create a cache entry that maps the source EID
(inner header source IP address) to the source RLOC (outer header
source IP address) in a received LISP packet. Such a cache entry is
termed a "gleaned" mapping and only contains a single RLOC for the
EID in question. More complete information about additional RLOCs
SHOULD be verified by sending a LISP Map-Request for that EID.

The last sentence in the quote contradicts the first sentence. The mapping lookup is not eliminated, but merely deferred.

Change History (3)

comment:1 Changed 9 years ago by terry.manderson@…

  • Priority changed from major to minor
  • Type changed from technical to editorial

comment:2 Changed 8 years ago by luigi@…

  • Resolution set to fixed
  • Status changed from new to resolved

The issue has been fixed in version -12 of the draft as described in section B.1:

  • Tracker item 95. Change "eliminate" to "defer" in section 4.1.

comment:3 Changed 8 years ago by luigi@…

  • Status changed from resolved to closed
Note: See TracTickets for help on using tickets.