Re: [IPsec] Candidate charter text is now in wiki
<mohamed.boucadair@orange.com> Wed, 07 February 2018 07:48 UTC
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 458811201FA for <ipsec@ietfa.amsl.com>; Tue, 6 Feb 2018 23:48:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.63
X-Spam-Level:
X-Spam-Status: No, score=-2.63 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6kXfnvU0bRYw for <ipsec@ietfa.amsl.com>; Tue, 6 Feb 2018 23:48:48 -0800 (PST)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B5C71200C1 for <ipsec@ietf.org>; Tue, 6 Feb 2018 23:48:48 -0800 (PST)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 50F90A0CC2; Wed, 7 Feb 2018 08:48:47 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.42]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id 3349020067; Wed, 7 Feb 2018 08:48:47 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM41.corporate.adroot.infra.ftgroup ([fe80::c845:f762:8997:ec86%19]) with mapi id 14.03.0382.000; Wed, 7 Feb 2018 08:48:46 +0100
From: mohamed.boucadair@orange.com
To: Tero Kivinen <kivinen@iki.fi>
CC: "ipsec@ietf.org" <ipsec@ietf.org>
Thread-Topic: [IPsec] Candidate charter text is now in wiki
Thread-Index: AQHTX2PY1LVxwKS2jUO3yJx92UH7bqMYHZYQgIAFf4CAAOrTYA==
Date: Wed, 07 Feb 2018 07:48:46 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A0CC90D@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <23054.29098.665202.402605@fireball.acr.fi> <787AE7BB302AE849A7480A190F8B93300A07C37A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <23161.62855.158031.367282@fireball.acr.fi>
In-Reply-To: <23161.62855.158031.367282@fireball.acr.fi>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/vOpDO7qj1xykax_wHlTARPwWArQ>
Subject: Re: [IPsec] Candidate charter text is now in wiki
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Feb 2018 07:48:50 -0000
Hi Tero, Thank you for the update. 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. I have one "logistic" question: if this proposed item is not included in the charter, does this mean that I can proceed with the code points assignment request (https://datatracker.ietf.org/doc/draft-boucadair-ipsecme-ipv6-ipv4-codes/) with IANA and the codes will be assigned? For the record, the only comments I received were from Paul (thanks), and an updated version of the draft that addresses those comments was released. Cheers, Med > -----Message d'origine----- > De : Tero Kivinen [mailto:kivinen@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.boucadair@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 about it since the IETF, so > is there really enough interest for it. The charter in wiki only > included items we discussed in the meeting. > > > I'm resending it fwiw: > > > > RFC7296 defines a generic notification code that is related to a > > failure to handle an internal address failure. That code does not > > explicitly allow an initiator to determine why a given address family > > is not assigned, nor whether it should try using another address > > family. The Working Group will specify a set of more specific > > notification codes that will provide sufficient information to the > > IKEv2 initiator about the encountered failure. > -- > kivinen@iki.fi
- [IPsec] Candidate charter text is now in wiki Tero Kivinen
- Re: [IPsec] Candidate charter text is now in wiki mohamed.boucadair
- Re: [IPsec] Candidate charter text is now in wiki David Schinazi
- Re: [IPsec] Candidate charter text is now in wiki Tero Kivinen
- Re: [IPsec] Candidate charter text is now in wiki Tero Kivinen
- Re: [IPsec] Candidate charter text is now in wiki mohamed.boucadair
- Re: [IPsec] Candidate charter text is now in wiki Tero Kivinen
- Re: [IPsec] Candidate charter text is now in wiki mohamed.boucadair
- Re: [IPsec] Candidate charter text is now in wiki Paul Wouters
- Re: [IPsec] Candidate charter text is now in wiki Yoav Nir