[Casm] review of draft-kumar-casm-requirements-and-framework

"Liushucheng (Will Liu)" <liushucheng@huawei.com> Thu, 23 February 2017 12:21 UTC

Return-Path: <liushucheng@huawei.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 CB15F1296E0; Thu, 23 Feb 2017 04:21:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 d7E6IcoMPDUJ; Thu, 23 Feb 2017 04:21:36 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A513E1296FC; Thu, 23 Feb 2017 04:21:35 -0800 (PST)
Received: from 172.18.7.190 (EHLO LHREML712-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DBO82619; Thu, 23 Feb 2017 12:21:32 +0000 (GMT)
Received: from SZXEMA413-HUB.china.huawei.com (10.82.72.72) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 23 Feb 2017 12:21:30 +0000
Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.147]) by SZXEMA413-HUB.china.huawei.com ([10.82.72.72]) with mapi id 14.03.0235.001; Thu, 23 Feb 2017 20:21:21 +0800
From: "Liushucheng (Will Liu)" <liushucheng@huawei.com>
To: "CASM@ietf.org" <CASM@ietf.org>, "draft-kumar-casm-requirements-and-framework@ietf.org" <draft-kumar-casm-requirements-and-framework@ietf.org>
Thread-Topic: review of draft-kumar-casm-requirements-and-framework
Thread-Index: AdKNzFaDf97aX6fvRmm+LIs5c5tAOw==
Date: Thu, 23 Feb 2017 12:21:21 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB898C8936@SZXEMA509-MBS.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.79.101]
Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB898C8936SZXEMA509MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.58AED3CD.00AA, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.147, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: e70f413c5b773fc37d01ab17b33a3caf
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/DtzMeQ0Q9sMq-wHcIpjh1CHPBF8>
Cc: "Pengtao \(Tony\)" <dr.pengtao@huawei.com>, "Xuweiping \(David\)" <xuweiping@huawei.com>
Subject: [Casm] review of draft-kumar-casm-requirements-and-framework
X-BeenThere: casm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Centralized 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: Thu, 23 Feb 2017 12:21:39 -0000

Hi all,

Below please find our review of draft-kumar-casm-requirements-and-framework.



**** Technical ****


* Section 4

I would suggest to put requirement section into the use case draft.



*Section 5

>       +----------------+ +------+ +----+ +-----+ +-----------------------+

>       |Interface for   | |SDN/  | |OSS/| |ADMIN| |Interface for logs,    |

>       |managing address| |Legacy| |BSS | |     | |DHCP, DNS, NAT, Address|

>       |space and pools | |      | |    | |     | |allocation records     |

>       +--------+-------+ +--+---+ +-+--+ +--+--+ +----------+------------+

o   |            |       |       |               ^

o   |            |       |       |               |

o   |            |       |       |               |

o   |            |       |       |               |

o   v            v       v       v               |

>       +---+------------+-------+-------+---------------+------+

>       |    Address Space Management (IPAM) System             |

>       |      +-----------+ +----------+ +--------+            |

>       |      | Pool      | |Address   | |Database|            |

>       |      | Management| |Management| |        |            |

>       |      +-----------+ +----------+ +--------+            |

>       |                                                       |

>       +-------------------------+-----------------------------+

o   |

>       +-----------v------------+

>       |Address Helper Plug|ins |

>       +----+--+------+-----+---+

>       |  |         |     |--------------------+

>       |  +----+    |                          |

>       |       |     ------------+             |

>       v       +----|            |             |

>       +--------+    +-----+  +----------+   +--------+

>       | DNS    |    |NAT  |  |  Address |   | DHCP   |

>       | Servers|    |     |  |  Mapping |   | Servers|

>       |        |    |     |  |  Systems |   |        |

>       +--------+    +-----+  +----------+   +--------+



As this is the framework draft, our main comments are about this figure:

1.      Given all the use cases in two use case draft, it seems this figure cannot cover all of the use cases.

2.      IPAM in the middle usually referred to IPAM tools, here I suggest use CASM system in the middle box if it's different from IPAM tools.

3.      There seems missing the NE at the bottom of this figure? Do you mean there is no direct interface toward NE?



**** Editorial ****

* Section 4

>       The requirements should be able to meet the

>       various use-cases identified in the draft.

s/in the draft/in use case draft , and better refer to use case draft here, as there is no use cases in this draft.

Regards,
Will LIU (LIU Shucheng)