IETF Logo Mail Archive

Re: [IPsec] Additional charter items 3/4: Labeled IPsec

"Hu, Jun (Nokia - US/Mountain View)" <jun.hu@nokia.com> Mon, 19 February 2018 17:52 UTC

Return-Path: <jun.hu@nokia.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 B98B912420B for <ipsec@ietfa.amsl.com>; Mon, 19 Feb 2018 09:52:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.911
X-Spam-Level:
X-Spam-Status: No, score=-2.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 Nq3HrTk3Mymj for <ipsec@ietfa.amsl.com>; Mon, 19 Feb 2018 09:52:27 -0800 (PST)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50107.outbound.protection.outlook.com [40.107.5.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 009BE1241F5 for <ipsec@ietf.org>; Mon, 19 Feb 2018 09:52:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=3V3ZmyARY0BvBRYy7FYuP6IJBS01aSDFRww0rcbfxU4=; b=K69KX7T+Bs9ONGLfyETd0Xi1gp/W5VVIimURvc3fseuxQd3lM0nACmgX7REK9s1/JSOKaN3Jh9Z9KsDz6HFIluVdwfzRgqQL8hLDWyIozC6EPTN5+Po8Ql3b8MQpF/+OiCLdPPsmLwHUW3aPkzqpgo03nXKNCqqCCEps3miqQZI=
Received: from AM4PR07MB3153.eurprd07.prod.outlook.com (10.171.188.142) by AM4PR07MB3476.eurprd07.prod.outlook.com (10.171.190.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.527.6; Mon, 19 Feb 2018 17:52:24 +0000
Received: from AM4PR07MB3153.eurprd07.prod.outlook.com ([fe80::296d:e6a1:bfb4:33e1]) by AM4PR07MB3153.eurprd07.prod.outlook.com ([fe80::296d:e6a1:bfb4:33e1%3]) with mapi id 15.20.0527.010; Mon, 19 Feb 2018 17:52:24 +0000
From: "Hu, Jun (Nokia - US/Mountain View)" <jun.hu@nokia.com>
To: Paul Wouters <paul@nohats.ca>, Tero Kivinen <kivinen@iki.fi>
CC: "ipsec@ietf.org" <ipsec@ietf.org>
Thread-Topic: [IPsec] Additional charter items 3/4: Labeled IPsec
Thread-Index: AQHTqapkaASM19JtwaAXCstWC7w7QA==
Date: Mon, 19 Feb 2018 17:52:24 +0000
Message-ID: <AM4PR07MB3153C9CDFF6DB45F8650AB9D95C80@AM4PR07MB3153.eurprd07.prod.outlook.com>
References: <23175.7597.238297.330233@fireball.acr.fi> <alpine.LRH.2.21.1802161447570.23713@bofh.nohats.ca>
In-Reply-To: <alpine.LRH.2.21.1802161447570.23713@bofh.nohats.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jun.hu@nokia.com;
x-originating-ip: [135.245.20.30]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM4PR07MB3476; 7:k9g171w5FM00Htyhm8cWFMgE7VleVI51H3CgtUXnxx5MKBnt3mIodvovcBXLM7AMWEhh0rQJjprxxA7dTkaVW6mnrJWaEAi+3c8mCkrjU15OOI+IFtc4nrZmRYMBQd6D/eB3KvPju6IOZofiG2hs6qowQIqzzVrLSpHddEg1d3oMkvGuQ8vHCDTeDU6b1TQX5BbtNLpBTuTaAOXmfPoTlwyU3b2ku5ZDog6c/ft4Z0Afemo7OMpXJYeRamlKnxB1
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 33d5a669-f4d3-4673-ad8f-08d577c1884f
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603307)(7193020); SRVR:AM4PR07MB3476;
x-ms-traffictypediagnostic: AM4PR07MB3476:
x-microsoft-antispam-prvs: <AM4PR07MB3476D7C3C870C9A59F332C7295C80@AM4PR07MB3476.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3002001)(3231101)(11241501184)(806099)(944501161)(10201501046)(93006095)(93001095)(6055026)(6041288)(20161123558120)(20161123564045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011); SRVR:AM4PR07MB3476; BCL:0; PCL:0; RULEID:; SRVR:AM4PR07MB3476;
x-forefront-prvs: 0588B2BD96
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(39380400002)(366004)(396003)(39860400002)(13464003)(189003)(199004)(3280700002)(14454004)(68736007)(33656002)(6246003)(4326008)(25786009)(5660300001)(478600001)(5250100002)(8936002)(8676002)(2900100001)(81166006)(305945005)(3660700001)(81156014)(74316002)(7736002)(66066001)(97736004)(966005)(86362001)(229853002)(59450400001)(102836004)(6506007)(53546011)(316002)(186003)(26005)(6116002)(2906002)(3846002)(105586002)(2950100002)(6436002)(53936002)(99286004)(76176011)(9686003)(55016002)(110136005)(6306002)(106356001)(7696005); DIR:OUT; SFP:1102; SCL:1; SRVR:AM4PR07MB3476; H:AM4PR07MB3153.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: ejcMP91q7E+3Brx8OL7Rk/8lpU0SscBhq5ZAfn4n8v9MSmnlF/xupVoJHw6EWpIFFBkGb+jGo7pSJWHOG2qfqattZrwwB+eqUDx4mI0A0HrHfymsVuC/k6FkLOGa3lTJOrqFechuz40dj36r4EGqjf8RiIyyDsBmoRwwyC1dN3I9P7Gi6H2JYgxnqj1W5xTS1Pf1HjqNcZGi8L5N/36Vxw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 33d5a669-f4d3-4673-ad8f-08d577c1884f
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Feb 2018 17:52:24.1172 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR07MB3476
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/UVso4OoYe7kUIAPoB8sQ1IHFXss>
Subject: Re: [IPsec] Additional charter items 3/4: Labeled IPsec
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 17:52:30 -0000

I am also interested in this, since currently there is no good way to identify a CHILD_SA, current traffic selector is too cumbersome to be used as identifier, and in some cases can't be used as a consistent id; for example there are two types of traffic (same protocol/port, but different responder address) need to be put into two different CHILD_SA, however initiator doesn't know the responder address range in advance, currently there is no way for responder to differentiate; 

> -----Original Message-----
> From: IPsec [mailto:ipsec-bounces@ietf.org] On Behalf Of Paul Wouters
> Sent: Friday, February 16, 2018 11:50 AM
> To: Tero Kivinen <kivinen@iki.fi>
> Cc: ipsec@ietf.org
> Subject: Re: [IPsec] Additional charter items 3/4: Labeled IPsec
> 
> On Fri, 16 Feb 2018, Tero Kivinen wrote:
> 
> > The proposed charter text for this item is:
> >
> > ----------------------------------------------------------------------
> > Some systems support security labels (aka security context) as one of
> > the selectors of the SPD. This label needs to be part of the IKE
> > negotiation for the IPsec SA. non-standard implementations exist for
> > IKEv1 (formerly abusing IPSEC Security Association Attribute 10, now
> > using private space IPSEC Security Association Attribute 32001). The
> > work is to standarize this for IKEv2.
> > ----------------------------------------------------------------------
> >
> > Is that charter text clear enough? Is there enough people interested
> > in this?
> 
> I brought it in, so I do agree it is clear enough. And after talking to some
> people in the working group, it seems this is ideally done using a new traffic
> selector. That would also satisfy Yoav's concern that there is no burden on
> implementations that dont want to support this.
> 
> I will co-author a draft on this in time for IETF 101 :)
> 
> Paul
> 
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec

v2.23.0 | Report a Bug | By Email