Re: Alternate AD review of draft-ietf-bfd-large-packets-11

then I will move forward with the IETF last call. Regards -éric From: Jeffrey Haas Date: Friday, 11 October 2024 at 17:59 To: Eric Vyncke (evyncke) Cc: rtg-bfd@ietf.org , John Scudder , af...@bloomberg.net , Reshad Rahman Subject: Re: Alternate AD review of draft-ietf-bfd-large-packets-11 [Re

[dns-privacy] Looking for WG chair volunteers in the INT area

The Internet area has to renew a handful of Working Group (WG) chairs in the coming weeks/months and the INT Area Directors are looking for volunteers, especially volunteers who have never chaired a WG but feel free to volunteer even if you have chaired or are still chairing a WG. Only Erik Kli

[Int-area] Looking for WG chair volunteers in the INT area

The Internet area in general has to renew a handful of Working Group (WG) chairs in the coming weeks/months and the INT Area Directors are looking for volunteers, especially volunteers who have never chaired a WG but feel free to volunteer even if you have chaired or are still chairing a WG. On

[6lo] Looking for WG chair volunteers in the INT area

The Internet area has to renew a handful of Working Group (WG) chairs in the coming weeks/months and the INT Area Directors are looking for volunteers, especially volunteers who have never chaired a WG but feel free to volunteer even if you have chaired or are still chairing a WG. Only Erik Kli

Next step after IETF Last Call of draft-ietf-bfd-unaffiliated-echo

Dear authors and WG, While there were no Last Call comments from the IETF community, there were some from the Last Call directorate reviews and I have seen Xiao and others replies, thanks for being reactive. INTDIR, by Tim Wicinski, https://mailarchive.ietf.org/arch/msg/int-dir/rYMojOLlnTSHxNS

Re: Next step after IETF Last Call of draft-ietf-bfd-unaffiliated-echo

want to defer the evaluation to the 24th of October. Regards -éric From: xiao.m...@zte.com.cn Date: Thursday, 10 October 2024 at 11:10 To: Eric Vyncke (evyncke) Cc: rtg-bfd@ietf.org , chengweiqi...@chinamobile.com , wangrui...@chinamobile.com , res...@yahoo.com , rche...@juniper.net , d

[ipv6-wg] Re: BCP/BCOP for ipv6 deployment and filtering policy

As a side note, there are now *TWO* documentation prefixes: * RFC 3849 2001:db8::/32 * RFC 9637 3fff::/20 -éric From: Rinse Kloek Date: Sunday, 6 October 2024 at 17:15 To: ipv6-wg@ripe.net Subject: [ipv6-wg] Re: BCP/BCOP for ipv6 deployment and filtering policy This RIPE Security PDF

[OAUTH-WG] Re: Éric Vyncke's No Objection on draft-ietf-oauth-resource-metadata-11: (with COMMENT)

Thank you Mike, for the accent on my first name ;-) More seriously, thanks for your reply and the update (and also for joining the telechat) Regards -éric From: Michael Jones Date: Thursday, 3 October 2024 at 19:41 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf-oauth-resource-metad

[GROW] Re: Éric Vyncke's No Objection on draft-ietf-grow-bmp-peer-up-04: (with COMMENT)

Thank you, Paolo, for your reply and the upcoming revised I-D. I now understand the issue about “String” ;-) Regards -éric From: Paolo Lucente Date: Wednesday, 2 October 2024 at 20:03 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf-grow-bmp-peer...@ietf.org , grow-cha...@ietf.org

[OPSEC]Re: [Technical Errata Reported] RFC7707 (8119)

I concur with Bob: bits (including the ones in the first octet) are numbered starting from 0 and the X bit (formerly called the Local/Global bit – see section 2.1.1 of RFC 9542) is the bit number 6. I.e., this errata should be rejected (thanks Anvar for your interest in the document though) R

Re: Alternate AD review of draft-ietf-bfd-unaffiliated-echo-10

Thank you, Xiao, for the revised I-D. I have requested the IETF Last Call (it may take one day though to get it done as it is a manual step by the IETF Secretariat). Regards -éric From: xiao.m...@zte.com.cn Date: Wednesday, 25 September 2024 at 04:42 To: Eric Vyncke (evyncke) Cc: rtg-bfd

Re: Alternate AD review of draft-ietf-bfd-unaffiliated-echo-10

the IETF Last Call. Regards -éric From: xiao.m...@zte.com.cn Date: Tuesday, 24 September 2024 at 09:25 To: Eric Vyncke (evyncke) Cc: rtg-bfd@ietf.org , j...@juniper.net , chengweiqi...@chinamobile.com , wangrui...@chinamobile.com , res...@yahoo.com , rche...@juniper.net , jh...@pfrc.org

Alternate AD review of draft-ietf-bfd-unaffiliated-echo-10

Dear BFD, dear authors, To lighten John Scudder’s workload, I will be the alternate responsible AD for draft-ietf-bfd-unaffiliated-echo. As I am an INT AD, please bear with me if I state something wrong about BFD ;-) First of all: thanks to the authors and the WHG for authoring this I-D and to

[Int-area] Re: Anonymous routing with encrypted IP addresses (Initial Internet Draft)

