Re: Alvaro Retana's No Objection on draft-ietf-rtgwg-lfa-manageability-09: (with COMMENT)

Alia Atlas <akatlas@gmail.com> Wed, 24 June 2015 14:34 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCF151ACC8C; Wed, 24 Jun 2015 07:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level:
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SoQgla4T10w4; Wed, 24 Jun 2015 07:34:10 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F8661ACCEF; Wed, 24 Jun 2015 07:34:10 -0700 (PDT)
Received: by oigb199 with SMTP id b199so31115192oig.3; Wed, 24 Jun 2015 07:34:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UtK/EVMSJgIgZ1HQd5FIeWgHBCB3rc/ztjpBl9vTI+o=; b=YEzrjm1C5DZTx/UL2NpU2lctVknq55IbEHpBUBvNOvQ1BCZ2MT8m/ZMkzwWKt0iBcs H+5ZhJnAOe0OjUK0AadMr5++ljHbTj6DchEwiAqFnTM4visxbqFig7flpaKtnMbOWCPZ UVbe4jAJJaL/o2CwPP7OsA+qJvVOqORmBLfiPfcGVWJCAUpre2M3Xw8x6f1AKpgELfJB WlsT37i3GORHuTWq4KSLPwuUIgn4Fzna24zna/iOsb0/rBJhhtnHsfq7Yj3w0p0f5J0S TuwAlJrJFqPwDMno5Y7wIlcGvqSaYrNtp/cKNnzvzWo7+Oguke/Yls/zhwWkKVrRMufs DiFw==
MIME-Version: 1.0
X-Received: by 10.60.74.34 with SMTP id q2mr35007999oev.68.1435156449664; Wed, 24 Jun 2015 07:34:09 -0700 (PDT)
Received: by 10.60.165.145 with HTTP; Wed, 24 Jun 2015 07:34:09 -0700 (PDT)
In-Reply-To: <21634_1435138901_558A7B54_21634_3497_16_9E32478DFA9976438E7A22F69B08FF921667862D@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <20150622144146.17459.58140.idtracker@ietfa.amsl.com> <18969_1435051333_55892544_18969_971_1_9E32478DFA9976438E7A22F69B08FF9216677F92@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <D1AED6D1.B96B9%aretana@cisco.com> <21634_1435138901_558A7B54_21634_3497_16_9E32478DFA9976438E7A22F69B08FF921667862D@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Date: Wed, 24 Jun 2015 10:34:09 -0400
Message-ID: <CAG4d1rfvZzM8Op2P8PrFkG_6Hkc9ixojmaKxdkg9nAmYh2F2YQ@mail.gmail.com>
Subject: Re: Alvaro Retana's No Objection on draft-ietf-rtgwg-lfa-manageability-09: (with COMMENT)
From: Alia Atlas <akatlas@gmail.com>
To: Stephane Litkowski <stephane.litkowski@orange.com>
Content-Type: multipart/alternative; boundary=001a1135fc5a612365051944668f
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/9qNxqjyWhsCyivz59Ujl6yOEVRA>
Cc: "draft-ietf-rtgwg-lfa-manageability@tools.ietf.org" <draft-ietf-rtgwg-lfa-manageability@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "iesg@ietf.org" <iesg@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jun 2015 14:34:14 -0000

I'm fine with clarifying that the existing mechanisms are an example and
not prescriptive.  On the other hand, if different implementations pick
different mechanisms, that's going to cause problems.  Frankly, there have
been admin-groups for a long time now and it's clear those are one of the
things that is meant.  However, the node admin tags have a specific
use-case for node-protecting RLFA - so having a pointer to them as a
possible mechanism is IMHO useful.

Alia

On Wed, Jun 24, 2015 at 5:41 AM, <stephane.litkowski@orange.com> wrote:

> Hi Alvaro, Alia
>
> > From Alvaro Retana> (aretana)
> > Sent: Tuesday, June 23, 2015 3:44 PM
> > To: LITKOWSKI Stephane SCE/IBNF
> > Cc: draft-ietf-rtgwg-lfa-manageability@tools.ietf.org; Brian Haberman;
> > iesg@ietf.org; rtgwg@ietf.org
> > Subject: Re: Alvaro Retana's No Objection on draft-ietf-rtgwg-lfa-
> > manageability-09: (with COMMENT)
> >
> > On 6/23/15, 5:22 AM, "stephane.litkowski@orange.com"
> > <stephane.litkowski@orange.com> wrote:
> >
> > Stephane:
> >
> > I¹m looping everyone else back in..I know Brian had the same comment.
> >
> > >For the point #3, we had a comment from Alia on the list saying that
> > >we needed to point to some existing solutions.
> > >
> > >We propose to change the text as follows :
> > >BEFORE :
> > >Link color information SHOULD be signalled in the IGP.  How
> > >   signalling is done is out of scope of the document but it may be
> > >   useful to reuse existing admin-groups from traffic-engineering
> > >   extensions or link attributes extensions like in
> > >   [I-D.ietf-ospf-prefix-link-attr].
> > >NEW TEXT :
> > > Link color information SHOULD be signalled in the IGP in order to
> > >limit configuration effort.  e.g.
> > >   [I-D.ietf-ospf-prefix-link-attr], [RFC5305], [RFC3630] ...
> > >
> > >Does it work ?
> >
> > Honestly, both options point at the same thing: the suggestion (at
> > least) of a solution.  I am completely in favor of reusing
> > technology/ideas/drafts if they will help solve the problem.  My point
> > is that this document is not specifying solutions, just requirements..if
> that is true, then don¹t point at the solutions.
> > OTOH, if this document is to specify solutions, then lets do that.
> >
> > Having said all that, I can defer to Alia.  However, please at least
> > make it clear that the solutions you are pointing to are just that
> (pointers).
> > In the text above I would rather keep the original text that clearly
> > states that solutions are out of scope.  The text in 6.2.4.4 doesn¹t
> > explicitly say that the solutions are not in scope.
>
> CURRENT text is:
>    Link color information SHOULD be signalled in the IGP.  How
>    signalling is done is out of scope of the document but it may be
>    useful to reuse existing admin-groups from traffic-engineering
>    extensions or link attributes extensions like in
>    [I-D.ietf-ospf-prefix-link-attr].
>
> My understanding is that you are calling for removing the pointer to the
> solution (and do the same thing for the node color section) or pushing for
> solutions.
>
> CANDIDATE1: we can limit the text to :
> "Link color information SHOULD be signaled in the IGP.  " and do the same
> thing for the node color.
>
>
> We would be ok for this, but, this seems like a different direction
> compared to a previous comment from Alia who had previously proposed to
> _add_ reference to solution drafts, including  ospf-prefix-link-attr:
> > From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Alia Atlas
> > Sent: Friday, June 12, 2015 4:23 PM
> > To: LITKOWSKI Stephane SCE/IBNF
> > Cc: draft-ietf-rtgwg-lfa-manageability@tools.ietf.org; rtgwg@ietf.org
> > Subject: Re: AD Review of draft-ietf-rtgwg-lfa-manageability
> [...]
> > 4) In Sec 6.2.7, you might be interested in the link/node-attribute
> drafts that are being finished.
> > [SLI] Could you give me the pointers of drafts you are thinking about ?
> >You have the ISIS one for node admin tags.  I was also thinking of
> >draft-ietf-ospf-node-admin-tag-02  and
> >draft-ietf-ospf-prefix-link-attr-06.  For ISIS, it looks like the similar
> draft  only provides for prefix attributes and not link ones.
>
> Since you deferred to Alia, and "would rather keep the original text", our
> current understanding is to keep CURRENT text which has been revised as per
> Alia's comment.
> Alia, Alvaro, please advise/propose text if this you prefer something
> different.
>
>
> Best regards,
>
>
> -----Original Message-----
> From: Alvaro Retana (aretana) [mailto:aretana@cisco.com]
> Sent: Tuesday, June 23, 2015 15:44
> To: LITKOWSKI Stephane SCE/IBNF
> Cc: rtgwg@ietf.org; draft-ietf-rtgwg-lfa-manageability@tools.ietf.org;
> iesg@ietf.org; Brian Haberman
> Subject: Re: Alvaro Retana's No Objection on
> draft-ietf-rtgwg-lfa-manageability-09: (with COMMENT)
>
> On 6/23/15, 5:22 AM, "stephane.litkowski@orange.com"
> <stephane.litkowski@orange.com> wrote:
>
> Stephane:
>
> I¹m looping everyone else back in..I know Brian had the same comment.
>
> >For the point #3, we had a comment from Alia on the list saying that we
> >needed to point to some existing solutions.
> >
> >We propose to change the text as follows :
> >BEFORE :
> >Link color information SHOULD be signalled in the IGP.  How
> >   signalling is done is out of scope of the document but it may be
> >   useful to reuse existing admin-groups from traffic-engineering
> >   extensions or link attributes extensions like in
> >   [I-D.ietf-ospf-prefix-link-attr].
> >NEW TEXT :
> > Link color information SHOULD be signalled in the IGP in order to
> >limit configuration effort.  e.g.
> >   [I-D.ietf-ospf-prefix-link-attr], [RFC5305], [RFC3630] ...
> >
> >Does it work ?
>
> Honestly, both options point at the same thing: the suggestion (at least)
> of a solution.  I am completely in favor of reusing technology/ideas/drafts
> if they will help solve the problem.  My point is that this document is not
> specifying solutions, just requirements..if that is true, then don¹t point
> at the solutions.  OTOH, if this document is to specify solutions, then
> lets do that.
>
> Having said all that, I can defer to Alia.  However, please at least make
> it clear that the solutions you are pointing to are just that (pointers).
> In the text above I would rather keep the original text that clearly
> states that solutions are out of scope.  The text in 6.2.4.4 doesn¹t
> explicitly say that the solutions are not in scope.
>
> Thanks!
>
> Alvaro.
>
>
>
> >3. In Section 6.2.4.2 the document talks about signaling color
> >information, it includes a set of requirements..and it reads ³How
> >signaling is done is out of scope of the document², but then you go on
> >and point to a specific solution.  Even if there might be a high
> >certainty that the solution you point at is moving on in the process,
> >is good, should be used, etc..  I think this document would be better
> >served by just defining the requirements (specially if you¹re pointing at
> the
> >solution as out of scope).   You do the same in 6.2.4.4.
>
>
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
>