
From nobody Fri May  5 19:04:47 2017
Return-Path: <xiechf.bri@chinatelecom.cn>
X-Original-To: casm@ietfa.amsl.com
Delivered-To: casm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7087127A90 for <casm@ietfa.amsl.com>; Fri,  5 May 2017 19:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.539
X-Spam-Level: **
X-Spam-Status: No, score=2.539 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.741, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 3Yn0O-QRw01D for <casm@ietfa.amsl.com>; Fri,  5 May 2017 19:04:42 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.219]) by ietfa.amsl.com (Postfix) with ESMTP id 2200C127180 for <casm@ietf.org>; Fri,  5 May 2017 19:04:40 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.188:22489.329869622
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-123.119.44.40 (unknown [172.18.0.188]) by chinatelecom.cn (HERMES) with ESMTP id 06A9928009A; Sat,  6 May 2017 10:04:36 +0800 (CST)
Received: from ip<123.119.44.40> ([172.18.0.188]) by App0023 with ESMTP id fb614733-ed64-44eb-8446-789a0708c58e for casm@ietf.org; Sat May  6 10:04:39 2017
0/X-Total-Score: 0:
X-Real-From: xiechf.bri@chinatelecom.cn
X-Receive-IP: 172.18.0.188
X-MEDUSA-Status: 0
Date: Sat, 6 May 2017 10:04:44 +0800
From: "Xie Chongfeng" <xiechf.bri@chinatelecom.cn>
To: "CASM@ietf.org" <CASM@ietf.org>
Cc: "Xuweiping (A)" <xuweiping@huawei.com>,  "lichen.bri@chinatelecom.cn" <lichen.bri@chinatelecom.cn>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 166[cn]
Mime-Version: 1.0
Message-ID: <201705061004422586259@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart868116046254_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/8cOqauu4HYIqn_n8JntMkCNGZec>
Subject: [Casm] New Version Notification for draft-li-casm-address-pool-management-architecture-00.txt
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Coordinated Address Space Management <casm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/casm>, <mailto:casm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/casm/>
List-Post: <mailto:casm@ietf.org>
List-Help: <mailto:casm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/casm>, <mailto:casm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 May 2017 02:04:46 -0000

This is a multi-part message in MIME format.

------=_001_NextPart868116046254_=----
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: base64

DQpIaSxhbGwsDQoNCiAgIEEgbmV3IHZlcnNpb24gb2YgYXJjaGl0ZWN0dXJlIGRyYWZ0IGhhcyBi
ZWVuIGNyZWF0ZWQgYmFzZWQgb24gdGhlIG9sZCBvbmVzIHN1Ym1pdHRlZCBieSBDaGluYSBUZWxl
Y29tIGFuZCBKdW5pcGVyIHNlcGVyYXRlbHkuIA0KDQogIGh0dHBzOi8vd3d3LmlldGYub3JnL2lu
dGVybmV0LWRyYWZ0cy9kcmFmdC1saS1jYXNtLWFkZHJlc3MtcG9vbC1tYW5hZ2VtZW50LWFyY2hp
dGVjdHVyZS0wMC50eHQNCiAgDQogICBJbiBhZGR0aW9uLCBzZXZlcmFsIGNoYW5nZXMgaGFzIGJl
ZW0gbWFkZSBhcyBmb2xsb3dzLA0KICAgMSkgIFRoZSBuZXcgZHJhZnQgaGlnaHRsaWdodHMgdGhl
IG5vcnRoIGFuZCBzb3V0aCBib3VuZCBpbnRlcmZhY2VzIGFuZCBpdHMgcGFyYWdyYXBocyBhcmUg
b3JnYWluemVkIGNvcnJlc3BvbmRpbmdseS4NCiAgIDIpICBUaGUgZnVuY3Rpb25hbCBibG9ja3Ms
IHRlcm1pbm9sb2dpZXMgYW5kIGRlc2NyaXB0aW9ucyBhcmUgbW9kaWZpZWQgYWNjb3JkaW5nbHku
DQogICAzKSAgVGhlIHVzZSBjYXNlcyBpbiB0aGUgb2xkIG9uZXMgZG8gbm90IGFwcGVhciBpbiB0
aGUgbmV3IGRyYWZ0cywgc2luY2UgdGhleSBhcmUgaW5jbHVkZWQgaW4gb3RoZXIgZHJhZnRzLg0K
DQogICBUaGFuayB5b3UgZm9yIHlvdXIgYXR0ZW50aW9uIHRvIENBU00sIGFuZCBhbnkgbmV3IGNv
bW1lbnRzIG9yIHN1Z2dlc3Rpb25zIGFyZSBoaWdseSBhcHByZWNpYXRlZC4NCg0KICAgVGhhbmsg
eW91IQ0KDQpDaG9uZ2ZlbmcgDQoNCg0KDQoNCnhpZWNoZi5icmlAY2hpbmF0ZWxlY29tLmNuDQo=

