comments on draft-ietf-6man-rs-refresh-02
神明達哉 <jinmei@wide.ad.jp> Fri, 11 November 2016 19:44 UTC
Return-Path: <jinmei.tatuya@gmail.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 BD1E1129C9E for <ipv6@ietfa.amsl.com>; Fri, 11 Nov 2016 11:44:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 n6rVA1DBJNER for <ipv6@ietfa.amsl.com>; Fri, 11 Nov 2016 11:44:08 -0800 (PST)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 133C3129CA6 for <ipv6@ietf.org>; Fri, 11 Nov 2016 11:44:06 -0800 (PST)
Received: by mail-qt0-x22c.google.com with SMTP id w33so15593838qtc.3 for <ipv6@ietf.org>; Fri, 11 Nov 2016 11:44:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to; bh=Mi2IZH4B3VzwDRPgoG0/2DNm5qvAXZZXCc4tVFoU+Jw=; b=08lCIDolkbyAncpOBvb/kOTqk5ytWlznU6bBc3X2BZ76HCtEvLTiwtHxkUsl2hbxIK f9nMjZjZWLkmt2h1NvWQgekq4QTplOAcEb/CsHWK7A09P47giOqruQoe0AETcE6xR7TN QgExzOWLFUI01sPv037acfGRzMCI5ZGArSGAnVzEPJAauuSDm3kOicM1lk9cKipGUzm5 ym2lMb/Vii3m1cd3oY62BO0KNnPoUHLOjeew4oGfvkYhIkzWB1RNEKXVZ2zkdLr16DbA F/td9D4DtcQenGRKpw4R/lm8Xa9x2IQv2bxk0k+WsHnOpT4qJotWskUkHIUUlT4KNhjh rzBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=Mi2IZH4B3VzwDRPgoG0/2DNm5qvAXZZXCc4tVFoU+Jw=; b=VmmsSB3lOXZGugw1lXgDBXmoGVjtoDeRsEiLaTPEML1b92WZCZZw41Zv8rKSM1KhVh kGJPv8pNADnKEOvmyfPhZlYm9YevpmVZXAHcXBFhB8soLQArLhqBqM68+/tba9AMkmgL N3HX37Q3XO5ss+cxms33+fbAcXNlHZ4DFkG86EOds5VwQMYQkzYjxaVxS0uYQkYRGCDe kMTQ9Fi2tozfOaUZhFTPfEYN5o5zYeC7NGTuh/kWwdgWNFqEM5fKb+Qkyp4OPlCgZV6A beE0RATbu4jLmrJyp7rmmSu9lKXlo7RMOmmQauw6YXTzyIjleofrpQNoEEr6k8+OhwcJ wGSQ==
X-Gm-Message-State: ABUngvdq8LnziG0iGXu5I9HXTXvriWdo3jOsayJ9QYxjJAq5v90OVAZLnmvx05ov0EjWxos1mlq2eRte2Hjqvw==
X-Received: by 10.200.45.6 with SMTP id n6mr735334qta.220.1478893444903; Fri, 11 Nov 2016 11:44:04 -0800 (PST)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.53.155 with HTTP; Fri, 11 Nov 2016 11:44:04 -0800 (PST)
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Fri, 11 Nov 2016 11:44:04 -0800
X-Google-Sender-Auth: QGWXR_js4aYdRPywDeNwloKDUYs
Message-ID: <CAJE_bqe=yKfeJEba=ddsSaY1=8Nh35gEJ17y9jtqD5VzjUKG2w@mail.gmail.com>
Subject: comments on draft-ietf-6man-rs-refresh-02
To: IPv6 IPv6 List <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/zuvta0dYd1pnquLItdMDbuxBGOk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 11 Nov 2016 19:44:10 -0000
I have a couple of minor comments on draft-ietf-6man-rs-refresh-02: - we might want to say the source link-layer address option SHOULD be included in RAs that contain the Refresh Time option with U-flag being on, since the hosts receiving the RAs are expected to send unicast RSes to the router subsequently as described in Section 7: [...] Otherwise the host will unicast the RS refresh to each router in the default router list. - On Section 9: In addition to the checks in that section, the routers SHOULD verify that the RTO have the same Refresh Time, and report to system management if they differ. I'd note this may be tricky if these routers omit periodic multicast RA since their chance of doing this check may be limited to the initial gratuitous multicast RAs. -- JINMEI, Tatuya