Re: vepc draft Rev. 04
Behcet Sarikaya <[email protected]>
| Newsgroups | gmane.ietf.nemo |
|---|---|
| Message-ID | <CAC8QAccadmdD0s6q1qCzY54xw8mVhqpAAHWKmh_+S7ZsMMpi+A__7196.76752710274$1433273167$gmane$org@mail.gmail.com> |
Hi Matsushima-san, On Fri, May 29, 2015 at 8:24 AM, Satoru Matsushima <[email protected]> wrote: > Hi Behcet-san, > > On Wed, May 27, 2015 at 5:34 AM, Behcet Sarikaya <[email protected]> > wrote: >> >> Hi Satoru, >> >> Thanks for your reply. >> >> Let me continue the discussion with your text in Section 3.2 where you >> mention >> vEPC may utilizes Forwarding Policy Configuration Protocol (FPCP) >> that defines FPCP Agent function and Client function. >> >> I don't understand how you could justify defining a new forwarding >> policy configuration protocol to do this Agent/Client functionality? >> Why not use similar Agent/Client models that are being defined rather >> than defining a new protocol? >> I think this point requires much stronger justification which I could >> not see in Section 3.2. >> > > The text just describes about a part of where FPCP may be applicable in > vEPC. > > > >> >> Are you that we have to to reinvent the wheel, rather than reusing >> something that is already available? How are we going to reinvent that >> wheel also remains to be seen, I think. >> > > Point taken. Which kind of wheel do you have in mind? Please check this draft: https://tools.ietf.org/html/draft-sarikaya-dmm-for-wifi-02 Regards, Behcet > > cheers, > --satoru >