Re: Consensus call on adopting:draft-krishnan-6man-rs-mark-06.txt

Wojciech Dec <wdec.ietf@gmail.com> Wed, 18 August 2010 15:00 UTC

Return-Path: <wdec.ietf@gmail.com>
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 266513A6840 for <ipv6@core3.amsl.com>; Wed, 18 Aug 2010 08:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.785
X-Spam-Level:
X-Spam-Status: No, score=-1.785 tagged_above=-999 required=5 tests=[AWL=0.813, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 rgb7GGBVMKp0 for <ipv6@core3.amsl.com>; Wed, 18 Aug 2010 08:00:50 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id BF2583A68A7 for <ipv6@ietf.org>; Wed, 18 Aug 2010 08:00:49 -0700 (PDT)
Received: by gwb20 with SMTP id 20so267480gwb.31 for <ipv6@ietf.org>; Wed, 18 Aug 2010 08:01:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=gWD4IGoFejo8j2iq2biue3c5FpBSRkIILuDV1a3mJao=; b=DJ8yxWGGyyTPkF+IHLTW8vMwMsF2Wp2qova0SVFzYey/8mgguRwy19fwlzB7kWeoFQ e9EPLtxR5VoG5tmnluPoJrvVF2O6RasfPBQG48wLhEcGflK+LFCGeURByqoXam07a37d ko43ymEX7fFUaCcAnS1j99pUdrZDw1X1+mVf0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=waftJMmc/danHxagVLAH9D3PJnoxxr7ik1a6icuf7zZMP24WyWDV8h2MYWfWr7WF7/ wqYj9jE6KR0TkXYXimi48Jbs27gYrXfKyKNdSG5VryDW6D2k276A+KEbcAvi9Arxy0Ft MWi+3OfvAZ/ZvoZd3FLi4WX7ih0+3qKgI/8Ns=
MIME-Version: 1.0
Received: by 10.229.246.194 with SMTP id lz2mr6072819qcb.216.1282143684779; Wed, 18 Aug 2010 08:01:24 -0700 (PDT)
Received: by 10.229.100.77 with HTTP; Wed, 18 Aug 2010 08:01:24 -0700 (PDT)
In-Reply-To: <1B6D0317D3AD964FBF3956DEFA3524D505C580FDBE@EUSAACMS0701.eamcs.ericsson.se>
References: <4C61959A.7040805@innovationslab.net> <AANLkTimmO3ah4sSJuisvgO5=yzVJmndqzD-i-=yVyek1@mail.gmail.com> <4C6BE824.9060201@ericsson.com> <AANLkTim+mVEbDX9F+BgxOv8y3pfrWU-NOn1g=64=nWag@mail.gmail.com> <1B6D0317D3AD964FBF3956DEFA3524D505C580FDBE@EUSAACMS0701.eamcs.ericsson.se>
Date: Wed, 18 Aug 2010 17:01:24 +0200
Message-ID: <AANLkTi=+63HHr7K0VkkQzg8+VbGsbpP4XsP8p_hwuZ6N@mail.gmail.com>
Subject: Re: Consensus call on adopting:draft-krishnan-6man-rs-mark-06.txt
From: Wojciech Dec <wdec.ietf@gmail.com>
To: Alan Kavanagh <alan.kavanagh@ericsson.com>
Content-Type: multipart/alternative; boundary="0016e64f9200e1dddf048e1a56a3"
Cc: Brian Haberman <brian@innovationslab.net>, IPv6 WG Mailing List <ipv6@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>
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: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Wed, 18 Aug 2010 15:00:51 -0000

Hi Alan,

that wasn't quite the question I asked. DHCPv6 has a well defined mechanism
to periodically retry, while RS client sending simply timeout. This would
seemingly leave such clients in the proposed scheme with no connectivity.

-Woj.

On 18 August 2010 16:51, Alan Kavanagh <alan.kavanagh@ericsson.com> wrote:

>  Hi Woj
>
> Its the same issue for DHCPv6, if the client dont send a DHCP_Solicit you
> dont get an address. Also, the RS similar to the DHCP_Solicit is used to
> "kick_start" the IP Sub session and as you know there are lots of hosts whom
> dont have a DHCPv6 client and will not have a DHCPv6 client.
>
> The RS LIO is used to cater for hosts who do not have a DHCPv6 Client. Also
> the LIO is used to identify the subscriber line and tie rules etc to this
> sub line.
>
> Alan
>
>  ------------------------------
> *From:* ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] *On Behalf Of
> *Wojciech Dec
> *Sent:* August-18-10 10:46 AM
> *To:* Suresh Krishnan
> *Cc:* Brian Haberman; IPv6 WG Mailing List
> *Subject:* Re: Consensus call on
> adopting:draft-krishnan-6man-rs-mark-06.txt
>
> Hi Suresh,
>
> thanks for your reply. Continued inline...
>
> On 18 August 2010 16:03, Suresh Krishnan <suresh.krishnan@ericsson.com>wrote:
>
>> Hi Woj,
>>  Thanks for your comments.
>>
>>
>> On 10-08-18 07:11 AM, Wojciech Dec wrote:
>>
>>> Hi,
>>>
>>> I have a question or two to the draft authors who can hopefully clarify
>>> the expected context and working of this scheme, which at the moment is a
>>> bit unclear.
>>> In essence the problem this draft appears to be trying to solve is using
>>> RS/RA messages to induce state into intermediate or IP edge devices like
>>> what is done for DHCP, with the LIO being used to induce such state. All
>>> this is presumably meant to take place following an RS message sent by a
>>> client. Thus, my questions are:
>>> How does this solution cope in a case where the client does not send an
>>> RS? (or the RS sending has timed out)?
>>>
>>
>> The first sign of life from the client is either an RS or a DHCPv6
>> message. If the network does not see either of the messages, there will be
>> no address allocated/prefix advertised to the client. The client will not
>> have any connectivity.
>>
>
> Hmm, but if the first sign of life is a DHCPv6 message from a client , then
> why would the RS LIO be needed ?
>
> Now, in the case of a non DHCPv6 client, given that such clients are do
> time out from sending RS messages, how does the solution cater to that? Just
> leaving clients with no connectivity seems like a highly undesirable
> proposition/outcome...
>
> -Woj.
>
>>
>> Thanks
>> Suresh
>>
>>
>