Re: [lisp] WG Last Call for LISP-SEC (draft-ietf-lisp-sec-17.txt)

[Luigi Iannone]

All,

WGLC for this document is now over.

No further comments have been received.

Thanks for the help and comments provided.

I will prepare the writeup of this document so that we can ask publication.

Thanks

Ciao

L.


> On 20 Nov 2019, at 03:47, Luigi Iannone  wrote:
> 
> All,
> 
> the LISP-Sec document has been in WG Last Call state for a long time.
> This was due to the comments that have been provided.
> We did not receive any further comment recently.
> 
> As such the this last call will be closed in one week time.
> 
> Please have a look for the latest changes.
> 
> Thanks
> 
> Ciao
> 
> L.
> 
> 
> 
> 
>> On 28 Jan 2019, at 21:29, Luigi Iannone > > wrote:
>> 
>> Hi All,
>> 
>> since work on bis documents is re-starting to move forward it is about time 
>> to move forward other pieces of the LISP ecosystem.
>> 
>> As such the LISP Security document has been revised a while ago for two 
>> reason:
>> - Make sure is PS quality 
>> - Make sure it is compliant with latest changes in the bis documents. 
>> 
>> The second point has been re-checked by the authors just last week, and 
>> seems we are ready to move the document forward.
>> 
>> This email open the usual two weeks Working Group Last Call, to end February 
>> 11th, 2019.
>> 
>> 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 LISP-SEC (draft-ietf-lisp-sec-17.txt)

[mohamed.boucadair]

Hi Luigi, all,

-19 looks good to me.

Fabio addressed my WGLC comments 
(https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-lisp-sec-17-rev%20Med.pdf).

Cheers,
Med

De : lisp [mailto:lisp-boun...@ietf.org] De la part de Luigi Iannone
Envoyé : mercredi 20 novembre 2019 03:47
À : lisp@ietf.org list
Cc : lisp-cha...@ietf.org
Objet : Re: [lisp] WG Last Call for LISP-SEC (draft-ietf-lisp-sec-17.txt)

All,

the LISP-Sec document has been in WG Last Call state for a long time.
This was due to the comments that have been provided.
We did not receive any further comment recently.

As such the this last call will be closed in one week time.

Please have a look for the latest changes.

Thanks

Ciao

L.





On 28 Jan 2019, at 21:29, Luigi Iannone mailto:g...@gigix.net>> 
wrote:

Hi All,

since work on bis documents is re-starting to move forward it is about time to 
move forward other pieces of the LISP ecosystem.

As such the LISP Security document has been revised a while ago for two reason:
- Make sure is PS quality
- Make sure it is compliant with latest changes in the bis documents.

The second point has been re-checked by the authors just last week, and seems 
we are ready to move the document forward.

This email open the usual two weeks Working Group Last Call, to end February 
11th, 2019.

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 LISP-SEC (draft-ietf-lisp-sec-17.txt)

[Luigi Iannone]

All,

the LISP-Sec document has been in WG Last Call state for a long time.
This was due to the comments that have been provided.
We did not receive any further comment recently.

As such the this last call will be closed in one week time.

Please have a look for the latest changes.

Thanks

Ciao

L.




> On 28 Jan 2019, at 21:29, Luigi Iannone  wrote:
> 
> Hi All,
> 
> since work on bis documents is re-starting to move forward it is about time 
> to move forward other pieces of the LISP ecosystem.
> 
> As such the LISP Security document has been revised a while ago for two 
> reason:
> - Make sure is PS quality 
> - Make sure it is compliant with latest changes in the bis documents. 
> 
> The second point has been re-checked by the authors just last week, and seems 
> we are ready to move the document forward.
> 
> This email open the usual two weeks Working Group Last Call, to end February 
> 11th, 2019.
> 
> 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 LISP-SEC (draft-ietf-lisp-sec-17.txt)

[Fabio Maino (fmaino)]

Hi Mohamed,
Thanks again for your comments.

They should be addressed by rev -18.

See my previous message to the list for the details.

Thanks,
Fabio

From: lisp  on behalf of "mohamed.boucad...@orange.com" 

Date: Monday, January 28, 2019 at 11:50 PM
To: Luigi Iannone , "lisp@ietf.org list" 
Cc: "lisp-cha...@ietf.org" 
Subject: Re: [lisp] WG Last Call for LISP-SEC (draft-ietf-lisp-sec-17.txt)

Hi Luigi, all,

FWIW, please find some comments to this document at :


  *   pdf: 
https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-lisp-sec-17-rev%20Med.pdf
  *   doc: 
https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-lisp-sec-17-rev%20Med.doc

These are easy to fix.

Cheers,
Med

