Re: [Casm] CASM BoF request just posted to BoF wiki

Ralph Droms <rdroms.ietf@gmail.com> Thu, 09 February 2017 16:12 UTC

Return-Path: <rdroms.ietf@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 D19BD129B61 for <casm@ietfa.amsl.com>; Thu, 9 Feb 2017 08:12:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 UVt8cu3Fykb1 for <casm@ietfa.amsl.com>; Thu, 9 Feb 2017 08:12:04 -0800 (PST)
Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (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 86C81129B5E for <CASM@ietf.org>; Thu, 9 Feb 2017 08:12:04 -0800 (PST)
Received: by mail-qt0-x230.google.com with SMTP id k15so8226327qtg.3 for <CASM@ietf.org>; Thu, 09 Feb 2017 08:12:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=RmrN+o+ELpdWP+o8CLVK/Su20RZF91Q1GX9xAkt3bv0=; b=S9q7bird24nmxpOjIUQezdVUOdOG6zlYRmbVQRtjBB8GVRzI+pnv7ycE0xXmBMk8iu hBr7KTQE6Eq9thjK9mwaKSyD0ZXrl+YqBFfWRgH5/aHDE8VgygJsA+KXZVySKK33bMgb 7gPLZlES+H3nBXFhcNx+2mOIkiIKcC8vFvDqDzhWQCvpzvIfNp+SrwJDrgMi45C6trdk BeIojTNsiu6OROlMumt25eShHIUPQ4F7wGSFrROiov4GTlk4Cm+nsXj7yV5L4ksJ2ZJK 0+9Vah2futAwXwIM6K1s0ZHCPq4FdJLS9HbcRzPgUzVx4m4S72A6mpeavcXPVBYSRimq RqBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=RmrN+o+ELpdWP+o8CLVK/Su20RZF91Q1GX9xAkt3bv0=; b=Ql/2rfciLm1lC7kzTPpUwSscLnNuuxJV11FTLztkoI0QGLug1ywltDemf6Lf7ZklSK FKG+xBfzzfHalMeJgMf44XfvYov/SfpVBjX45EzH6rHpr6WSUiafgvq83kKw72039nRr d5ZfnenKn/4x7CY6DYYKAo0mEXD0QyVEy8j2X/652xsmd3uGvTAiDvxqrauqvc3x7juT 6FZ0+A5+PL391VCzbLeovsRnYjTwfXXEjFqpz1Aypyn9P1RKU8++q/3gGkhbQHXE2EV7 j5kCWpYXJ9COUCxugbGhMbVC131gL84qrZeBbnLDne2uLitbNUUB0fK2smrC4+gzjeL8 y9fQ==
X-Gm-Message-State: AMke39me6F0eG5Tu7NLLM18qM4dt6DqL6c4OgQzP8I2xZHM9kg2YAoqZR9hkCwbBXahGiQ==
X-Received: by 10.237.37.202 with SMTP id y10mr3774701qtc.170.1486656723705; Thu, 09 Feb 2017 08:12:03 -0800 (PST)
Received: from ?IPv6:2601:18f:801:600:ec4d:93bb:3e58:398? ([2601:18f:801:600:ec4d:93bb:3e58:398]) by smtp.gmail.com with ESMTPSA id r57sm9489773qtr.27.2017.02.09.08.12.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Feb 2017 08:12:03 -0800 (PST)
From: Ralph Droms <rdroms.ietf@gmail.com>
Message-Id: <FF81302C-8D24-4BF9-92AF-DE0AD02F321F@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7E19A86B-E900-44A8-9401-366B3C518CF2"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Thu, 9 Feb 2017 11:12:01 -0500
In-Reply-To: <09b401d282ed$9bced850$d36c88f0$@olddog.co.uk>
To: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>, "Liushucheng (Will)" <liushucheng@huawei.com>
References: <C9B5F12337F6F841B35C404CF0554ACB898C0D11@SZXEMA509-MBS.china.huawei.com> <09b401d282ed$9bced850$d36c88f0$@olddog.co.uk>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/casm/xkkrjnonEFYnBWDr0ey_H3F43qY>
Cc: CASM@ietf.org
Subject: Re: [Casm] CASM BoF request just posted to BoF wiki
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, 09 Feb 2017 16:12:08 -0000

> On Feb 9, 2017, at 11:00 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> 
> Thanks for posting this ahead of time, Will. It's helpful to be able to read it and think about it.

+1

>  
> Picking up on a point raised on the list and using Joel's suggestion...
>  
> Do you want to change "Centralized Address Management (CASM)" to "Coordinated Address Management (CASM)"? That does not preclude centralized solutions, but it also allows some degree of delegation as suggested by Brian.

Also +1

Prior work in this area from the dhc WG, esp. in DHCP failover protocols, may be of interest.

- Ralph

>  
> Thanks,
> Adrian
>  
> From: CASM [mailto:casm-bounces@ietf.org] On Behalf Of Liushucheng (Will)
> Sent: 09 February 2017 03:56
> To: CASM@ietf.org
> Subject: [Casm] CASM BoF request just posted to BoF wiki
>  
> Hi all,
>  
> I’m writing to notify you that the CASM BoF request was just posted in the bof wiki. https://trac.tools.ietf.org/bof/trac/ <https://trac.tools.ietf.org/bof/trac/>
> Many thanks for the efforts from Marc, Adrian, Rakesh and Chongfeng.
>  
> Please help to review it and let us know your thoughts. I’m copying it below.
>  
> --start--
> Centralized Address Management (CASM)
> 
> Description: Organizations use IP Address Space Management (IPAM) tools to manage their IP address space, often with proprietary database and interfaces. This work intends to evolve IPAM into standardized interfaces for centralized management of IP addresses, specially in the context of SDN/NFV networks. Use cases include dynamic allocation and release of IP addresses and prefixes based on usage (reallocation in case of no more in use) and/or user intent (for specific services).
> Agenda
> Problem statement and use cases
> Requirements and framework
> Possible charter goals and milestones
> Next steps
> Status: WG Forming
> Responsible AD: OPS (Benoit Claise, Joel Jaeggli)
> BoF proponents: Chongfeng Xie(China Telecom), Rakesh Kumar (Juniper), Ying Cheng(China Unicom), Will Liu(Huawei)
> BoF chairs: TBD
> Number of people expected to attend: 100
> Length of session (1, 1.5, 2, or 2.5 hours): 1.5 hours
> Conflicts to avoid (whole Areas and/or WGs): intarea, opsawg, anima, supa, dhc, nfvrg
> Mailing List: ​​https://www.ietf.org/mailman/listinfo/casm <https://www.ietf.org/mailman/listinfo/casm>
> Draft charter: TBD
> Relevant drafts:
> ​https://datatracker.ietf.org/doc/draft-kumar-casm-problem-and-use-cases <https://datatracker.ietf.org/doc/draft-kumar-casm-problem-and-use-cases>
> ​https://datatracker.ietf.org/doc/draft-xie-ps-centralized-address-management <https://datatracker.ietf.org/doc/draft-xie-ps-centralized-address-management>
> ​https://datatracker.ietf.org/doc/draft-kumar-casm-requirements-and-framework <https://datatracker.ietf.org/doc/draft-kumar-casm-requirements-and-framework>
> ​https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-arch <https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-arch>
> ​https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-yang <https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-yang>
> --end--
>  
> Regards,
> Will (LIU Shucheng)
>  
> _______________________________________________
> CASM mailing list
> CASM@ietf.org
> https://www.ietf.org/mailman/listinfo/casm