Re: [lisp] I-D Action: draft-ietf-lisp-yang-11.txt

[Reshad Rahman (rrahman)]

- The new version addresses the comments from Dino at last IETF. 
- Also minor changes to some descriptions (s/Group /Grouping /).
- For instance-id, description says value 0 is for default VRF.

Regards,
Reshad.

On 2019-03-06, 5:48 PM, "lisp on behalf of internet-dra...@ietf.org" 
 wrote:


A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Locator/ID Separation Protocol WG of the 
IETF.

Title   : LISP YANG Model
Authors : Vina Ermagan
  Alberto Rodriguez-Natal
  Florin Coras
  Carl Moberg
  Reshad Rahman
  Albert Cabellos-Aparicio
  Fabio Maino
Filename: draft-ietf-lisp-yang-11.txt
Pages   : 77
Date: 2019-03-06

Abstract:
   This document describes a YANG data model to use with the Locator/ID
   Separation Protocol (LISP).

   The YANG modules in this document conform to the Network Management
   Datastore Architecture (NMDA).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lisp-yang/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-lisp-yang-11
https://datatracker.ietf.org/doc/html/draft-ietf-lisp-yang-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-yang-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp


--- Begin Message ---
Reshad, here are my comments. 

For every occurence of “virtual-networks” change to “vpns”.
For every occurence of “virtual-network” change to “vpn”.
For every occurence of “vni” change to “instance-id”.
For every occurence of “ni-name” change to “iid-name”.
For every occurence of “Virtual network identifier change to “VPN identifier”.
For every occurence of “Virtual networks" to “VPNs".
For every occurence of “Virtual network" to “VPN”.

Thanks,
Dino
___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

--- End Message ---
___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] Comments to draft-ietf-lisp-yang-10

[Reshad Rahman (rrahman)]

Thanks Dino. I'll discuss with the authors and will get back to you.


On 2018-11-05, 5:47 PM, "lisp on behalf of Dino Farinacci" 
 wrote:

Reshad, here are my comments. 

For every occurence of “virtual-networks” change to “vpns”.
For every occurence of “virtual-network” change to “vpn”.
For every occurence of “vni” change to “instance-id”.
For every occurence of “ni-name” change to “iid-name”.
For every occurence of “Virtual network identifier change to “VPN 
identifier”.
For every occurence of “Virtual networks" to “VPNs".
For every occurence of “Virtual network" to “VPN”.

Thanks,
Dino
___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp


___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf

[Reshad Rahman (rrahman)]

I agree that this document is ready to be handed to the AD.

From: lisp  on behalf of Luigi Iannone 
Date: Friday, July 6, 2018 at 6:09 AM
To: "lisp@ietf.org list" 
Cc: "lisp-cha...@ietf.org" 
Subject: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf

Folks,

As Alberto mentioned in a previous mail, in London there was consensus to move 
forward draft-ietf-lisp-vendor-lcaf 
[https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after the few 
fixes that I asked).

Fixes are done, hence, this email starts the usual two weeks WG Last Call, to 
end July 20th, 2018.

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
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] The LISP WG has placed draft-iannone-6834bis in state "In WG Last Call"

[Reshad Rahman (rrahman)]

Support.

Regards,
Reshad.


On 2018-05-21, 11:39 AM, "lisp on behalf of IETF Secretariat" 
 wrote:


The LISP WG has placed draft-iannone-6834bis in state
In WG Last Call (entered by Joel Halpern)

The document is available at
https://datatracker.ietf.org/doc/draft-iannone-6834bis/

Comment:
A small delta to bring RFC 6834 to proposed Standards.  Going directly to WG
last call to avoid slowing down other work, and because it is so small. 
Please do speak up, either with support or objection.

___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp


___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] WG Last Call for draft-ietf-lisp-rfc6830bis-12

[Reshad Rahman (rrahman)]

I have reviewed this document and I believe it's ready for the AD.

Regards,
Reshad.

From: lisp  on behalf of Luigi Iannone 
Date: Thursday, April 5, 2018 at 10:18 AM
To: "lisp@ietf.org list" 
Subject: [lisp] WG Last Call for draft-ietf-lisp-rfc6830bis-12

Hi All,

During our last meeting it was apparent that the work on the LISP document  
[https://tools.ietf.org/html/draft-ietf-lisp-rfc6830bis-12]
seems done and the document ready for WG Last Call.

This email starts the usual two weeks WG Last Call, to end April 20th, 2018.

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
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] WG Last Call for draft-ietf-lisp-rfc6833bis-10

