Hi Luigi, all,

I also think that it is reasonable to publish this spec as a proposed standard.

Cheers,
Med

> -----Message d'origine-----
> De : lisp <lisp-boun...@ietf.org> De la part de Luigi Iannone
> Envoyé : jeudi 8 décembre 2022 16:45
> À : Jordi Paillissé <jordi.pailli...@upc.edu>
> Cc : Alberto Rodriguez-Natal (natal)
> <natal=40cisco....@dmarc.ietf.org>; lisp@ietf.org
> Objet : Re: [lisp] LISP PubSub to Proposed Standard?
> 
> <chairs hat off>
> 
> As an individual I think there is sufficient experience to make
> this draft a proposed standard.
> 
> <chairs hat on>
> 
> Folks, please express your opinion about moving this document to
> PS.
> 
> Ciao
> 
> L.
> 
> 
> > On 10 Nov 2022, at 11:15, Jordi Paillissé
> <jordi.pailli...@upc.edu> wrote:
> >
> > I agree with moving the document forward. It's a valuable
> functionality.
> >
> > Thanks,
> >
> > Jordi
> >
> > El 6/11/22 a les 13:57, Dino Farinacci ha escrit:
> >>
> >>> On Nov 6, 2022, at 12:27 PM, Alberto Rodriguez-Natal (natal)
> <natal=40cisco....@dmarc.ietf.org> wrote:
> >>>
> >>> On the meantime, what is the view of the WG on moving the
> document to Proposed Standard?
> >> I think it is critical to carry this fundamental solution as
> Proposed Standard. We have struggled for years keeping mappings up
> to date on proxy-ITRs.
> >>
> >> Pubsub provides an event triggered solution which I believe is
> fundamental functionality the architecture needs.
> >>
> >> Dino

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Reply via email to