+1
it’s been deployed for several years and very stable (and simple to work with).
I support this going to last call.



On Jan 29, 2015, at 11:12 AM, Lori Jakab <[email protected]> wrote:

> On 01/24/2015 12:39 AM, Fabio Maino wrote:
>> Agree. It was recently refreshed from expiration, and I believe it's
>> ready for last call.
> 
> +1
> 
> There are several implementations, that have been thoroughly tested for
> interoperability, so I support this document going into working group
> last call.
> 
> -Lori
> 
>> 
>> Fabio
>> 
>> On 1/23/15 9:25 AM, Dino Farinacci wrote:
>>> I would like to ask the working group if there are any issues with
>>> draft-ietf-lisp-ddt-02 and if there is any reason to not send this
>>> document for working group last call?
>>> 
>>> It has been around for a while, has good implementation and deployment
>>> support and hasn't been presented in a working group meeting for a while.
>>> 
>>> Dino
>>> _______________________________________________
>>> lisp mailing list
>>> [email protected]
>>> https://www.ietf.org/mailman/listinfo/lisp
>> 
>> _______________________________________________
>> lisp mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/lisp
> 
> _______________________________________________
> lisp mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/lisp

Best regards,
Gregg

--------------------------------------------------------------------
.:|:.:|:. | gregg schudel (ccie#9591) LISP technical marketing engr
  cisco   | mobile: +1 571 332 2222   email: [email protected]
--------------------------------------------------------------------
cisco corporate legal statement: 
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
--------------------------------------------------------------------

_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp

Reply via email to