Re: [ipwave] Éric Vyncke's Discuss on draft-ietf-ipwave-vehicular-networking-28: (with DISCUSS and COMMENT)

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Sat, 25 June 2022 07:08 UTC

Return-Path: <evyncke@cisco.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB7C0C15AAC3; Sat, 25 Jun 2022 00:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.607
X-Spam-Level:
X-Spam-Status: No, score=-7.607 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URI_DOTEDU=1.999, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=FjbdHU6p; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=RSK7MhqA
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fGFBgxitKA8j; Sat, 25 Jun 2022 00:08:08 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F5C5C15A75D; Sat, 25 Jun 2022 00:08:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=45513; q=dns/txt; s=iport; t=1656140888; x=1657350488; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=QAHLOF8NBvNmv8CadN87VN9UGeMG0YeCZRKrZMs8jV0=; b=FjbdHU6pRBw1eO/pIT8uK5+jyg9c0PukbnokWzoJIOPRidt9WNZEiuhu qcph0EuuI5S855s5npSH3/TB3Beizrd+D2el9esFDQoFsh5xNdPL98Xpp GmyWWeMRqrbJS+XGEnkWvAVpvM8eZfcUcnseAgFCz1l3cVBIOnQokKwuQ 4=;
X-IPAS-Result: A0AAAQBVs7ZimI0NJK0+HIJYgSExUn8CWTpEhE6DTAOFMYULXYIlA4EpiXOFNYp1gSwUgREDTwIDCwEBAQ0BASwBDgcEAQGDTYE2AhaFNAIlNAkOAQIEAQEBAQMCAwEBAQEBAQMBAQUBAQECAQcEFAEBAQEBAQEBCRQHBgwFDhAnhWgNhkIBAQEBAwEBEAgJHQEBKQMLAQ0CAgEIEQECAQIhAwQDAgICFAsGCxQDAwMIAgQBDQUWBQeCWwGCDlcDMAMBDkWeRAGBPwKKH3qBMYEBgggBAQYEBIE7AgELAgJAAYMADQuCOAkFgTiDFoMIgS0BAYEngUCCPwqBeyccgUlEgRUnHIJnPoIgQgEBAQEBgSgBDAYBBzEJDAEJgyA3gi6CX4o0hFyHUQc4AxotLxKBIG4BCAYGBwoFMAYCDBgUBAITElMcAhIFBwobDhQcJBcMDwMSAxEBBwIJEggVKwgDAgMIAwIDIAsCAxYJBwoDHQgKHBIQFAIEER4LCAMZHiwJAgQOA0AICwoDEQQDExgJFggQBAYDCC8NJwsDBQ8NAQYDBgIFBQEDIAMUAwUkBwMhDyYNDQQbBx0DAwUlAwICGwcCAgMCBhUGAgJuLg0IBAgENyQPBQIHLwUELwIeBAUGEQgCFgIGBAUCBAQWAhAIAggnFwcTGBsZAQVZEAkhHCkKBgUGFgMjbgUKOw8oNDY8EBwfGwqBGiwrFgMEBAMCBhwDAyUCEi0GDAYiAR2WJYQ2LCcYBQEBATwQFgQiFgMQBgEBAgIeDSEHBAINEQQGBSYVDwseBQEBAQ4CARELCAE8A5IQBhmCdAFGigONRUeSH2sKg06LII53BIV6BC2DdYFQinMDhl+DQIp5gxGWcCCCK4cXg06DXJB9ARiEcgIEAgQFAg4BAQY1gRkTgSVwcBU7KgGCCQEBATEJSBkPhD6JQDsegztqhCqFSnUCOQIGAQoBAQMJAYI6hAyFc4JHAQE
IronPort-PHdr: A9a23:H4negR+3+OW1B/9uWCXoyV9kXcBvk7n3PwtA7J0hhvoOd6m45J3tM QTZ4ukll17GW4jXqpcmw+rbuqztQyoMtJCGtn1RfJlFTRRQj8IQkkQpC9KEDkuuKvnsYmQ6E c1OWUUj8Wu8NB1eGd31YBvZpXjhhQM=
IronPort-Data: A9a23:BdHNVqxjKJk/DiSEpEN6t+eWxirEfRIJ4+MujC+fZmUNrF6WrkUGy WcfWTvTOv7YYGT3Lo12Ptix8x5Q7ZbTzYJmSwM5r1hgHilAwSbn6Xt1DatR0we6dJCroJdPt p1GAjX4BJloCCea/H9BC5C5xZVG/fngqoHUVaiVYEideSc+EH170Uw5xrZj6mJVqYHR7z2l6 IuaT/L3YDdJ6xYsWo7Dw/vewP/HlK2aVAIw5jTSV9gS1LPtvyV94KYkGE2EByCQrr+4sQKNb 72rILmRpgs19vq2Yz+vuu6TnkYiGtY+MeUS45Zbc/DKv/RMmsA9+o8nascWMElXsSSYtoBhz vNfn7q/Dhh8a8UgmMxFO/VZOyh6OasD87jdLD3v98eS1EbBNXDrxp2CDmlvYtZeobgxWDoIr KBBQNwORkjra+aezayqTOJvi+woLdLgO8UUvXQIITTxXah5EMySHPSRjTNe9Bdq2/0WI+yOX pUcYx0zYlfAOBwfKH5CXfrSm8/x1iWgLFW0smm9pLYsy2ne0AI316LiWPLUd8eFbcRYgkjeo XjJl0z1CxcbOdjZzDuK+2+omsfChyLwQ5kVEvuz8fsCqEWa22hVFxoLSVahutGwi1CzXZReL CQ84Tc2oLIv70GxZtb4Vhy85nWDu3Y0UsBdD+Q84UeMx7baywmcD2kACDVGbbQOsMYsXhQn2 VCEhc+vAiZg2JWPRX61/bqOsXW1Iyd9BW0LaC8DSg1D+9D+pKk8ixvOSpBoF6vdszHuMTj0x zbPpy8kivBDy8UKzK68u1vAhlpAu6QlUCYc+lvqVDur7jlodaf1d4qO+3L94rFfedPxoka6g FAInM2X7eYrBJ6LlTCQTOhlIF1Pz6vYWNE7qQMzd6TN5whB6Fb4JtkJv28WyFNBd5daJ2C4O Sc/rCsLvPdu0G2Wgbibim5bI+0uyaXmfTgOfq+JNoMVCnSdmfPuwc2DTUeU22aom082nORvf 5yaas2rS30dDMyLLQZapc9AjtfHJQhnmAs/oKwXKTz8jdJyg1bOE9843KOmNLxR0U99iFy9H yxjH8WL0Q5Dd+b1fzPa94UeRXhTcyVlXcGr95cKLb7eSuaDJI3HI6KOqV/GU9E495m5as+Tl p1AchYCkQGm1SGvxfuiMys9ONsDoqqTXVpibXBzYj5EKlAoYJ2k6+8EZoArcLw8nNGPPtYqJ 8Tpj/6oW6wVIhyeomx1RcCk8ORKKUT67SrTbnHNSGVuIPZIGVeTkve6JVSHycX7Jnft3SfIi +f+hlqzrFtqb1kKMfs6n9rylAzq5yhFxIqfnSLge7FuRakly6AyQwSZsxP9C5hkxcnrrtdC6 zurPA==
IronPort-HdrOrdr: A9a23:AQpJPKAUuYplbmjlHegZsceALOsnbusQ8zAXPh9KJyC9I/b2qy nxppgmPEfP+UossHFJo6HlBEDyewKiyXcV2/hcAV7GZmjbUQSTXflfBOfZsl/d8mjFh5NgPM RbAudD4b/LfCNHZK/BiWHSebtBsbq6GeKT9J3jJhxWPGZXgtRbnn5E43GgYytLrWd9dP8EPa vZwvACiyureHwRYMj+LGICRfL/q9rCk4+jSQIaBjY8gTP+ww+A2frfKVy1zx0eWzRAzfMJ6m 7eiTH04a2lrrWS1gLc7WnO9J5b8eGRi+erRfb8yvT9GA+cyDpAV74RHoFqewpF5N1H3Wxa0+ UkZS1QePibpUmhOF1d6iGdpTUImAxemkMKj2Xo2EcKZafCNWkH4w0rv/MATvKR0TtSgDk3up g7r16xpt5ZCwjNkz/64MWNXxZ2llCsqX5niuILiWdDOLFuI4O5gLZvtX+9Kq1wVB7S+cQiCq 1jHcvc7PFZfReTaG3YpHBmxJipUm4oFhmLT0AesojNugIm0UxR3g8d3ogSj30A/JUyR91N4P nFKL1hkPVLQtUNZaxwCe8dSY+8C3DLQxjLLGWOSG6XXp0vKjbIsdr68b817OaldNgBy4Yzgo 3IVBdCuWs7ayvVeLuzNV1wg2fwqUmGLEHQI5tllupEU5XHNc7WDRE=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.92,221,1650931200"; d="scan'208,217";a="867949793"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Jun 2022 07:08:06 +0000
Received: from mail.cisco.com (xfe-rtp-003.cisco.com [64.101.210.233]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 25P7861v010025 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Sat, 25 Jun 2022 07:08:06 GMT
Received: from xfe-rtp-002.cisco.com (64.101.210.232) by xfe-rtp-003.cisco.com (64.101.210.233) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14; Sat, 25 Jun 2022 03:08:05 -0400
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xfe-rtp-002.cisco.com (64.101.210.232) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14 via Frontend Transport; Sat, 25 Jun 2022 03:08:05 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Jyoy9GFpKNixwkVcOGBVSNusmuiI1ENu+vz1wBGMLf/xI2SKJril0xhLKEdr9KM86P1bTKUj7cwS3inlZXhSeH/YR7InUezwTGwMpwX9RZ7ZQymbGCxv54lvznNm3QSlYvdYHr1FoKNA6NzCBTJ1mEN30EozwhXPxPdHYNmQGT3Cw5vRcBlyUZafojgcLIJbOERhX+Nf9GYVdUsD39u+JKsE0cIwFFy2ekJeszQBxHPYNS7dbRxsOskVPdafLzQMOHcdMTLbQDHTOe0RHZu13a82XJEdGD2pThWwn0aMWAkHzKKKkkWKEX+WHEoQNO43pTkm6d76hrwFv0Er6Jz+Sw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=QAHLOF8NBvNmv8CadN87VN9UGeMG0YeCZRKrZMs8jV0=; b=A9zNLxtw6yMQIiLjD7vIhFYwe3miPMMp0XTzOiBrG71M3ckka1Pjw/umWXnuug5FXuxYIXxMHz3eJSzw5/5eeES57VH+HzIz6iUe/oV99uykCnODLbpjsi9RdTZ1Misor+q9ZR0Y7bOrnXUvjQBAbLgIKKJGVbau6cFtYiqOBjjq2C7WfH/tPXNyO08NH2JQC1HgFayGimBYN4ete2jDrkYyg2er8hc81LOLGPgbrGYG8c/zTkj7hFZzQM18XyEV3Qa1BrULi6XUH/YrLA0355WtsLFrYtcaD/P1VHDzaiDnvI8rbfNtmtm5Gefw/VmANNTNfIyO2JGgrbUd8dxvYQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QAHLOF8NBvNmv8CadN87VN9UGeMG0YeCZRKrZMs8jV0=; b=RSK7MhqA6byouFTXOzwV944RttdMyDJt62RcNmL3alBRrCitFK/Qjmomqwk6O+YamOMxF/OsSlRc4p75My5G7bxNc6geqEhRI/djb+jcxnwkuTk2tbvMRLwLE5RjKQMPluOqiOj73COXO7wFEhsQmgaEQN0JxC6mRuBI6O8JDJc=
Received: from PH0PR11MB4966.namprd11.prod.outlook.com (2603:10b6:510:42::21) by BN6PR11MB1331.namprd11.prod.outlook.com (2603:10b6:404:49::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5373.15; Sat, 25 Jun 2022 07:07:58 +0000
Received: from PH0PR11MB4966.namprd11.prod.outlook.com ([fe80::3891:c0c9:3d21:bfe7]) by PH0PR11MB4966.namprd11.prod.outlook.com ([fe80::3891:c0c9:3d21:bfe7%6]) with mapi id 15.20.5373.018; Sat, 25 Jun 2022 07:07:58 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, Roman Danyliw <rdd@cert.org>
CC: Lars Eggert <lars@eggert.org>, Alvaro Retana <aretana.ietf@gmail.com>, Murray Kucherawy <superuser@gmail.com>, Paul Wouters <paul.wouters@aiven.io>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, Daniel Migault <daniel.migault@ericsson.com>, The IESG <iesg@ietf.org>, "its@ietf.org" <its@ietf.org>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>
Thread-Topic: [ipwave] Éric Vyncke's Discuss on draft-ietf-ipwave-vehicular-networking-28: (with DISCUSS and COMMENT)
Thread-Index: AQHYa7cyK7/CrRmQo0iWtGKP79INwa1I3scAgBa7aYCAAHR/AA==
Date: Sat, 25 Jun 2022 07:07:58 +0000
Message-ID: <8B0CAC81-C4EC-44B4-B3DD-3B1FA168C8E3@cisco.com>
References: <164922662907.16687.3467089534808946908@ietfa.amsl.com> <CAPK2DezzymMEiQVtGeAc4RK7Bdn6Hw34cgW_s_1cOeZCt2bE9w@mail.gmail.com> <CAPK2DezFQMt8x5XUmEPDTv-hdssm1JvEpxzWWozoFCkQTxNCvw@mail.gmail.com> <CAPK2DewL=z4PDkjhCgTi0WnV2eZ5K6i5ZQZd9GB4QCxx=oNMzg@mail.gmail.com>
In-Reply-To: <CAPK2DewL=z4PDkjhCgTi0WnV2eZ5K6i5ZQZd9GB4QCxx=oNMzg@mail.gmail.com>
Accept-Language: fr-BE, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.62.22061100
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=cisco.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: aecc4040-475a-49aa-ea5a-08da56796f4c
x-ms-traffictypediagnostic: BN6PR11MB1331:EE_
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: CDJDQTWAChnjmM2VZOHbceNYLmNOptxBRPsrF0Fci17cEH4YfL4kXdaBHcP+xX6tM3cRvQxqTUORNYvfRkOEipukDlVbJzhyK18l5kakaUznFOK5i/HOo9S34hBJrRlTfwZXdfqnatL5PM6M1V5U+hFB48pFsA57yWyUGgCIvQf51FCkV1Ky0e+6e9++tMiMTQJqumOFMA6qmmWjzQFwCYrx/UNrk6n4fRtw//hIH5lBLlfMO9Z4FBXdlXEzEbWouCO4A3Quo93F57hRQy1/8hbLJb3PkOjo+yLrYO4xcV6Qlzr+B24A0EARiQfXPoT8xNwr/VoiRF16ptI1QyMlyTr+dOFtNvcpYyojyl7G0ye9QO9CJqZG4h5ZTnBem5+8ZRklH2wGQTzcAJnnnBjJ7dbaMaackPfHfb2goypAGW8nwovdqCq2kw330GC3dbjB7/0aE3GDX2Nnb1xDZTNfsBoRWdqrSLorRiWk8o14SzFNp8o4G7TpKbTvbnxZI6ovpSqWEOSM/C0TnMXCcZfGGYvK+vgMgS8YjtjYnKoQbbGDlUGG5O6SI9l0Pzi36K6cGYCMxBuwmIx/nGfXeRXqVvssMmuv0M6wUKHykPJHfCEeIl+jMWdkSac7GPWvGGmyybn0oMB6fGh2NOi3vx4cEBw9dJjzxEaMW+uDQS2rYgJ1nRx/4QrSVU4M6GQy/4bue8HquCzUV5wEUKoxZi5kbgcVklraenYwx8eNjI8Og7lAy/hzdXP7QCyWRA1WZxWz0xVgHUqIh2a07io7Z73OOsfIVGQifWCO/COEhR9vycCvr15qt0M53dlauENsIccJqB/HxjUWkOgW5wkznR5VbYAaaVkFI8L79qhF3rHLYrIKLJe4/FUOmC2O5ijUzIYRMcTtk5mYuVHQL5WcKaUn3w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:PH0PR11MB4966.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230016)(4636009)(366004)(136003)(346002)(39860400002)(376002)(396003)(8936002)(966005)(64756008)(83380400001)(4326008)(33656002)(38070700005)(5660300002)(91956017)(186003)(86362001)(66476007)(107886003)(71200400001)(30864003)(6486002)(478600001)(66946007)(66446008)(2906002)(41300700001)(2616005)(76116006)(6506007)(316002)(38100700002)(6512007)(15188155005)(122000001)(66574015)(53546011)(66556008)(166002)(224303003)(36756003)(110136005)(16799955002)(54906003)(45980500001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: uj/o9qDly/vHE5AGsC0/qeYQwgj51RXFQmKUjrCzXLKCvwnwIatkywfUvQhbdWxnjAvtkmh58PukU4br5StBrVQWOFTBJSS5Z6DWAu1OuBWDVDMqEwZUzc/XRWGAf9zs4R/vKUb5pJvAHbDWqMdXzzmvJwf7sxNYCKAu9xquvg6++AqLftsqDMT5Fd6s5zP/J88jO43ByMG5QuOi4lq46NYBpS3mzGAQSHkoiXh/AuTthvKzhSBaTtYXiYogf5ru0y76/ib49gCRfsusyuoK3Vy/4N3IO/aiA1LE5n45QfMwoNhma8ruIOg3upO7XpB85ptXPRNXuXCocwETFi750UTG72+M35dQVGwQwTQWRAclNwwUVdt2iERtwI1wpPALh5DbhVtDvWz/VknRgaqWXWipb6c7KBvh7RtBNcohqntpXk4kQt9OQNXChHEL3ZvNp8OLZGvD167LQCpyU04zYvCv7TA84/QQYVW9kd+oAfcEjAqrJx09Q/Kk8nkldv3YyoeZNF0Ppves26W5PExt7QlXOHWM2irENg75BH7EuwB/VcvAvGyHeN9EUErCMDxC1/ZussJunRI3raRBIrUytL1eteZyc/hpCXzudmdSgtmpIxZwaIgZhj9IcmnZdfA7xxzBjajKQGtTBK8dyimxOAALoYj33KG/rY9kwu5YKgWwZf8iB61rPzouoqS5jEEPg8xiDpBWDXRNWa+NMwb79F2OsLcfSeBTeXHxfc3GaM2wIUHFXiCP7NYnDt4HuBKT9jep1yTe7kSK4k7k0TdZGGvDd/02YhdKtgcPA8tKCeqaWzWHqnfzi6w91POzv8SOGjb2b1beQR+FF0YLQ2LcCraZSKJS4LSnJ2vZdaeOXWgx/b+ENbKwfKC4l+ZDCi6gvO+S6iLY8FWt0Q4C+n5b2NbvZxoleYTL39Tw8I3fwFoe2e5n8Ygz5s6IWW9mdCO0rFYQtCvRu6Xh1wU6rPAoMtl/kfOp1WYMprqToYrd/Vj75lSQzdSCh9ev2ubUjtolA1dIuefTvnrHjlFVV4j3qnJt00p9mO3bXseXSw7Rx0SErcoVLCTBFc5Symz7OoamR/OM0zUlI3Q6liPY4yYZhuEWSxNg16tEJH8GnW6PzspLJqSCamRLpwmwQBfWf5fTaaDJWzcCzssM37Ktjjx8ZNhHEU/UT+B0Whn9aCAco+gFvwhbBXCvBoLrADlbUtnQQYklCTi9qSTd0ZzvDOxx873ymG0emMU1UjKBqAecLHBSg9hVP1fEeZUK22N/oK0p7dGt58iIt+qIjSaUVHI1PmLCLl9fLg5DnzdF5/Spv4s8hOaZSf5d5U+Q9w6snIFjOGlFoBXWzBPKAHOjZxhEZbwqTxby3334LAeE6FBViMl3B9qNlL0mrYsnIJqbbwVSWAbmOtGZdLVkJuxIAz4ZRyiIW4KwWV5ViSeVepumhAIss9m39dWplEnwIlPqFSkxeHYfoBEuebaltCi0aEotUHk52BEkZfuMRgbJgAItjSpABIV/Un5gy89uf3E1oclKkxWtyiQTkvZBIci7st8gBNce33d2wdxm2UM9ZqUiTU5ChSsotw6pIHx0lAIt2U0rscKo1w5cFu0yMnbj3t6S9xUstltqlJV6W+RHTGkd8qQ3zV8HvtbEgTSBJhVIn4ZL
Content-Type: multipart/alternative; boundary="_000_8B0CAC81C4EC44B4B3DD3B1FA168C8E3ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PH0PR11MB4966.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: aecc4040-475a-49aa-ea5a-08da56796f4c
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jun 2022 07:07:58.4064 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: T9wvMdszkjsPGaRs5xsuY1+HMk9gdzrU5jAd8BnrMLzVlCKLvMI9GXAARGI3vy8BBwi0437Fhn4VF+B47a8ZrA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1331
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 64.101.210.233, xfe-rtp-003.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/-XquuB-LRdPSlkbOO6ReQyP7qvU>
X-Mailman-Approved-At: Sat, 25 Jun 2022 05:43:01 -0700
Subject: Re: [ipwave] Éric Vyncke's Discuss on draft-ietf-ipwave-vehicular-networking-28: (with DISCUSS and COMMENT)
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2022 07:08:13 -0000

Paul,

Sorry for belated reply, your revision letter seems to address all my DISCUSS and most of my COMMENTs (still remaining the non-blocking COMMENT in section 6.1 about using IPv6 SEND to protect against DAD flooding – non blocking so you can safely ignore it).

As soon as the revised I-D is uploaded with the proposed changes, then I am clearing my DISCUSS.

Regards

-éric


From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Saturday, 25 June 2022 at 04:11
To: Eric Vyncke <evyncke@cisco.com>, Roman Danyliw <rdd@cert.org>
Cc: Lars Eggert <lars@eggert.org>, Alvaro Retana <aretana.ietf@gmail.com>, Murray Kucherawy <superuser@gmail.com>, Paul Wouters <paul.wouters@aiven.io>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, Daniel Migault <daniel.migault@ericsson.com>, The IESG <iesg@ietf.org>, "its@ietf.org" <its@ietf.org>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Subject: Fwd: [ipwave] Éric Vyncke's Discuss on draft-ietf-ipwave-vehicular-networking-28: (with DISCUSS and COMMENT)

Hi Éric and Roman,
Though you guys seem very busy with other stuffs, could you check whether my revision is satisfying your DISCUSS or not?

I hope this IPWAVE PS draft moves forward and IPWAVE WG will be able to take the next step.

Thanks.

Best Regards,
Paul
---------- Forwarded message ---------
From: Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>>
Date: Sat, Jun 11, 2022 at 12:02 AM
Subject: Re: [ipwave] Éric Vyncke's Discuss on draft-ietf-ipwave-vehicular-networking-28: (with DISCUSS and COMMENT)
To: Éric Vyncke <evyncke@cisco.com<mailto:evyncke@cisco.com>>, Lars Eggert <lars@eggert.org<mailto:lars@eggert.org>>, Roman Danyliw <rdd@cert.org<mailto:rdd@cert.org>>, Alvaro Retana <aretana.ietf@gmail.com<mailto:aretana.ietf@gmail.com>>, Murray Kucherawy <superuser@gmail.com<mailto:superuser@gmail.com>>, Paul Wouters <paul.wouters@aiven.io<mailto:paul.wouters@aiven.io>>, Robert Wilton <rwilton@cisco.com<mailto:rwilton@cisco.com>>, Daniel Migault <daniel.migault@ericsson.com<mailto:daniel.migault@ericsson.com>>
Cc: The IESG <iesg@ietf.org<mailto:iesg@ietf.org>>, Pascal Thubert <pthubert@cisco.com<mailto:pthubert@cisco.com>>, CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es<mailto:cjbc@it.uc3m.es>>, <its@ietf.org<mailto:its@ietf.org>>, Chris Shen <shenyiwen7@gmail.com<mailto:shenyiwen7@gmail.com>>, skku-iotlab-members <skku-iotlab-members@googlegroups.com<mailto:skku-iotlab-members@googlegroups.com>>, Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>>


Hi Éric, Roman, Lars, Alvaro, Murray, Paul, Robert, and Daniel,
Let me remind you of the revision of the IPWAVE Problem Statement Draft:
https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-vehicular-networking-29

Zahed gave me his comment, and I will reflect it on version -30.

Could you review my revision on your comments and update your position as soon as possible?
Thanks for your valuable comments and help.

Best Regards,
Paul

On Fri, May 20, 2022 at 4:31 AM Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>> wrote:
Hi Éric, Lars, Roman, Alvaro, Murray, Paul, Zaheduzzaman, Robert, Daniel,
Here is the revision of the IPWAVE Problem Statement Draft:
https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-vehicular-networking-29
I attach a revision letter to explain how Chris and I have addressed
your comments on the revised draft.

If you have further comments or questions, please let me know.

Thanks for your valuable comments and help.

Best Regards,
Paul
--
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department Head
Department of Computer Science and Engineering
Sungkyunkwan University
Office: +82-31-299-4957
Email: pauljeong@skku.edu<mailto:pauljeong@skku.edu>, jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php<http://cpslab.skku.edu/people-jaehoon-jeong.php>


On Wed, Apr 6, 2022 at 3:30 PM Éric Vyncke via Datatracker <noreply@ietf.org<mailto:noreply@ietf.org>> wrote:
Éric Vyncke has entered the following ballot position for
draft-ietf-ipwave-vehicular-networking-28: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-ipwave-vehicular-networking/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thank you for the work put into this document. I found the use cases part of
section 3.1 very interesting to read even if some of them seem very far fetched
;-)

Please find below some blocking DISCUSS points (easy to address though), some
non-blocking COMMENT points (but replies would be appreciated even if only for
my own education), and some nits.

Special thanks to

- Carlos Bernardos for the shepherd's write-up even if a justification for the
informational status would have been welcome but the WG consensus description
is appreciated.

- Pascal Thubert for his IETF last call INT directorate review at:
https://datatracker.ietf.org/doc/review-ietf-ipwave-vehicular-networking-20-intdir-lc-thubert-2021-06-18/
and for his IESG telechat INT directorate review
https://datatracker.ietf.org/doc/review-ietf-ipwave-vehicular-networking-27-intdir-telechat-thubert-2022-02-28/
Pascal's Last Call & telechat reviews were (at least partially) acted upon by
Paul ;-)

I hope that this helps to improve the document,

Regards,

-éric

# DISCUSS

As noted in https://www.ietf.org/blog/handling-iesg-ballot-positions/, a
DISCUSS ballot is a request to have a discussion on the following topics:

## Abstract & Section 1

"then enumerates requirements for the extensions of those IPv6 protocols" does
not match any IPWAVE WG work item, i.e., it is outside the scope of the charter
of IPWAVE WG. As the document does not explicitly specify requirements, I
strongly suggest to use the word "gaps" rather than "requirements" in the
abstract and section 1.

## Section 4.1

Using an IPv6 address out of a ULA prefix still requires DAD. So the text below
should be updated to be corrected:
  "their own IPv6 Unique Local Addresses
   (ULAs) [RFC4193] over the wireless network, which does not require
   the messaging (e.g., Duplicate Address Detection (DAD)) of IPv6
   Stateless Address Autoconfiguration (SLAAC) [RFC4862]."

## Section 4.2

Very similar comment as above (i.e., DAD & MLD must be done for all IPv6
addresses of an interface and not only for the global one):
  "... When global IPv6
   addresses are used, wireless interface configuration and control
   overhead for DAD"

## Section 5.2
  "... If DHCPv6 is used to assign
   a unique IPv6 address to each vehicle in this shared link, DAD is not
   required. "
This is incorrect and must be changed (see section 18.2.10.1. of RFC 8415)


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


# COMMENTS

"100km/h as the speed limit in highway" will make many European drivers smile
as it is really slow...

## Section 1

"Most countries and regions in the world have adopted the same frequency
allocation for vehicular networks." but there are TWO frequency allocations
described just before, so, which one has been adopted ?

## Section 2

"GPS" is just the USA commercial example of the more generic "global navigation
satellite system" (GNSS), GNSS should be used in this document.

As IP-RSU have at least 2 interfaces, should "Also, it may have *the* third
IP-enabled wireless interface" be replaced by "Also, it may have *a* third
IP-enabled wireless interface" ?

LiDAR ... "by measuring the reflected pulsed light" but on which kind of
metrics ?

## Section 3.1

Should the 1st and 5th bullets be grouped together ?

Please describe "UAM" (e.g., in the terminology section) as it is unclear to
the reader whether it is a crewed / uncrewed aircraft.

If both road and air vehicles are use case, what about river / sea ships or
trains ?

Does the paragraph about "reward system" belong to the use case ? It rather
sounds like a business requirement. Suggest to remove this part.

Like written by Pascal Thubert in his telechat review, the last paragraph
"IPv6-based packet exchange and secure" should be clear that this is not only
about data plane traffic but also control plane L2/L3 ones. Please also use the
Oxford comma, i.e., add a "," after "exchange".

## Section 3.2

Suggest to also mention "5G" after "IP-RSU or 4G-LTE networks"

How is the UAM use case different from a driverless terrestrial EV ? Suggest to
merge those use cases.

## Section 4.1

As noted by other ADs, "Existing network architectures," the list should not
include OMNI yet as it is not deployed and would probably not be described as
an architecture.

"the wireless media interfaces are autoconfigured with a global IPv6 prefix",
is it the same shared prefix or multiple prefixes ?

Is "RSU" the same concept as "IP-RSU" ?

The last paragraph is about TCP session continuity, but does not explain why
multi-path TCP or QUIC session resumption cannot be used.

## Section 4.2

The computation about "dwell time" is interesting even if it is computed in the
best case. But, I really wonder whether using IPv6 and routing are applicable
to the use case as opposed to more layer-2 + tunnel solutions (like 3GPP) with
such short time for hand-over. I am a strong supporter of layer-3 (IPv6 and
routing), but I cannot refrain from thinking that IPv6 is the wrong technical
solution for those use cases... Was this discussed in the WG ?

## Section 5.1

What is "legacy DAD" ?

  "...the NA interval needs to be
   dynamically adjusted according to a vehicle's speed so that the
   vehicle can maintain its neighboring vehicles in a stable way"
With the issues linked to multicast over wireless, are the authors and the WG
sure that increasing the amount of multicast will not aggravate the problem ?
See RFC 9119 (cited as a normative down reference)

