RE: I-D Action: draft-ietf-6man-enhanced-dad-01.txt
"Hemant Singh (shemant)" <shemant@cisco.com> Sat, 08 September 2012 21:44 UTC
Return-Path: <shemant@cisco.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 416C121F84DA for <ipv6@ietfa.amsl.com>; Sat, 8 Sep 2012 14:44:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kkMCE6BWn+EK for <ipv6@ietfa.amsl.com>; Sat, 8 Sep 2012 14:44:39 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 9055721F84D9 for <ipv6@ietf.org>; Sat, 8 Sep 2012 14:44:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1681; q=dns/txt; s=iport; t=1347140679; x=1348350279; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=gBL3TV7JURabbouI13m6tOhJAxtyLgpRKdVRBTvBWVo=; b=ac2ux72XbwCJPVkfhb1mary6q8/nw8Iq86NCkHuk5kAO8c3y5CbLahRs HjmVRFTaUF/8Lee31KTLVWXsUI7LnTcd4g/lLrgFmDM5wlo93JVneyOgL x+WhQqZficDPflyZyYXeQ4H/7JN8c11Uz54jfN+PDZgWKSWxU4lsxxmJl A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EABi7S1CtJXG//2dsb2JhbABFu1OBB4IgAQEBBBIBJzQLDAQCAQgOAwQBAQsUCQcyFAkIAgQBDQUIGodumwSfHIsThVZgA6QTgWeCZoFj
X-IronPort-AV: E=Sophos;i="4.80,392,1344211200"; d="scan'208";a="116662624"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-9.cisco.com with ESMTP; 08 Sep 2012 21:44:39 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id q88LidFk009087 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 8 Sep 2012 21:44:39 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.230]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0298.004; Sat, 8 Sep 2012 16:44:38 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: Ray Hunter <v6ops@globis.net>, "draft-ietf-6man-enhanced-dad@tools.ietf.org" <draft-ietf-6man-enhanced-dad@tools.ietf.org>
Subject: RE: I-D Action: draft-ietf-6man-enhanced-dad-01.txt
Thread-Topic: I-D Action: draft-ietf-6man-enhanced-dad-01.txt
Thread-Index: AQHNjbO8RVNJOyJbNUmsXyxWVlLVe5eA8RvQ
Date: Sat, 08 Sep 2012 21:44:37 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B89083623@xmb-rcd-x06.cisco.com>
References: <504B2961.5060605@globis.net>
In-Reply-To: <504B2961.5060605@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.246.129]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19172.001
x-tm-as-result: No--29.712300-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 08 Sep 2012 21:44:40 -0000
Ray, Appreciate the review. I will send another email to reply to your questions related to use cases. Other questions have been addressed below. -----Original Message----- From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Ray Hunter Sent: Saturday, September 08, 2012 7:18 AM To: draft-ietf-6man-enhanced-dad@tools.ietf.org Cc: 6man Mailing List Subject: I-D Action: draft-ietf-6man-enhanced-dad-01.txt >Since the (tentative) IID and DAD operation is address and interface >specific; as well as the nonce, should the node also remember on which >interface the NS(DAD) was sent, and also for which (tentative) address? Yes. Note RFC 4862 is interface-specific for DAD of each IPv6 address used by the interface and RFC 4861 is also interface-specific for the ND protocol. >Should the node generate a separate nonce per instance of the DAD >algorithm, or per interface initialisation? Anytime DAD is performed by a network interface for an IPv6 address, a separate nonce is generated. The reason is because, by definition, a nonce is used only once and the interface has to perform DAD for each IPv6 address used by the interface. Our document is using the nonce defined by RFC 3971. See section 2 of RFC 3971 and the definition of the "Nonce" term on page 5. Other sections in RFC 3971 has additional details on the Nonce Option. >When is it safe for a node to garbage collect the stored nonce? >When should a node garbage collect the stored nonce [e.g. to cover >equipment moves and interface re-patching]? >Once DAD completes? Once DAD completes. Regards, Hemant
- I-D Action: draft-ietf-6man-enhanced-dad-01.txt Ray Hunter
- I-D Action: draft-ietf-6man-enhanced-dad-01.txt internet-drafts
- RE: I-D Action: draft-ietf-6man-enhanced-dad-01.t… Hemant Singh (shemant)
- RE: I-D Action: draft-ietf-6man-enhanced-dad-01.t… Hemant Singh (shemant)
- Re: I-D Action: draft-ietf-6man-enhanced-dad-01.t… Ray Hunter
- FW: I-D Action: draft-ietf-6man-enhanced-dad-01.t… Hemant Singh (shemant)
- RE: I-D Action: draft-ietf-6man-enhanced-dad-01.t… Hemant Singh (shemant)