------=_001_NextPart868116046254_=----
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3Dus-ascii"><style>body { line-height: 1.5; }body { font-size: 10.5pt; f=
ont-family: 'Microsoft YaHei UI'; color: rgb(0, 0, 0); line-height: 1.5; }=
</style></head><body>=0A<div><span></span><br></div><div><span style=3D"fo=
nt-family: &quot;" microsoft=3D"" yahei=3D"" ui'";=3D"" font-size:=3D"" 14=
px;=3D"" color:=3D"" rgb(0,=3D"" 0,=3D"" 0);=3D"" background-color:=3D"" r=
gba(0,=3D"" font-weight:=3D"" normal;=3D"" font-style:=3D"" normal;text-de=
coration:=3D"" none;'=3D"">Hi,all,<br><br>&nbsp;&nbsp;&nbsp;A&nbsp;new&nbs=
p;version&nbsp;of&nbsp;architecture&nbsp;draft&nbsp;has&nbsp;been&nbsp;cre=
ated&nbsp;based&nbsp;on&nbsp;the&nbsp;old&nbsp;ones&nbsp;submitted&nbsp;by=
&nbsp;China&nbsp;Telecom&nbsp;and&nbsp;Juniper&nbsp;seperately.&nbsp;<br><=
span style=3D"font-family: &quot;" microsoft=3D"" yahei=3D"" ui'";=3D"" fo=
nt-size:=3D"" 14px;=3D"" color:=3D"" rgb(0,=3D"" 0,=3D"" 0);=3D"" backgrou=
nd-color:=3D"" rgba(0,=3D"" font-weight:=3D"" normal;=3D"" font-style:=3D"=
" normal;text-decoration:=3D"" none;'=3D""><br></span></span></div><div><s=
pan style=3D"font-family: &quot;" microsoft=3D"" yahei=3D"" ui'";=3D"" fon=
t-size:=3D"" 14px;=3D"" color:=3D"" rgb(0,=3D"" 0,=3D"" 0);=3D"" backgroun=
d-color:=3D"" rgba(0,=3D"" font-weight:=3D"" normal;=3D"" font-style:=3D""=
 normal;text-decoration:=3D"" none;'=3D""><span style=3D"font-family: &quo=
t;" microsoft=3D"" yahei=3D"" ui'";=3D"" font-size:=3D"" 14px;=3D"" color:=
=3D"" rgb(0,=3D"" 0,=3D"" 0);=3D"" background-color:=3D"" rgba(0,=3D"" fon=
t-weight:=3D"" normal;=3D"" font-style:=3D"" normal;text-decoration:=3D"" =
none;'=3D"">&nbsp; https://www.ietf.org/internet-drafts/draft-li-casm-addr=
ess-pool-management-architecture-00.txt</span><br>&nbsp;&nbsp;<br>&nbsp;&n=
bsp;&nbsp;In&nbsp;addtion,&nbsp;several&nbsp;changes&nbsp;has&nbsp;beem&nb=
sp;made&nbsp;as&nbsp;follows,<br>&nbsp;&nbsp;&nbsp;1)&nbsp;&nbsp;The&nbsp;=
new&nbsp;draft&nbsp;hightlights&nbsp;the&nbsp;north&nbsp;and&nbsp;south&nb=
sp;bound&nbsp;interfaces&nbsp;and&nbsp;its&nbsp;paragraphs&nbsp;are&nbsp;o=
rgainzed&nbsp;correspondingly.<br>&nbsp;&nbsp;&nbsp;2)&nbsp;&nbsp;The&nbsp=
;functional&nbsp;blocks,&nbsp;terminologies&nbsp;and&nbsp;descriptions&nbs=
p;are&nbsp;modified&nbsp;accordingly.<br>&nbsp;&nbsp;&nbsp;3)&nbsp;&nbsp;T=
he&nbsp;use&nbsp;cases&nbsp;in&nbsp;the&nbsp;old&nbsp;ones&nbsp;do&nbsp;no=
t&nbsp;appear&nbsp;in&nbsp;the&nbsp;new&nbsp;drafts,&nbsp;since&nbsp;they&=
nbsp;are&nbsp;included&nbsp;in&nbsp;other&nbsp;drafts.<br><br>&nbsp;&nbsp;=
&nbsp;Thank&nbsp;you&nbsp;for&nbsp;your&nbsp;attention&nbsp;to&nbsp;CASM,&=
nbsp;and&nbsp;any&nbsp;new&nbsp;comments&nbsp;or&nbsp;suggestions&nbsp;are=
&nbsp;higly&nbsp;appreciated.<br><br>&nbsp;&nbsp;&nbsp;Thank&nbsp;you!<br>=
<br>Chongfeng&nbsp;</span></div><div><br></div><div><span microsoft=3D"" y=
ahei=3D"" ui'";=3D"" font-size:=3D"" 14px;=3D"" color:=3D"" rgb(0,=3D"" 0,=
=3D"" 0);=3D"" background-color:=3D"" rgba(0,=3D"" font-weight:=3D"" norma=
l;=3D"" font-style:=3D"" normal;text-decoration:=3D"" none;'=3D"" style=3D=
"font-family: '';"><br></span></div><hr style=3D"width: 210px; height: 1px=
;" color=3D"#b5c4df" size=3D"1" align=3D"left">=0A<div><span><div style=3D=
"MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt"><div>xiechf.bri@chin=
atelecom.cn</div></div></span></div>=0A</body></html>
------=_001_NextPart868116046254_=------


From nobody Sat May  6 20:13:59 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: casm@ietfa.amsl.com
Delivered-To: casm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 021EF127873 for <casm@ietfa.amsl.com>; Sat,  6 May 2017 20:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 gRGPE0qsK9sF for <casm@ietfa.amsl.com>; Sat,  6 May 2017 20:13:56 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62F9E126C26 for <casm@ietf.org>; Sat,  6 May 2017 20:13:56 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id q4so19389886pga.3 for <casm@ietf.org>; Sat, 06 May 2017 20:13:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:references:to:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=oqTzMxaCv9Mo1VK7Ou3bpjV6Gj6s0aIMh1QaTgEDx48=; b=YGlwGR31YIZVpFfEzEDq/N6Nc75+1wYcoIC4H5NWOUoApFjumkM7Kniz9zUBKc3PwR GWUuNCZpEsHQppDInhP5KZzE7l2vGI9GneRKy7IY0Y/wZ3FW7FYL7KUXN8HJsgkAB3QC kDs+yJAYyl7YcogOsbN5so/REsMeohfZamcMzaw2OaHrnaRqxnRV1I99oqXYjVXPY6ip Wa7SWAUHyxdSQYU8ybn1WUFWnU8FOc0pS8bxnGXzv3/1KcFQSxmfJqjsaOrxJtfCp8O9 7kfmwXUIVbS73Q3CppK7DoWl77z5iP2GkmgpasoShOoqwXwtyFm+DGPUaGTzmqUBM7e4 ROqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=oqTzMxaCv9Mo1VK7Ou3bpjV6Gj6s0aIMh1QaTgEDx48=; b=LF9xe0MXj4u8qSBFW62JWDc/riinJ8i7xas5IRbgqZq6oUxq7/j+BGt2uC8aO2sclJ E/aBo9pPaWb/AhnLOkdnBY08BybN7SAi7LxkkCjPN4LVZelieDLTMtrGx6sK1S8TkwEW 5Xc47TXwdogRkEAWwvS49kRFgn2UcqAfte5aVCf7aakDQ2E01vzlLnjVdahqQU4Mu+X2 c6XZPda8ItSxFWEJrBJEPdo+vSvTyPpT3lwzfw0OKluwO/Iobofsgu6pSlBlc4S3tRtm HOXOg/W/8W17XMe2co1HAGiWHhGEp35OQZq+Lx56FT19QV72x5cLxx+98BJ7axr6efo7 n1Mg==
X-Gm-Message-State: AN3rC/4pJOd/Sjdh0GlX84qTSKqe/sbRxqANJB9qO7oD/AGBXkySVqx2 LbQNtD/UZ/+z6Rj3
X-Received: by 10.99.156.2 with SMTP id f2mr11649918pge.65.1494126835764; Sat, 06 May 2017 20:13:55 -0700 (PDT)
Received: from [192.168.178.21] (181.228.69.111.dynamic.snap.net.nz. [111.69.228.181]) by smtp.gmail.com with ESMTPSA id s18sm16411449pfi.16.2017.05.06.20.13.54 for <casm@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 May 2017 20:13:55 -0700 (PDT)
References: <8d965972-312c-aff0-a011-b6198baa660e@gmail.com>
To: casm@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
X-Forwarded-Message-Id: <8d965972-312c-aff0-a011-b6198baa660e@gmail.com>
Message-ID: <be7e9963-efd4-acc8-ed35-1c33308aee78@gmail.com>
Date: Sun, 7 May 2017 15:13:51 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <8d965972-312c-aff0-a011-b6198baa660e@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/01DyCJOQhZfITEoXlm5tIaCGRJc>
Subject: [Casm] Fwd: Prefix manager code updated
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Coordinated Address Space Management <casm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/casm>, <mailto:casm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/casm/>
List-Post: <mailto:casm@ietf.org>
List-Help: <mailto:casm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/casm>, <mailto:casm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 May 2017 03:13:58 -0000

In case anybody here is interested; comments welcome of course.

    Brian

-------- Forwarded Message --------
Subject: Prefix manager code updated
Date: Sun, 7 May 2017 15:04:17 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
To: Anima WG <anima@ietf.org>

Hi,

I've uploaded a new improved version of my demo code for draft-ietf-anima-prefix-management.

It can be found at https://www.cs.auckland.ac.nz/~brian/graspy/pfxm2.py, but I advise reading the implementation notes first: https://www.cs.auckland.ac.nz/~brian/graspy/pfxm2.pdf .

There's also a screen shot at https://www.cs.auckland.ac.nz/~brian/graspy/prefixen.png . This shows a 'master' prefix manager (bottom left) and four prefix delegators in action, all running on the same machine (but independent GRASP instances). It works between machines too, but that's hard to capture in a screen shot.

TL;DR:  "Apart from figuring out the bit manipulations and eliminating a few fencepost errors, this was quite easy work. I think it shows that the whole mechanism is viable. With stable storage added, and a secure ACP, it should be safe for real world use. Expansion to cover IPv4 as well would be straightforward, if the objective format allowed it."

Regards
   Brian Carpenter



From nobody Tue May  9 02:38:14 2017
Return-Path: <madi@zdns.cn>
X-Original-To: casm@ietfa.amsl.com
Delivered-To: casm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84A72129409 for <casm@ietfa.amsl.com>; Tue,  9 May 2017 02:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level: 
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 UWbuBkoAqIR1 for <casm@ietfa.amsl.com>; Tue,  9 May 2017 02:38:11 -0700 (PDT)
Received: from gw1.turbomail.org (gw1.turbomail.org [159.8.83.126]) (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 97A6D1287A7 for <CASM@ietf.org>; Tue,  9 May 2017 02:38:07 -0700 (PDT)
X-TM-DID: 7f3505ee720828613a49a6483b231d7f
Content-Type: text/plain; charset=gb2312
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Declan Ma <madi@zdns.cn>
X-Priority: 3
In-Reply-To: <201705061004422586259@chinatelecom.cn>
Date: Tue, 9 May 2017 17:33:35 +0800
Cc: "CASM@ietf.org" <CASM@ietf.org>, "lichen.bri@chinatelecom.cn" <lichen.bri@chinatelecom.cn>, "Xuweiping (A)" <xuweiping@huawei.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD8326E0-110C-4276-98BF-D696158C1798@zdns.cn>
References: <201705061004422586259@chinatelecom.cn>
To: Xie Chongfeng <xiechf.bri@chinatelecom.cn>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/N_jOE4QaslBxBRjSReimgNyDMl4>
Subject: Re: [Casm] New Version Notification for draft-li-casm-address-pool-management-architecture-00.txt
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Coordinated Address Space Management <casm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/casm>, <mailto:casm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/casm/>
List-Post: <mailto:casm@ietf.org>
List-Help: <mailto:casm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/casm>, <mailto:casm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 May 2017 09:38:13 -0000

Chongfeng,

This version is better shaped, which gives prominence to the key points.=20=


I have some editorial comments as follow.

1) There are inconsistent definitions of CASM throughout this document, =
as Coordinated Address Space Management versus Centralized Address Space =
Management.
=20
2) Section 4.2 duplicates what CASM Coordinator is, which has been =
defined in section Terminology yet. Furthermore, I would cross out the =
definition of =A1=B0CASM Coordinator=A1=B1 in this section, for CASM =
Application (section 4.1) and CASM Device (Section 4.3) should be also =
listed if CASM Coordinator would have been seen as a terminology.=20

