Re: [OSPF] Comments on draft-ietf-ospf-node-admin-tag-00

Shraddha Hegde <shraddha@juniper.net> Fri, 27 February 2015 06:29 UTC

Return-Path: <shraddha@juniper.net>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B72211A893B for <ospf@ietfa.amsl.com>; Thu, 26 Feb 2015 22:29:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 CZ5uPK5z02gT for <ospf@ietfa.amsl.com>; Thu, 26 Feb 2015 22:29:37 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0146.outbound.protection.outlook.com [207.46.100.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2E291A893A for <ospf@ietf.org>; Thu, 26 Feb 2015 22:29:37 -0800 (PST)
Received: from BY1PR0501MB1381.namprd05.prod.outlook.com (25.160.107.139) by BY1PR0501MB1382.namprd05.prod.outlook.com (25.160.107.140) with Microsoft SMTP Server (TLS) id 15.1.93.16; Fri, 27 Feb 2015 06:29:35 +0000
Received: from BY1PR0501MB1381.namprd05.prod.outlook.com ([25.160.107.139]) by BY1PR0501MB1381.namprd05.prod.outlook.com ([25.160.107.139]) with mapi id 15.01.0093.004; Fri, 27 Feb 2015 06:29:35 +0000
From: Shraddha Hegde <shraddha@juniper.net>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "OSPF List (ospf@ietf.org)" <ospf@ietf.org>, "draft-ietf-ospf-node-admin-tag@tools.ietf.org" <draft-ietf-ospf-node-admin-tag@tools.ietf.org>
Thread-Topic: Comments on draft-ietf-ospf-node-admin-tag-00
Thread-Index: AdBPfSNCyUldFDN8QUWs01CQsfRW8gC0OLKg
Date: Fri, 27 Feb 2015 06:29:34 +0000
Message-ID: <BY1PR0501MB1381BF53FAD51BA9107887F3D5150@BY1PR0501MB1381.namprd05.prod.outlook.com>
References: <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE14@xmb-aln-x02.cisco.com>
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F4EF2EE14@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [116.197.184.12]
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1382;
x-microsoft-antispam-prvs: <BY1PR0501MB1382750B813E5229F4AADBA5CF150@BY1PR0501MB1382.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1382;
x-forefront-prvs: 05009853EF
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(13464003)(51914003)(377454003)(77156002)(66066001)(86362001)(76576001)(74316001)(107886001)(122556002)(15975445007)(102836002)(19580395003)(19580405001)(2900100001)(2950100001)(230783001)(99286002)(2501003)(33656002)(76176999)(50986999)(54356999)(46102003)(87936001)(92566002)(2656002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1382; H:BY1PR0501MB1381.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2015 06:29:34.9701 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1382
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/hh186lFgyzzj9wfs6nQXblFoYKk>
Subject: Re: [OSPF] Comments on draft-ietf-ospf-node-admin-tag-00
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2015 06:29:39 -0000

Les,

Thanks for the review and comments.
Pls see in-line..

I have some comments in this draft.

---Introduction
----------------
---I think the last sentence should be removed. It is providing an example of a use case - and as such is more appropriate for Section 5. 

---Also, node-tags are a property of the node - not of the routing protocol used to advertise them - I would like to see this point explicitly stated. Perhaps something like:

---"Per-node administrative tags are used to advertise an attribute of the node. As such they are independent of the routing protocol used to advertise them. "

<Shraddha> Will work on the rewording of introduction section.


Section 2
---------------

This section seems redundant w Section 1. It should be removed.

<Shraddha> I think this section is needed to explicitly imply that the tags are used for TE as well as non-TE applications.

Section 3 - Last Paragraph
----------------------------------
What is the reason for restricting the # of tags in a single TLV to 64? As OSPF TLVs have a 16 bit length field this restriction seems arbitrary.

<Shraddha> This was suggestion from Acee to restrict it to prevent the RI LSA overflowing. Since we have multi instanced RI-LSA this restriction can be removed.
                       Will update the draft for this.

Figure 1
-----------
The format of the ASCII art above needs to be corrected to properly indicate the field lengths.

<Shraddha> OK

Section 5
-------------

I would like to see this section moved to an Appendix. Since this section is not normative that would more clearly separate the normative/non-normative parts.

<Shraddha>Use cases section gives information on the motivation of the draft and looks necessary to be in the draft sections than moving it to appendix.

Rgds
Shraddha

-----Original Message-----
From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Les Ginsberg (ginsberg)
Sent: Monday, February 23, 2015 9:02 PM
To: OSPF List (ospf@ietf.org); draft-ietf-ospf-node-admin-tag@tools.ietf.org
Subject: [OSPF] Comments on draft-ietf-ospf-node-admin-tag-00

I have some comments in this draft.

Introduction
----------------
I think the last sentence should be removed. It is providing an example of a use case - and as such is more appropriate for Section 5. 

Also, node-tags are a property of the node - not of the routing protocol used to advertise them - I would like to see this point explicitly stated. Perhaps something like:

"Per-node administrative tags are used to advertise an attribute of the node. As such they are independent of the routing protocol used to advertise them. "




Section 2
---------------

This section seems redundant w Section 1. It should be removed.

Section 3 - Last Paragraph
----------------------------------
What is the reason for restricting the # of tags in a single TLV to 64? As OSPF TLVs have a 16 bit length field this restriction seems arbitrary.

Figure 1
-----------
The format of the ASCII art above needs to be corrected to properly indicate the field lengths.

Section 5
-------------

I would like to see this section moved to an Appendix. Since this section is not normative that would more clearly separate the normative/non-normative parts.

   Les

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf