Fwd: New Version Notification for draft-ietf-6man-rs-refresh-01.txt
Erik Nordmark <nordmark@acm.org> Tue, 22 March 2016 17:28 UTC
Return-Path: <nordmark@acm.org>
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 AA00512D13C for <ipv6@ietfa.amsl.com>; Tue, 22 Mar 2016 10:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] 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 FU0Ui492i58O for <ipv6@ietfa.amsl.com>; Tue, 22 Mar 2016 10:28:29 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 50B1F12D1E8 for <6man@ietf.org>; Tue, 22 Mar 2016 10:28:29 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id u2MHSOm6023925 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 22 Mar 2016 10:28:24 -0700
Subject: Fwd: New Version Notification for draft-ietf-6man-rs-refresh-01.txt
References: <20160321161949.31924.24504.idtracker@ietfa.amsl.com>
To: "6man@ietf.org" <6man@ietf.org>
From: Erik Nordmark <nordmark@acm.org>
X-Forwarded-Message-Id: <20160321161949.31924.24504.idtracker@ietfa.amsl.com>
Message-ID: <56F180B8.4060001@acm.org>
Date: Tue, 22 Mar 2016 10:28:24 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <20160321161949.31924.24504.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVZEegZynFfbylhJ/tCfmXr43uYeBUpVb3cfPTDq2/TaF1dsrmgRt9pxm98ss6NbdQSk09VC8RvbigEOzhZ4cJ1K
X-Sonic-ID: C;fH9Te1Pw5RGzPpFDXdaMvg== M;/J97e1Pw5RGzPpFDXdaMvg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/l3dy8MlaJLaKFyAg5MLp-QPCScg>
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: Tue, 22 Mar 2016 17:28:30 -0000
I don't understand why this wasn't sent to the 6man list automagically. Anyhow, please review and see if we need to add some strong(er) language about this not being an excuse for ignoring multicast RAs. The statement we want to make is something along the lines of: If a host is receiving unicast IP packets, then it MUST NOT ignore periodic (multicast) RAs. The purpose of the draft is that a host which power's off its receiver (hence doesn't receive any IP packets) can quickly use RS-refresh to get any updates when it wakes up. But given the experience that Lorenzo and folks have had with implementations which ignore multicast RAs we need to make sure the language is sufficiently tight in this document. Thanks, Erik -------- Forwarded Message -------- Subject: New Version Notification for draft-ietf-6man-rs-refresh-01.txt Date: Mon, 21 Mar 2016 09:19:49 -0700 From: internet-drafts@ietf.org To: Erik Nordmark <nordmark@acm.org>, Andrew Yourtchenko <ayourtch@cisco.com>, Suresh Krishnan <suresh.krishnan@ericsson.com> A new version of I-D, draft-ietf-6man-rs-refresh-01.txt has been successfully submitted by Erik Nordmark and posted to the IETF repository. Name: draft-ietf-6man-rs-refresh Revision: 01 Title: IPv6 Neighbor Discovery Optional RS/RA Refresh Document date: 2016-03-21 Group: 6man Pages: 14 URL: https://www.ietf.org/internet-drafts/draft-ietf-6man-rs-refresh-01.txt Status: https://datatracker.ietf.org/doc/draft-ietf-6man-rs-refresh/ Htmlized: https://tools.ietf.org/html/draft-ietf-6man-rs-refresh-01 Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-rs-refresh-01 Abstract: IPv6 Neighbor Discovery relies on periodic multicast Router Advertisement messages to update timer values and to distribute new information (such as new prefixes) to hosts. On some links the use of periodic multicast messages to all host becomes expensive, and in some cases it results in hosts waking up frequently. Many implementations of RFC 4861 also use multicast for solicited Router Advertisement messages, even though that behavior is optional. This specification provides an optional mechanism for hosts and routers where instead of periodic multicast Router Advertisements the hosts are instructed (by the routers) to use Router Solicitations to request refreshed Router Advertisements. This mechanism is enabled by configuring the router to include a new option in the Router Advertisement in order to allow the network administrator to choose host behavior based on whether periodic multicast are more efficient on their link or not. The routers can also tell whether the hosts are capable of the new behavior through a new flag in the Router Solicitations. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat
- Fwd: New Version Notification for draft-ietf-6man… Erik Nordmark