Opened 9 years ago

Closed 8 years ago

#34 closed editorial (fixed)

Editorial Issues Section 8 of draft-ietf-lisp-06.txt

Reported by: luigi@… Owned by:
Priority: trivial Component: draft-ietf-lisp
Severity: - Keywords:
Cc:

Description (last modified by luigi@…)

This ticket groups together editorial issues raised by D. Papadimitriou and Y. Rekhter in their respective reviews.

From D. Papadimitriou's review:

Section 8.1 first paragraph, it is not the location of the source that determines the “size” of the working set of the EID prefix-to-RLOC cache but the number of EID prefixes this “source site” has to reach. The same issue occurs at ETR, small sites may have to be configured with a large list of EID-to-RLOC mapping entries. Next to this the granularity of the EID prefix allocation is also important.

From Y. Rekhter's review:
This is part of Comment 39

By having the PE be the first router on the path to encapsulate, it
can choose a TE path first, and the ETR can decapsulate and
re-encapsulate for a tunnel to the destination end site.

This is hard to understand.

This is part of Comment 36

ISP is doing the TE, then the site has no control. Recursive tunneling
generally will result in suboptimal paths but at the benefit of
steering traffic to resource available parts of the network.

What exactly does "suboptimal" mean here?

Change History (6)

comment:1 Changed 9 years ago by luigi@…

  • Description modified (diff)
  • Summary changed from Editorial Issues Section 8 of draft-ietf-lisp-06.txt raised by Dimitri Papadimitriou in his review to Editorial Issues Section 8 of draft-ietf-lisp-06.txt

comment:2 Changed 9 years ago by luigi@…

  • Description modified (diff)

comment:3 Changed 9 years ago by luigi@…

  • Description modified (diff)

comment:4 Changed 9 years ago by luigi@…

  • Description modified (diff)

comment:5 Changed 8 years ago by luigi@…

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

Text has been modified to fix the issue.

comment:6 Changed 8 years ago by luigi@…

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