Re: [IPv6] WG Last Call on draft-ietf-6lo-multicast-registration-11

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 21 November 2022 13:11 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 492F3C1524B0; Mon, 21 Nov 2022 05:11:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.896
X-Spam-Level:
X-Spam-Status: No, score=-11.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Wdc+a6QM; dkim=pass (1024-bit key) header.d=cisco.com header.b=PNgrdmKV
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 jORkJFrLdKRD; Mon, 21 Nov 2022 05:11:40 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C514CC1524AF; Mon, 21 Nov 2022 05:11:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14188; q=dns/txt; s=iport; t=1669036299; x=1670245899; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=u+TD/1nac1rWK2Cnyrue8+IAogzZTe/6yV4U26ZTN4g=; b=Wdc+a6QMYsizd4bFMujyaxfBxWAdEZyU5qygkqTsbHUPt8T4Un+3V2pY +PSXiQxbO6mDrzKjyt86aNIFNEl77grjgJr7YCCDC0Ne6yMMjrKvgauFK vpZJax5uOn4ZEYi50MPQNjTjXnytdNBVvj/Edr6ZS5En3gOO9yA1LwMPt A=;
X-IPAS-Result: A0ADAAA1eHtjmJtdJa1aDgwBAQEBAQEBAQEBAwEBAQESAQEBAQICAQEBAUCBOwUBAQEBCwGBWlKBAgJZOkWEToNMA4RQX4gcA4s3kE6BLBSBEQNWDwEBAQ0BAS4LCwQBAYFTgzICFoRrAiU0CQ4BAgQBAQEBAwIDAQEBAQEBAwEBBQEBAQIBBwQUAQEBAQEBAQEdGQUOECeFaA2GUwEBAQECAQEBEBEEDQwBASwLAQQHBAIBBgIRBAEBAQICCAEaAwICAh8GCxQBCAgCBAENBQgaglsBgm4DDiMDAQ+YUo88AYE/Aoofen8zgQGCCAEBBgQEgTgBFUGaOg2CRgMGgRQsAYcsA3Rcg0kXhDAnHIFJRIEVQ4JnPoIgQgEBAgGBHwQRCyCDVTmCLotWgktYgROBaYVxHDcDRB1AAws7MgpKG1gOCR8WBg4XDQUGEgMgRiYFQQ8oLgFnIgkcGweBDCoJHxUDBAQDAgYTAyACDSkxFAQpEw0rJ28JAgMiZQUDAwQoLAMJIAQcBxYRJDwHVhIoAQQDAg8gOAYDCQMCJFZzCyUmBQMLFSUIBUsECDkFBlISAgoRAxIPBiZGDkg+ORYGJ0IBMQ4OFANegWkENUiBKQoCmHh3gSsQWwYwDiYEUQIgLQIBCyoTAhYqERcUJzqSKAiDWJhGkXSBCG4Kg2iLTY8AhiMWg3iMVIZnkQVelzQgjSODaZEOhRUCBAIEBQIOAQEGgWI6gVtwFRohgmdSGQ+OIAwNCYNQhRSFBUV1AjkCBwEKAQEDCYgJglkBAQ
IronPort-PHdr: A9a23:IavVphDNHSweFiKNCKWtUyQVaBdPi9zP1kY95pkmjudIdaKut9TnM VfE7PpgxFnOQc3A6v1ChuaX1sKoWWEJ7Zub9nxXdptKWkwJjMwMlFkmB8iIQUTwMP/taXk8G 8JPHF9o9n22Kw5bAsH7MlbTuXa1qzUVH0aXCA==
IronPort-Data: A9a23:cllquqwCRgUyhTPTW6N6t+cIxirEfRIJ4+MujC+fZmUNrF6WrkUHm GVNWD3TPf+KMGanLt0jaIy/9xtT7Mfdz9RnSlRkq1hgHilAwSbn6Xt1DatR0we6dJCroJdPt p1GAjX4BJloCCea/H9BC5C5xZVG/fngqoHUVaiVZEideSc+EH170Es5wrZg6mJVqYHR7z2l6 IuaT/L3YDdJ6xYsWo7Dw/vewP/HlK2aVAIw5jTSV9gS1LPtvyV94KYkGE2EByCQrr+4sQKNb 72rILmRpgs19vq2Yz+vuu6TnkYiGtY+MeUS45Zbc/DKv/RMmsA9+qo9FqQcdUNOshKilYlY6 Phq9re+axh8a8UgmMxFO/VZOzt1MasD87jdLD3j98eS1EbBNXDrxp2CDmlvYtZeobkxUDoIr KFFQNwORkjra+ae2K67V+NhnNgLJ8jwN4RZsXZlpd3cJat8G8mTGvSiCdlw0DgLp5pwEPTkS OlAYyRQTiycYB1jNQJCYH45tL742iagG9FCk3qUvbRpy2ne0AI316LiWPKLftuiRMhJkACfv G2u12/wGBUXL5qQzj+I4FqxnuSJkC/mMKoXHae75Ox4m1iS2mw7BxgfVF/9qv684ma/Vs5RI GQe5iEpq64//1DtRd74NyBUu1aetRIaHtFXCeB/tEeGy7Hf5ECSAW1soiN9hMIOuMkUGzw20 kawuPjjXBVPnZrWYny/6eLBxd+tAhQ9IWgHbC4CaAIK5dj/vY0+5i7yosZf/L2d1YekRW6qq 9yehG1v2epL15FjO7CTpwivvt66mnTeoufZDC3tX2ml5xl1f4mjD2BDwQeGtaYZRGp1o6Xog ZTps9KV4OZLBpaXmWnRBu4MB7quof2CNVUwYGKD/bF/rFxBGFb6Lei8BQ2Swm8zbK7onheyO yfuVft5vsM7AZdTRfYfj3iNI8or17P8Mt/uS+rZaNFDCrAoKlHXrX8/PRTAjzy0+KTJrU3ZE crFGSpLJStKYZmLMBLtLwvg+eZxn3tnlT+7qW7Tlkz9jdJym0J5uZ9cYAfRMYjVHYuPoR7e9 J5EJtCWxhBEONASkQGJmbP/2WsidCBhbbiv8pQ/XrfafmJORjp7Y9ePmuxJRmCQt/kP/gs+1 ivjChYwJZuWrSCvFDhmnVg5NuiwDM4j8SxmVcHuVH7xs0UejU+UxP93X/MKkXMPrYSPEdYco yE5Rvi9
IronPort-HdrOrdr: A9a23:DSs61aviP1ARPjz7MFVTTRJB7skC1IMji2hC6mlwRA09TyXGra 6TdaUguiMc1gx8ZJh5o6H+BEGBKUmskaKdkrNhQ4tKOzOW9ldATbsSorcKpgeAJ8SQzJ8k6U /vGZIOc+EYYWIK7/oSpTPIb+rIo+P3sZxA592utUuFJDsCA8oLgmcJaTpzUHcGOTWubqBJc6 Z0k/A33gZIDk5nCPhTaEN1OtTrlpnurtbLcBQGDxko5E2lljWz8oP3FBCew1M3Ty5P6a1Kyx mEryXJooGY992rwB7V0GHeq75MnsH699dFDMuQzuAINzTXjBqybogJYczAgNl1mpDs1L8Zqq iJn/4SBbU115oXRBDynfLZ4Xik7N/p0Q669bbXuwq6nSWzfkNKNyMIv/MoTvKe0Tt6gDm5u5 g7gl5wcPFsfEn9dW3Glqr1vx0GrDvGnVMy1eEUlHBRSo0YdftYqpEe5lpcFNMaEDv9851PKp glMCjw3ocfTbqhVQGTgkB/hNi3GngjFBaPRUYP/sSTzjhNhXh8i08V3tYWkHsM/I80D8As3Z WJDo140LVVCsMGZ6N0A+kMBcOxF2zWWBrJdGafO07uGq0LM2/E75T3/LI27ue3f4Fg9up+pL 3RFFdD8WIicUPnDsODmJVN7xDWWW24GS/gz8lPjqIJ84EUhICbRxFrZGpe5PdI+c9vd/Ezc8 zDTK5rPw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.96,181,1665446400"; d="scan'208";a="5221819"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 Nov 2022 13:11:38 +0000
Received: from mail.cisco.com (xfe-rtp-003.cisco.com [64.101.210.233]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 2ALDBbvl005356 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Mon, 21 Nov 2022 13:11:38 GMT
Received: from xfe-rtp-003.cisco.com (64.101.210.233) 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.1118.9; Mon, 21 Nov 2022 08:11:37 -0500
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (64.101.32.56) 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.1118.9 via Frontend Transport; Mon, 21 Nov 2022 08:11:36 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QCT2NoMYZp3YK8Xx+Oy/MvoRDsMYhKM2kBga5FXIzZRL2HtXxJHP1jd7rauntuydcpvh8y4SU2dHZ3P8o3LRU9c4aE4zMS+DDZ6BUAL6AYWxvR2vlhnFCOMf0jjOuZfJNDoRbIxWUvjCfQqj6ktDaIusrNFgA9voqWnC0G+ufBzx8wuxl5iuxC2Q6CHgHrT/grpLHwPpuzQq5V9DWlaBVGt7QMtc7jcZqiKTU8XwuE1EX0yze99Bz4KVqn7wTEdPFeFqrJ9QgEshQj1SXDRjXFwnF9Qg420HMOJWo2VyRkiYg1jsPYXxJqlvQpJXQftDaHFnZGn/cPHU1eVnIjHIHw==
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=u+TD/1nac1rWK2Cnyrue8+IAogzZTe/6yV4U26ZTN4g=; b=RxoUqrWmIu1l9By0GcKZHNAGJNu+2vFM/WFUPfas1RuU402lK0/xr2rjI8p8sOwlMgYIV6ybWQbrYJPCVjmWS8n75nB0QMBZ8fgN51zI2eDC9fznrQaoSVNCfi4AMQsOcW8Ox266gQB3dRcerpqqUoioWGbJt24Onv/guNu9PPaZKhO8ZU3ADL8ewIZpVvTb58v0/qFvnt6MDFsjrk6B1B+6/pUOfc/mW9A8NApmiDucvUQKL62qQpsv7hHX+2UWAZR7OY2SrqilseHhNqZS+pgm9Z6WEIDTBYIQ8bn1eNZaKw8U2GZVHRYJxkIONBEa+5u98EP3Wx+Bu2jsnpS6QA==
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.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=u+TD/1nac1rWK2Cnyrue8+IAogzZTe/6yV4U26ZTN4g=; b=PNgrdmKVMfPBiF8O1tlKNd7MYmm0nNGurARZH4nQG2h/mZ5nzWzKvkTyp5fAD13n8Ho37WdnTZEEHRBBa3BIW+p3qjyGiz1p9kNpp73a5tyh/ZCWSjYuLDSXNN3i/1FVovv8lf8lY/Wzq3Ho5jUN8D9p4Fi8HiPMrN+1XaxS0FE=
Received: from CO1PR11MB4881.namprd11.prod.outlook.com (2603:10b6:303:91::20) by MW4PR11MB7007.namprd11.prod.outlook.com (2603:10b6:303:22c::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5834.9; Mon, 21 Nov 2022 13:11:35 +0000
Received: from CO1PR11MB4881.namprd11.prod.outlook.com ([fe80::20d9:5c5:9e71:961]) by CO1PR11MB4881.namprd11.prod.outlook.com ([fe80::20d9:5c5:9e71:961%7]) with mapi id 15.20.5834.015; Mon, 21 Nov 2022 13:11:35 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: tom petch <ietfc@btconnect.com>, Mark Smith <markzzzsmith@gmail.com>, "carles.gomez@upc.edu" <carles.gomez@upc.edu>
CC: "6lo@ietf.org" <6lo@ietf.org>, 6man WG <ipv6@ietf.org>
Thread-Topic: [IPv6] WG Last Call on draft-ietf-6lo-multicast-registration-11
Thread-Index: AQHY+iKX4t3qDQaMwkSF9cCM5QTVDa5DA+VQgABR7wCAASPDIIABvA8AgAME2IA=
Date: Mon, 21 Nov 2022 13:11:11 +0000
Deferred-Delivery: Mon, 21 Nov 2022 13:10:54 +0000
Message-ID: <CO1PR11MB4881FD27EAF74C486A0B1B44D80A9@CO1PR11MB4881.namprd11.prod.outlook.com>
References: <CAAUO2xxJ-Cksm6uL19LxpbH4q1nodCsKbUPUAd3UEH=SMRSokg@mail.gmail.com> <CAO42Z2z6_kHhO5goSKDBudJjLTxBejZJEqQ-Rh5VSganinVnYQ@mail.gmail.com> <CO1PR11MB4881144FAEC23F671C46E25FD8069@CO1PR11MB4881.namprd11.prod.outlook.com> <AM7SPR01MB0017AF6A62A3D9935181A090A0069@AM7SPR01MB0017.eurprd07.prod.outlook.com> <CO1PR11MB4881AFB1045D0BE039E0ADC5D8099@CO1PR11MB4881.namprd11.prod.outlook.com> <VI1PR07MB6256DF69383B67B3D2ABAD19A0089@VI1PR07MB6256.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR07MB6256DF69383B67B3D2ABAD19A0089@VI1PR07MB6256.eurprd07.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=cisco.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: CO1PR11MB4881:EE_|MW4PR11MB7007:EE_
x-ms-office365-filtering-correlation-id: 444c8bb9-9410-43f1-4df3-08dacbc1eae0
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: yKR8uoAvH0o9rczTvs+NKyyOnrYH+3s3SbEYmuXEjjF62m0a22N01F7z775R1UN58lBx0VcC4+fKRdYIDakU511R7ahhfFrmYZI+5bqkaOqcOoy/hH5JBegSOK+AexoHFMH23Mtx66ebKAadEnpkZ4HpK3naTRQ/g8mxRu9YH2RFrk8lWU7c92iun6ZXgmVWFq0iCaNgxKon8PCB32lAztMN64I4sCCWvnBObovJPJlBgQ2SEar3c1rySuuC4I46NkPr5aiYceMh72iBsqiQskyJEBAGGwrGgPaSWZrnIi67kCHW7RHUejdp9RDTLoOJMAaDoXrkm38W6UWLzOLz/hnuhcn/YMm+NAHggORzIuU5DNtj21uuOGmXrSDP7YmhEn/1GsJ+n08eFE+oXX05DFpxcs5sV7fZN0l2TbHYZMuSH1kvTjgpacpudk4zHIQAspxinhyuTlxe5/ngTzwDkR5oHy612QH62l9Ec5eYcWWF1qbZlcPwo2gZhc7vthtKinpFL6Xc6ye6gMrjvLrdO2U0Hjqclju44ObxI1GU3rkNjtDjQM8gjpD4DMefsH1TIH7zsueWXYnlgLEIU5jyTZ07lnXT5beE8MJfSa1PgQoS7pjR32fx0+EOWSzdlmDbamcUFnRxA5OLMDhxUS6zK2T9xDNmdLWvOxFQQW67JV7b4k522ymBfnSJn9jCQCrfko0P4bIjb0bZIzlvDolLF7aHB2eU8GLvjpnNz4ZziIiR+fRZ7h5GzoO4x2uiRTAWnb4w+aBIR22uazAD7UdakQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CO1PR11MB4881.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230022)(4636009)(39860400002)(396003)(376002)(366004)(136003)(346002)(451199015)(6666004)(71200400001)(966005)(478600001)(66899015)(64756008)(66446008)(4326008)(76116006)(66946007)(66556008)(9686003)(41300700001)(8936002)(52536014)(186003)(316002)(26005)(110136005)(33656002)(53546011)(54906003)(296002)(5660300002)(6506007)(8676002)(7696005)(83380400001)(66574015)(2906002)(86362001)(55016003)(66476007)(38070700005)(38100700002)(122000001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: AD9kMYVRnuRT+WLF9jiFhyfyi0DKizV7xY5P45z+/k2QAEifIcQwiyNGZ79aRQfLgfzlSaWiCbiYFTKyW8aFGymYHqVLDiEI8fOShG3h0cXwKvKjWdJLK0tFNu0MvFhlKhyVJ2NtPmqfx1LGzijPtsIUrb4RyTvrOrRoEnoXRYm9fqJHsqhnJK7KaRBwPpuSUgrGVntUq+TwXhzE+bQtJ/84N5y9W2JJiiMdy/2qr/sZzQ6L2ILeouVe9UwyMFaj29q+c/1WkpoDFm0pm948Pjf2tRF9ElBDnq/CZP0PN5bdrGOJmwjGEGLbJMTBvUPO+nuxzSjv/UIvfSAqErazA54IC3/vGPNLLKCIz7bIn1kIOtjfv+XFuXr9gO9fkZhpxKbUd3qN0Gu9p1tkZxpk29wSwP1/2Z2V1SU6zG+LZHeKhEALzAVO6Flze1/2w0i5h+hEmXojJm/z8gxp4AaOQEF7c8g/GtnnGbOrwEgkoj2VrpensOfR4YT1JodF3IOnhBJp6hrQiJdlS5rbGKcFponWi8AgQwcAsBYEiGwM4xi4/pQEflVkbvdpRzA5ZOGj1f6HwihR3SOUgNCFlkDaARejsXCIDFB4311hSKsnr4x8ppoeX5tOzfB04ft1aHsaWMDlso3/TLZNPT0npVzCuJ6g21AlMg5spLU1B8meSTNpiiHqJzZS9hboaWaJDxCH/nhmOoToENZqHypoV2FTzFD8JuAEAuy5J760Wtxw6/zRqa3d3dmP/raW3NTy5BU2bJ9UPyf0G1qrDIMKXQCWYJaf2QX3Q9t91fGigNZ5Z9ZubkdCeS0jU/A0zee49nhbR/N1xhOMxcEI47wRBZgJfFFiryiM7LdmZqvRrXpnkbstfDV+/LDrXSNLjTN02Tkxy8H3n+Hs3K4+LmR6rBqIe2KsydyxqrPN0C+uvUw/zlbiqYbuNCtKrCSEEClIq9FMEhUjHqu99ewV+lTbzMTdyi1fJ2T5lwNjOBHIGTp7y4ypcOYABKSufEMsZZiA+9Q4KeshSVOgIkH6aIRC8SjEiDsadVvBVzCZsFmAydIrTDt6T/wEp04aN1WankbNGfAusvHYwDB86e3GnZ4aVPJ41mBBbQ5xFtJH3livshrm+4low+IBxTCsrwXAEb4iIcHzMDllWWpxfquSgNf5BZ3mf5MZ3HXOo3o1f1JULoQfd3Luvxh1Q6ACXLFtDEvKutZrZbgB+HC54Yms6bp1sGBZrTB25UVjJmS9lxLOE7WHbh3W6lq2Rdx++J7OxZgvIt788p9DBbd4rQyTc2rU8kKC1BpwS3aXRdXRqmqEIlYJutbHrFkoCDRpLXQZDDBeeHN0nhxQCNfJR5ITBNJN0WiqFcK6Qi0ETZuGRT6GXqvjFunWa/DwJVjCkLbx9sG+JlYhNcnaxRJd19pzI3Vx73F5pVERkF/S3KzaAycGlrkHkx75fgSY80QCxNe2Wn/ObetGpGmXsN+/1BUB4SOVMgG4Va3v6zcOXWVnzQ/aySr4Md2R3IrorLScajbtkJ8HSNhRXACUYkHnnS/kRH7kjypN+lPGfyJP7Dmde3n4zEUGppJ8yD0spCZ9u+VARIykGlMS
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CO1PR11MB4881.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 444c8bb9-9410-43f1-4df3-08dacbc1eae0
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Nov 2022 13:11:35.5416 (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: 0pW3WAOJP9RMP+l1o6CEdIERSFUNtxylJirabdp82gVqye49EP4JNSI9bv3k2F5xIjaK4++Y5zX6Nq1Lw9/Erw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW4PR11MB7007
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 64.101.210.233, xfe-rtp-003.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/O_au3rMbksUycRkV6zv9FtFmTDE>
Subject: Re: [IPv6] WG Last Call on draft-ietf-6lo-multicast-registration-11
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2022 13:11:44 -0000

Many thanks Tom.

As a reference for the reader since it is unpublished, the current title in github is:
"
     IPv6 Neighbor Discovery Multicast and Anycast Address Listener
                              Subscription
"
And the current abstract is as follows:
"
   This document updates RFC 8505 to enable a listener to subscribe an
   IPv6 anycast or multicast address; the draft updates RFC 6550 (RPL)
   to add a new Non-Storing Multicast Mode and a new support for anycast
   addresses in Storing and Non-Storing Modes.  This document extends
   RFC 9010 to enable the 6LR to inject the anycast and multicast
   addresses in RPL.
"


> 
> Equally I found Multicast on its own adequate,  Yes the I-D caters for
> Anycast and that is in the Abstract but I query the need for it in the
> Title- a reader  might well wonder about the latter and find the answer in
> the Abstract.

Pardon my non-native limitation here; I read this as:
 "anycast is superfluous, find it in the abstract" is that correct?
The source of confusion is that your initial proposal was
"Subscribing to IPv6 Broadcast and Multicast Addresses in a 6LN Network"
Which clearly was a typo so I read " IPv6 Broadcast" -> "IPv6 Anycast"
and I applied that. Also, Mark recommended to place Anycast in the title.

> My thought remains that the Title should lead into the Abstract, as the
> Abstract leads into the document but in neither case will the former cover
> all that the latter does.

Makes full sense to me.

> So with no explicit mention of ND in the Abstract I query its appearance in
> the Title.

I guess this calls for a change in the abstract to mention it.
The tension here is that we need to list RFC 8505 in the abstract because we 
extend it. RFC 8505 is "Registration Extensions for IPv6 over 6LoWPAN Neighbor
Discovery" so using those words in full would be cumbersome.


> I think that the Title of the RFC needs to indicate the type of network
> involved and did look at other RFC to see how this network is referred to
> and see much usage of Low-Power Wireless Personal Area Networks (6LoWPANs)
> which seems cumbersome to me but suggests that there is no recognised,
> shorter tag which might be used:-(.

True; and even worse, LoWPAN in IEEE parlance is 802.15.4 only. 
But 6LoWPAN ND works on any link I'm aware of. So the term 6LoWPAN ND is
Highly misleading.

> 
> As you gather, I think that titles matter, as do abstracts, that they
> should be short enough to read, recognise or remember but should not be
> overloaded with all the possible semantics.
> 
> By contrast, I care little about the title of the I-D which almost vanishes
> once the RFC is published; for me, many I-D titles are too cumbersome
> although this one is just fine (no need for Anycast or ND in it:-).

I appreciate that, Tom.

From the discussion above I'm not sure I should take anycast out of the title.
I made the changes below:

     IPv6 Neighbor Discovery Multicast and Anycast Address Listener
                              Subscription

   This document updates the 6LoWPAN extensions to IPv6 Neighbor
   Discovery (RFC 8505) to enable a listener to subscribe an IPv6
   anycast or multicast address; the draft updates RPL (RFC 6550) to add
   a new Non-Storing Multicast Mode and a new support for anycast
   addresses in Storing and Non-Storing Modes.  This document extends
   RFC 9010 to enable the 6LR to inject the anycast and multicast
   addresses in RPL.

Many thanks,

Pascal


> -----Original Message-----
> From: 6lo <6lo-bounces@ietf.org> On Behalf Of tom petch
> Sent: samedi 19 novembre 2022 13:47
> To: Pascal Thubert (pthubert) <pthubert@cisco.com>; Mark Smith
> <markzzzsmith@gmail.com>; carles.gomez@upc.edu
> Cc: 6lo@ietf.org; 6man WG <ipv6@ietf.org>
> Subject: Re: [6lo] [IPv6] WG Last Call on draft-ietf-6lo-multicast-
> registration-11
> 
> From: Pascal Thubert (pthubert) <pthubert@cisco.com>
> Sent: 18 November 2022 10:56
> 
> Hello Tom:
> 
> I agree nunicast is weird and I'm not inclined to use it.
> 
> About your proposed "6LN network": we do not have that language so far. We
> have LLN but that does not imply 6LoWPAN ND, and RFC 8505 does not imply
> constrained networks. It is a stateful AAD operation, it consumes less
> resource so it works EVEN in constrained devices and networks. It's an EVEN
> not an ONLY. It makes ND greener. As an L3 function, stateful AAD should be
> abstract to the lower layers, to the network they are used in, to the
> hardware in general. And it is, more than SLAAC actually, since SLAAC is
> limited to certain abstract topologies (P2P and NBMA).
> 
> Also there's a semantic confusion between "constrained node" and "node that
> supports 6LoWPAN HC" or "node that supports 6LoWPAN ND". In this
> specification, we mean the latter, so we really refer to the L3 function
> not a type of nodes. In other words, we use 6LN and 6LR as nodes that
> support the L3 functions that 6LoWPAN defined as part of IPv6 ND for the
> host and the router side respectively to provide stateful AAD. Maybe we
> should have introduced new terms but at this point it makes sense reusing
> the language in RFC 8505 that we are extending.
> 
> Considering the number of ND broadcasts we observe it's probably time we
> sunset SLAAC in any large network. Our small contribution to the planet if
> you like. But dropping AAC with SLAAC would be throwing the baby with the
> water of the bath. RFC 8505 makes AAD greener and more deterministic by
> avoiding the broadcasts in SLAAC and providing a contract between the host
> and the router for address ownership and usability. As you've seen recently
> on v6ops ML, SLAAC has a huge issue there and we're now hitting that wall.
> 
> <tp>
> Pascal
> 
> Thank you for the comprehensive reply.
> 
> My thought remains that the Title should lead into the Abstract, as the
> Abstract leads into the document but in neither case will the former cover
> all that the latter does.
> So with no explicit mention of ND in the Abstract I query its appearance in
> the Title.
> 
> Equally I found Multicast on its own adequate,  Yes the I-D caters for
> Anycast and that is in the Abstract but I query the need for it in the
> Title- a reader  might well wonder about the latter and find the answer in
> the Abstract.
> 
> I think that the Title of the RFC needs to indicate the type of network
> involved and did look at other RFC to see how this network is referred to
> and see much usage of Low-Power Wireless Personal Area Networks (6LoWPANs)
> which seems cumbersome to me but suggests that there is no recognised,
> shorter tag which might be used:-(.
> 
> As you gather, I think that titles matter, as do abstracts, that they
> should be short enough to read, recognise or remember but should not be
> overloaded with all the possible semantics.
> 
> By contrast, I care little about the title of the I-D which almost vanishes
> once the RFC is published; for me, many I-D titles are too cumbersome
> although this one is just fine (no need for Anycast or ND in it:-).
> 
> Tom Petch
> 
> All the best,
> 
> Pascal
> 
> 
> 
> > -----Original Message-----
> > From: tom petch <ietfc@btconnect.com>
> > Sent: jeudi 17 novembre 2022 17:53
> > To: Pascal Thubert (pthubert) <pthubert@cisco.com>; Mark Smith
> > <markzzzsmith@gmail.com>; carles.gomez@upc.edu
> > Cc: 6lo@ietf.org; 6man WG <ipv6@ietf.org>
> > Subject: Re: [IPv6] WG Last Call on
> > draft-ietf-6lo-multicast-registration-
> > 11
> >
> > From: ipv6 <mailto:ipv6-bounces@ietf.org> on behalf of Pascal Thubert
> > (pthubert) <mailto:pthubert=40cisco.com@dmarc.ietf.org>
> > Sent: 17 November 2022 12:02
> >
> > Done 😊
> >
> > <tp>
> > Piling nouns in a  heap often does not work well in English and may be
> > ambiguous.  The Abstract seems clear but I would not have expected it
> > from the title, old or new.
> >
> > Neighbor Discovery is not in the Abstract and I do not think it adds
> > to the Title.  The Abstract has subscribe as a verb and that seems to me
> spot on.
> >
> > The Abstract has 6LR without expansion but it does narrow the scope
> > from all aspects of ND.
> >
> > Hence I suggest something along the lines of Subscribing to IPv6
> > Broadcast and Multicast Addresses in a 6LN Network.
> > In passing, I saw recently the term 'nunicast' and thought it ugly and
> > incomprehensible.  It got revised to non-unicast which I understood
> > and then to multicast and broadcast.
> >
> > Tom Petch
> >
> > From: ipv6 <mailto:ipv6-bounces@ietf.org> On Behalf Of Mark Smith
> > Sent: jeudi 17 novembre 2022 2:18
> >
> > Hi,
> >
> > I think the naming needs to change now that it is also doing anycast,
> > to something like "IPv6 Neighbor Discovery Multicast and Anycast
> > Address Listener Subscription".
> >
> > I think anycast is a different and distinct type of communication to
> > multicast, and is in the middle between unicast and multicast:
> >
> > i.e. unicast = 1 to 1; anycast = 1 to 1 of any/many; multicast = 1 to
> > many;
> >
> > Regards,
> > Mark.
> >
> >
> >
> > On Thu, 17 Nov 2022, 00:23 Carles Gomez Montenegro,
> > <mailto:carles.gomez@upc.edu<mailto:carles.gomez@upc.edu>> wrote:
> > Dear 6lo WG,
> >
> > (CC'ing 6man.)
> >
> > This message initiates WG Last Call on the following document:
> >
> > "IPv6 Neighbor Discovery Multicast Address Listener Subscription"
> > https://datatracker.ietf.org/doc/html/draft-ietf-6lo-multicast-registr
> > ation-11
> >
> > The Last Call will end on Wednesday, 30th of November.
> >
> > Please provide your feedback on this document on the mailing list.
> > Short confirmation messages such as "it looks fine" are also welcome.
> >
> > Thanks,
> >
> > Shwetha and Carles
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > mailto:ipv6@ietf.org<mailto:ipv6@ietf.org>
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo