IETF Logo Mail Archive

Re: New Version Notification for draft-sarikaya-6man-sadr-overview-06.txt

Behcet Sarikaya <sarikaya2012@gmail.com> Fri, 10 April 2015 16:37 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8D801ACDD9 for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 09:37:03 -0700 (PDT)
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 o8wzzONGIQ49 for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 09:37:01 -0700 (PDT)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D19801ACEE3 for <6man@ietf.org>; Fri, 10 Apr 2015 09:37:00 -0700 (PDT)
Received: by lbbqq2 with SMTP id qq2so17697281lbb.3 for <6man@ietf.org>; Fri, 10 Apr 2015 09:36:59 -0700 (PDT)
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=ICu6ksUAue12EPpRRk/PEcjI4kH7FCBm96AcJrO1jgw=; b=iz5tKCgsOr5JJgSpl4aIjD2gqikqCY6NkDFF8bQOWutOMuT1++TK9wwkTQ8B+543QO ItITouFBE2XWzNx9xS3dCJHJZDkNeH2YftYHDkMn0RUxzIcmSTC2KaHpANmHn+NqSx2K fu0KvslGPXY4DaTPqLESl2F3suMkP/2gkL2st20NtO/fXvwJ2LJmKNVtoNqbUyjdQUP9 EcR4TkOpm3iCOi55nip0AIJ04W5QHqfWOHoCoKMwFJo2ytjUu+XTkXYORYu8SSMMr+YD rwhs0TaoqbHVx3eWk3C1g1ogBLxZad4EBuPbCsEXFjm3Nyd4yRaIDYxpmPggJcTPOcFn er+w==
MIME-Version: 1.0
X-Received: by 10.152.121.72 with SMTP id li8mr2100230lab.11.1428683819352; Fri, 10 Apr 2015 09:36:59 -0700 (PDT)
Received: by 10.114.74.225 with HTTP; Fri, 10 Apr 2015 09:36:59 -0700 (PDT)
In-Reply-To: <5527A84B.8090201@globis.net>
References: <CAC8QAceCoBx8VCgLq5tJ8JUGtVCPP+PXC0gxmhpRpmrp0MXqPw@mail.gmail.com> <55240885.9060200@globis.net> <CAC8QAcddWTb-w_3Q29sq0GpUOcqyOPjDRd1a0Uk3zY0ivzohNg@mail.gmail.com> <5526E648.4020004@gmail.com> <F48F50DA-4257-48E7-B34D-A0543EA3E50D@cisco.com> <5527A84B.8090201@globis.net>
Date: Fri, 10 Apr 2015 11:36:59 -0500
Message-ID: <CAC8QAceRxLOhkZDMrXEu0MJURWm-Jc07J9nAcrPXzNOALHzzeA@mail.gmail.com>
Subject: Re: New Version Notification for draft-sarikaya-6man-sadr-overview-06.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Ray Hunter <v6ops@globis.net>
Content-Type: multipart/related; boundary="089e01176b3b8ca3250513615f46"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6eW6juQtntxCpOYHMspHK1OxynY>
Cc: Ole Troan <ot@cisco.com>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 10 Apr 2015 16:37:04 -0000

Hi Ray, all,

On Fri, Apr 10, 2015 at 5:39 AM, Ray Hunter <v6ops@globis.net> wrote:

>
>
>   Ole Troan <ot@cisco.com>
>  10 April 2015 08:15
>
> fully agree. SADR might not be the best name for the host portion.
> perhaps something like "IPv6 Multi-homed host gaps”?
>
> Isn't this limiting the host gaps, possibly the future ones to source
address selection?
Otherwise I am OK.


> Ole
>   Brian E Carpenter <brian.e.carpenter@gmail.com>
>  9 April 2015 22:51
>
> On 08/04/2015 05:02, Behcet Sarikaya wrote:
>
> Hi Ray,
>
> On Tue, Apr 7, 2015 at 11:40 AM, Ray Hunter <v6ops@globis.net> <v6ops@globis.net> wrote:
>
> ...
>
> But I'd expect any "SADR overview" to also cover router - router forwarding
> behaviour. Not just end host - router.
>
> Can you offer some text?
>
>
> At the moment that's covered by draft-baker-rtgwg-src-dst-routing-use-cases.
> IMHO the separation into host and router drafts is reasonable, so that
> each draft fits mainly into a single WG.
>
>
I agree.

snipped some text here.

> This should be
> draft-sarikaya-6man-sadr-ra
>
>  we do not plan on pursuing draft-sarikaya-6man-next-hop-ra-04 any
> further because of the third part next hop issue.
>
>  or
>
> https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00 ?
>
> In my mind, https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00  is a
> logical progression from https://tools.ietf.org/html/rfc4191
>
> The other approach is to define a new option as in
> draft-sarikaya-6man-sadr-ra then we don't need an I flag.
>
> Snipped some text.

> Currently we (Pfister and I) are discussing how to merge these two
> solution documents. So I believe there will be one solution document
> in the end.
>
>
We need more feedback on the above choices for solution approaches.


>
>  Both of your comments make sense to me: host portion covered in this WG
> and changing the title.
>
> What about other considerations then?
>
> Such as potentially extending ICMP redirects to include source address
> specific applicability?
>
> I know this has been discussed, but it isn't included in any problem
> statement yet AFAICS.
>
> regards
> RayH
>
Regards,

Behcet

v2.23.0 | Report a Bug | By Email