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

JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org> Thu, 10 July 2008 05:23 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 674E63A67EA; Wed, 9 Jul 2008 22:23:56 -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 E1B813A67EA for <ipv6@core3.amsl.com>; Wed, 9 Jul 2008 22:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.733
X-Spam-Level: *
X-Spam-Status: No, score=1.733 tagged_above=-999 required=5 tests=[AWL=-0.655, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RDNS_DYNAMIC=0.1]
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 E7YXA09E5pja for <ipv6@core3.amsl.com>; Wed, 9 Jul 2008 22:23:55 -0700 (PDT)
Received: from mon.jinmei.org (mon.jinmei.org [IPv6:2001:4f8:3:36::162]) by core3.amsl.com (Postfix) with ESMTP id 14AB43A67A2 for <ipv6@ietf.org>; Wed, 9 Jul 2008 22:23:55 -0700 (PDT)
Received: from jmb.jinmei.org (user-64-9-237-16.googlewifi.com [64.9.237.16]) by mon.jinmei.org (Postfix) with ESMTP id 4165533C2E; Wed, 9 Jul 2008 22:24:08 -0700 (PDT)
Date: Wed, 09 Jul 2008 22:24:05 -0700
Message-ID: <m2lk0a48i2.wl%Jinmei_Tatuya@isc.org>
From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: Re: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D04E41EFD@xmb-rtp-20e.amer.cisco.com>
References: <486388BD.2090801@innovationslab.net> <200807031925.m63JPRp7031611@cichlid.raleigh.ibm.com> <B00EDD615E3C5344B0FFCBA910CF7E1D04E41EB6@xmb-rtp-20e.amer.cisco.com> <200807032111.m63LBUCF014613@cichlid.raleigh.ibm.com> <B00EDD615E3C5344B0FFCBA910CF7E1D04E41EB9@xmb-rtp-20e.amer.cisco.com> <m2k5fv6b4b.wl%Jinmei_Tatuya@isc.org> <B00EDD615E3C5344B0FFCBA910CF7E1D04E41EFD@xmb-rtp-20e.amer.cisco.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.1 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Cc: Thomas Narten <narten@us.ibm.com>, Bob Hinden <bob.hinden@nokia.com>, Brian Haberman <brian@innovationslab.net>, ipv6@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

At Wed, 9 Jul 2008 12:21:06 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Erik suggested some new text to us related to bullets 3 and 4 of on-link
> definition in the Terminology section of RFC4861. He is busy this week -
> we are sending this on his behalf. As you know bullet 4 is being debated
> in 6man. Erik thinks even bullet 3 is suspect. We don't want such
> suspect information to be lost in archived emails of 6man. So we added
> the information to our draft. Please see the new paragraph from us:
> 
> 
>                The on-link definition in the Terminology section of
> [RFC4861] 
>                defines the complete list of cases where an address is
> considered on-link.
>                Note, in particular, that Redirect Messages can also
> indicate an address is off-link. 
>                As of the writing of this document, bullets three and
> four of the on-link
>                definition are being debated and may need further
> clarification.
>                Individual address entries can be expired by the Neighbor
> Unreachability 
>                Detection mechanism.
> 
> Please let us know if the new text works for you?

This text works for me (although I guess these new sentences would be
a very good target for the IESG to make a "discuss" comment - good
luck:-).

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------