Pedro, Thanks for your email and BTW the usual format is a submitted IETF draft as pointed to by Alvaro (see https://authors.ietf.org). I quickly browsed through your text and the big question is of course the scalability of your proposal: an Internet router cannot really flood unknown destina

Re: Anonymous routing with encrypted IP addresses (Initial Internet Draft)

Pedro, Thanks for your email and BTW the usual format is a submitted IETF draft as pointed to by Alvaro (see https://authors.ietf.org). I quickly browsed through your text and the big question is of course the scalability of your proposal: an Internet router cannot really flood unknown destina

[netmod] Re: Éric Vyncke's No Objection on draft-ietf-netmod-syslog-model-32: (with COMMENT)

[Removing IESG to avoid waste of bandwidth] While I do not mind too much expanding the grouping, it would be useful to graphically indicate that this is an expanded grouping/imported model. -éric From: Mahesh Jethanandani Date: Thursday, 5 September 2024 at 00:43 To: Eric Vyncke (evyncke) Cc

[netmod] Re: Éric Vyncke's No Objection on draft-ietf-netmod-syslog-model-32: (with COMMENT)

delineating the grouping and imported branches... Was there any project in NETMOD about this ? Regards -éric From: Mahesh Jethanandani Date: Wednesday, 4 September 2024 at 19:41 To: Eric Vyncke (evyncke) Cc: The IESG , draft-ietf-netmod-syslog-mo...@ietf.org , NETMOD WG Chairs , NETMOD Working

[OPSAWG]Re: One week WG Last Call: draft-ietf-opsawg-mud-iot-dns-considerations-17.txt

Hi Michael, It seems that we digress from draft-ietf-opsawg-mud-iot-dns-considerations ;-) and we agree that the use of DNS for layer-3 ACL is wider than plain MUD even if MUD is a special case as you noted below. Regards -éric On 02/09/2024, 02:12, "Michael Richardson" wrote: E

[OPSAWG]Re: One week WG Last Call: draft-ietf-opsawg-mud-iot-dns-considerations-17.txt

of firewalls, which is common (at least for one firewall that I know), it makes life easier for security people to write ACL (notably when handing IPv6-only or dual-stack nodes). -éric On 30/08/2024, 00:27, "Michael Richardson" wrote: Eric Vyncke \(evyncke\) mail

[OPSAWG]Re: One week WG Last Call: draft-ietf-opsawg-mud-iot-dns-considerations-17.txt

Bonjour Benoît, dear chairs/authors, I have reviewed the diffs: - with my IESG/AD hat, the diffs are extensive but do not really change the core of the document, i.e., another IESG ballot does not seem required even for the vast amount of changes - thanks for addressing many of the COMMENTs in m

[Pce] Re: Éric Vyncke's No Objection on draft-ietf-pce-pcep-extension-native-ip-34: (with COMMENT)

a reference or in-line) makes it super clear, but again, up to the authors/WG Regards -éric From: Aijun Wang Date: Thursday, 22 August 2024 at 11:43 To: Eric Vyncke (evyncke) , 'The IESG' Cc: draft-ietf-pce-pcep-extension-native...@ietf.org , pce-cha...@ietf.org , pce@ie

[bess] Re: Éric Vyncke's No Objection on draft-ietf-bess-evpn-mh-split-horizon-10: (with COMMENT)

Hello Jorge, Thanks for your reply, the fix, and the explanations. All is good for me and I think the I-D is in better shape. Regards -éric From: Jorge Rabadan (Nokia) Date: Sunday, 18 August 2024 at 03:17 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf-bess-evpn-mh-split-hori

Re: Alternate AD review of draft-ietf-bfd-large-packets-11

Hello Jeff, Thanks for your quick reply. There is no urgency to reply to all my points, else I would have submitted a PR ;-) See below for EVY> Regards -éric From: Jeffrey Haas Date: Wednesday, 14 August 2024 at 14:35 To: Eric Vyncke (evyncke) Cc: rtg-bfd@ietf.org , John Scudder ,

Alternate AD review of draft-ietf-bfd-large-packets-11

Dear BFD, dear authors, To lighten John Scudder’s workload, I will be the alternate responsible AD for draft-ietf-bfd-large-packets. As I am an INT AD, please bear with me if I state something wrong about BFD ;-) Before proceeding with the publication process, I usually do my AD review before

[Softwires] Re: [Editorial Errata Reported] RFC7599 (8063)

Any taker on this erratum ? I was only following softwire WG from far away... -éric From: RFC Errata System Date: Friday, 2 August 2024 at 19:56 To: rfc-edi...@rfc-editor.org Cc: dsfreem...@freemire.net , congx...@cernet.edu.cn , Wojciech Dec (wdec) , o...@cisco.com , satoru.matsush...@g.soft

[spring] Re: WG Adoption Call for draft-bdmgct-spring-srv6-security (ends Aug/19)

Without any hat, I support this important document. Time permitting, I also intend to review it. -éric From: Alvaro Retana Date: Monday, 5 August 2024 at 15:05 To: SPRING WG Cc: draft-bdmgct-spring-srv6-secur...@ietf.org , spring-cha...@ietf.org Subject: [spring] WG Adoption Call for draft-

[DNSOP] Re: [Ext] Re: [dnsext] [Technical Errata Reported] RFC4035 (8037)

