It was pointed out to the document authors privately that a locally
caching Map Server, as mentioned in the penultimate bullet of Section
2.3, is not something that we should recommend anymore.
We, the authors agree, and want to note that the concept of a "locally
caching Map Server" was introduced into the document at the time when
DDT was still being in design phase, with many of its properties being
inspired by DNS. As a result, we removed the sentence that read "To
lower the impact, the site could use a local caching Map Resolver." in
revision -09 of the document, which we just posted to the datatracker.
On behalf of the authors,
-Lorand Jakab
On 7/1/13 7:03 PM, The IESG wrote:
The IESG has received a request from the Locator/ID Separation Protocol
WG (lisp) to consider the following document:
- 'LISP Network Element Deployment Considerations'
<draft-ietf-lisp-deployment-08.txt> as Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2013-07-15. Exceptionally, comments
may be
sent to iesg(_at_)ietf(_dot_)org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.
Abstract
This document discusses the different scenarios for the deployment of
the new network elements introduced by the Locator/Identifier
Separation Protocol (LISP).
The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-lisp-deployment/
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-lisp-deployment/ballot/
No IPR declarations have been submitted directly on this I-D.