3) I would prefer to place section 5.1.1 into Section 4.2 since section =
5.1.1 is to present functional description and technical requirements of =
CASM Coordinator.=20


Declan(Di) Ma

ZDNS


> =D4=DA 2017=C4=EA5=D4=C26=C8=D5=A3=AC10:04=A3=ACXie Chongfeng =
<xiechf.bri@chinatelecom.cn> =D0=B4=B5=C0=A3=BA
>=20
>=20
> Hi,all,
>=20
>    A new version of architecture draft has been created based on the =
old ones submitted by China Telecom and Juniper seperately.=20
>=20
>   =
https://www.ietf.org/internet-drafts/draft-li-casm-address-pool-management=
-architecture-00.txt
>  =20
>    In addtion, several changes has beem made as follows,
>    1)  The new draft hightlights the north and south bound interfaces =
and its paragraphs are orgainzed correspondingly.
>    2)  The functional blocks, terminologies and descriptions are =
modified accordingly.
>    3)  The use cases in the old ones do not appear in the new drafts, =
since they are included in other drafts.
>=20
>    Thank you for your attention to CASM, and any new comments or =
suggestions are higly appreciated.
>=20
>    Thank you!
>=20
> Chongfeng=20
>=20
>=20
> xiechf.bri@chinatelecom.cn
> _______________________________________________
> CASM mailing list
> CASM@ietf.org
> https://www.ietf.org/mailman/listinfo/casm


From nobody Fri May 12 19:00:28 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: casm@ietfa.amsl.com
Delivered-To: casm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F4DE129C34 for <casm@ietfa.amsl.com>; Fri, 12 May 2017 19:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 hpAWnBKJYe4x for <casm@ietfa.amsl.com>; Fri, 12 May 2017 19:00:25 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60C0C129C4B for <casm@ietf.org>; Fri, 12 May 2017 18:57:48 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id e193so37717068pfh.0 for <casm@ietf.org>; Fri, 12 May 2017 18:57:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=g6wgJPMDTuPgrgOt5865oNfZ5xB45z6BogtPjkHKRbo=; b=jnlJN5SgaXXOImXVYfRPXidYijW5YxZ7W25DX03rqO0pHEmcLme/Z1No7vQHofV2qs qVFt974DwoTbA+xinq/ZYEXqke1vxA7C9XVR6PdpuJ+qQ00P6Uy2Unw7zTdDRhgvuN2O kk7sAG7U5I4J41rmowmmKbzPyFpov+/eXJ002OD4lS1IMTG37RWf3kHCBCSAyk/KmGxb lp1gWv2nazkUMK4D1IazNJ0IBfOBLJ83ny5uEwXbwdmLFHwijW5r6LF+ShPzABsjFg/g GzLlPTYcEmWN68YIJ80wN/TAcCisjgeib0bo7jOQPEkPvQ7ih/eNjwyNZJDMHBftLp7d nsnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; 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=g6wgJPMDTuPgrgOt5865oNfZ5xB45z6BogtPjkHKRbo=; b=KP2h29flGqlkgZV3aFwAvRdrhZX0NcB6LCHSwf0j6r4j6hd6cGdkrsqkMoSDWkkgqL gmg8hnEAIvuTN9FaFyRskHIPExa2/We58x8LfLGuUpFBDWYWXDqghqKHa3JhBL8Kga6I lvKnFwAGaExImERatzSEh4tQ/F/bbsna9TLUNX+DduIfkLEtIeaTIh7MtNNdDp7K9USJ iPpg9NZwW5q3gBl3oxGOjjG+Kcpn+IkyICw8ndtIotru1lqYoI3liO9dgnp/XOKYV5cT hFHKQDE43FvwpjcxkDetyr32TwbUD5rN4fDT2dpzhmJkSMhA/m9RGzBz9lc8aAHcy6as EGqg==
X-Gm-Message-State: AODbwcAj1XwYixOB8tJQAI3dHCkfDjMp7BxZ7THIjtRjEuFiSvx66E+L /VHuM4mnJnZGWv3o
X-Received: by 10.84.176.100 with SMTP id u91mr9581600plb.39.1494640667776; Fri, 12 May 2017 18:57:47 -0700 (PDT)
Received: from [192.168.178.21] ([118.149.101.24]) by smtp.gmail.com with ESMTPSA id g23sm729538pfb.54.2017.05.12.18.57.46 for <casm@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 May 2017 18:57:47 -0700 (PDT)
To: casm@ietf.org
References: <149395650243.6922.17434599893857692648@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <aafc4043-06bf-e48c-ac05-4fe1396d0040@gmail.com>
Date: Sat, 13 May 2017 13:57:57 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <149395650243.6922.17434599893857692648@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/88GVRT5YAt_nsYf_wljWWlk4D_w>
Subject: Re: [Casm] I-D Action: draft-li-casm-address-pool-management-architecture-00.txt
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Coordinated Address Space Management <casm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/casm>, <mailto:casm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/casm/>
List-Post: <mailto:casm@ietf.org>
List-Help: <mailto:casm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/casm>, <mailto:casm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 May 2017 02:00:26 -0000

