> On 9 Feb 2018, at 18:40, Paul Wouters wrote:
>
> On Wed, 7 Feb 2018, Tero Kivinen wrote:
>
>> It depends. If we do not take the item as official working group
>> chartered item, there are still few different options. You can either
>> get it processed as AD sponsored draft,
On Wed, 7 Feb 2018, Tero Kivinen wrote:
It depends. If we do not take the item as official working group
chartered item, there are still few different options. You can either
get it processed as AD sponsored draft, or you can go individual
submission track.
It is a little strange we don't
t; Envoyé : mercredi 7 février 2018 11:05
> À : BOUCADAIR Mohamed IMT/OLN
> Cc : ipsec@ietf.org
> Objet : Re: [IPsec] Candidate charter text is now in wiki
>
> mohamed.boucad...@orange.com writes:
> > I was naively expecting a formal call to assess the
> > interest/objec
mohamed.boucad...@orange.com writes:
> I was naively expecting a formal call to assess the
> interest/objections for each of the proposed items. Perhaps, I'm not
> the only one in that case.
That could have been another possibility, but as I was so busy between
the last IETF and now, I didn't
sses those comments was released.
Cheers,
Med
> -Message d'origine-
> De : Tero Kivinen [mailto:kivi...@iki.fi]
> Envoyé : mardi 6 février 2018 19:36
> À : BOUCADAIR Mohamed IMT/OLN
> Cc : ipsec@ietf.org
> Objet : RE: [IPsec] Candidate charter text is now in wiki
>
mohamed.boucad...@orange.com writes:
> It seems that you missed this text for the address failure codes (Nov 13):
> https://www.ietf.org/mail-archive/web/ipsec/current/msg11724.html
Yes, as I wanted to get some more discussion about it in the mailing
list first. I have not seen any discussion
David Schinazi writes:
> Here is proposed charter text for the "Mitigating privacy concerns"
> section:
As there has not been any support for this item in the mailing list I
do not think we will be adding it in the charter this time.
> IKEv2 is currently vulnerable to the two following privacy
Hi Tero,
Here is proposed charter text for the "Mitigating privacy concerns" section:
IKEv2 is currently vulnerable to the two following privacy concerns:
1) It's not possible to run a server that obfuscates IKEv2/IPsec using TLS.
Today thanks to RFC 8229 it is possible to run an
Dear Tero,
It seems that you missed this text for the address failure codes (Nov 13):
https://www.ietf.org/mail-archive/web/ipsec/current/msg11724.html
I'm resending it fwiw:
RFC7296 defines a generic notification code that is related to a
failure to handle an internal address