Bruno,

Please add the following to the list of last call comments to be tracked:


  *   https://mailarchive.ietf.org/arch/msg/spring/2BvW_aGaEsOfRclrE4-ctEGbTZs
  *   https://mailarchive.ietf.org/arch/msg/spring/t8Bm_kQdV2rTlxtvYss5KPY1KlI
  *   https://mailarchive.ietf.org/arch/msg/spring/nfzSTbLy24FLOd5h-52Hfr5zEnU

                                                                            Ron




Juniper Business Use Only
From: ipv6 <ipv6-boun...@ietf.org> On Behalf Of bruno.decra...@orange.com
Sent: Thursday, December 5, 2019 12:15 PM
To: 'SPRING WG List' <spring@ietf.org>
Cc: 6...@ietf.org; draft-ietf-spring-srv6-network-programming 
<draft-ietf-spring-srv6-network-programm...@ietf.org>
Subject: WGLC - draft-ietf-spring-srv6-network-programming


Hello SPRING,



This email starts a two weeks Working Group Last Call on 
draft-ietf-spring-srv6-network-programming [1].



Please read this document if you haven't read the most recent version, and send 
your comments to the SPRING WG list, no later than December 20.



You may copy the 6MAN WG for IPv6 related comment, but consider not duplicating 
emails on the 6MAN mailing list for the comments which are only spring 
specifics.



If you are raising a point which you expect will be specifically debated on the 
mailing list, consider using a specific email/thread for this point.

This may help avoiding that the thread become specific to this point and that 
other points get forgotten (or that the thread get converted into parallel 
independent discussions)



Thank you,

Bruno



[1] 
https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-05<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-05__;!8WoA6RjC81c!WtdxYG2xSF_q2rpWnOYGhgrGW8yw7jzvLa8EiJUeP05yi3TdBSyI35n-pjc7gafR$>




_________________________________________________________________________________________________________________________



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.
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Reply via email to