Re: [L3sm] Followup of RFC8049bis

Hi Qin,

Any update on this?

     David

On 20/07/2017 16:36, Qin Wu wrote:
> In trip, will ping all other L2SM design team members for this, and get back to you.
>
> -Qin
> ________________________________________
> 发件人: David Ball [daviball@cisco.com]
> 发送时间: 2017年7月18日 19:56
> 收件人: Ogaki, Kenichi; Qin Wu; l3sm@ietf.org
> 抄送: 'Benoit Claise (bclaise)'; adrian@olddog.co.uk
> 主题: Re: [L3sm] Followup of RFC8049bis
>
> Qin, do you agree here?  Could we put some statement like this in section 5?
>
>       David
>
> On 14/07/2017 09:05, Ogaki, Kenichi wrote:
>> Hi David,
>>
>>> Another way of looking at it: would it be correct to say that the way the model is intended to be used is that the SP's system is the server and the customer's
>>> system is the client?
>> [KO] This best describes the rational of this model.
>>
>>> In that case, any information intended to be passed from the SP to the customer could be modelled with "config false", meaning that the
>>> SP could change it but the customer could not.
>> [KO] Yes, "config false" or NACM is utilized for this purpose.
>>
>> Thanks,
>> Kenichi
>>
>> -----Original Message-----
>> From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of David Ball
>> Sent: Thursday, July 13, 2017 8:30 PM
>> To: Ogaki, Kenichi; 'Qin Wu'; l3sm@ietf.org
>> Cc: 'Benoit Claise (bclaise)'; adrian@olddog.co.uk
>> Subject: Re: [L3sm] Followup of RFC8049bis
>>
>> Hi Kenichi,
>>
>>
>> On 13/07/2017 11:44, Ogaki, Kenichi wrote:
>>
>>
>>                Anyway, does the following paragraph in section 5 cover the rational?
>>
>>                The idea of the L3 IP VPN service model is to propose an abstracted
>>                    interface between customers and network operators to manage
>>                    configuration of components of an L3VPN service.  A typical scenario
>>                    would be to use this model as an input for an orchestration layer
>>                    that will be responsible for translating it to an orchestrated
>>                    configuration of network elements that will be part of the service.
>>
>>        To me, this paragraph does not clearly express that the information that needs to be passed from the SP to the customer is not in scope.  I would like to see that stated explicitly, if that is indeed the intent.
>>
>>        [KO] I can't agree with that.
>>        Even though the current model doesn't intend something, to exclude their future possibility only brings a disadvantage rather than an advantage.
>>        I can't see any major advantage to state that explicitly.
>>
>> I agree, we do not want to preclude future enhancements.  However, I do think this is critical to help an unfamiliar reader understand and use the model we have today.  How about text like this:
>>
>> "The version of the model described in this document does not include information that is passed from the SP to the customer.  This could be added in a future extension or augmentation."
>>
>> Another way of looking at it: would it be correct to say that the way the model is intended to be used is that the SP's system is the server and the customer's system is the client?  In that case, any information intended to be passed from the SP to the customer could be modelled with "config false", meaning that the SP could change it but the customer could not.
>>
>>
>>       David
>>
>>
> --
> David Ball
> <daviball@cisco.com>
> _______________________________________________
> L3sm mailing list
> L3sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l3sm

-- 
David Ball
<daviball@cisco.com>