IETF Logo Mail Archive

Re: [IPsec] Additional charter items 2/4: Address Failure Errors

<mohamed.boucadair@orange.com> Mon, 19 February 2018 06:16 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 AFC10127058 for <ipsec@ietfa.amsl.com>; Sun, 18 Feb 2018 22:16:40 -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 Wdcqt_gjiSYv for <ipsec@ietfa.amsl.com>; Sun, 18 Feb 2018 22:16:39 -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 297A4126C89 for <ipsec@ietf.org>; Sun, 18 Feb 2018 22:16:39 -0800 (PST)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 8EFB241558; Mon, 19 Feb 2018 07:16:37 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.43]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id 777392006A; Mon, 19 Feb 2018 07:16:37 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM5F.corporate.adroot.infra.ftgroup ([fe80::e172:f13e:8be6:71cc%18]) with mapi id 14.03.0382.000; Mon, 19 Feb 2018 07:16:37 +0100
From: mohamed.boucadair@orange.com
To: Tero Kivinen <kivinen@iki.fi>, "ipsec@ietf.org" <ipsec@ietf.org>
Thread-Topic: [IPsec] Additional charter items 2/4: Address Failure Errors
Thread-Index: AQHTp1CO7c1Gfi5aMUK2SJZZgDO4JaOrQt1A
Date: Mon, 19 Feb 2018 06:16:36 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A0D41BE@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <23175.7445.247642.686611@fireball.acr.fi>
In-Reply-To: <23175.7445.247642.686611@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.4]
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/OCK-QYT0kHdLKa7SFFZUSoeF41M>
Subject: Re: [IPsec] Additional charter items 2/4: Address Failure Errors
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: Mon, 19 Feb 2018 06:16:40 -0000

Hi all, 

I support this item, obviously. 

Cheers,
Med

> -----Message d'origine-----
> De : IPsec [mailto:ipsec-bounces@ietf.org] De la part de Tero Kivinen
> Envoyé : vendredi 16 février 2018 19:04
> À : ipsec@ietf.org
> Objet : [IPsec] Additional charter items 2/4: Address Failure Errors
> 
> This item has draft (draft-boucadair-ipsecme-ipv6-ipv4-codes) which
> quite well the needs and why this is to done, and I think we do
> undestand the item itself, but the charter text was not covered in the
> IETF 100 meeting, so we did not get consensus call done for it.
> 
> The proposed charter text is:
> 
> ----------------------------------------------------------------------
> 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.
> draft-boucadair-ipsecme-ipv6-ipv4-codes will be used as a starting
> point for this item.
> ----------------------------------------------------------------------
> 
> Send your comments and whether you support adding this to the charter
> to the ipsec list in next two weeks.
> --
> kivinen@iki.fi
> 
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec

v2.23.0 | Report a Bug | By Email