Re: I-D Action:draft-ietf-6man-ipv6-subnet-model-00.txt
Suresh Krishnan <suresh.krishnan@ericsson.com> Wed, 18 June 2008 20:55 UTC
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipngwg-archive@lists.ietf.org
Delivered-To: ietfarch-ipngwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCD603A6914; Wed, 18 Jun 2008 13:55:30 -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 257863A6914; Wed, 18 Jun 2008 13:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.442
X-Spam-Level:
X-Spam-Status: No, score=-6.442 tagged_above=-999 required=5 tests=[AWL=0.157, 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 qXlPkJ5TtNMf; Wed, 18 Jun 2008 13:55:29 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 1F84F3A68D4; Wed, 18 Jun 2008 13:55:29 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m5IKuBI2018579; Wed, 18 Jun 2008 15:56:12 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jun 2008 15:56:29 -0500
Received: from [142.133.10.113] ([142.133.10.113]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jun 2008 15:56:28 -0500
Message-ID: <485976A1.2010604@ericsson.com>
Date: Wed, 18 Jun 2008 16:57:05 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080505)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: Re: I-D Action:draft-ietf-6man-ipv6-subnet-model-00.txt
References: <20080508140001.790BB28D372@core3.amsl.com> <B00EDD615E3C5344B0FFCBA910CF7E1D04E41CA4@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D04E41CA4@xmb-rtp-20e.amer.cisco.com>
X-OriginalArrivalTime: 18 Jun 2008 20:56:28.0313 (UTC) FILETIME=[C7362890:01C8D185]
Cc: ipv6@ietf.org, Erik Nordmark <erik.nordmark@sun.com>, Internet-Drafts@ietf.org, i-d-announce@ietf.org
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
Hi Hemant, I went through the document and it looks very good. There is just one thing I would like to comment on. * The document claims to only clarify RFC4861 but it overreaches a bit. If you look at section 2 bullet 3, this lays out a NEW rule for a host to follow. This rule does not exist in RFC4861. I personally feel that this rule is intuitive and desirable, but it is certainly not backward compatible. Cheers Suresh Hemant Singh (shemant) wrote: > Folks, > > Could you please review this draft now that it's a 6man WG work item. So > far this version has taken care of comments on an earlier version that > the following folks reviewed. > > Suresh Krishnan > Jinmei Tatuya > Thomas Narten > Ralph Droms > > Brian Carpenter sent us a private email on his review of this version. > We have taken care of his review as follows. > > At the end of section 2, the following paragraph has been changed from > > [This case is analogous to the behavior > specified in the last paragraph of section 7.2.2 of > [RFC4861]: when address resolution fails, the host SHOULD > send an ICMPv6 Destination Unreachable indication as > specified in [RFC4861]. The specified behavior MAY be > extended to cover this case where address resolution cannot > be performed.] > > to > > [This case is specified in the last paragraph of section 4 of > [RFC4943]: when there is no route to destination, the host > should send an ICMPv6 Destination Unreachable indication > (for example, a locally delivered error message) as > specified in the Terminology section of [RFC4861].] > > > Thanks, > > Hemant > > > -----Original Message----- > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of > Internet-Drafts@ietf.org > Sent: Thursday, May 08, 2008 10:00 AM > To: i-d-announce@ietf.org > Cc: ipv6@ietf.org > Subject: I-D Action:draft-ietf-6man-ipv6-subnet-model-00.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the IPv6 Maintenance Working Group of the > IETF. > > > Title : IPv6 Subnet Model: the Relationship between > Links and Subnet Prefixes > Author(s) : H. Singh, et al. > Filename : draft-ietf-6man-ipv6-subnet-model-00.txt > Pages : 8 > Date : 2008-05-08 > > IPv6 specifies a model of a subnet that is different than the IPv4 > subnet model. The subtlety of the differences has resulted in incorrect > implementations that do not interoperate. This document spells out the > most important difference; that an IPv6 address isn't automatically > associated with an IPv6 on-link prefix. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-6man-ipv6-subnet-model-00 > .txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- I-D Action:draft-ietf-6man-ipv6-subnet-model-00.t… Internet-Drafts
- RE: I-D Action:draft-ietf-6man-ipv6-subnet-model-… Hemant Singh (shemant)
- Re: I-D Action:draft-ietf-6man-ipv6-subnet-model-… Suresh Krishnan
- RE: I-D Action:draft-ietf-6man-ipv6-subnet-model-… Hemant Singh (shemant)