Subject: Re: [netext] WG last call: draft-ietf-netext-pmip-cp-up-separation

From: <[email-masked]>
Date: Tue, 1 Apr 2014 08:12:54 +0000

Hi,

Sorry for the late answer,

>-----Message d'origine-----
>De : Ryuji Wakikawa [mailto:[email-masked]]
>Envoyé : jeudi 27 mars 2014 03:05
>À : SEITE Pierrick IMT/OLN
>Cc : [email-masked]; Hidetoshi Yokota
>Objet : Re: [netext] WG last call: draft-ietf-netext-pmip-cp-up-separation
>
>Hi Pierrick
>
>thanks for comments.
>
>2014/03/27 午前7:31、[email-masked] のメール：
>
>> Hi
>>
>> I support this draft; it adresses valid architecture scenario with separated
>control and data plane entities.
>> However architecture in figure 1 should be updated to clearly show this
>separation. Fig 1 put both mag cp and mag up within the same box, which is a
>bit confusing regarding the scope of the document.
>
>We will fix this.
>
>> Although out of scope of the document, it would be worth to give indication
>on interface between mag cp and up (eg Capwap based) in order to have the
>full picture on how the solution can work.
>
>We can clarify that this interface is out of scope.
>Do we need examples like capwap/forces/sdn in the document?
>

Yes, I think so. Also, if possible, you could give requirements for this interface. So, the reader could know if legacy CAPWAP (for example) could be used or if extensions are required.

BR,
Pierrick

>regards,
>ryuji
>
>
>
>>
>> Sent from my mobile
>>
>> ---- Hidetoshi Yokota <
>> [email-masked]> wrote ----
>> Hi authors,
>>
>> I think this is in good shape enough to go, but just one clarification question:
>>
>> In Section 6,
>>          When this variable on the MAG is set to a value of (0), the MAG
>>          must explicitly indicate its support-capability for this
>>          feature by including the LMA User Plane Address mobility Option
>>          in the
>> Proxy Binding Acknowledgement
>> .  If the option is not
>>          present in the Proxy Binding Update, the local mobility anchor
>>          will not enable this feature for that mobility session.
>>
>>
>> How can MAG indicate its support by PBA? Is it PBU or LMA does it by any
>chance? The same question applies in the following paragraph in the
>document.
>>
>> Regards,
>> --
>> Hidetoshi Yokota
>>
>> KDDI R&D Laboratories, Inc.
>>
>> e-mail:[email-masked]
>>
>>
>>
>>
>> (2014/03/13 3:42), Basavaraj Patil wrote:
>>> Hello,
>>>
>>> This is the working group last call for I-D: Separation of Control and User
>Plane for Proxy Mobile IPv6 <draft-ietf-netext-pmip-cp-up-separation-
>02.txt>.
>>>
>>> This I-D is intended to be progressed as a standards track document.
>>> Please review and post your comments on the mailing list.
>>> The last call will expire on March 27th, 14.
>>>
>>> -Chairs
>>>
>>>
>>>
>>> _______________________________________________
>>> netext mailing list
>>>
>>> [email-masked]
>>> https://www.ietf.org/mailman/listinfo/netext
>>
>>
>___________________________________________________________
>___________
>> ___________________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations
>> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
>> exploites ou copies sans autorisation. Si vous avez recu ce message
>> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les
>pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>Orange decline toute responsabilite si ce message a ete altere, deforme ou
>falsifie. Merci.
>>
>> This message and its attachments may contain confidential or
>> privileged information that may be protected by law; they should not be
>distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete
>this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been
>modified, changed or falsified.
>> Thank you.
>>
>> _______________________________________________
>> netext mailing list
>> [email-masked]
>> https://www.ietf.org/mailman/listinfo/netext

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.