IETF Logo Mail Archive

Re: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt

"Prashanth Patil (praspati)" <praspati@cisco.com> Wed, 05 February 2014 04:07 UTC

Return-Path: <praspati@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 2C7551A0029 for <dhcwg@ietfa.amsl.com>; Tue, 4 Feb 2014 20:07:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.036
X-Spam-Level:
X-Spam-Status: No, score=-15.036 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=-0.535, 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 3Bkvs_-8O0xw for <dhcwg@ietfa.amsl.com>; Tue, 4 Feb 2014 20:07:16 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id B3D6F1A0028 for <dhcwg@ietf.org>; Tue, 4 Feb 2014 20:07:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1063; q=dns/txt; s=iport; t=1391573235; x=1392782835; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=5G4jhX12rPOXUcRIGLWXRrEFmplxR6x+DkQrD3xMxUY=; b=Imu/m1EpcTJTbgc/OcB0WA2/tQn+Ujs/dDBdJ4ayzFCLpAfeb0+x/OGz qtqnOvq0w6IC7zVkPxtQWklC13KyMN64zpR50Z9vLV5K+cGfDBo2wa+Q+ spy5TUwjbDEnY0kRZfGkdJgK4P+zpME5QgdZdr9Ib97LoJBpMTEXTtSH/ E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAIq38VKtJV2a/2dsb2JhbABZgww4V75MgQoWdIIlAQEBAwEBAQE3NAsFCwIBCDYQJwslAgQBDQWHfQgNziwTBI51B4Q4AQOYK5Ihgy2CKg
X-IronPort-AV: E=Sophos;i="4.95,784,1384300800"; d="scan'208";a="301903079"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-5.cisco.com with ESMTP; 05 Feb 2014 04:07:15 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s1547F4N026659 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Feb 2014 04:07:15 GMT
Received: from xmb-rcd-x07.cisco.com ([169.254.7.109]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Tue, 4 Feb 2014 22:07:14 -0600
From: "Prashanth Patil (praspati)" <praspati@cisco.com>
To: Ted Lemon <ted.lemon@nominum.com>, Simon Perreault <simon.perreault@viagenie.ca>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt
Thread-Index: AQHPIifAqrhBbDVm+UGlCKLrE1Sl9Q==
Date: Wed, 05 Feb 2014 04:07:14 +0000
Message-ID: <CF17B34D.17390%praspati@cisco.com>
References: <20140204093611.4914.51694.idtracker@ietfa.amsl.com> <52F0F3C2.20807@viagenie.ca> <4B094E1A-431F-4F2B-9004-37D6D12BE8F8@nominum.com> <52F0F8F4.4060905@viagenie.ca> <EEEC392B-7B7B-4AAE-BE24-AEC944DFABFA@nominum.com>
In-Reply-To: <EEEC392B-7B7B-4AAE-BE24-AEC944DFABFA@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.65.43.160]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9B2723C26A24EF46ADBCD7DE4F27201F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt
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, 05 Feb 2014 04:07:20 -0000

On 2/4/14 8:16 PM, "Ted Lemon" <ted.lemon@nominum.com> wrote:

>On Feb 4, 2014, at 9:28 AM, Simon Perreault <simon.perreault@viagenie.ca>
>wrote:
>> I'm sorry, I don't understand what you're suggesting. How would the
>> link-layer address be of any use? We want to know what kind of IP-layer
>> connectivity a client has, and we don't care about the link layer. What
>> do you mean by "making allocations"? How is the relay "making
>> allocations" in draft conn-status?
>
>You can use the link-layer address in DHCPv6 to correlate to the
>link-layer address in DHCPv4.

Sure. The idea was to be able to detect transitions as well i.e. Dual
stack to IPv6 only, which the server cannot detect unless informed.
Whether this detection is generically useful, needs discussion.

-Prashanth

>   By "make allocations" I mean "do what DHCP does, including assigning
>parameters."   Sorry for the imprecision.
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email