Re: Comments on draft-yourtchenko-colitti-nd-reduce-multicast

Ole Troan <otroan@employees.org> Tue, 25 February 2014 09:31 UTC

Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554A71A0657 for <ipv6@ietfa.amsl.com>; Tue, 25 Feb 2014 01:31:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 Ip5WF8sXXjnC for <ipv6@ietfa.amsl.com>; Tue, 25 Feb 2014 01:31:13 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) by ietfa.amsl.com (Postfix) with ESMTP id 65E7D1A0663 for <ipv6@ietf.org>; Tue, 25 Feb 2014 01:31:12 -0800 (PST)
Received: from dhcp-10-61-104-154.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 23BB360D8; Tue, 25 Feb 2014 01:31:08 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_E17D059A-40F0-4878-9E42-757BB18A4BF3"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Comments on draft-yourtchenko-colitti-nd-reduce-multicast
From: Ole Troan <otroan@employees.org>
In-Reply-To: <C43B8408-5249-423E-8361-E8619C280E25@cisco.com>
Date: Tue, 25 Feb 2014 10:31:06 +0100
Message-Id: <1657A615-4C3F-4C59-9A87-05B78905F264@employees.org>
References: <5305AF13.5060201@acm.org> <7461F3DA-FB05-400D-9C54-2F30C73DE2B9@employees.org>, <530BCF83.4090500@acm.org> <C43B8408-5249-423E-8361-E8619C280E25@cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/3HwhTpdfXCD8IRy5Q7Fb8fYMB44
Cc: Erik Nordmark <nordmark@acm.org>, Andrew Yourtchenko <ayourtch@cisco.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2014 09:31:16 -0000

Pascal,

> And we need to remember that the assignment is just one component of the lifecycle of an address. 
> 
> When the client stops using an address, or moves the address somewhere else in the fabric, there is a need to update the network support that defends the address and proxies.

why isn't that: SOLICIT, CONFIRM, RENEW, REBIND, RELEASE?

cheers,
Ole without hat.