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

["Liushucheng (Will)" <[e-mail]>]

Hi Adrian and all,

Thanks for your comments. The proponents discussed and agreed with “coordinated”.

However, seems we missed the “Space” in title ?  Should be *“Coordinated Address Space Management”* instead of “Coordinated Address Management”. I  just fixed this on wiki.

Regards,
Will (LIU Shucheng)

From: Adrian Farrel [mailto:[e-mail]]
Sent: Friday, February 10, 2017 12:00 AM
To: Liushucheng (Will) <[e-mail]>; [e-mail]
Subject: RE: [Casm] CASM BoF request just posted to BoF wiki

Thanks for posting this ahead of time, Will. It's helpful to be able to read it and think about it.

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.

Thanks,
Adrian

From: CASM [mailto:[e-mail]] On Behalf Of Liushucheng (Will)
Sent: 09 February 2017 03:56
To: [e-mail]<mailto:[e-mail]>
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/
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
o  Problem statement and use cases
o  Requirements and framework
o  Possible charter goals and milestones
o  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:
o  ​https://datatracker.ietf.org/doc/draft-kumar-casm-problem-and-use-cases<https://datatracker.ietf.org/doc/draft-kumar-casm-problem-and-use-cases>
o  ​https://datatracker.ietf.org/doc/draft-xie-ps-centralized-address-management<https://datatracker.ietf.org/doc/draft-xie-ps-centralized-address-management>
o  ​https://datatracker.ietf.org/doc/draft-kumar-casm-requirements-and-framework<https://datatracker.ietf.org/doc/draft-kumar-casm-requirements-and-framework>
o  ​https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-arch<https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-arch>
o  ​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)