Hi,

Thanks for this interesting draft.

First, here is one of the definitions:

>       CASM Coordinator: A management system which has a centralized
>       database manage the overall address pools and allocate address
>       pools to the device in the devices.

Ther is no need for this database to be centralized or for the
allocation of address pools to be centralized. It can be done with
a completely distributed system. (I agree that centralized logging
might be needed.) In fact, sections 4.2 and 4.3 describe a centralized
model for everything, not just for logging.

Could we perhaps agree that this is only one possible architecture?
If so, we would also need a second draft describing a distributed
architecture. It's quite hard to cover both designs in one document.

>    The overall procedure is as follows:
> 
>    o  Operators will configure remaining address pools centrally in the
>       Address Pool Management System (APMS).  There are multiple address
>       pools which can be configured centrally.  The APMS server will
>       then divide the address pools into addressing unit (AU) which will
>       be allocated to the agent in devices by default.

Certainly the NOC will configure initial address pools into a master agent.
But from that moment, a distributed process can take over in which pools
(prefixes) will allocated to distributed agents on demand, with no need
for default allocations.

>    o  If the lifetime of the address pool is going to expire, the DA
>       should issue an AddressPoolRenew request to extend the
>       lifetime,including the IPv4, IPv6, Ports, etc.

A couple of questions on this.:

1. Why is the lifetime useful? Firstly, once an address has been
allocated to an end-user, it must be left there as long as necessary;
you can't recover an address while it is in active use. That will
block the address pool that contains it indefinitely, so what is the
value of the lifetime? Secondly, if there is no lifetime, the agent
can release the address pool on demand if it is not in use. Again,
there is no value in the lifetime that I can see.

2. Is it really useful to include the notion of ports in an address
pool? In the case of IPv6 it is definitely useless. In the case of
IPv4 with A+P (port-based address sharing, RFC6346), surely you never
want to share a single address across different agents? That would
lead to complex and fragile CASM operations at rather high frequency.
RFC6346 defines how A+P gateways may talk to each other (horizontally,
not north-south) to share an address using A+P. You seem to be
duplicating that function. Also, RFC7768 seems to assume that port
sharing occurs entirely within a single CGN. So it seems to me that
it's wrong to include port ranges in the CASM model.

(Note: I have no problem with 'port-range' being defined in the
CASM YANG model; that seems necessary for completeness. My problem
is with using it in network-wide resource management, which doesn't
seem reasonable.)

> 5.1.1.1.  Address pools
...
>    o  IPv6 addresses

I suggest dividing this into 'Globally routable' and 'ULA'

>    o  MAC Addresses

Can you explain this? Where do layer 2 addresses fit in?

...
>   Multicast address pool:

This topic needs more discussion.

Regards
   Brian


From nobody Wed May 17 02:35:07 2017
Return-Path: <xiechf.bri@chinatelecom.cn>
X-Original-To: casm@ietfa.amsl.com
Delivered-To: casm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD410129AC4 for <casm@ietfa.amsl.com>; Wed, 17 May 2017 02:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.808
X-Spam-Level: 
X-Spam-Status: No, score=0.808 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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 yHhTs-X4BXzc for <casm@ietfa.amsl.com>; Wed, 17 May 2017 02:35:00 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.219]) by ietfa.amsl.com (Postfix) with ESMTP id 04420126E01 for <casm@ietf.org>; Wed, 17 May 2017 02:30:21 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.80:49994.177726158
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.78 (unknown [172.18.0.80]) by chinatelecom.cn (HERMES) with ESMTP id ED1652800A5 for <casm@ietf.org>; Wed, 17 May 2017 17:30:17 +0800 (CST)
Received: from ip<219.142.69.78> ([172.18.0.80]) by App0022 with ESMTP id c554f3e1-c1ae-4bd0-8524-f13111e7c561 for casm@ietf.org; Wed May 17 17:30:17 2017
0/X-Total-Score: 0:
X-Real-From: xiechf.bri@chinatelecom.cn
X-Receive-IP: 172.18.0.80
X-MEDUSA-Status: 0
Date: Wed, 17 May 2017 17:30:14 +0800
From: "xiechf.bri@chinatelecom.cn" <xiechf.bri@chinatelecom.cn>
To: casm <casm@ietf.org>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 8, 379[cn]
Mime-Version: 1.0
Message-ID: <2017051717301370653329@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart504111817885_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/m6B2u3RXS6d7G6IF6QZsetaqa8w>
Subject: Re: [Casm] I-D Action: draft-li-casm-address-pool-management-architecture-00.txt
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Coordinated Address Space Management <casm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/casm>, <mailto:casm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/casm/>
List-Post: <mailto:casm@ietf.org>
List-Help: <mailto:casm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/casm>, <mailto:casm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 May 2017 09:35:06 -0000

This is a multi-part message in MIME format.

------=_001_NextPart504111817885_=----
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: base64

