Re: [Casm] New Version Notification for draft-kumar-requirements-and-framework-00.txt

Brian E Carpenter <> Wed, 08 February 2017 19:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 57825129FD3 for <>; Wed, 8 Feb 2017 11:37:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SZ2OSOwegKb1 for <>; Wed, 8 Feb 2017 11:37:32 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 24C9E129FD1 for <>; Wed, 8 Feb 2017 11:37:32 -0800 (PST)
Received: by with SMTP id 203so108177254ith.0 for <>; Wed, 08 Feb 2017 11:37:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=lqzaDFR3riCjVTnGkM6vVSgXxFPyFDHrVost69X9M4s=; b=qtETQ8Swn5IYiLCxfyHKxVeMK57DDP8DiLKuUPOXQYyu9zv1Daznu2yNO4IBSoMsJS R18xXZPdohnOM2eHnGlhwrG4MXXvKWqhLTvR8uThWAllx46Q3oNY1TkCrWfE/DTfuZ5X NU19tCpNXx4waPfAElWXGpd3ULfb2AKc84k3uckJXfj8WlBIMYvgItc8EGYbJBmRvoHl LTfLDKH/Rz32dnBns3EBMr/jWXgh9e0uqvIPF+U7HumoZhfrpAMlBmd1tD3I0Url+COj g1xVAXEZlnXIpgikrg+MotivRlyHkumvuMB4ycbCtzXhxoaeuLcaPDLAw03I9YGcwg/j +vgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=lqzaDFR3riCjVTnGkM6vVSgXxFPyFDHrVost69X9M4s=; b=XFcQyTNYTFEe++Pe5vSby6PMHqBlbNG/Pm8h3wS5ah2UEKCRePq/ZP8UFW+Jc7FOpf sD/eo5/pPGzoIz1gHN89h9cX6h5F6twfN4X1Y2Wci7yBXYCxHIPQ8xKrOOzs5/sM1BRt ADBHiY9IZ4uWCYF44D8iAfTiRxwKLl4Qs/Bw/6dzmNcuO/ifRlf/S3YEqVCET2obnLsB CAvLMc7lv5BnGad8QkJ24GgT6MMbE+4AVAy2XbD0tuNY6JQS5vez359JFxtvZXHkLmh2 WBFf22AcEMLLW0HROosZveG/tcril/ufgzGPcDaK900JsefMr2SY8TJ1bRBP6QPCcx8y p4zg==
X-Gm-Message-State: AIkVDXItRZEAtstDYI7Vs0e0Ewa6Wvj9B+U8YsHlbpAk7Awjgs2q62IhM/SxNYmybYu4xw==
X-Received: by with SMTP id m3mr35316902pld.89.1486582651208; Wed, 08 Feb 2017 11:37:31 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id y201sm22480078pfb.16.2017. for <> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Feb 2017 11:37:30 -0800 (PST)
References: <> <>
From: Brian E Carpenter <>
Organization: University of Auckland
Message-ID: <>
Date: Thu, 9 Feb 2017 08:37:32 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [Casm] New Version Notification for draft-kumar-requirements-and-framework-00.txt
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Centralized Address Space Management <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 08 Feb 2017 19:37:33 -0000

On 09/02/2017 02:51, Xie Chongfeng wrote:
> One of the basic requirments of centralized address management is that the mechanism shouled be aligned with the routing system, for instance, when one address block is allocated to an network equiment, the routing entry correspondent to this address block will be broadcasted accordingly, otherwise, the network will not work correctly.  Similarly,when one address block is withdrawl from an given network equipment, the routing entry will be withdrawl as well.  
> Chongfeng Xie  

That is correct, but it doesn't need to be centralised. The route(s) to a
prefix are announced by the router(s) that handle that prefix, in every routing
protocol that I know. So that is intrinsically distributed. If prefix assignment
decisions are centralized or distributed, that doesn't change anything for
the router. Somebody gives it a prefix, that's all it cares about.

You can look at Homenet (RFC7788 and RFC7695) for a fully distributed model
of assignment. That probably doesn't meet the CASM requirements because it's
designed for operator-free networks. The Anima work is directed at enterprise
networks with a NOC.