Subject: [lisp] Issue Title (number): LISP for inbound TE (113)

From: Darrel Lewis <[email-masked]>
Date: Tue, 20 Jul 2010 15:14:27 -0700

Issue Title (number): LISP for inbound TE (113)
Draft Section: 2, also 6.2
Issue Description: Inbound Traffic Engineering
Comments:

From Section 2:

   4. Traffic engineering capabilities that can be performed by network elements and do not depend on injecting additional state into the routing system. This will fall out of the mechanism that is use to implement the EID/RLOC split (see Section 4). 

What is described in Section 4 is the use of LISP for outbound/forward traffic engineering. There is nothing in Section 4 that describes how LISP could be used to support inbound/return traffic engineering.Either (a) the draft should add specific details on how LISP supports inbound/return traffic engineering, or (b) the draft has to explicitly state that LISP support for traffic engineering is limited to the outbound/forward traffic only.

Response:

Dear Yakov-

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. The authors feel that section 6.2 on RLOC selection give a detailed example on how an ETR can specify a site's ingress TE policy.  Please feel free to continue discussion of your issue on the LISP working group mailing list, [email-masked]. Should discussion result in WG consensus that changes are required, the authors will incorporate
appropriate text into a future version of the draft.

	Thanks!
	Darrel, for the LISP document authors