[IPsec] Erik Kline's Yes on draft-ietf-ipsecme-ikev1-algo-to-historic-08: (with COMMENT)

2022-12-07 Thread Erik Kline via Datatracker
Erik Kline has entered the following ballot position for draft-ietf-ipsecme-ikev1-algo-to-historic-08: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer

[IPsec] Erik Kline's No Objection on draft-ietf-ipsecme-ikev2-multiple-ke-10: (with COMMENT)

2022-11-29 Thread Erik Kline via Datatracker
Erik Kline has entered the following ballot position for draft-ietf-ipsecme-ikev2-multiple-ke-10: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please

Re: [IPsec] Fwd: New Version Notification for draft-xu-risav-02.txt

2022-10-23 Thread Erik Kline
On Sun, Oct 23, 2022 at 9:37 AM Paul Wouters wrote: > On Oct 21, 2022, at 23:50, Erik Kline wrote: > > > >  > > You could also just say that ASBRs are presumed to be communicating > within a well-managed environment, are often zero or one hops away from one > another

Re: [IPsec] Fwd: New Version Notification for draft-xu-risav-02.txt

2022-10-21 Thread Erik Kline
el, and IMHO should not be viewed as a violation of > RFC 8200. > > Where this gets interesting is ICMP responses from intermediary routers > (e.g. traceroute, PMTUD). I'm not sure what to do about this, but I guess > it's probably not worse than what would happen with an ESP tunnel... > &g

Re: [IPsec] Fwd: New Version Notification for draft-xu-risav-02.txt

2022-10-20 Thread Erik Kline
I don't understand how "transport mode" can work for non-originated packets; for IPv6, inserting random headers along the path would violate 8200. On Thu, Oct 20, 2022 at 7:23 AM Ben Schwartz wrote: > Hello IPSEC, > > We've just put out an extensively revised version of our RISAV proposal >

Re: [IPsec] Éric Vyncke's Discuss on draft-ietf-ipsecme-iptfs-14: (with DISCUSS and COMMENT)

2022-08-24 Thread Erik Kline
> > I.e., either this document needs to formally update RFC 4303 by allowing > any > > number or another IP protocol number must be requested to the IANA. > > As I pointed out in my previous email that is not the case. > > The RFC4303 ESP has a Next Header field which contains indicates what >

[IPsec] Erik Kline's No Objection on draft-ietf-ipsecme-rfc8229bis-07: (with COMMENT)

2022-08-07 Thread Erik Kline via Datatracker
Erik Kline has entered the following ballot position for draft-ietf-ipsecme-rfc8229bis-07: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer

Re: [IPsec] Last Call: (Minimal ESP) to Informational RFC

2021-08-14 Thread Erik Kline
[+ipsec] On Thu, Aug 12, 2021 at 2:50 PM The IESG wrote: > > The IESG has received a request from the Light-Weight Implementation > Guidance > WG (lwig) to consider the following document: - 'Minimal ESP' >as Informational RFC > > The IESG plans to make a decision in the next few weeks, and

[IPsec] Erik Kline's Yes on draft-ietf-ipsecme-ipv6-ipv4-codes-05: (with COMMENT)

2020-12-16 Thread Erik Kline via Datatracker
Erik Kline has entered the following ballot position for draft-ietf-ipsecme-ipv6-ipv4-codes-05: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer