Re: [dhcwg] Prefix-length of an assigned address, in a DHCPv6 message

"Hemant Singh (shemant)" <shemant@cisco.com> Wed, 10 September 2014 10:57 UTC

Return-Path: <shemant@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F36B1A6F2B for <dhcwg@ietfa.amsl.com>; Wed, 10 Sep 2014 03:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.153
X-Spam-Level:
X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YF8Oz8OFn_ne for <dhcwg@ietfa.amsl.com>; Wed, 10 Sep 2014 03:57:04 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17A5D1A6F47 for <dhcwg@ietf.org>; Wed, 10 Sep 2014 03:57:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3186; q=dns/txt; s=iport; t=1410346624; x=1411556224; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=CVENC/cxDociFzcnhUovlVpFtTo7W/ZrcA1gaCgAzLk=; b=LlkqIBPypZ8/smQMpUptTQnYPqEOgIKGV5wiP/fQ/6kE7zRq1HtgBrrb R0nW5SnL6DBi755EkFWoyl5vzLivT8QM4IGNGVeEAVlP7I162BW7OFrp3 qm7ixe4RytNk4T9Cl0+s4qFSjLq+0ei+IsEvQFUhQtkGuIobzk2BrRHOu 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikFAA4uEFStJV2P/2dsb2JhbABZgw1TVwTKIAyHSgGBDBZ4hAMBAQEDAQEBATc0CwUHBAIBCBEEAQELFAkHJwsUCQgCBAENBQiIMggNvUkBF45rEQEfMQcGgymBHQWRQYQwiGGTT4NhbIEPOYEHAQEB
X-IronPort-AV: E=Sophos;i="5.04,498,1406592000"; d="scan'208";a="354061519"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-6.cisco.com with ESMTP; 10 Sep 2014 10:57:02 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s8AAv2wC003183 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 10 Sep 2014 10:57:02 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.218]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0195.001; Wed, 10 Sep 2014 05:57:02 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, Ralph Droms <rdroms.ietf@gmail.com>, Simon Hobson <linux@thehobsons.co.uk>
Thread-Topic: [dhcwg] Prefix-length of an assigned address, in a DHCPv6 message
Thread-Index: AQHPyRs8NyciopNb4Uy41AeEordXXZvzEkAAgAAdswCABRQjAIAA/uGAgAAQ8YCAAEjWAIAAc0UAgAApQtA=
Date: Wed, 10 Sep 2014 10:57:02 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B89155B07E6@xmb-rcd-x06.cisco.com>
References: <20140519150302.3625.29866.idtracker@ietfa.amsl.com> <489D13FBFA9B3E41812EA89F188F018E1B03125B@xmb-rcd-x04.cisco.com> <53E3872A.30204@gmail.com> <53E38954.1030206@gmail.com> <AD6668B4-834A-4777-B667-006BA06A2C4F@gmail.com> <53E39157.8060708@gmail.com> <CAJE_bqcr5ytrgrUWwPLvZ=vHNPe=C4OZcah0529suOLOgM6odA@mail.gmail.com> <53E39635.60608@gmail.com> <CAJE_bqcv6PavTP_-EM-FMwD1hVrsqnfmWaCceZQshsxXNVr=4w@mail.gmail.com> <5409C1B8.3000101@gmail.com> <EC3A32FA-CE3F-41DC-A7CF-109F87980DE9@gmail.com> <5409D1A0.4040407@gmail.com> <F23B845B-5409-4D05-92A3-EF57505D9C64@gmail.com> <CAJE_bqd2y4oNEHBoLi0LgUX5-op7UndXhzaLKu7PCMZeeMGqGQ@mail.gmail.com> <540E4368.5050809@gont.com.ar> <10C0F0D1-8498-43E4-A083-2DB2BAB896B2@gmail.com> <DF8CBD46-2CA4-4E3A-9406-ABD711B023D8@thehobsons.co.uk> <CB9E81C7-A0E7-4653-92EF-6C8974D05494@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B686B30@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B686B30@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.248.180]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/MDaMd_cik6npt0dqLhAMpqtZJVM
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] Prefix-length of an assigned address, in a DHCPv6 message
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 10:57:06 -0000

Few years back, in the 6man mailer, we have discussed this issue.  If the router has different prefix length than what the DHCPv6 server assigned to the client, who wins?

Hemant

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Tuesday, September 09, 2014 11:28 PM
To: Ralph Droms; Simon Hobson
Cc: dhcwg
Subject: Re: [dhcwg] Prefix-length of an assigned address, in a DHCPv6 message

Perhaps it has been raised already in this thread, but there is again a draft on using DHCPv6 for some ND aspects:

http://datatracker.ietf.org/doc/draft-sarikaya-dhc-dhcpv6-raoptions-sadr

I am not advocating this work, just pointing out it is yet another attempt to distribute prefix information via DHCPv6.

There already has been an email discussion with the author that this work is probably best done in another WG (if at all).

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ralph Droms
Sent: Tuesday, September 09, 2014 4:35 PM
To: Simon Hobson
Cc: dhcwg
Subject: Re: [dhcwg] Prefix-length of an assigned address, in a DHCPv6 message

Simon ...

On Sep 9, 2014, at 12:14 PM 9/9/14, Simon Hobson <linux@thehobsons.co.uk> wrote:

> Perhaps it's just me struggling to break out from "IPv4 thinking", but I struggle to see what use an IPv6 address is without explicitly or implicitly a prefix length to go with it. Unless you restrict yourself to "on link" communications, at some point you need to work out whether, when using that address, the other address you wish to communicate with is local (on link) or remote.

The way I think about IPv6 addresses, prefixes and prefix length is that the prefix length is associated with the prefix, not the address.  In typical usage, the prefix is matched against the leftmost bits of the address corresponding to the prefix length and a match indicates the address is in the subnet defined by the prefix.

In my opinion, the "IPv4 thinking" is the association of a prefix length with an address, implicitly defining a prefix; for example, an on-link prefix derived from an assigned address.  In IPv6, prefixes and addresses are more clearly delineated and the prefix lengths are associated explicitly with the prefixes.

> 
> I know there's the arguments that in many large organisations, the routers and DHCP servers are managed by different groups - but the groups still need to agree on what the prefixes and prefix lengths are for any network !

Yes, there need to be agreement - and the agreed upon conventions are typically expressed in ND PIOs, which give the lengths for the advertised prefixes.

- Ralph

> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg