Re: [v6ops] New Version Notification for draft-yourtchenko-ra-dhcpv6-comparison-00.txt (fwd)

Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 04 December 2013 20:50 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E19911AE326 for <v6ops@ietfa.amsl.com>; Wed, 4 Dec 2013 12:50:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 oFunlPjxNrAt for <v6ops@ietfa.amsl.com>; Wed, 4 Dec 2013 12:50:26 -0800 (PST)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) by ietfa.amsl.com (Postfix) with ESMTP id 8C7AF1AE2C4 for <v6ops@ietf.org>; Wed, 4 Dec 2013 12:50:25 -0800 (PST)
Received: by mail-lb0-f178.google.com with SMTP id c11so9601501lbj.37 for <v6ops@ietf.org>; Wed, 04 Dec 2013 12:50:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=JvAlLPXcIwqAc1RbZj/jZ61xD1kjvOszuVrpBcS2nNE=; b=WTL0u26Opg05cTQt+bB9BtD+kn7y4fyRWnmneAZ+OIMCgUGHq19J93WvMN174sbood QN8SbokATJbMurS7y0bF8XU446+oaFs6FqhY9Pc2dzMF8ZIfaK78orlVybqiGFZ/LwUA 87PXcwGAUU51xtrv7rErbUe9TdQC/8mznZOsjCN33BytIygEof+6PZggxRkXvqjthgdr /mgJWuKF0hCVxQJrK+u2p6f7Jnwg5W/pnZrT5GGOwoQW7A3jWE41qB0vo2sUnFNngpOV vORnMiwcMsLrz0Mw6HIOMzDzhDpqXeDP8itZ6Gf3NqUj2ARW+tBR6IPbZcQQRQDMEZGB L83A==
MIME-Version: 1.0
X-Received: by 10.152.234.170 with SMTP id uf10mr401020lac.43.1386190221723; Wed, 04 Dec 2013 12:50:21 -0800 (PST)
Received: by 10.114.217.129 with HTTP; Wed, 4 Dec 2013 12:50:21 -0800 (PST)
In-Reply-To: <alpine.OSX.2.00.1312041021520.35140@ayourtch-mac>
References: <alpine.OSX.2.00.1311271353550.3903@ayourtch-mac> <CAC8QAceTP5omdjS2_43AVKH8Jrb867scmKeb4_sS9YfwqQVTUw@mail.gmail.com> <alpine.OSX.2.00.1312041021520.35140@ayourtch-mac>
Date: Wed, 04 Dec 2013 14:50:21 -0600
Message-ID: <CAC8QAceZtqZ2OGfcmK+eiSanPdLiziuYMFvgied=HbsqdaXaNA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Andrew Yourtchenko <ayourtch@cisco.com>
Content-Type: multipart/alternative; boundary="001a1133ad0ec1ca9404ecbb8fee"
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] New Version Notification for draft-yourtchenko-ra-dhcpv6-comparison-00.txt (fwd)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2013 20:50:29 -0000

Hi Andrew,

Please see inline.

Regards,

Behcet


On Wed, Dec 4, 2013 at 3:45 AM, Andrew Yourtchenko <ayourtch@cisco.com>wrote:

> Hi Behcet,
>
>
> On Tue, 3 Dec 2013, Behcet Sarikaya wrote:
>
>  Hi Andrew,
>>
>> Thanks for writing this draft. It is interesting and useful.
>>
>> I have a few comments:
>>
>> 1. There is another draft, https://datatracker.ietf.org/
>> doc/draft-ietf-v6ops-dhcpv6-slaac-problem
>> what is the relation between these two drafts?
>>
>
> IIRC The draft I wrote came out of the discussion of the above draft (in
> fact I accidentally hijacked the thread there :) - there were the usual two
> strong opinions "this needs to be there" and "this does not need to be
> there", so I decided to try to write up a balanced overall comparison -
> especially that this type of question comes up a lot in many contexts
> outside the IETF.
>
>
>  2. In Section 2.1, you consider Wi-Fi but not 3G/LTE. As you know, on 3G
>> links, the standard requires SLAAC.
>>
>
> Great catch! I added the new section to the "running head" version of the
> doc on the github. Thank you!
>
>
>  3. The document is missing a discussion on another aspect of this issue,
>> i.e. RA options, such as in RFC 4191 and the corresponding DHCP option in
>> http://tools.ietf.org/html/draft-ietf-mif-dhcpv6-route-option-05.
>> Adding this to your draft is recommended.
>>
>
> Could you suggest a one-paragraph wording for such a discussion ? Your
> comment triggered another idea in my head re options, but I would like to
> hear you first so I do not skew what you wanted to say - maybe they are
> different ideas.
>
>
Sure.
Here is my text (two paragraphs instead of one :-)) Please feel free to add
more, I believe other people, e.g. Brian Carpenter can also help.

