Re: [lisp] Support draft-nexagon wg adoption

[Jordi Paillissé Vilanova]

As a co-author, I support adoption because of the added functionality to 
LISP.


Jordi

El 18/11/19 a les 22:50, Bruno Fernandez-Ruiz ha escrit:

I believe the pub/sub + H3-server brokered model of communication fits 
naturally with LISP and addresses a hugely important networking requirement for 
continuously roaming mobility clients.

As such, I endorse the draft to be published as an informational RFC.

-b


On 19 Nov 2019, at 06:36, Sharon Barkai  wrote:

Hey, following very productive session today and as discussed would like to 
formally ask group for draft adoption.

Cheers,
Sharon

--szb
Cell: +972.53.2470068
WhatsApp: +1.650.492.0794
___
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] 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

[lisp] Move RFC7954 and RFC7955 to HISTORIC

[Luigi Iannone]

Folks,

as discussed yesterday during the f2f meeting, we plan to move RFC7954 and 
RFC7955 to HISTORIC state.

Rationale is described in the text provide below. This text will be associated 
to the documents so to keep track of the LISP EID prefix experiment.

Please let us know if you have any comment.

We plan to move forward in one week time.

Thanks

Ciao

L.
 




—— PROPOSED TEXT———

RFC 7954 created an experimental IPv6 prefix, namely 2001:5::/32, to be used as 
Endpoint-IDentifier (EID) space for the Locator/Identifier Separation Protocol 
(LISP).  The reserved address space was requested for an initial 3-year period
starting in September 2016 (until September 2019), with an option to extend it 
by three years (until September 2022) upon the decision of the IETF.
RFC 7955 describes a framework for the management of the prefix crested by RFC 
7954. As described in RFC 7955, RIPE NCC volunteered to provide registration 
service during the experiment (up to 2022 at latest).

The initial experiment was supposed to last three years, until September 2019.
The option to extend the experiment to three more years was subject to the 
requirements written in section 10 of RFC 7954:

 Following the policies outlined in
  [RFC5226], upon IETF Review, the decision should be made on whether
  to have a permanent EID block assignment by September 2019.  If no
  explicit action is taken or, if the IETF Review outcome is that it is
  not worth having a reserved prefix as a global EID space, the whole
  /32 will be taken out from the "IANA IPv6 Special-Purpose Address
  Registry" and put back in the free pool managed by IANA.

In August 2019 RIPE NCC contacted the LISP WG asking if any action was ongoing 
concerning the extension of the experiment. The LISP WG concluded that very few 
requests have been made during three years and there was no compelling reason 
to extent the experiment. No further action has been taken by the LISP WG or 
the IETF. As such, in accordance with Section 10 of RFC 7954, RIPE NCC 
de-registered the existing assignments and IANA put the prefix back in the free 
pool (removing the entry from 
https://www.iana.org/assignments/iana-ipv6-special-registry 
).

At this point, RFC 7954 and RFC 7955 refer to a prefix that does not exists 
anymore. As such it make sense to move both documents to the status of 
"HISTORIC". This note, associated with the status change of the two RFCs will 
allow to keep track of the LISP EID prefix experiment.___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

Re: [lisp] Support draft-nexagon wg adoption

[Luigi Iannone]

Hi,

happy to see that there is already support for this document.

This email formally opens the two weeks WG adoption call.

Please have a look at the document and send an email on whether you agree or 
not to adopt it.
(Silence is NOT consensus)

Thanks

Ciao

L.




> On 19 Nov 2019, at 13:36, Sharon Barkai  wrote:
> 
> Hey, following very productive session today and as discussed would like to 
> formally ask group for draft adoption. 
> 
> Cheers,
> Sharon
> 
> --szb
> Cell: +972.53.2470068
> WhatsApp: +1.650.492.0794

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

Re: [lisp] Support draft-nexagon wg adoption

[Lori Jakab (lojakab)]

I agree, I also support adopting this as a working group document.

-Lori

On 11/19/19 06:49, Dino Farinacci wrote:

I think this use-case is a great one to make use of all the functionality LISP 
already supports.

I support adoption as a working group draft with a goal to publish the draft as 
an Informational RFC.

Dino


On Nov 19, 2019, at 1:37 PM, Sharon Barkai  wrote:

Hey, following very productive session today and as discussed would like to 
formally ask group for draft adoption.

Cheers,
Sharon

--szb
Cell: +972.53.2470068
WhatsApp: +1.650.492.0794
___
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





smime.p7s
Description: S/MIME Cryptographic Signature
___
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp