RE: Comments on draft-shaikh-rtgwg-policy-model

Hi Rob,

Agree with the case you presented, IMO, we may provide some guidance to implementation on the behavior to use when a local-tag is translated to a protocol-tag and translation is not possible due to protocol-tag constraint (for example “do not copy tag”).

From: Rob Shakir [mailto:rjs@rob.sh]
Sent: Tuesday, July 21, 2015 20:30
To: LITKOWSKI Stephane SCE/IBNF; Jeffrey Haas
Cc: rtgwg@ietf.org
Subject: RE: Comments on draft-shaikh-rtgwg-policy-model

Hi Stephane,

Thanks for the clarification.

The challenge that we might have here is that there are cases where I may want to match/set the ‘colour’ as well as an IGP tag. For instance, if I want to mark something in the RIB to say that it should be propagated to neighbour sets Amber, Blue and Cyan - which each have their own colour value - but these values also have an associated IGP tag. Given that we can have both, it seems to me that we should prefer to look at something that is like Option B.

IMHO, the intent of the tag we have today [0] is really to be the ‘generic colour’ type of tag, since we did not model IGP policies yet I don’t think that we examined this issue in too much detail — although Jeff and others have pointed it out before, and we marked it as something we did need to look at!

Best,
r.

[0]: I’d recommend using the latest version of the YANG, which is  at https://github.com/YangModels/yang/tree/master/experimental/openconfig/policy

On 21 July 2015 at 16:53:15, stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com> (stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>) wrote:
Sure ...

In the current version of the doc, option A is : single ‘tag’ type which can represent a protocol tag (it's only related to IGP tags in the draft)

So I would be in favor of option C :) (slight variation of option A) which is really single ‘tag’ type which can represent a protocol tag, or some purely local ‘colour’ attribute.

-----Original Message-----
From: Rob Shakir [mailto:rjs@rob.sh]
Sent: Tuesday, July 21, 2015 16:30
To: LITKOWSKI Stephane SCE/IBNF; Jeffrey Haas
Cc: rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: RE: Comments on draft-shaikh-rtgwg-policy-model

Folks,

There’s some ambiguity in the discussion here, from my perspective:

Option A: single ‘tag’ type which can represent a protocol tag, or some ‘colour’ attribute.
Option B: multiple ‘tag’ types, a generic ‘colour’ and then per-protocol tags.

Right now, oc-policy uses option A. I can see arguments for either - but Stephane I was not clear from your view which of these you prefer - can you clarify for me please?

Thanks,
r.

On 20 July 2015 at 15:30:56, stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com> (stephane.litkowski@orange.com(mailto:stephane.litkowski@orange.com))<mailto:stephane.litkowski@orange.com(mailto:stephane.litkowski@orange.com))> wrote:

>
> Inline
>
>
>
>
>
> From: Jeffrey Haas [mailto:jhaas@pfrc.org]
> Sent: Monday, July 20, 2015 16:05
> To: LITKOWSKI Stephane SCE/IBNF
> Cc: rtgwg@ietf.org<mailto:rtgwg@ietf.org>
> Subject: Re: Comments on draft-shaikh-rtgwg-policy-model
>
>
>
>
>
>
>
>
>
> >
> > On Jul 20, 2015, at 3:58 PM, stephane.litkowski@orange.com(mailto:stephane.litkowski@orange.com)<mailto:stephane.litkowski@orange.com(mailto:stephane.litkowski@orange.com)> wrote:
> >
> >
> >
> >
> >
> >
> > Right, each protocol has its own constraint, but do you think creating an additional generic marker will solve those constraints ? We would expect to be able to have the generic marker to protocol tag and also two protocol tags with different constraints to interact between each other (I mean for example, learning a RIP tag and copying it to ISIS or OSPF).
> >
> >
>
>
>
>
>
>
> My thought is that by not using an element that has protocol semantics, we can free the user from worrying about them when they don't care about whether the route will or will not get redistributed into a protocol that might use it. This is mostly to deal with your "local" property noted earlier.
>
>
>
>
>
>
> [SLI] Agree, that’s why I was pushing “tag” to be protocol agnostic and having only this tag and then let implementations to manage the translation to protocol tag when necessary.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> -- Jeff
>
>
>
>
>
>
>
> _________________________________________________________________________________________________________________________ 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.
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org<mailto:rtgwg@ietf.org>
> https://www.ietf.org/mailman/listinfo/rtgwg

_________________________________________________________________________________________________________________________

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.

_________________________________________________________________________________________________________________________

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.