DDT went already through WG last call. 

We are waiting an update fixing editorial issues that I spotted as shepherd of 
the document.

Once this step is done, the document will go forward.

ciao

L. 

> On 22 Apr 2016, at 23:07, Dino Farinacci <[email protected]> wrote:
> 
> And the same for LISP-DDT. Can I request last call for it?
> 
> Dino
> 
> On Apr 22, 2016, at 1:55 PM, Fabio Maino <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>> This draft has been around for quite some time, and went through multiple 
>> reviews and editing cycles. 
>> 
>> I support handing it to the AD. 
>> 
>> Thanks,
>> Fabio
>> 
>> On 4/8/16 6:27 AM, Luigi Iannone wrote:
>>> Hi All,
>>> 
>>> During our meeting yesterday, the authors of the LISP LCAF document  
>>> [https://tools.ietf.org/html/draft-ietf-lisp-lcaf-12 
>>> <https://tools.ietf.org/html/draft-ietf-lisp-lcaf-12>]
>>> asked for Last Call. The room showed consensus and no objections were 
>>> raised.
>>> 
>>> This email starts the usual two weeks WG Last Call, to end April 22nd, 2016.
>>> 
>>> Please review this WG document and let the WG know if you agree that it is 
>>> ready for handing to the AD.
>>> If you have objections, please state your reasons why, and explain what it 
>>> would take to address your concerns.
>>> 
>>> Thanks
>>> 
>>> Luigi & Joel
>>> 
>>> 
>>> _______________________________________________
>>> lisp mailing list
>>> [email protected] <mailto:[email protected]>
>>> https://www.ietf.org/mailman/listinfo/lisp 
>>> <https://www.ietf.org/mailman/listinfo/lisp>
>> 
>> _______________________________________________
>> lisp mailing list
>> [email protected] <mailto:[email protected]>
>> https://www.ietf.org/mailman/listinfo/lisp 
>> <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

Reply via email to