Re: [v6ops] I-D Action: draft-ietf-v6ops-conditional-ras-01.txt

Jen Linkova <furry13@gmail.com> Wed, 21 March 2018 19:46 UTC

Return-Path: <furry13@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB5E127333 for <v6ops@ietfa.amsl.com>; Wed, 21 Mar 2018 12:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 PqXgy1qx5Gxk for <v6ops@ietfa.amsl.com>; Wed, 21 Mar 2018 12:46:00 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 ABF8F126C25 for <v6ops@ietf.org>; Wed, 21 Mar 2018 12:45:59 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id m16-v6so5907820lfc.4 for <v6ops@ietf.org>; Wed, 21 Mar 2018 12:45:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Ip4mZdDtSrIW2epVwNwY+k3GuEffc1Dl/1Oanl4dnWk=; b=DQgBZAK4Uvs+jkC64lgkZoQ+8tLELZKuhkTEVuva2XjdzXu2mWX1dxLW0xGqS9ddyT UHOfaRy+fFrwutXq+M0+v+dSmC4H+ohlQbwFhMHTRAIDCCDTqmJkl0pLpNfj3g6CNXmR 6JRHadPghqprX7gy5FmVkaaS9uOOCZrPqEzQQE5tVy8lrFVaB8nLz9xs8F33PbosKWTM zLnU/ogNfuFkZYHlCHFUgwwE4U/ca43t7xOBqR2MTQD+0eeRapr9Zyddytuf2oc8sd3I 4m3WbPLkEMxy2n7OnJrgkpPc4vP/vVaeOmQG95nns4DJkhdDvCew8Nr32X1vDfB0p2xV WDlQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Ip4mZdDtSrIW2epVwNwY+k3GuEffc1Dl/1Oanl4dnWk=; b=bwZHx3bRcwDNJ3cIQXvth9dO6HhNA3oGZDpje/hmaXklGnYjvPaROoxxiJvsZU0o91 aaqPeRYvw6ldCyViZmPqnLNEj3Ya2XIMQ0GaLWKyEYu51y1UcOCNOPrMKvBNOm+tDlXZ DvIm/dfYQvSAnDIwjbf7OR4I5dEoxwaXzzXicdrojL2qYcApsxJUZCILp+O43MWy8Sh8 888uJeeYD51F7ud0WTYdqwbNTV+5/zPtvGVVr0eXYIBs+wWdAPNqwSkiOVjSx+iCH307 fdTF86bYpBk1KznHq3hNIxu9XVeCSyRnokD5/ZnEK9X1uKRU40dBF7hDyxZorsTdLnDx IuyA==
X-Gm-Message-State: AElRT7GEjXbBfH8fnrazftTD/HrlwyrjAAB1gui9xpltdJ3BdxlcyiLc QBT1GAkNO4r/J8WTYI6ykhwPwfCfmPNVh9V5fU8mZQ==
X-Google-Smtp-Source: AG47ELtvrDiYSLMMB4gQPMLdwc/2Jyr9N+Hx3Dq2ot2P00ymrB9kYBJ0zby0z5iR9W0Es9XesIpinAQlnjzIy4//nQI=
X-Received: by 10.46.45.18 with SMTP id t18mr2330596ljt.48.1521661557854; Wed, 21 Mar 2018 12:45:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:d10a:0:0:0:0:0 with HTTP; Wed, 21 Mar 2018 12:45:36 -0700 (PDT)
In-Reply-To: <CAJE_bqe-VshYhWY1n=M39P0koQ-tOSdZVU10uNN+Q2wD5FTJAQ@mail.gmail.com>
References: <151976142032.28517.14035738749286138638@ietfa.amsl.com> <CAFU7BAR=ax86N6YMhQeN9fQTgnYO7mzyJNwK2x1OzwpXWwACYQ@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E459B55D41A@AZ-US1EXMB03.global.avaya.com> <20180302185656.GT56288@Space.Net> <9142206A0C5BF24CB22755C8EC422E459B55EA0A@AZ-US1EXMB03.global.avaya.com> <CAFU7BAR+Uyk1PrWN=UCBhuUic-+GO7fAYvSknpLKjr5YixX2iQ@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E459B560FB5@AZ-US1EXMB03.global.avaya.com> <CAFU7BARdE+pzsQVpoWMvDSF7SQpbfR_yP9Ri9xk6togRSmMRgA@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E459B562054@AZ-US1EXMB03.global.avaya.com> <CAFU7BAQ8VsK05MiOt3gjjApoU17tqQZZB2YqJmegcypfiVhbXA@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E459B57DDBB@AZ-US1EXMB03.global.avaya.com> <CAKD1Yr0vOAfYSj2+Up94xvDzCaRkR38v96EEdL-BkF3-Loro4g@mail.gmail.com> <CAJE_bqe-VshYhWY1n=M39P0koQ-tOSdZVU10uNN+Q2wD5FTJAQ@mail.gmail.com>
From: Jen Linkova <furry13@gmail.com>
Date: Thu, 22 Mar 2018 06:45:36 +1100
Message-ID: <CAFU7BATXrJiLNh-gWatFtiOqmpEuEd8Qyn04fE9PCFHd8tRe-A@mail.gmail.com>
To: 神明達哉 <jinmei@wide.ad.jp>
Cc: Lorenzo Colitti <lorenzo@google.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/VmwlC63owlz-tiS2ER3-UwYp1rw>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-conditional-ras-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Mar 2018 19:46:02 -0000

On Thu, Mar 22, 2018 at 6:26 AM, 神明達哉 <jinmei@wide.ad.jp> wrote:
>> > [[Dusan]] This is an implementation aspect. If hosts implement the Prf
>> > from rfc4191#section-2.2, they will recognize Rrf. You should not limit the
>> > options based on the current implementations.
>>
>> Actually, we should. This is an operational working group, and as such,
>> needs to document practices that work today.
>
> I've not closely followed this thread so this may be out of context
> (if so, sorry), but if it's about host implementation of the "Prf"
> value of RFC4191, BSD variants have been supporting it for more than
> 10 years (for example, FreeBSD added it in 2006
> https://svnweb.freebsd.org/base/head/sys/netinet6/nd6_rtr.c?revision=156871&view=markup).
> So I suspect it's also in iOS.  Unlike other features of
> the RFC like route information option, implementing Prf is pretty
> simple, so I wouldn't be surprised if it's also available in non
> BSD-flavor host implementations.

Yeah, you are right, it's reasonably well supported. The issue here is
that just using router preference would not help at all (or may even
make the routing more sub-optimal). Let's say a host honors the router
preference and selects a router  R1 (connected to an ISP1) as a
default gateway but it does not support Rule 5.5, then it may select
ISP2 source prefix and the packet will be send to ISP2 ( R1 -> R2 ->
ISP2). So I'm not sure I can see any value in using the router
preference w/o rule 5.5 support in this scenario..Am I missing
anything?


-- 
SY, Jen Linkova aka Furry