IETF Logo Mail Archive

Re: ULA scope [draft-ietf-6man-rfc3484-revise-05.txt]

Arifumi Matsumoto <a@arifumi.net> Sat, 17 March 2012 00:29 UTC

Return-Path: <a@arifumi.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1EE421F856A for <ipv6@ietfa.amsl.com>; Fri, 16 Mar 2012 17:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZkpQlApXKG0J for <ipv6@ietfa.amsl.com>; Fri, 16 Mar 2012 17:29:39 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id E263D21F8569 for <ipv6@ietf.org>; Fri, 16 Mar 2012 17:29:38 -0700 (PDT)
Received: by lagj5 with SMTP id j5so4346139lag.31 for <ipv6@ietf.org>; Fri, 16 Mar 2012 17:29:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=90yFSoWLE3epGNiLl6R8Wp95hZpMr9ksIkULpV+ORVw=; b=EQ/DZePzHNgLDNerNq/XChvAyuwoqTCCV1i1v2FOWMHFOO71vqiLg+gHJps4SC54pp Hw4EBVu9evuE9BIpRV+xotk7cGdrcT8UPG4RNyt1Wm2gfJLMIF7qB1HYzq6HfngOdTYO oayQ8/z7dbDCta90y3paJHyZ1aWjKPiHI7aaK5VK0qFDXAo7svwp3R2c3DVGOSKB4HCX nchvwEu/8CFIA8R+SoGleLIpVllNaFIuogpWN9T8FOgcI4+sgfBG0FzOEtlsRL4eoxhv lOAXTMCkQrHB3N/XRsd1e/5i1oXBi+Dc/wrtnmrOqflArZhz2MWPoX5oWXEstCSG9/vk Ip8A==
MIME-Version: 1.0
Received: by 10.152.131.3 with SMTP id oi3mr3682548lab.35.1331944177864; Fri, 16 Mar 2012 17:29:37 -0700 (PDT)
Received: by 10.112.109.68 with HTTP; Fri, 16 Mar 2012 17:29:37 -0700 (PDT)
X-Originating-IP: [118.21.146.144]
In-Reply-To: <4F63896E.10607@gmail.com>
References: <4EB3F3D6.4090302@innovationslab.net> <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com> <4EEA3D20.7020603@innovationslab.net> <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com> <4EEA5793.8080800@gmail.com> <CAKFn1SHA-=cQ_=5rJVLVMvQYXoTL_D1dCR=uWZK-qFrcGp6P-w@mail.gmail.com> <4EEA7AF8.2090508@gmail.com> <CAC1-dtn9M8-9cPAmkhCiGV0Gi5+Gfs8GAssTOaA-ZFhyUY3feg@mail.gmail.com> <9B57C850BB53634CACEC56EF4853FF653B3C3777@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653B3EDB9E@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <E6E7EE34-8244-40B6-84C1-C79E8BDE7921@nttv6.net> <4F3ABFBA.8060605@gmail.com> <29EBA88D-BDB1-464C-915F-B9063578DC51@nttv6.net> <9B57C850BB53634CACEC56EF4853FF653B45BB08@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <C8827D58-5C69-4A44-B9CE-86791466814E@nttv6.net> <4F63896E.10607@gmail.com>
Date: Sat, 17 Mar 2012 09:29:37 +0900
Message-ID: <CAFtBC=8=__8GdtExB8oYgA7pOfjxNfXCLzuOXz7_UKCPhwjenw@mail.gmail.com>
Subject: Re: ULA scope [draft-ietf-6man-rfc3484-revise-05.txt]
From: Arifumi Matsumoto <a@arifumi.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQl0TMUjm+aWEuhgEc94kmLojyj27Y1mzU6+JFgEVzsuShbz5a5uNqkjvnHabbJblJEL9fCn
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>, Dave Thaler <dthaler@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 17 Mar 2012 00:29:39 -0000

Brian,

2012/3/17 Brian E Carpenter <brian.e.carpenter@gmail.com>:
> On 2012-03-16 23:30, Arifumi Matsumoto wrote:
> ...
>> Rather, my question was about the design choice.
>>
>> Regarding the design of ULA and how to use the ULA, can we agree that
>> ULA-to-ULA communication within the same /48 prefix is not always preferred
>> over other communications using IPv4 or IPv6 global addresses ?
>
> I would expect it to be preferred as a result of longest match; I would
> not expect it to be a special case in the default policy for global
> scope addresses, if that is the question.

ULA-to-ULA will not be preferred, because ULAs are assigned lower
precedence value in the policy table than those of IPv4 and IPv6
global addresses.

Best,

>>>> Second,
>>>> when a user configures his policy table, the configured table is overwritten by
>>>> this implementation dependent policy injection behavior ?
>>>> Can the user suppress this behavior of policy injection ?
>>>> This issue should arise also when a policy distributing mechanism is ready.
>>> Good questions.  Do you have suggested answers to those questions?
>>> I might throw out a strawman of:
>>>
>>> Any automatic rows added by the implementation as a result of address
>>> acquisition MUST NOT override a row for the same prefix configured
>>> via other means.   That is, rows can be added but never updated
>>> automatically.   An implementation SHOULD provide a means for
>>> an administrator to disable automatic row additions.
>>
>>
>> My suggested answer for this was to use macros, which can be
>> added/deleted by a user, and interpreted as the actual prefix
>> attached to the hosts.
>
> That's an implementation method. I think Dave's proposed rule is
> correct.
>
>    Brian
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email