Elias, I will have to read erratum report 8038 (RFC6840) for a definitive answer, but the IESG statement and my explanations about erratum report 8037 probably apply. Regards -éric From: Elias Heftrig Date: Friday, 2 August 2024 at 17:29 To: Paul Hoffman , Eric Vyncke (evyncke) Cc: Rose

[DNSOP] Re: [dnsext] [Technical Errata Reported] RFC4035 (8037)

/statement-iesg-iesg-processing-of-rfc-errata-for-the-ietf-stream-20210507/ From: Paul Hoffman Date: Tuesday, 30 July 2024 at 20:49 To: Elias Heftrig Cc: Rose, Scott W. (Fed) , Rob Austein , RFC Errata System , s...@isc.org , mas...@cs.colostate.edu , ek.i...@gmail.com , Eric Vyncke (evyncke

[spring] Re: The SPRING WG has placed draft-bdmgct-spring-srv6-security in state "Candidate for WG Adoption"

With the only of “IPv6 security” hat, I support the adoption of this draft as a WG document (albeit not ready for publication yet). I intend to do reviews and suggest text. Regards, -éric PS: replying to the data tracker email without waiting for the chairs’ email about this CfA, what matters

[OPSEC]Re: Sunsetting the OPSec WG: It's Been a Secure Ride!

Also a tear or two in my eyes when reading this... Thank you to Jen, Ron, and Warren -éric PS: what is the status of the mailing list ? Will it be kept open ? From: Jen Linkova Date: Friday, 26 July 2024 at 19:41 To: opsec WG Cc: OpSec Chairs , Warren Kumari Subject: [OPSEC]Sunsetting the OP

[Int-area] Some comments on draft-heiwin-intarea-reverse-traceroute-stateless

Dear authors, Without any hat (i.e., feel free to ignore), in preparation for the IETF-120 I have read your I-D and here are some comments. As always, reviews note the things to be improved and are not criticisms. # Generic This I-D/idea is really interesting and useful, unsure whether it is r

[Int-area] Re: New Version Notification for draft-bonica-intarea-icmp-op-exp-00.txt

Hello Ron and authors, While preparing IETF-120, I had a quick look at this I-D. Like others have written, an informational RFC cannot easily be used as a normative reference (moreover it does not specify anything). Suggest removing this goal from the abstract. If sections 8 and 9 were expande

[dns-privacy] Re: [Editorial Errata Reported] RFC9076 (8024)

Greg, thanks for your erratum, which I just rejected because “to choose” in the past tense is actually “chose” ;-) -éric From: RFC Errata System Date: Tuesday, 9 July 2024 at 08:19 To: rfc-edi...@rfc-editor.org Cc: gregchoules+...@googlemail.com , tjw.i...@gmail.com , dns-privacy@ietf.org S

[OPSAWG]Re: Éric Vyncke's No Objection on draft-ietf-opsawg-ipfix-fixes-10: (with COMMENT)

Med, super fast reply as usual ;-) The PR addresses indeed my concerns. Have a nice end of the week -éric From: mohamed.boucad...@orange.com Date: Friday, 5 July 2024 at 10:23 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf-opsawg-ipfix-fi...@ietf.org , opsawg-cha...@ietf.org , opsawg

[OPSAWG]Re: Éric Vyncke's Yes on draft-ietf-opsawg-ipfix-tcpo-v6eh-16: (with COMMENT)

: mohamed.boucad...@orange.com Date: Tuesday, 2 July 2024 at 16:20 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf-opsawg-ipfix-tcpo-v...@ietf.org , opsawg-cha...@ietf.org , opsawg@ietf.org , thomas.g...@swisscom.com Subject: RE: Éric Vyncke's Yes on draft-ietf-opsawg-ipfix-tcpo-v6eh-16:

[OPSAWG]Re: Éric Vyncke's No Objection on draft-ietf-opsawg-tsvwg-udp-ipfix-12: (with COMMENT)

Med, Indeed, adding sections in the actual entries would make it weird... So, your proposal looks fine to me Regards -éric From: mohamed.boucad...@orange.com Date: Tuesday, 2 July 2024 at 14:17 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf-opsawg-tsvwg-udp-ip...@ietf.org , opsawg-cha

[OPSAWG]Re: Éric Vyncke's No Objection on draft-ietf-opsawg-tsvwg-udp-ipfix-12: (with COMMENT)

and udpUnsafeExIDList IEs specified in sections 4.4 and 4.5” ? NB: expect a very similar comment in my ballot for draft-ietf-opsawg-ipfix-tcpo-v6eh-16 ;-) Regards -éric From: mohamed.boucad...@orange.com Date: Tuesday, 2 July 2024 at 13:17 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf

[Int-area] Re: [Technical Errata Reported] RFC9542 (7952)

Thank you, Donald, it seems logical indeed. I will mark it as “hold for doc update” Regards, -éric From: Donald Eastlake Date: Friday, 24 May 2024 at 04:19 To: Eric Vyncke (evyncke) Cc: RFC Errata System , jab...@strandkip.nl , liyiz...@huawei.com , ek.i...@gmail.com , Juan Carlos Zuniga

[Int-area] Re: [Technical Errata Reported] RFC9542 (7952)