SGmjrEJyaWFuLCANCg0KICAgICAgIFRoYW5rIHlvdSBmb3IgeW91ciBjb21tZW50cywgcGxzIHNl
ZSBpbmxpbmUgZm9yIG1vcmUgY29tbWVudHOjrg0KDQpDaG9uZ2ZlbmehoQ0KIA0KSGksDQogDQpU
aGFua3MgZm9yIHRoaXMgaW50ZXJlc3RpbmcgZHJhZnQuDQogDQpGaXJzdCwgaGVyZSBpcyBvbmUg
b2YgdGhlIGRlZmluaXRpb25zOg0KIA0KPiAgICAgICBDQVNNIENvb3JkaW5hdG9yOiBBIG1hbmFn
ZW1lbnQgc3lzdGVtIHdoaWNoIGhhcyBhIGNlbnRyYWxpemVkDQo+ICAgICAgIGRhdGFiYXNlIG1h
bmFnZSB0aGUgb3ZlcmFsbCBhZGRyZXNzIHBvb2xzIGFuZCBhbGxvY2F0ZSBhZGRyZXNzDQo+ICAg
ICAgIHBvb2xzIHRvIHRoZSBkZXZpY2UgaW4gdGhlIGRldmljZXMuDQogDQpUaGVyIGlzIG5vIG5l
ZWQgZm9yIHRoaXMgZGF0YWJhc2UgdG8gYmUgY2VudHJhbGl6ZWQgb3IgZm9yIHRoZSBhbGxvY2F0
aW9uIG9mIGFkZHJlc3MgcG9vbHMgdG8gYmUgY2VudHJhbGl6ZWQuIEl0IGNhbiBiZSBkb25lIHdp
dGggYSBjb21wbGV0ZWx5IGRpc3RyaWJ1dGVkIHN5c3RlbS4gKEkgYWdyZWUgdGhhdCBjZW50cmFs
aXplZCBsb2dnaW5nIG1pZ2h0IGJlIG5lZWRlZC4pIEluIGZhY3QsIHNlY3Rpb25zIDQuMiBhbmQg
NC4zIGRlc2NyaWJlIGEgY2VudHJhbGl6ZWQgbW9kZWwgZm9yIGV2ZXJ5dGhpbmcsIG5vdCBqdXN0
IGZvciBsb2dnaW5nLg0KDQogQ2hvbmdmZW5nOiChoUNlbnRyYWxpemVkIGFuZCBkaXN0cmlidXRl
ZCBpcyBhIGRpZmZlcmVudCB3YXkgb2YgaW1wbGVtZW50YXRpb24sIGluIHRoZSB0cmFkaXRpb25h
bCBuZXR3b3JrLCB1c3VhbGx5IHVzaW5nIGEgZGlzdHJpYnV0ZWQgYXBwcm9hY2gsIHRoZSBkaXN0
cmlidXRlZCBhcHByb2FjaCBpcyBub3QgZXhjbHVkZWQsIGFuZCBDQVNNIGZvY3VzIG9uIGNlbnRy
YWxpemVkIHNvbHV0aW9ucy6hoUluIHRoZSBjZW50cmFsaXplZCBhZGRyZXNzIHJlc291cmNlIG1h
bmFnZW1lbnQgYXJjaGl0ZWN0dXJlLCB0aGUgYWxsb2NhdGlvbiBvZiBhZGRyZXNzIGJsb2NrcyBp
cyBkZXRlcm1pbmVkIGJ5IHRoZSBDQVNNIENvb3JkaW5hdG9yLCB3aGljaCByZXF1aXJlcyB0aGUg
bWFpbnRlbmFuY2Ugb2YgYWxsb2NhdGVkLCB1bmFsbG9jYXRlZCBhZGRyZXNzIGJsb2NrLCBhbmQg
dGhlcmVmb3JlIHJlcXVpcmVzIGEgZGF0YWJhc2UgdG8gaG9sZCBzdWNoIGluZm9ybWF0aW9uLiBB
bmQgYWxzbywgaXQgbWFpbnRhaW5zIGxvZyBpbmZvcm1hdGlvbi4NCiANCkNvdWxkIHdlIHBlcmhh
cHMgYWdyZWUgdGhhdCB0aGlzIGlzIG9ubHkgb25lIHBvc3NpYmxlIGFyY2hpdGVjdHVyZT8NCklm
IHNvLCB3ZSB3b3VsZCBhbHNvIG5lZWQgYSBzZWNvbmQgZHJhZnQgZGVzY3JpYmluZyBhIGRpc3Ry
aWJ1dGVkIGFyY2hpdGVjdHVyZS4gSXQncyBxdWl0ZSBoYXJkIHRvIGNvdmVyIGJvdGggZGVzaWdu
cyBpbiBvbmUgZG9jdW1lbnQuDQoNCiBDaG9uZ2Zlbmc6IKGhWWVzLCBhcyBtZW50aW9uZWQgZWFy
bGllciwgY2VudHJhbGl6ZWQgaXMgYSBwb3NzaWJsZSBhcmNoaXRlY3R1cmUuIEEgdHlwaWNhbCBk
aXN0cmlidXRlZCBleGFtcGxlIGlzIEJORywgd2hpY2ggYXNzaWducyBhZGRyZXNzZXMgdG8gZW5k
IHVzZXJzLiBJdCBpcyBhIHdheSB0aGF0IGhhcyBleGlzdGVkIGZvciBhIGxvbmcgdGltZSwgc2hv
dWxkIG5vdCBuZWVkIHRoZSBzdGFuZGFyZCwgcmlnaHQ/IA0KIA0KPiAgICBUaGUgb3ZlcmFsbCBw
cm9jZWR1cmUgaXMgYXMgZm9sbG93czoNCj4gDQo+ICAgIG8gIE9wZXJhdG9ycyB3aWxsIGNvbmZp
Z3VyZSByZW1haW5pbmcgYWRkcmVzcyBwb29scyBjZW50cmFsbHkgaW4gdGhlDQo+ICAgICAgIEFk
ZHJlc3MgUG9vbCBNYW5hZ2VtZW50IFN5c3RlbSAoQVBNUykuICBUaGVyZSBhcmUgbXVsdGlwbGUg
YWRkcmVzcw0KPiAgICAgICBwb29scyB3aGljaCBjYW4gYmUgY29uZmlndXJlZCBjZW50cmFsbHku
ICBUaGUgQVBNUyBzZXJ2ZXIgd2lsbA0KPiAgICAgICB0aGVuIGRpdmlkZSB0aGUgYWRkcmVzcyBw
b29scyBpbnRvIGFkZHJlc3NpbmcgdW5pdCAoQVUpIHdoaWNoIHdpbGwNCj4gICAgICAgYmUgYWxs
b2NhdGVkIHRvIHRoZSBhZ2VudCBpbiBkZXZpY2VzIGJ5IGRlZmF1bHQuDQogDQpDZXJ0YWlubHkg
dGhlIE5PQyB3aWxsIGNvbmZpZ3VyZSBpbml0aWFsIGFkZHJlc3MgcG9vbHMgaW50byBhIG1hc3Rl
ciBhZ2VudC4NCkJ1dCBmcm9tIHRoYXQgbW9tZW50LCBhIGRpc3RyaWJ1dGVkIHByb2Nlc3MgY2Fu
IHRha2Ugb3ZlciBpbiB3aGljaCBwb29scw0KKHByZWZpeGVzKSB3aWxsIGFsbG9jYXRlZCB0byBk
aXN0cmlidXRlZCBhZ2VudHMgb24gZGVtYW5kLCB3aXRoIG5vIG5lZWQgZm9yIGRlZmF1bHQgYWxs
b2NhdGlvbnMuDQoNCkNob25nZmVuZzqhoSBJbiB0aGUgaW5pdGlhbCBzdGF0ZSwgQ0FTTSBDb29y
ZGluYXRvciBhc3NpZ24gYWRkcmVzcyBwb29scyB0byB0aGUgQWdlbnQgaW4gdGhlIGRldmljZS4g
VGhlbiwgSW4gdGhlIHByb2Nlc3Mgb2YgcnVubmluZywgaWYgdGhlIEFnZW50J3MgYWRkcmVzcyBw
b29sIHJlc291cmNlcyBoYXZlIGJlZW4gdXNlZCB1cCwgdGhlIEFnZW50IG5lZWQgdG8gYXBwbHkg
bW9yZSBhZGRyZXNzIGJsb2NrczsgSW4gYWRkaXRpb24sIHdoZW4gdGhlIGFkZHJlc3MgcG9vbCB1
c2FnZSBpcyB0b28gbG93LCB0aGUgQWdlbnQgY2FuIHJlbGVhc2UgYSBwYXJ0IG9mIHRoZSBhZGRy
ZXNzIGJsb2NrcyB0byBDQVNNIENvb3JkaW5hdG9yLiANCiANCj4gICAgbyAgSWYgdGhlIGxpZmV0
aW1lIG9mIHRoZSBhZGRyZXNzIHBvb2wgaXMgZ29pbmcgdG8gZXhwaXJlLCB0aGUgREENCj4gICAg
ICAgc2hvdWxkIGlzc3VlIGFuIEFkZHJlc3NQb29sUmVuZXcgcmVxdWVzdCB0byBleHRlbmQgdGhl
DQo+ICAgICAgIGxpZmV0aW1lLGluY2x1ZGluZyB0aGUgSVB2NCwgSVB2NiwgUG9ydHMsIGV0Yy4N
CiANCkEgY291cGxlIG9mIHF1ZXN0aW9ucyBvbiB0aGlzLjoNCiANCjEuIFdoeSBpcyB0aGUgbGlm
ZXRpbWUgdXNlZnVsPyBGaXJzdGx5LCBvbmNlIGFuIGFkZHJlc3MgaGFzIGJlZW4gYWxsb2NhdGVk
IHRvIGFuIGVuZC11c2VyLCBpdCBtdXN0IGJlIGxlZnQgdGhlcmUgYXMgbG9uZyBhcyBuZWNlc3Nh
cnk7IHlvdSBjYW4ndCByZWNvdmVyIGFuIGFkZHJlc3Mgd2hpbGUgaXQgaXMgaW4gYWN0aXZlIHVz
ZS4gVGhhdCB3aWxsIGJsb2NrIHRoZSBhZGRyZXNzIHBvb2wgdGhhdCBjb250YWlucyBpdCBpbmRl
ZmluaXRlbHksIHNvIHdoYXQgaXMgdGhlIHZhbHVlIG9mIHRoZSBsaWZldGltZT8gU2Vjb25kbHks
IGlmIHRoZXJlIGlzIG5vIGxpZmV0aW1lLCB0aGUgYWdlbnQgY2FuIHJlbGVhc2UgdGhlIGFkZHJl
c3MgcG9vbCBvbiBkZW1hbmQgaWYgaXQgaXMgbm90IGluIHVzZS4gQWdhaW4sIHRoZXJlIGlzIG5v
IHZhbHVlIGluIHRoZSBsaWZldGltZSB0aGF0IEkgY2FuIHNlZS4NCg0KQ2hvbmdmZW5nOqGhoaFG
b3IgREhDUCBTZXJ2ZXIgc2VydmljZSwgbGlmZXRpbWUgaXMgYW4gaW1wb3J0YW50IHBhcmFtZXRl
ciwgaXQgbmVlZCBzcGVjaWZ5IExpZmV0aW1lLCBmb3IgdGhlIERIQ1Agc2VydmVyIHRvIGFzc2ln
biBhZGRyZXNzZXMgdG8gdGhlIGVuZCB1c2VyLCBjb250cm9sIHRoZSBhdmFpbGFibGUgdGltZSwg
aW4gYWRkaXRpb24sIHdoZW4gdGhlIGVuZCB1c2VyIGFibm9ybWFsIG9mZi1saW5lLCBESENQIFNl
cnZlciBuZWVkIHRvIHJlY3ljbGUgdGhlIGFkZHJlc3MgYnkgTGlmZXRpbWUgZXhwaXJhdGlvbi4g
DQogDQoyLiBJcyBpdCByZWFsbHkgdXNlZnVsIHRvIGluY2x1ZGUgdGhlIG5vdGlvbiBvZiBwb3J0
cyBpbiBhbiBhZGRyZXNzIHBvb2w/IEluIHRoZSBjYXNlIG9mIElQdjYgaXQgaXMgZGVmaW5pdGVs
eSB1c2VsZXNzLiBJbiB0aGUgY2FzZSBvZg0KSVB2NCB3aXRoIEErUCAocG9ydC1iYXNlZCBhZGRy
ZXNzIHNoYXJpbmcsIFJGQzYzNDYpLCBzdXJlbHkgeW91IG5ldmVyIHdhbnQgdG8gc2hhcmUgYSBz
aW5nbGUgYWRkcmVzcyBhY3Jvc3MgZGlmZmVyZW50IGFnZW50cz8gVGhhdCB3b3VsZCBsZWFkIHRv
IGNvbXBsZXggYW5kIGZyYWdpbGUgQ0FTTSBvcGVyYXRpb25zIGF0IHJhdGhlciBoaWdoIGZyZXF1
ZW5jeS4NClJGQzYzNDYgZGVmaW5lcyBob3cgQStQIGdhdGV3YXlzIG1heSB0YWxrIHRvIGVhY2gg
b3RoZXIgKGhvcml6b250YWxseSwgbm90IG5vcnRoLXNvdXRoKSB0byBzaGFyZSBhbiBhZGRyZXNz
IHVzaW5nIEErUC4gWW91IHNlZW0gdG8gYmUgZHVwbGljYXRpbmcgdGhhdCBmdW5jdGlvbi4gQWxz
bywgUkZDNzc2OCBzZWVtcyB0byBhc3N1bWUgdGhhdCBwb3J0IHNoYXJpbmcgb2NjdXJzIGVudGly
ZWx5IHdpdGhpbiBhIHNpbmdsZSBDR04uIFNvIGl0IHNlZW1zIHRvIG1lIHRoYXQgaXQncyB3cm9u
ZyB0byBpbmNsdWRlIHBvcnQgcmFuZ2VzIGluIHRoZSBDQVNNIG1vZGVsLg0KIA0KKE5vdGU6IEkg
aGF2ZSBubyBwcm9ibGVtIHdpdGggJ3BvcnQtcmFuZ2UnIGJlaW5nIGRlZmluZWQgaW4gdGhlIENB
U00gWUFORyBtb2RlbDsgdGhhdCBzZWVtcyBuZWNlc3NhcnkgZm9yIGNvbXBsZXRlbmVzcy4gTXkg
cHJvYmxlbSBpcyB3aXRoIHVzaW5nIGl0IGluIG5ldHdvcmstd2lkZSByZXNvdXJjZSBtYW5hZ2Vt
ZW50LCB3aGljaCBkb2Vzbid0IHNlZW0gcmVhc29uYWJsZS4pDQoNCkNob25nZmVuZzqhoUFzIHdl
IGtub3csIHRoZSByYW5nZSBvZiBwb3J0cyBpcyAxIHRvIDY1NTM1LCBidXQgZHVyaW5nIE5BVCB1
c2UsIG9ubHkgYSBwb3J0aW9uIGlzIGF2YWlsYWJsZSBmb3IgdXNlLCBzdWNoIGFzIDIwNDggdG8g
NjU1MzUuIEkgYWdyZWUgd2l0aCB3aGF0IHlvdSBzYWlkICJSRkM3NzY4IHNlZW1zIHRvIGFzc3Vt
ZSB0aGF0IHBvcnQgY29tcHJvbWlzZWQgYnkgd2l0aGluIGEgc2luZ2xlIENHTiIsIEhlcmUgaXQg
dXNlZCBpbiBub3J0aC1zb3V0aCwgYW5kIHVzZWQgdG8gc2V0IHRoZSByYW5nZSBvZiBwb3J0cyB0
aGF0IE5BVCBjYW4gdXNlLiBVc3VhbGx5LCBJUHY0IGFuZCBwb3J0IGFyZSB1c2VkIHRvZ2V0aGVy
LiANCiANCj4gNS4xLjEuMS4gIEFkZHJlc3MgcG9vbHMNCi4uLg0KPiAgICBvICBJUHY2IGFkZHJl
c3Nlcw0KIA0KSSBzdWdnZXN0IGRpdmlkaW5nIHRoaXMgaW50byAnR2xvYmFsbHkgcm91dGFibGUn
IGFuZCAnVUxBJw0KDQogDQo+ICAgIG8gIE1BQyBBZGRyZXNzZXMNCiANCkNhbiB5b3UgZXhwbGFp
biB0aGlzPyBXaGVyZSBkbyBsYXllciAyIGFkZHJlc3NlcyBmaXQgaW4/DQogDQouLi4NCj4gICBN
dWx0aWNhc3QgYWRkcmVzcyBwb29sOg0KIA0KVGhpcyB0b3BpYyBuZWVkcyBtb3JlIGRpc2N1c3Np
b24uDQogDQpSZWdhcmRzDQogICBCcmlhbg0KIA0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCkNBU00gbWFpbGluZyBsaXN0DQpDQVNNQGlldGYub3JnDQpo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2Nhc20NCg==