[Reshad Rahman (rrahman)]

I have reviewed this document and I believe it's ready for the AD.

Regards,
Reshad.

From: lisp  on behalf of Luigi Iannone 
Date: Thursday, April 5, 2018 at 10:35 AM
To: "lisp@ietf.org list" 
Subject: [lisp] WG Last Call for draft-ietf-lisp-rfc6833bis-10

Hi All,

During our last meeting it was apparent that the work on the LISP document  
[https://tools.ietf.org/html/draft-ietf-lisp-rfc6833bis-10]
seems done and the document ready for WG Last Call.

This email starts the usual two weeks WG Last Call, to end April 20th, 2018.

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
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] The LISP WG has placed draft-rodrigueznatal-lisp-pubsub in state "Call For Adoption By WG Issued"

[Reshad Rahman (rrahman)]

I support the draft to be adopted by the WG.

Regards,
Reshad.


On 2018-04-03, 9:27 PM, "lisp on behalf of Joel M. Halpern" 
 wrote:

This was discussed in London, and the authors have requested working 
group adoption.

Please comment on whether you think this document is ready for WG 
adoption.  Which does not mean it is perfect, but rather that it is a 
good start on the problem it aims to solve.
Comments with motivation or explanation are preferred.

Silence does NOT mean consent.

This last call will last for 2 weeks.
Thank you,
Joel

On 4/3/18 9:14 PM, IETF Secretariat wrote:
> 
> The LISP WG has placed draft-rodrigueznatal-lisp-pubsub in state
> Call For Adoption By WG Issued (entered by Joel Halpern)
> 
> The document is available at
> https://datatracker.ietf.org/doc/draft-rodrigueznatal-lisp-pubsub/
> 
> Comment:
> As requested by the authors, calling for WG adoption.
> 
> ___
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
> 

___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp


___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] New name for upcoming LISP -OAM- document

[Reshad Rahman (rrahman)]

Ack.


On 2018-03-21, 8:37 AM, "Luigi Iannone"  wrote:

> 
> The cost and time we have spent on this topic has already exceeded the 
benefit.
> 

This is also consuming my patience.

During f2f meeting decision has been made. The last question was the name 
and we opened for suggestion from the mailing list.

Let’s not start again  in endless discussion. 

By Friday we settle for a name and we move on AS DECIDED. 
Not opening again for any change that will trigger discussion.

We are close to finish this part of the work, so let’s do it.

L.




___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] New name for upcoming LISP -OAM- document

[Reshad Rahman (rrahman)]

I don't have a name suggestion either, but I do find it odd having a document 
with these 3 seemingly unrelated items (mobility seems to be the odd one out). 
So I would be in favour of proposal from Albert below.

Regards,
Reshad.

On 2018-03-19, 4:53 PM, "lisp on behalf of Dino Farinacci" 
 wrote:

> The suggested name is “LISP Mobility, Deployment and Traceroute 
considerations”.
> 
> The chairs would like to hear from the mailing list if there is any 
objection or you have a better name to suggest.

I don’t have a name suggestion (for the 3 items included in one document) 
but I would like to support an idea that Albert provided after the meeting 
today. 

He suggested to put the Mobility sections in an Appendix in RFC6830bis and 
put Deployment and Traceroute considerations in a document that now can be 
called “draft-ietf-lisp-oam”.

Wonder how people would feel about that?

Dino

___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp


___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] 6830bis Review

[Reshad Rahman (rrahman)]

I also believe SMRs should be in the CP doc. I would support Dino’s  proposal 
below.

Regards,
Reshad.

On 2018-01-15, 2:10 PM, "lisp on behalf of Dino Farinacci" 
 wrote:

I’d be willing to make a deal.

SMRs go to 6833bis and RLOC-probes stay in 6830bis. Since RLOC-probes are 
connected (semantically) to echo-noncing which use bits in the LISP header.

Dino

> On Jan 15, 2018, at 10:32 AM, Alberto Rodriguez-Natal 
 wrote:
