IETF Logo Mail Archive

Re: [OSPF] RtgDir review: draft-ietf-ospf-link-overload-9

Shraddha Hegde <shraddha@juniper.net> Tue, 02 January 2018 05:22 UTC

Return-Path: <shraddha@juniper.net>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D98B712421A; Mon, 1 Jan 2018 21:22:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 EzLh2-t_AyiX; Mon, 1 Jan 2018 21:22:47 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81F9212025C; Mon, 1 Jan 2018 21:22:47 -0800 (PST)
Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id w025Mk7A001852; Mon, 1 Jan 2018 21:22:46 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=WDeWvHlj9LXcR3c710S9kxkU20ibaCJN5iWMexxBI/o=; b=qC39VMmkb/+7VJFdEgsqlak6BB9HCn1aelLayVjoUeItRfQzBjUDkXWDSzYbw5i6+L5y IENaMh1vAkjheqvw5LiuXYz+HdUZTpNJXsKzdey90Ry079GKgwmlnbEdiw9rFEEn+SAe XF0dV6/hxseVqz0D6VSeFewUK5DweZzhquWqPLqJXZbdVuHeBvAbpRQlZfaj2L7tTltQ 6uqRe9pIZd7bfh5nSxKacbq1cC0WNdiDZ5CFiNMcqkjykCBclMP4GLXLNexzArw3rLoJ NPX/x9af67bpma87xjA8XuZsS3uXqib/AhIYAODOy2fD8je3NYBLf1akc5asWih98oAg kQ==
Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp0081.outbound.protection.outlook.com [207.46.163.81]) by mx0b-00273201.pphosted.com with ESMTP id 2f83vjr00e-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 01 Jan 2018 21:22:46 -0800
Received: from CY1PR05MB2714.namprd05.prod.outlook.com (10.167.18.8) by CY1PR05MB2714.namprd05.prod.outlook.com (10.167.18.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.302.2; Tue, 2 Jan 2018 05:22:44 +0000
Received: from CY1PR05MB2714.namprd05.prod.outlook.com ([10.167.18.8]) by CY1PR05MB2714.namprd05.prod.outlook.com ([10.167.18.8]) with mapi id 15.20.0302.007; Tue, 2 Jan 2018 05:22:44 +0000
From: Shraddha Hegde <shraddha@juniper.net>
To: Martin Vigoureux <martin.vigoureux@nokia.com>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>
CC: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-ospf-link-overload@ietf.org" <draft-ietf-ospf-link-overload@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: RtgDir review: draft-ietf-ospf-link-overload-9
Thread-Index: AQHTexLMev7YBkC+yUq4XB/rQrmNNqNgFLXw
Date: Tue, 02 Jan 2018 05:22:44 +0000
Message-ID: <CY1PR05MB2714B3F0AA9E8575F1211834D5190@CY1PR05MB2714.namprd05.prod.outlook.com>
References: <44c0141a-bee1-6a79-079e-29f1ce90058b@nokia.com>
In-Reply-To: <44c0141a-bee1-6a79-079e-29f1ce90058b@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [116.197.184.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR05MB2714; 7:fXKLkUOL5dXye1/DAeAZ/upZXqC4Gbjvrvuugz58e+25fJQWegAvEpAKw9aRm6C9uW7DlpsUuXL+hZcMIWRKOYtKdv/l6KJpcxJUFtaDNMxKIP8MG8peYYKn1Pwf7M9wTixBwL0B4ni1grT+YpVQqy0N7APPnG4MuH5QkU4rG2viDUEq+zGyxotKZ+dqdDEMoctnFsjt98BQ+koOc+ax5uYMa6tQMykT86VRbPI+2FsEQ+N+c1RznrcUjUEIEN+V
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: cf4f150c-bead-4e98-44a7-08d551a0daa9
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020020)(48565401081)(4534040)(4602075)(4627136)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060); SRVR:CY1PR05MB2714;
x-ms-traffictypediagnostic: CY1PR05MB2714:
x-microsoft-antispam-prvs: <CY1PR05MB271417099CF46A8CC3EE89EED5190@CY1PR05MB2714.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162)(82608151540597);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(8121501046)(5005006)(10201501046)(3231023)(3002001)(93006095)(93001095)(6055026)(6041268)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(6072148)(201708071742011); SRVR:CY1PR05MB2714; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:CY1PR05MB2714;
x-forefront-prvs: 0540846A1D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39860400002)(366004)(346002)(396003)(39380400002)(51914003)(13464003)(51444003)(199004)(189003)(377424004)(305945005)(106356001)(53936002)(575784001)(2900100001)(76176011)(9686003)(316002)(86362001)(7736002)(81156014)(7696005)(97736004)(8656006)(33656002)(14454004)(3280700002)(8936002)(4326008)(2501003)(230783001)(478600001)(81166006)(74316002)(66066001)(4001150100001)(99286004)(110136005)(8676002)(68736007)(6116002)(102836004)(59450400001)(5660300001)(54906003)(25786009)(55016002)(6436002)(2906002)(3660700001)(53546011)(6246003)(77096006)(6506007)(2950100002)(229853002)(3846002)(105586002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR05MB2714; H:CY1PR05MB2714.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: SLXoieaRWdh0JN2RuFhJpzivtU5KwSbMZJjnCxwnaJc3OJVtByAzKmDLDAvnyBTKVwxOL/rOpTMHhUvy5Fp1Uw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: cf4f150c-bead-4e98-44a7-08d551a0daa9
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jan 2018 05:22:44.6842 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR05MB2714
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-02_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801020081
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/YgdoP9q3kRx-1Od2ObUJCkRMWA4>
Subject: Re: [OSPF] RtgDir review: draft-ietf-ospf-link-overload-9
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 02 Jan 2018 05:22:50 -0000

Martin,

Thanks for the detailed review and comments. 
I have added a new section 4.5 in -11 version on details of remote-ipv4 address and the need for it.
If you are talking about some other missing details, pls provide specific information.
Sometimes certain details seem trivial and well understood to authors but not so for others.

Rgds
Shraddha


-----Original Message-----
From: Martin Vigoureux [mailto:martin.vigoureux@nokia.com] 
Sent: Friday, December 22, 2017 4:21 PM
To: rtg-ads@ietf.org
Cc: rtg-dir@ietf.org; draft-ietf-ospf-link-overload@ietf.org; ospf@ietf.org
Subject: RtgDir review: draft-ietf-ospf-link-overload-9

Hello,

I have been selected as the Routing Directorate reviewer for this draft. 
The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see ​https://urldefense.proofpoint.com/v2/url?u=http-3A__trac.tools.ietf.org_area_rtg_trac_wiki_RtgDir&d=DwIDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=NyjLsr7JA7mvpCJa0YmPdVKcmMXJ31bpbBaNqzCNrng&m=mTTVgQyIphzdQXrtzuyX4FlD9pIHtdk57qE_gp8hgYY&s=d13HiGqS4KWdv0qkP-fD9NT1jEVnToFuz9wSPpaIzwc&e=

Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft.

Document: draft-ietf-ospf-link-overload-9
Reviewer: Martin Vigoureux
Review Date: 2017-12-22
IETF LC End Date: date-if-known
Intended Status: Standard Track

Summary:
This document is basically ready for publication, but has nits (see
Comments) that should be considered prior to publication.

Comments:
So, before accepting this review I took a look at the draft and told myself "oh, not long, not apparently complicated.". Then I started reading it...
I have to admit that beyond the apparent simplicity of the objective, I did not understand much at first read. So I went on reading the mailing list and discovered a field of information and more specifically discussions explaining why certain design choices were made.

These are missing in the draft. I think that we should not expect readers and implementers to dig into the mailing list to understand the design described in a draft.

So I'd like to encourage the authors to add some text which summarizes the discussions that happened on the list and which explains why such and such design was in the end decided.

Thanks
-m

v2.23.0 | Report a Bug | By Email