------=_001_NextPart504111817885_=----
Content-Type: text/html;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DGB2312"><style>body { line-height: 1.5; }blockquote { margin-top: 0px;=
 margin-bottom: 0px; margin-left: 0.5em; }body { font-size: 10.5pt; font-f=
amily: 'Microsoft YaHei UI'; color: rgb(0, 0, 0); line-height: 1.5; }</sty=
le></head><body>=0A<div><b><span></span>Hi=A3=ACBrian,&nbsp;</b></div><div=
><b><br></b></div><div><b>&nbsp; &nbsp; &nbsp; &nbsp;Thank you for your co=
mments,&nbsp;</b><span style=3D"font-family: ''; font-size: 10.5pt; line-h=
eight: 1.5; background-color: window;"><b>pls&nbsp;see&nbsp;inline&nbsp;fo=
r&nbsp;more&nbsp;comments=A3=AE</b></span></div><div><b><br></b></div><div=
><b>Chongfeng=A1=A1</b></div><blockquote style=3D"margin-top: 0px; margin-=
bottom: 0px; margin-left: 0.5em;">=0A<div>&nbsp;</div>=0A<div>Hi,</div>=0A=
<div>&nbsp;</div>=0A<div>Thanks for this interesting draft.</div>=0A<div>&=
nbsp;</div>=0A<div>First, here is one of the definitions:</div>=0A<div>&nb=
sp;</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CASM Coordinator=
: A management system which has a centralized</div>=0A<div>&gt;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; database manage the overall address pools and al=
locate address</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pools=
 to the device in the devices.</div>=0A<div>&nbsp;</div>=0A<div>Ther is no=
 need for this database to be centralized or for the allocation of address=
 pools to be centralized. It can be done with a completely distributed sys=