Donald and Joe, I will let you decide whether the erratum is correct. -éric From: RFC Errata System Date: Thursday, 23 May 2024 at 11:33 To: d3e...@gmail.com , jab...@strandkip.nl , liyiz...@huawei.com , ek.i...@gmail.com , Eric Vyncke (evyncke) , Juan Carlos Zuniga (juzuniga) , wassim.had

Re: WG Adoption Call - draft-llsyang-rtgwg-dst-src-routing (05/20/24 - 06/02/24)

As an individual contributor, I also support the WG adoption of this I-D. It is really important for IPv6 multi-homing without using eBGP and PI space. Note that the BCP14 template is outdated and should be fixed. s/Conventionally, NAT or policy routing would be used/In the legacy IPv4 work, N

[6lo] Follow-up of the IESG evaluation of draft-ietf-6lo-multicast-registration-18

Dear authors, This document is approved by a revised I-D is required based on the multiple COMMENT + a remark by Sandy Ginoza that the ack section contains “to thank ... and” so the “...” should be expanded ;-) We also wondered whether RFC 9030 is a normative or informative reference. Regards

[6lo] Processing old erratum 6194 on RFC 4944, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks"

As the new shepherding AD for 6LO, I just found a reported (i.e., neither verified nor closed) erratum on RFC 4944, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks". https://www.rfc-editor.org/errata_search.php?eid=6194 This erratum was never posted to the 6LO list probably due to a te

[6lo] Proceeding with draft-ietf-6lo-multicast-registration

As you know, I am the new shepherding Area Director for 6LO since March. As Erik Kline, the previous AD in copy, has already done the job until the IETF Last Call, I am fully trusting him about an AD review, therefore I won’t do my own ;-) Thanks Erik ! Nevertheless, I spotted a couple of easy-

Re: [6lo] Secdir last call review of draft-ietf-6lo-multicast-registration-16

Kelly , sec...@ietf.org , Eric Vyncke (evyncke) Cc: 6lo@ietf.org <6lo@ietf.org>, draft-ietf-6lo-multicast-registration@ietf.org , last-c...@ietf.org Subject: Re: Secdir last call review of draft-ietf-6lo-multicast-registration-16 Hello Scott many thanks for the time and contributi

Re: [IPsec] Éric Vyncke's No Objection on draft-ietf-ipsecme-ikev2-auth-announce-09: (with COMMENT)

Your latest addition is good for me Thank you -éric From: Valery Smyslov Date: Monday, 15 April 2024 at 09:43 To: Eric Vyncke (evyncke) , 'The IESG' Cc: draft-ietf-ipsecme-ikev2-auth-annou...@ietf.org , ipsecme-cha...@ietf.org , ipsec@ietf.org , kivi...@iki.fi Subject: RE: Éri

Re: [IPsec] Éric Vyncke's No Objection on draft-ietf-ipsecme-ikev2-auth-announce-09: (with COMMENT)

Thank you, Valery, for your 2nd reply and for allowing me to reply w/o on-line access to the I-D when I replied. One last comment below as EVY2> All comments were non-blocking anyway :) -éric From: Valery Smyslov Date: Friday, 12 April 2024 at 09:40 To: Eric Vyncke (evyncke) , 'The I

Re: [IPsec] Éric Vyncke's No Objection on draft-ietf-ipsecme-ikev2-auth-announce-09: (with COMMENT)

Thank you, Valery, for the prompt reply. See below for EVY> Regards -éric From: Valery Smyslov Date: Thursday, 11 April 2024 at 15:23 To: Eric Vyncke (evyncke) , 'The IESG' Cc: draft-ietf-ipsecme-ikev2-auth-annou...@ietf.org , ipsecme-cha...@ietf.org , ipsec@ietf.org , k

Re: [ipv6-wg] IPv6 torrent and non-GUA addresses

I saw that 10+ years ago when experimenting IPv6 torrents. AFAIK, those addresses are plain IPv4 addresses in the wrong part of the address field. Sigh From: ipv6-wg on behalf of Marco Moock Date: Saturday, 6 April 2024 at 09:50 To: ipv6-wg@ripe.net Subject: [ipv6-wg] IPv6 torrent and no

Re: [Pce] Éric Vyncke's No Objection on draft-ietf-pce-segment-routing-ipv6-24: (with COMMENT)

Hello Cheng and Dhruv, Thanks a lot for all the explanations and the revised I-D. I sincerely think that the document has been improved with those changes. Regards -éric From: Cheng Li Date: Thursday, 4 April 2024 at 17:45 To: Dhruv Dhody , Eric Vyncke (evyncke) Cc: The IESG , draft-ietf

Re: [COSE] Éric Vyncke's No Objection on draft-ietf-cose-typ-header-parameter-04: (with COMMENT)

Thank you Mike for your reply and for the PR. All is good for me. Regards -éric From: Michael Jones Date: Wednesday, 3 April 2024 at 06:48 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf-cose-typ-header-parame...@ietf.org , cose-cha...@ietf.org , cose@ietf.org , ivaylopet...@google.com

Re: [spring] Separating Threads (draft-ietf-spring-srv6-srh-compression)