> 
> On Mon, Jan 15, 2018 at 6:55 PM, Dino Farinacci  
wrote:
>>> SMRs and RLOC-probes are control-plane features used by xTRs to be able 
to run the data-plane.
>> 
>> They are data-plane features that use control-plane messages. No other 
devices sends an RLOC-probe (or SMR) then an xTR.
> 
> IMHO I think that the SMR should go into the control-plane document. I
> believe that there are many cases (specially from an SDN point of
> view) where you may want to send SMRs from entities other than xTRs.
> 
> There's already a draft [1] that proposes that SMRs can also be sent
> by MSMRs. That draft is documenting what has been implemented and
> running on OpenDaylight for a while now.
> 
> Furthermore, lig-lispmob [2] supports sending SMRs on demand through a
> CLI without running an xTR. I've found that capability useful on many
> occasions.
> 
> Alberto
> 
> [1] https://tools.ietf.org/html/draft-rodrigueznatal-lisp-ms-smr-04
> [2] https://github.com/LISPmob/lig-lispmob

___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp


___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] Adoption call: draft-lewis-lisp-gpe-04.txt

[Reshad Rahman (rrahman)]

In favour.


On 2017-12-15, 12:15 PM, "lisp on behalf of Florin Coras" 
 wrote:

+1

Florin

> On Dec 15, 2017, at 8:40 AM, Fabio Maino  wrote:
> 
> As an author I support the adoption of this document.
> 
> This simple LISP dataplane extension enables multiprotocol support in 
LISP. It allows use of LISP in L2 overlays, and introduces the capability to 
support dataplane extensions such as Network Service Header or Group Based 
Policy.
> 
> This is bit-by-bit compatible with RFC6830bis and allows the use of 
Map-Versioning and Echo-Noncing, albeit with a reduced size of the 
corresponding dataplane metadata.
> 
> An earlier version of the draft has been implemented in the FD.io 
(http://FD.io) and OOR (https://www.openoverlayrouter.org/) open source data 
plane implementations.
> 
> Thanks,
> Fabio
> 
> 
> 
> On 12/15/17 8:23 AM, Joel Halpern wrote:
>> The authors of the lisp-gpe draft (below) have requested working group 
adoption for this document.
>> 
>> This email starts a two week last call for working group adoption of 
this document.
>> 
>> Please respond, positively or negatively.  Silence does NOT mean 
consent.  Please include explanation / motivation / reasoning for your view.
>> 
>> Also remember that this is not a last call.  Once the document is 
adopted (assuming it is), we as a working group can make changes as needed.  
The primary quesitonin this call is whether this is a good basis for work we 
want to do.
>> 
>> Thank you,
>> Joel (& Luigi)
>> 
>> 
>>  Forwarded Message 
>> Subject: I-D Action: draft-lewis-lisp-gpe-04.txt
>> Date: Fri, 15 Dec 2017 08:13:24 -0800
>> From: internet-dra...@ietf.org
>> Reply-To: internet-dra...@ietf.org
>> To: i-d-annou...@ietf.org
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
>> 
>> 
>> Title   : LISP Generic Protocol Extension
>> Authors : Darrel Lewis
>>   John Lemon
>>   Puneet Agarwal
>>   Larry Kreeger
>>   Paul Quinn
>>   Michael Smith
>>   Navindra Yadav
>>   Fabio Maino
>> Filename: draft-lewis-lisp-gpe-04.txt
>> Pages   : 8
>> Date: 2017-12-15
>> 
>> Abstract:
>>This draft describes extending the Locator/ID Separation Protocol
>>(LISP), via changes to the LISP header, to support multi-protocol
>>encapsulation.
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-lewis-lisp-gpe/
>> 
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-lewis-lisp-gpe-04
>> https://datatracker.ietf.org/doc/html/draft-lewis-lisp-gpe-04
>> 
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-lewis-lisp-gpe-04
>> 
>> 
>> Please note that it may take a couple of minutes from the time of 
submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> ___
>> I-D-Announce mailing list
>> i-d-annou...@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> 
>> ___
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
> 
> 
> ___
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp


___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] [ERRATA] Call for WG Adoption of LISP Anonymity [draft-farinacci-lisp-eid-anonymity-02.txt]

[Reshad Rahman (rrahman)]

Support WG adoption of draft-farinacci-lisp-eid-anonymity

