Re: [dna] #17: DHCP and ND probes complete with different results

"dna issue tracker" <trac@tools.ietf.org> Wed, 16 September 2009 18:34 UTC

Return-Path: <trac@tools.ietf.org>
X-Original-To: dna@core3.amsl.com
Delivered-To: dna@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC0243A69DD for <dna@core3.amsl.com>; Wed, 16 Sep 2009 11:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level:
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ZEB6EflfC2G for <dna@core3.amsl.com>; Wed, 16 Sep 2009 11:34:45 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:1112:1:214:22ff:fe1f:1e54]) by core3.amsl.com (Postfix) with ESMTP id 274793A6966 for <dna@ietf.org>; Wed, 16 Sep 2009 11:34:44 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1MnzLq-0003uv-N2; Wed, 16 Sep 2009 11:35:34 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="ascii"
Content-Transfer-Encoding: 7bit
From: "dna issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.1
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.1, by Edgewall Software
To: suresh.krishnan@ericsson.com
X-Trac-Project: dna
Date: Wed, 16 Sep 2009 18:35:34 -0000
X-URL: http://tools.ietf.org/dna/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/dna/trac/ticket/17#comment:1
Message-ID: <075.6eada793adc012b3d7e50503c25d48f6@tools.ietf.org>
References: <066.877f7a236780113f81cb0d6f5fff6060@tools.ietf.org>
X-Trac-Ticket-ID: 17
In-Reply-To: <066.877f7a236780113f81cb0d6f5fff6060@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: suresh.krishnan@ericsson.com, dna@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: dna@ietf.org
Subject: Re: [dna] #17: DHCP and ND probes complete with different results
X-BeenThere: dna@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: dna@ietf.org
List-Id: DNA working group mailing list <dna.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dna>, <mailto:dna-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dna>
List-Post: <mailto:dna@ietf.org>
List-Help: <mailto:dna-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dna>, <mailto:dna-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Sep 2009 18:34:46 -0000

#17: DHCP and ND probes complete with different results
------------------------------------------+---------------------------------
 Reporter:  suresh.krishnan@ericsson.com  |        Owner:  Suresh Krishnan
     Type:  defect                        |       Status:  closed         
 Priority:  major                         |    Milestone:                 
Component:  simple                        |      Version:                 
 Severity:  Active WG Document            |   Resolution:  fixed          
 Keywords:                                |  
------------------------------------------+---------------------------------
Changes (by suresh.krishnan@ericsson.com):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 I propose adding the following section to resolve this issue.

 4.7.1.  Conflicting results

    It is possible that the DHCPv6 based probes and the neighbor
    discovery based probes complete with conflicting results.  In this
    case, the host SHOULD use the following rules to determine the final
    result.

    o  If the DHCPv6 exchange was authenticated, use the result from the
       DHCPv6 probe.

    o  If the DHCPv6 exchange was not authenticated and the neighbor
       discovery exchange was protected by SEND [RFC3971], use the result
       from the neighbor discovery probe.

    o  If both the DHCPv6 and neighbor discovery exchanges were not
       authenticated, use the result from the DHCPv6 probe

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/dna/trac/ticket/17#comment:1>
dna <http://tools.ietf.org/dna/>