Alvaro Minor correction, there is also https://datatracker.ietf.org/doc/draft-wkumari-intarea-safe-limited-domains/ for a more generic approach on limited domains -éric From: spring on behalf of Alvaro Retana Date: Thursday, 28 March 2024 at 13:03 To: SPRING WG List Cc: spring-cha...@ietf.

Re: [DNSOP] Éric Vyncke's Yes on draft-ietf-dnsop-dns-error-reporting-07: (with COMMENT)

Hello Roy, Thanks for coming back to my previous ballot. It took me a while to bring it back from the level-2 cache ;-) I agree with you, the abstract is indeed clear. About the "SHOULD" without any documented exceptions, it is really unusual to do so but nothing that dramatic tough. Anyway, p

Re: [Lsr] Éric Vyncke's No Objection on draft-ietf-lsr-ospfv3-extended-lsa-yang-27: (with COMMENT)

Mahesh Indeed, this was my question: why including BCP14 template when they are not used ? 😊 Acee, the comment about a less trivial example was just a suggestion, feel free to ignore it Regards -éric From: Mahesh Jethanandani Date: Tuesday, 30 January 2024 at 02:52 To: Acee Lindem Cc: The

Re: [homenet] congrats!

[Extending to homenet as the concluded WG list should still exist] Indeed, congratulations to the authors, shepherds, WG chairs ! It has been a long path, but all main documents are now published, and SNAC WG (a spin-off) is thriving. Regards -éric On 29/01/2024, 11:36, "Stephen Farrell" mai

Re: [DNSOP] Dnsdir telechat review of draft-ietf-dnsop-avoid-fragmentation-16

Thank you, Vladimir, has you may have seen I have mentioned your reviews in my "NoObj" ballot (adding though other issues). Regards -éric On 27/12/2023, 17:13, "DNSOP on behalf of Vladimír Čunát via Datatracker" mailto:dnsop-boun...@ietf.org> on behalf of nore...@ietf.org

Re: Éric Vyncke's No Objection on draft-ietf-rtgwg-vrrp-rfc5798bis-17: (with COMMENT)

Acee, Thank you for your reply and thank you in advance for the -17. Regards -éric On 04/01/2024, 16:39, "Acee Lindem" mailto:acee.i...@gmail.com>> wrote: Hi Eric, > On Jan 4, 2024, at 09:53, Éric Vyncke via Datatracker > wrote: > > Éric Vyncke has entered the f

Re: [Pce] Éric Vyncke's No Objection on charter-ietf-pce-07-04: (with COMMENT)

John, You nailed it. With the suggest NEW text, I think that the PCE charter will be clearer -éric From: John Scudder Date: Thursday, 14 December 2023 at 15:52 To: Eric Vyncke (evyncke) Cc: The IESG , pce-cha...@ietf.org , pce@ietf.org Subject: Re: [Pce] Éric Vyncke's No Objecti

Re: [IPsec] [Schc] WG Adoption calls for draft-mglt-ipsecme-diet-esp and draft-mglt-ipsecme-ikev2-diet-esp-extension

Let me reply to Hannes’ statement: “Integrating the functionality into SCHC alone is not enough.” I consider SCHC as a technical mean and not an end. I.e., it is not about adding IPsec to SCHC but rather about using SCHC to compress IPsec (= ESP & IKE). The SCHC WG did a similar work with COAP.

[ipv6-wg] Allocating a /16 to a large enterprise ?

[This is about ARIN, but curious to see if anybody has any insight...] A colleague of mine showed me https://whois.arin.net/rest/net/NET6-2630-2, i.e., a /16 allocated by ARIN to Capital One (AFAIK a US bank). Of course, this may be a tool bug, or a human encoding mistake, else I will start to

Re: [COSE] Éric Vyncke's No Objection on draft-ietf-cose-cwt-claims-in-headers-09: (with COMMENT)

Mike, Thanks for your reply, and you made a good point indeed. -éric From: Michael Jones Date: Tuesday, 28 November 2023 at 22:36 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf-cose-cwt-claims-in-head...@ietf.org , cose-cha...@ietf.org , cose@ietf.org , mpror...@mesur.io , orie

Re: [spring] Éric Vyncke's No Objection on draft-ietf-spring-mpls-path-segment-17: (with COMMENT)

Thank you, Cheng, for your reply and the amended draft. Regards -éric From: Cheng Li Date: Monday, 27 November 2023 at 17:20 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf-spring-mpls-path-segm...@ietf.org , spring-cha...@ietf.org , spring@ietf.org , james.n.guich...@futurewei.com

Re: [Int-area] "Identification Extension for the Internet Protocol" question

Fred, Without any hat, I agree with Tom: any new protocol should be able to work with legacy (== current) devices including routers on the path. Tom, rather than HbH (that would be processed by every router on the path and whose fate is not too positive), I would rather suggest Dest Options as

[spring] Additional references for draft-bdmgct-spring-srv6-security

As said this morning during the SPRING WG meeting, the authors may consider taking input from RFC 6169 (Security Concerns with IP Tunneling) and RFC 9099 (Operational Security Considerations for IPv6 Networks). Hope this helps -éric (obviously no hat) ___

Re: [alto] Éric Vyncke's No Objection on draft-ietf-alto-oam-yang-15: (with COMMENT)

