Opened 10 years ago

Closed 9 years ago

#4 closed technical (invalid)

LISP errors

Reported by: "Templin, Fred L" <Fred.L.Templin@…> Owned by:
Priority: major Component: draft-ietf-lisp
Severity: - Keywords:


Chair Note

Fred opened this issue before the issue tracker was available. Discussion on the list suggested that Fred's original conception might not have WG consensus, but the general problem of when LISP should send errors and how this should be done definitely is an open issue.

Original Description

In addition to errors that may occur along the path from
the ITE to the ETE *before* decapsulation and errors that
may occur along the path from the ETE to the final
destination *after* decapsulation, errors may also occur
*during* decapsulation. An example is what if the ETR
decapsulates the outer IP header, but the inner IP stack
is not configured? (Answer is that the ITR should receive
an error by which it can ascertain that this ETR is having
trouble, and should start using a different ETR instead.)

Change History (2)

comment:1 Changed 9 years ago by jmh@…

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

If there are specific error cases that need to be covered, an issued should be raised describing the problem. The IETf does not generally expect the specification to describe the handling of all possible implementation errors.

comment:2 Changed 9 years ago by luigi@…

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