Opened 9 years ago

Closed 8 years ago

#82 closed editorial (fixed)

Wording in Abstract (comment 8 and 44 reported by Y. Rekhter)

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

Description

The first sentence says LISP is "simple". Yet such components of LISP as the additional aspects of MTU and fragmentation, cache management and reachability management add considerable complexity, not to mention the operational expense of learning to operate and debug an entirely new infrastructure.

Change History (4)

comment:1 Changed 9 years ago by wmhaddad@…

  • Summary changed from Wording in Abstract (comment 8 reported by Y. Rekhter) to Wording in Abstract (comment 8 and 44 reported by Y. Rekhter)

comment:2 Changed 8 years ago by yakov@…

There are still few places in the draft that make unsubstantiated claims on the topic of being "simple". To remove these claims I would propose the following changes:

  1. Section 5. Delete "simple" from the following sentence "These two simple existing schemes are detailed in Section 5.4.
  1. Section 5.4. Delete "simple" from the following sentence "This section proposes two simple mechanisms to deal with packets that exceed the path MTU between the ITR and ETR."
  1. Section 6.3.1 Delete "simple" from the following sentence "When data flows bidirectionally between locators from different sites, a simple mechanism called "nonce echoing" can be used to determine reachability between an ITR and ETR."

comment:3 Changed 8 years ago by terry.manderson@…

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

This has been addressed as of -11. The raised wording no longer appears.

comment:4 Changed 8 years ago by terry.manderson@…

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