De : lisp [mailto:lisp-boun...@ietf.org] De la part de Luigi Iannone
Envoyé : lundi 28 janvier 2019 14:30
À : lisp@ietf.org list
Cc : lisp-cha...@ietf.org
Objet : [lisp] WG Last Call for LISP-SEC (draft-ietf-lisp-sec-17.txt)

Hi All,

since work on bis documents is re-starting to move forward it is about time to 
move forward other pieces of the LISP ecosystem.

As such the LISP Security document has been revised a while ago for two reason:
- Make sure is PS quality
- Make sure it is compliant with latest changes in the bis documents.

The second point has been re-checked by the authors just last week, and seems 
we are ready to move the document forward.

This email open the usual two weeks Working Group Last Call, to end February 
11th, 2019.

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 LISP-SEC (draft-ietf-lisp-sec-17.txt)

[Alberto Rodriguez-Natal]

Luigi, all,

I support handing this to the AD as soon as the few remaining open comments
on this document coming from the review of 6833/30bis are closed.

Thanks,
Alberto

On Tue, Feb 19, 2019 at 5:01 AM Luigi Iannone  wrote:

> Folks,
>
> this WG Last Call has been out for a while and we did not receive
> substantial feedback.
>
> Note that following the discussion on the main specs (the two bis
> documents) LISP-SEC is supposed to be MTI - Mandatory To Implement.
>
> Please send your support gif you want to see this happening.
>
> Ciao
>
> L.
>
>
> On 28 Jan 2019, at 14:29, Luigi Iannone  wrote:
>
> Hi All,
>
> since work on bis documents is re-starting to move forward it is about
> time to move forward other pieces of the LISP ecosystem.
>
> As such the LISP Security document has been revised a while ago for two
> reason:
> - Make sure is PS quality
> - Make sure it is compliant with latest changes in the bis documents.
>
> The second point has been re-checked by the authors just last week, and
> seems we are ready to move the document forward.
>
> This email open the usual two weeks Working Group Last Call, to end
> February 11th, 2019.
>
> 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] WG Last Call for LISP-SEC (draft-ietf-lisp-sec-17.txt)

[Dino Farinacci]

I have one comment that will help address the SECDIR comments to RFC6833bis. So 
I request this change to be made in Section 5.4 “ITR Processing”:



Add this paragraph after the above paragraph:

If the ITR receives a Map-Reply without the S-bit set, meaning the Map-Reply 
does not include an EID-AD and PKT-AD,  it should not cache the EID-prefix and 
RLOC-set from the Map-Reply. It should store state for the EID-prefix from the 
Map-Reply noting to send a Map-Request at a later time. The rate-limiting 
procedures for when and how often to resend the Map-Request should follow the 
procedures in RFC 6833bis.

Dino


> On Feb 19, 2019, at 5:01 AM, Luigi Iannone  wrote:
> 
> Folks,
> 
> this WG Last Call has been out for a while and we did not receive substantial 
> feedback.
> 
> Note that following the discussion on the main specs (the two bis documents) 
> LISP-SEC is supposed to be MTI - Mandatory To Implement.
> 
> Please send your support gif you want to see this happening.
> 
> Ciao
> 
> L.
> 
> 
>> On 28 Jan 2019, at 14:29, Luigi Iannone  wrote:
>> 
>> Hi All,
>> 
>> since work on bis documents is re-starting to move forward it is about time 
>> to move forward other pieces of the LISP ecosystem.
>> 
>> As such the LISP Security document has been revised a while ago for two 
>> reason:
>> - Make sure is PS quality 
>> - Make sure it is compliant with latest changes in the bis documents. 
>> 
>> The second point has been re-checked by the authors just last week, and 
>> seems we are ready to move the document forward.
>> 
>> This email open the usual two weeks Working Group Last Call, to end February 
>> 11th, 2019.
>> 
>> 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] WG Last Call for LISP-SEC (draft-ietf-lisp-sec-17.txt)

[mohamed.boucadair]

Hi Luigi, all,

FWIW, please find some comments to this document at :


· pdf: 
https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-lisp-sec-17-rev%20Med.pdf

· doc: 
https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-lisp-sec-17-rev%20Med.doc

These are easy to fix.

Cheers,
Med

De : lisp [mailto:lisp-boun...@ietf.org] De la part de Luigi Iannone
Envoyé : lundi 28 janvier 2019 14:30
À : lisp@ietf.org list
Cc : lisp-cha...@ietf.org
Objet : [lisp] WG Last Call for LISP-SEC (draft-ietf-lisp-sec-17.txt)

Hi All,

since work on bis documents is re-starting to move forward it is about time to 
move forward other pieces of the LISP ecosystem.

As such the LISP Security document has been revised a while ago for two reason:
- Make sure is PS quality
- Make sure it is compliant with latest changes in the bis documents.

The second point has been re-checked by the authors just last week, and seems 
we are ready to move the document forward.

This email open the usual two weeks Working Group Last Call, to end February 
11th, 2019.

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