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

"Wojciech Dec (wdec)" <wdec@cisco.com> Thu, 26 June 2008 17:32 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 0FA113A6A08; Thu, 26 Jun 2008 10:32:15 -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 06EBF3A6A08 for <ipv6@core3.amsl.com>; Thu, 26 Jun 2008 10:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 2Z3slUIdiM8s for <ipv6@core3.amsl.com>; Thu, 26 Jun 2008 10:32:10 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 5980E3A68E3 for <ipv6@ietf.org>; Thu, 26 Jun 2008 10:32:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,709,1204498800"; d="scan'208";a="12781067"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 26 Jun 2008 19:32:11 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m5QHWB58032630; Thu, 26 Jun 2008 19:32:11 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m5QHWB3L010351; Thu, 26 Jun 2008 17:32:11 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Jun 2008 19:32:11 +0200
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, 26 Jun 2008 19:32:07 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D4054291A5@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03A2C459@xmb-rtp-211.amer.cisco.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: AcjXjoFxMisnTMw3QlKNp3HTw669XgAAhZKAAAHjtdAABZ0y8A==
References: <D9872168DBD43A41BD71FFC4713274D405429068@xmb-ams-33b.emea.cisco.com> <BB56240F3A190F469C52A57138047A03A2C459@xmb-rtp-211.amer.cisco.com>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>, "Brian Haberman" <brian@innovationslab.net>, <ipv6@ietf.org>
X-OriginalArrivalTime: 26 Jun 2008 17:32:11.0302 (UTC) FILETIME=[90C4B460:01C8D7B2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4292; t=1214501531; x=1215365531; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=wdec@cisco.com; z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com> |Subject:=20RE=3A=206MAN=20WG=20Last=20Call=3Adraft-ietf-6m an-ipv6-subnet-model-00.txt |Sender:=20; bh=R6TB86v+Zkqs1Mft83lVA848ClXV3zE0LXN6+B6dooo=; b=Sj5ZRFxN/tLxebv66RI4mf2idqRLqSubIGlsjRMbETlfLQk1FNtOiSDhJh 0OaMeoFCp7HeRensqlljCzIhOwYw60HodcS4Bj+QTewnlO+HxitGGo2ca3mG mDNhGY1K75;
Authentication-Results: ams-dkim-2; header.From=wdec@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
Cc: Bob Hinden <bob.hinden@nokia.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
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

I understand that the topic has a fair bit of history, but could someone
please re-explain the use-case that justifies keeping such
cross-subnet-but-hey-no-router behaviour? 
Personally I see little value in it in today's world of home routers,
but plenty of potential for confusion for users if not downright
additional security issues for operators.

-Woj.


> -----Original Message-----
> From: Wes Beebee (wbeebee) 
> Sent: 26 June 2008 16:29
> To: Wojciech Dec (wdec); Brian Haberman; ipv6@ietf.org
> Cc: MILES DAVID; Bob Hinden
> Subject: RE: 6MAN WG Last 
> Call:draft-ietf-6man-ipv6-subnet-model-00.txt
> 
> This rule derives directly from the Terminology section of 
> RFC 4861 (definition of on-link).
> 
> Note that the presence of a bogus entry causes no harm (the 
> routing table takes precedence over the ND cache in this case).
> 
> However, the removal of the rule DOES cause harm in the case 
> of communication without routers.
> 
> Therefore, we currently see no reason to change the text.
> 
> - Wes & Hemant
> 
> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On 
> Behalf Of Wojciech Dec (wdec)
> Sent: Thursday, June 26, 2008 10:05 AM
> To: Brian Haberman; ipv6@ietf.org
> Cc: MILES DAVID; Bob Hinden
> Subject: RE: 6MAN WG Last 
> Call:draft-ietf-6man-ipv6-subnet-model-00.txt
> 
> Based on a recent thread
> (http://www.ops.ietf.org/lists/v6ops/v6ops.2008/msg00896.html)
>  the following paragraph from the draft appears to warrant 
> some more thought if not outright a revision
> 
> "   In addition to the Prefix List, individual addresses are 
> on-link if
>    they are the target of a Redirect Message indicating 
> on-link, or the
>    source of a valid Neighbor Solicitation or Neighbor Advertisement
>    message.  Note that Redirect Messages can also indicate an 
> address is
>    off-link.  Individual address entries can be expired by 
> the Neighbor
>    Unreachability Detection mechanism."
> 
> Using unconditionally the source address of a neighbour 
> solicitation or NA to determine on-link would indeed appear 
> to be undesirable, unless the intent is allow some direct 
> host-host cross subnet/prefix communication without a router 
> involved at any stage (this is not a good idea IMO). A 
> constraint could be introduced such as: A host only learns 
> on-link addresses from the source of NS and NA messages iff 
> it already has an on-link prefix that would cover that 
> address. Learning from Redirect messages would continue to be allowed.
> 
> My 2c.
> -Woj.
>  
> 
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] 
> On Behalf 
> > Of Brian Haberman
> > Sent: 26 June 2008 14:17
> > To: ipv6@ietf.org
> > Cc: Bob Hinden
> > Subject: 6MAN WG Last Call:draft-ietf-6man-ipv6-subnet-model-00.txt
> > 
> > All,
> >       This message starts a 3-week 6MAN Working Group Last Call on
> > advancing:
> > 
> >       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
> > 
> > as a Proposed Standard.  Substantive comments and statements of 
> > support for advancing this document should be directed to 
> the mailing 
> > list.
> > Editorial suggestions can be sent to the document editor.  
> > This last call will end on July 10, 2008.
> > 
> > Regards,
> > Brian & Bob
> > 6MAN co-chairs
> > --------------------------------------------------------------------
> > 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
> --------------------------------------------------------------------
> 
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------