tem. (I agree that centralized logging might be needed.) In fact, sections=
 4.2 and 4.3 describe a centralized model for everything, not just for log=
ging.</div>=0A<div><span style=3D"font-size: 10.5pt; line-height: 1.5; bac=
kground-color: window;"><br></span></div><div><b><span style=3D"font-size:=
 10.5pt; line-height: 1.5; background-color: window;">&nbsp;Chongfeng: =A1=
=A1Centralized and distributed is a different way of implementation, in th=
e traditional network, usually using a distributed approach, the distribut=
ed approach is not excluded, and CASM focus on centralized solutions.=A1=
=A1</span><span style=3D"font-size: 10.5pt; line-height: 1.5; background-c=
olor: window;">In the centralized address resource management architecture=
, the allocation of address blocks is determined by the CASM Coordinator, =
which requires the maintenance of allocated, unallocated address block, an=
d therefore requires a database to hold such information. And also, it mai=
ntains log information.</span></b></div>=0A<div>&nbsp;</div>=0A<div>Could =
we perhaps agree that this is only one possible architecture?</div>=0A<div=
>If so, we would also need a second draft describing a distributed archite=
cture. It's quite hard to cover both designs in one document.</div>=0A<div=
><span style=3D"font-size: 10.5pt; line-height: 1.5; background-color: win=
dow;"><br></span></div><b>&nbsp;Chongfeng: =A1=A1<span style=3D"background=
-color: window; font-size: 10.5pt; line-height: 1.5;">Yes, as mentioned ea=
rlier, centralized is a possible architecture. A typical distributed examp=
le is BNG, which assigns addresses to end users. It is a way that has exis=
ted for a long time, should not need the standard, right?</span></b>=0A<di=
v>&nbsp;</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp; The overall procedure is as f=
ollows:</div>=0A<div>&gt; </div>=0A<div>&gt;&nbsp;&nbsp;&nbsp; o&nbsp; Ope=
rators will configure remaining address pools centrally in the</div>=0A<di=
v>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Address Pool Management System =
(APMS).&nbsp; There are multiple address</div>=0A<div>&gt;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; pools which can be configured centrally.&nbsp; The AP=
MS server will</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; then =
divide the address pools into addressing unit (AU) which will</div>=0A<div=
>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be allocated to the agent in dev=
ices by default.</div>=0A<div>&nbsp;</div>=0A<div>Certainly the NOC will c=
onfigure initial address pools into a master agent.</div>=0A<div>But from =
that moment, a distributed process can take over in which pools</div>=0A<d=
iv>(prefixes) will allocated to distributed agents on demand, with no need=
 for default allocations.</div>=0A<div><br></div>=0A<div><b>Chongfeng:=A1=
=A1 In the initial state, CASM Coordinator assign address pools to the Age=
nt in the device. Then, In the process of running, if the Agent's address =
pool resources have been used up, the Agent need to apply more address blo=
cks; In addition, when the address pool usage is too low, the Agent can re=
lease a part of the address blocks to CASM Coordinator. </b></div>=0A<div>=
&nbsp;</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp; o&nbsp; If the lifetime of the =
address pool is going to expire, the DA</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; should issue an AddressPoolRenew request to extend the=
</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lifetime,including =
the IPv4, IPv6, Ports, etc.</div>=0A<div>&nbsp;</div>=0A<div>A couple of q=
uestions on this.:</div>=0A<div>&nbsp;</div>=0A<div>1. Why is the lifetime=
 useful? Firstly, once an address has been allocated to an end-user, it mu=
st be left there as long as necessary; you can't recover an address while =
it is in active use. That will block the address pool that contains it ind=
efinitely, so what is the value of the lifetime? Secondly, if there is no =
lifetime, the agent can release the address pool on demand if it is not in=
 use. Again, there is no value in the lifetime that I can see.</div>=0A<di=