What an efficient shepherd, you are, Med 😊 Thanks for your quick reply, a variation of your text at the bottom about http vs. https would be nice in section 5.3.1.1 Regards -éric From: iesg on behalf of mohamed.boucad...@orange.com Date: Wednesday, 25 October 2023 at 13:15 To: Eric Vyncke

Re: [bess] Éric Vyncke's No Objection on draft-ietf-bess-pbb-evpn-isid-cmacflush-08: (with COMMENT)

2023 at 13:21 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf-bess-pbb-evpn-isid-cmacfl...@ietf.org , bess-cha...@ietf.org , bess@ietf.org , Matthew Bocci (Nokia) Subject: Re: Éric Vyncke's No Objection on draft-ietf-bess-pbb-evpn-isid-cmacflush-08: (with COMMENT) Hi Éric, Thanks very

Re: [OPSAWG] Length of EHs RE: About draft-boucadair-opsawg-ipfix-tcpo-v6eh

? From: mohamed.boucad...@orange.com Date: Monday, 9 October 2023 at 16:39 To: Eric Vyncke (evyncke) , opsawg@ietf.org Subject: Length of EHs RE: About draft-boucadair-opsawg-ipfix-tcpo-v6eh Hi Éric, all, > - what would also be SUPER interesting / useful is the length of those > Ext Heade

Re: [OPSAWG] Full or Truncated EHs RE: Some comments on draft-ietf-opsawg-ipfix-tcpo-v6eh

y, 9 October 2023 at 14:10 To: Eric Vyncke (evyncke) , opsawg@ietf.org Cc: ip...@ietf.org Subject: Full or Truncated EHs RE: Some comments on draft-ietf-opsawg-ipfix-tcpo-v6eh Hi Éric, “There should be a way to convey the information that the exporter was (un)able to parse the *full* exten

Re: [ipv6-wg] Why did the Google IPv6 statistics dropped for the Netherlands?

A measurement issue at Google is probably where to look (or some peering/routing with Google AS) -éric From: ipv6-wg on behalf of Mikael Abrahamsson via ipv6-wg Date: Tuesday, 10 October 2023 at 11:35 To: Marco Davids (Private) Cc: RIPE IPv6 WG Subject: Re: [ipv6-wg] Why did the Google IPv6

Re: [ipv6-wg] IPv6 Working group call for presentations for RIPE87

Raymond, If you find this interesting, then I can present “what’s new on the IPv6 front at the IETF?” for 15 minutes or so, just the most important/visible IETF drafts (or recent RFC). Of course, Jen could also present ;-) or co-present ;-) -éric From: ipv6-wg on behalf of Raymond Jetten D

Re: [OPSAWG] Some IPv6 comments on draft-ietf-opsawg-ipfix-fixes-02

Hello Med, Thanks for the conversation on this interesting topic. See in-line for EVY> Bien à toi, -éric From: mohamed.boucad...@orange.com Date: Monday, 9 October 2023 at 11:32 To: Eric Vyncke (evyncke) , opsawg@ietf.org Cc: ip...@ietf.org Subject: RE: Some IPv6 comments on draft-i

Re: [OPSAWG] Desambiguite unknwon EH vs. unknown upper layer headers RE: Some comments on draft-ietf-opsawg-ipfix-tcpo-v6eh

Med, You may also want to state the obvious, i.e., the subsequent EH are neither parsed nor counted. From: mohamed.boucad...@orange.com Date: Friday, 6 October 2023 at 16:20 To: Eric Vyncke (evyncke) , opsawg@ietf.org Cc: ip...@ietf.org Subject: Desambiguite unknwon EH vs. unknown upper

Re: [bess] Éric Vyncke's No Objection on draft-ietf-bess-evpn-pref-df-11: (with COMMENT)

Thank you, Jorge, for taking the time to reply. I can only regret the use of “DP” rather than “DNP”, but you have a point if there are existing implementations. Regards -éric From: Jorge Rabadan (Nokia) Date: Friday, 6 October 2023 at 21:51 To: Eric Vyncke (evyncke) , The IESG Cc: draft

Re: [bess] Éric Vyncke's No Objection on draft-ietf-bess-mvpn-evpn-aggregation-label-13: (with COMMENT)

Hello Jeffrey, Thanks again for your reply. Please look below for EV> -éric From: Jeffrey (Zhaohui) Zhang Date: Wednesday, 4 October 2023 at 20:24 To: Eric Vyncke (evyncke) , The IESG Cc: draft-ietf-bess-mvpn-evpn-aggregation-la...@ietf.org , bess-cha...@ietf.org , bess@ietf.

[OPSAWG] Some comments on draft-ietf-opsawg-ipfix-tcpo-v6eh

Benoît and Med, Thanks for this useful document, please find below some comments (obviously without any hat). Should the “No Next-Header” (next-header=59) be included (cfr my other remarks on the companion I-D) ? There should be a way to convey the information that the exporter was (un)able t

[OPSAWG] Some IPv6 comments on draft-ietf-opsawg-ipfix-fixes-02

Benoît and Med, Thanks for this document, please find below some comments on the IPv6 sections (4.1 and 9.1), obviously wearing no hat. I like the idea of creating a registry mapping IPFIX IE bits to IPv6 extension headers, even if there won’t be any new IPv6 extension headers. Another importa

