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

"Mudric, Dusan (Dusan)" <dmudric@avaya.com> Thu, 22 March 2018 14:55 UTC

Return-Path: <dmudric@avaya.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 0C60612D872 for <v6ops@ietfa.amsl.com>; Thu, 22 Mar 2018 07:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=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 fNSBKzl2O3nh for <v6ops@ietfa.amsl.com>; Thu, 22 Mar 2018 07:55:44 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA70D12D86E for <v6ops@ietf.org>; Thu, 22 Mar 2018 07:55:44 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2GcAAC7w7Na/yYyC4ddGQEBAQEBAQEBAQEBAQcBAQEBAYJrUmFwKAqDUod/jQ2Bc4ERkmGBST0LIwmEWQIag0khNBgBAgEBAQEBAQIDaBwMgmsvBgcDDCEJAgMBAQEBAQEmAQEBAQEBAQEBAQEBARwCDy8SAQEYAQEBAQMSEQQNOgsMBAIBBgINAQMEAQEBAgIGHQMCAgIwFAEICAIEAQ0FCBqEbAEOjx6RTYlrgWs1GwKII4IJBYEIhCeCEYFVP4QSgxMBAQEBARiBHQYBASCCfzCCJAOXfggChVyKTIZPhHuHNIFqhm6BJRw5gVJwFTqCQ4V/hROFPW8BjgsOGIEIAYEVAQE
X-IPAS-Result: A2GcAAC7w7Na/yYyC4ddGQEBAQEBAQEBAQEBAQcBAQEBAYJrUmFwKAqDUod/jQ2Bc4ERkmGBST0LIwmEWQIag0khNBgBAgEBAQEBAQIDaBwMgmsvBgcDDCEJAgMBAQEBAQEmAQEBAQEBAQEBAQEBARwCDy8SAQEYAQEBAQMSEQQNOgsMBAIBBgINAQMEAQEBAgIGHQMCAgIwFAEICAIEAQ0FCBqEbAEOjx6RTYlrgWs1GwKII4IJBYEIhCeCEYFVP4QSgxMBAQEBARiBHQYBASCCfzCCJAOXfggChVyKTIZPhHuHNIFqhm6BJRw5gVJwFTqCQ4V/hROFPW8BjgsOGIEIAYEVAQE
X-IronPort-AV: E=Sophos;i="5.48,345,1517893200"; d="scan'208";a="280659523"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 22 Mar 2018 10:55:36 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC01.global.avaya.com) ([135.11.85.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Mar 2018 10:55:36 -0400
Received: from AZ-US1EXMB03.global.avaya.com ([fe80::a5d3:ad50:5be9:1922]) by AZ-US1EXHC01.global.avaya.com ([135.11.85.12]) with mapi id 14.03.0352.000; Thu, 22 Mar 2018 10:55:36 -0400
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: Jen Linkova <furry13@gmail.com>, 神明達哉 <jinmei@wide.ad.jp>
CC: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-conditional-ras-01.txt
Thread-Index: AQHTvfmTCDwHYFt5g0SYi8yGx9x3RaPbA57AgAAVi6GAAEhOAIAA+byw
Date: Thu, 22 Mar 2018 14:55:35 +0000
Message-ID: <9142206A0C5BF24CB22755C8EC422E459B57E18B@AZ-US1EXMB03.global.avaya.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> <CAFU7BATXrJiLNh-gWatFtiOqmpEuEd8Qyn04fE9PCFHd8tRe-A@mail.gmail.com>
In-Reply-To: <CAFU7BATXrJiLNh-gWatFtiOqmpEuEd8Qyn04fE9PCFHd8tRe-A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.0.150.1
dlp-reaction: no-action
x-originating-ip: [135.11.85.50]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/waFQARtdyeLGEWoOZJLzojza5PI>
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: Thu, 22 Mar 2018 14:55:47 -0000


> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Jen Linkova
> Sent: Wednesday, March 21, 2018 3:46 PM
> To: 神明達哉
> Cc: v6ops@ietf.org
> Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-conditional-ras-01.txt
> 
> 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://urldefense.proofpoint.com/v2/url?u=https-
> 3A__svnweb.freebsd.org_base_head_sys_netinet6_nd6-5Frtr.c-3Frevision-
> 3D156871-26view-
> 3Dmarkup&d=DwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3i
> CrhIoUWB8YLZU23029sMQGQ2kY&m=Bt5Tr3OFzuMg-KD6-
> VnJOYJxuE_o98MuBUuvWheKQYU&s=fKZV7uOZ6tmyWip4Gvh2oTIbeFM-
> 48LejDFEElgSf7o&e=).
> > 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?
> 

[[Dusan]] 
[[Dusan]] https://tools.ietf.org/html/draft-ietf-6man-rfc6434-bis-07 makes Rule 5.5 SHOULD requirement:
"[RFC8028]
   updates rule 5.5 from [RFC6724]; implementations SHOULD implement
   this rule."

That does not mean there are not end points that don't benefit from Rule 5.5. If both Prf and Rule 5.5 are implemented, the endpoints will benefit from Prf preference sent from the router.

Btw, is there any update on this discussion about Linux Rule 5.5: https://www.ietf.org/mail-archive/web/v6ops/current/msg24934.html 

> 
> --
> SY, Jen Linkova aka Furry
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_v6ops&d=DwIGaQ&c=BFpWQw8bsuKpl1
> SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=Bt5Tr3
> OFzuMg-KD6-
> VnJOYJxuE_o98MuBUuvWheKQYU&s=fACl19Teeq2xU8evNXsgijmoqbwYJmLXsj
> 85X9EuxGM&e=