v><br></div>=0A<b>Chongfeng:=A1=A1=A1=A1<span style=3D"font-size: 10.5pt; =
line-height: 1.5; background-color: window;">For DHCP Server service, life=
time is an important parameter, it need specify Lifetime, for the DHCP ser=
ver to assign addresses to the end user, control the available time, in ad=
dition, when the end user abnormal off-line, DHCP Server need to recycle t=
he address by Lifetime expiration.</span></b>=0A<div>&nbsp;</div>=0A<div>2=
. Is it really useful to include the notion of ports in an address pool? I=
n the case of IPv6 it is definitely useless. In the case of</div>=0A<div>I=
Pv4 with A+P (port-based address sharing, RFC6346), surely you never want =
to share a single address across different agents? That would lead to comp=
lex and fragile CASM operations at rather high frequency.</div>=0A<div>RFC=
6346 defines how A+P gateways may talk to each other (horizontally, not no=
rth-south) to share an address using A+P. You seem to be duplicating that =
function. Also, RFC7768 seems to assume that port sharing occurs entirely =
within a single CGN. So it seems to me that it's wrong to include port ran=
ges in the CASM model.</div>=0A<div>&nbsp;</div>=0A<div>(Note: I have no p=
roblem with 'port-range' being defined in the CASM YANG model; that seems =
necessary for completeness. My problem is with using it in network-wide re=
source management, which doesn't seem reasonable.)</div>=0A<div><b><br></b=
></div>=0A<b>Chongfeng:=A1=A1<span style=3D"font-size: 10.5pt; line-height=
: 1.5; background-color: window;">As we know, the range of ports is 1 to 6=
5535, but during NAT use, only a portion is available for use, such as 204=
8 to 65535. I agree with what you said "RFC7768 seems to assume that port =
compromised by within a single CGN", Here it used in north-south, and used=
 to set the range of ports that NAT can use. Usually, IPv4 and port are us=
ed together.</span></b>=0A<div>&nbsp;</div>=0A<div>&gt; 5.1.1.1.&nbsp; Add=
ress pools</div>=0A<div>...</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp; o&nbsp; IP=
v6 addresses</div>=0A<div>&nbsp;</div>=0A<div>I suggest dividing this into=
 'Globally routable' and 'ULA'</div>=0A<div><br></div>=0A<div>&nbsp;</div>=
=0A<div>&gt;&nbsp;&nbsp;&nbsp; o&nbsp; MAC Addresses</div>=0A<div>&nbsp;</=
div>=0A<div>Can you explain this? Where do layer 2 addresses fit in?</div>=
=0A<div>&nbsp;</div>=0A<div>...</div>=0A<div>&gt;&nbsp;&nbsp; Multicast ad=
dress pool:</div>=0A<div>&nbsp;</div>=0A<div>This topic needs more discuss=
ion.</div>=0A<div>&nbsp;</div>=0A<div>Regards</div>=0A<div>&nbsp;&nbsp; Br=
ian</div>=0A<div>&nbsp;</div>=0A<div>_____________________________________=
__________</div>=0A<div>CASM mailing list</div>=0A<div>CASM@ietf.org</div>=
=0A<div>https://www.ietf.org/mailman/listinfo/casm</div>=0A</blockquote>=
=0A</body></html>
------=_001_NextPart504111817885_=------


From nobody Tue May 23 12:51:58 2017
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: casm@ietfa.amsl.com
Delivered-To: casm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6D2A12EAE1 for <casm@ietfa.amsl.com>; Tue, 23 May 2017 12:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 QT3-SdWRcBIo for <casm@ietfa.amsl.com>; Tue, 23 May 2017 12:51:54 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7644912EAEB for <CASM@ietf.org>; Tue, 23 May 2017 12:51:54 -0700 (PDT)
Received: from [10.0.1.20] (h132.viagenie.ca [206.123.31.132]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E489347679 for <CASM@ietf.org>; Tue, 23 May 2017 15:51:53 -0400 (EDT)
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: "CASM@ietf.org" <CASM@ietf.org>
Date: Tue, 23 May 2017 15:51:53 -0400
Message-ID: <BD0DFE75-6D45-4C62-A708-3F4123D9BF9D@viagenie.ca>
References: <149556850339.28443.2716896366216678645.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/6fbwy8d2qAmTP3mRD947Je8DrKA>
Subject: [Casm] Fwd: Last Call: <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> (Unique IPv6 Prefix Per Host) to Best Current Practice
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Coordinated Address Space Management <casm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/casm>, <mailto:casm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/casm/>
List-Post: <mailto:casm@ietf.org>
List-Help: <mailto:casm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/casm>, <mailto:casm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 May 2017 19:51:57 -0000

hello,
  this could really benefit from CASM architecture, IMHO.

Marc.

Forwarded message:

> From: The IESG <iesg-secretary@ietf.org>
> To: IETF-Announce <ietf-announce@ietf.org>
> Cc: v6ops@ietf.org, rbonica@juniper.net, =

> draft-ietf-v6ops-unique-ipv6-prefix-per-host@ietf.org, =

> draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org, =

> v6ops-chairs@ietf.org
> Subject: Last Call: =

> <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> (Unique IPv6 =

> Prefix Per Host) to Best Current Practice
> Date: Tue, 23 May 2017 12:41:43 -0700
>
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'Unique IPv6 Prefix Per Host'
>   <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> as Best =

> Current
> Practice
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-06-06. Exceptionally, comments may =

> be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    In some IPv6 environments, the need has arisen for hosts to be able
>    to utilize a unique IPv6 prefix, even though the link or media may =

> be
>    shared.  Typically hosts (subscribers) on a shared network, either
>    wired or wireless, such as Ethernet, WiFi, etc., will acquire =

> unique
>    IPv6 addresses from a common IPv6 prefix that is allocated or
>    assigned for use on a specific link.
>
>    In most deployments today, IPv6 address assignment from a single =

> IPv6
>    prefix on a shared network is done by either using IPv6 stateless
>    address auto-configuration (SLAAC) and/or stateful DHCPv6.  While
>    this is still viable and operates as designed, there are some large
>    scale environments where this concept introduces significant
>    performance challenges and implications, specifically related to =

> IPv6
>    router and neighbor discovery.
>
>    This document outlines an approach utilising existing IPv6 =

> protocols
>    to allow hosts to be assigned a unique IPv6 prefix (instead of a
>    unique IPv6 address from a shared IPv6 prefix).  Benefits of unique
>    IPv6 prefix over a unique IPv6 address from the service provider
>    include improved subscriber isolation and enhanced subscriber
>    management.
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-pe=
r-host/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-pe=
r-host/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> The document contains these normative downward references.
> See RFC 3967 for additional information:
>     rfc6106: IPv6 Router Advertisement Options for DNS Configuration =

> (Proposed Standard - IETF stream)
>     rfc4941: Privacy Extensions for Stateless Address =

> Autoconfiguration in IPv6 (Draft Standard - IETF stream)
>     rfc4862: IPv6 Stateless Address Autoconfiguration (Draft Standard =

> - IETF stream)
>     rfc3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) =

> (Proposed Standard - IETF stream)

