[Int-dir] Fwd: int-dir last call review on draft-ietf-mboned-ieee802-mcast-problems-09
神明達哉 <jinmei@wide.ad.jp> Wed, 09 October 2019 18:52 UTC
Return-Path: <jinmei.tatuya@gmail.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 C6FBD120B20 for <int-dir@ietfa.amsl.com>; Wed, 9 Oct 2019 11:52:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.477
X-Spam-Level:
X-Spam-Status: No, score=-1.477 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.172, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 wm2pahWDCXwl for <int-dir@ietfa.amsl.com>; Wed, 9 Oct 2019 11:52:26 -0700 (PDT)
Received: from mail-wm1-f49.google.com (mail-wm1-f49.google.com [209.85.128.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5028B120BB7 for <int-dir@ietf.org>; Wed, 9 Oct 2019 11:52:23 -0700 (PDT)
Received: by mail-wm1-f49.google.com with SMTP id 5so3777659wmg.0 for <int-dir@ietf.org>; Wed, 09 Oct 2019 11:52:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=lZpLcY/ZT5tCQg9wS1PfUFZWoPx+jBEzrl2kytiRLVk=; b=oneIdxejlZMF48/+ftAuQaAdqIfzBa2BGyHuLYGJ3AKake0bGMBQeLWIpIkNAiUfZs U61TdCHMmPgJyP9Wayxm2LGqUmY2/sZNnMRlblZBmNO3XbCNgxYnK8vvP4t3nvnFmlxN joTdtMMETe6hpUn6jf0mlRL47yjgSasH3bCRYaiPyCYhesGnRlfWnlOp6MsD9Tuhk3FR kz2KhfRCkBvcanqY2M5TX5C+msbnQcqkwa3mrCMmdvqx1sK6J5k0uE2gcfS5ylL0+p/Z NPEd1CUTcJmp5bwU1ufJkZ9EPuDd0AFYmsFSt7h/TFHxNaZ4k5H6UNl76FgZDbVLQu2r UvGg==
X-Gm-Message-State: APjAAAWRu5AiO5D1gF/wrdL+4ekK9ofa67yC6raxwHJCn7vYVCLHAAd1 m+RzGav2Mfn5zoJQc0F2iIUX9eG5HiC/RK7+iNfMbA==
X-Google-Smtp-Source: APXvYqy5kQsmjENBVH+FEYu3kgN9l5Yu773Az6DELPYVqlG3in+N9VjryupmSBlgvHMuBBXxD90P72JRk522uvTa5to=
X-Received: by 2002:a1c:4456:: with SMTP id r83mr3799885wma.44.1570647141261; Wed, 09 Oct 2019 11:52:21 -0700 (PDT)
MIME-Version: 1.0
References: <CAJE_bqevnRTVTBO7thcRPoK5T_1NKP=BSa8rU5b726gURG95Cw@mail.gmail.com>
In-Reply-To: <CAJE_bqevnRTVTBO7thcRPoK5T_1NKP=BSa8rU5b726gURG95Cw@mail.gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Wed, 09 Oct 2019 11:52:10 -0700
Message-ID: <CAJE_bqd0Ab-Ju0WoUxAqh8hTdwLaaVKxgy0Akf8Hd+s3sfkJAw@mail.gmail.com>
To: "<int-dir@ietf.org>" <int-dir@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ec25c205947ec81e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/nZkNYVpWpUGvns90pi5V4phUWA8>
Subject: [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: Wed, 09 Oct 2019 18:52:29 -0000
oops, looks like I forgot to include the int-dir list. forwarding it. ---------- Forwarded message --------- From: 神明達哉 <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> Cc: <draft-ietf-mboned-ieee802-mcast-problems@ietf.org>, < jholland@akamai.com>, <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)