From: lisp mailto:lisp-boun...@ietf.org>> on behalf of 
Luigi Iannone mailto:g...@gigix.net>>
Date: Wednesday, July 26, 2017 at 7:16 AM
To: LISP mailing list list mailto:lisp@ietf.org>>
Cc: "lisp-cha...@ietf.org" 
mailto:lisp-cha...@ietf.org>>
Subject: [lisp] [ERRATA] Call for WG Adoption of LISP Anonymity 
[draft-farinacci-lisp-eid-anonymity-02.txt]

The call ends August 10th 2017 !

Luigi


On 26 Jul 2017, at 11:41, Luigi Iannone mailto:g...@gigix.net>> 
wrote:

Hi All,

During the 99th IETF authors of the document 
draft-farinacci-lisp-eid-anonymity-02.txt
[https://tools.ietf.org/html/draft-farinacci-lisp-eid-anonymity-02]
asked for WG adoption. Meeting participants expressed consensus on adoption.

This message begins the two weeks call for WG adoption to confirm the meeting 
outcome.
The call ends on  August 3rd 2017.

Please respond to the LISP mailing list with any statements of approval or 
disapproval.

Recall that:

- This is not WG Last Call. The document is not final, and the WG is expected to
  modify the document's content until there is WG consensus that the content is 
solid.
  Therefore, please don't oppose adoption just because you want to see changes 
to its content.

- If you have objections to adoption of the document, please state your reasons 
why,
  and explain what it would take to address your concerns.

- If you have issues with the content, by all means raise those issues and we 
can
  begin a dialog about how best to address them.


Luigi and Joel

___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] [ERRATA] Call for WG Adoption of Vendor Specific LCAF [draft-rodrigueznatal-lisp-vendor-lcaf-00.txt]

[Reshad Rahman (rrahman)]

I support WG adoption of draft-rodrigueznatal-lisp-vendor-lcaf.

From: lisp mailto:lisp-boun...@ietf.org>> on behalf of 
Luigi Iannone mailto:g...@gigix.net>>
Date: Wednesday, July 26, 2017 at 7:16 AM
To: LISP mailing list list mailto:lisp@ietf.org>>
Cc: "lisp-cha...@ietf.org" 
mailto:lisp-cha...@ietf.org>>
Subject: [lisp] [ERRATA] Call for WG Adoption of Vendor Specific LCAF 
[draft-rodrigueznatal-lisp-vendor-lcaf-00.txt]

The call ends August 10th 2017 !

Luigi

On 26 Jul 2017, at 11:41, Luigi Iannone mailto:g...@gigix.net>> 
wrote:

Hi All,

During the 99th IETF authors of the document 
draft-rodrigueznatal-lisp-vendor-lcaf-00.txt
[https://tools.ietf.org/html/draft-rodrigueznatal-lisp-vendor-lcaf-00]
asked for WG adoption. Meeting participants expressed consensus on adoption.

This message begins the two weeks call for WG adoption to confirm the meeting 
outcome.
The call ends on  August 3rd 2017.

Please respond to the LISP mailing list with any statements of approval or 
disapproval.

Recall that:

- This is not WG Last Call. The document is not final, and the WG is expected to
  modify the document's content until there is WG consensus that the content is 
solid.
  Therefore, please don't oppose adoption just because you want to see changes 
to its content.

- If you have objections to adoption of the document, please state your reasons 
why,
  and explain what it would take to address your concerns.

- If you have issues with the content, by all means raise those issues and we 
can
  begin a dialog about how best to address them.


Luigi and Joel

___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] I-D Action: draft-ietf-lisp-yang-05.txt

[Reshad Rahman (rrahman)]

LISP WG, we are looking for comments/feedback on the LISP YANG model.


The slides which we were planning on presenting are @
https://www.ietf.org/proceedings/99/slides/slides-99-lisp-lisp-yang-model-0
0.pdf

I am now in Prague so if anyone wants to discuss f2f please send me a note.

Regards,
Reshad.


On 2017-07-03, 4:10 PM, "lisp on behalf of internet-dra...@ietf.org"
 wrote:

>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>This draft is a work item of the Locator/ID Separation Protocol of the
>IETF.
>
>Title   : LISP YANG Model
>Authors : Vina Ermagan
>  Alberto Rodriguez-Natal
>  Florin Coras
>  Carl Moberg
>  Reshad Rahman
>  Albert Cabellos-Aparicio
>  Fabio Maino
>   Filename: draft-ietf-lisp-yang-05.txt
>   Pages   : 56
>   Date: 2017-07-03
>
>Abstract:
>   This document describes a YANG data model to use with the Locator/ID
>   Separation Protocol (LISP).
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-lisp-yang/
>
>There are also htmlized versions available at:
>https://tools.ietf.org/html/draft-ietf-lisp-yang-05
>https://datatracker.ietf.org/doc/html/draft-ietf-lisp-yang-05
>
>A diff from the previous version is available at:
>https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-yang-05
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>___
>lisp mailing list
>lisp@ietf.org
>https://www.ietf.org/mailman/listinfo/lisp

___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] Call for WG Adoption of document draft-farinacci-lisp-geo-03.txt

[Reshad Rahman (rrahman)]

Support adoption.

Regards,
Reshad.



From: lisp mailto:lisp-boun...@ietf.org>> on behalf of 
Luigi Iannone mailto:g...@gigix.net>>
Date: Wednesday, June 28, 2017 at 8:03 AM
To: LISP mailing list list mailto:lisp@ietf.org>>
Cc: "lisp-cha...@ietf.org" 
mailto:lisp-cha...@ietf.org>>
Subject: [lisp] Call for WG Adoption of document draft-farinacci-lisp-geo-03.txt

Hi All,

Authors of the document draft-farinacci-lisp-geo-03.txt
[https://datatracker.ietf.org/doc/draft-farinacci-lisp-geo/]
asked for WG adoption.

This message begins the two weeks call for WG adoption.
The call ends on  July 13th 2017.

Please respond to the LISP mailing list with any statements of approval or 
disapproval.

Recall that:

- This is not WG Last Call. The document is not final, and the WG is expected to
  modify the document's content until there is WG consensus that the content is 
solid.
  Therefore, please don't oppose adoption just because you want to see changes 
to its content.

- If you have objections to adoption of the document, please state your reasons 
why,
  and explain what it would take to address your concerns.

- If you have issues with the content, by all means raise those issues and we 
can
  begin a dialog about how best to address them.


Luigi and Joel
___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] Call for WG Adoption of document draft-moreno-lisp-vpn-00.txt

[Reshad Rahman (rrahman)]

I support adoption of draft-moreno-lisp-vpn as LISP WG document.

Regards,
Reshad.

From: lisp mailto:lisp-boun...@ietf.org>> on behalf of 
Luigi Iannone mailto:g...@gigix.net>>
Date: Wednesday, April 12, 2017 at 5:29 AM
To: LISP mailing list list mailto:lisp@ietf.org>>
Cc: "lisp-cha...@ietf.org" 
mailto:lisp-cha...@ietf.org>>
Subject: [lisp] Call for WG Adoption of document draft-moreno-lisp-vpn-00.txt

Hi All,

During the 98th IETF authors of the document draft-moreno-lisp-vpn-00.txt
[https://tools.ietf.org/html/draft-moreno-lisp-vpn-00]
asked for WG adoption. Meeting participants expressed consensus on adoption.

This message begins the two weeks call for WG adoption to confirm the meeting 
outcome.
The call ends on  April 27th 2017.

Please respond to the LISP mailing list with any statements of approval or 
disapproval.

Recall that:

- This is not WG Last Call. The document is not final, and the WG is expected to
  modify the document's content until there is WG consensus that the content is 
solid.
  Therefore, please don't oppose adoption just because you want to see changes 
to its content.

- If you have objections to adoption of the document, please state your reasons 
why,
  and explain what it would take to address your concerns.

- If you have issues with the content, by all means raise those issues and we 
can
  begin a dialog about how best to address them.


Luigi and Joel
___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] Call for WG Adoption of document draft-portoles-lisp-eid-mobility-02.txt

[Reshad Rahman (rrahman)]

I support adoption of draft-portoles-lisp-eid-mobility as LISP WG document.

Regards,
Reshad.

From: lisp mailto:lisp-boun...@ietf.org>> on behalf of 
Luigi Iannone mailto:g...@gigix.net>>
Date: Wednesday, April 12, 2017 at 5:28 AM
To: LISP mailing list list mailto:lisp@ietf.org>>
Cc: "lisp-cha...@ietf.org" 
mailto:lisp-cha...@ietf.org>>
Subject: [lisp] Call for WG Adoption of document 
draft-portoles-lisp-eid-mobility-02.txt

Hi All,

