Re: [Casm] New Version Notification for draft-kumar-requirements-and-framework-00.txt

[Benoit Claise <[e-mail]>]

On 2/15/2017 2:27 AM, Xie Chongfeng wrote:
> Hi, Benoit,
>
> Thank you for your notififying me. we are updating the 3 drafts and 
> will submit them soon.
Does it mean that you consider those 3 drafts as potential outcomes for 
CASM?
If yes, here is a question I asked to the mailing list:

    If the solution is this YANG module, based on
    draft-sun-i2apm-address-pool-management-arch, should we jump
    directly to the solution? In other words, what is the BoF added
    value? Note: I thought that those two drafts received some (mild)
    support in OPSAWG already in IETF 94.

Or maybe the 3 drafts are not complete. So what's missing?

Trying to understand.

Regards, Benoit
>
>
> Best regards
> Chongfeng
>
>
> ------------------------------------------------------------------------
> [e-mail]
>
>     *From:* Benoit Claise <mailto:[e-mail]>
>     *Date:* 2017-02-14 23:50
>     *To:* Xie Chongfeng <mailto:[e-mail]>; Rakesh
>     Kumar <mailto:[e-mail]>; 'Liushucheng (Will)'
>     <mailto:[e-mail]>; [e-mail]
>     <mailto:[e-mail]>
>     *CC:* ian.farrer <mailto:[e-mail]>; normen.kowalewski
>     <mailto:[e-mail]>; [e-mail]
>     <mailto:[e-mail]>
>     *Subject:* Re: [Casm] New Version Notification for
>     draft-kumar-requirements-and-framework-00.txt
>     Chongfeng,
>
>     For my understanding...
>     So the plan is to stop working on these three drafts in OPSAWG?
>
>         draft-xi-ps-centralized-address-management
>         <http://tools.ietf.org/html/draft-xi-ps-centralized-address-management>    
>         expired
>         draft-sun-i2apm-address-pool-management-arch
>         <http://tools.ietf.org/html/draft-sun-i2apm-address-pool-management-arch>
>         expired
>         draft-sun-i2apm-address-pool-management-yang
>         <http://tools.ietf.org/html/draft-sun-i2apm-address-pool-management-yang> 
>         expired
>
>     Regards, Benoit
>>     Yes, I agree to  combine all ideas into one set of drafts to push
>>     forward this work.
>>
>>     BUT  I didn't find any major difference between CASM and the old
>>     drafts, major use cases of centralized address management has
>>     been considered in the old PS draft
>>     (https://datatracker.ietf.org/doc/draft-xie-ps-centralized-address-management/),
>>     including the DNS and NAT. CT put forward the use case of address
>>     management in metro network,  Ian and norman of DT raised the
>>     case of address management for OpenStack, OSS,etc.
>>
>>     So, I think it is necessary to clarify the relationship of these
>>     drafts. Thank you!
>>
>>     Chongfeng
>>
>>     ------------------------------------------------------------------------
>>     [e-mail]
>>
>>         *From:* Rakesh Kumar <mailto:[e-mail]>
>>         *Date:* 2017-02-03 14:37
>>         *To:* Liushucheng (Will) <mailto:[e-mail]>;
>>         Marc Blanchet <mailto:[e-mail]>; Xie
>>         Chongfeng <mailto:[e-mail]>
>>         *CC:* [e-mail] <mailto:[e-mail]>
>>         *Subject:* Re: [Casm] New Version Notification for
>>         draft-kumar-requirements-and-framework-00.txt
>>         Hi Will,
>>         The draft we wrote was based on the slide set we had
>>         presented earlier, that details a comprehensive approach to
>>         address management including with other address services such
>>         as DNS and NAT. We have also introduced the concept of
>>         interfaces based on user requirements.
>>         I think, it would be good idea to combine all ideas into one
>>         set of drafts.
>>         I think, CASM would also be useful for mining data for
>>         security related analytics.
>>         Thanks
>>         Rakesh
>>         On 2/2/17, 10:26 PM, "CASM on behalf of Liushucheng (Will)"
>>         <[e-mail] on behalf of [e-mail]>
>>         wrote:
>>             Hi Rakesh,
>>             Many thanks for your efforts!
>>             No worries. Let's review and update in next version. And
>>         maybe another online meeting in next week.
>>             Btw, there are also some old work on this area as we
>>         discussed:
>>         https://datatracker.ietf.org/doc/draft-xie-ps-centralized-address-management/
>>         https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-arch/
>>         https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-yang/
>>             Would you please let the audience know about the
>>         differences between new ones and old ones?
>>             Regards,
>>             Will (LIU Shucheng)
>>             -----Original Message-----
>>             From: CASM [mailto:[e-mail]] On Behalf Of
>>         Marc Blanchet
>>             Sent: Monday, January 30, 2017 9:02 PM
>>             To: Rakesh Kumar <[e-mail]>
>>             Cc: [e-mail]
>>             Subject: Re: [Casm] New Version Notification for
>>         draft-kumar-requirements-and-framework-00.txt
>>             On 30 Jan 2017, at 1:43, Rakesh Kumar wrote:
>>             > It looks like we messed up on the name. My mistake.
>>             >
>>             > It should have been
>>             > “draft-kumar-casm-requirements-and-framework-00”
>>         instead of
>>             > “draft-kumar-requirements-and-framework-00”.
>>             > Is there a way to correct it?
>>             yeah. no big deal. we shall fix it for the new rev.
>>             Marc.
>>             >
>>             > Thanks
>>             > Rakesh
>>             >
>>             > On 1/29/17, 8:03 PM, "CASM on behalf of Rakesh Kumar"
>>             > <[e-mail] on behalf of
>>         [e-mail]> wrote:
>>             >
>>             >
>>             >
>>             >     On 1/29/17, 7:53 PM, "[e-mail]"
>>             > <[e-mail]> wrote:
>>             >
>>             >
>>             >         A new version of I-D,
>>             > draft-kumar-requirements-and-framework-00.txt
>>             >         has been successfully submitted by Marc
>>         Blanchet and posted to
>>             > the
>>             >         IETF repository.
>>             >
>>             >         Name: draft-kumar-requirements-and-framework
>>             >         Revision: 00
>>             >         Title: Centralized Address Space Management(CASM)
>>             > Requirements and Framework
>>             >         Document date: 2017-01-29
>>             >         Group: Individual Submission
>>             >         Pages: 8
>>             >         URL:
>>             >
>>         https://www.ietf.org/internet-drafts/draft-kumar-requirements-and-framework-00.txt
>>             >         Status:
>>             >
>>         https://datatracker.ietf.org/doc/draft-kumar-requirements-and-framework/
>>             >         Htmlized:
>>             >
>>         https://tools.ietf.org/html/draft-kumar-requirements-and-framework-00
>>             >
>>             >
>>             >         Abstract:
>>             >            The organizations use IP Address Space
>>         Management (IPAM)
>>             > tools to
>>             >            manage their IP address space, often with
>>         proprietary
>>             > database and
>>             >            interfaces.  This document describes
>>         evolution of IPAM into
>>             > a
>>             >            standardized interfaces for centralized
>>         management of IP
>>             > addresses.
>>             >
>>             >
>>             >
>>             >
>>             >         Please note that it may take a couple of
>>         minutes from the time
>>             > of submission
>>             >         until the htmlized version and diff are
>>         available at
>>             > tools.ietf.org.
>>             >
>>             >         The IETF Secretariat
>>             >
>>             >
>>             >
>>             > _______________________________________________
>>             >     CASM mailing list
>>             > [e-mail]
>>             > https://www.ietf.org/mailman/listinfo/casm
>>             >
>>             >
>>             > _______________________________________________
>>             > CASM mailing list
>>             > [e-mail]
>>             > https://www.ietf.org/mailman/listinfo/casm
>>         _______________________________________________
>>             CASM mailing list
>>         [e-mail]
>>         https://www.ietf.org/mailman/listinfo/casm
>>         _______________________________________________
>>             CASM mailing list
>>         [e-mail]
>>         https://www.ietf.org/mailman/listinfo/casm
>>
>