mic comments on presentation of draft-pfister-6man-sadr-ra-00

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 23 March 2015 16:43 UTC

Return-Path: <alexandru.petrescu@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 711191ACD6C for <ipv6@ietfa.amsl.com>; Mon, 23 Mar 2015 09:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 OK4KmZbV_1oc for <ipv6@ietfa.amsl.com>; Mon, 23 Mar 2015 09:43:00 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01B561ACD5F for <ipv6@ietf.org>; Mon, 23 Mar 2015 09:42:59 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t2NGgwHn028708 for <ipv6@ietf.org>; Mon, 23 Mar 2015 17:42:58 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A0081202C38 for <ipv6@ietf.org>; Mon, 23 Mar 2015 17:43:38 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 8CAEF20282A for <ipv6@ietf.org>; Mon, 23 Mar 2015 17:43:38 +0100 (CET)
Received: from [127.0.0.1] ([132.166.84.81]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t2NGgtRY001821 for <ipv6@ietf.org>; Mon, 23 Mar 2015 17:42:57 +0100
Message-ID: <5510428F.8050408@gmail.com>
Date: Mon, 23 Mar 2015 17:42:55 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ipv <ipv6@ietf.org>
Subject: mic comments on presentation of draft-pfister-6man-sadr-ra-00
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1riPS8ar_5t8aEKsdNHBXI2oIxM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Mon, 23 Mar 2015 16:43:05 -0000

Hello,

Please allow me to reiterate the mic comments I had during the
presentation of draft-pfister-6man-sadr-ra-00.

Encoding source prefix in an RA, along with RIO, is making sense.

But when it comes to specifying the Host (and Router, for that matter)
behaviour do source-based routing, things are less clear.

I think we do not have a specification of dst-based routing in first
place, and as such adding src-based routing could only be less clear.

What's the place of a default route in the dst-based longest match
followed by the src-based longest match?  If src-based longest prefix
match search finds nothing, will it hit a 'src-based' default route?  Or
hit the existing dst-based default route?  If the former, would it take
precedence over the dst-based def route?

How will it behave when the unspecified address is used as src?

Will it be CIDR/SADR?  Or search only the first 64 bits?

An earlier commenter asked about the Default Router Preference, and
Lifetimes in the RA - will this apply to src-based routing as well?
Will we have a src-based default router address in an RA?

Alex