[IPsec] Mirja Kühlewind's No Objection on draft-ietf-ipsecme-qr-ikev2-10: (with COMMENT)

2020-01-07 Thread Mirja Kühlewind via Datatracker
Mirja Kühlewind has entered the following ballot position for draft-ietf-ipsecme-qr-ikev2-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 refer

[IPsec] Mirja Kühlewind's No Objection on charter-ietf-ipsecme-11-01: (with COMMENT)

2018-06-06 Thread Mirja Kühlewind
Mirja Kühlewind has entered the following ballot position for charter-ietf-ipsecme-11-01: 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.) The document

[IPsec] Mirja Kühlewind's No Objection on draft-ietf-ipsecme-tcp-encaps-10: (with COMMENT)

2017-06-14 Thread Mirja Kühlewind
Mirja Kühlewind has entered the following ballot position for draft-ietf-ipsecme-tcp-encaps-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] Mirja Kuehlewind's Discuss on draft-ietf-ipsecme-tcp-encaps-09: (with DISCUSS)

2017-05-03 Thread Mirja Kühlewind
I didn't propose to obsolete RFC3947 in this document. I guess you can also file an error for this if you don't want to take any further actions. However, for updating the IANA registry, I would say the right action is to do this simply by IESG approval for UDP then. Mirja On 03.05.2017 11:1

Re: [IPsec] Mirja Kuehlewind's Discuss on draft-ietf-ipsecme-tcp-encaps-09: (with DISCUSS)

2017-04-28 Thread Mirja Kühlewind
Hi Tero, a few quick replies but we also discussed this yesterday at the telechat and agreed on a way forward. On 27.04.2017 16:12, Tero Kivinen wrote: Mirja Kühlewind writes: I agree that this kind of port squatting is regrettable, but I also don't think it really helps to not publish

Re: [IPsec] Mirja Kühlewind's Discuss on draft-ietf-ipsecme-tcp-encaps-09: (with DISCUSS)

2017-04-27 Thread Mirja Kühlewind
wrote: On Apr 27, 2017, at 7:32 AM, Mirja Kühlewind wrote: See below On 27.04.2017 16:27, Eric Rescorla wrote: "This document leaves the selection of TCP ports up to implementations. It is suggested to use TCP port 4500, which is allocated for

Re: [IPsec] Mirja Kühlewind's Discuss on draft-ietf-ipsecme-tcp-encaps-09: (with DISCUSS)

2017-04-27 Thread Mirja Kühlewind
See below On 27.04.2017 16:27, Eric Rescorla wrote: "This document leaves the selection of TCP ports up to implementations. It is suggested to use TCP port 4500, which is allocated for IPsec NAT Traversal." Which sounds to me like an invit

Re: [IPsec] Mirja Kühlewind's Discuss on draft-ietf-ipsecme-tcp-encaps-09: (with DISCUSS)

2017-04-27 Thread Mirja Kühlewind
See below. On 27.04.2017 16:10, Eric Rescorla wrote: On Thu, Apr 27, 2017 at 6:42 AM, Mirja Kühlewind mailto:i...@kuehlewind.net>> wrote: Hi Ekr, hi all, (not sure anymore which email best to reply to but I'm using this one now to partly also reply to others).

Re: [IPsec] Mirja Kühlewind's Discuss on draft-ietf-ipsecme-tcp-encaps-09: (with DISCUSS)

2017-04-27 Thread Mirja Kühlewind
Yes, just saying... On 27.04.2017 15:50, Eric Rescorla wrote: On Thu, Apr 27, 2017 at 6:46 AM, Mirja Kühlewind mailto:i...@kuehlewind.net>> wrote: One more side comment on the magic number: actually the magic number makes it easy for network operator to identify IKE/IPSec traf

Re: [IPsec] Mirja Kühlewind's Discuss on draft-ietf-ipsecme-tcp-encaps-09: (with DISCUSS)

2017-04-27 Thread Mirja Kühlewind
, you should probably always encrypt it. On 27.04.2017 15:42, Mirja Kühlewind wrote: Hi Ekr, hi all, (not sure anymore which email best to reply to but I'm using this one now to partly also reply to others). See below. On 27.04.2017 14:51, Eric Rescorla wrote: On Thu, Apr 27, 2017

Re: [IPsec] Mirja Kühlewind's Discuss on draft-ietf-ipsecme-tcp-encaps-09: (with DISCUSS)

2017-04-27 Thread Mirja Kühlewind
Hi Ekr, hi all, (not sure anymore which email best to reply to but I'm using this one now to partly also reply to others). See below. On 27.04.2017 14:51, Eric Rescorla wrote: On Thu, Apr 27, 2017 at 1:32 AM, Mirja Kühlewind mailto:i...@kuehlewind.net>> wrote: I do see

Re: [IPsec] Mirja Kühlewind's Discuss on draft-ietf-ipsecme-tcp-encaps-09: (with DISCUSS)

2017-04-27 Thread Mirja Kühlewind
Hi Tommy, please see below, only on the first point for now. On 26.04.2017 05:28, Tommy Pauly wrote: On Apr 25, 2017, at 5:48 AM, Mirja Kühlewind wrote: Mirja Kühlewind has entered the following ballot position for draft-ietf-ipsecme-tcp-encaps-09: Discuss When responding, please keep

[IPsec] Mirja Kühlewind's Discuss on draft-ietf-ipsecme-tcp-encaps-09: (with DISCUSS)

2017-04-25 Thread Mirja Kühlewind
Mirja Kühlewind has entered the following ballot position for draft-ietf-ipsecme-tcp-encaps-09: Discuss 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 to

Re: [IPsec] Mirja Kühlewind's No Objection on draft-ietf-ipsecme-ddos-protection-09: (with COMMENT)

2016-10-12 Thread Mirja Kühlewind
Hi Valery, sorry for the late reply (holidays :-) ) See below. On 25.09.2016 22:20, Valery Smyslov wrote: Hi Mirja, Yoav, I agree with Yoav's answers, just want to clarify a few things. See below (I removed the comments where I have nothing to add to Yoav's answers). ---