Re: [Int-dir] Fwd: int-dir last call review on draft-ietf-mboned-ieee802-mcast-problems-09
"Eric Vyncke (evyncke)" <evyncke@cisco.com> Thu, 10 October 2019 09:29 UTC
Return-Path: <evyncke@cisco.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C4E11200B3 for <int-dir@ietfa.amsl.com>; Thu, 10 Oct 2019 02:29:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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=WvICAtlR; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=qUzHnjft
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 DQnCLB_VJnbJ for <int-dir@ietfa.amsl.com>; Thu, 10 Oct 2019 02:29:25 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 249E612002F for <int-dir@ietf.org>; Thu, 10 Oct 2019 02:29:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18311; q=dns/txt; s=iport; t=1570699765; x=1571909365; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=4iy2/TyclAI6riCsi1xMbr56sn4Li7+TVh6nGrJIZug=; b=WvICAtlR6DT8o2M9Qdr8BjuvuhnOErFCsgfxq/kkyyJDQqim7C3qU50f FHnGUM7RSX2qnw7FmRjQqpJbzHPzRv7B49a6tRfAny0w2hhJa32A5D/xD ryFywTgjT7v6LLPO1pWUZugoWidDkhPUO0EBr0XsLaGiZPCiwEWUfK1n3 o=;
IronPort-PHdr: 9a23:dQuKnBOvfNgwOz7IsUgl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu60/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBj2Mu/sZC83NM9DT1RiuXq8NBsdFQ==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BMAQB1+Z5d/51dJa1lGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYF7gRwvUAVsViAECyqEI4NHA4pFTYFqJYM5j2OEYYFCgRADVAkBAQEMAQEjCgIBAYRAAheCQSM4EwIDCQEBBAEBAQIBBQRthS0MhUsBAQEBAxIRHQEBKQ8PAgEGAhEDAQIoAwICAjAUCQgCBAESIlOCLQGBeU0DLgECDJVdkGICgTiIYXWBMoJ9AQEFgkmCQBiCFwMGgTSMDhiBQD+BEScME4JMPoFUgQ0BAQOBNw84DQmCWDKCLIxlEhKCZoU3iQ2OLGgKgiKHCI4RG5BHiHmOLYgikRQCBAIEBQIOAQEFgWkigVhwFTsqAYINATNQEBSBTziDO4UUhT90gSmNHg8Xgi4BAQ
X-IronPort-AV: E=Sophos;i="5.67,279,1566864000"; d="scan'208,217";a="347903045"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Oct 2019 09:29:24 +0000
Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x9A9TOg0022608 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 10 Oct 2019 09:29:24 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 10 Oct 2019 04:29:23 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 10 Oct 2019 04:29:23 -0500
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 10 Oct 2019 05:29:23 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=k6j3mLvjGgNdBwWZHsuWgBlOG+iXKNJU5aRWGQ1dNSW0ZuL8Q2WhCeaJO7vw8+izbGMTrMOm+aoz2Ldpi9SRu2X/mYASQNLsNfd7Rolpqw6xRdX0tJDKV69bpXsjwuv7+BSs0IgjihsCPvW3VrpkDiqmr826yk7PFSNW/ZDtcfvrqZsBLpuzCxfLG3cfVbGODrgAyIjG6zIJVckQnJ1xkOylBjvxXZQW1oCUCKLeLlFvSe3mxnx0wsbePYdGeph/CZgFBjYJVxUkKtSH7voXUAk7RmwLztdl0/eCvxEcNXgOl4pZ1xPwSCbJwgVRZljgSwd3UqKxMnOitlZx7Ra1gQ==
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-SenderADCheck; bh=4iy2/TyclAI6riCsi1xMbr56sn4Li7+TVh6nGrJIZug=; b=Npu7HF26+LEicChMMni9+ZxIXZmDUAsqPdpJ+Vmgn1kBHboRUP3/kMr6hcGoOJizWrmBAtD6m2HVW0y2w25EBWHaQNYex4vDzXy5x7jOY0hkDN/wmgCvHQRiQykm1S/SxrpSQsRBXuiMLa/S4nZ76/6/6jFPPbfeZJHLm0QwtmitxWQdflU3kx/RcmBOgRDU0UP5FQIt8EB0Pb1P/pm0+yPxatwWKmFUiEUTfex07gQ28tyQ+NHdoJQrgPQAaA5KYmbf1PYjiERGU5oph6y/NtPiqawTWpa4Vk1cV+LxbhAFo8kI5P5D8YTOBAiLC7ScZ/T5V5zMr1+35H/yK1ggiw==
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=4iy2/TyclAI6riCsi1xMbr56sn4Li7+TVh6nGrJIZug=; b=qUzHnjftskdqykuMAB5J5VZi59mVE0EJDtlyn0hfBLzWrGzvBh36nw0Omq2cuZSdvgJKOKMCOWJNtWb63XUi5B+EpZTJcvVi6NrOSRpbr2WcyJGl67jPpC3hO9fldWXwGTY4SikifSVVIuJAurTxtoqIb6kczbVOsiGufhjhPuU=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB4096.namprd11.prod.outlook.com (20.179.150.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.17; Thu, 10 Oct 2019 09:29:21 +0000
Received: from MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::e4f8:d335:c018:c62a]) by MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::e4f8:d335:c018:c62a%7]) with mapi id 15.20.2347.016; Thu, 10 Oct 2019 09:29:21 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: η₯ζιε <jinmei@wide.ad.jp>, "<int-dir@ietf.org>" <int-dir@ietf.org>
Thread-Topic: [Int-dir] Fwd: int-dir last call review on draft-ietf-mboned-ieee802-mcast-problems-09
Thread-Index: AQHVftK4B/cytlb2LUeKKRZKy+WvYadS706AgADO9gA=
Date: Thu, 10 Oct 2019 09:29:21 +0000
Message-ID: <7C8D0986-424E-48BD-8172-A13B5253C293@cisco.com>
References: <CAJE_bqevnRTVTBO7thcRPoK5T_1NKP=BSa8rU5b726gURG95Cw@mail.gmail.com> <CAJE_bqd0Ab-Ju0WoUxAqh8hTdwLaaVKxgy0Akf8Hd+s3sfkJAw@mail.gmail.com> <9BBC79AE-0A0F-4616-A809-0D022B45C2A6@cisco.com>
In-Reply-To: <9BBC79AE-0A0F-4616-A809-0D022B45C2A6@cisco.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c0:1006::32]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: cbc16457-2310-4c24-9798-08d74d645521
x-ms-traffictypediagnostic: MN2PR11MB4096:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR11MB4096C237F31C658BDE2DE389A9940@MN2PR11MB4096.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:525;
x-forefront-prvs: 018632C080
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(136003)(376002)(346002)(396003)(366004)(199004)(189003)(22974007)(66574012)(66446008)(64756008)(66556008)(66476007)(91956017)(76116006)(86362001)(66946007)(229853002)(2906002)(6116002)(6436002)(6512007)(6246003)(256004)(6306002)(14444005)(54896002)(236005)(25786009)(6486002)(71190400001)(316002)(5660300002)(110136005)(71200400001)(58126008)(606006)(478600001)(7736002)(36756003)(53546011)(76176011)(486006)(8936002)(99286004)(446003)(966005)(2616005)(81156014)(46003)(6506007)(186003)(14454004)(8676002)(476003)(81166006)(102836004)(11346002)(33656002)(491001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4096; H:MN2PR11MB4144.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: SXy9NhMx4njKwMiJJTTJuk4x2t2K5DxG67+fF27K1Pz7Uy9r6z1yxBZ9ka7rKmogk0kqICfmBLMwAK+c3Wp6MRSe9VwipAbCkrfYtJhxsqWZX9j/vDd4rbvIE0DTLPuvnW5mkGCrVi7sPwMOk0Zm8wFYCBn4VfhWx9F5R0ZEMzcC5jt2jSB4BWHveSCvbkMRB+PEriRArtDncEWtRyn2+yXWoFBR2hLIQJdbtReKjHaXQtLjfYkdjF09o61xaMuSxsbGJE69t+dLWtn2AorsDz6QoIjAAxDGZhFihJje4V6ZBZvJQcE/O6JRPr7bwGcxaR9lcFxSFbUn220xMFOmPzXSvvin5YoOh6taC74pP9D25dmnQ69rYFF9LSvX02dwgpiwIptAGcBdSdX2n2hlj391YDrlOJNIBaWuSxhOMAUvLsG99dVuzv0YLT5mQuoYvu88mjy8llOmexkahKNZfw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_7C8D0986424E48BD8172A13B5253C293ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: cbc16457-2310-4c24-9798-08d74d645521
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Oct 2019 09:29:21.5578 (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: trK0nR3a1l1Cy6osQoTWaMOGEGWFRwrjRFJ226DXBH9utZ9XCg9n3MN9XknCQfSNKrVTHlA1k6qob09YAxMRrA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4096
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.29, xch-aln-019.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/MRqLLRSBd76f2P7Yhh9XIawnRLs>
Subject: Re: [Int-dir] Fwd: int-dir last call review on draft-ietf-mboned-ieee802-mcast-problems-09
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Oct 2019 09:29:27 -0000
Shame on me: I should have checked the datatracker first as it is there Time for a cup of coffee π -Γ©ric From: Int-dir <int-dir-bounces@ietf.org> on behalf of Eric Vyncke <evyncke@cisco.com> Date: Wednesday, 9 October 2019 at 23:08 To: η₯ζιε <jinmei@wide.ad.jp>, "<int-dir@ietf.org>" <int-dir@ietf.org> Subject: Re: [Int-dir] Fwd: int-dir last call review on draft-ietf-mboned-ieee802-mcast-problems-09 Tatuya-san Thank you very much for your review even if you are not an βexpertβ in the domain (as you modestly wrote), it is useful. May I kindly ask you to enter the review in the datatracker as well ? So, that everyone will have access to your review? Thank you again -Γ©ric From: Int-dir <int-dir-bounces@ietf.org> on behalf of η₯ζιε <jinmei@wide.ad.jp> Date: Wednesday, 9 October 2019 at 20:52 To: "<int-dir@ietf.org>" <int-dir@ietf.org> Subject: [Int-dir] Fwd: int-dir last call review on draft-ietf-mboned-ieee802-mcast-problems-09 oops, looks like I forgot to include the int-dir list. forwarding it. ---------- Forwarded message --------- From: η₯ζιε <jinmei@wide.ad.jp<mailto:jinmei@wide.ad.jp>> Date: Wed, Oct 9, 2019 at 11:37 AM Subject: int-dir last call review on draft-ietf-mboned-ieee802-mcast-problems-09 To: <jholland@akamai.com<mailto:jholland@akamai.com>> Cc: <draft-ietf-mboned-ieee802-mcast-problems@ietf.org<mailto:draft-ietf-mboned-ieee802-mcast-problems@ietf.org>>, <jholland@akamai.com<mailto:jholland@akamai.com>>, <mboned-chairs@ietf.org<mailto:mboned-chairs@ietf.org>> I am an assigned INT directorate reviewer for draft-ietf-mboned-ieee802-mcast-problems-09.txt. These comments were written primarily for the benefit of the Internet Area Directors. Document editors and shepherd(s) should treat these comments just like they would treat comments from any other IETF contributors and resolve them along with any other Last Call comments that have been received. For more details on the INT Directorate, see https://datatracker.ietf.org/group/intdir/about/. Based on my review, the document is ready to go to IETF Last Call and therefore can be forwarded to the IESG. I first have to note that my knowledge and expertise on the underlying technical areas (especially those defined in IEEE) are quite limited. So my review is more or less superficial anyway. Overall I found the document well written and useful. I didn't find any obvious technical issues on topics I'm relatively familiar with. I only some have minor comments as follows: - Section 3.2.2 IPv6 makes extensive use of multicast, including the following: ... o Route Discovery o Decentralized Address Assignment o Geographic routing What specifically does "Route Discovery" mean? If it means the default router discovery using RA, I suspect it's better to call it that way since "Route Discovery" may also sound like a generic routing protocol. On the other hand, if it means something different from default router discovery, it'd be better to provide a reference to avoid confusion like mine. Similarly, it would be nice to provide references for "Decentralized Address Assignment" and "Geographic routing". - Section 3.2.2 Neighbors may be considered lost if several consecutive Neighbor Discovery packets fail. It's not clear what this sentence refers to. If it means neighbor unreachability detection as described in Section 7.3 of RFC4861, I'm not sure how it's relevant to this document since the unreachability detection (normally) doesn't rely on multicast. Maybe we can simply remove this sentence if it means the unicast based neighbor unreachability detection. - Section 3.2.4 With Neighbor Discovery for IPv6 [RFC2461], nodes accomplish address s/[RFC2461]/[RFC4861]/. And, since this is the only reference to the old RFC, it should now be removed from the References section. -- JINMEI, Tatuya
- [Int-dir] Fwd: int-dir last call review on draft-β¦ η₯ζιε
- Re: [Int-dir] Fwd: int-dir last call review on dr⦠Eric Vyncke (evyncke)
- Re: [Int-dir] Fwd: int-dir last call review on dr⦠Eric Vyncke (evyncke)