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

Rakesh Kumar <rkkumar@juniper.net> Mon, 27 February 2017 18:37 UTC

Return-Path: <rkkumar@juniper.net>
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 1EE0A12A2CE; Mon, 27 Feb 2017 10:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.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 Cgs5af-HW91V; Mon, 27 Feb 2017 10:37:02 -0800 (PST)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0104.outbound.protection.outlook.com [104.47.40.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C183212A2D3; Mon, 27 Feb 2017 10:36:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=gsUihpWDDTDcTJoCKNCeblX6FJYK/QgXWc2oEpqo46g=; b=b9fyw0gA9p6rLYy0t+SU1kpDh+IyBmsd2RJhYeCsv6e7RU/2zMYKaA+TDqK2YBZgoh9EsM5ZZJ8Udm9d8Wc/ne/jprabGBl0YxAPE8PCha6x6HNdDbpZkhyBvQ3TzHiiVxigCaAChOVUgMxypb4OFIbgFt8pSwHbDQmnLjMuMms=
Received: from BN6PR05MB2993.namprd05.prod.outlook.com (10.173.19.11) by BN6PR05MB2996.namprd05.prod.outlook.com (10.173.19.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.2; Mon, 27 Feb 2017 18:36:56 +0000
Received: from BN6PR05MB2993.namprd05.prod.outlook.com ([10.173.19.11]) by BN6PR05MB2993.namprd05.prod.outlook.com ([10.173.19.11]) with mapi id 15.01.0947.011; Mon, 27 Feb 2017 18:36:56 +0000
From: Rakesh Kumar <rkkumar@juniper.net>
To: "Liushucheng (Will Liu)" <liushucheng@huawei.com>, "CASM@ietf.org" <CASM@ietf.org>, "draft-kumar-casm-requirements-and-framework@ietf.org" <draft-kumar-casm-requirements-and-framework@ietf.org>
Thread-Topic: [Casm] review of draft-kumar-casm-requirements-and-framework
Thread-Index: AQHSkSh5n31IqJpQXU2gjHN+W+5OBw==
Date: Mon, 27 Feb 2017 18:36:56 +0000
Message-ID: <F2D8D13B-D886-4148-BBDC-C1590B8F1887@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.17.0.160611
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rkkumar@juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [73.241.94.21]
x-microsoft-exchange-diagnostics: 1; BN6PR05MB2996; 7:KTwBMLM7myvS4uhXR6gDYC6Nl19fPDthX+pKZNB3bcRuM/eqHe/ciTTptwZvJ4az9tmCnFIcOZjp0jXDmM5mO5B2M6gp0WPrNzfKPkLqHKNujePFVhWo47cvpMmxsLUILcc8Nx+GdhtykzEDuouAg1mA9yjrxKFnBWsnmhbTyKMG+Bm6Edp7j6ZMIbSO5zNXTRprykohFr/G7i/1mlHaAPiUdqIVGLH9CtLG9kAmPCUqc5RjV9FnSTbXVflzy0fN3L0tfWJNLYRMmTtU3WrOkcGA5by8qThhFmy80ARq9yqDj8zjTYCGTgkwSaPF0TPjN8YMVhAE9+ZSAGuFyt3Kmw==
x-forefront-antispam-report: SFV:SKI; SCL:-1SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39840400002)(39860400002)(39850400002)(39450400003)(39410400002)(189002)(53754006)(199003)(377454003)(3846002)(229853002)(6486002)(83506001)(66066001)(6116002)(77096006)(102836003)(6506006)(53936002)(83716003)(7736002)(86362001)(2201001)(2906002)(107886003)(4326007)(6436002)(6246003)(38730400002)(2501003)(230783001)(8936002)(54356999)(50986999)(9326002)(4001350100001)(36756003)(25786008)(33656002)(97736004)(5660300001)(122556002)(3280700002)(3660700001)(68736007)(54896002)(8676002)(81156014)(6512007)(81166006)(101416001)(106356001)(105586002)(6306002)(54906002)(99286003)(92566002)(82746002)(53546006)(106116001)(189998001)(2900100001)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR05MB2996; H:BN6PR05MB2993.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
x-ms-office365-filtering-correlation-id: 6130c952-28d9-4189-979d-08d45f3f9bdf
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:BN6PR05MB2996;
x-microsoft-antispam-prvs: <BN6PR05MB29962629FB6141EECAE32602AD570@BN6PR05MB2996.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(35073007944872)(50582790962513)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123555025)(20161123560025)(20161123564025)(20161123562025)(6072148); SRVR:BN6PR05MB2996; BCL:0; PCL:0; RULEID:; SRVR:BN6PR05MB2996;
x-forefront-prvs: 02318D10FB
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_F2D8D13BD8864148BBDCC1590B8F1887junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2017 18:36:56.7291 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR05MB2996
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/1Olsa5PpL4dvFzA212n9uL3xlKo>
Cc: Rakesh Kumar <rkkumar@juniper.net>, "Pengtao \(Tony\)" <dr.pengtao@huawei.com>, "Xuweiping \(David\)" <xuweiping@huawei.com>
Subject: Re: [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: Mon, 27 Feb 2017 18:37:04 -0000

Hi Will,

Please see answers below with [Rakesh].

Thanks
Rakesh

From: CASM <casm-bounces@ietf.org> on behalf of "Liushucheng (Will Liu)" <liushucheng@huawei.com>
Date: Thursday, February 23, 2017 at 4:21 AM
To: "CASM@ietf.org" <CASM@ietf.org>rg>, "draft-kumar-casm-requirements-and-framework@ietf.org" <draft-kumar-casm-requirements-and-framework@ietf.org>
Cc: "Pengtao (Tony)" <dr.pengtao@huawei.com>om>, "Xuweiping (David)" <xuweiping@huawei.com>
Subject: [Casm] review of draft-kumar-casm-requirements-and-framework

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.



[Rakesh] We wanted to maintain separation between two drafts. One draft that summarizes possible use-cases for “CASM” and other creates a high level requirement in generic manner (not related any use-case in particular) and also propose a reference architecture.

*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.

[Rakesh] This is a reference architecture based on high level requirements. We should first see, whether the requirements generated from the use-case in mind are captured, once captured we should see how to fit this into same reference architecture.



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.



[Rakesh] I agree; I would say this was a “typo”.



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

[Rakesh] What do you mean “NE”? Is it networking element? If so, any device that request an IP address must either do through protocol (DHCP) or some proprietary mechanism. The proprietary system would interact with “CASM” at northbound side in the figure (interface for managing address).



**** 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.

[Rakesh] Will do.

Regards,
Will LIU (LIU Shucheng)