Re: [dhcwg] Regarding DhcpV6 alternatives to dhcpv4 option 118 and dhcp option 82 sub-option 5
"Bernie Volz (volz)" <volz@cisco.com> Thu, 16 January 2014 14:19 UTC
Return-Path: <volz@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 EE2BE1AE2C3 for <dhcwg@ietfa.amsl.com>; Thu, 16 Jan 2014 06:19:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.038
X-Spam-Level:
X-Spam-Status: No, score=-15.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, 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 uBbSX98foIF3 for <dhcwg@ietfa.amsl.com>; Thu, 16 Jan 2014 06:19:49 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id C145E1AE0C8 for <dhcwg@ietf.org>; Thu, 16 Jan 2014 06:19:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7783; q=dns/txt; s=iport; t=1389881977; x=1391091577; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=TFZp0FzwGBuUrHjumtlzKKhV3rePmNdUKdgbSmw6U30=; b=JnXwHiVvTaw8acs5vYCIrhq3eqBEUGUHmlEgz/o6CclPxB3HLAdZNlXf 3C+wBL08Faebu2larVoL/jOE2w60DZXN/httSec4uAxTrvA+OV1zXW195 Gx6eFiuCiYHddGO53ja46LjpqGnWMxB01/vMjARtWgOZQdbsniC3kwfLA g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlEFAObp11KtJV2d/2dsb2JhbABZgkdEOFa7C4ELFnSCJQEBAQQtXAIBCA4DBAEBCx0HMhQJCAEBBAESCId8xDUXjk43AYMkgRQEqjiBb4E+gio
X-IronPort-AV: E=Sophos; i="4.95,668,1384300800"; d="scan'208,217"; a="297558350"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 16 Jan 2014 14:19:36 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s0GEJaEo017319 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Jan 2014 14:19:36 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Thu, 16 Jan 2014 08:19:36 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Vivek Dadu <vdadu@microsoft.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Regarding DhcpV6 alternatives to dhcpv4 option 118 and dhcp option 82 sub-option 5
Thread-Index: Ac8StZJncfxA+dXbSxOzBKsZbhMVuQAEDdNQ
Date: Thu, 16 Jan 2014 14:19:35 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE22FA7@xmb-rcd-x04.cisco.com>
References: <2D833948ADBB574BAB0A4AD8CF32A8991B464E7B@SINEX14MBXC418.southpacific.corp.microsoft.com>
In-Reply-To: <2D833948ADBB574BAB0A4AD8CF32A8991B464E7B@SINEX14MBXC418.southpacific.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.242.7]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1AE22FA7xmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: Re: [dhcwg] Regarding DhcpV6 alternatives to dhcpv4 option 118 and dhcp option 82 sub-option 5
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: Thu, 16 Jan 2014 14:19:51 -0000
The link-address field in the Relay-Forw is usually used for this and no link-selection option is needed. The reason v4 needs this is that giaddr is both the relay agent's address AND the default link-selection. With DHCPv6, there is no overloading - the Relay Agent address is obtained from the IPv6 header (source address) the link-selection is the link-address field in the Relay-Forw. - Bernie From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Vivek Dadu Sent: Thursday, January 16, 2014 7:23 AM To: dhcwg@ietf.org Subject: [dhcwg] Regarding DhcpV6 alternatives to dhcpv4 option 118 and dhcp option 82 sub-option 5 Hi All I would like to know whether there are any link selection options for dhcpv6 like option 118 for dhcpv4 client and Option 82 Sub-option 5 for DHCP V4 relay agents. Regards Vivek
- [dhcwg] Regarding DhcpV6 alternatives to dhcpv4 o… Vivek Dadu
- Re: [dhcwg] Regarding DhcpV6 alternatives to dhcp… Bernie Volz (volz)