Re: [IPsec] [Add] Summary & Next Steps RE: DNR's SvcParams encoding

the favorite solution for everyone [2] Med has already acted ;) From: Eric Vyncke (evyncke) Date: Wednesday, 4 October 2023 at 16:51 To: Erik Nygren , mohamed.boucad...@orange.com Cc: Chris Box , ADD Mailing list Subject: Re: [Add] Summary & Next Steps RE: DNR's SvcParams encoding

Re: [dns-privacy] Paul Wouters' Abstain on draft-ietf-dprive-unilateral-probing-12: (with COMMENT)

Paul, thank you for reconsidering (and explaining) your ballot position. Authors, do you intend to submit a revise I-D to take into account the IESG comments ? Thanks to all -éric From: dns-privacy on behalf of Paul Wouters via Datatracker Date: Thursday, 5 October 2023 at 20:46 To: The IES

Re: [Softwires] IPR Disclosure Telefonaktiebolaget LM Ericsson (publ)'s Statement about IPR related to RFC 5969

Humm It seems that this IPR disclosure has been removed by the submitter. -éric On 30/08/2023, 21:57, "Softwires on behalf of IETF Secretariat" mailto:softwires-boun...@ietf.org> on behalf of ietf-...@ietf.org > wrote: Dear Mark Townsley, Ole Trøan: An IPR disc

Re: [bess] Éric Vyncke's Discuss on draft-ietf-bess-mvpn-evpn-aggregation-label-11: (with DISCUSS and COMMENT)

Thank you, let's wait until the shepherd updates his write-up, then I am clearing my DISCUSS -éric On 29/09/2023, 16:38, "Jeffrey (Zhaohui) Zhang" mailto:zzh...@juniper.net>> wrote: Hi Eric, Thanks for your thorough review. I have submitted the -12 revision that fixes the reference error (a

[Int-area] The CBOR section of draft-ietf-intarea-rfc7042bis...

Dear authors, CBOR/INTAREA WGs, fellow ADs, When doing my AD review of draft-ietf-intarea-rfc7042bis, I find the section 2.4 (https://datatracker.ietf.org/doc/html/draft-ietf-intarea-rfc7042bis#section-2.4 ) "CBOR tags" out of the scope of this IETF draft, which is more about the use of IEEE i

Re: [Int-area] AD review of draft-ietf-intarea-rfc7042bis-08

mp; ADs. Regards -éric PS: Please note that I will be on holidays from this WE for 10 days. On 13/09/2023, 06:54, "Donald Eastlake" mailto:d3e...@gmail.com>> wrote: Hi Eric, Thanks for the review. See responses below. On Mon, Sep 11, 2023 at 8:43 AM Eric Vyncke (evyncke) m

[Int-area] AD review of draft-ietf-intarea-rfc7042bis-08

Dear authors, dear shepherd, dear WG, As the Int-area WG chairs have requested the publication of this IETF draft, I have done my usual AD review of it. Before processing with the publication (i.e., the IETF Last Call), I am requesting a reply or an action on all the points below. Special note

Re: [Taps] Éric Vyncke's Discuss on draft-ietf-taps-arch-18: (with DISCUSS and COMMENT)

Top post replying ;-) and deleting the previous text. The TAPS I-Ds are all very *neat* and I intend to change my ballot to YES after a discussion with the relevant ADs this Thursday. Authors are obviously welcome as observers during the telechat. I like Brian's distinction between prescriptive

Re: [Taps] Éric Vyncke's Discuss on draft-ietf-taps-arch-18: (with DISCUSS and COMMENT)

Let's have a chat (aka discussion) during the IESG telechat on Thursday with the AD (and authors/shepherd if they want to join). My own preference is to avoid normative language in an architecture I-D, else it becomes a 'requirements' I-D. Regards, -éric From: Mirja Kuehlewind Date: Monday,

[homenet] FW: Protocol Action: 'Service Identity in TLS' to Proposed Standard (draft-ietf-uta-rfc6125bis-15.txt)

FYI, Once this document is published, it will unblock the last two approved but not yet published Homenet documents: - draft-ietf-homenet-front-end-naming-delegation-27 - draft-ietf-homenet-naming-architecture-dhc-options-24 See also https://www.rfc-editor.org/cluster_info.php?cid=C472 (even if

Re: [nvo3] Éric Vyncke's Discuss on draft-ietf-nvo3-bfd-geneve-12: (with DISCUSS and COMMENT)

Xiao, The proposed text will address my DISCUSS point indeed. Thanks for the -13 revision, I am clearing my previous DISCUSS ballot ;-) Other comments are also OK. Regards -éric From: "xiao.m...@zte.com.cn" Date: Wednesday, 23 August 2023 at 11:39 To: Eric Vyncke Cc: "i...@ietf.org" , "dr

Re: [dns-privacy] [Ext] AD review of draft-ietf-dprive-unilateral-probing-09

Hello Paul, Thanks for your reply, look below for EV2> but, in short, we are all set *except* for the shepherd's write-up . Regards -éric On 05/08/2023, 02:53, "Paul Hoffman" mailto:paul.hoff...@icann.org>> wrote: On Jul 31, 2023, at 8:29 AM, Eric Vyncke (