The issue is delivering routes to the hosts. RFC 4191 defines Router
Advertisement extensions for communicating default router preferences and
more-
   specific routes from routers to hosts. The draft on IPv6 RA Options for
Next Hop Routes, draft-sarikaya-6man-rfc4191bis-00 proposes some new  Router
   Advertisement options for configuring next hop routes on the mobile
   or fixed nodes.

DHCP can also be used for delivering routes, as in
draft-ietf-mif-dhcpv6-route-option-05. DHCPv6 Route Options can be defined
basically to mimic the RA options defined in RFC 4191 as well as with some
extensions such as the next hop address. DHCP approach claims the advantage
of being applicable to configuring the routers, e.g. residential
   gateways (RG) or Customer Premises Equipment (CPE) as well as the hosts.

>
>  4. Lastly, your .txt document prints two pages for each page you have, I
>> think there is some formatting issue.
>>
>
> Indeed. Thanks! Weird, I just used the xml2rfc with the default settings,
> and the boilerplate came from template generator... Maybe I need to update
> it. I've created an issue onto the github repo for it, will take care of it.
>
> --a
>
>
>
>> Regards,
>>
>> Behcet
>>
>>
>> On Wed, Nov 27, 2013 at 7:06 AM, Andrew Yourtchenko <ayourtch@cisco.com>
>> wrote:
>>       Hello all,
>>
>>       Finally I managed to comb a little bit and finally submit the doc
>> that aims to compare RAs with DHCPv6 which emerged from the discussion on
>> this list a few weeks ago.
>>
>>       I'll be very happy to hear any comments, suggestions, flames, etc.
>>
>>       --a
>>
>>
>>       p.s. The "realtime changes" repository is at:
>> https://github.com/ayourtch/ra-dhcpv6, in case you want to send the
>> feedback via a pull request :)
>>
>>       ---------- Forwarded message ----------
>>       Date: Wed, 27 Nov 2013 04:52:14 -0800
>>       From: internet-drafts@ietf.org
>>       To: Andrew Yourtchenko <ayourtch@cisco.com>
>>       Subject: New Version Notification for
>>           draft-yourtchenko-ra-dhcpv6-comparison-00.txt
>>
>>
>>       A new version of I-D, draft-yourtchenko-ra-dhcpv6-comparison-00.txt
>>       has been successfully submitted by Andrew Yourtchenko and posted to
>> the
>>       IETF repository.
>>
>>       Filename:        draft-yourtchenko-ra-dhcpv6-comparison
>>       Revision:        00
>>       Title:           A comparison between the DHCPv6 and RA based host
>> configuration
>>       Creation date:   2013-11-27
>>       Group:           Individual Submission
>>       Number of pages: 12
>>       URL:             http://www.ietf.org/internet-
>> drafts/draft-yourtchenko-ra-dhcpv6-comparison-00.txt
>>       Status:          http://datatracker.ietf.org/
>> doc/draft-yourtchenko-ra-dhcpv6-comparison
>>       Htmlized:        http://tools.ietf.org/html/
>> draft-yourtchenko-ra-dhcpv6-comparison-00
>>
>>
>>       Abstract:
>>          This document attempts to make a balanced comparison between the
>> RA-
>>          based and DHCPv6-based host configuration mechanisms.  It
>> compares
>>          the two on different aspects, e.g: underlying media assumptions,
>>          coordination, locality, etc.  and highlights the strong and weak
>>          sides of both protocols for each scenario.
>>
>>
>>
>>
>>       Please note that it may take a couple of minutes from the time of
>> submission
>>       until the htmlized version and diff are available at tools.ietf.org
>> .
>>
>>       The IETF Secretariat
>>       _______________________________________________
>>       v6ops mailing list
>>       v6ops@ietf.org
>>       https://www.ietf.org/mailman/listinfo/v6ops
>>
>>
>>
>>