IETF Logo Mail Archive

Re: [Pidloc] Comments on REQUIREMENT DRAFT draft-xyz-pidloc-reqs-00

<Dirk.von-Hugo@telekom.de> Thu, 01 August 2019 15:23 UTC

Return-Path: <Dirk.von-Hugo@telekom.de>
X-Original-To: pidloc@ietfa.amsl.com
Delivered-To: pidloc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B45271200F3 for <pidloc@ietfa.amsl.com>; Thu, 1 Aug 2019 08:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.297
X-Spam-Level:
X-Spam-Status: No, score=-4.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 F0gtUZybSaCb for <pidloc@ietfa.amsl.com>; Thu, 1 Aug 2019 08:23:21 -0700 (PDT)
Received: from mailout31.telekom.de (mailout31.telekom.de [194.25.225.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F3C5120103 for <pidloc@ietf.org>; Thu, 1 Aug 2019 08:23:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1564672997; x=1596208997; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=tsXB9siGfg6XZJvDWo5d7K0aFi+uvEOr2ROEynmkg2s=; b=7QXByC9hap7ROdYhDyflmgNdX666AqIWl5xpDkns6y20kzwuQNL6zgkE Op0QGQ2qV/kjoB7NF0DLfC4SZeOcfTeWEDLXje5p+1mYEFYZWGzfyLXv6 n/NpnZA9EGhloNO0lSPD4lzqOvyQjobzYJEFlh+Scgg98UmAoGrXnPL3q cn6rlQK/eg/AP+1Fssfmg/zB/VjbjZcMhsw6G552+pyHb3jTz+FUJIz7l 2o7Np+UZ4uoOV9caDKYa3KfGFf53Gy1IP08LGyXhYx3F+71/wuTCQALqX hINIHVVbWzF8OLGzka75Q8hi+l5/grnHYNz55UZ9unjOT2KwbLE/L1LAL A==;
Received: from qde9xy.de.t-internal.com ([10.171.254.32]) by MAILOUT31.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Aug 2019 17:23:15 +0200
X-IronPort-AV: E=Sophos;i="5.64,334,1559512800"; d="scan'208,217";a="334863476"
X-MGA-submission: MDHuc/Fx73s4kFI4XY4ZtqTbLNhBdmgq+822hJgcTMjIKW6ryXCyVVdfRsgtjDVaoY38b0objBWRsA+IwSDtDe7iS1q9uhEO1DbrWPwmQqOu24p3Y19XeFSd03A57VCByc+fzUMkVOvl2Nj22PvAv5vMJGKm0MMy5K07ULjW6ujjaA==
Received: from he199743.emea1.cds.t-internal.com ([10.169.119.51]) by QDE9Y1.de.t-internal.com with ESMTP/TLS/AES256-SHA; 01 Aug 2019 17:23:06 +0200
Received: from HE199743.EMEA1.cds.t-internal.com (10.169.119.51) by HE199743.emea1.cds.t-internal.com (10.169.119.51) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 1 Aug 2019 17:23:03 +0200
Received: from HE100181.emea1.cds.t-internal.com (10.171.40.15) by HE199743.EMEA1.cds.t-internal.com (10.169.119.51) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 1 Aug 2019 17:23:03 +0200
Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.17) by O365mail02.telekom.de (172.30.0.235) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 1 Aug 2019 17:23:03 +0200
Received: from FRXPR01MB0344.DEUPRD01.PROD.OUTLOOK.DE (10.158.152.15) by FRXPR01MB1032.DEUPRD01.PROD.OUTLOOK.DE (10.158.157.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.14; Thu, 1 Aug 2019 15:23:02 +0000
Received: from FRXPR01MB0344.DEUPRD01.PROD.OUTLOOK.DE ([fe80::bcc5:5ccb:131c:a7ce]) by FRXPR01MB0344.DEUPRD01.PROD.OUTLOOK.DE ([fe80::bcc5:5ccb:131c:a7ce%6]) with mapi id 15.20.2115.005; Thu, 1 Aug 2019 15:23:02 +0000
From: Dirk.von-Hugo@telekom.de
To: pidloc@ietf.org
CC: ggx@gigix.net, shunsuke.homma.fp@hco.ntt.co.jp, sarikaya@ieee.org
Thread-Topic: Comments on REQUIREMENT DRAFT draft-xyz-pidloc-reqs-00
Thread-Index: AdUmbWSs+c9Jg4Z+Ra6MZwsk5Iy8dwGiOjCABuC4R8A=
Date: Thu, 01 Aug 2019 15:23:02 +0000
Message-ID: <FRXPR01MB0344A5508757B60834C6E590D1DE0@FRXPR01MB0344.DEUPRD01.PROD.OUTLOOK.DE>
References: <004801d52676$79cc0d70$6d642850$@hco.ntt.co.jp> <CAC8QAcdnW7mT9LyG6v_RyRsYUkfotG2Ufy=9GnZo07MzN80NqQ@mail.gmail.com>
In-Reply-To: <CAC8QAcdnW7mT9LyG6v_RyRsYUkfotG2Ufy=9GnZo07MzN80NqQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Dirk.von-Hugo@telekom.de;
x-originating-ip: [212.201.104.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: cf526669-f265-466c-01fd-08d716942500
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:FRXPR01MB1032;
x-ms-traffictypediagnostic: FRXPR01MB1032:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <FRXPR01MB103262E7921B21FD62AFDF70D1DE0@FRXPR01MB1032.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01165471DB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(346002)(366004)(376002)(396003)(39860400002)(51444003)(199004)(189003)(54164003)(86362001)(53936002)(76176011)(52396003)(6246003)(186003)(102836004)(8676002)(7696005)(55016002)(14454004)(66066001)(236005)(316002)(53546011)(5640700003)(14444005)(68736007)(486006)(6916009)(26005)(3846002)(54896002)(9686003)(6306002)(54906003)(478600001)(966005)(2501003)(256004)(33656002)(229853002)(5660300002)(7736002)(66446008)(790700001)(66476007)(6116002)(64756008)(66946007)(76116006)(71190400001)(66556008)(476003)(11346002)(8936002)(2351001)(1730700003)(446003)(71200400001)(81156014)(81166006)(4326008)(2906002)(606006); DIR:OUT; SFP:1101; SCL:1; SRVR:FRXPR01MB1032; H:FRXPR01MB0344.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Qy6sxsEI/if7u6gt3s6LpdTrHPC/U/AF5Zk7zki8uU2Ceh/9we/F0AaFEyPPyNHMSCakt9QRO+EIwa0rnIyMsj192fIpsSemEzEuBHlan9p3Ex9MkkLgIyHU0dwZYim7p3kxdKFgYLdAmVP0duft871eqvRN+7IfFH2JPBj0kESAHpC22667/lcQUS7l47DaTr845+AHQnJgmzOXe4XcQJ5403sfJ/fVXpHGRPB2GegyLrqtdBp3EielibSzTBJ17Psq+JwdtS5bZLGlpxYBR4VqPGAv/zZhrVzBxDEpQ1nFxZYxvElaer8pcNQEKsivQ0AVPdDBLzT6/oNE7izLEELsfGFhLdpNou548XlE8O1nG38Knq5UiloNaavLykuzArEnl6LYd+B9kd8ao1h1g0lhBoFPOFcZr5Ru3PBkTyM=
Content-Type: multipart/alternative; boundary="_000_FRXPR01MB0344A5508757B60834C6E590D1DE0FRXPR01MB0344DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: cf526669-f265-466c-01fd-08d716942500
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Aug 2019 15:23:02.7123 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Dirk.von-Hugo@telekom.de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRXPR01MB1032
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/pidloc/wNF3sTeYQ81x1tlrZ1I2gA3R0K4>
Subject: Re: [Pidloc] Comments on REQUIREMENT DRAFT draft-xyz-pidloc-reqs-00
X-BeenThere: pidloc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <pidloc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pidloc>, <mailto:pidloc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pidloc/>
List-Post: <mailto:pidloc@ietf.org>
List-Help: <mailto:pidloc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pidloc>, <mailto:pidloc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2019 15:23:24 -0000

Dear all
The idea of pidloc in terms of different Identifier-Locator Split approaches and the privacy issues to be considered for operational deployment was presented last week in Montreal in SAAG (Security Area Advisory Group) as suggested by Sec ADs – slides are available at https://datatracker.ietf.org/meeting/105/materials/slides-105-saag-privacy-issues-in-identifier-locator-seperation-protocols-00.

Please find the provisional minutes here https://etherpad.ietf.org/p/notes-ietf-105-saag
My major take-away may be: Since a powerful mapping system is both the bottleneck for large deployment and a critical issue for privacy preservation that may be one of the gaps to identify. Surely more issues will have to be discussed … maybe whether we can inherit some insights from HIP protocol (not mentioned here as ‘above Layer 3’) and extending vehicular IdLoc use case to UAVs (unmanned aerial vehicles).

Please provide your comments here.
Next steps planned are to update two of our drafts to reflect recent suggestions.
Thanks to all!

Kind regards
Dirk

From: Behcet Sarikaya <sarikaya2012@gmail.com>
Sent: Donnerstag, 27. Juni 2019 16:41
To: Shunsuke Homma <shunsuke.homma.fp@hco.ntt.co.jp>
Cc: pidloc@ietf.org; Luigi Iannone <ggx@gigix.net>; von Hugo, Dirk <Dirk.von-Hugo@telekom.de>
Subject: Re: Comments on REQUIREMENT DRAFT draft-xyz-pidloc-reqs-00

Folks,

Thanks for all the comments.
Now that we received some feedback from SEC ADs, we need to consider those and take future steps based on that. One feedback was if I am not wrong there were too many use cases.
Dirk is going to talk to the ADs during IETF 105 week next month and hopefully get a more clear picture of what they want.
Let's see what they say. I think that any further action on the existing work should be delayed until that time.

Right now I can say that we drop the side meeting plan and replace it with SAAG presentation on Thursday July 25.
Those who are attending IETF 105 please make sure to be there at the SAAG meeting.
SAAG meeting attracts a large audience, usually SEC area WG chairs shortly present their sessions, and some additional presentations like proposed BOFs.

Regards,
Behcet

v2.23.0 | Report a Bug | By Email