[v6ops] RFC6724 policy table for Multi-Homed Site
"Mudric, Dusan (Dusan)" <dmudric@avaya.com> Tue, 12 December 2017 18:54 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 F2253129511 for <v6ops@ietfa.amsl.com>; Tue, 12 Dec 2017 10:54:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.919
X-Spam-Level:
X-Spam-Status: No, score=-6.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] 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 lWhpo2N-Nglc for <v6ops@ietfa.amsl.com>; Tue, 12 Dec 2017 10:54:20 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (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 D8412129504 for <v6ops@ietf.org>; Tue, 12 Dec 2017 10:54:19 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2EwAgCXJDBa/yYyC4ddGgEBAQEBAgEBAQEIAQEBAYJsUmZ0JweDe5kmmQ6CFQoTEIUYAhqEbkAXAQEBAQEBAQEBA2gdC4JrS1kBAQEBAQEjAj5FERFXARUNAgYgAgQwFREBBBsaigYBD54Nim6CJyECij4BCgEBAQEeBYEPgjgcgguBV4UhgTuBZQGBcIMTMYIyBaMXAod5jyiKLIc+jQ6JVoE7IQI2JYEpbxU6giqEVHgBiTcBgRQBAQE
X-IPAS-Result: A2EwAgCXJDBa/yYyC4ddGgEBAQEBAgEBAQEIAQEBAYJsUmZ0JweDe5kmmQ6CFQoTEIUYAhqEbkAXAQEBAQEBAQEBA2gdC4JrS1kBAQEBAQEjAj5FERFXARUNAgYgAgQwFREBBBsaigYBD54Nim6CJyECij4BCgEBAQEeBYEPgjgcgguBV4UhgTuBZQGBcIMTMYIyBaMXAod5jyiKLIc+jQ6JVoE7IQI2JYEpbxU6giqEVHgBiTcBgRQBAQE
X-IronPort-AV: E=Sophos;i="5.45,395,1508817600"; d="scan'208";a="226625863"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by de307622-de-outbound.net.avaya.com with ESMTP; 12 Dec 2017 13:54:17 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC03.global.avaya.com) ([135.11.85.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 12 Dec 2017 13:54:17 -0500
Received: from AZ-US1EXMB03.global.avaya.com ([fe80::a5d3:ad50:5be9:1922]) by AZ-US1EXHC03.global.avaya.com ([::1]) with mapi id 14.03.0352.000; Tue, 12 Dec 2017 13:54:16 -0500
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] RFC6724 policy table for Multi-Homed Site
Thread-Index: AdNzeehU7jpKypsnREKU8Av+2tIjgw==
Date: Tue, 12 Dec 2017 18:54:16 +0000
Message-ID: <9142206A0C5BF24CB22755C8EC422E459B4C10E1@AZ-US1EXMB03.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 10.0.250.9
dlp-reaction: no-action
x-originating-ip: [135.11.85.49]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/CzBuR6go0Yl50BRop3RY6zqiazw>
Subject: [v6ops] RFC6724 policy table for Multi-Homed Site
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: Tue, 12 Dec 2017 18:54:22 -0000
Hi, How is this candidate pair selected based on the policy table in https://tools.ietf.org/html/rfc6724#section-10.5 : " Candidate Source Addresses: 2001:db8:1aaa::a or 2001:db8:70aa::a or fe80::a Destination Address List: 2001:db8:1ccc::c or 2001:db8:6ccc::c New Result: 2001:db8:6ccc::c (src 2001:db8:70aa::a) then 2001:db8: 1ccc::c (src 2001:db8:70aa::a) (longest matching prefix) " This is 35 bit match. Should not the longest prefix match give: 2001:db8:1ccc::c (src 2001:db8:1aaa::a), 37 bit match? If this is not the longest prefix match, what should be in the policy table to give the resulting selection to Site C? Thanks, Dusan
- [v6ops] RFC6724 policy table for Multi-Homed Site Mudric, Dusan (Dusan)