Re: [DMM] vepc draft Rev. 04

2015-05-29 Thread Satoru Matsushima
Hi Behcet-san, On Wed, May 27, 2015 at 5:34 AM, Behcet Sarikaya 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 functi

Re: [DMM] vepc draft Rev. 04 - /62s to UE, not /64s

2015-05-29 Thread Satoru Matsushima
Ah OK. thanks. Slightly off-topic, I think that there is still chance for tethering with single /64 if it is allocated as a off-link prefix. But yes, I agree with you. cheers, --satoru On Wed, May 27, 2015 at 8:31 PM, Alexandru Petrescu < alexandru.petre...@gmail.com> wrote: > Hi, > > In additi

Re: [DMM] FPC carrier ID and network ID question

2015-05-29 Thread Marco Liebsch
Hi Larry, thanks for your feedback and valid doubts, as you pointed out an important point to discuss. First of all, the space for a certain field in the ID can be increased. We may have a preceding discussion about how the identifier format should look like; as proposed in this version of the

Re: [DMM] vepc draft Rev. 04 - /62s to UE, not /64s

2015-05-29 Thread Alexandru Petrescu
Le 29/05/2015 15:30, Satoru Matsushima a écrit : Ah OK. thanks. Slightly off-topic, I think that there is still chance for tethering with single /64 if it is allocated as a off-link prefix. Yes, there is still such a chance. But it can not tether more than one single subnet. Connected vehicl

Re: [DMM] vepc draft Rev. 04 - /62s to UE, not /64s

2015-05-29 Thread Templin, Fred L
Hi Alex, > -Original Message- > From: dmm [mailto:dmm-boun...@ietf.org] On Behalf Of Alexandru Petrescu > Sent: Friday, May 29, 2015 10:59 AM > To: Satoru Matsushima > Cc: dmm > Subject: Re: [DMM] vepc draft Rev. 04 - /62s to UE, not /64s > > Le 29/05/2015 15:30, Satoru Matsushima a écrit

Re: [DMM] [dmm] #49 (ondemand-mobility): full on-demand mobility support

2015-05-29 Thread Alper Yegin
Hello Seil, > >> >> #49: full on-demand mobility support >> >> The three proposed flags express a "type" of source IP address an > application wants to get to the IP stack. Particularly, the sustained IP > address is proposed to provide on-demand IP session continuity, which > activates IP mobi

Re: [DMM] [dmm] #49 (ondemand-mobility): full on-demand mobility support

2015-05-29 Thread Alper Yegin
Hello Sergio, On May 22, 2015, at 6:24 PM, FIGUEIREDO Sergio wrote: > Hi Alper, > > As Seil wrote, the problem which this ticket intends to reflect is that of > non-optimal routing as a result of not being able to request a non-anchored > (or local) source IP address. A non-anchored (local)

Re: [DMM] [dmm] #49 (ondemand-mobility): full on-demand mobility support

2015-05-29 Thread FIGUEIREDO Sergio
Hi Alper, Thanks for the answer. Please check inline. On 29-05-2015 22:44, Alper Yegin wrote: Hello Sergio, On May 22, 2015, at 6:24 PM, FIGUEIREDO Sergio wrote: Hi Alper, As Seil wrote, the problem which this ticket intends to reflect is that of non-optimal routing as a result of not bein

[DMM] RES: [dmm] #49 (ondemand-mobility): full on-demand mobility support

2015-05-29 Thread FIGUEIREDO Sergio
I'm sorry but I had problems sending the previous message. Hope I succeed this time, my response is inline. De: dmm [dmm-boun...@ietf.org] em nome de FIGUEIREDO Sergio [sergio.figueir...@altran.com] Enviado: sexta-feira, 29 de maio de 2015 23:34 Para: Alper Yeg