Re: [OSPF] Poll for WG adoption of draft-hegde-ospf-node-admin-tag

<> Wed, 03 September 2014 10:25 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id D49E71A892B for <>; Wed, 3 Sep 2014 03:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ukiR8-BFZqqu for <>; Wed, 3 Sep 2014 03:25:10 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4C9E61A891F for <>; Wed, 3 Sep 2014 03:25:10 -0700 (PDT)
Received: from (unknown [xx.xx.xx.2]) by (ESMTP service) with ESMTP id 834E23B42D8; Wed, 3 Sep 2014 12:25:08 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown []) by (ESMTP service) with ESMTP id 53F4027C07D; Wed, 3 Sep 2014 12:25:08 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0195.001; Wed, 3 Sep 2014 12:25:08 +0200
From: <>
To: Peter Psenak <>, Rob Shakir <>
Thread-Topic: [OSPF] Poll for WG adoption of draft-hegde-ospf-node-admin-tag
Thread-Index: AQHPx1AVtvZWODn3ike5gZjbZZ1ijZvvLvew
Date: Wed, 3 Sep 2014 10:25:07 +0000
Message-ID: <15316_1409739908_5406EC84_15316_1787_1_53C29892C857584299CBF5D05346208A071EC421@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2014.6.25.100319
Cc: "" <>
Subject: Re: [OSPF] Poll for WG adoption of draft-hegde-ospf-node-admin-tag
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 03 Sep 2014 10:25:13 -0000

Hi Peter, Rob,

+1 on Rob's comment regarding the use of admin tag for expressing operator policy (rather than spec/feature capability)

1 point in lined below 

> From: Peter Psenak > Sent: Wednesday, September 03, 2014 10:21 AM
> Hi Rob,
> On 9/3/14 10:16 , Rob Shakir wrote:
> > Hi Peter,
> >
> > On 3 Sep 2014, at 09:13, Peter Psenak <> wrote:
> >
> >>> As per the above, I do not think that this mechanism replaces any
> capability, it just gives an operator a means to be more granular than the
> binary "supported"/"not supported" view that a flag indicating capabilities
> does.
> >>
> >> I understand. My point was that admin tags should not be used in cases
> where only a binary capability is signaled.
> >
> > ACK, I completely agree. Perhaps we should add something into the draft that the admin-tag should not be used for such a purpose.

> I would certainly appreciate that.

I agree as a general rule. Yet IMHO we should not kill this possibility. In particular for feature allowing incremental deployment & interaction with non-compliant nodes.
One example would have been Remote LFA (RLFA):
- the PLR (FRR node) needs to be RLFA compliant. Therefore (potential) communication between PLR regarding their capabilities can be done using IANA/implemented code point.
- the PQ node (Merge Point) does not need to be RLFA compliant. And we should keep this property to ease incremental deployment. Therefore communication between PQ and PLR regarding PQ capabilities should/may be done using node tag.  RLFA spec could have defined an IANA registered node tag to be used by PQ (configured by the network operator) to exclude them as PQ candidate. e.g. for PQ node not accepting T-LDP session or nodes which should not be used as PQ per policy.

> thanks,
> Peter
> >
> > Cheers,
> > r.
> >
> _______________________________________________
> OSPF mailing list


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.