on to the document after
> the document is adopted.
> --
> kivi...@iki.fi
>
> ___
> IPsec mailing list -- ipsec@ietf.org
> To unsubscribe send an email to ipsec-le...@ietf.org
--
Cheers, Jen Linkova
___
ssage -
From:
Date: Fri, Nov 8, 2024 at 2:30 AM
Subject: New Version Notification for draft-colitti-ipsecme-esp-ping-03.txt
To: Jen Linkova , Lorenzo Colitti
, Michael Richardson
A new version of Internet-Draft draft-colitti-ipsecme-esp-ping-03.txt has been
successfully submitted by Jen Linkov
f.org/arch/msg/ipsec/9_hkyF3P7Nq5oEOPc73v6i2gdLU/
> 2 emails.
>
>
>
> --
> Michael Richardson , Sandelman Software Works
> -= IPv6 IoT consulting =- *I*LIKE*TRAINS*
>
>
>
> ___
> IPsec mailing
We've just submitted -02 which should address comments raised during
the IPSECME session at IETF119.
Comments/suggestions?
-- Forwarded message -
From:
Date: Fri, Apr 5, 2024 at 9:43 AM
Subject: New Version Notification for draft-colitti-ipsecme-esp-ping-02.txt
To: Jen Li
!
-- Forwarded message -
From:
Date: Fri, Mar 1, 2024 at 2:24 AM
Subject: New Version Notification for draft-colitti-ipsecme-esp-ping-01.txt
To: Jen Linkova , Lorenzo Colitti
, Michael Richardson
A new version of Internet-Draft draft-colitti-ipsecme-esp-ping-01.txt has been
successfully
n IKE, the device can
use ESP ping to find out that..ooops, the corporate WiFi the device is
connected to is having issues with end2end ESP connectivity, and
switch back to the mobile network, instead of blackholing the data
packets.
So I do not see any harm in advertising it in IKE but
letely
uncoupled from IKE...
--
Cheers, Jen Linkova
___
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec
llows a 3rd party to respond to ESP ping.
2. We try to make it work with real SPIs. Then the next header can not
be 59. Options are:
2.1 Explore that ICMP trick
2.2 Define a new destination option - similar to ICMPv6 echo
response/echo reply. Pros:
-- solves all problems c
EQUEST'
Or maybe we can change the meaning and allow a dummy packet with SPI =
7 to be processed as a echo request..
In this case this document shall update RFC4303..
> > -Original Message-
> > From: IPsec On Behalf Of Jen Linkova
> > Sent: Wednesday, January 10, 20
How would that device A differentiate between:
- an Echo Reply sent in response to its Echo request;
- an Echo Request sent by the peer independently;
- just some garbage (or shall the device assume that any packet with
next header = 59 is a valid ESP ping packet?
In the original proposal it w
10 matches
Mail list logo
