Opened 9 years ago

Closed 9 years ago

#44 closed technical (fixed)

LISP vs existing (reported by Yakov Rekhter)

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

Description

What LISP offers to audiences which are already using PI?

Change History (8)

comment:1 Changed 9 years ago by wmhaddad@…

  • Owner changed from Yakov to wmhaddad@…

comment:2 Changed 9 years ago by wmhaddad@…

  • Owner wmhaddad@… deleted
  • Summary changed from LISP vs existing to LISP vs existing (reported by Yakov Rekhter)

comment:3 Changed 9 years ago by luigi@…

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

Authors replied on the mailinglist that in their opinion there is no need to make any change to the draft. Neither the original person that raised the issue nor the mailinglist stated a different opinion.

comment:4 Changed 9 years ago by luigi@…

  • Status changed from resolved to closed

comment:5 Changed 9 years ago by yakov@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

In order to close the ticket the authors need to point to the text that answers the question raised in the ticket.

comment:6 Changed 9 years ago by yakov@…

From the response I received:

Thank you for your contribution to draft-ietf-lisp-06.txt. The draft authors
have reviewed your comments but do not feel that changes to the document are
warranted at this time. In this case, this draft is an experimental protocol
specification it seems out of place to discuss the benefits of existing PI
multihoming at length.

Note that I did not ask "to discuss the benefits of existing PI multihoming at length" - I asked to document the benefits that LISP could offer to sites that use PI. If the authors think that this should be done in some other LISP WG document, then I'll be glad to hear their proposal.

comment:7 Changed 9 years ago by yakov@…

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

comment:8 Changed 9 years ago by yakov@…

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