[bess] Errata 7180 on RFC 4364 BGP/MPLS IP Virtual Private Networks (VPNs)

As the L3VPN activities have been transferred to the BESS WG, I would appreciate feedback from the BESS WG on this errata. https://www.rfc-editor.org/errata_search.php?eid=7180 The section 4.3.4 text " Note that this VPN architecture does not require the capability to distribute unlabeled VP

Re: [spring] Éric Vyncke's No Objection on draft-ietf-spring-sr-replication-segment-15: (with COMMENT)

Thank you, Rishabh, for your quick reply. I had a look at the revised -16. As you know, all my points were and are just non-blocking comments, see below for EV> Regards -éric From: Rishabh Parekh Date: Monday, 31 July 2023 at 22:05 To: Eric Vyncke Cc: The IESG , "draft-ietf-spring-sr-replic

Re: [Uta] Éric Vyncke's No Objection on draft-ietf-uta-rfc6125bis-14: (with COMMENT)

Thank you, Rich, for the prompt action -éric On 02/08/2023, 15:59, "Salz, Rich" mailto:rs...@akamai.com>> wrote: Thanks for the feedback. The SVCB issue is recorded in https://github.com/richsalz/draft-ietf-uta-rfc6125bis/issues/98

Re: [dns-privacy] AD review of draft-ietf-dprive-unilateral-probing-09

appendix A. This MUST be resolved before the IETF Last Call. (and sorry for the Outlook look of my reply ☹ ...) Regards, I sincerely hope that this thread has improved the quality of the document. -éric On 17/07/2023, 14:06, "Eric Vyncke (evyncke)" mailto:evyn...@cisco.com>> w

Re: [dns-privacy] [Ext] AD review of draft-ietf-dprive-unilateral-probing-09

Thank you, Paul, Joey, Daniel, for the -10. As you can guess, I won't have time to review the -10 and the email thread before next week __ Regards -éric On 27/07/2023, 08:18, "Paul Hoffman" mailto:paul.hoff...@icann.org>> wrote: Please see the -10 that was just submitted. Let us know if we

[dns-privacy] AD review of draft-ietf-dprive-unilateral-probing-09

Dear authors, dear DPRIVE WG, Thank you for the hard work done on this document, it was not an easy ride, but the WG has reached consensus, and the change of intended status also fits the charter. As usual, I have done an AD review of draft-ietf-dprive-unilateral-probing-09 before going forwar

Re: [dns-privacy] WGLC : draft-ietf-dprive-unilateral-probing

Daniel, Joey, Paul, As I am doing my AD review, may I check with the 3 authors whether they are aware of any IPR behind the one cited by Brian below ? Thanks, in advance, -éric On 07/07/2023, 15:03, "dns-privacy on behalf of Brian Haberman" mailto:dns-privacy-boun...@ietf.org> on behalf of

Re: [OPSEC] Martin Duke's Discuss on draft-ietf-opsec-probe-attribution-08: (with DISCUSS and COMMENT)

Hello Martin, Thanks for your review of this informational draft. Please find below some replies to your points, look for EV> If required, then Justin will follow up with a revised I-D. Regards -éric On 10/07/2023, 18:52, "Martin Duke via Datatracker" mailto:nore...@ietf.org>> wrote: Mart

Re: [OPSEC] I-D Action: draft-ietf-opsec-probe-attribution-08.txt

This version should address most if not all comments received during the IESG evaluation of Thursday 6th of July. Regards -éric & -justin On 10/07/2023, 17:02, "OPSEC on behalf of internet-dra...@ietf.org " mailto:opsec-boun...@ietf.org> on behalf of internet-

Re: [OPSEC] Paul Wouters' Discuss on draft-ietf-opsec-probe-attribution-07: (with DISCUSS and COMMENT)

Hello Paul, Thanks for your review: it is always nice to see another point of view on your work. Let me repeat the top part of my reply to Roman's DISCUSS (in case you have not read it) as it provides more context and explanations about what is meant by 'probe' in this case. Then, please in-l

Re: [OPSEC] Roman Danyliw's Discuss on draft-ietf-opsec-probe-attribution-07: (with DISCUSS and COMMENT)

Hello Roman, Thank you for your review. My understanding of your DISCUSS ballot is that this I-D is worse than the cure. If the above statement is correct, then there is probably a disconnect between your view and the actual purpose of this I-D, which is more like "if you bumped into another

Re: [Int-area] draft-pauly-intarea-proxy-config-pvd-00

It does indeed seem cleaner ;-) From: Int-area on behalf of Tommy Pauly Date: Thursday, 29 June 2023 at 17:32 To: Erik Kline Cc: MASQUE , "int-area@ietf.org" Subject: Re: [Int-area] draft-pauly-intarea-proxy-config-pvd-00 Yes, it is an interesting outcome — but I think that in the same was t

[Int-area] Looking for designated expert for Hierarchical HIT prefixes

Dear all, The IANA has asked me to find RFC 8126 designated experts for the Hierarchical HIT (HHIT) Prefixes registry [1] created by RFC 9374. This registry currently contains a single entry 2001:30::/28 that is used by the DRIP (Drone Remote ID Protocol) but other entries could also be added l

  1   2   3   4   5   6   7   8   >