Bruno:

The mail link that you mentioned is sufficient and clear.  Based on the 
feedback, the authors have decided to remove the H.Insert.Red text from their 
draft.

Thank you for your quick response.

Cheerily, Sue Hares

From: bruno.decra...@orange.com <bruno.decra...@orange.com>
Sent: Monday, June 10, 2024 7:54 AM
To: Susan Hares <sha...@ndzh.com>
Cc: spring-cha...@ietf.org; idr-cha...@ietf.org; Dongjie (Jimmy) 
<jie.d...@huawei.com>; i...@ietf.org; spring@ietf.org
Subject: RE: draft-ietf-idr-cpr-02

Hi Susan, Please see inline [Bruno]  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  
‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌ 
 ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  
‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌
External (bruno.decra...@orange.com<mailto:bruno.decra...@orange.com>)
  Report This 
Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnMTA1ODY5MTIvc2hhcmVzQG5kemguY29tLzUzZWJhNWYzOWZmYTg3N2ViZjE3MjQ2NDI1OGNiZTIzLzE3MTgwMjA0NTUuMzY=#key=972f99f098a64e34ab47912aee056c6d>
  
FAQ<https://www.godaddy.com/help/report-email-with-advanced-email-security-40813>
  GoDaddy Advanced Email Security, Powered by 
INKY<https://www.inky.com/protection-by-inky>

Hi Susan,

Please see inline [Bruno]

From: Susan Hares <sha...@ndzh.com<mailto:sha...@ndzh.com>>
Sent: Thursday, June 6, 2024 3:47 PM
To: spring@ietf.org<mailto:spring@ietf.org>
Cc: spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>; 
idr-cha...@ietf.org<mailto:idr-cha...@ietf.org>; Dongjie (Jimmy) 
<jie.d...@huawei.com<mailto:jie.d...@huawei.com>>; 
i...@ietf.org<mailto:i...@ietf.org>
Subject: draft-ietf-idr-cpr-02

CAUTION : This email originated outside the company. Do not click on any links 
or open attachments unless you are expecting them from the sender.
ATTENTION : Cet e-mail provient de l'extérieur de l'entreprise. Ne cliquez pas 
sur les liens ou n'ouvrez pas les pièces jointes à moins de connaitre 
l'expéditeur.

Spring  WG:

draft-ietf-idr-cpr-02.txt is an informational draft that has past WG LC.

I’m writing up the shepherd’s report for this draft and  I need some 
information from Spring.

draft-ietf-idr-cpr-02.txt  reports on the use of H.Insert.Red.  H.Insert is 
defined in [draft-filsfils-spring-srv6-net-pgm-insertion/].

Ketan Talaulikar (ketant.i...@gmail.com<mailto:ketant.i...@gmail.com>) suggests 
that [draft-filsfils-spring-srv6-net-pgm-insertion] is unlikely to get adopted 
by SPRING WG, but that it is a “de-facto industry standard”.

[Bruno] I tend to agree with Ketan although I would have phrased the second 
part differently (It has been implemented. Probably significantly implemented 
although I did not run a poll)

Ketan believes that almost all SRv6 implementations prefer this function over 
H.Encaps.

Could the Spring WG and/or Spring Chairs provide me a summary of the history on 
this draft and SRv6 functions?  You can send it to me or the IDR WG.

[Bruno] Would this email on IDR archive work or do you have more specifics 
points in mind ? 
https://mailarchive.ietf.org/arch/msg/idr/MocXZIPp_VlfVprgeA6B1CEcFsE/<https://shared.outlook.inky.com/link?domain=mailarchive.ietf.org&t=h.eJxNzD0PgjAUheG_YjqbXloooJMf0cTBxMkYF1PKLRChJbfooPG_azfXk_c8b_agni1nrJ2mMSwBBt31mkzbPZF3OFnuqYE4wBAa6GqCozeX6-E03s69PY_U4DrfiO3O7MMO2HzG7pFzOP2OIlFlvhASQqsJw8rVr5YbP4BKsdLKpgtrdVkUWFlRyCzPpCpNhTIFUYgykUmmFE_zqGJUK3o4z2s0pNHhypN2DUYwFnUs_qbPF5xIRKQ.MEQCICq3ftIxabj9S6EY2S8D3_PSACMaR3qe21vAt1hjYCJkAiAyTqBZxW3Ggptb5lgxGjorQVAPyn__7uRz1B967m1TOg>


I will forward a summary to the IDR mail list and Spring mail list.

[Bruno] Thank you for this
--Bruno

Thank you,
Sue Hares
(shepherd, IDR WG chair)

____________________________________________________________________________________________________________

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
To unsubscribe send an email to spring-le...@ietf.org

Reply via email to