## Section 5.1.2

Please add some references to the MADINAS WG current work items. The authors
may also consider adding this use case to the MADINAS use case.

"The pseudonym of a MAC address affects an IPv6 address based on the MAC
address", nearly no implementations use EUI-64 anymore so this part should
probably be removed from the document. But, the change of MAC address probably
has other impact on the IP stack, e.g., the neighbour cache.

## Section 5.1.3

AFAIK, RPL relies on messages to discover the topology and I am afraid that in
such a moving / dynamic environment, there will be too many of RPL messages.
Will RPL scale in this ever changing network ? Please note that I am not a RPL
expert.

## Section 6.1

Some explanations on how SEND protects against DAD flooding would be welcome.

Is "classical IPv6 ND" the same as the previously used "legacy ND" ?

Wondering why "Vehicle Identification Number (VIN)" is suggested to be used as
SubjectAltName in a certificate rather than a car manufacturer cert ?

## Section 6.3

The part about bitcoin and blockchain errs probably too far away from the IETF
remit.

## Appendix B

I fail to understand how RPL and OMNI can be compared as they are vastly
different technologies (routing vs. tunneling).

"In OMNI protocol, each wireless media interface is configured with an IPv6
Unique Local Address (ULA)" but from my last read of OMNI drafts (1+ year ago),
the OMNI virtual interface can have a ULA indeed but the wireless physical ones
are using any prefix.

## Appendix D

What will be the impact of high packet loss rate (that I am expecting on such
networks) on IP parcels ?

# NITS

Please check that all IPv6 addresses are in lowercase (e.g., in section 4.1).



_______________________________________________
its mailing list
its@ietf.org<mailto:its@ietf.org>
https://www.ietf.org/mailman/listinfo/its