RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt

"Hemant Singh (shemant)" <shemant@cisco.com> Thu, 03 July 2008 21:35 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2BA263A6912; Thu, 3 Jul 2008 14:35:51 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFE463A6868 for <ipv6@core3.amsl.com>; Thu, 3 Jul 2008 14:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.161
X-Spam-Level:
X-Spam-Status: No, score=-6.161 tagged_above=-999 required=5 tests=[AWL=0.438, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 g498LC4s5UUI for <ipv6@core3.amsl.com>; Thu, 3 Jul 2008 14:35:48 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id A44083A680E for <ipv6@ietf.org>; Thu, 3 Jul 2008 14:35:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,744,1204502400"; d="scan'208";a="13159085"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 03 Jul 2008 21:35:56 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m63LZuot017550; Thu, 3 Jul 2008 17:35:56 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m63LZugr006184; Thu, 3 Jul 2008 21:35:56 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 3 Jul 2008 17:35:56 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt
Date: Thu, 3 Jul 2008 17:35:56 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E41EB9@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <200807032111.m63LBUCF014613@cichlid.raleigh.ibm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt
Thread-Index: AcjdUZZSqzrpO2evTEChXBmXSZ9gkQAAlqgw
References: <486388BD.2090801@innovationslab.net> <200807031925.m63JPRp7031611@cichlid.raleigh.ibm.com> <B00EDD615E3C5344B0FFCBA910CF7E1D04E41EB6@xmb-rtp-20e.amer.cisco.com> <200807032111.m63LBUCF014613@cichlid.raleigh.ibm.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Thomas Narten" <narten@us.ibm.com>
X-OriginalArrivalTime: 03 Jul 2008 21:35:56.0650 (UTC) FILETIME=[C70BF4A0:01C8DD54]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1773; t=1215120956; x=1215984956; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=shemant@cisco.com; z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco. com> |Subject:=20RE=3A=206MAN=20WG=20Last=20Call=3Adraft-ietf-6m an-ipv6-subnet-model-00.txt |Sender:=20 |To:=20=22Thomas=20Narten=22=20<narten@us.ibm.com>; bh=Ko+DHxe+D2rHT8w//XZmBcFLHJf9DHi1g2R2fn6bBIA=; b=cgBew+sZqvCJnEUiywEdiiZkownUjag2o2Jm6tdV/+4gbfaksxU1iwnSoF OjIaWo5Id95e/t24XBS6tHrBe4Z54gGWXP3DkWCeB3Cl/D+GROqKPF+jASGJ vw4rHaU31d;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: ipv6@ietf.org, Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@nokia.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Thomas,

Will something like this work for you - we have replaced "change" with
"clarification".

[The source of an ND message is no longer used for on-link
determination, which is a clarification of bullet four of on-link
definition in Terminology section of [RFC4861].]

or 

[The source of an ND message is no longer used for on-link
determination, which is a clarification of on-link definition in
Terminology section of [RFC4861].]


I agree with you, no implementations have actually interpreted this
source address rule, but when folks like David notice the bug, folks
quote the definition of on-link in Terminology section of RFC4861. That
is why we thought of adding this line to our doc.

Thanks.

Hemant

-----Original Message-----
From: Thomas Narten [mailto:narten@us.ibm.com] 
Sent: Thursday, July 03, 2008 5:12 PM
To: Hemant Singh (shemant)
Cc: Brian Haberman; Bob Hinden; ipv6@ietf.org
Subject: Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt


> Sorry, I forgot one item that Wes just reminded me of. Earlier in the 
> day I had emailed out our new text for bullet 2 that has this new
line:

> "The source of an ND message is no longer used for on-link 
> determination, which is a change from [RFC4861]."

I object, because I do not believe 4861 really says this (if you look
across the document in totality) or was widely interpreted to say this.

Until the recent notes from David Miles, I don't think anyone noticed
the bug. Certainly, I have seen no evidence that implementations
actually interpreted 4861 or its predecessors and actually did the wrong
thing when receiving an NS.

So, we can call certainly this a clarification, but I'd hesitate to call
it a change.

Thomas
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------