Re: [OSPF] Alvaro's DISCUSS on OSPF Admin Tags

Shraddha Hegde <> Wed, 18 November 2015 04:28 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id BCB731AC428 for <>; Tue, 17 Nov 2015 20:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id F_6j9IE3f4Qu for <>; Tue, 17 Nov 2015 20:28:52 -0800 (PST)
Received: from ( [IPv6:2a01:111:f400:fc10::1:760]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 051281AC425 for <>; Tue, 17 Nov 2015 20:28:51 -0800 (PST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.1.325.17; Wed, 18 Nov 2015 04:28:33 +0000
Received: from ([]) by ([]) with mapi id 15.01.0325.019; Wed, 18 Nov 2015 04:28:33 +0000
From: Shraddha Hegde <>
To: "Acee Lindem (acee)" <>, Alia Atlas <>
Thread-Topic: [OSPF] Alvaro's DISCUSS on OSPF Admin Tags
Thread-Index: AQHRGWy0NezfSgA9Q0GdYS5ndTxcnJ6QyHcAgAT0xQCACTXy0IAACzuAgAAL7ICAAJxa4IAAj62AgAEJ32A=
Date: Wed, 18 Nov 2015 04:28:32 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-microsoft-exchange-diagnostics: 1; BY1PR0501MB1381; 5:Fd5b2oMS4TNi8pHKSp6UYnNhU1JCgaOKQaR+H9PKSucbWsGNC2c1Xl2CYe3DcOdpXa+5/u7Nin2QBRt4gjEI+mNpCRbAJBHPY3v2TQXT0fEkIGQGWc8Kzeh8Lx4QzY3LtiJMCx64WZQaAcaIl2FhZQ==; 24:Xun5J3GsI2lpwjFwTjp6jun1wr2O/ltbtQdFkk8e/uTke+4qXDaifFBdTN6h+1VG0TciQxVssfx4bc8sPQ/lUzyaC6A3sYwYYBPxxnSmSfs=; 20:RwbGWPaZOaqMR4lo6dqQjBumSXlrYYOFpxDhfy9Jl1yOmyTBdDHpO0rBUdU0gu1ZczaCXzVAgaD5Gi/Pe7ElOw==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1381;
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(138986009662008)(95692535739014)(108003899814671);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(520078)(8121501046)(10201501046)(3002001); SRVR:BY1PR0501MB1381; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1381;
x-forefront-prvs: 0764C4A8CD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(24454002)(377454003)(164054003)(199003)(189002)(19625215002)(5003600100002)(92566002)(40100003)(19580395003)(93886004)(5002640100001)(16236675004)(19580405001)(101416001)(106356001)(105586002)(77096005)(87936001)(76176999)(2900100001)(54356999)(15975445007)(102836002)(74316001)(50986999)(97736004)(19617315012)(5001770100001)(99286002)(86362001)(586003)(106116001)(122556002)(5001920100001)(19609705001)(2950100001)(66066001)(33656002)(19300405004)(5001960100002)(76576001)(189998001)(11100500001)(10400500002)(81156007)(5007970100001)(5008740100001)(5004730100002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1381;; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BY1PR0501MB1381BCBE72F010D0D9D7CE3FD51C0BY1PR0501MB1381_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Nov 2015 04:28:32.9333 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1381
Archived-At: <>
Cc: OSPF WG List <>, OSPF ADs <>
Subject: Re: [OSPF] Alvaro's DISCUSS on OSPF Admin Tags
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, 18 Nov 2015 04:28:58 -0000



From: Acee Lindem (acee) []
Sent: Tuesday, November 17, 2015 6:07 PM
To: Shraddha Hegde <>; Alia Atlas <>
Cc: OSPF WG List <>; OSPF ADs <>
Subject: Re: [OSPF] Alvaro's DISCUSS on OSPF Admin Tags

Hi Shraddha,

After considering Alvaro’s DISCUSS, I don’t think this restriction is necessary. I’d remove the paragraph.


From: Shraddha Hegde <<>>
Date: Monday, November 16, 2015 at 11:06 PM
To: Acee Lindem <<>>, Alia Atlas <<>>
Cc: OSPF WG List <<>>, OSPF ADs <<>>
Subject: RE: [OSPF] Alvaro's DISCUSS on OSPF Admin Tags

Hi Alia/Acee,

  Do you suggest to remove the  last paragraph in section 3.2.1 or remove the normative language?


From: Acee Lindem (acee) []
Sent: Tuesday, November 17, 2015 12:13 AM
To: Alia Atlas <<>>; Shraddha Hegde <<>>
Cc: OSPF WG List <<>>; OSPF ADs <<>>
Subject: Re: [OSPF] Alvaro's DISCUSS on OSPF Admin Tags

Hi Alia, Shraddha,

From: Alia Atlas <<>>
Date: Monday, November 16, 2015 at 1:00 PM
To: Shraddha Hegde <<>>
Cc: Acee Lindem <<>>, OSPF WG List <<>>, OSPF ADs <<>>
Subject: Re: [OSPF] Alvaro's DISCUSS on OSPF Admin Tags

Hi Shraddha & Acee,

On Mon, Nov 16, 2015 at 12:52 PM, Shraddha Hegde <<>> wrote:
Hi Acee/Alia,

Pls see inline..

From: Acee Lindem (acee) [<>]
Sent: Wednesday, November 11, 2015 2:11 AM
To: Alia Atlas <<>>
Cc: Shraddha Hegde <<>>; OSPF WG List <<>>; OSPF ADs <<>>
Subject: Re: [OSPF] Alvaro's DISCUSS on OSPF Admin Tags

Hi Alia, Shraddha,

From: Alia Atlas <<>>
Date: Sunday, November 8, 2015 at 1:59 AM
To: Acee Lindem <<>>
Cc: Shraddha Hegde <<>>, OSPF WG List <<>>, OSPF ADs <<>>
Subject: Re: [OSPF] Alvaro's DISCUSS on OSPF Admin Tags

Hi Acee,

Thanks very much for reading through and pulling out the relevant questions.
I'd like to see this conversation resolve quickly.

On Sat, Nov 7, 2015 at 9:58 AM, Acee Lindem (acee) <<>> wrote:
Hi Shraddha,

I’ve read through this discussion and I’m wondering why we just can’t
remove this normative text with respect to the interpretation of OSPF Node
Admin tags?

   1. Since the tags are advertised by a single node, why is do they have
to be unordered? It seems there should be a reason for this even if this
semantic is retained.

I can understand this restriction in terms of implementation complexity &
assumptions.  A router that receives the tag list might want to store them in
numerical order or such for easier searching.  If the tag order matters, there
can be rather different requirements in terms of how the listener uses the

Perhaps the answer is that we don’t see a use case for maintaining tag order given that they may come from multiple sources it adds a lot of complexity to try and maintain order. Note that the order independence is also in RFC 5130 (IS-IS prefix admin tags) - see section 4.

<Shraddha> The restriction of keeping the tag set unordered ensures that the vendor policy implementations will use node tags as a set and not as an ordered list.
                       Since there are no standards defined for policy module, its hard for the operators  to guess how the vendor policy implementations behave.
                       I think the explicit mention of the tag ordering ensures there is no ambiguity in interpreting the tags.

 Ok - this makes sense to me.  Let's keep that restriction.

I’m ok with this as well. There is precedence with non-order dependence with the IS-IS Admin Tags (Section 4 in RFC 5140).

   2. Why can’t they be advertised in multiple flooding scopes? There
could be one set of tags applicable at the area scope and another
applicable at the AS wide scope.

I agree that I don't see implementation complexity logic driving this.  Perhaps
it allows for storing tags per device in a flat structure instead of requiring that
they are stored per area?

I wouldn’t think so.

Regardless, this feels like it has more impact on operational complexity of
having to define the same meaning for different tags for different areas.

This restriction of a single flooding scope wouldn’t preclude this.
<Shraddha> Tags are independent characteristics of a node. It’s perfectly valid to advertise same tag in different areas so operator need not
                       Define different tags having same meaning for different areas.
                       Since tags are independent characteristics it is well defined whether that characteristic need to be seen by AS wide nodes
                       Or area wide nodes.

This sounds like an assumption on the meaning for tags that they won't need to be sent in different
scopes.  I'm not hearing a strong reason to force this assumption.  Let's relax it in the draft.


If the WG is ok with this resolution, could we get an updated draft this week so I can approve the draft?

Sounds good.





In essence, since the tags are purely opaque, it seems you could simply
remove the last 2-3 paragraphs of section 3.2.1 and the last paragraph of
section 3.2.2 as these seem to be rather arbitrary restrictions.


OSPF mailing list<>