Subject: Re: [L3sm] Suresh Krishnan's Discuss on draft-ietf-l3sm-l3vpn-service-model-18: (with DISCUSS)

From: <[email-masked]>
Date: Thu, 3 Nov 2016 08:18:02 +0000

Hi,

I added the new address allocation type. It will be part of the next revision.

Thanks,

From: Benoit Claise [mailto:[email-masked]]
Sent: Thursday, October 27, 2016 18:07
To: [email-masked]
Cc: Suresh Krishnan; Qin Wu; [email-masked]; 'The IESG'; [email-masked]; [email-masked]; [email-masked]
Subject: Re: Suresh Krishnan's Discuss on draft-ietf-l3sm-l3vpn-service-model-18: (with DISCUSS)

Dear authors,

We discussed https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/ballot/#suresh-krishnan during the IESG telechat.
It's now a COMMENT (as opposed to a DISCUSS), but there is an expectation that this issue will be addressed.

Adding a 5th address-allocation-type, dhcp-slaac, would solve the issue.
We can't think of any other valid combinations at this point.

We were also thinking in the direction of adding a sentence that address-allocation-type could be augmented in the future (for new type or new combinations). However, this is already covered by this generic statement.

   In addition, as for any YANG model, this service model can be

   augmented to implement new behaviors or specific features.  For

   example, this model proposes different options for IP address

   assignment, if those options are not filling all requirements, new

   options can be added through augmentation.
So I believe we're good.

Regards, B.

On 10/27/2016 02:08 AM, Qin Wu wrote:

Suresh:

I think it is good to make that text change to allow for future mechanisms but that does not address my concern. My question was how the model will support cases where more than one of the such mechanisms needs to be in use at the same time.

[Qin]:Let me make it clear, the base model doesn't support this case since isn't one allocation mechanism for a single point of attachment for a single site enough?, suppose you need to support both SLAAC and DHCP, we can define a new address-allocation-type (let's call it dhcp-slaac) as a new option in the base model extension rather than in base model, to support this case by augmentation. You may add a few parameters and YANG statements under container ipv4 and ipv6 to describe when address-allocation-type is dhcp-slaac what should be included. I can give you an example if needed.

Thanks Qin. That makes sense.

Regards

Suresh

_________________________________________________________________________________________________________________________

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.