During the 98th IETF authors of the document 
draft-portoles-lisp-eid-mobility-02.txt
[https://tools.ietf.org/html/draft-portoles-lisp-eid-mobility-02]
asked for WG adoption. Meeting participants expressed consensus on adoption.

This message begins the two weeks call for WG adoption to confirm the meeting 
outcome.
The call ends on  April 27th 2017.

Please respond to the LISP mailing list with any statements of approval or 
disapproval.

Recall that:

- This is not WG Last Call. The document is not final, and the WG is expected to
  modify the document's content until there is WG consensus that the content is 
solid.
  Therefore, please don't oppose adoption just because you want to see changes 
to its content.

- If you have objections to adoption of the document, please state your reasons 
why,
  and explain what it would take to address your concerns.

- If you have issues with the content, by all means raise those issues and we 
can
  begin a dialog about how best to address them.


Luigi and Joel
___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt

[Reshad Rahman (rrahman)]

I support publication of this document.

Regards,
Reshad.

From: lisp mailto:lisp-boun...@ietf.org>> on behalf of 
Florin Coras mailto:fcoras.li...@gmail.com>>
Date: Friday, December 2, 2016 at 4:26 PM
To: Luigi Iannone mailto:g...@gigix.net>>
Cc: "lisp-cha...@ietf.org" 
mailto:lisp-cha...@ietf.org>>, LISP mailing list list 
mailto:lisp@ietf.org>>
Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt

I support handing the document to the AD.

Florin

On Dec 2, 2016, at 8:50 AM, Luigi Iannone 
mailto:g...@gigix.net>> wrote:

Hi All,

feedback for this last call has been quite low. For this reason we decide to 
extend the last call for another two weeks, ending December 16th.

Please state your opinion on whether this document is ready for publication.

Silence is NOT consensus.

Ciao

Luigi & Joel

On 17 Nov 2016, at 09:36, Luigi Iannone mailto:g...@gigix.net>> 
wrote:

Hi All,

The authors of the LISP-Security (LISP-SEC) document 
[https://datatracker.ietf.org/doc/draft-ietf-lisp-sec/] asked for WG Last Call.

This email starts the usual two weeks WG Last Call, to end December  1st, 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
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] Call for adoption draft-farinacci-lisp-rfc6830bis

[Reshad Rahman (rrahman)]

Support.

From: lisp mailto:lisp-boun...@ietf.org>> on behalf of 
Luigi Iannone mailto:g...@gigix.net>>
Date: Tuesday, November 15, 2016 at 9:57 PM
To: LISP mailing list list mailto:lisp@ietf.org>>
Cc: "lisp-cha...@ietf.org" 
mailto:lisp-cha...@ietf.org>>
Subject: [lisp] Call for adoption draft-farinacci-lisp-rfc6830bis

Folks,

The chairs received a request for the following document to be
adopted as a WG item:

https://datatracker.ietf.org/doc/draft-farinacci-lisp-rfc6830bis/

Here starts a 14 day call for adoption, this call will end on
Wednesday the 30 November, 2016.

Please email the WG list stating whether or not you support acceptance.

If you email to support the acceptance of this document as a WG item, please
also indicate if you are able and willing to either contribute to, or review, 
(or both) the draft.

Sitting in silence does not indicate support, please respond appropriately.


The Chairs
Joel & Luigi
___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] Call for adoption draft-farinacci-lisp-rfc6833bis

[Reshad Rahman (rrahman)]

I support adoption. I am willing to contribute or review.

Regards,
Reshad.

From: lisp mailto:lisp-boun...@ietf.org>> on behalf of 
Luigi Iannone mailto:g...@gigix.net>>
Date: Tuesday, November 15, 2016 at 9:58 PM
To: LISP mailing list list mailto:lisp@ietf.org>>
Cc: "lisp-cha...@ietf.org" 
mailto:lisp-cha...@ietf.org>>
Subject: [lisp] Call for adoption draft-farinacci-lisp-rfc6833bis

Folks,

The chairs received a request for the following document to be
adopted as a WG item:

https://datatracker.ietf.org/doc/draft-farinacci-lisp-rfc6833bis/

Here starts a 14 day call for adoption, this call will end on
Wednesday the 30 November, 2016.

Please email the WG list stating whether or not you support acceptance.

If you email to support the acceptance of this document as a WG item, please
also indicate if you are able and willing to either contribute to, or review, 
(or both) the draft.

Sitting in silence does not indicate support, please respond appropriately.


The Chairs
Joel & Luigi
___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp