Opened 9 years ago

Closed 8 years ago

#45 closed technical (fixed)

LISP vs. Existing (from Y. 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 NAT?

Change History (6)

comment:1 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:2 Changed 9 years ago by luigi@…

  • Status changed from resolved to closed

comment:3 Changed 9 years ago by yakov@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

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

comment:4 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 how sites use NAT at length.

Note that I did not ask "to discuss how sites use NAT at length" - I asked to document the benefits that LISP could offer to sites that use NAT. 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:5 Changed 8 years ago by terry.manderson@…

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

As a protocol definition in a document with experimental status we do not believe, as chairs, that

it needs to outline the benefits that LISP may offer in NAT environments, or many other similar

technology environments.

It may be that these benefits are outlined in another informational document in the future, but
it is out of scope for draft-ietf-lisp.

comment:6 Changed 8 years ago by luigi@…

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